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 0812f22bbb..4388166f97 100644 --- a/translations/de-DE/content/actions/creating-actions/about-actions.md +++ b/translations/de-DE/content/actions/creating-actions/about-actions.md @@ -33,8 +33,8 @@ Sie können Docker-Container- und JavaScript-Aktionen erstellen. Für Aktionen w | Typ | Betriebssystem | | ------------------------------------ | --------------------- | | Docker-Container | Linux | -| JavaScript | Linux, MacOS, Windows | -| Zusammengesetzte Ausführungsschritte | Linux, MacOS, Windows | +| JavaScript | Linux, macOS, Windows | +| Zusammengesetzte Ausführungsschritte | Linux, macOS, Windows | #### Docker-Containeraktionen diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md index c399dd557c..37c36fd7d0 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md @@ -226,6 +226,10 @@ Jobs: ``` {% endraw %} -Klicke in Deinem Repository auf die Registerkarte **Actions** (Aktionen), und wähle die neueste Workflow-Ausführung aus. Es sollten „Hello Mona the Octocat“ oder der von Dir für die Eingabe `who-to-greet` verwendete Name und der im Protokoll ausgegebene Zeitstempel angezeigt werden. +Klicke in Deinem Repository auf die Registerkarte **Actions** (Aktionen), und wähle die neueste Workflow-Ausführung aus. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Ein Screenshot zur Verwendung Deiner Aktion in einem Workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png) +{% else %} ![Ein Screenshot zur Verwendung Deiner Aktion in einem Workflow](/assets/images/help/repository/docker-action-workflow-run.png) +{% endif %} diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md index 1d44eb633e..d0e537f72b 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md @@ -176,7 +176,7 @@ git tag -a -m "Mein erstes Aktions-Release" v1 git push --follow-tags ``` -As an alternative to checking in your `node_modules` directory you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. +Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. 1. Install `vercel/ncc` by running this command in your terminal. `npm i -g @vercel/ncc` @@ -256,9 +256,11 @@ Jobs: ``` {% endraw %} -Klicke in Deinem Repository auf die Registerkarte **Actions** (Aktionen), und wähle die neueste Workflow-Ausführung aus. Es sollten „Hello Mona the Octocat“ oder der von Dir für die Eingabe `who-to-greet` verwendete Name und der im Protokoll ausgegebene Zeitstempel angezeigt werden. +Klicke in Deinem Repository auf die Registerkarte **Actions** (Aktionen), und wähle die neueste Workflow-Ausführung aus. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Ein Screenshot zur Verwendung Deiner Aktion in einem Workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} ![Ein Screenshot zur Verwendung Deiner Aktion in einem Workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png) {% else %} ![Ein Screenshot zur Verwendung Deiner Aktion in einem Workflow](/assets/images/help/repository/javascript-action-workflow-run.png) 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 a7da6feb63..62834275fe 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 @@ -22,19 +22,19 @@ Für Docker- und JavaScript-Aktionen ist eine Metadatendatei erforderlich. Der D Aktionsmetadatendateien verwenden die 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)“. -### **`name`** +### `name` **Required** (Erforderlich): Der Name Deiner Aktion. {% data variables.product.prodname_dotcom %} zeigt den `name` auf der Registerkarte **Actions** an, damit Du die Aktionen in jedem Auftrag visuell identifizieren kannst. -### **`Autor`** +### `Autor` **Optional**: Der Name des Autors der Aktion. -### **`Beschreibung`** +### `Beschreibung` **Erforderlich** Eine kurze Beschreibung der Aktion. -### **`inputs`** +### `inputs` **Optional**: Mit Eingabeparametern können Sie die Daten angeben, welche die Aktion während der Laufzeit erwartet. {% data variables.product.prodname_dotcom %} speichert Eingabeparameter als Umgebungsvariablen. Eingabe-IDs in Großbuchstaben werden während der Laufzeit in Kleinbuchstaben umgewandelt. Sie sollten Eingabe-IDs in Kleinbuchstaben verwenden. @@ -57,23 +57,23 @@ Wenn Sie eine Eingabe für eine Aktion in einer Workflow-Datei angeben oder eine 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. -#### **`inputs.`** +#### `inputs.` **Erforderlich** Ein Kennzeichner, der die Eingabe identifiziert, als `string`. Der Wert von `` ist eine Übersicht zu den Metadaten der Eingabe. Die `` muss im Objekt `inputs` als ein eindeutiger Kennzeichner vorhanden sein. Die `` muss mit einem Buchstaben oder `_` beginnen und darf nur alphanumerische Zeichen, `-` oder `_` enthalten. -#### **`inputs..description`** +#### `inputs..description` **Erforderlich** Eine Beschreibung des Eingabeparameters als `String`. -#### **`inputs..required`** +#### `inputs..required` **Erforderlich**: Ein `boolescher` Wert, um anzugeben, ob für die Aktion der Eingabeparameter erforderlich ist. Legen Sie den Wert `true` fest, wenn der Parameter erforderlich ist. -#### **`inputs..default`** +#### `inputs..default` **Optional**: Ein `String`, der den Standardwert darstellt. Der Standardwert wird verwendet, wenn ein Eingabeparameter in einer Workflow-Datei nicht angegeben ist. -### **`outputs`** +### `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. @@ -87,15 +87,15 @@ outputs: description: 'Die Summe der Eingaben' ``` -#### **`outputs.`** +#### `outputs.` **Erforderlich** Ein Kennzeichner, der die Ausgabe identifiziert, als `String`. Der Wert von `` ist eine Übersicht zu den Metadaten der Ausgabe. Die `` muss im Objekt `outputs` als ein eindeutiger Kennzeichner vorhanden sein. Die `` muss mit einem Buchstaben oder `_` beginnen und darf nur alphanumerische Zeichen, `-` oder `_` enthalten. -#### **`outputs..description`** +#### `outputs..description` **Erforderlich** Eine Beschreibung des Ausgabeparameters als `String`. -### **`-Ausgaben`** für Aktionen mit zusammengesetzten Ausführungsschritten +### `outputs` for composite run steps actions **Optional** `outputs` use the same parameters as `outputs.` and `outputs..description` (see "[`outputs` for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), but also includes the `value` token. @@ -116,12 +116,12 @@ läuft: ``` {% endraw %} -#### **`outputs.`** +#### `outputs..value` **Erforderliche** Der Wert, dem der Ausgabeparameter zugeordnet wird. Sie können dies auf eine `Zeichenfolge` oder einen Ausdruck mit Kontext festlegen. Sie können z. B. die `Schritte` Kontext verwenden, um den `Wert` einer Ausgabe auf den Ausgabewert eines Schritts festzulegen. For more information on how to use context and expression syntax, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -### **`runs`** für JavaScript-Aktionen +### `runs` for JavaScript actions **Erforderlich** Konfiguriert den Pfad zum Code der Aktion und zu der Anwendung, die den Code ausführen soll. @@ -133,15 +133,15 @@ runs: main: 'main.js' ``` -#### **`runs.using`** +#### `runs.using` **Erforderlich** Die Anwendung, welche den in [`main`](#runsmain) angegebenen Code ausführen soll. -#### **`runs.main`** +#### `runs.main` **Erforderlich** Die Datei, die den Code Deiner Aktion enthält. Die in [`using`](#runsusing) angegebene Anwendung führt diese Datei aus. -#### **`pre`** +#### `pre` **Optional** Erlaubt es Dir, ein Skript am Anfang eines Jobs auszuführen, bevor die `main:`-Aktion startet. Du kannst `pre:` zum Beispiel verwenden, um mit einem Setup-Skript die Voraussetzungen zu schaffen. Die mit der Syntax [`using`](#runsusing) angegebene Anwendung wird diese Datei ausführen. Die `pre:`-Aktion wird normalerweise immer ausgeführt, aber Du kannst dies mit [`pre-if`](#pre-if) ändern. @@ -155,7 +155,7 @@ runs: post: 'cleanup.js' ``` -#### **`pre-if`** +#### `pre-if` **Optional** Erlaubt Dir, Bedingungen für die Ausführung der `pre:`-Aktion festzulegen. Die `pre:`-Aktion läuft nur, wenn die Bedingungen in `pre-if` erfüllt sind. Wenn `pre-if` nicht definiert ist, gilt `always()` als Standardwert. Beachte, dass der `step`-Kontext nicht verfügbar ist, da noch keine Schritte ausgeführt wurden. @@ -166,7 +166,7 @@ In diesem Beispiel läuft `cleanup.js` nur auf Linux-basierten Runnern: pre-if: 'runner.os == linux' ``` -#### **`Beitrag`** +#### `Beitrag` **Optional** Erlaubt es Dir, ein Skript am Ende eines Jobs auszuführen, sobald die `main:`-Aktion abgeschlossen ist. Zum Beispiel kannst Du `post:` verwenden, um bestimmte Prozesse zu beenden oder unnötige Dateien zu entfernen. Die mit der Syntax [`using`](#runsusing) angegebene Anwendung wird diese Datei ausführen. @@ -181,7 +181,7 @@ runs: Die `post:`-Aktion wird normalerweise immer ausgeführt, aber Du kannst dies mit `post-if` ändern. -#### **`post-if`** +#### `post-if` **Optional** Erlaubt Dir, Bedingungen für die Ausführung der `post:`-Aktion festzulegen. Die `post:`-Aktion läuft nur, wenn die Bedingungen in `post-if` erfüllt sind. Wenn `post-if` nicht definiert ist, gilt `always()` als Standardwert. @@ -192,19 +192,19 @@ In diesem Beispiel läuft `cleanup.js` nur auf Linux-basierten Runnern: post-if: 'runner.os == linux' ``` -### **`führt`** für Aktionen für zusammengesetzte Ausführungsschritte aus +### `runs` for composite run steps actions **Erforderliche** Konfiguriert den Pfad zur zusammengesetzten Aktion und die Anwendung, die zum Ausführen des Codes verwendet wird. -#### **`runs.using`** +#### `runs.using` **Erforderliche** Um eine Aktion für zusammengesetzte Ausführungsschritte zu verwenden, legen Sie diese auf `"zusammengesetzte"`fest. -#### **`runs.steps`** +#### `runs.steps` **Erforderliche** Die Ausführungsschritte, die Sie in dieser Aktion ausführen möchten. -##### **`runs.steps.run`** +##### `runs.steps.run` **Erforderliche** Der Befehl, den Sie ausführen möchten. Dies kann inline oder ein Skript in Ihrem Aktions-Repository sein: ```yaml @@ -227,27 +227,27 @@ läuft: Weitere Informationen finden Sie unter "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". -##### **`runs.steps.shell`** +##### `runs.steps.shell` **Erforderliche** Die Shell, in der Sie den Befehl ausführen möchten. Sie können eine der hier aufgeführten Shells [](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)verwenden. -##### **`runs.steps.name`** +##### `runs.steps.name` **Optionaler** Der Name des zusammengesetzten Ausführungsschritts. -##### **`runs.steps.id`** +##### `runs.steps.id` **Optionaler** Ein eindeutiger Bezeichner für den Schritt. Anhand der `id` können Sie in Kontexten auf den Schritt verweisen. Weitere Informationen findest Du unter "[Kontext- und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -##### **`runs.steps.env`** +##### `runs.steps.env` **Optionale** Legt eine `Zuordnung` von Umgebungsvariablen nur für diesen Schritt fest. If you want to modify the environment variable stored in the workflow, use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} in a composite run step. -##### **`runs.steps.working-directory`** +##### `runs.steps.working-directory` **Optionale** Gibt das Arbeitsverzeichnis an, in dem der Befehl ausgeführt wird. -### **`runs`** für Docker-Aktionen +### `runs` for Docker actions **Erforderlich** Konfiguriert das Image, welches für die Docker-Aktion verwendet wird. @@ -267,11 +267,11 @@ läuft: Image: 'docker://debian:stretch-slim' ``` -#### **`runs.using`** +#### `runs.using` **Erforderlich** Du musst diesen Wert auf `'docker'` setzen. -#### **`pre-entrypoint`** +#### `pre-entrypoint` **Optional** Erlaubt Dir, ein Skript auszuführen, bevor die Aktion `entrypoint` beginnt. Du kannst `pre-entrypoint:` zum Beispiel verwenden, um mit einem Setup-Skript die Voraussetzungen zu schaffen. {% data variables.product.prodname_actions %} verwendet `docker run`, um diese Aktion zu starten, und führt das Skript in einem neuen Container aus, der das gleiche Basis-Image verwendet. Das bedeutet, dass sich der Laufzeitstatus vom Container des Haupt-`entrypoint` unterscheidet, und alle benötigten Zustände müssen entweder im Arbeitsbereich, `HOME`, oder als `STATE_`-Variable verwendet werden. Die `pre-entrypoint:`-Aktion wird normalerweise immer ausgeführt, aber Du kannst dies mit [`pre-if`](#pre-if) ändern. @@ -289,21 +289,21 @@ runs: entrypoint: 'main.sh' ``` -#### **`runs.image`** +#### `runs.image` **Erforderlich** Das Docker-Image, das als Container zum Ausführen der Aktion verwendet werden soll. Der Wert kann der Name des Docker-Basis-Images sein, eine lokale `Dockerdatei` in Deinem Repository, oder ein öffentliches Image im Docker-Hub oder in einer anderen Registry. Um eine lokale `Dockerdatei` innerhalb Deines Repositorys zu referenzieren, gibst Du einen Pfad relativ zur Metadaten-Datei Deiner Aktion an. Die `Docker`-Anwendung wird diese Datei ausführen. -#### **`runs.env`** +#### `runs.env` **Optional** Gibt eine Schlüssel-Wert-Zuordnung von Umgebungsvariablen an, die in der Containerumgebung festgelegt werden sollen. -#### **`runs.entrypoint`** +#### `runs.entrypoint` **Optional** Überschreibt den `ENTRYPOINT` des Dockers in der `Dockerdatei`oder setzt ihn, falls nicht bereits angegeben. Verwende `Entrypoint`, wenn die `Dockerdatei` gibt keinen `Entrypoint` angibt, oder wenn Du die Anweisung `Entrypoint` überschreiben willst. Wenn Du `Entrypoint` weglässt, werden jene Befehle ausgeführt, welche Du in der Anweisung `Entrypoint` des Dockers angibst. Für die Docker-Anweisung `ENTRYPOINT` gibt es sowohl eine _shell_-Form als auch eine _exec_-Form. Die Docker-Dokumentation für `ENTRYPOINT` empfiehlt die _exec_-Form der `ENTRYPOINT`-Anweisung. Weitere Informationen dazu, wie die `Entrypoint` ausgeführt wird, findest Du unter "[Dockerdatei-Unterstützung für {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)." -#### **`post-entrypoint`** +#### `post-entrypoint` **Optional** Erlaubt Dir, ein Aufräumskript auszuführen, sobald die Aktion `runs.entrypoint` abgeschlossen ist. {% data variables.product.prodname_actions %} verwendet `docker run` um diese Aktion zu starten. Da {% data variables.product.prodname_actions %} das Skript in einem neuen Container mit dem glaichen Basis-Image ausführt, unterscheidet sich der Laufzeitstatus vom Container des Haupt-`entrypoint`. Du kannst auf jeden benötigten Zustand, entweder im Arbeitsbereich, `HOME`, oder als `STATE_`-Variable zugreifen. Die `post-entrypoint:`-Aktion wird normalerweise immer ausgeführt, aber Du kannst dies mit [`post-if`](#post-if) ändern. @@ -317,7 +317,7 @@ runs: post-entrypoint: 'cleanup.sh' ``` -#### **`runs.args`** +#### `runs.args` **Optional** Ein Array von Strings, welche die Eingaben für einen Docker-Container definieren. Eingaben können hartcodierte Strings enthalten. Beim Start des Containers übergibt {% data variables.product.prodname_dotcom %} die `args`-Anweisung an den `ENTRYPOINT` des Containers. @@ -343,7 +343,7 @@ runs: ``` {% endraw %} -### **`branding`** +### `branding` Du kannst mit einer Farbe und [Feder](https://feathericons.com/) ein Badge zu erstellen, um Deine Aktion zu personalisieren und von anderen zu unterscheiden. Badges werden neben Deinem Aktionsnamen in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) angezeigt. @@ -355,11 +355,11 @@ branding: color: 'green' ``` -#### **`branding.color`** +#### `branding.color` Die Hintergrundfarbe des Badges. Kann eine der folgenden sein: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple` oder `gray-dark`. -#### **`branding.icon`** +#### `branding.icon` Der Name des zu verwendenden [Federsymbols](https://feathericons.com/). 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 fb128bd6d5..31dcbc4d98 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 @@ -25,7 +25,11 @@ Das Erstellen eines Pakets am Ende eines Workflows zur kontinuierlichen Integrat Wenn Du nun einen Pull-Request überprüfst, kannst Du Dir den Ablauf des Workflows ansehen und das erzeugte Artefakt herunterladen. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down-updated.png) +{% else %} ![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down.png) +{% endif %} Dadurch kannst Du den Code im Pull-Request auf Deinem Rechner ausführen, was beim Debuggen oder Testen des Pull-Requests helfen kann. 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 2314effa60..d22fdc1c4b 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 @@ -53,7 +53,7 @@ jobs: with: java-version: 1.8 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -85,7 +85,7 @@ steps: with: java-version: 1.8 - name: Run the Maven verify phase - run: mvn -B verify --file pom-ci.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -108,7 +108,7 @@ steps: key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} restore-keys: ${{ runner.os }}-m2 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -125,7 +125,7 @@ Maven erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeich steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 - - run: mvn -B package --file pom.xml + - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 with: diff --git a/translations/de-DE/content/actions/guides/building-and-testing-powershell.md b/translations/de-DE/content/actions/guides/building-and-testing-powershell.md index 9f0b0eb43d..7adb13f39d 100644 --- a/translations/de-DE/content/actions/guides/building-and-testing-powershell.md +++ b/translations/de-DE/content/actions/guides/building-and-testing-powershell.md @@ -60,7 +60,11 @@ jobs: * `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory. * `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. Ein Beispiel: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png) + {% else %} ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png) + {% endif %} * `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following: ``` 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 0e085f18c0..d676a182f7 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 @@ -84,7 +84,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -143,7 +143,7 @@ jobs: with: java-version: 1.8 - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` @@ -182,7 +182,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish to the Maven Central Repository - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -191,7 +191,7 @@ jobs: with: java-version: 1.8 - name: Publish to GitHub Packages - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` diff --git a/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md b/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md index c8e4b8c16f..944534e21d 100644 --- a/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/de-DE/content/actions/guides/publishing-nodejs-packages.md @@ -8,8 +8,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/de-DE/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index c4f5928c6e..3e47530f79 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,8 +11,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md index e1d0067de3..f3b152a418 100644 --- a/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/de-DE/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -108,8 +108,6 @@ jobs: pfad: output/test/code-coverage.html ``` -![Bild mit Workflow-Ausführung des Workflow-Upload-Artefakts](/assets/images/help/repository/upload-build-test-artifact.png) - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Configuring a custom artifact retention period @@ -238,7 +236,12 @@ Jobs: echo Das Ergebnis ist $value ``` +The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Workflow, der zum Durchführen mathematischer Operationen Daten zwischen Aufträgen weitergibt](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% else %} ![Workflow, der zum Durchführen mathematischer Operationen Daten zwischen Aufträgen weitergibt](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +{% endif %} {% if currentVersion == "free-pro-team@latest" %} 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 e80066c926..cb99f1f536 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 @@ -87,7 +87,7 @@ The following operating systems are supported for the self-hosted runner applica - Windows Server 2016 64-bit - Windows Server 2019 64-bit -#### MacOS +#### macOS - macOS 10.13 (High Sierra) oder höher diff --git a/translations/de-DE/content/actions/index.md b/translations/de-DE/content/actions/index.md index 8249d43973..c7f1b0afd5 100644 --- a/translations/de-DE/content/actions/index.md +++ b/translations/de-DE/content/actions/index.md @@ -41,6 +41,7 @@ changelog: title: Self-Hosted Runner Group Access Changes date: '2020-10-16' href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ +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/ @@ -69,18 +70,18 @@ versions:

Code examples

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

Sorry, there is no result for

+

Sorry, there is no result for

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

Learn how to add a code example {% octicon "arrow-right" %}
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 7747872bbb..9d9e77a00f 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 @@ -204,13 +204,18 @@ In this diagram, you can see the workflow file you just created and how the {% d ### Viewing the job's activity -Once your job has started running, you can view each step's activity on {% data variables.product.prodname_dotcom %}. +Once your job has started running, you can {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}. {% data reusables.repositories.navigate-to-repo %} 1. Klicke unter Deinem Repository-Namen auf **Actions** (Aktionen). ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png) 1. In the left sidebar, click the workflow you want to see. ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png) 1. Under "Workflow runs", click the name of the run you want to see. ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Select job](/assets/images/help/images/overview-actions-result-navigate.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. View the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. Click on the job name to see the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated.png) {% else %} 1. Click on the job name to see the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result.png) 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 0f2e888b06..924edb09b3 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 @@ -54,6 +54,8 @@ This means that a compromise of a single action within a workflow can be very si **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail. {% endwarning %} + + * **Audit the source code of the action** Ensure that the action is handling the content of your repository and secrets as expected. For example, check that secrets are not sent to unintended hosts, or are not inadvertently logged. @@ -92,10 +94,14 @@ This list describes the recommended approaches for accessing repository data wit As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be cautious when using self-hosted runners on private repositories, as anyone who can fork the repository and open a PR (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the more privileged `GITHUB_TOKEN` which grants write-access permissions on the repository. +When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)." + You should also consider the environment of the self-hosted runner machines: - What sensitive information resides on the machine configured as a self-hosted runner? For example, private SSH keys, API access tokens, among others. - Does the machine have network access to sensitive services? For example, Azure or AWS metadata services. The amount of sensitive information in this environment should be kept to a minimum, and you should always be mindful that any user capable of invoking workflows has access to this environment. +Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. + ### Auditing {% data variables.product.prodname_actions %} events 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. @@ -130,5 +136,3 @@ The following tables describe the {% data variables.product.prodname_actions %} | `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. | - - diff --git a/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md index f7c90bf8eb..9ac905ac1d 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -17,8 +17,13 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} -{% data reusables.repositories.view-run %} -1. In the upper-right corner of the workflow, click **Cancel workflow**. ![Schaltfläche zum Abbrechen der Prüfsuite](/assets/images/help/repository/cancel-check-suite.png) +1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel. ![Name der Workflow-Ausführung](/assets/images/help/repository/in-progress-run.png) +1. In the upper-right corner of the workflow, click **Cancel workflow**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Schaltfläche zum Abbrechen der Prüfsuite](/assets/images/help/repository/cancel-check-suite-updated.png) +{% else %} + ![Schaltfläche zum Abbrechen der Prüfsuite](/assets/images/help/repository/cancel-check-suite.png) +{% endif %} ### Steps {% data variables.product.prodname_dotcom %} takes to cancel a workflow run diff --git a/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 0ca6879bf7..7ca9828bf0 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -19,4 +19,9 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under **Artifacts**, click the artifact you want to download. ![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down.png) +1. Under **Artifacts**, click the artifact you want to download. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down-updated.png) + {% else %} + ![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down.png) + {% endif %} diff --git a/translations/de-DE/content/actions/managing-workflow-runs/index.md b/translations/de-DE/content/actions/managing-workflow-runs/index.md index 67e6b68e26..e8456dae1d 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/index.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/index.md @@ -18,6 +18,7 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% link_in_list /using-the-visualization-graph %}{% endif %} {% link_in_list /viewing-workflow-run-history %} {% link_in_list /using-workflow-run-logs %} {% link_in_list /manually-running-a-workflow %} diff --git a/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md index 09907159f4..323ebab2d3 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -16,4 +16,4 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**. ![Dropdownmenü zum erneuten Durchführen der Prüfungen](/assets/images/help/repository/rerun-checks-drop-down.png) +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} diff --git a/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 59250dcfca..efcafa3b60 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -26,7 +26,13 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under **Artifacts**, click {% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove. ![Dropdown-Menü zum Löschen von Artefakten](/assets/images/help/repository/actions-delete-artifact.png) +1. Under **Artifacts**, click +{% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Dropdown-Menü zum Löschen von Artefakten](/assets/images/help/repository/actions-delete-artifact-updated.png) + {% else %} + ![Dropdown-Menü zum Löschen von Artefakten](/assets/images/help/repository/actions-delete-artifact.png) + {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Setting the retention period for an artifact diff --git a/translations/de-DE/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/de-DE/content/actions/managing-workflow-runs/using-the-visualization-graph.md new file mode 100644 index 0000000000..f1ef803e42 --- /dev/null +++ b/translations/de-DE/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -0,0 +1,21 @@ +--- +title: Using the visualization graph +intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.visualization-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} + +1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies. ![Workflow graph](/assets/images/help/images/workflow-graph.png) + +2. Click on a job to view the job log. ![Workflow graph](/assets/images/help/images/workflow-graph-job.png) diff --git a/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 3395a68711..fa16a5e4d1 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -44,7 +44,12 @@ Sie können die Build-Protokolle für einen bestimmten Schritt durchsuchen. Beim {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Gib in der oberen rechten Ecke der Protokollausgabe im Suchfeld **Search logs** (Protokolle durchsuchen) eine Suchanfrage ein. ![Suchfeld zum Durchsuchen von Protokollen](/assets/images/help/repository/search-log-box-updated.png) +1. Gib in der oberen rechten Ecke der Protokollausgabe im Suchfeld **Search logs** (Protokolle durchsuchen) eine Suchanfrage ein. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Suchfeld zum Durchsuchen von Protokollen](/assets/images/help/repository/search-log-box-updated-2.png) +{% else %} + ![Suchfeld zum Durchsuchen von Protokollen](/assets/images/help/repository/search-log-box-updated.png) +{% endif %} {% else %} 1. Um jeden Schritt, den Sie in Ihre Suche einbeziehen möchten, einzublenden, klicken Sie auf den Schritt. ![Name des Schrittes](/assets/images/help/repository/failed-check-step.png) 1. Gib in der oberen rechten Ecke der Protokollausgabe im Suchfeld **Search logs** (Protokolle durchsuchen) eine Suchanfrage ein. ![Suchfeld zum Durchsuchen von Protokollen](/assets/images/help/repository/search-log-box.png) @@ -61,8 +66,12 @@ Sie können die Protokolldateien von Ihrem Workflowlauf herunterladen. Sie könn {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 1. In the upper right corner, click -{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Download log archive**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Dropdownmenü zum Herunterladen von Protokollen](/assets/images/help/repository/download-logs-drop-down-updated-2.png) + {% else %} ![Dropdownmenü zum Herunterladen von Protokollen](/assets/images/help/repository/download-logs-drop-down-updated.png) + {% endif %} {% else %} 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Download log archive**. @@ -78,8 +87,20 @@ Du kannst die Logdateien aus Deiner Workflow-Ausführung löschen. {% data reusa {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) -2. Um die Logdateien zu löschen, klicke auf **Delete all logs** (Alle Logs löschen) und überprüfe die Bestätigungsanfrage. ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) Nach die Protokolle gelöscht sind, verschwindet die Schaltfläche **Delete all logs**, um anzuzeigen, dass keine Protokolldateien mehr im Workflowlauf verbleiben. +1. In the upper right corner, click +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) + {% else %} + ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) + {% endif %} +2. Um die Logdateien zu löschen, klicke auf **Delete all logs** (Alle Logs löschen) und überprüfe die Bestätigungsanfrage. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png) + {% else %} + ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) + {% endif %} +After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. {% else %} 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png) 2. Um die Logdateien zu löschen, klicke auf **Delete all logs** (Alle Logs löschen) und überprüfe die Bestätigungsanfrage. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) After the logs have been deleted, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. diff --git a/translations/de-DE/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/de-DE/content/actions/managing-workflow-runs/viewing-job-execution-time.md index e6df60d0ec..9f594eb251 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/viewing-job-execution-time.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -15,7 +15,7 @@ Billable job execution minutes are only shown for jobs run on private repositori {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under the job summary, you can view the job's execution time. To view the billable job execution time, click **Run and billable time details**. ![Link zu Den Ausführungs- und Abrechnungsdetails](/assets/images/help/repository/view-run-billable-time.png) +1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, click the time under **Billable time**. ![Link zu Den Ausführungs- und Abrechnungsdetails](/assets/images/help/repository/view-run-billable-time.png) {% note %} diff --git a/translations/de-DE/content/actions/quickstart.md b/translations/de-DE/content/actions/quickstart.md index 0f2ce1770c..5d97596d00 100644 --- a/translations/de-DE/content/actions/quickstart.md +++ b/translations/de-DE/content/actions/quickstart.md @@ -59,7 +59,11 @@ Committing the workflow file in your repository triggers the `push` event and ru {% 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 %} ### More starter workflows @@ -101,7 +105,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o # When the event is triggered, GitHub Actions will run the jobs indicated jobs: say_hello: - # Uses a ubuntu-lates runner to complete the requested steps + # Uses a ubuntu-latest runner to complete the requested steps runs-on: ubuntu-latest steps: - run: | diff --git a/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 0691692498..e53cad90c5 100644 --- a/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,7 +75,7 @@ Bei der Eigenschaftsdereferenzierungs-Syntax muss der Eigenschaftsname - mit `a-Z` oder `_` beginnen, - mit `a-Z`, `0-9`, `-` oder `_` weitergehen. -#### **`github`-Kontext** +#### `github`-Kontext Der `github`-Kontext enthält Informationen zum Workflow-Lauf und zu dem Ereignis, das den Lauf ausgelöst hat. Sie können die meisten `github`-Kontextdaten in Umgebungsvariablen lesen. Weitere Informationen über Umgebungsvariablen findest Du unter „[Umgebungsvariablen verwenden](/actions/automating-your-workflow-with-github-actions/using-environment-variables)“. @@ -103,7 +103,7 @@ Der `github`-Kontext enthält Informationen zum Workflow-Lauf und zu dem Ereigni | `github.workflow` | `string` | Der Name des Workflows. Wenn in der Workflow-Datei kein `name` (Name) festgelegt ist, entspricht der Wert dieser Eigenschaft dem vollständigen Pfad der Workflow-Datei im Repository. | | `github.workspace` | `string` | Das Standardarbeitsverzeichnis für Schritte und der Standardspeicherort Deines Repositorys bei Verwendung der Aktion [ `checkout`](https://github.com/actions/checkout). | -#### **`env`-Kontext** +#### `env`-Kontext Der `env`-Kontext enthält Umgebungsvariablen, die in einem Workflow, Job oder Schritt gesetzt wurden. Weitere Informationen über das Setzen von Umgebungsvariablen in Deinem Workflow findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)“. @@ -117,7 +117,7 @@ Du kannst den `env`-Kontext nur im Wert der Schlüssel `with` und `name` verwend | `env.` | `string` | Der Wert einer bestimmten Umgebungsvariable. | -#### **`job`-Kontext** +#### `job`-Kontext Der `job`-Kontext enthält Informationen zum gerade ausgeführten Auftrag. @@ -133,7 +133,7 @@ Der `job`-Kontext enthält Informationen zum gerade ausgeführten Auftrag. | `job.services..ports` | `Objekt` | Die offengelegten Ports des Service-Containers | | `job.status` | `string` | Der aktuelle Status des Auftrags. Mögliche Werte sind `success` (erfolgreich), `failure` (fehlgeschlagen) oder `cancelled` (abgebrochen). | -#### **`steps`-Kontext** +#### `steps`-Kontext Der `steps`-Kontext enthält Informationen zu den Schritten im aktuellen Auftrag, die bereits ausgeführt wurden. @@ -145,7 +145,7 @@ Der `steps`-Kontext enthält Informationen zu den Schritten im aktuellen Auftrag | `steps..outcome` | `string` | Das Ergebnis eines abgeschlossenen Schritts bevor [`continue-on-error` (bei Fehler weitermachen)](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) angewendet wird. Mögliche Werte sind `success` (erfolgreich), `failure` (fehlgeschlagen), `cancelled` (abgebrochen) oder `skipped` (übersprungen). Wenn ein Schritt mit `continue-on-error` (bei Fehler weitermachen) fehlschlägt, ist `outcome` (Ergebnis) `failure` zwar (Fehler), aber `conclusion` (Schlussfolgerung) ist am Ende `success` (Erfolg). | | `steps..outputs.` | `string` | Der Wert einer bestimmten Ausgabe | -#### **`runner`-Kontext** +#### `runner`-Kontext Der `runner`-Kontext enthält Informationen über den Runner, der den aktuellen Job ausführt. @@ -155,7 +155,7 @@ Der `runner`-Kontext enthält Informationen über den Runner, der den aktuellen | `runner.temp` | `string` | Der Pfad des temporären Verzeichnisses für den Runner. Dieses Verzeichnis ist zu Beginn jedes Auftrags garantiert leer, sogar bei selbst-gehosteten Runnern. | | `runner.tool_cache` | `string` | Der Pfad des Verzeichnisses, das einige der vorinstallierten Tools für {% data variables.product.prodname_dotcom %}-gehostete Runner enthält. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". | -#### **`needs`-Kontext** +#### `needs`-Kontext Der `needs`-Kontext enthält Ausgaben von allen Jobs, die als Abhängigkeit des aktuellen Jobs definiert sind. Weitere Informationen zur Definition von Jobabhängigkeiten findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)“. diff --git a/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md b/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md index 043d41a583..10d113b915 100644 --- a/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/de-DE/content/actions/reference/events-that-trigger-workflows.md @@ -137,9 +137,9 @@ jobs: #### `repository_dispatch` -| Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------- | --------------- | ------------------------------------- | -------------------------------------- | -| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | – | Letzter Commit im Branch `GITHUB_REF` | Branch, der den Dispatch empfangen hat | +| Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------------------- | --------------- | --------------------------------- | --------------- | +| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | – | Letzter Commit im Standard-Branch | Standard-Branch | {% data reusables.github-actions.branch-requirement %} @@ -699,6 +699,8 @@ on: {% data reusables.webhooks.workflow_run_desc %} +{% data reusables.github-actions.branch-requirement %} + | Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------- | --------------- | --------------------------------- | --------------- | | [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - n/a | Letzter Commit im Standard-Branch | Standard-Branch | diff --git a/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md index 894b1f477a..124ad94aa5 100644 --- a/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/de-DE/content/actions/reference/specifications-for-github-hosted-runners.md @@ -63,8 +63,8 @@ The software tools included in {% data variables.product.prodname_dotcom %}-host * [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md) * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md) -* [MacOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) -* [MacOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) +* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) {% data reusables.github-actions.ubuntu-runner-preview %} {% data reusables.github-actions.macos-runner-preview %} diff --git a/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md index 4a9cb976a0..f59527d0ee 100644 --- a/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/reference/workflow-syntax-for-github-actions.md @@ -21,17 +21,17 @@ Workflow-Dateien verwenden die YAML-Syntax und müssen die Dateierweiterung `.ym Workflow-Dateien müssen im Verzeichnis `.github/workflows` im Repository gespeichert werden. -### **`name`** +### `name` Name des Workflows. {% data variables.product.prodname_dotcom %} zeigt die Namen der Workflows auf der Repository-Seite der Aktionen an. Wenn Du `name`weglässt, setzt {% data variables.product.prodname_dotcom %} den Pfad der Workflow-Datei relativ zum Stammverzeichnis des Repositorys. -### **`on`** +### `on` **Erforderlich** Name des Ereignisses auf {% data variables.product.prodname_dotcom %}, das den Workflow auslöst. Sie können einen `string` für ein einzelnes Ereignis, ein `array` mit Ereignissen, ein `array` mit Ereignis-`types` oder eine Ereigniskonfigurations-`map` festlegen, mit der ein Workflow geplant oder die Ausführung eines Workflows auf bestimmte Dateien, Tags oder Branch-Änderungen beschränkt wird. Eine Liste der verfügbaren Ereignisse finden Sie unter „[Ereignisse, die Workflows auslösen](/articles/events-that-trigger-workflows)“. {% data reusables.github-actions.actions-on-examples %} -### **`on..types`** +### `on..types` Legt die Aktivitätstypen fest, die die Ausführung eines Workflows auslösen. Die meisten GitHub-Ereignisse werden von mehreren Aktivitätstypen ausgelöst. Beispielsweise wird das Ereignis für die Veröffentlichungsressource ausgelöst, wenn eine Veröffentlichung veröffentlicht (`published`), erstellt (`created`), bearbeitet (`edited`), gelöscht (`deleted`), vorab veröffentlicht (`prereleased`) oder ihre Veröffentlichung zurückgezogen (`unpublished`) wird. Mit dem Stichwort `types` grenzt Du die Aktivitäten ein, die die Ausführung des Workflows auslösen. Wird ein Webhook-Ereignis nur von einem einzigen Aktivitätstyp ausgelöst, ist das Stichwort `types` nicht erforderlich. @@ -45,7 +45,7 @@ on: types: [published, created, edited] ``` -### **`on..`** +### `on..` Wenn Sie die Ereignisse `push` und `pull_request` verwenden, können Sie einen Workflow so konfigurieren, dass er auf bestimmten Branches oder Tags ausgeführt wird. Für ein `pull_request`-Ereignis werden nur Branches und Tags auf der Basis ausgewertet. Wenn Du nur `tags` oder nur `branches` definierst, wird der Workflow bei Ereignissen, die sich auf die nicht definierte Git-Ref auswirken, nicht ausgeführt. @@ -112,7 +112,7 @@ on: - '!releases/**-alpha' ``` -### **`on..paths`** +### `on..paths` Bei den Ereignissen `push` und `pull_request` kannst Du einen Workflows zur Ausführung konfigurieren, wenn mindestens eine Datei nicht zu den `paths-ignore` passt oder mindestens eine geänderte Datei zu den konfigurierten `paths` passt. Bei Push-Vorgängen zu Tags werden Pfadfilter nicht ausgewertet. @@ -179,13 +179,13 @@ Zur Ermittlung, ob ein Workflow ausgeführt werden soll, wertet der Filter die g Weitere Informationen findest Du unter „[Informationen zum Vergleich von Branches in Pull-Requests](/articles/about-comparing-branches-in-pull-requests)“. -### **`on.schedule`** +### `on.schedule` {% data reusables.repositories.actions-scheduled-workflow-example %} Weitere Informationen zur Cron-Syntax findest Du unter „[Ereignisse, die Workflows auslösen](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)“. -### **`env`** +### `env` Eine `map` mit Umgebungsvariablen, die für alle Jobs und Schritte im Workflow verfügbar sind. Darüber hinaus kannst Du auch Umgebungsvariablen festlegen, die ausschließlich für einen Job oder Schritt bereitstehen. Weitere Informationen findest Du unter [`jobs..env`](#jobsjob_idenv) und [`jobs..steps.env`](#jobsjob_idstepsenv). @@ -198,13 +198,13 @@ env: SERVER: production ``` -### **`defaults`** +### `defaults` Eine `map` der Standardeinstellungen, die für alle Jobs im Workflow gelten. Du kannst auch Standardeinstellungen festlegen, die nur für einen Job verfügbar sind. Weitere Informationen findest Du unter [`jobs..defaults`](#jobsjob_iddefaults). {% data reusables.github-actions.defaults-override %} -### **`defaults.run`** +### `defaults.run` Du kannst Standardeinstellungen der Optionen `shell` und `working-directory` (Arbeitsverzeichnis) für alle [`run`](#jobsjob_idstepsrun)-Schritte in einem Workflow angeben. Du kannst auch Standardeinstellungen für `run` festlegen, die nur für einen Job verfügbar sind. Weitere Informationen findest Du unter [`jobs..defaults.run`](#jobsjob_iddefaultsrun). In diesem Schlüsselwort kannst Du keine Kontexte oder Ausdrücke verwenden. @@ -219,7 +219,7 @@ defaults: working-directory: scripts ``` -### **`jobs`** +### `jobs` Ein Workflow-Lauf besteht aus mindestens einem Auftrag. Die Aufträge werden standardmäßig parallel ausgeführt. Sollen Aufträge sequenziell ausgeführt werden, können Sie mit dem Stichwort `jobs..needs` eine Abhängigkeit von anderen Aufträgen definieren. @@ -229,7 +229,7 @@ Innerhalb der Nutzungsbeschränkungen des Workflows kannst Du unbegrenzt viele J Wenn Du den eindeutigen Bezeichner eines Jobs finden musst, der in einem Workflowlauf ausgeführt wird, kannst Du die API von {% data variables.product.prodname_dotcom %} verwenden. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." -### **`jobs.`** +### `jobs.` Jedem Auftrag muss eine ID zugewiesen sein. Das Stichwort `job_id` ist ein String, und der Wert umfasst eine Zuordnung der Konfigurationsdaten für den Auftrag. Sie müssen `` durch einen eindeutigen String für das `jobs`-Objekt ersetzen. Die `` muss mit einem Buchstaben oder einem Unterstrich (`_`) beginnen und darf nur alphanumerische Zeichen, Bindestriche (`-`) und Unterstriche (`_`) enthalten. @@ -243,15 +243,15 @@ jobs: name: My second job ``` -### **`jobs..name`** +### `jobs..name` Name des Auftrags, der auf {% data variables.product.prodname_dotcom %} angezeigt wird. -### **`jobs..needs`** +### `jobs..needs` -Liste mit allen Aufträgen, die erfolgreich abgeschlossen sein müssen, bevor dieser Auftrag ausgeführt wird. Hier ist ein String oder ein Array mit Strings zulässig. Wenn ein Auftrag fehlschlägt, werden alle Aufträge übersprungen, die diesen Auftrag benötigen, außer die Aufträge umfassen eine bedingte Anweisung, mit der der Auftrag dennoch fortgesetzt wird. +Liste mit allen Aufträgen, die erfolgreich abgeschlossen sein müssen, bevor dieser Auftrag ausgeführt wird. Hier ist ein String oder ein Array mit Strings zulässig. If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. -#### Beispiel +#### Example requiring dependent jobs to be successful ```yaml jobs: @@ -270,7 +270,21 @@ Die Aufträge in diesem Beispiel werden sequenziell ausgeführt: 2. `job2` 3. `job3` -### **`jobs..runs-on`** +#### Example not requiring dependent jobs to be successful + +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + if: always() + 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)." + +### `jobs..runs-on` **Erforderlich** Typ der Maschine, auf der der Job ausgeführt wird. Die Maschine kann entweder ein {% data variables.product.prodname_dotcom %}-gehosteter oder ein selbst-gehosteter Runner sein. @@ -286,7 +300,7 @@ Verfügbare Arten von {% data variables.product.prodname_dotcom %}-gehostete Run {% data reusables.github-actions.ubuntu-runner-preview %} -##### **Beispiel** +##### Beispiel ```yaml Runs-on: ubuntu-latest @@ -298,7 +312,7 @@ Weitere Informationen findest Du unter "[Virtuelle Umgebungen für {% data varia {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -##### **Beispiel** +##### Beispiel ```yaml runs-on: [self-hosted, linux] @@ -306,7 +320,7 @@ runs-on: [self-hosted, linux] Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)“ und „[Selbst-gehostete Runner in einem Workflow verwenden](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)“. -### **`jobs..outputs`** +### `jobs..outputs` Eine `map` der Ausgaben eines Jobs. Ausgaben eines Jobs stehen allen nachgelagerten Jobs zur Verfügung, die von diesem Job abhängen. Weitere Informationen zur Definition von Abhängigkeiten zwischen Jobs findest Du unter [`Jobs..needs`](#jobsjob_idneeds). @@ -314,7 +328,7 @@ Ausgaben von Jobs sind Zeichenketten und wenn sie Ausdrücke enthalten, werden d Um Jobausgaben in einem abhängigen Job zu verwenden, kannst Du den Kontext `needs` verwenden. Weitere Informationen findest Du unter "[Kontext- und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)". -#### **Beispiel** +#### Beispiel {% raw %} ```yaml @@ -338,13 +352,13 @@ jobs: ``` {% endraw %} -### **`jobs..env`** +### `jobs..env` Eine `map` mit Umgebungsvariablen, die für alle Schritte im Auftrag verfügbar sind. Darüber hinaus können Sie Umgebungsvariablen für den gesamten Workflow oder für einen einzelnen Schritt festlegen. Weitere Informationen finden Sie unter [`env`](#env) und [`jobs..steps.env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -#### **Beispiel** +#### Beispiel ```yaml jobs: @@ -353,13 +367,13 @@ jobs: FIRST_NAME: Mona ``` -### **`jobs..defaults`** +### `jobs..defaults` Eine `map` mit Standardeinstellungen, die für alle Schritte im Job gelten. Du kannst auch Standardeinstellungen für den gesamten Workflow festlegen. Weitere Informationen findest Du unter [`Standardwerte`](#defaults). {% data reusables.github-actions.defaults-override %} -### **`jobs..defaults.run`** +### `jobs..defaults.run` Standards für `shell` und `working-directory` (Arbeitsverzeichnis) bereitstellen, die für alle `run`-Schritte des Jobs gelten. Kontext und Ausdruck sind in diesem Abschnitt nicht zulässig. @@ -379,17 +393,17 @@ jobs: working-directory: scripts ``` -### **`jobs..if`** +### `jobs..if` -Mit der `if`-Bedingung geben Sie an, dass ein Auftrag nur dann ausgeführt werden soll, wenn eine bestimmte Bedingung erfüllt ist. Sie können eine Bedingung mit jedem unterstützten Kontext und Ausdruck erstellen. +Mit der `if`-Bedingung geben Sie an, dass ein Auftrag nur dann ausgeführt werden soll, wenn eine bestimmte Bedingung erfüllt ist. Du kannst eine Bedingung mit jedem unterstützten Kontext und Ausdruck erstellen. {% data reusables.github-actions.expression-syntax-if %} Weitere Informationen findest Du unter „[Kontext- und Ausdruckssyntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)“. -### **`jobs..steps`** +### `jobs..steps` -Ein Auftrag enthält eine Sequenz von Aufgaben, sogenannten `steps`. Mit Schritten können Befehle oder Einrichtungsaufgaben ausgeführt werden, und außerdem Aktionen, die sich in Ihrem Repository oder in einem öffentlichen Repository befinden oder in einer Docker Registry veröffentlicht sind. Nicht alle Schritte führen eine Aktion aus, doch alle Aktionen werden als Schritt ausgeführt. Jeder Schritt wird in einem eigenen Prozess in der Runner-Umgebung ausgeführt. Er hat Zugriff auf den Arbeitsbereich und das Dateisystem. Da die Schritte jeweils in einem eigenen Prozess ausgeführt werden, werden Änderungen an den Umgebungsvariablen nicht von Schritt zu Schritt beibehalten. {% data variables.product.prodname_dotcom %} umfasst integrierte Schritte zum Einrichten und Ausführen eines Auftrags. +Ein Auftrag enthält eine Sequenz von Aufgaben, sogenannten `steps`. Mit Schritten können Befehle oder Einrichtungsaufgaben ausgeführt werden, und außerdem Aktionen, die sich in Ihrem Repository oder in einem öffentlichen Repository befinden oder in einer Docker Registry veröffentlicht sind. Nicht alle Schritte führen eine Aktion aus, doch alle Aktionen werden als Schritt ausgeführt. Jeder Schritt wird in einem eigenen Prozess in der Runner-Umgebung ausgeführt. Er hat Zugriff auf den Arbeitsbereich und das Dateisystem. Da die Schritte jeweils in einem eigenen Prozess ausgeführt werden, werden Änderungen an den Umgebungsvariablen nicht von Schritt zu Schritt beibehalten. {% data variables.product.prodname_dotcom %} umfasst integrierte Schritte zum Einrichten und Ausführen eines Jobs. -Innerhalb der Nutzungseinschränkungen des Workflows können Sie unbegrenzt viele Schritte ausführen. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. +Innerhalb der Nutzungsbeschränkungen des Workflows kannst Du unbegrenzt viele Schritte ausführen. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits. #### Beispiel @@ -415,17 +429,17 @@ jobs: ``` {% endraw %} -#### **`jobs..steps.id`** +### `jobs..steps.id` Eindeutige Kennung für den Schritt. Anhand der `id` können Sie in Kontexten auf den Schritt verweisen. Weitere Informationen findest Du unter „[Kontext- und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)“. -#### **`jobs..steps.if`** +### `jobs..steps.if` -Mit der `if`-Bedingung geben Sie an, dass ein Schritt nur dann ausgeführt werden soll, wenn eine bestimmte Bedingung erfüllt ist. Sie können eine Bedingung mit jedem unterstützten Kontext und Ausdruck erstellen. +Mit der Bedingung `if` gibst Du an, dass ein Schritt nur dann ausgeführt werden soll, wenn eine bestimmte Bedingung erfüllt ist. Du kannst eine Bedingung mit jedem unterstützten Kontext und Ausdruck erstellen. {% data reusables.github-actions.expression-syntax-if %} Weitere Informationen findest Du unter „[Kontext- und Ausdruckssyntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)“. -##### Beispiel für die Verwendung von Kontexten +#### Beispiel für die Verwendung von Kontexten Dieser Schritt wird nur ausgeführt, wenn der Ereignistyp ein `pull_request` ist und die Ereignisaktion `unassigned` ist. @@ -436,7 +450,7 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -##### Beispiel für die Verwendung von Statusprüf-Funktionen +#### Beispiel für die Verwendung von Statusprüffunktionen `my backup step` wird nur dann ausgeführt, wenn der vorherige Schritt eines Auftrags fehlschlägt. Weitere Informationen findest Du unter „[Kontext- und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)“. @@ -449,11 +463,11 @@ steps: uses: actions/heroku@1.0.0 ``` -#### **`jobs..steps.name`** +### `jobs..steps.name` -Name des Schritts, der auf {% data variables.product.prodname_dotcom %} angezeigt wird. +Name Deines Schritts, der auf {% data variables.product.prodname_dotcom %} angezeigt wird. -#### **`jobs..steps.uses`** +### `jobs..steps.uses` Wählt eine Aktion aus, die als Teil eines Schritts im Auftrag ausgeführt wird. Eine Aktion ist eine wiederverwendbare Code-Einheit. Sie können eine Aktion verwenden, die im selben Repository wie der Workflow, in einem öffentlichen Repository oder in einem [veröffentlichten Docker-Container-Image](https://hub.docker.com/) definiert ist. @@ -462,11 +476,11 @@ Es wird dringend empfohlen, die verwendete Version der Aktion zu nennen (Git-Ref - Wenn Du Dich auf die Hauptversion der Aktion beziehst, kannst Du kritische Fehlerbehebungen und Sicherheits-Patches erhalten und gleichzeitig die Kompatibilität wahren. Außerdem ist damit sichergestellt, dass der Workflow weiterhin problemlos arbeiteten sollte. - 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. -Für einige Aktionen sind Eingaben erforderlich, die Sie mit dem Stichwort [`with`](#jobsjob_idstepswith) festlegen müssen. Die erforderlichen Eingaben finden Sie in der README-Datei der Aktion. +Für einige Aktionen sind Eingaben erforderlich, die Du mit dem Schlüsselwort [`with`](#jobsjob_idstepswith) festlegen musst. Die erforderlichen Eingaben finden Sie in der README-Datei der Aktion. Aktionen sind entweder JavaScript-Dateien oder Docker-Container. Bei Docker-Containern als Aktion mmusst Du den Job in einer Linux-Umgebung ausführen. Weitere Details findest Du unter [`runs-on`](#jobsjob_idruns-on). -##### Beispiel mit versionierten Aktionen +#### Beispiel mit versionierten Aktionen ```yaml steps: @@ -480,11 +494,11 @@ steps: - uses: actions/setup-node@main ``` -##### Beispiel mit einer öffentlichen Aktion +#### Beispiel mit einer öffentlichen Aktion `{owner}/{repo}@{ref}` -Sie können einen bestimmten Branch, eine bestimmte Ref oder eine bestimmte SHA in einem öffentlichen Repository auf {% data variables.product.prodname_dotcom %} heranziehen. +Du kannst einen bestimmten Branch, eine bestimmte Ref oder eine bestimmte SHA in einem öffentlichen Repository auf {% data variables.product.prodname_dotcom %} heranziehen. ```yaml jobs: @@ -498,11 +512,11 @@ jobs: uses: actions/aws@v2.0.1 ``` -##### Beispiel mit einer öffentlichen Aktion in einem Unterverzeichnis +#### Beispiel mit einer öffentlichen Aktion in einem Unterverzeichnis `{owner}/{repo}/{path}@{ref}` -Ein Unterverzeichnis in einem öffentlichen Repository auf {% data variables.product.prodname_dotcom %} in einem bestimmten Branch, einem bestimmten Ref oder einer bestimmten SHA. +Ein Unterverzeichnis in einem öffentlichen Repository auf {% data variables.product.prodname_dotcom %} in einem bestimmten Branch, einer bestimmten Ref oder einer bestimmten SHA. ```yaml jobs: @@ -512,7 +526,7 @@ jobs: uses: actions/aws/ec2@main ``` -##### Beispiel mit einer Aktion im selben Repository wie der Workflow +#### Beispiel mit einer Aktion im selben Repository wie der Workflow `./path/to/dir` @@ -528,7 +542,7 @@ jobs: uses: ./.github/actions/my-action ``` -##### Beispiel mit einer Docker-Hub-Aktion +#### Beispiel mit einer Docker Hub-Aktion `docker://{image}:{tag}` @@ -542,7 +556,7 @@ jobs: verwendet: docker://alpine:3.8 ``` -##### Beispiel mit einer Aktion in einer öffentlichen Docker-Registry +#### Beispiel mit einer Aktion in einer öffentlichen Docker Registry `docker://{host}/{image}:{tag}` @@ -556,11 +570,11 @@ jobs: uses: docker://gcr.io/cloud-builders/gradle ``` -#### **`jobs..steps.run`** +### `jobs..steps.run` -Führt Befehlszeilenprogramme über die Betriebssystem-Shell aus. Wenn Sie keinen `name` angeben, wird standardmäßig der im `run`-Befehl angegebene Text als Schrittname übernommen. +Führt Befehlszeilen-Programme über die Betriebssystem-Shell aus. Wenn Du keinen `name` angibst, wird standardmäßig der im Befehl `run` angegebene Text als Name für den Schritt übernommen. -Befehle greifen standardmäßig auf Shells zurück, für die keine Anmeldung erforderlich ist. Sie können eine andere Shell für die Ausführung von Befehlen auswählen und die Shell anpassen. Weitere Informationen finden Sie unter „[Bestimmte Shell verwenden](#using-a-specific-shell)“. +Befehle greifen standardmäßig auf Shells zurück, für die keine Anmeldung erforderlich ist. Du kannst für die Ausführung von Befehlen eine andere Shell auswählen und die Shell anpassen. Weitere Informationen findest Du unter „[Bestimmte Shell verwenden](#using-a-specific-shell)“. Jedes Schlüsselwort `run` stellt einen neuen Prozess und eine neue Shell in der Runnerumgebung dar. Wenn Du mehrzeilige Befehle angibst, werden alle Zeilen in derselben Shell ausgeführt. Ein Beispiel: @@ -580,7 +594,7 @@ Jedes Schlüsselwort `run` stellt einen neuen Prozess und eine neue Shell in der npm run build ``` -Mit dem Stichwort `working-directory` geben Sie das Arbeitsverzeichnis an, in dem der Befehl ausgeführt werden soll. +Mit dem Schlüsselwort`working-directory` gibst Du das Arbeitsverzeichnis an, in dem der Befehl ausgeführt werden soll. ```yaml - name: Clean temp directory @@ -588,7 +602,7 @@ Mit dem Stichwort `working-directory` geben Sie das Arbeitsverzeichnis an, in de working-directory: ./temp ``` -##### Bestimmte Shell verwenden +#### Bestimmte Shell verwenden Du kannst die Einstellungen zur Standard-Shell im Betriebssystem des Läufers mit dem Schlüsselwort `shell` überschreiben. Sie können die integrierten `shell`-Stichwörter verwenden oder eine benutzerdefinierte Reihe von Shell-Optionen definieren. @@ -601,7 +615,7 @@ Du kannst die Einstellungen zur Standard-Shell im Betriebssystem des Läufers mi | Windows | `cmd` | {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.cmd` an Deinen Skriptnamen an und ersetzt `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | | Windows | `powershell` | Dies ist die standardmäßig für Windows verwendete Shell. Die Desktop PowerShell. {% data variables.product.prodname_dotcom %} hängt die Erweiterung `.ps1` an Deinen Skriptnamen an. | `powershell -command ". '{0}'"`. | -##### Beispiel zur Ausführung eines Skripts mittels Bash +#### Beispiel zur Ausführung eines Skripts mittels Bash ```yaml steps: @@ -610,7 +624,7 @@ steps: shell: bash ``` -##### Beispiel zur Ausführung eines Skripts mittels `cmd` von Windows +#### Beispiel zur Ausführung eines Skripts mittels `cmd` von Windows ```yaml steps: @@ -619,7 +633,7 @@ steps: shell: cmd ``` -##### Beispiel zur Ausführung eines Skripts mittels PowerShell Core +#### Beispiel zur Ausführung eines Skripts mittels PowerShell Core ```yaml steps: @@ -628,7 +642,7 @@ steps: shell: pwsh ``` -##### Beispiel zur Ausführung eines Python-Skripts +#### Beispiel zur Ausführung eines Python-Skripts ```yaml steps: @@ -639,13 +653,13 @@ steps: shell: python ``` -##### Benutzerdefinierte Shell +#### Benutzerdefinierte Shell -Mit `command […options] {0} [..more_options]` können Sie einen Vorlagen-String für den `shell`-Wert festlegen. {% data variables.product.prodname_dotcom %} interpretiert das erste Wort im String, nach dem ein Leerzeichen steht, als Befehl, und der Dateiname für das temporäre Skript wird in `{0}` eingefügt. +Mit `command […options] {0} [..more_options]` können Sie einen Vorlagen-String für den `shell`-Wert festlegen. {% data variables.product.prodname_dotcom %} interpretiert das erste Wort im String, nach dem ein „Whitespace“ (Zwischenraum-Zeichen) steht, als Befehl, und der Dateiname für das temporäre Skript wird in `{0}` eingefügt. -##### Exit-Codes und Voreinstellung für Fehleraktionen +#### Exit-Codes und Voreinstellung für Fehleraktionen -Für integrierte Shell-Stichwörter gelten die folgenden Standards, die durch auf {% data variables.product.prodname_dotcom %} gehostete Runner ausgeführt werden. Beachten Sie diese Richtlinien beim Ausführen von Shell-Skripts. +Für integrierte Shell-Schlüsselwörter gelten die folgenden Standards, die durch auf {% data variables.product.prodname_dotcom %} gehostete Runner ausgeführt werden. Beachte diese Richtlinien beim Ausführen von Shell-Skripts. - `bash`/`sh`: - Fail-Fast-Verhalten mit `set -e o pipefail`: Standard für `bash` und integrierte `shell`. Dies ist außerdem der Standard, wenn Du eine Option für eine Plattform außer Windows angibst. @@ -661,11 +675,11 @@ Für integrierte Shell-Stichwörter gelten die folgenden Standards, die durch au - Wenn Du das Fail-Fast-Verhalten uneingeschränkt nutzen möchtest, hast Du anscheinend keine andere Wahl, als Dein Skript so zu schreiben, dass jeder Fehlercode geprüft und eine entsprechende Reaktion eingeleitet wird. Dieses Verhalten kann nicht standardmäßig bereitgestellt werden; Du musst es explizit in Dein Skript schreiben. - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. Dieses Verhalten ist intern mit dem vorherigen Standardverhalten von `sh` und `pwsh` konsistent und ist der Standard für `cmd.exe`, weshalb dieses Verhalten unverändert bleibt. -#### **`jobs..steps.with`** +### `jobs..steps.with` -`map` der Eingabeparameter, die in der Aktion definiert sind. Jeder Eingabeparameter ist ein Schlüssel-Wert-Paar. Eingabeparameter werden als Umgebungsvariablen festgelegt. Die Variable erhält das Präfix `INPUT_` und wird in Großbuchstaben umgewandelt. +Eine `map` der Eingabeparameter, die in der Aktion definiert sind. Jeder Eingabeparameter ist ein Schlüssel-Wert-Paar. Eingabeparameter werden als Umgebungsvariablen festgelegt. Die Variable erhält das Präfix `INPUT_` und wird in Großbuchstaben umgewandelt. -##### Beispiel +#### Beispiel Definiert die drei Eingabeparameter (`first_name`, `middle_name` und `last_name`), die in der Aktion `hello_world` definiert sind. Diese Eingabevariablen sind für die Aktion `hello-world` als Umgebungsvariablen `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` und `INPUT_LAST_NAME` zugänglich. @@ -681,11 +695,11 @@ jobs: last_name: Octocat ``` -#### **`jobs..steps.with.args`** +### `jobs..steps.with.args` Ein `string`, der die Eingaben für einen Docker-Container definiert. Beim Start des Containers übergibt {% data variables.product.prodname_dotcom %} die `args`-Anweisung an den `ENTRYPOINT` des Containers. Ein `array of strings` wird von diesem Parameter nicht unterstützt. -##### Beispiel +#### Beispiel {% raw %} ```yaml @@ -704,11 +718,11 @@ Die `args`-Anweisungen werden anstelle der `CMD`-Anweisung in einem `Dockerfile` 1. Verwenden Sie Standardwerte, die die Verwendung der Aktion ohne Angabe von `args` erlauben. 1. Wenn die Aktion einen Schalter `--help` oder Ähnliches anbietet, verwende diesen als Standard, um eine selbstständige Dokumentation der Aktion herbeizuführen. -#### **`jobs..steps.with.entrypoint`** +### `jobs..steps.with.entrypoint` Überschreibt den Docker-`ENTRYPOINT` im `Dockerfile` oder legt ihn fest, sofern er noch nicht angegeben wurde. Im Gegensatz zur Docker `ENTRYPOINT`-Anweisung, die eine Shell- und eine ausführbare Form aufweist, akzeptiert das Stichwort `entrypoint` nur einen einzigen Schritt, der die entsprechende ausführbare Datei definiert. -##### Beispiel +#### Beispiel ```yaml steps: @@ -720,15 +734,15 @@ steps: The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. -#### **`jobs..steps.env`** +### `jobs..steps.env` Legt Umgebungsvariablen für Schritte fest, die in der Runner-Umgebung verwendet werden sollen. Darüber hinaus können Sie Umgebungsvariablen für den gesamten Workflow oder für einen Auftrag festlegen. Weitere Informationen finden Sie unter [`env`](#env) und [`jobs..env`](#jobsjob_idenv). {% data reusables.repositories.actions-env-var-note %} -Die erwarteten Umgebungsvariablen können durch öffentliche Aktionen in der README-Datei angegeben werden. Wenn Sie ein Geheimnis in einer Umgebungsvariable festlegen, müssen Sie dieses Geheimnis mit dem `secrets`-Kontext angeben. Weitere Informationen findest Du unter „[Umgebungsvariablen verwenden](/actions/automating-your-workflow-with-github-actions/using-environment-variables)“ und „[Kontext- und Ausdruckssyntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)“. +Die erwarteten Umgebungsvariablen können durch öffentliche Aktionen in der README-Datei angegeben werden. Wenn Du ein Geheimnis in einer Umgebungsvariable festlegst, musst Du dieses Geheimnis mit dem Kontext `secrets` angeben. Weitere Informationen findest Du unter „[Umgebungsvariablen verwenden](/actions/automating-your-workflow-with-github-actions/using-environment-variables)“ und „[Kontext- und Ausdruckssyntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)“. -##### Beispiel +#### Beispiel {% raw %} ```yaml @@ -741,23 +755,23 @@ steps: ``` {% endraw %} -#### **`jobs..steps.continue-on-error`** +### `jobs..steps.continue-on-error` -Verhindert das Fehlschlagen eines Auftrags, wenn ein Schritt fehlschlägt. Legen Sie `true` fest, damit ein Auftrag auch dann erfolgreich abgeschlossen werden kann, wenn dieser Schritt fehlschlägt. +Verhindert das Fehlschlagen eines Auftrags, wenn ein Schritt fehlschlägt. Leg `true` fest, damit ein Auftrag auch dann erfolgreich abgeschlossen werden kann, wenn dieser Schritt fehlschlägt. -#### **`jobs..steps.timeout-minutes`** +### `jobs..steps.timeout-minutes` Maximaler Zeitraum in Minuten für die Ausführung des Schritts, bevor der Prozess abgebrochen wird. -### **`jobs..timeout-minutes`** +### `jobs..timeout-minutes` Die maximale Anzahl von Minuten, die ein Job ausgeführt wird, bevor {% data variables.product.prodname_dotcom %} automatisch abbricht. Standard: 360 -### **`jobs..strategy`** +### `jobs..strategy` Mit einer Strategie wird eine Build-Matrix für die Aufträge erstellt. Sie können verschiedene Varianten einer Umgebung definieren, in denen die einzelnen Aufträge ausgeführt werden. -#### **`jobs..strategy.matrix`** +### `jobs..strategy.matrix` Du kannst eine Matrix aus verschiedenen Job-Konfigurationen definieren. Mit einer Matrix kannst Du mehrere Jobs erstellen, indem Du in einer einzigen Jobdefinition Variablen substituierst. Zum Beispiel kannst Du eine Matrix verwenden, um Jobs für mehrere unterstützte Versionen einer Programmiersprache, eines Betriebssystems oder eines Tools zu erstellen. Eine Matrix verwendet die Job-Konfiguration mehrfach und erstellt einen Job für jeden Eintrag in der Matrix, die Du konfigurierst. @@ -767,7 +781,7 @@ Jede Option, die Du in der `Matrix` definierst, hat einen Schlüssel und einen W Die Reihenfolge, in der Du eine `Matrix` definierst, ist wichtig. Die erste Option, die Du definierst, ist der erste Job, der im Workflow ausgeführt wird. -##### Beispiel für die Ausführung mit mehreren Versionen von Node.js +#### Beispiel für die Ausführung mit mehreren Versionen von Node.js Zum Erstellen einer Matrix geben Sie ein Array für die Konfigurationsoptionen an. Wenn der Runner beispielsweise die Node.js-Versionen 6, 8 und 10 unterstützt, kannst Du ein Array dieser Versionen in der `matrix` festlegen. @@ -789,7 +803,7 @@ steps: Die Aktion `setup-node` ist das empfohlene Mittel zur Konfiguration einer Node.js-Version, wenn {% data variables.product.prodname_dotcom %}-gehostete Runner verwendet werden. Weitere Informationen findest Du in der Aktion [`setup-node`](https://github.com/actions/setup-node). -##### Beispiel für die Ausführung mit mehreren Betriebssystemen +#### Beispiel für die Ausführung mit mehreren Betriebssystemen Du kannst eine Matrix erstellen, um Workflows auf mehreren Runner-Betriebssystemen auszuführen. Du kannst auch mehrere Matrix-Konfigurationen angeben. Dieses Beispiel erstellt eine Matrix von 6 Jobs: @@ -814,7 +828,7 @@ steps: Unterstützte Konfigurationsoptionen für {% data variables.product.prodname_dotcom %}-gehostete Runner findest Du unter „[Virtuelle Umgebungen für {% data variables.product.prodname_dotcom %}-gehostete Runner](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)“. -##### Beispiel mit kombinierten zusätzlichen Werten +#### Beispiel mit kombinierten zusätzlichen Werten Sie können zusätzliche Konfigurationsoptionen hinzufügen, um einen bereits vorhandenen Matrixauftrag zu erstellen. Wenn Du beispielsweise eine bestimmte Version von `npm` verwenden willst, wenn der Auftrag mit `windows-latest` und Version 4 von `node` ausgeführt wird, kannst Du `include` verwenden, um diese zusätzliche Option anzugeben. @@ -834,7 +848,7 @@ strategy: ``` {% endraw %} -##### Beispiel zum Einbeziehen neuer Kombinationen +#### Beispiel zum Einbeziehen neuer Kombinationen Du kannst `include` verwenden, um neue Jobs zu einer Build-Matrix hinzuzufügen. Alle Include-Konfigurationen, die nicht passen, werden zur Matrix hinzugefügt. Wenn Du beispielsweise `node` Version 12 verwenden willst, um auf mehreren Betriebssystemen zu bauen, aber Du willst einen zusätzlichen experimentellen Job mit Node Version 13 auf Ubuntu, kannst Du `include` verwenden, um diesen zusätzlichen Job anzugeben. @@ -852,7 +866,7 @@ strategy: ``` {% endraw %} -##### Beispiel zum Ausschließen von Konfigurationen aus einer Matrix +#### Beispiel zum Ausschließen von Konfigurationen aus einer Matrix Mit der Option `exclude` können Sie bestimmte in der Build-Matrix definierte Konfigurationen entfernen. Durch die Verwendung von `exclude` wird ein durch die Build-Matrix definierter Auftrag entfernt. Die Anzahl der Aufträge ist das Kreuzprodukt der Anzahl der Betriebssysteme (`os`), die in den von Ihnen bereitgestellten Arrays enthalten sind, abzüglich etwaiger Subtraktionen (`exclude`). @@ -882,11 +896,11 @@ You can add custom environment variables for each test combination by using the {% data reusables.github-actions.matrix-variable-example %} -### **`jobs..strategy.fail-fast`** +### `jobs..strategy.fail-fast` Wenn diese Option auf `true` gesetzt ist, bricht {% data variables.product.prodname_dotcom %} alle laufenden Jobs ab, sobald ein Job der `matrix` fehlschlägt. Standard: `true` -### **`jobs..strategy.max-parallel`** +### `jobs..strategy.max-parallel` Maximale Anzahl der Aufträge, die gleichzeitig ausgeführt werden können, wenn eine `matrix`-Auftragsstrategie herangezogen wird. Standardmäßig führt {% data variables.product.prodname_dotcom %} so viele Aufträge wie möglich parallel aus, je nach der Anzahl der verfügbaren Runner auf von {% data variables.product.prodname_dotcom %} gehosteten virtuellen Maschinen. @@ -895,7 +909,7 @@ strategy: max-parallel: 2 ``` -### **`jobs..continue-on-error`** +### `jobs..continue-on-error` Verhindert, dass ein Workflow scheitert, wenn ein Job scheitert. Setze es auf `true` um einen Workflow-Lauf fortzusetzen, wenn dieser Job scheitert. @@ -920,7 +934,7 @@ strategy: ``` {% endraw %} -### **`jobs..container`** +### `jobs..container` Container, in dem alle Schritte eines Auftrags ausgeführt werden, für die kein Container explizit angegeben ist. Wenn ein Schritt sowohl Skript- als auch Container-Aktionen umfasst, werden die Container-Aktionen als nebengeordnete Container in demselben Netzwerk mit denselben Volume-Mounts ausgeführt. @@ -950,16 +964,17 @@ jobs: container: node:10.16-jessie ``` -#### **`jobs..container.image`** +### `jobs..container.image` Docker-Image, das beim Ausführen der Aktion als Container herangezogen wird. 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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..container.credentials`** + +### `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -##### Beispiel +#### Beispiel {% raw %} ```yaml @@ -972,15 +987,15 @@ container: {% endraw %} {% endif %} -#### **`jobs..container.env`** +### `jobs..container.env` Legt eine `map` mit Umgebungsvariablen im Container fest. -#### **`jobs..container.ports`** +### `jobs..container.ports` Legt ein `array` mit Ports fest, die im Container offengelegt werden. -#### **`jobs..container.volumes`** +### `jobs..container.volumes` Legt ein `array` mit Volumes für den Container fest. Mithilfe von Volumes können Sie Daten zwischen Diensten oder anderen Schritten in einem Auftrag austauschen. Sie können benannte Docker-Volumes, anonyme Docker-Volumes oder Bind-Mounts auf dem Host angegeben. @@ -990,7 +1005,7 @@ Für ein Volume geben Sie den Quell- und Zielpfad an: `` bezeichnet einen Volume-Namen oder einen absoluten Pfad auf der Hostmaschine und `` einen absoluten Pfad im Container. -##### Beispiel +#### Beispiel ```yaml volumes: @@ -999,11 +1014,11 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..container.options`** +### `jobs..container.options` Zusätzliche Optionen für die Docker-Containerressource. Eine Liste der Optionen finden Sie unter „[Optionen für `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)“. -### **`jobs..services`** +### `jobs..services` {% data reusables.github-actions.docker-container-os-support %} @@ -1033,16 +1048,17 @@ services: - 6379/tcp ``` -#### **`jobs..services..image`** +### `jobs..services..image` Docker-Image, das beim Ausführen der Aktion als Dienstcontainer herangezogen wird. 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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..services..credentials`** + +### `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -##### Beispiel +#### Beispiel {% raw %} ```yaml @@ -1061,15 +1077,15 @@ services: {% endraw %} {% endif %} -#### **`jobs..services..env`** +### `jobs..services..env` Legt eine `map` mit Umgebungsvariablen im Servicecontainer fest. -#### **`jobs..services..ports`** +### `jobs..services..ports` Legt ein `array` mit Ports fest, die im Dienstcontainer offengelegt werden. -#### **`jobs..services..volumes`** +### `jobs..services..volumes` Legt ein `array` mit Volumes für den Dienstcontainer fest. Mithilfe von Volumes können Sie Daten zwischen Diensten oder anderen Schritten in einem Auftrag austauschen. Sie können benannte Docker-Volumes, anonyme Docker-Volumes oder Bind-Mounts auf dem Host angegeben. @@ -1079,7 +1095,7 @@ Für ein Volume geben Sie den Quell- und Zielpfad an: `` bezeichnet einen Volume-Namen oder einen absoluten Pfad auf der Hostmaschine und `` einen absoluten Pfad im Container. -##### Beispiel +#### Beispiel ```yaml volumes: @@ -1088,7 +1104,7 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..services..options`** +### `jobs..services..options` Zusätzliche Optionen für die Docker-Containerressource. Eine Liste der Optionen finden Sie unter „[Optionen für `docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)“. diff --git a/translations/de-DE/content/admin/configuration/index.md b/translations/de-DE/content/admin/configuration/index.md index e096445fd3..1311a4e241 100644 --- a/translations/de-DE/content/admin/configuration/index.md +++ b/translations/de-DE/content/admin/configuration/index.md @@ -31,9 +31,7 @@ versions: {% link_in_list /enabling-private-mode %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} - {% link_in_list /configuring-applications %} - {% link_in_list /troubleshooting-ssl-errors %} {% link_in_list /configuring-time-synchronization %} {% link_in_list /command-line-utilities %} @@ -54,11 +52,7 @@ versions: {% link_in_list /connecting-github-enterprise-server-to-github-enterprise-cloud %} {% link_in_list /enabling-unified-search-between-github-enterprise-server-and-githubcom %} {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %} - {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %} {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} - - {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} - diff --git a/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md index 88c402a15d..e94f6ff87c 100644 --- a/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/de-DE/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -37,7 +37,7 @@ Die für das Failover erforderliche Zeit hängt davon ab, wie lange es dauert, d ``` - On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace *`UUID`* with a UUID you retrieved in the previous step. ```shell - $ ghe-repl-teardown -u UUNID + $ ghe-repl-teardown -u UUID ``` ### Weiterführende Informationen 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 7ad06ed0b1..6ac6a0c8d7 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 @@ -24,7 +24,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ### Vorrausetzungen -* Before using the 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](/github/setting-up-and-managing-organizations-and-teams/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)." ### Example: Using the `actions-sync` tool diff --git a/translations/de-DE/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/de-DE/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 3a62e64192..7f4fa7c691 100644 --- a/translations/de-DE/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/de-DE/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -1,6 +1,6 @@ --- title: Setting up the tool cache on self-hosted runners without internet access -intro: 'To use the the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' +intro: 'To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' redirect_from: - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access versions: diff --git a/translations/de-DE/content/admin/index.md b/translations/de-DE/content/admin/index.md index 14c3aca964..6928e31fc4 100644 --- a/translations/de-DE/content/admin/index.md +++ b/translations/de-DE/content/admin/index.md @@ -28,3 +28,5 @@ versions: {% link_with_intro /packages %} {% link_with_intro /enterprise-support %} + +{% link_with_intro /release-notes %} diff --git a/translations/de-DE/content/admin/overview/about-enterprise-accounts.md b/translations/de-DE/content/admin/overview/about-enterprise-accounts.md index fd8076ac5d..9014ddded9 100644 --- a/translations/de-DE/content/admin/overview/about-enterprise-accounts.md +++ b/translations/de-DE/content/admin/overview/about-enterprise-accounts.md @@ -15,7 +15,7 @@ An enterprise account allows you to manage multiple organizations{% if enterpris - 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) +- 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 reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." diff --git a/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md b/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md index ec679b8d8c..8305fed871 100644 --- a/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/de-DE/content/developers/apps/authenticating-with-github-apps.md @@ -28,7 +28,7 @@ To generate a private key: {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. In "Private keys," click **Generate a private key**. ![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png) +5. In "Private keys", click **Generate a private key**. ![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png) 6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key. {% note %} 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 1da31833df..f93dbcf20d 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 @@ -73,7 +73,9 @@ You can select permissions in a query string using the permission name in the fo | `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. | | [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | | [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %} | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. | | [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. | | [`statuses (Statusangaben)`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. | diff --git a/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md b/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md index 2902008e0d..b1331ee4fb 100644 --- a/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/scopes-for-oauth-apps.md @@ -46,7 +46,8 @@ X-Accepted-OAuth-Scopes: user |  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | |  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | |  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | -|  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +|  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +|  `security_events` | Grants:
read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).
read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} |  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} | **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | |  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | diff --git a/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index b0afd855de..bbc2fba7ef 100644 --- a/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/de-DE/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -422,7 +422,7 @@ Here are a few common problems and some suggested solutions. If you run into any **A:** You may not be running the Smee client, or you may not have the correct Smee domain in your GitHub App settings. First check to make sure the Smee client is running in a Terminal tab. If that's not the problem, visit your [app settings page](https://github.com/settings/apps) and check the fields shown in "[Step 2. Register a new GitHub App](#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u ` command in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." -* **Q:** I'm getting seeing an `Octokit::NotFound` 404 error in my debug output: +* **Q:** I'm getting an `Octokit::NotFound` 404 error in my debug output: ``` 2018-12-06 15:00:56 - Octokit::NotFound - POST https://api.github.com/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token: ``` diff --git a/translations/de-DE/content/developers/github-marketplace/about-github-marketplace.md b/translations/de-DE/content/developers/github-marketplace/about-github-marketplace.md index 8f20b883d4..47019fdbe0 100644 --- a/translations/de-DE/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/de-DE/content/developers/github-marketplace/about-github-marketplace.md @@ -1,6 +1,6 @@ --- title: Informationen zu GitHub Marketplace -intro: 'Learn the basics to prepare your app for review before joining {% data variables.product.prodname_marketplace %}.' +intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.' redirect_from: - /apps/marketplace/getting-started/ - /marketplace/getting-started @@ -14,52 +14,41 @@ versions: {% data reusables.actions.actions-not-verified %} -To learn about publishing {% data variables.product.prodname_actions %} in the {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." +To learn about publishing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." ### Apps -You can list verified and unverified apps in {% data variables.product.prodname_marketplace %}. Unverified apps do not go through the security, testing, and verification cycle {% data variables.product.prodname_dotcom %} requires for verified apps. +Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only listings that are verified by {% data variables.product.company_short %} can include paid plans. For more information, see "[About verified creators](/developers/github-marketplace/about-verified-creators)." -Verified apps have a green badge in {% data variables.product.prodname_marketplace %}. Unverified apps have a grey badge next to their listing and are only available as free apps. +If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)." -![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) - -If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s, see "[Building apps](/apps/)." - -{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. See "[Differences between GitHub and OAuth apps](/apps/differences-between-apps/)" for more details. To learn more about switching from OAuth to {% data variables.product.prodname_github_apps %}, see [Migrating OAuth Apps to {% data variables.product.prodname_github_app %}s](/apps/migrating-oauth-apps-to-github-apps/). +{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_app %}s to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. -#### Unverified Apps +### Publishing an app to {% data variables.product.prodname_marketplace %} -Unverified apps do not need to meet the "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)" or go through the "[Security review process](/marketplace/getting-started/security-review-process/)". +When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: -{% data reusables.marketplace.unverified-apps %} Having a published paid plan will prevent you from being able to submit an unverified app. You must remove paid plans or keep them in draft mode before publishing an unverified app. +1. Review your app carefully to ensure that it will behave as expected in other repositories and that it follows best practice guidelines. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)." -To list your unverified app in {% data variables.product.prodname_marketplace %}, you only need to create a "[Listing on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)" and submit it as an unverified listing. +1. Add webhook events to the app to track user billing requests. For more information about the {% data variables.product.prodname_marketplace %} API, webhook events, and billing requests, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.launch-with-free %} +1. Create a draft {% data variables.product.prodname_marketplace %} listing. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -#### Verified Apps +1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -If you've already built an app and you're interested in submitting a verified listing in {% data variables.product.prodname_marketplace %}, start here: +1. Check whether your app meets the requirements for listing on {% data variables.product.prodname_marketplace %} as a free or a paid app. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." -1. [Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)
Learn about requirements, guidelines, and the app submission process. +1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -1. [Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)
Before you can list your app on {% data variables.product.prodname_marketplace %}, you'll need to integrate billing flows using the {% data variables.product.prodname_marketplace %} API and webhook events. +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}, requesting verification if you want to sell the app. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." -1. [Listing on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)
Create a draft {% data variables.product.prodname_marketplace %} listing, configure webhook settings, and set up pricing plans. +An onboarding expert will contact you with any questions or further steps. For example, if you have added a paid plan, you will need to complete the verification process and complete financial onboarding. As soon as your listing is approved the app is published to {% data variables.product.prodname_marketplace %}. -1. [Selling your app](/marketplace/selling-your-app/)
Learn about pricing plans, billing cycles, and how to receive payment from {% data variables.product.prodname_dotcom %} for your app. +### Seeing how your app is performing -1. [{% data variables.product.prodname_marketplace %} Insights](/marketplace/github-marketplace-insights/)
See how your app is performing in {% data variables.product.prodname_marketplace %}. You can use metrics collected by {% data variables.product.prodname_dotcom %} to guide your marketing campaign and be successful in {% data variables.product.prodname_marketplace %}. +You can access metrics and transactions for your listing. Weitere Informationen findest Du unter: -1. [{% data variables.product.prodname_marketplace %} transactions](/marketplace/github-marketplace-transactions/)
Download and view transaction data for your {% data variables.product.prodname_marketplace %} listing. - -### Reviewing your app - -We want to make sure that the apps offered on {% data variables.product.prodname_marketplace %} are safe, secure, and well tested. The {% data variables.product.prodname_marketplace %} onboarding specialists will review your app to ensure that it meets all requirements. Follow the guidelines in these articles before submitting your app: - - -* [Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) -* [Security review process](/marketplace/getting-started/security-review-process/) +- "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" +- "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" diff --git a/translations/de-DE/content/developers/github-marketplace/about-verified-creators.md b/translations/de-DE/content/developers/github-marketplace/about-verified-creators.md new file mode 100644 index 0000000000..915c221b27 --- /dev/null +++ b/translations/de-DE/content/developers/github-marketplace/about-verified-creators.md @@ -0,0 +1,43 @@ +--- +title: About verified creators +intro: 'Each organization that wants to sell apps on {% data variables.product.prodname_marketplace %} must follow a verification process. Their identity is checked and their billing process reviewed.' +versions: + free-pro-team: '*' +--- + +### About verified creators + +A verified creator is an organization that {% data variables.product.company_short %} has checked. Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only organizations that are verified by {% data variables.product.company_short %} can sell apps. For more information about organizations, see "[About organizations](/github/setting-up-and-managing-organizations-and-teams/about-organizations)." + +The verification process aims to protect users. For example, it verifies the seller's identity, checks that their {% data variables.product.product_name %} organization is set up securely, and that they can be contacted for support. + +After passing the verification checks, any apps that the organization lists on {% data variables.product.prodname_marketplace %} are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. The organization can now add paid plans to any of their apps. Each app with a paid plan also goes through a financial onboarding process to check that it's set up to handle billing correctly. + +![verified creator badges](/assets/images/marketplace/marketplace_verified_creator_badges_apps.png) + +In addition to the verified creator badge, you'll also see badges for unverified and verified apps. These apps were published using the old method for verifying individual apps. + +![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) + +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." + +### About the verification process + +The first time you request verification for a listing of one of your apps, you will enter the verification process. An onboarding expert will guide you through the process. This includes checking: + +- Profile information - The basic profile information is populated accurately and appropriately. +- Security - The organization has enabled two-factor authentication. +- Verified domain - The organization has verified the domain of the site URL. +- Purchase webhook event - The event is handled correctly by the app. + +When your organization is verified, all your apps are shown with a verified creator badge. You are now able to offer paid plans for any of your apps. + +For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% note %} + +**Note:** This verification process for apps replaces the previous process where individual apps were verified. The current process is similar to the verification process for actions. If you have apps that were verified under the old process, these will not be affected by the changes. The {% data variables.product.prodname_marketplace %} team will contact you with details of how to migrate to organization-based verification. + +{% endnote %} diff --git a/translations/de-DE/content/developers/github-marketplace/billing-customers.md b/translations/de-DE/content/developers/github-marketplace/billing-customers.md index 301f6bab3d..657be717d5 100644 --- a/translations/de-DE/content/developers/github-marketplace/billing-customers.md +++ b/translations/de-DE/content/developers/github-marketplace/billing-customers.md @@ -13,17 +13,17 @@ versions: ### Understanding the billing cycle -Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[Webhook events for the {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)." ### Providing billing services in your app's UI -Customers must be able to perform the following actions from your app's website: -- Customers must be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. +Customers should be able to perform the following actions from your app's website: +- Customers should be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. {% data reusables.marketplace.marketplace-billing-ui-requirements %} ### Billing services for upgrades, downgrades, and cancellations -Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)." +Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). @@ -33,7 +33,7 @@ When a customer upgrades their pricing plan or changes their billing cycle from {% data reusables.marketplace.marketplace-failed-purchase-event %} -For information about building upgrade and downgrade workflows into your app, see "[Upgrading and downgrading plans](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)." +For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)." #### Downgrades and cancellations @@ -45,4 +45,4 @@ When a customer cancels a plan, you must: {% data reusables.marketplace.cancellation-clarification %} - Enable them to upgrade the plan through GitHub if they would like to continue the plan at a later time. -For information about building cancellation workflows into your app, see "[Cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)." +For information about building cancellation workflows into your app, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." diff --git a/translations/de-DE/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md b/translations/de-DE/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md new file mode 100644 index 0000000000..4107fa4427 --- /dev/null +++ b/translations/de-DE/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md @@ -0,0 +1,20 @@ +--- +title: Customer experience best practices for apps +intro: 'Guidelines for creating an app that will be easy to use and understand.' +shortTitle: Customer experience best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a good customer experience. + +### Customer communication + +- Marketing materials for the app should accurately represent the app's behavior. +- Apps should include links to user-facing documentation that describe how to set up and use the app. +- Customers should be able to see what type of plan they have in the billing, profile, or account settings section of the app. +- Customers should be able to install and use your app on both a personal account and an organization account. They should be able to view and manage the app on those accounts separately. + +### Plan management + +{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/de-DE/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/de-DE/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 7bc6b6e542..52c2c64dc9 100644 --- a/translations/de-DE/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/de-DE/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,8 +60,8 @@ Once you've created a {% data variables.product.prodname_marketplace %} draft li ### Submitting your app -Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, the {% data variables.product.prodname_marketplace %} onboarding team will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." +Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." ### Removing a {% data variables.product.prodname_marketplace %} listing -If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact [marketplace@github.com](mailto:marketplace@github.com) to remove your listing. +If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing. diff --git a/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index 5cfbcccaff..0b34ca2176 100644 --- a/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/de-DE/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -28,7 +28,7 @@ GitHub then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketp Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins. -If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)." See "[Upgrading and downgrading plans](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)" to find out how to transition a free trial to a paid plan when a free trial expires. +If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." See "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)" to find out how to transition a free trial to a paid plan when a free trial expires. See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload. diff --git a/translations/de-DE/content/developers/github-marketplace/index.md b/translations/de-DE/content/developers/github-marketplace/index.md index a6fdfe44e7..612c9ed17c 100644 --- a/translations/de-DE/content/developers/github-marketplace/index.md +++ b/translations/de-DE/content/developers/github-marketplace/index.md @@ -11,8 +11,10 @@ versions: {% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /about-github-marketplace %} + {% link_in_list /about-verified-creators %} {% link_in_list /requirements-for-listing-an-app %} - {% link_in_list /security-review-process-for-submitted-apps %} + {% link_in_list /security-best-practices-for-apps %} + {% link_in_list /customer-experience-best-practices-for-apps %} {% link_in_list /viewing-metrics-for-your-listing %} {% link_in_list /viewing-transactions-for-your-listing %} {% topic_link_in_list /using-the-github-marketplace-api-in-your-app %} @@ -27,7 +29,7 @@ versions: {% link_in_list /writing-a-listing-description-for-your-app %} {% link_in_list /setting-pricing-plans-for-your-listing %} {% link_in_list /configuring-a-webhook-to-notify-you-of-plan-changes %} - {% link_in_list /submitting-your-listing-for-review %} + {% link_in_list /submitting-your-listing-for-publication %} {% topic_link_in_list /selling-your-app-on-github-marketplace %} {% link_in_list /pricing-plans-for-github-marketplace-apps %} {% link_in_list /billing-customers %} diff --git a/translations/de-DE/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/de-DE/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md index bb33fe004f..aa9d924b49 100644 --- a/translations/de-DE/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/de-DE/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -10,35 +10,45 @@ versions: -{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit, and GitHub lists the price in US dollars. Customers purchase your app using a payment method attached to their {% data variables.product.product_name %} account, without having to leave GitHub.com. You don't have to write code to perform billing transactions, but you will have to handle [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) for purchase events. +{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to verified listings. + +Customers purchase your app using a payment method attached to their {% data variables.product.product_name %} account, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed. For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." -{% note %} - -**Note:** If you're listing an app on {% data variables.product.prodname_marketplace %}, you can't list your app with a free pricing plan if you offer a paid service outside of {% data variables.product.prodname_marketplace %}. - -{% endnote %} +{% data reusables.marketplace.free-plan-note %} ### Types of pricing plans -**Free pricing plans** are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. Unverified free apps do not need to implement any billing flows. Free apps that are verified by Github need to implement billing flows for new purchases and cancellations, but do not need to implement billing flows for free trials, upgrades, and downgrades. If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to resubmit the app for review. +#### Free pricing plans -**Flat rate pricing plans** charge a set fee on a monthly and yearly basis. +{% data reusables.marketplace.free-apps-encouraged %} -**Per-unit pricing plans** charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). +Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. -**Marketplace free trials** provide 14-day free trials of OAuth or GitHub Apps to customers. When you [set up a Marketplace pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/), you can select the option to provide a free trial for flat-rate or per-unit pricing plans. +All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding. + +#### Paid pricing plans + +There are two types of paid pricing plan: + +- Flat rate pricing plans charge a set fee on a monthly and yearly basis. + +- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). + +You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans. ### Free trials -Customers can start a free trial for any available paid plan on a Marketplace listing, but will not be able to create more than one free trial for a Marketplace product. +Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product. Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel. -See "[New purchases and free trials](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for details on how to handle free trials in your app. +For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)." {% note %} diff --git a/translations/de-DE/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/de-DE/content/developers/github-marketplace/requirements-for-listing-an-app.md index 3e31fed9db..2ae24c334e 100644 --- a/translations/de-DE/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/de-DE/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- title: Requirements for listing an app -intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before our {% data variables.product.prodname_marketplace %} onboarding specialists will approve the listing.' +intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ @@ -12,49 +12,62 @@ versions: free-pro-team: '*' --- + +The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app. -Before you submit your app for review, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." You'll accept the terms within your [draft listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) on {% data variables.product.product_name %}. Once you've submitted your app, one of the {% data variables.product.prodname_marketplace %} onboarding specialists will reach out to you with more information about the onboarding process, and review your app to ensure it meets these requirements: +### Requirements for all {% data variables.product.prodname_marketplace %} listings -### User experience +All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -- {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. -- {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. +#### User experience requirements for all apps + +All listings should meet the following requirements, regardless of whether they are for a free or paid app. + +- Listings must not actively persuade users away from {% data variables.product.product_name %}. +- Listings must include valid contact information for the publisher. +- Listings must have a relevant description of the application. +- Listings must specify a pricing plan. - Apps must provide value to customers and integrate with the platform in some way beyond authentication. - Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only. -- Apps cannot actively persuade users away from {% data variables.product.product_name %}. -- Marketing materials for the app must accurately represent the app's behavior. -- Apps must include links to user-facing documentation that describe how to set up and use the app. -- When a customer purchases an app and GitHub redirects them to the app's installation URL, the app must begin the OAuth flow immediately. For details, see "[Handling new purchases and free trials](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/#step-3-authorization)." +- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -- Customers must be able to install your app and select repositories on both a personal and organization account. They should be able to view and manage those accounts separately. +For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)." -### Brand and listing +#### Brand and listing requirements for all apps -- Apps that use GitHub logos must follow the "[{% data variables.product.product_name %} Logos and Usage](https://github.com/logos)" guidelines. +- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)." - Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." - Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." -### Sicherheit +To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)." -Apps will go through a security review before being listed on {% data variables.product.prodname_marketplace %}. A successful review will meet the requirements and follow the security best practices listed in "[Security review process](/marketplace/getting-started/security-review-process/)." For information on the review process, contact [marketplace@github.com](mailto:marketplace@github.com). +### Considerations for free apps -### Billing flows +{% data reusables.marketplace.free-apps-encouraged %} -Your app must integrate [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) using the [{% data variables.product.prodname_marketplace %} webhook event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). +### Requirements for paid apps -#### Free apps +In addition to the requirements for all apps above, each app that you offer as a paid service on {% data variables.product.prodname_marketplace %} must also meet the following requirements: -{% data reusables.marketplace.free-apps-encouraged %} If you are listing a free app, you'll need to meet these requirements: +- {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. +- {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. +- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. +- Publishing organizations must have a verified domain and must enable two-factor authentication. 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.") -- Customers must be able to see that they have a free plan in the billing, profile, or account settings section of the app. -- When a customer cancels your app, you must follow the flow for [cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/). +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the listing. -#### Paid apps +{% note %} -To offer your app as a paid service, you'll need to meet these requirements to list your app on {% data variables.product.prodname_marketplace %}: +The verification process is open to organizations. {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% endnote %} + +### Billing requirements for paid apps + +Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their {% data variables.product.product_name %} account. -- To sell your app in {% data variables.product.prodname_marketplace %}, it must use GitHub's billing system. Your app does not need to handle payments but does need to use "[{% data variables.product.prodname_marketplace %} purchase events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" to manage new purchases, upgrades, downgrades, cancellations, and free trials. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" to learn about how to integrate these events into your app. Using GitHub's billing system allows customers to purchase an app without leaving GitHub and pay for the service with the payment method already attached to their {% data variables.product.product_name %} account. - Apps must support both monthly and annual billing for paid subscriptions purchases. - Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." -{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/de-DE/content/developers/github-marketplace/security-best-practices-for-apps.md b/translations/de-DE/content/developers/github-marketplace/security-best-practices-for-apps.md new file mode 100644 index 0000000000..eaec8c6874 --- /dev/null +++ b/translations/de-DE/content/developers/github-marketplace/security-best-practices-for-apps.md @@ -0,0 +1,59 @@ +--- +title: Security best practices for apps +intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/marketplace/getting-started/security-review-process/ + - /marketplace/getting-started/security-review-process + - /developers/github-marketplace/security-review-process-for-submitted-apps +shortTitle: Security best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a secure user experience. + +### Authorization, authentication, and access control + +We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details. +- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia. +- Apps should provide customers with a way to delete their account, without having to email or call a support person. +- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately. +- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code. +- Apps should not share service accounts such as email or database services to manage your SaaS service. +- All services used in your app should have unique login and password credentials. +- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties. +- Apps should not use personal access tokens to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps): + - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/). + - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). + +### Data protection + +- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git. +- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). +- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub. +- Apps should not require the user to provide their GitHub password. +- Apps should encrypt tokens, client IDs, and client secrets. + +### Logging and monitoring + +Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year. A security log should include: + +- Authentication and authorization events +- Service configuration changes +- Object reads and writes +- All user and group permission changes +- Elevation of role to admin +- Consistent timestamping for each event +- Source users, IP addresses, and/or hostnames for all logged actions + +### Incident response workflow + +To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident. + +For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template. + +### Vulnerability management and patching workflow + +You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. + +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)." diff --git a/translations/de-DE/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/de-DE/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 7359ded5a1..9ab919817d 100644 --- a/translations/de-DE/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/de-DE/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Setting pricing plans for your listing -intro: 'When [listing your app on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/), you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' +intro: 'When you list your app on {% data variables.product.prodname_marketplace %}, you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' redirect_from: - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ @@ -17,57 +17,52 @@ versions: free-pro-team: '*' --- +### About setting pricing plans +If you want to sell an app on {% data variables.product.prodname_marketplace %}, you need to request verification when you publish the listing for your app. During the verification process, an onboarding expert checks the organization's identity and security settings. The onboarding expert will also take the organization through financial onboarding. For more information, see: "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% data variables.product.prodname_marketplace %} offers several different types of pricing plan. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." + +### About saving pricing plans + +You can save pricing plans in a draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish a pricing plan on a published listing, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. + +For guidelines on billing customers, see "[Billing customers](/developers/github-marketplace/billing-customers)." ### Creating pricing plans -To learn about the types of pricing plans that {% data variables.product.prodname_marketplace %} offers, see "[{% data variables.product.prodname_marketplace %} Pricing Plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." You'll also find helpful billing guidelines in "[Selling your app](/marketplace/selling-your-app/)." - -Pricing plans can be in the draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published listing will function the same way as draft listings until your app is approved and listed on {% data variables.product.prodname_marketplace %}. Draft listings allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish the pricing plan, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. - -To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). If you haven't created a {% data variables.product.prodname_marketplace %} listing yet, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how. +To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). For more information, see "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)." When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan: -#### Plan name +- **Plan name** - Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align with the plan's resources, the size of the company that will use the plan, or anything you'd like. -Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align to the plan's resources, the size of the company that will use the plan, or anything you'd like. +- **Pricing models** - There are three types of pricing plan: free, flat-rate, and per-unit. All plans require you to process new purchase and cancellation events from the marketplace API. In addition, for paid plans: -#### Pricing models + - You must set a price for both monthly and yearly subscriptions in US dollars. + - Your app must process plan change events. + - You must request verification to publish a listing with a paid plan. + - {% data reusables.marketplace.marketplace-pricing-free-trials %} -##### Free plans + For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.free-apps-encouraged %} A free plan still requires you to handle [new purchase](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/) and [cancellation](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/) billing flows. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" for more details. +- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. -##### Flat-rate plans +- **Short description** - Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. -Flat-rate pricing plans allow you to offer your service to customers for a flat-rate fee. {% data reusables.marketplace.marketplace-pricing-free-trials %} +- **Bullets** - You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. -You must set a price for both monthly and yearly subscriptions in U.S. Dollars for flat-rate plans. Dollars for flat-rate plans. - -##### Per-unit plans - -Per-unit pricing allows you to offer your app in units. For example, a unit can be a person, seat, or user. You'll need to provide a name for the unit and set a price for both monthly and yearly subscriptions, in U.S. Dollars. Dollars. - -#### Available for - -{% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. - -#### Short description - -Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. - -#### Bullets - -You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. +{% data reusables.marketplace.free-plan-note %} ### Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan -If a pricing plan for your {% data variables.product.prodname_marketplace %} plan is no longer needed or if you need to adjust pricing details, you can remove it. +If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it. ![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png) -Once you publish a pricing plan for an app already listed in the {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." +Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan and create a new plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription. diff --git a/translations/de-DE/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/de-DE/content/developers/github-marketplace/submitting-your-listing-for-publication.md new file mode 100644 index 0000000000..b25c4580ae --- /dev/null +++ b/translations/de-DE/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -0,0 +1,37 @@ +--- +title: Submitting your listing for publication +intro: 'You can submit your listing for the {% data variables.product.prodname_dotcom %} community to use.' +redirect_from: + - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review + - /developers/github-marketplace/submitting-your-listing-for-review +versions: + free-pro-team: '*' +--- + + + +Once you've completed the listing for your app, you'll see two buttons that allow you to request publication of the listing with or without verification. The **Request** button for "Publish without verification" is disabled if you have published any paid pricing plans in the listing. + +![Unverified and verified request button](/assets/images/marketplace/marketplace-request-button.png) + +{% data reusables.marketplace.launch-with-free %} + +After you submit your listing for review, an onboarding expert will reach out to you with additional information. + +For an overview of the process for creating and submitting a listing, see "[About {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)." + +### Prerequisites for publishing with verification + +Before you request verification of your listing, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your app. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +If you've met the requirements for listing and you've integrated with the {% data variables.product.prodname_marketplace %} API, go ahead and submit your listing. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Transferring an app to an organization before you submit](#transferring-an-app-to-an-organization-before-you-submit)" below. + +### Transferring an app to an organization before you submit + +You cannot sell an app that's owned by a user account. You need to transfer the app to an organization that is already a verified creator, or that can request verification for a listing for the app. For details, see: + +1. "[Creating an organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" + +1. "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" diff --git a/translations/de-DE/content/developers/github-marketplace/testing-your-app.md b/translations/de-DE/content/developers/github-marketplace/testing-your-app.md index 09e79b1a7a..577b6d624a 100644 --- a/translations/de-DE/content/developers/github-marketplace/testing-your-app.md +++ b/translations/de-DE/content/developers/github-marketplace/testing-your-app.md @@ -1,6 +1,6 @@ --- title: Testing your app -intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before the {% data variables.product.prodname_marketplace %} onboarding team approves your app, it must adequately handle the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows).' +intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.' redirect_from: - /apps/marketplace/testing-apps-apis-and-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ @@ -13,7 +13,7 @@ versions: ### Testing apps -You can use a [draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) to simulate each of the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows). A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. +You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." #### Using a development app with a draft listing to test changes diff --git a/translations/de-DE/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/de-DE/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index 49d83c1c6b..356e731262 100644 --- a/translations/de-DE/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/de-DE/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -1,6 +1,6 @@ --- title: Webhook events for the GitHub Marketplace API -intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan. For details on how to respond to each of these types of events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)."' +intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.' redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ diff --git a/translations/de-DE/content/developers/overview/about-githubs-apis.md b/translations/de-DE/content/developers/overview/about-githubs-apis.md index 0d647b78cb..e60baa72e3 100644 --- a/translations/de-DE/content/developers/overview/about-githubs-apis.md +++ b/translations/de-DE/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,7 @@ versions: github-ae: '*' --- -There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). - -When using the REST API, we encourage you to [request v3 via the `Accept` header](/rest/overview/media-types#request-specific-version). - -For information on using the GraphQL API, see the [v4 docs](/graphql). +There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). For information on using the GraphQL API, see the [v4 docs](/graphql). ## Deprecated versions diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md index 983d1ee06a..4657527874 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/de-DE/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -145,7 +145,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {{ webhookPayloadsForCurrentVersion.check_suite.completed }} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### code_scanning_alert {% data reusables.webhooks.code_scanning_alert_event_short_desc %} @@ -445,7 +445,7 @@ When someone revokes their authorization of a {% data variables.product.prodname #### Webhook payload object {% data reusables.webhooks.installation_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Webhook payload example @@ -469,7 +469,7 @@ When someone revokes their authorization of a {% data variables.product.prodname #### Webhook payload object {% data reusables.webhooks.installation_repositories_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Webhook payload example @@ -1047,7 +1047,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends | Schlüssel | Typ | Beschreibung | | --------- | -------- | -------------------------------------------------------------------------------- | -| `action` | `string` | die Aktion, die durchgeführt wurde. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/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.
| +| `action` | `string` | die Aktion, die durchgeführt wurde. 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.
| {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1100,6 +1100,31 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### secret_scanning_alert + +{% data reusables.webhooks.secret_scanning_alert_event_short_desc %} + +#### Availability + +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `secret_scanning_alerts:read` permission + +#### Webhook payload object + +{% 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. + +#### Webhook payload example + +{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} +{% endif %} + ### 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/)." @@ -1305,7 +1330,7 @@ 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)." +When a {% data variables.product.prodname_actions %} workflow run is requested or completed. Weitere Informationen findest Du unter "[Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#workflow_run)." #### Availability 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 new file mode 100644 index 0000000000..68ac147589 --- /dev/null +++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -0,0 +1,54 @@ +--- +title: About discussions +intro: Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About discussions + +With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools. + +- Share announcements and information, gather feedback, plan, and make decisions +- Ask questions, discuss and answer the questions, and mark the discussions as answered +- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows + +![Discussions tab for a repository](/assets/images/help/discussions/hero.png) + +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).“ + +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)." + +### About categories and formats for discussions + +{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %} + +For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %} + +For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +### Best practices for discussions + +As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)." + +Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." + +### Feedback teilen + +You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). + +### Weiterführende Informationen + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- „[Über Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" +- „[Kommentare und Unterhaltungen moderieren](/github/building-a-strong-community/moderating-comments-and-conversations)“ +- „[Deine Sicherheit auf {% data variables.product.prodname_dotcom %} aufrechterhalten](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md new file mode 100644 index 0000000000..10d84f58f7 --- /dev/null +++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -0,0 +1,48 @@ +--- +title: Collaborating with maintainers using discussions +shortTitle: Collaborating with maintainers +intro: You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion. +permissions: People with read permissions to a repository can start and participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About collaboration with maintainers using discussions + +{% data reusables.discussions.about-discussions %} If you use or contribute to a project, you can start a discussion to make suggestions and engage with maintainers and community members about your plans, questions, ideas, and feedback. For more information, see "[‎About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +{% data reusables.discussions.about-categories-and-formats %} Repository administrators and project maintainers can delete a discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)." + +{% data reusables.discussions.github-recognizes-members %} These members appear in a list of the most helpful contributors to the project's discussions. As your project grows, you can grant higher access permissions to active members of your community. For more information, see "[Granting higher permissions to top contributors](/discussions/guides/granting-higher-permissions-to-top-contributors)" + +![Most helpful contributors to discussions for a project](/assets/images/help/discussions/most-helpful.png) + +For more information about participation in discussions, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +### Vorrausetzungen + +To collaborate with maintainers using discussions, a repository administrator or project maintainer must enable discussions for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Starting a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Filtering the list of discussions + +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the **Search all discussions** field, type a search query. Optionally, to the right of the search field, click a button to further filter the results. ![Search bar and buttons for filtering discussions](/assets/images/help/discussions/search-and-filter-controls.png) +1. In the list of discussions, click the discussion you want to view. ![Discussion search results](/assets/images/help/discussions/search-result.png) + +### Converting an issue to a discussion + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)." + +### Weiterführende Informationen + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- „[Deine Sicherheit auf {% data variables.product.prodname_dotcom %} aufrechterhalten](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/index.md new file mode 100644 index 0000000000..44aed03c8b --- /dev/null +++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/index.md @@ -0,0 +1,14 @@ +--- +title: Collaborating with your community using discussions +shortTitle: Collaborating using discussions +intro: Gather and discuss your project with community members and other maintainers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /about-discussions %} +{% link_in_list /participating-in-a-discussion %} +{% link_in_list /collaborating-with-maintainers-using-discussions %} + diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md new file mode 100644 index 0000000000..1652438725 --- /dev/null +++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -0,0 +1,31 @@ +--- +title: Participating in a discussion +intro: You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}. +permissions: People with read permissions to a repository can participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About participation in a discussion + +{% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)." + +You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)." + +### Vorrausetzungen + +Discussions must be enabled for the repository for you to participate in a discussion in the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Creating a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Marking a comment as an answer + +Discussion authors and users with the triage role or greater for a repository can mark a comment as the answer to a discussion in the repository. + +{% data reusables.discussions.marking-a-comment-as-an-answer %} 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 new file mode 100644 index 0000000000..32da707aef --- /dev/null +++ b/translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -0,0 +1,49 @@ +--- +title: Best practices for community conversations on GitHub +shortTitle: Best practices for community conversations +intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to a discussion when you are ready to scope out the work.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Community conversations in {% data variables.product.prodname_discussions %} + +Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository and gather diverse feedback and ideas more quickly. You can help drive a productive conversation by: + +- Asking pointed questions and follow-up questions to garner specific feedback +- Capture a diverse experience and distill it down to main points +- Open an issue to take action based on the conversation, where applicable + +For more information about opening an issue and cross-referencing a discussion, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." + +### Learning about conversations on GitHub + +You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have. + +You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and spike out a project's specific details before committing it to an issue, which can then be scoped. Discussions are useful for teams if: +- You are in the discovery phase of a project and are still learning which director your team wants to go in +- You want to collect feedback from a wider community about a project +- You want to keep bug fixes, feature requests, and general conversations separate + +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](/articles/about-team-discussions).“ + +### Following contributing guidelines + +Before you open a discussion, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project. + +Weitere Informationen findest Du unter „[Dein Projekt für förderliche Beiträge einrichten](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Nächste Schritte: + +To continue learning about {% data variables.product.prodname_discussions %} and quickly create a discussion for your community, see "[Quickstart for {% data variables.product.prodname_discussions %}](/discussions/quickstart)." + +### Weiterführende Informationen + +- „[Dein Projekt für sinnvolle Beiträge einrichten](/articles/setting-up-your-project-for-healthy-contributions)“ +- „[Vorlagen benutzen, um hilfreiche Issues und Pull Requests zu ermutigen](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- „[Kommentare und Unterhaltungen moderieren](/articles/moderating-comments-and-conversations)“ +- „[Auf {% data variables.product.prodname_dotcom %} schreiben](/articles/writing-on-github)“ diff --git a/translations/de-DE/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/de-DE/content/discussions/guides/finding-discussions-across-multiple-repositories.md new file mode 100644 index 0000000000..6bdc994c1d --- /dev/null +++ b/translations/de-DE/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -0,0 +1,20 @@ +--- +title: Finding discussions across multiple repositories +intro: 'You can easily access every discussion you''ve created or participated in across multiple repositories.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Finding discussions + +1. Navigieren Sie zu {% data variables.product.prodname_dotcom_the_website %} +1. In the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your discussions**. !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. + +### Weiterführende Informationen + +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" 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 new file mode 100644 index 0000000000..1ed259dc09 --- /dev/null +++ b/translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -0,0 +1,32 @@ +--- +title: Granting higher permissions to top contributors +intro: 'Repository administrators can promote any community member to a moderator and maintainer.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Einführung + +The most helpful contributors for the past 30 days are highlighted on the {% data variables.product.prodname_discussions %} dashboard, based on how many comments were marked as answers by other community members. Helpful contributors can help drive a healthy community and moderate and guide the community space in addition to maintainers. + +### Step 1: Audit your discussions top contributors + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Compare the list of contributors with their access permissions to see who qualifies to moderate the discussion. + +### Step 2: Review permission levels for discussions + +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)." + +### Step 3: Change permissions levels for top contributors + +You can change a contributor's permission levels to give them more access to the tooling they need to moderate GitHub Discussions. To change a person's or team's permission levels, see "[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)." + +### Step 4: Notify community members of elevated access + +When you change a collaborators permission level, they will receive a notification for the change. diff --git a/translations/de-DE/content/discussions/guides/index.md b/translations/de-DE/content/discussions/guides/index.md new file mode 100644 index 0000000000..21c1f11bf1 --- /dev/null +++ b/translations/de-DE/content/discussions/guides/index.md @@ -0,0 +1,31 @@ +--- +title: Discussions guides +shortTitle: Leitfäden +intro: 'Discover pathways to get started or learn best practices for participating or monitoring your community''s discussions.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Getting started with discussions + +{% link_in_list /about-discussions %} +{% link_in_list /best-practices-for-community-conversations-on-github %} +{% link_in_list /finding-discussions-across-multiple-repositories %} + +### Administering discussions + +{% link_in_list /granting-higher-permissions-to-top-contributors %} + + + + + diff --git a/translations/de-DE/content/discussions/index.md b/translations/de-DE/content/discussions/index.md new file mode 100644 index 0000000000..66dca4f270 --- /dev/null +++ b/translations/de-DE/content/discussions/index.md @@ -0,0 +1,55 @@ +--- +title: GitHub Discussions Documentation +beta_product: true +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.' +introLinks: + quickstart: /discussions/quickstart +featuredLinks: + guides: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + gettingStarted: + - /discussions/quickstart + guideCards: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + popular: + - /discussions/guides/granting-higher-permissions-to-top-contributors + - /discussions/guides/best-practices-for-community-conversations-on-github + - /discussions/guides/finding-discussions-across-multiple-repositories + - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions + - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository +product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +layout: product-landing +versions: + free-pro-team: '*' +--- + + + + + + + +{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} +{% if discussionsCommunityExamples %} +
+

Communities using discussions

+ +
+ {% 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" %} +
+
+{% endif %} diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md new file mode 100644 index 0000000000..8ccb2875b2 --- /dev/null +++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md @@ -0,0 +1,13 @@ +--- +title: Managing discussions for your community +shortTitle: Managing discussions +intro: 'You can enable and configure discussions for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /managing-discussions-in-your-repository %} +{% link_in_list /managing-categories-for-discussions-in-your-repository %} +{% link_in_list /moderating-discussions %} diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md new file mode 100644 index 0000000000..943fec9924 --- /dev/null +++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md @@ -0,0 +1,56 @@ +--- +title: Managing categories for discussions in your repository +intro: You can categorize the discussions in your repository to organize conversations for your community members, and you can choose a format for each category. +permissions: Repository administrators and people with write or greater access to a repository can enable discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About categories for discussions + +{% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} + +Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations.{% data reusables.discussions.repository-category-limit %} + +For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +### Default categories + +| Kategorie | Purpose | Typ | +|:--------------- |:-------------------------------------------------------------------- |:--------------------- | +| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion | +| 💡Ideas | Ideas to change or improve the project | Open-ended discussion | +| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer | +| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion | + +### Creating a category + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.edit-categories %} +1. Click **New category**. !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png) +1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png) +1. Klicke auf **Create** (Erstellen). !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png) + +### Editing a category + +You can edit a category to change the category's emoji, title, description, and discussion format. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} +![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png) +1. Klicke auf **Save changes** (Änderungen speichern). !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +### Deleting a category + +When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png) +1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png) +1. Click **Delete & Move**. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png) 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 new file mode 100644 index 0000000000..e552242986 --- /dev/null +++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -0,0 +1,94 @@ +--- +title: Managing discussions in your repository +intro: You can categorize, spotlight, transfer, or delete the discussions in a repository. +permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About management of discussions + +{% 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)." + +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](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)." + +For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/github/building-a-strong-community/moderating-comments-and-conversations)." + +### Vorrausetzungen + +To manage discussions in a repository, discussions must be enabled for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Changing the category for a discussion + +You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" article. + +You can also move a discussion to a different category. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) + +### Pinning a discussion + +You can pin up to four important discussions above the list of discussions for the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png) +1. Optionally, customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Editing a pinned discussion + +Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Unpinning a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) +1. Read the warning, then click **Unpin discussion**. !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png) + +### Transferring a discussion + +To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png) +1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Click **Transfer discussion**. !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png) + +### Deleting a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png) +1. Read the warning, then click **Delete this discussion**. !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) + +### Converting issues based on labels + +You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Next to the label you want to convert to issues, click **Convert issues**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md new file mode 100644 index 0000000000..2c91d32d89 --- /dev/null +++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -0,0 +1,39 @@ +--- +title: Moderating discussions +intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, and converting issues to discussions. and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct to discussions.' +permissions: People with triage access to a repository can moderate discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About moderating discussions + +{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you 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. + +### Marking a comment as an answer + +{% data reusables.discussions.marking-a-comment-as-an-answer %} + +### Locking discussions + +It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository will still be able to comment on the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the discussion you want to lock. ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the right margin of a discussion, click **Lock conversation**. +1. Read the information about locking conversations and click **Lock conversation on this discussion**. +1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**. + +### Converting an issue to a discussion + +When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository can bulk convert issues based on labels. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to convert. +1. In the right margin of an issue, click **Convert to discussion**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/de-DE/content/discussions/quickstart.md b/translations/de-DE/content/discussions/quickstart.md new file mode 100644 index 0000000000..47ab3f8c73 --- /dev/null +++ b/translations/de-DE/content/discussions/quickstart.md @@ -0,0 +1,58 @@ +--- +title: Quickstart for GitHub Discussions +intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository and start conversations with your community.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Einführung + +{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike issues. Discussions enable fluid, open conversation in a public forum. + +Discussions give a space for more collaborative conversations by connecting and giving a more centralized area to connect and find information. + +### Enabling {% data variables.product.prodname_discussions %} on your repository + +Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public repositories. + +When you first enable a {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. + +{% data reusables.repositories.navigate-to-repo %} +1. Klicke unter Deinem Repository-Namen auf {% octicon "gear" aria-label="The gear icon" %} **Settings** (Einstellungen). ![Public settings button](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", click **Set up discussions**. ![Set up a discussion button under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png) +1. Under "Start a new discussion," edit the template to align with the resources and tone you want to set for your community. +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) + +### Welcoming contributions to your discussions + +You can welcome your community and introduce a new way to communicate in a repository by creating a welcome post and pin the post to your {% data variables.product.prodname_discussions %} page. Pinning and locking discussions helps people know that a post is meant as an announcement. You can use announcements as a way to link people to more resources and offer guidance for opening discussions in your community. For more information about pinning a discussion, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + + +### Setting up community guidelines for contributors + +You can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. You can also update the repository's README to communicate expectations on when collaborators should open an issue or discussion. + +For more information about providing guidelines for your project, see "[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and "[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Creating a new discussion + +Anyone with access to a repository can create a discussion. + +{% data reusables.discussions.starting-a-discussion %} + +### Organizing discussions into relevant categories + +Repository owners and people with write access can create new categories to keep discussions organized. Collaborators participating and creating new discussions can group discussions into the most relevant existing categories. Discussions can also be recategorized after they are created. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" + +### Promoting healthy conversations + +People with write permissions for a repository can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +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)." + +### Nächste Schritte: + +Once there is a clear path to scope work out and move an idea from concept to reality, you can create an issue and start tracking your progress. For more information on creating an issue from a discussion, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." diff --git a/translations/de-DE/content/education/guides.md b/translations/de-DE/content/education/guides.md new file mode 100644 index 0000000000..45263ae4da --- /dev/null +++ b/translations/de-DE/content/education/guides.md @@ -0,0 +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 +versions: + free-pro-team: '*' +--- + +### Get started with {% 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. + +- [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/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) + +### Run a software development course with {% 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 %}. + +- [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) + +### Learn to develop software + +Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. + +- [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/teach-and-learn-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) + +### Contribute to the community + +Participate in the community, get training from {% data variables.product.company_short %}, and learn or teach new skills. + +- [{% data variables.product.prodname_education_community %}](https://education.github.community) +- [Informationen zu Campus Experts](/education/teach-and-learn-with-github-education/about-campus-experts) +- [Informationen zu Campus Advisors](/education/teach-and-learn-with-github-education/about-campus-advisors) diff --git a/translations/de-DE/content/education/index.md b/translations/de-DE/content/education/index.md new file mode 100644 index 0000000000..c3827df288 --- /dev/null +++ b/translations/de-DE/content/education/index.md @@ -0,0 +1,45 @@ +--- +title: GitHub Education Documentation +shortTitle: Education +intro: "{% data variables.product.prodname_education %} helps you teach or learn software development with the tools and support of {% data variables.product.company_short %}'s platform and community." +introLinks: + quickstart: /education/quickstart +featuredLinks: + guides: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + guideCards: + - /github/getting-started-with-github/signing-up-for-a-new-github-account + - /github/getting-started-with-github/git-and-github-learning-resources + - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom + popular: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /desktop + - /github/getting-started-with-github/github-cli + - /education/manage-coursework-with-github-classroom/teach-with-github-classroom +changelog: + - + title: 'Try something new at Local Hack Day: Learn' + date: '2020-10-15' + href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ + - + title: 'Remote Education: Creating community through shared experiences' + date: '2020-09-24' + href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ + - + title: 'Remote Education: A series of best practices for online campus communities' + date: '2020-09-10' + href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ + - + title: Welcome to the inaugural class of MLH Fellows + date: '2020-06-24' + href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ +layout: product-landing +versions: + free-pro-team: '*' +--- + + + diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md new file mode 100644 index 0000000000..4785781a1e --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -0,0 +1,31 @@ +--- +title: About using MakeCode Arcade with GitHub Classroom +shortTitle: About using MakeCode Arcade +intro: You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-makecode +--- + +### About MakeCode Arcade + +MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade. + +For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. + +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. + +### About submission of assignments with MakeCode Arcade + +By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.product.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen. + +![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) + +### Weiterführende Informationen + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md new file mode 100644 index 0000000000..b33557b66e --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: About using Repl.it with GitHub Classroom +shortTitle: About using Repl.it +intro: You can configure Repl.it as the online integrated development environment (IDE) for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-replit +--- + +### About Repl.it + +Repl.it is an online integrated development environment (IDE) that supports multiple programming languages. Students can write, edit, run, test, and debug code in a browser with Repl.it. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. + +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). + +For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. + +### About submission of assignments with Repl.it + +By default, Repl.it is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with Repl.it, students should push changes to {% data variables.product.product_location %} using the version control functionality in the left sidebar. + +![Repl.it version control functionality](/assets/images/help/classroom/ide-replit-version-control-button.png) + +For more information about using Git on Repl.it, see the [Repl.it + Git Tutorial](https://repl.it/talk/learn/Replit-Git-Tutorial/23331) on the Repl.it website. + +### Weiterführende Informationen + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md new file mode 100644 index 0000000000..5454736d9c --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: Basics of setting up GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %} basics' +intro: Learn how to set up your classroom, manage assignments, and configure time-saving automation. +versions: + free-pro-team: '*' +--- + +### Videos about {% data variables.product.prodname_classroom %} + +You can watch a series of short video tutorials about the configuration and use of {% data variables.product.prodname_classroom %}. To watch all videos as part of a continuous playlist, see the [{% data variables.product.prodname_classroom %} Getting Started Guide](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) on YouTube. + +For more information about terminology for {% data variables.product.prodname_classroom %}, see "[Glossary](/education/manage-coursework-with-github-classroom/glossary)". + +1. Getting started {% octicon "link-external" aria-label="The external link icon" %} +2. Adding your student roster {% octicon "link-external" aria-label="The external link icon" %} +3. Creating assignments + - Creating an assignment using a {% data variables.product.prodname_dotcom %} repository {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Microsoft MakeCode as your online IDE {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Repl.it as your online IDE {% octicon "link-external" aria-label="The external link icon" %} +4. How students complete assignments {% octicon "link-external" aria-label="The external link icon" %} +5. How teachers review assignments {% octicon "link-external" aria-label="The external link icon" %} +6. Creating group assignments {% octicon "link-external" aria-label="The external link icon" %} +7. Next steps to get started {% octicon "link-external" aria-label="The external link icon" %} +8. {% data variables.product.prodname_dotcom %} Teacher Toolbox {% octicon "link-external" aria-label="The external link icon" %} + +### Nächste Schritte: + +For more information about teaching with {% data variables.product.prodname_classroom %}, see "[Teach with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom)." + +### Weiterführende Informationen + +- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md new file mode 100644 index 0000000000..64438c15c4 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md @@ -0,0 +1,50 @@ +--- +title: Configure default settings for assignment repositories +shortTitle: Configure defaults for assignment repositories +intro: You can use the Probot Settings app to configure the default settings for repositories that {% data variables.product.prodname_classroom %} creates for an assignment. +permissions: Organization owners can configure default settings for assignment repositories by installing a {% data variables.product.prodname_github_app %} for the organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/probot-settings +--- + +### About configuration of defaults for assignment repositories + +{% data variables.product.prodname_classroom %} creates a repository that belongs for each student or team that accepts an assignment. The repository belongs to the organization that you use for {% data variables.product.prodname_classroom %}. Assignment repositories can be empty, or you can use a template repository. For more information, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} + +With the Probot Settings app, you can create a file named _.github/settings.yml_ in a repository that contains a list of settings for the repository, and then install a {% data variables.product.prodname_github_app %} for your organization that automatically applies the settings to the repository. + +You can include _.github/settings.yml_ in a template repository that you use for an assignment in {% data variables.product.prodname_classroom %}. When an individual or team accepts the assignment, {% data variables.product.prodname_classroom %} creates the assignment repository, and the Settings app automatically applies the settings from _.github/settings.yml_. + +Probot is a a project, framework, and collection of free apps to automate {% data variables.product.product_name %}. A Probot app can listen to repository events, like the creation of new commits, comments, and issues, and automatically respond to the event. + +For more information, see the [Probot website](https://probot.github.io) and the [Settings app website](https://probot.github.io/apps/settings/). For more information about {% data variables.product.prodname_github_apps %}, see "[About apps](/developers/apps/about-apps)." + +### Adding the Settings app to your organization + +After you install the Probot Settings app for your organization, the app will apply the settings that you define in _.github/settings.yml_ for any repository in your organization, including new assignment repositories that {% data variables.product.prodname_classroom %} creates. + +1. Navigate to the [Settings app page](https://github.com/apps/settings). +1. Click **Install**, then click the organization that you use for {% data variables.product.prodname_classroom %}. Provide the app full access to all repositories owned by the organization. ![Installing the Probot Settings app](/assets/images/help/classroom/probot-settings.gif) + +### Configuring default settings for an assignment repository + +1. Create a template repository that contains a _.github/settings.yml_ file. For a complete list of settings, see the [README](https://github.com/probot/settings#github-settings) for the `probot/settings` repository. For more information about using a template repository for starter code in {% data variables.product.prodname_classroom %}, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + + {% warning %} + + **Warning:** Do not define `collaborators` in the _.github/settings.yml_ file for your template repository. {% data variables.product.prodname_classroom %} automatically grants teachers and teaching assistants access to assignment repositories. + + {% endwarning %} + +1. Create an assignment using the template repository containing _.github/settings.yml_ as the starter code. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +The Probot Settings app for your organization will now apply the settings you define in _.github/settings.yml_ within the template repository to every assignment repository that {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} creates for a student or team. + +### Weiterführende Informationen + +- [Probot apps](https://probot.github.io/apps/) +- [Probot documentation](https://probot.github.io/docs/) diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md new file mode 100644 index 0000000000..137d13116b --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -0,0 +1,138 @@ +--- +title: Connect a learning management system to GitHub Classroom +intro: You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom + - /education/manage-coursework-with-github-classroom/connect-to-lms + - /education/manage-coursework-with-github-classroom/generate-lms-credentials + - /education/manage-coursework-with-github-classroom/setup-canvas + - /education/manage-coursework-with-github-classroom/setup-generic-lms + - /education/manage-coursework-with-github-classroom/setup-moodle +--- + +### About configuration of your LMS + +You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS. + +### Vorrausetzungen + +To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)." + +### Supported LMSes + +{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards. + +- LTI version 1.0 and/or 1.1 +- LTI Names and Roles Provisioning 1.X + +Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website. + +{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. + +- Canvas +- Google Classroom +- Moodle +- Sakai + +Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace + +### Generating configuration credentials for your classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster. + - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)." +1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**. ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. Read about connecting your LMS, then click **Connect to _LMS_**. +1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom. ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png) + +### Configuring a generic LMS + +You must configure the privacy settings for your LMS to allow external tools to receive roster information. + +1. Navigate to your LMS. +1. Configure an external tool. +1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}. + - Consumer key + - Shared secret + - Launch URL (sometimes called "tool URL" or similar) + +### Configuring Canvas + +You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). + +1. Sign into [Canvas](https://www.instructure.com/canvas/#login). +1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}. +1. Klicke auf der linken Seitenleiste auf **Settings** (Einstellungen). +1. Click the **Apps** tab. +1. Click **View app configurations**. +1. Click **+App**. +1. Select the **Configuration Type** drop-down menu, and click **By URL**. +1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Canvas app configuration | Value or setting | + |:------------------------------------------------------------------------- |:------------------------------------------------------------------ | + | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} + | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled | + | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} + + {% note %} + + **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website. + + {% endnote %} + +1. Klicke auf **Submit** (Einreichen). +1. In the left sidebar, click **Home**. +1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}. + +### Configuring Moodle + +You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org). + +You must be using Moodle version 3.0 or greater. + +1. Sign into [Moodle](https://moodle.org/login/index.php). +1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}. +1. Click **Turn editing on**. +1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**. +1. Choose **External tool** and click **Add**. +1. In the "Activity name" field, type "GitHub Classroom". +1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**. +1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Moodle app configuration | Value or setting | + |:--------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_

**Note**: You can use any name, but we suggest this value for clarity. | + | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} + | **LTI version** | LTI 1.0/1.1 | + | **Default launch container** | New window | + | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} + +1. Scroll to and click **Services**. +1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**. +1. Scroll to and click **Privacy**. +1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**. +1. Klicke am Ende der Seite auf **Save changes** (Änderungen speichern). +1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**. +1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**. +1. At the bottom of the page, click **Save and return to course**. +1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity. + +### Importing a roster from your LMS + +For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + +### Disconnecting your LMS + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Connect to a learning management system (LMS)", click **Connection Settings**. !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**. !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) 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 new file mode 100644 index 0000000000..5bc887c1c7 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -0,0 +1,145 @@ +--- +title: Create a group assignment +intro: 'You can create a collaborative assignment for teams of students who participate in your course.' +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/create-group-assignments +--- + +### About group assignments + +{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers. + +When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment. + +{% data reusables.classroom.classroom-creates-group-repositories %} + +{% data reusables.classroom.about-assignments %} + +You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. Weitere Informationen finden Sie unter „[Informationen zu Teams](/github/setting-up-and-managing-organizations-and-teams/about-teams)“. + +For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### Vorrausetzungen + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Defining teams for an assignment](#defining-teams-for-an-assignment) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +#### Defining teams for an assignment + +If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams. + +{% tip %} + +**Tips**: + +- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course. + +- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members. + +{% endtip %} + +![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png) + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +### Providing feedback + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the team. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
+ Group assignment +
+ +### Nächste Schritte: + +- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. + +- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### Weiterführende Informationen + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md new file mode 100644 index 0000000000..76cef7d653 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -0,0 +1,19 @@ +--- +title: Create an assignment from a template repository +intro: You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments +--- + +You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. Weitere Informationen findest Du unter „[Repository-Vorlage erstellen](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository).“ + +To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." + +### Weiterführende Informationen + +- "[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)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md new file mode 100644 index 0000000000..b44f0c64fa --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -0,0 +1,124 @@ +--- +title: Create an individual assignment +intro: You can create an assignment for students in your course to complete individually. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment + - /education/manage-coursework-with-github-classroom/create-an-individual-assignment +--- + +### About individual assignments + +{% data reusables.classroom.assignments-individual-definition %} + +{% data reusables.classroom.classroom-creates-individual-repositories %} + +{% data reusables.classroom.about-assignments %} + +For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### Vorrausetzungen + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +### Providing feedback for an assignment + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the student. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
+ Individual assignment +
+ +### Nächste Schritte: + +- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." + +- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### Weiterführende Informationen + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md new file mode 100644 index 0000000000..8bf6925a00 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md @@ -0,0 +1,9 @@ +--- +title: Get started with GitHub Classroom +shortTitle: Erste Schritte +intro: Learn how to configure and use {% data variables.product.prodname_classroom %} to administer your course. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/glossary.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/glossary.md new file mode 100644 index 0000000000..cc67ca1166 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/glossary.md @@ -0,0 +1,52 @@ +--- +title: Glossar +intro: You can review explanations of terminology for {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +--- + +### abtretung + +An assignment is coursework in {% data variables.product.prodname_classroom %}. A teacher can assign an assignment to an individual student or a group of students. Teachers can import starter code for the assignment, assign students, and create a deadline for each assignment. For more information, see the definitions for "[individual assignment](#individual-assignment)" and "[group assignment](#group-assignment)." + +--- + +### classroom + +A classroom is the basic unit of {% data variables.product.prodname_classroom %}. Teachers can use a classroom to organize and manage students, teaching assistants, and assignments for a single course. A classroom belongs to an organization on {% data variables.product.prodname_dotcom_the_website %}. To administer a classroom, you must be an organization owner for the organization on {% data variables.product.prodname_dotcom %}. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." + +--- + +### {% data variables.product.prodname_classroom %} + +{% data variables.product.prodname_classroom %} is a web application for educators that provides course administration tools integrated with {% data variables.product.prodname_dotcom %}. For more information, see the [{% data variables.product.prodname_classroom %}](https://classroom.github.com/) website. + +--- + +### group assignment + +{% data reusables.classroom.assignments-group-definition %} For more information, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +--- + +### identifier + +An identifier in {% data variables.product.prodname_classroom %} is a unique ID for a student participating in a course. For example, an identifier can be a student name, alphanumeric ID, or email address. + +--- + +### individual assignment + +{% data reusables.classroom.assignments-individual-definition %} For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +--- + +### roster + +A roster allows a teacher to manage students and assignment submissions in a classroom on {% data variables.product.prodname_classroom %}. Teachers can create a roster by entering a list of student identifiers, or by connecting {% data variables.product.prodname_classroom %} to a learning management system (LMS). For more information about identifiers, see the definition of "[identifier](#identifier)." For more information about connecting {% data variables.product.prodname_classroom %} to an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + +--- + +### Weiterführende Informationen + +- „[{% data variables.product.prodname_dotcom %}-Glossar](/github/getting-started-with-github/github-glossary)“ diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md new file mode 100644 index 0000000000..72fbf280b2 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md @@ -0,0 +1,32 @@ +--- +title: Manage coursework with GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %}' +intro: With {% data variables.product.prodname_classroom %}, you can use {% data variables.product.product_name %} to administer or participate in a course about software development. +versions: + free-pro-team: '*' +--- + +### Inhaltsverzeichnis + +{% topic_link_in_list /get-started-with-github-classroom %} + {% link_in_list /basics-of-setting-up-github-classroom %} + {% link_in_list /glossary %} + +{% topic_link_in_list /teach-with-github-classroom %} + {% link_in_list /manage-classrooms %} + {% link_in_list /create-an-individual-assignment %} + {% link_in_list /create-a-group-assignment %} + {% link_in_list /create-an-assignment-from-a-template-repository %} + {% link_in_list /leave-feedback-with-pull-requests %} + {% link_in_list /use-autograding %} + {% link_in_list /configure-default-settings-for-assignment-repositories %} + {% link_in_list /connect-a-learning-management-system-to-github-classroom %} + +{% topic_link_in_list /integrate-github-classroom-with-an-ide %} + {% link_in_list /integrate-github-classroom-with-an-online-ide %} + {% link_in_list /about-using-makecode-arcade-with-github-classroom %} + {% link_in_list /about-using-replit-with-github-classroom %} + {% link_in_list /run-student-code-in-an-online-ide %} + +{% topic_link_in_list /learn-with-github-classroom %} + {% link_in_list /view-autograding-results %} diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md new file mode 100644 index 0000000000..f4245ea672 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md @@ -0,0 +1,9 @@ +--- +title: Integrate GitHub Classroom with an IDE +shortTitle: Integrate with an IDE +intro: You can help your students write, test, and debug code by preconfiguring a development environment for assignment repositories on {% data variables.product.prodname_classroom %}. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md new file mode 100644 index 0000000000..7f49bd453c --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md @@ -0,0 +1,42 @@ +--- +title: Integrate GitHub Classroom with an online IDE +shortTitle: Integrate with an online IDE +intro: You can preconfigure a supported online integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/online-ide-integrations +--- + +### About integration with an online IDE + +{% data reusables.classroom.about-online-ides %} + +After a student accepts an assignment with an online IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary. + +![Button for online IDE in README.md for assignment repository](/assets/images/help/classroom/assignment-repository-ide-button-in-readme.png) + +### Supported online IDEs + +{% data variables.product.prodname_classroom %} supports the following online IDEs. You can learn more about the student experience for each IDE. + +| IDE | Weitere Informationen | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | +| Repl.it | "[About using Repl.it with GitHub Classroom](/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom)" | + +### Configuring an online IDE for an assignment + +You can choose the online IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an online IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Authorizing the OAuth app for an online IDE + +The first time you configure an assignment with an online IDE, you must authorize the OAuth app for the online IDE for your organization. + +!["Go grant access" button in popover for authorizing OAuth app for online IDE](/assets/images/help/classroom/assignment-ide-go-grant-access-button.png) + +For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." + +### Weiterführende Informationen + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md new file mode 100644 index 0000000000..bca1150346 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Learn with GitHub Classroom +intro: You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md new file mode 100644 index 0000000000..d4db1b9c1d --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md @@ -0,0 +1,31 @@ +--- +title: Leave feedback with pull requests +intro: You can leave feedback for your students in a special pull request within the repository for each assignment. +permissions: People with read permissions to a repository can leave feedback in a pull request for the repository. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github +--- + +### About feedback pull requests for assignments + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +When you enable the pull request for feedback for an assignment, {% data variables.product.prodname_classroom %} will create a special pull request titled **Feedback** in the assignment repository for each student or team. The pull request automatically shows every commit that a student pushed to the assignment repository's default branch. + +### Vorrausetzungen + +To create and access the feedback pull request, you must enable the feedback pull request when you create the assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +### Leaving feedback in a pull request for an assignment + +{% data reusables.classroom.sign-into-github-classroom %} +1. In the list of classrooms, click the classroom with the assignment you want to review. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **Review**. ![Review button for assignment in list of submissions for an assignment](/assets/images/help/classroom/assignments-click-review-button.png) +1. Review the pull request. Weitere Informationen findest Du unter „[Einen Pull Request kommentieren](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)." + +### Weiterführende Informationen + +- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](http://localhost:4000/en/free-pro-team@latest/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" 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 new file mode 100644 index 0000000000..fe8fb67ade --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -0,0 +1,106 @@ +--- +title: Manage classrooms +intro: You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}. +permissions: Organization owners can manage a classroom for an organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/archive-a-classroom +--- + +### About classrooms + +{% data reusables.classroom.about-classrooms %} + +![Classroom](/assets/images/help/classroom/classroom-hero.png) + +### About management of classrooms + +{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. + +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 classrom. 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)." + +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. + +### About classroom rosters + +Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course. + +When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment. + +![Classroom roster](/assets/images/help/classroom/roster-hero.png) + +### 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 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)." + +### Creating a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **New classroom**. !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png) +{% data reusables.classroom.guide-create-new-classroom %} + +After you create a classroom, you can begin creating assignments for students. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Creating a roster for your classroom + +You can create a roster of the students who participate in your course. + +If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) +1. To create a roster manually, type your student identifiers. Optionally, click **Upload a CSV or text file** to upload a file containing the identifiers. ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png) +1. Click **Create roster**. !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png) + +### Adding students to the roster for your classroom + +Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classrom](#creating-a-roster-for-your-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To the right of "Classroom roster", click **Update students**. !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png) +1. Follow the instructions to add students to the roster. + - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**. ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) + +### Renaming a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Classroom name", type a new name for the classroom. ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png) +1. Click **Rename classroom**. !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png) + +### Archiving or unarchiving a classroom + +You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**. ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png) +1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**. ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) + +### Deleting a roster for a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Under "Delete this roster", click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png) +1. Read the warnings, then click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) + +### Deleting a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) +1. **Lies die Warnungen.**. +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md new file mode 100644 index 0000000000..57e3f1e824 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md @@ -0,0 +1,21 @@ +--- +title: Run student code in an online IDE +intro: You can run the code from a student assignment within the online integrated development environment (IDE) that you configured for the assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/running-student-code +--- + +### About student code and online IDEs + +If you configure an online integrated development environment (IDE) for an assignment, you can run the code within the online IDE. You don't need to clone the assignment repository to your computer. + +For more information about online IDEs, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +### Running student code in the online IDE + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **View IDE**. !["View IDE" button for submission using an online IDE](/assets/images/help/classroom/assignments-click-view-ide.png) diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md new file mode 100644 index 0000000000..6e051e9d2d --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Teach with GitHub Classroom +intro: Learn how to set up your classroom and assignments. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/use-autograding.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/use-autograding.md new file mode 100644 index 0000000000..cdb2039a70 --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/use-autograding.md @@ -0,0 +1,83 @@ +--- +title: Use autograding +intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers +--- + +### About autograding + +{% data reusables.classroom.about-autograding %} + +After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding. + +You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." + +You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment. + +![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png) + +### Grading methods + +There are two grading methods: input/output tests and run command tests. + +#### Input/output test + +An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result. + +| Einstellung | Beschreibung | +|:------------------- |:------------------------------------------------------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate standard output for evaluation | +| **Inputs** | Standard input for run command | +| **Expected output** | The output that you want to see as standard output from the run command | +| **Comparison** | The type of comparison between the run command's output and the expected output

  • **Included**: Passes when the expected output appears
    anywhere in the standard output from the run command
  • **Exact**: Passes when the expected output is completely identical
    to the standard output from the run command
  • **Regex**: Passes if the regular expression in expected
    output matches against the standard output from the run command
| +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +#### Run command test + +A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure. + +{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`. + +| Einstellung | Beschreibung | +|:----------------- |:------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate an exit code for evaluation | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +### Configuring autograding tests for an assignment + +You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests. + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.assignments-click-pencil %} +1. In the left sidebar, click **Grading and feedback**. !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) +1. Add, edit, or delete an autograding test. + - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png) +1. At the bottom of the page, click **Update assignment**. !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png) + +### Viewing logs from autograding tests + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of a submission, click **View test**. !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png) +1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)." + +### Weiterführende Informationen + +- [{% data variables.product.prodname_actions %} documentation](/actions) diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/view-autograding-results.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/view-autograding-results.md new file mode 100644 index 0000000000..8c407b4d5f --- /dev/null +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/view-autograding-results.md @@ -0,0 +1,30 @@ +--- +title: View autograding results +intro: You can see results from autograding within the repository for your assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students +--- + +### About autograding + +Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.product.product_location %}. + +If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X. + +### Viewing autograding results for an assignment repository + +{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." + +The **Actions** tab shows the full history of test runs. + +!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png) + +You can click a specific test run to review log output, like compilation errors and test failures. + +![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) + +### Weiterführende Informationen + +- „[Über Statuschecks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/de-DE/content/education/quickstart.md b/translations/de-DE/content/education/quickstart.md new file mode 100644 index 0000000000..b529f6f348 --- /dev/null +++ b/translations/de-DE/content/education/quickstart.md @@ -0,0 +1,87 @@ +--- +title: Quickstart for GitHub Educators +intro: In about 15 minutes, teachers can get started with discounts, training, and tools for {% data variables.product.company_short %}, then create a classroom for the students in a software development course using {% data variables.product.prodname_classroom %}. +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +### Einführung + +Educators who teach a course on software development can use discounts, partnerships, training, and tools from {% data variables.product.prodname_education %} to effectively teach relevant skills to students. + +In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}. + +{% tip %} + +**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Applying for a student developer pack](/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack)." + +{% endtip %} + +### Creating accounts on {% data variables.product.product_name %} + +First, you'll need to create a free user account on {% data variables.product.product_name %}. + +{% data reusables.accounts.create-account %} +1. Follow the prompts to create your free user account. + +After you create your user account, create a free organization account. You'll use this organization account to create and manage classrooms {% data variables.product.prodname_classroom %}. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Follow the prompts to create a free organization. + +For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." + +### Applying for an educator discount + +Next, you'll sign up for discounts on services from {% data variables.product.company_short %}. {% data reusables.education.educator-requirements %} + +{% tip %} + +**Tip** In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website. + +{% endtip %} + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Set up {% data variables.product.prodname_classroom %} + +With your user account and organization account, you're ready to get started with {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %} is free to use. You can track and manage assignments, grade work automatically, and provide feedback to your students. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To authorize {% data variables.product.prodname_classroom %} to access your user account on {% data variables.product.prodname_dotcom %}, review the information, then click **Authorize {% data variables.product.prodname_classroom %}**. !["Authorize {% data variables.product.prodname_classroom %}" button for user account](/assets/images/help/classroom/setup-click-authorize-github-classroom.png) +1. Review the information. To authorize {% data variables.product.prodname_classroom %} to access your organization account on {% data variables.product.prodname_dotcom %}, click **Grant**. !["Grant" button for organization](/assets/images/help/classroom/setup-click-grant.png) + + {% tip %} + + **Tip**: If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps#oauth-apps-and-organizations)." + + {% endtip %} + +1. Click **Authorize github**. ![Click "Authorize" button for organization](/assets/images/help/classroom/setup-click-authorize-github.png) + +### Create your classroom + +{% data reusables.classroom.about-classrooms %} + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **Create your first classroom** or **New classroom**. +{% data reusables.classroom.guide-create-new-classroom %} + +### Nächste Schritte: + +You've created a classroom, and you're ready to enrich your course with {% data variables.product.product_name %} and {% data variables.product.prodname_classroom %}! 🎉 + +- Watch some videos about {% data variables.product.prodname_classroom %}. For more information, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." +- Manage your classrooms and classroom admins, and create a roster of students for your classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." +- Create an assignment for individual students or teams. {% data reusables.classroom.for-more-information-about-assignment-creation %} +- Write and implement automated tests to provide immediate feedback to students directly in assignment repositories. For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." +- Participate in {% data variables.product.prodname_education_community_with_url %}. diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/about-campus-advisors.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..2b62ef8bb6 --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-campus-advisors.md @@ -0,0 +1,17 @@ +--- +title: Informationen zu Campus Advisors +intro: 'Lernen Sie als Instrukteur oder Mentor, {% data variables.product.prodname_dotcom %} an Ihrer Einrichtung mit Campus Advisors-Schulungen und -Support zu verwenden.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +Professoren, Lehrer und Mentoren können die Onlineschulungen von Campus Advisors nutzen, um den Umgang mit Git und {% data variables.product.prodname_dotcom %} sowie Best Practices für das Unterrichten von Studenten mit {% data variables.product.prodname_dotcom %} zu erlernen. Weitere Informationen findest Du unter „[Campus Advisors](https://education.github.com/teachers/advisors).“ + +{% note %} + +**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 %} diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/about-campus-experts.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..6fcec7a12c --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-campus-experts.md @@ -0,0 +1,11 @@ +--- +title: Informationen zu Campus Experts +intro: 'Erwirb Dir als Student mit Campus Experts-Schulungen für {% data variables.product.prodname_dotcom %} die notwendigen Fähigkeiten, um die Technologie-Community an Deiner Bildungseinrichtung sowie ein realistisches Portfolio aufzubauen.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +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).“ diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..26a4ac53c1 --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,31 @@ +--- +title: Informationen über GitHub Education für Lehrer und Forscher +intro: '{% data variables.product.prodname_education %} bietet eine Vielzahl von Tools, mit denen Lehrer und Forscher innerhalb und außerhalb des Unterrichts effektiver arbeiten können.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} für Lehrer + +Die Werkzeuge und Dienste von {% data variables.product.prodname_education %} für Lehrer aller Bildungsebenen ermöglichen Dir Folgendes: + - Verwende [{% data variables.product.prodname_classroom %}](https://classroom.github.com), um Code zu verteilen, Schülern und Studenten Feedback zu geben und Aufgaben auf {% data variables.product.prodname_dotcom %} einzusammeln. + - Tritt unserer [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) bei, um mit Deinen Kollegen aus der ganzen Welt über aktuelle Trends in der technologischen Bildung zu diskutieren. + - Greife auf unsere [Open-Source-Lehrpläne](https://education.github.community/t/open-source-lesson-plans/1591) zum Unterrichten von Git und {% data variables.product.prodname_dotcom %} zu und passe diese an. + - [Fordere eine {% data variables.product.prodname_dotcom %}-Tasche](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) mit Lehrmaterialien und Aufmerksamkeiten für Deine Schüler und Studenten an. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} für Forscher + +Die Werkzeuge und Dienste von {% data variables.product.prodname_education %} für Forscher ermöglichen Dir Folgendes: + - Arbeite weltweit auf {% data variables.product.prodname_dotcom %} mit anderen Personen gemeinsam an Deiner Forschungsarbeit. + - [Erfahre](https://education.github.com/stories), wie akademische Einrichtungen auf der ganzen Welt {% data variables.product.prodname_dotcom %} für ihre Forschung verwenden. + {% data reusables.education.apply-for-team %} + +### Weiterführende Informationen + +- „[Informationen zu {% data variables.product.prodname_education %} für Schüler und Studenten](/articles/about-github-education-for-students)“ diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..92c7773cfe --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md @@ -0,0 +1,21 @@ +--- +title: Informationen zu GitHub Education für Schüler und Studenten +intro: '{% data variables.product.prodname_education %} bietet Schülern und Studenten praktische Erfahrung mit kostenlosem Zugriff auf verschiedene Entwicklertools von Partnern von {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Die Verwendung von {% data variables.product.prodname_dotcom %} für Ihre Projektarbeiten ist ein praktischer Weg, um mit anderen zusammenzuarbeiten und ein Portfolio aufzubauen, das Ihre praktische Erfahrung zeigt. + +{% data reusables.education.about-github-education-link %} + +Jeder mit einem {% data variables.product.prodname_dotcom %}-Konto kann unbegrenzt in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_free_user %} zusammenarbeiten. Als Schüler oder Student können Sie auch das {% data variables.product.prodname_student_pack %} beantragen, das kostenlosen Zugriff auf Tools und Dienste bietet, die von professionellen Entwicklern verwendet werden. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +Wenn Sie Mitglied in einem FIRST Robotics Club sind, kann Ihr Lehrer einen Rabatt beantragen, damit Ihr Team mit {% data variables.product.prodname_team %} zusammenarbeiten kann, wodurch eine unbegrenzte Anzahl von Benutzern und privaten Repositorys kostenlos genutzt werden kann. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." + +### Weiterführende Informationen + +- „[Informationen zu {% data variables.product.prodname_education %} für Lehrer und Forscher](/articles/about-github-education-for-educators-and-researchers)“ diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education.md new file mode 100644 index 0000000000..7c0a1e20ce --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/about-github-education.md @@ -0,0 +1,23 @@ +--- +title: Informationen zu GitHub Education +intro: '{% data variables.product.prodname_education %} bietet ein spezielles kostenloses Produkt für Bildungseinrichtungen, die {% data variables.product.prodname_dotcom %} optimal für ihre Community nutzen möchten und den spezifischen Programmanforderungen zustimmen.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +Wenn Ihre Schule bestimmte Anforderungen erfüllt, kann Ihre weiterführende Schule, Ihre Universität oder Ihr Schülercamp {% data variables.product.prodname_education %} und damit das Beste von {% data variables.product.prodname_dotcom %} kostenlos nutzen, einschließlich +- {% data variables.product.prodname_ghe_cloud %} und/oder {% data variables.product.prodname_ghe_server %}, +- Lehrerschulung zur Beherrschung von Git und {% data variables.product.prodname_dotcom %} mit unserem Campus Advisors-Programm, +- automatisierter Zugriff auf die Premiumfunktionen von {% data variables.product.prodname_education %}, wie z. B. das {% data variables.product.prodname_student_pack %}, +- Schulungen für Schüler und Studenten mit dem Campus Experts-Programm zur Entwicklung von Leadership und technischer Kompetenz. + +Weitere Informationen findest Du auf der [offiziellen {% data variables.product.prodname_education %}-Seite](https://education.github.com/partners/schools). + +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)." + +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).“ + +Wenn Sie Schüler, Student oder Lehrkraft sind und Ihre Einrichtung nicht mit {% data variables.product.prodname_dotcom %} als {% data variables.product.prodname_education %}-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/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..f0d4370059 --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,53 @@ +--- +title: Apply for a student developer pack +intro: 'Studenten können das {% data variables.product.prodname_student_pack %} beantragen, das Angebote und Vorteile von {% data variables.product.prodname_dotcom %}-Partnern umfasst.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### Anforderungen + +Damit Du ein {% data variables.product.prodname_student_pack %} nutzen kannst, musst Du: +- Derzeit als Schüler oder Student in einer Einrichtung eingeschrieben sein, die einen Abschluss oder ein Diplom verleiht, beispielsweise ein Gymnasium, eine weiterführende Schule, eine Hochschule, eine Universität, eine Heimschule oder eine ähnliche Bildungseinrichtung, +- Eine überprüfbare E-Mail-Adresse einer Hochschule besitzen oder Dokumente hochladen, die Deinen aktuellen Status als Student bestätigen +- Ein [{% data variables.product.prodname_dotcom %}-Benutzerkonto](/articles/signing-up-for-a-new-github-account) besitzen, +- Mindestens 13 Jahre alt sein + +Zu den Dokumenten, die Deinen aktuellen Status als Schüler oder Student belegen, gehören ein Bild Deines Schulausweises, Deines Stundenplans und Deiner Zeugnisse sowie ein Schreiben zur Bestätigung der Mitgliedschaft oder Immatrikulation. + +Während Deiner Zeit als Student wirst Du möglicherweise dazu aufgefordert, in regelmäßigen Abständen Deinen aktuellen akademischen Status zu bestätigen. + +{% note %} + +**Hinweis:** Du kannst akademische Rabatte nicht von einem Konto zu einem anderen übertragen. Wenn Du den Rabatt auf mehrere Konten anwenden möchtest, kannst Du Deine Benutzerkonten [zusammenführen](/articles/merging-multiple-user-accounts) und das resultierende Konto [umbenennen](/articles/changing-your-github-username), falls gewünscht. + +{% endnote %} + +Weitere Informationen zum Verlängerung Ihres {% data variables.product.prodname_student_pack %}s finden Sie unter „[Ablauf und Verlängerungen](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)“. + +### Ein {% data variables.product.prodname_student_pack %} beantragen + +{% data reusables.education.benefits-page %} +3. Wähle unter „Which best describes your academic status?“ (Was beschreibt Deinen akademischen Status am besten?) **Student** aus. ![Akademischen Status auswählen](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Ablauf und Verlängerungen + +Wenn Ihr Zugriff auf das {% data variables.product.prodname_student_pack %} abgelaufen ist, können Sie ihn erneut beantragen, sofern Sie die Voraussetzungen weiterhin erfüllen. Einige unserer Partnerangebote können jedoch nicht verlängert werden. Die meisten zeitlich begrenzten Angebote unserer Partner beginnen unmittelbar nachdem Du sie eingerichtet hast. Weitere Informationen findest Du auf der [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)-Seite. + +Angaben dazu, wann Ihr kostenloser Zugriff auf das {% data variables.product.prodname_student_pack %} abläuft, finden Sie in den [Abrechnungseinstellungen](https://github.com/settings/billing) Ihres Kontos. + +### Weiterführende Informationen + +- „[Warum wurde mein Antrag für das {% data variables.product.prodname_student_pack %}s abgelehnt?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)“ +- „[Für ein neues {% data variables.product.prodname_dotcom %}-Konto anmelden](/articles/signing-up-for-a-new-github-account)“ +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..08165e1422 --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,57 @@ +--- +title: Apply for an educator or researcher discount +intro: 'Wenn Sie ein Lehrer oder Forscher sind, können Sie beantragen, {% data variables.product.prodname_team %} kostenlos für das Konto Ihrer Organisation zu erhalten.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### Informationen zu Lehrer- und Forscherrabatten + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### Einen Lehrer- oder Forscherrabatt beantragen + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Ein Upgrade Deiner Organisation durchführen + +Nachdem Dein Antrag für einen Lehrer- oder Forscherrabatt genehmigt wurde, kannst Du die von Dir mit Deiner Lerngemeinschaft benutzte Organisation auf {% data variables.product.prodname_team %} hochstufen, was die kostenlose Nutzung von unbegrenzten Benutzern und privaten Repositorys erlaubt. Du kannst eine vorhandene Organisation hochstufen oder eine neue Organisation für das Hochstufen erstellen. + +#### Hochstufen einer vorhandenen Organisation + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Hochstufen einer neuen Organisation + +{% data reusables.education.upgrade-page %} +1. Klicke auf {% octicon "plus" aria-label="The plus symbol" %} **Create an organization** (Erstelle eine Organisation). ![Schaltfläche „Create an organization“ (Eine Organisation erstellen)](/assets/images/help/education/create-org-button.png) +3. Lies die Informationen, dann klicke auf **Create organization** (Organisation erstellen). ![Schaltfläche „Create organization“ (Organisation erstellen)](/assets/images/help/education/create-organization-button.png) +4. Klicke unter "Choose your plan" (Wähle Deinen Plan), auf **Choose {% data variables.product.prodname_free_team %}** (Wähle Produkt). +5. Folge den Anweisungen, um Deine Organisation zu erstellen. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### Weiterführende Informationen + +- „[Warum wurde mein Antrag eines Lehrer- oder Forscherrabatts nicht genehmigt?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)“ +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %}-Videos](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/index.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/index.md new file mode 100644 index 0000000000..56260e46e2 --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Teach and learn +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Inhaltsverzeichnis + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..117b993cad --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub at your educational institution +intro: 'Maximieren Sie die Vorteile der Nutzung von {% data variables.product.prodname_dotcom %} in Ihrer Einrichtung für Ihre Studenten, Instrukteure und IT-Mitarbeiter mit {% data variables.product.prodname_education %} und unseren verschiedenen Schulungsprogrammen für Studenten und Instrukteure.' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..02877d7dcf --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub for your schoolwork +intro: 'Schüler und Studenten können {% data variables.product.prodname_dotcom %} verwenden, um an Schulprojekten zusammenzuarbeiten und erste praktische Erfahrung aufzubauen.' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..fc0ccbe7fa --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub in your classroom and research +intro: 'Lehrer oder Forscher können {% data variables.product.prodname_dotcom %} für die Zusammenarbeit im Klassenraum, in der Studenten- oder Forschungsgruppe usw. verwenden.' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..fcb92caa95 --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,67 @@ +--- +title: Warum wurde mein Antrag für das Studentenentwicklungspaket abgelehnt? +intro: 'Lies die generellen Gründe, weshalb Anträge für das {% data variables.product.prodname_student_pack %} nicht genehmigt werden, und Tipps, um die erneute Bewerbung erfolgreich zu gestalten.' +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved + - /articles/why-was-my-application-for-a-student-developer-pack-denied/ + - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved + - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tipp:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unklare Dokumente zur akademischen Zugehörigkeit + +Wenn anhand des von Dir hochgeladenen Bildes Dein aktueller akademischer Status nicht eindeutig identifiziert werden kann, fordern wir einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Akademische E-Mail-Adresse mit einer nicht verifizierten Domäne verwenden + +Wenn Deine akademische E-Mail-Adresse eine nicht verifizierte Domäne aufweist, fordern wir einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Akademische E-Mail-Adresse von einer Bildungseinrichtung mit lockeren E-Mail-Richtlinien verwenden + +Wenn Deine Bildungseinrichtung E-Mail-Adressen vor der bezahlten Studentenregistrierung ausstellt, fordern wir einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +Bei anderen Fragen oder Bedenken zur Domäne der Bildungseinrichtung solltest Du das IT-Personal Deiner Bildungseinrichtung bitten, uns zu kontaktieren. + +### Akademische E-Mail-Adresse wird bereits verwendet + +Wenn Deine akademische E-Mail-Adresse bereits verwendet wurde, um ein {% data variables.product.prodname_student_pack %} für ein anderes {% data variables.product.prodname_dotcom %}-Konto anzufordern, kannst Du die akademische E-Mail-Adresse bis zum Ablauf des entsprechenden Rabatts nicht erneut verwenden, um Dich erfolgreich für ein anderes {% data variables.product.prodname_student_pack %} zu bewerben. + +{% note %} + +**Hinweis:** Es verstößt gegen die {% data variables.product.prodname_dotcom %}-[Nutzungsbedingungen](/articles/github-terms-of-service/#3-account-requirements), mehr als ein persönliches Konto zu verwenden. + +{% endnote %} + +Falls Du über mehrere persönliche Konten verfügst, musst Du Deine Konten zusammenführen. Um den Rabatt zu erhalten, solltest Du das Konto beibehalten, für das der Rabatt gewährt wurde. Du kannst das beibehaltene Konto umbenennen und Deinen Beitragsverlauf beibehalten. Füge dem beibehaltenen Konto dazu alle Deine E-Mail-Adressen hinzu. + +Weitere Informationen findest Du unter: +- „[Mehrere Benutzerkonten zusammenführen](/articles/merging-multiple-user-accounts)“ +- „[Deinen {% data variables.product.prodname_dotcom %}-Benutzernamen ändern](/articles/changing-your-github-username)“ +- „[E-Mail-Adresse zu Deinem {% data variables.product.prodname_dotcom %}-Konto hinzufügen](/articles/adding-an-email-address-to-your-github-account)“ + +### 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. +- 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. + +### Weiterführende Informationen + +- „[Ein Studentenentwicklungspaket beantragen](/articles/applying-for-a-student-developer-pack)“ +- "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/de-DE/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/de-DE/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..f476fa7db5 --- /dev/null +++ b/translations/de-DE/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,45 @@ +--- +title: Warum wurde mein Antrag auf einen Lehrer- oder Forscherrabatt nicht genehmigt? +intro: Lies die generellen Gründe durch, weshalb Bewerbungen für einen Lehrer- oder Forscherrabatt nicht genehmigt werden, und die Tipps, um die erneute Bewerbung erfolgreich zu gestalten. +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tipp:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unklare Zugehörigkeitsnachweisdokumente + +Falls das von Dir hochgeladene Bild Deine aktuelle Beschäftigung an einer Schule oder Universität nicht zweifelsfrei belegt, musst Du Dich erneut bewerben und ein anderes Bild Deiner Fakultäts-ID oder einen Beschäftigungsnachweis mit eindeutigen Informationen hochladen. + +{% data reusables.education.pdf-support %} + +### Akademische E-Mail-Adresse mit einer nicht verifizierten Domäne verwenden + +Wenn Deine akademische E-Mail-Adresse eine nicht verifizierte Domäne aufweist, fordern wir allenfalls einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Akademische E-Mail-Adresse von einer Bildungseinrichtung mit lockeren E-Mail-Richtlinien verwenden + +Falls Alumni und pensionierte Lehrkörper Deiner Bildungseinrichtung lebenslang auf die von Deiner Bildungseinrichtung ausgestellten E-Mail-Adressen zugreifen können, fordern wir allenfalls einen weiteren Nachweis Deines akademischen Status an. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +Bei anderen Fragen oder Bedenken zur Domäne der Bildungseinrichtung solltest Du das IT-Personal Deiner Bildungseinrichtung bitten, uns zu kontaktieren. + +### Nichtstudent beantragt das Studentenentwicklungspaket + +Lehrer und Forscher sind nicht berechtigt für die Partnerangebote, die im Lieferumfang von [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) enthalten sind. Stelle bei der erneuten Bewerbung sicher, dass Du **Faculty** (Universitätsmitglied) auswählst, um Deinen akademischen Status zu beschreiben. + +### Weiterführende Informationen + +- "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md index dd0e47873e..14b39274ad 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/de-DE/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -32,14 +32,14 @@ If you've enabled security updates, you'll sometimes see extra pull requests for ### Supported repositories and ecosystems +You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)." + {% note %} -{% data reusables.dependabot.private-dependencies %} +{% 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. See the details in the table below. {% endnote %} -You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)." - {% data reusables.dependabot.supported-package-managers %} If your repository already uses an integration for dependency management, you will need to disable this before enabling {% data variables.product.prodname_dependabot %}. For more information, see "[About integrations](/github/customizing-your-github-workflow/about-integrations)." diff --git a/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md b/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md index 188b6b5f8d..e695704f83 100644 --- a/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/de-DE/content/github/administering-a-repository/about-secret-scanning.md @@ -36,6 +36,7 @@ Wenn {% data variables.product.prodname_secret_scanning %} einen Satz von Anmeld - Databricks - Datadog - Discord +- Doppler - Dropbox - Dynatrace - Finicity @@ -79,6 +80,8 @@ Wenn {% data variables.product.prodname_secret_scanning %} ein Geheimnis in eine Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." + {% data variables.product.product_name %} durchsucht derzeit private Repositorys nach Geheimnissen, die von den folgenden Dienstanbietern veröffentlicht wurden. - Adafruit @@ -90,6 +93,7 @@ Repository administrators and organization owners can grant users and team acces - CloudBees CodeShip - Databricks - Discord +- Doppler - Dropbox - Dynatrace - Finicity diff --git a/translations/de-DE/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/de-DE/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index 950bc3a00d..5f9908aa05 100644 --- a/translations/de-DE/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/de-DE/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -302,13 +302,14 @@ updates: - dependency-name: "express" # For Express, ignore all updates for version 4 and 5 versions: ["4.x", "5.x"] - # For Loadash, ignore all updates - - dependency-name: "loadash" + # For Lodash, ignore all updates + - dependency-name: "lodash" ``` {% note %} -**Note**: {% data variables.product.prodname_dependabot_version_updates %} can't run version updates for any dependencies in manifests containing private git dependencies or private git registries, even if you add the private dependencies to the `ignore` option of your configuration file. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot#supported-repositories-and-ecosystems)“. +**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-repositories)" 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/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/de-DE/content/github/administering-a-repository/enabling-and-disabling-version-updates.md index ac4d471c64..41fc745b85 100644 --- a/translations/de-DE/content/github/administering-a-repository/enabling-and-disabling-version-updates.md +++ b/translations/de-DE/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -14,14 +14,10 @@ You enable {% data variables.product.prodname_dependabot_version_updates %} by c {% data reusables.dependabot.initial-updates %} For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)." +{% 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)." + ### Enabling {% data variables.product.prodname_dependabot_version_updates %} -{% note %} - -{% data reusables.dependabot.private-dependencies %} - -{% endnote %} - {% data reusables.dependabot.create-dependabot-yml %} 1. Use `package-ecosystem` to specify the package managers to monitor. 1. For each package manager, use: diff --git a/translations/de-DE/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/de-DE/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md new file mode 100644 index 0000000000..ff7815a490 --- /dev/null +++ b/translations/de-DE/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -0,0 +1,20 @@ +--- +title: Enabling or disabling GitHub Discussions for a repository +intro: 'You can use discussions in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.' +product: '{% data reusables.gated-features.discussions %}' +permissions: People with admin permissions to a repository can enable discussions for the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Enabling or disabling discussions for your repository + +{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} +1. To disable discussions, under "Features", unselect **Discussions**. + +### 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/github/administering-a-repository/index.md b/translations/de-DE/content/github/administering-a-repository/index.md index 38ac86d0f3..52b4a0d2e6 100644 --- a/translations/de-DE/content/github/administering-a-repository/index.md +++ b/translations/de-DE/content/github/administering-a-repository/index.md @@ -12,36 +12,25 @@ versions: ### Inhaltsverzeichnis {% topic_link_in_list /managing-repository-settings %} - {% link_in_list /setting-repository-visibility %}{% if currentVersion == "free-pro-team@latest" %} - {% link_in_list /managing-teams-and-people-with-access-to-your-repository %}{% endif %} + {% link_in_list /setting-repository-visibility %} + {% link_in_list /managing-teams-and-people-with-access-to-your-repository %} {% link_in_list /classifying-your-repository-with-topics %} {% link_in_list /customizing-how-changed-files-appear-on-github %} {% link_in_list /about-email-notifications-for-pushes-to-your-repository %} - {% link_in_list /displaying-a-sponsor-button-in-your-repository %} - - {% link_in_list /customizing-your-repositorys-social-media-preview %} - - {% link_in_list /viewing-deployment-activity-for-your-repository %} - {% link_in_list /managing-the-forking-policy-for-your-repository %} - {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository %} - {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %} + {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /enabling-or-disabling-github-discussions-for-a-repository %}{% endif %} {% link_in_list /managing-git-lfs-objects-in-archives-of-your-repository %} {% link_in_list /enabling-anonymous-git-read-access-for-a-repository %} - - {% link_in_list /configuring-autolinks-to-reference-external-resources %} - {% link_in_list /renaming-a-repository %} {% link_in_list /transferring-a-repository %} {% link_in_list /deleting-a-repository %} - {% link_in_list /restoring-a-deleted-repository %} - {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} {% link_in_list /changing-the-default-branch %} @@ -50,9 +39,7 @@ versions: {% link_in_list /about-merge-methods-on-github %} {% link_in_list /configuring-commit-squashing-for-pull-requests %} {% link_in_list /configuring-commit-rebasing-for-pull-requests %} - {% link_in_list /managing-the-automatic-deletion-of-branches %} - {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} {% link_in_list /configuring-protected-branches %} @@ -65,31 +52,22 @@ versions: {% link_in_list /enabling-required-reviews-for-pull-requests %} {% link_in_list /about-required-commit-signing %} {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} {% link_in_list /enabling-force-pushes-to-a-protected-branch %} {% link_in_list /enabling-deletion-of-a-protected-branch %} - {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} {% link_in_list /viewing-your-repositorys-releases-and-tags %} {% link_in_list /linking-to-releases %} - {% link_in_list /comparing-releases %} - - {% link_in_list /automation-for-release-forms-with-query-parameters %} - - {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} {% link_in_list /configuring-secret-scanning-for-private-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} - - {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} {% link_in_list /about-dependabot-version-updates %} {% link_in_list /enabling-and-disabling-version-updates %} @@ -98,4 +76,3 @@ versions: {% link_in_list /customizing-dependency-updates %} {% link_in_list /configuration-options-for-dependency-updates %} {% link_in_list /keeping-your-actions-up-to-date-with-dependabot %} - diff --git a/translations/de-DE/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/de-DE/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md index 1e96f1d87a..73d4f0b4cb 100644 --- a/translations/de-DE/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/de-DE/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -19,9 +19,9 @@ Nachdem Sie einen neuen SSH-Schlüssel zu Ihrem {% data variables.product.produc {% mac %} -1. Kopiere den SSH-Schlüssel in die Zwischenablage. +1. Copy the SSH public key to your clipboard. - Wenn Deine SSH-Schlüsseldatei einen anderen Namen hat als die Datei im Beispielcode, passe den Dateinamen entsprechend an. Achte beim Kopieren des Schlüssels darauf, keine neuen Zeilen oder Leerzeichen hinzuzufügen. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. Achte beim Kopieren des Schlüssels darauf, keine neuen Zeilen oder Leerzeichen hinzuzufügen. ```shell $ pbcopy < ~/.ssh/id_ed25519.pub @@ -46,9 +46,9 @@ Nachdem Sie einen neuen SSH-Schlüssel zu Ihrem {% data variables.product.produc {% windows %} -1. Kopiere den SSH-Schlüssel in die Zwischenablage. +1. Copy the SSH public key to your clipboard. - Wenn Deine SSH-Schlüsseldatei einen anderen Namen hat als die Datei im Beispielcode, passe den Dateinamen entsprechend an. Achte beim Kopieren des Schlüssels darauf, keine neuen Zeilen oder Leerzeichen hinzuzufügen. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. Achte beim Kopieren des Schlüssels darauf, keine neuen Zeilen oder Leerzeichen hinzuzufügen. ```shell $ clip < ~/.ssh/id_ed25519.pub @@ -73,9 +73,9 @@ Nachdem Sie einen neuen SSH-Schlüssel zu Ihrem {% data variables.product.produc {% linux %} -1. Kopiere den SSH-Schlüssel in die Zwischenablage. +1. Copy the SSH public key to your clipboard. - Wenn Deine SSH-Schlüsseldatei einen anderen Namen hat als die Datei im Beispielcode, passe den Dateinamen entsprechend an. Achte beim Kopieren des Schlüssels darauf, keine neuen Zeilen oder Leerzeichen hinzuzufügen. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. Achte beim Kopieren des Schlüssels darauf, keine neuen Zeilen oder Leerzeichen hinzuzufügen. ```shell $ sudo apt-get install xclip 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 3b65522121..8af0d490dc 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 @@ -9,7 +9,7 @@ versions: enterprise-server: '*' --- -Sie müssen ein Passwort für Ihr {% data variables.product.product_name %}-Konto auswählen oder erstellen, das +You must choose or generate a password for your {% data variables.product.product_name %} account that is at least: - 8 Zeichen lang ist, wenn es eine Zahl und einen Kleinbuchstaben enthält, oder - 16 Zeichen lang ist, bei einer beliebigen Kombination an Zeichen. diff --git a/translations/de-DE/content/github/authenticating-to-github/index.md b/translations/de-DE/content/github/authenticating-to-github/index.md index f1eb260b51..a388e3e426 100644 --- a/translations/de-DE/content/github/authenticating-to-github/index.md +++ b/translations/de-DE/content/github/authenticating-to-github/index.md @@ -35,11 +35,9 @@ versions: {% link_in_list /reviewing-your-authorized-applications-oauth %} {% link_in_list /reviewing-your-security-log %} {% link_in_list /removing-sensitive-data-from-a-repository %} - {% link_in_list /about-anonymized-image-urls %} {% link_in_list /about-githubs-ip-addresses %} {% link_in_list /githubs-ssh-key-fingerprints %} - {% link_in_list /sudo-mode %} {% link_in_list /preventing-unauthorized-access %} {% topic_link_in_list /securing-your-account-with-two-factor-authentication-2fa %} @@ -48,18 +46,14 @@ versions: {% link_in_list /configuring-two-factor-authentication-recovery-methods %} {% link_in_list /accessing-github-using-two-factor-authentication %} {% link_in_list /recovering-your-account-if-you-lose-your-2fa-credentials %} - {% link_in_list /changing-two-factor-authentication-delivery-methods-for-your-mobile-device %} {% link_in_list /countries-where-sms-authentication-is-supported %} - {% link_in_list /disabling-two-factor-authentication-for-your-personal-account %} - {% topic_link_in_list /authenticating-with-saml-single-sign-on %} {% link_in_list /about-authentication-with-saml-single-sign-on %} {% link_in_list /authorizing-an-ssh-key-for-use-with-saml-single-sign-on %} {% link_in_list /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-your-active-saml-sessions %} - {% topic_link_in_list /connecting-to-github-with-ssh %} {% link_in_list /about-ssh %} {% link_in_list /checking-for-existing-ssh-keys %} @@ -68,13 +62,9 @@ versions: {% link_in_list /testing-your-ssh-connection %} {% link_in_list /working-with-ssh-key-passphrases %} {% topic_link_in_list /troubleshooting-ssh %} - {% link_in_list /using-ssh-over-the-https-port %} - {% link_in_list /recovering-your-ssh-key-passphrase %} - {% link_in_list /deleted-or-missing-ssh-keys %} - {% link_in_list /error-permission-denied-publickey %} {% link_in_list /error-bad-file-number %} {% link_in_list /error-key-already-in-use %} @@ -82,9 +72,7 @@ versions: {% link_in_list /error-permission-to-userrepo-denied-to-userother-repo %} {% link_in_list /error-agent-admitted-failure-to-sign %} {% link_in_list /error-ssh-add-illegal-option----k %} - {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %} - {% link_in_list /error-were-doing-an-ssh-key-audit %} {% topic_link_in_list /managing-commit-signature-verification %} {% link_in_list /about-commit-signature-verification %} diff --git a/translations/de-DE/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/de-DE/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index dc70aa71bf..e9ed19699e 100644 --- a/translations/de-DE/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/de-DE/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -40,6 +40,12 @@ Um allen Text in der Datei `passwords.txt` zu ersetzen, unabhängig davon, wo er $ bfg --replace-text passwords.txt ``` +After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. + +```shell +$ git push --force +``` + Ausführliche Informationen zum Download und zur Verwendung von [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) findest Du in seiner Dokumentation. #### Mit „filter-branch“ 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 f36a844efc..9204a93747 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 @@ -176,7 +176,7 @@ An overview of some of the most common actions that are recorded as events in th | `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` | Wird ausgelöst, wenn Du einen Entwickler unterstützt (siehe „[Unterstützen eines Open-Source-Mitarbeiters](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor#sponsoring-a-developer)") | +| `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` | Wird ausgelöst, wenn Sie Ihre Einstellung zum Empfangen von E-Mail-Aktualisierungen von einem gesponserten Entwickler ändern (siehe „[Sponsoring verwalten](/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` | Wird ausgelöst, wenn Dein {% data variables.product.prodname_sponsors %}-Konto genehmigt ist (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/building-a-strong-community/index.md b/translations/de-DE/content/github/building-a-strong-community/index.md index c78e31380d..92e10f9873 100644 --- a/translations/de-DE/content/github/building-a-strong-community/index.md +++ b/translations/de-DE/content/github/building-a-strong-community/index.md @@ -13,21 +13,15 @@ versions: ### Inhaltsverzeichnis {% topic_link_in_list /setting-up-your-project-for-healthy-contributions %} - {% link_in_list /about-community-management-and-moderation %} {% link_in_list /about-community-profiles-for-public-repositories %} {% link_in_list /accessing-a-projects-community-profile %} {% link_in_list /adding-a-code-of-conduct-to-your-project %} - {% link_in_list /setting-guidelines-for-repository-contributors %} {% link_in_list /adding-a-license-to-a-repository %} {% link_in_list /adding-support-resources-to-your-project %} - {% link_in_list /creating-a-default-community-health-file %} - - {% link_in_list /encouraging-helpful-contributions-to-your-project-with-labels %} - {% topic_link_in_list /using-templates-to-encourage-useful-issues-and-pull-requests %} {% link_in_list /about-issue-and-pull-request-templates %} {% link_in_list /configuring-issue-templates-for-your-repository %} @@ -42,7 +36,6 @@ versions: {% link_in_list /tracking-changes-in-a-comment %} {% link_in_list /managing-how-contributors-report-abuse-in-your-organizations-repository %} {% link_in_list /managing-reported-content-in-your-organizations-repository %} - {% topic_link_in_list /maintaining-your-safety-on-github %} {% link_in_list /blocking-a-user-from-your-personal-account %} {% link_in_list /viewing-users-youve-blocked-from-your-personal-account %} @@ -51,7 +44,6 @@ versions: {% link_in_list /viewing-users-who-are-blocked-from-your-organization %} {% link_in_list /unblocking-a-user-from-your-organization %} {% link_in_list /reporting-abuse-or-spam %} - {% topic_link_in_list /documenting-your-project-with-wikis %} {% link_in_list /about-wikis %} {% link_in_list /adding-or-editing-wiki-pages %} @@ -60,10 +52,8 @@ versions: {% link_in_list /viewing-a-wikis-history-of-changes %} {% link_in_list /changing-access-permissions-for-wikis %} {% link_in_list /disabling-wikis %} - {% topic_link_in_list /collaborating-with-your-team %} {% link_in_list /about-team-discussions %} {% link_in_list /creating-a-team-discussion %} {% link_in_list /editing-or-deleting-a-team-discussion %} {% link_in_list /pinning-a-team-discussion %} - diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md index d3cfd7e9f0..b00db0468c 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -22,7 +22,11 @@ versions: {% data reusables.pull_requests.automatically-delete-branches %} -If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." +{% note %} + +**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." + +{% endnote %} If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)" or "[Closing a pull request](/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request)." diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/index.md index e4bc0c4313..6a1f436ac4 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/index.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/index.md @@ -29,9 +29,7 @@ versions: {% link_in_list /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility %} {% topic_link_in_list /collaborating-on-repositories-with-code-quality-features %} {% link_in_list /about-status-checks %} - {% link_in_list /working-with-pre-receive-hooks %} - {% topic_link_in_list /proposing-changes-to-your-work-with-pull-requests %} {% link_in_list /about-branches %} {% link_in_list /creating-and-deleting-branches-within-your-repository %} @@ -39,9 +37,7 @@ versions: {% link_in_list /about-comparing-branches-in-pull-requests %} {% link_in_list /creating-a-pull-request %} {% link_in_list /creating-a-pull-request-from-a-fork %} - {% link_in_list /changing-the-stage-of-a-pull-request %} - {% link_in_list /requesting-a-pull-request-review %} {% link_in_list /changing-the-base-branch-of-a-pull-request %} {% link_in_list /committing-changes-to-a-pull-request-branch-created-from-a-fork %} @@ -52,15 +48,12 @@ versions: {% topic_link_in_list /reviewing-changes-in-pull-requests %} {% link_in_list /about-pull-request-reviews %} {% link_in_list /reviewing-proposed-changes-in-a-pull-request %} - {% link_in_list /filtering-files-in-a-pull-request %} - {% link_in_list /finding-changed-methods-and-functions-in-a-pull-request %} {% link_in_list /commenting-on-a-pull-request %} {% link_in_list /viewing-a-pull-request-review %} - + {% link_in_list /reviewing-dependency-changes-in-a-pull-request %} {% link_in_list /incorporating-feedback-in-your-pull-request %} - {% link_in_list /approving-a-pull-request-with-required-reviews %} {% link_in_list /dismissing-a-pull-request-review %} {% link_in_list /checking-out-pull-requests-locally %} diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md new file mode 100644 index 0000000000..308d7f0f33 --- /dev/null +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -0,0 +1,74 @@ +--- +title: Reviewing dependency changes in a pull request +intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Dependency review is currently in beta and subject to change. + +{% endnote %} + +### About dependency review + +If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. + +Dependency review is available in: + +* All public repositories. +* Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[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)." + +Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. + +By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. {% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix them at some later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)." + +Dependency review supports the same languages and package management ecosystems as the dependency graph. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." + +### Reviewing dependencies in a pull request + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} + +1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. + + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + + {% note %} + + **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% endnote %} + +1. Check the dependencies listed in the dependency review. + + ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) + + Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name. + + The icon beside each dependency indicates whether the dependency has been added ({% octicon "diff-added" aria-label="Dependency added icon" %}), updated ({% octicon "diff-modified" aria-label="Dependency modified icon" %}), or removed ({% octicon "diff-removed" aria-label="Dependency removed icon" %}) in this pull request. + + Other information includes: + + * The version, or version range, of the new, updated, or deleted dependency. + * For a specific version of a dependency: + * The age of that release of the dependency. + * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency. + * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project. + + Where a dependency has a known vulnerability, the warning message includes: + + * A brief description of the vulnerability. + * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability. + * The severity of the vulnerability. + * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. + +1. You can return to the original view of the file by clicking the source diff button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 074a8300ae..16b08f16b6 100644 --- a/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -29,6 +29,18 @@ Vor dem Absenden Deines Reviews haben Deine Zeilenkommentare den Status _Aussteh ![Schaltfläche „Cancel review“ (Review abbrechen)](/assets/images/help/pull_requests/cancel-review-button.png) +{% if currentVersion == "free-pro-team@latest" %} +### Reviewing dependency changes + +If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. 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 reusables.repositories.changed-files %} + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) +{% endif %} + ### Datei als „gesehen“ markieren Wenn Sie den Review einer Datei abgeschlossen haben, können Sie sie als „gesehen“ markieren, um sie auszublenden. Falls die Datei nach Ihrer Überprüfung geändert wird, wird die Markierung aufgehoben und die Datei wird wieder eingeblendet. @@ -53,8 +65,5 @@ Wenn Sie den Review der Dateien des Pull Requesta abgeschlossen haben, senden Si ### Weiterführende Informationen -- „[Informationen zu Pull-Request-Reviews](/articles/about-pull-request-reviews)“ -- „[Informationen zu erforderlichen Reviews für Pull Requests](/articles/about-required-reviews-for-pull-requests)“ -- „[Pull Request mit erforderlichen Reviews genehmigen](/articles/approving-a-pull-request-with-required-reviews)“ -- „[Einen Pull Request kommentieren](/articles/commenting-on-a-pull-request)“ -- „[Pull Requests nach Review-Status filtern](/articles/filtering-pull-requests-by-review-status)“ +- „[Informationen zu erforderlichen Reviews für Pull Requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)“ +- „[Pull Requests nach Review-Status filtern](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)“ diff --git a/translations/de-DE/content/github/committing-changes-to-your-project/index.md b/translations/de-DE/content/github/committing-changes-to-your-project/index.md index 39a4aeb797..adb9307896 100644 --- a/translations/de-DE/content/github/committing-changes-to-your-project/index.md +++ b/translations/de-DE/content/github/committing-changes-to-your-project/index.md @@ -16,9 +16,7 @@ versions: {% topic_link_in_list /creating-and-editing-commits %} {% link_in_list /about-commits %} {% link_in_list /creating-a-commit-with-multiple-authors %} - {% link_in_list /creating-a-commit-on-behalf-of-an-organization %} - {% link_in_list /changing-a-commit-message %} {% topic_link_in_list /viewing-and-comparing-commits %} {% link_in_list /commit-branch-and-tag-labels %} 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 1845cf3779..1d19152e5d 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 @@ -40,9 +40,9 @@ Damit Codeinhaber Review-Anfragen erhalten können, muss sich die CODEINHABER-Da ### CODEOWNERS-Syntax -Eine CODEINHABER-Datei verwendet ein Muster, das den gleichen Regeln folgt wie in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format)-Dateien. Dem Muster folgen ein oder mehrere {% data variables.product.prodname_dotcom %}-Benutzernamen oder Teamnamen im Standardformat `@benutzername` oder `@org/teamname`. Du kannst auf einen Benutzer auch über eine E-Mail-Adresse verweisen, die zu dessen {% data variables.product.product_name %}-Konto hinzugefügt wurde, z. B. `benutzer@beispiel.com`. +A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). Dem Muster folgen ein oder mehrere {% data variables.product.prodname_dotcom %}-Benutzernamen oder Teamnamen im Standardformat `@benutzername` oder `@org/teamname`. Du kannst auf einen Benutzer auch über eine E-Mail-Adresse verweisen, die zu dessen {% data variables.product.product_name %}-Konto hinzugefügt wurde, z. B. `benutzer@beispiel.com`. -If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. Invalid syntax includes inline comments and user or team names that do not exist on {% data variables.product.product_name %}. +If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. #### Beispiel für eine CODEOWNERS-Datei ``` # Dies ist ein Kommentar. @@ -84,6 +84,13 @@ apps/ @octocat # subdirectories. /docs/ @doctocat ``` +#### Syntax exceptions +There are some syntax rules for gitignore files that do not work in CODEOWNERS files: +- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment +- Using `!` to negate a pattern +- Using `[ ]` to define a character range + + ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index e5aaafd263..c0202a16e9 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -1,6 +1,6 @@ --- title: Informationen zu Repositorys -intro: Ein Repository ist wie ein Ordner für Dein Projekt. Das Repository Deines Projekts enthält alle Dateien Deines Projekts und speichert den Revisionsverlauf jeder Datei. Im Repository kannst Du außerdem die Arbeit Deines Projekts diskutieren und verwalten. +intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository. redirect_from: - /articles/about-repositories versions: @@ -22,9 +22,11 @@ With Jede Person und Organisation kann unbegrenzte Repositorys besitzen und eine unbegrenzte Anzahl von Mitarbeitern in alle Repositorys einladen. {% endif %} -Mithilfe der Issues, Pull Requests und Projektboards Ihres Repositorys können Sie mit anderen an Ihrem Projekt zusammenarbeiten. - -![Hauptseite des Octocat-/Hello-World-Repositorys](/assets/images/help/repository/repo-main-page.png) +You can use repositories to manage your work and collaborate with others. +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)." +- {% data reusables.discussions.you-can-use-discussions %} +- You can use pull requests to propose changes to a repository. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests).“ +- You can use project boards to organize and prioritize your issues and pull requests. Weitere Informationen findest Du unter „[Informationen zu Projektboards](/github/managing-your-work-on-github/about-project-boards).“ {% data reusables.repositories.repo-size-limit %} diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md index ecff7ae105..6da456fa01 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md @@ -45,16 +45,16 @@ Um die URL des lokalen Repositorys zu ermitteln, öffne die Befehlszeile und gib ```shell $ git remote -v # Zeigt vorhandene Remote-Repositorys an -> origin https://github.com/github/reactivecocoa.git (fetch) -> origin https://github.com/github/reactivecocoa.git (push) +> origin https://github.com/ghost/reactivecocoa.git (fetch) +> origin https://github.com/ghost/reactivecocoa.git (push) -$ git remote set-url origin https://github.com/github/ReactiveCocoa.git +$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git # Ändert die origin-Remote-URL $ git remote -v # Überprüft die neue Remote-URL -> origin https://github.com/github/ReactiveCocoa.git (fetch) -> origin https://github.com/github/ReactiveCocoa.git (push) +> origin https://github.com/ghost/ReactiveCocoa.git (fetch) +> origin https://github.com/ghost/ReactiveCocoa.git (push) ``` Alternativ können Sie die URL auch über unsere [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)-Anwendung ändern. diff --git a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/index.md index d26bc165ef..68a6ca7fa4 100644 --- a/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/index.md +++ b/translations/de-DE/content/github/creating-cloning-and-archiving-repositories/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repositories %} {% link_in_list /about-repository-visibility %} {% link_in_list /creating-a-new-repository %} - {% link_in_list /creating-a-repository-from-a-template %} - {% link_in_list /about-readmes %} {% link_in_list /about-code-owners %} {% link_in_list /about-repository-languages %} {% link_in_list /licensing-a-repository %} - {% link_in_list /creating-a-template-repository %} - {% link_in_list /creating-an-issues-only-repository %} {% link_in_list /limits-for-viewing-content-and-diffs-in-a-repository %} {% link_in_list /duplicating-a-repository %} @@ -39,8 +35,6 @@ versions: {% topic_link_in_list /archiving-a-github-repository %} {% link_in_list /about-archiving-repositories %} {% link_in_list /archiving-repositories %} - {% link_in_list /about-archiving-content-and-data-on-github %} {% link_in_list /referencing-and-citing-content %} - {% link_in_list /backing-up-a-repository %} diff --git a/translations/de-DE/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/de-DE/content/github/customizing-your-github-workflow/about-github-marketplace.md index 25bb385ca8..dd51c26ffa 100644 --- a/translations/de-DE/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/de-DE/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -7,26 +7,27 @@ versions: free-pro-team: '*' --- -Auf [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) können Sie kostenlose und kostenpflichtige Tools entdecken, durchsuchen und installieren, darunter [{% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/) und {% data variables.product.prodname_actions %}. +You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Wenn Sie ein kostenpflichtiges Tool erwerben, bezahlen Sie für Ihr Tool-Abonnement mit den gleichen Abrechnungsinformationen, mit denen Sie für Ihr {% data variables.product.product_name %}-Abonnement bezahlen, und erhalten an Ihrem regulären Abrechnungsdatum eine Rechnung. Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace).“ -Unter Umständen hast Du auch die Möglichkeit, eine kostenlose 14-tägige Testversion für ausgewählte Tools zu nutzen. Du kannst während der Testphase jederzeit kündigen, und es wird Dir nichts in Rechnung gestellt, aber Du verlierst automatisch den Zugriff auf das Tool. Dein kostenpflichtiges Abonnement beginnt am Ende der 14-tägigen Testphase. Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace).“ +You may also have the option to select a free 14-day trial on some tools. Du kannst während der Testphase jederzeit kündigen, und es wird Dir nichts in Rechnung gestellt, aber Du verlierst automatisch den Zugriff auf das Tool. Dein kostenpflichtiges Abonnement beginnt am Ende der 14-tägigen Testphase. Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace).“ -{% data variables.product.prodname_github_app %}s und {% data variables.product.prodname_oauth_app %}s können verifiziert oder nicht verifiziert sein. Verifizierte Apps erfüllen die spezifischen Anforderungen von {% data variables.product.prodname_dotcom %} und durchlaufen eine Sicherheitsüberprüfung, bevor sie auf {% data variables.product.prodname_marketplace %} veröffentlicht werden. For more information, see "[Requirements for listing an app on GitHub Marketplace](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." +### Finding tools on {% data variables.product.prodname_marketplace %} -### {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_marketplace %} +You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." -Du kannst {% data variables.product.prodname_actions %} entdecken, durchsuchen und installieren, die von Dritten auf {% data variables.product.prodname_marketplace %} erstellt wurden. Weitere Informationen findest Du unter „[Durchsuche {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +{% data reusables.actions.actions-not-verified %} -Jeder kann eine Aktion auf {% data variables.product.prodname_marketplace %} veröffentlichen. Im Gegensatz zu einigen Apps sind {% data variables.product.prodname_actions %}, die auf {% data variables.product.prodname_marketplace %} aufgeführt sind, nie von {% data variables.product.prodname_dotcom %} verifiziert. +Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About verified creators](/developers/github-marketplace/about-verified-creators)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### Ein Tool auf {% data variables.product.prodname_marketplace %} erstellen und veröffentlichen -For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/apps)" and "[{% data variables.product.prodname_actions %}](/actions)." +For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/developers/apps)" and "[{% data variables.product.prodname_actions %}](/actions)." ### Weiterführende Informationen - „[Apps in {% data variables.product.prodname_marketplace %} kaufen und installieren](/articles/purchasing-and-installing-apps-in-github-marketplace)“ - „[Abrechnung für Ihre {% data variables.product.prodname_marketplace %}-Apps verwalten](/articles/managing-billing-for-github-marketplace-apps)“ - „[{% data variables.product.prodname_marketplace %}-Support](/articles/github-marketplace-support)“ +- "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)" diff --git a/translations/de-DE/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/de-DE/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md index 10d9376b25..8c7116cd1d 100644 --- a/translations/de-DE/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/de-DE/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -15,7 +15,7 @@ versions: {% data reusables.codespaces.about-configuration %} -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes tools for Node.js, JavaScript, TypeScript, Python, C++, Java, C#, .NET Core, PHP, and PowerShell. For more information about the base Linux image, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) repository. +If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes tools for Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, PowerShell, Go, Ruby, and Rust. For more information about the base Linux image, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) repository. {% data reusables.codespaces.about-personalization %} {% data reusables.codespaces.codespace-config-order %} Weitere Informationen findest Du unter „[{% data variables.product.prodname_codespaces %} für Dein Konto personalisieren](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." 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 878369e4a0..309effd0a6 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 @@ -44,11 +44,11 @@ Scanning code when someone pushes a change, and whenever a pull request is creat #### 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)." +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)." #### 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. 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 %} 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)." @@ -148,14 +148,14 @@ jobs: matrix: language: ['javascript', 'python'] ``` - + If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. ```yaml - uses: github/codeql-action/init@v1 with: languages: cpp, csharp, python -``` +``` {% if currentVersion == "free-pro-team@latest" %} ### Analyzing Python dependencies @@ -183,20 +183,20 @@ jobs: - name: Install dependencies run: | python -m pip install --upgrade pip - if [ -f requirements.txt ]; + if [ -f requirements.txt ]; then pip install -r requirements.txt; fi # Set the `CODEQL-PYTHON` environment variable to the Python executable # that includes the dependencies - echo "::set-env name=CODEQL_PYTHON::$(which python)" + echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV - name: Initialize CodeQL uses: github/codeql-action/init@v1 with: languages: python - # Override the default behavior so that the action doesn't attempt + # Override the default behavior so that the action doesn't attempt # to auto-install Python dependencies setup-python-dependencies: false -``` +``` {% endif %} ### Running additional queries @@ -239,7 +239,7 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp ``` The configuration file can be located within the local repository, or in a public, remote repository. For remote repositories, you can use the _owner/repository/file.yml@branch_ syntax. The settings in the file are written in YAML format. - + #### Specifying additional queries 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. @@ -265,15 +265,15 @@ For the interpreted languages that {% data variables.product.prodname_codeql %} ``` yaml paths: - - src -paths-ignore: + - src +paths-ignore: - src/node_modules - '**/*.test.js' ``` {% note %} -**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. @@ -298,7 +298,7 @@ You can quickly analyze small portions of a monorepo when you modify code in spe 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 `github/foo`, `github/bar`, and `github/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. +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 @@ -307,9 +307,9 @@ steps: env: TOKEN: ${{ secrets.ACCESS_TOKEN }} run: | - git config --global url."https://${TOKEN}@github.com/github/foo".insteadOf "https://github.com/github/foo" - git config --global url."https://${TOKEN}@github.com/github/bar".insteadOf "https://github.com/github/bar" - git config --global url."https://${TOKEN}@github.com/github/baz".insteadOf "https://github.com/github/baz" + 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 %} diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md index fa8a14334b..b344e67a80 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md @@ -21,7 +21,7 @@ You must run {% data variables.product.prodname_codeql %} in the same container You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations: * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* MacOS: https://github.com/actions/virtual-environments/tree/main/images/macos +* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos * Windows: https://github.com/actions/virtual-environments/tree/main/images/win ### Example workflow diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 539d8eca9a..c071341bd5 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -40,7 +40,7 @@ On Linux: chmod +x codeql-runner-linux ``` -On MacOS: +Unter macOS: ```shell chmod +x codeql-runner-macos diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index b042803451..2a8acbc0b4 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -107,13 +107,13 @@ A location within a programming artifact, such as a file in the repository or a #### `physicalLocation` object -| Name | Beschreibung | -| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `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/github/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. | +| Name | Beschreibung | +| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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. | ### SARIF output file examples diff --git a/translations/de-DE/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/de-DE/content/github/getting-started-with-github/git-and-github-learning-resources.md index fe35c2cfd7..12f894aba4 100644 --- a/translations/de-DE/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/de-DE/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +authors: + - GitHub --- ### Git verwenden diff --git a/translations/de-DE/content/github/getting-started-with-github/github-glossary.md b/translations/de-DE/content/github/getting-started-with-github/github-glossary.md index 60b1fb36de..dc6f67613a 100644 --- a/translations/de-DE/content/github/getting-started-with-github/github-glossary.md +++ b/translations/de-DE/content/github/getting-started-with-github/github-glossary.md @@ -10,8 +10,8 @@ versions: --- {% for term in site.data.glossaries.external %} - ### {{term.term}} - {{term.description}} + ### {% data glossaries.external[forloop.index0].term %} + {% data glossaries.external[forloop.index0].description %} --- {% endfor %} diff --git a/translations/de-DE/content/github/getting-started-with-github/index.md b/translations/de-DE/content/github/getting-started-with-github/index.md index 5bc2a62a79..9b70ebbe0d 100644 --- a/translations/de-DE/content/github/getting-started-with-github/index.md +++ b/translations/de-DE/content/github/getting-started-with-github/index.md @@ -27,37 +27,27 @@ versions: {% link_in_list /fork-a-repo %} {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} - {% link_in_list /githubs-products %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} - {% link_in_list /types-of-github-accounts %} - {% link_in_list /faq-about-changes-to-githubs-plans %} {% link_in_list /github-cli %} {% link_in_list /github-desktop %} {% link_in_list /github-for-mobile %} - {% link_in_list /access-permissions-on-github %} {% link_in_list /github-glossary %} {% link_in_list /git-cheatsheet %} {% link_in_list /git-and-github-learning-resources %} {% topic_link_in_list /signing-up-for-github %} - {% link_in_list /signing-up-for-a-new-github-account %} {% link_in_list /verifying-your-email-address %} - {% link_in_list /setting-up-a-trial-of-github-enterprise-cloud %} {% link_in_list /setting-up-a-trial-of-github-enterprise-server %} {% topic_link_in_list /exploring-projects-on-github %} - {% link_in_list /finding-ways-to-contribute-to-open-source-on-github %} - {% link_in_list /saving-repositories-with-stars %} {% link_in_list /following-people %} {% topic_link_in_list /using-github %} {% link_in_list /supported-browsers %} - {% link_in_list /troubleshooting-connectivity-problems %} - {% link_in_list /keyboard-shortcuts %} diff --git a/translations/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 a5c927908e..f3f7cbdb3b 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 @@ -123,9 +123,9 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |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 +|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 +|command + → or command + l or control + → or control + l | Move column to the rightmost position #### Moving a card @@ -135,17 +135,17 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |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 +|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 +|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 +|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 +|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 #### Previewing a card @@ -158,7 +158,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ -|command space or control space | In the workflow editor, get suggestions for your workflow file. +|command + space or control + space | In the workflow editor, get suggestions for your workflow file. {% endif %} @@ -168,16 +168,16 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ |e | Mark as done -| shift u| Mark as unread -| shift i| Mark as read -| shift m | Unsubscribe +| shift + u| Mark as unread +| shift + i| Mark as read +| shift + m | Unsubscribe {% else %} | Keyboard shortcut | Description |-----------|------------ |e or I or y | Mark as read -|shift m | Mute thread +|shift + m | Mute thread {% endif %} ### Network graph @@ -188,7 +188,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |→ 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 +|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 diff --git a/translations/de-DE/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md b/translations/de-DE/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md index 0e34a4eec2..2f878b9456 100644 --- a/translations/de-DE/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md +++ b/translations/de-DE/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md @@ -1,5 +1,6 @@ --- title: Neues GitHub-Konto registrieren +shortTitle: Sign up for a new GitHub account intro: 'Für die Teamarbeit bietet {% data variables.product.product_name %} Benutzerkonten für Einzelpersonen und Organisationen.' redirect_from: - /articles/signing-up-for-a-new-github-account @@ -9,9 +10,8 @@ versions: Weitere Informationen zu den verschiedenen Konto- und Produkttypen findest Du unter „[Arten von {% data variables.product.prodname_dotcom %}-Konten](/articles/types-of-github-accounts)“ und „[Produkte von {% data variables.product.product_name %}](/articles/github-s-products).“ -1. Rufen Sie die [Preisübersicht]({% data variables.product.pricing_url %}) von {% data variables.product.product_name %} auf. -2. Lies die Informationen zu den von {% data variables.product.product_name %} angebotenen Produkten und Abonnements, und klicke dann unter dem Abonnement, das Dich interessiert, auf die Schaltfläche „Upgrade“. -3. Folge den Eingabeaufforderungen, um Dein persönliches Konto oder Deine Organisation zu erstellen. +{% data reusables.accounts.create-account %} +1. Folge den Eingabeaufforderungen, um Dein persönliches Konto oder Deine Organisation zu erstellen. ### Nächste Schritte: diff --git a/translations/de-DE/content/github/importing-your-projects-to-github/index.md b/translations/de-DE/content/github/importing-your-projects-to-github/index.md index 47624c323b..86dd2555b6 100644 --- a/translations/de-DE/content/github/importing-your-projects-to-github/index.md +++ b/translations/de-DE/content/github/importing-your-projects-to-github/index.md @@ -15,11 +15,9 @@ versions: ### Inhaltsverzeichnis {% topic_link_in_list /importing-source-code-to-github %} - {% link_in_list /about-github-importer %} {% link_in_list /importing-a-repository-with-github-importer %} {% link_in_list /updating-commit-author-attribution-with-github-importer %} - {% link_in_list /importing-a-git-repository-using-the-command-line %} {% link_in_list /adding-an-existing-project-to-github-using-the-command-line %} {% link_in_list /source-code-migration-tools %} diff --git a/translations/de-DE/content/github/index.md b/translations/de-DE/content/github/index.md index 9b581e0b4f..33f2c4a15d 100644 --- a/translations/de-DE/content/github/index.md +++ b/translations/de-DE/content/github/index.md @@ -20,24 +20,14 @@ versions: {% link_in_list /authenticating-to-github %} - {% link_in_list /managing-subscriptions-and-notifications-on-github %} - - {% link_in_list /receiving-notifications-about-activity-on-github %} - {% link_in_list /setting-up-and-managing-organizations-and-teams %} - - {% link_in_list /setting-up-and-managing-your-enterprise %} - - - {% link_in_list /setting-up-and-managing-billing-and-payments-on-github %} - {% link_in_list /writing-on-github %} @@ -50,10 +40,7 @@ versions: {% link_in_list /collaborating-with-issues-and-pull-requests %} {% link_in_list /managing-your-work-on-github %} - - {% link_in_list /developing-online-with-codespaces %} - {% link_in_list /building-a-strong-community %} @@ -64,45 +51,20 @@ versions: {% link_in_list /administering-a-repository %} {% link_in_list /visualizing-repository-data-with-graphs %} - - {% link_in_list /managing-security-vulnerabilities %} - {% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %} {% link_in_list /managing-files-in-a-repository %} {% link_in_list /managing-large-files %} - - {% link_in_list /customizing-your-github-workflow %} - {% link_in_list /extending-github %} {% link_in_list /working-with-github-pages %} - - {% link_in_list /supporting-the-open-source-community-with-github-sponsors %} - - - -{% link_in_list /teaching-and-learning-with-github-education %} - - - {% link_in_list /finding-talent-with-github-jobs %} - - - {% link_in_list /working-with-github-support %} - - - {% link_in_list /understanding-how-github-uses-and-protects-your-data %} - - - {% link_in_list /site-policy %} - diff --git a/translations/de-DE/content/github/managing-files-in-a-repository/index.md b/translations/de-DE/content/github/managing-files-in-a-repository/index.md index dea3f734ab..1e00f814a6 100644 --- a/translations/de-DE/content/github/managing-files-in-a-repository/index.md +++ b/translations/de-DE/content/github/managing-files-in-a-repository/index.md @@ -14,9 +14,7 @@ versions: ### Inhaltsverzeichnis {% topic_link_in_list /managing-files-on-github %} - {% link_in_list /navigating-code-on-github %} - {% link_in_list /creating-new-files %} {% link_in_list /adding-a-file-to-a-repository %} {% link_in_list /moving-a-file-to-a-new-location %} diff --git a/translations/de-DE/content/github/managing-large-files/index.md b/translations/de-DE/content/github/managing-large-files/index.md index 5fd72e0248..41f38b164b 100644 --- a/translations/de-DE/content/github/managing-large-files/index.md +++ b/translations/de-DE/content/github/managing-large-files/index.md @@ -15,16 +15,12 @@ versions: {% link_in_list /conditions-for-large-files %} {% link_in_list /removing-files-from-a-repositorys-history %} {% link_in_list /distributing-large-binaries %} - {% link_in_list /what-is-my-disk-quota %} - {% topic_link_in_list /versioning-large-files %} {% link_in_list /about-git-large-file-storage %} {% link_in_list /installing-git-large-file-storage %} {% link_in_list /configuring-git-large-file-storage %} - {% link_in_list /about-storage-and-bandwidth-usage %} - {% link_in_list /collaboration-with-git-large-file-storage %} {% link_in_list /moving-a-file-in-your-repository-to-git-large-file-storage %} {% link_in_list /removing-files-from-git-large-file-storage %} 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 5ed4ecd34c..5225874dd2 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 @@ -25,6 +25,8 @@ When your code depends on a package that has a security vulnerability, this vuln - 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 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)." {% note %} diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/de-DE/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md new file mode 100644 index 0000000000..f686f2002b --- /dev/null +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -0,0 +1,24 @@ +--- +title: About managing vulnerable dependencies +intro: '{% data variables.product.prodname_dotcom %} helps you to avoid using third-party software that contains known vulnerabilities.' +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies. + +#### Dependency graph +The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." + +#### Dependency review +By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + +#### {% data variables.product.prodname_dependabot_alerts %} +{% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | + +#### {% data variables.product.prodname_dependabot_security_updates %} +When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." + + +#### {% data variables.product.prodname_dependabot_version_updates %} +Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 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 c476be75c7..3bd8bae1cb 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 @@ -12,7 +12,7 @@ versions: {% 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-features-for-new-repositories)." +{% 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)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %} diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/index.md b/translations/de-DE/content/github/managing-security-vulnerabilities/index.md index 588a51e650..477133253e 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/index.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/index.md @@ -9,8 +9,6 @@ versions: ### Inhaltsverzeichnis - - {% topic_link_in_list /managing-security-vulnerabilities-in-your-project %} {% link_in_list /adding-a-security-policy-to-your-repository %} {% link_in_list /about-github-security-advisories %} @@ -22,17 +20,13 @@ versions: {% link_in_list /publishing-a-security-advisory %} {% link_in_list /editing-a-security-advisory %} {% link_in_list /withdrawing-a-security-advisory %} - {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %} - + {% link_in_list /about-managing-vulnerable-dependencies %} {% link_in_list /browsing-security-vulnerabilities-in-the-github-advisory-database %} - {% link_in_list /about-alerts-for-vulnerable-dependencies %} {% link_in_list /configuring-notifications-for-vulnerable-dependencies %} - {% link_in_list /about-dependabot-security-updates %} {% link_in_list /configuring-dependabot-security-updates %} {% link_in_list /viewing-and-updating-vulnerable-dependencies-in-your-repository %} {% link_in_list /troubleshooting-the-detection-of-vulnerable-dependencies %} {% link_in_list /troubleshooting-dependabot-errors %} - diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/de-DE/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index c33aa46aba..dd179ef0df 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -76,6 +76,12 @@ There are separate limits for security and version update pull requests, so that 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 %} can't resolve your dependency files + +**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". + +{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." + ### Triggering a {% data variables.product.prodname_dependabot %} pull request manually If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request. diff --git a/translations/de-DE/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/de-DE/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 5677e04981..d780c025d9 100644 --- a/translations/de-DE/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/de-DE/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -13,9 +13,11 @@ Your repository's {% data variables.product.prodname_dependabot %} alerts tab li You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +{% data reusables.repositories.dependency-review %} + ### About updates for vulnerable dependencies in your repository -{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. +{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. ### Viewing and updating vulnerable dependencies diff --git a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index a9cd8fdeb8..8a45110eb4 100644 --- a/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/de-DE/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -124,7 +124,8 @@ Um Benachrichtigungen nach bestimmten Aktivitäten auf {% data variables.product - `is:repository-invitation`{% if currentVersion != "github-ae@latest" %} - `is:repository-vulnerability-alert` - `is:repository-advisory`{% endif %} -- `is:team-discussion` +- `is:team-discussion`{% if currentVersion == "free-pro-team@latest" %} +- `is:discussions`{% endif %} {% if currentVersion != "github-ae@latest" %} For information about reducing noise from notifications for diff --git a/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md b/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md index c5d27795d2..f58e1b0df4 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/about-issues.md @@ -10,17 +10,23 @@ versions: github-ae: '*' --- +### Informationen zu Issues + Du kannst Feedback von Benutzern sammeln, Softwarefehler melden und Aufgaben organisieren, die Du mit Issues in einem Repository durchführen möchtest. Issues sind mehr als nur ein Ort zum Melden von Softwarefehlern. +Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} + +{% data reusables.discussions.you-cannot-convert-a-discussion %} + {% data reusables.pull_requests.close-issues-using-keywords %} -Um über die neuesten Kommentare in einem Issue auf dem Laufenden zu bleiben, kannst Du einen Issue beobachten, um Benachrichtigungen über neue Kommentare zu erhalten. 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 %}." +Um über die neuesten Kommentare in einem Issue auf dem Laufenden zu bleiben, können Sie einen Issue beobachten, um Benachrichtigungen über die neuesten Kommentare zu erhalten. 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 %}." Um schnell Links zu kürzlich aktualisierten Issues zu finden, besuche Dein Dashboard. Weitere Informationen findest Du unter „[Informationen zum persönlichen Dashboard](/articles/about-your-personal-dashboard).“ ### Mit Issues arbeiten -Issues ermöglichen Dir Folgendes: +Issues ermöglichen Ihnen Folgendes: - Verfolge und priorisiere Deine Arbeit mithilfe von Projektboards. Weitere Informationen findest Du unter „[Projektboards verwenden](/articles/about-project-boards).“ - Erstelle neue Issues, um Feedback aus einem Kommentar in einem Issue-oder Pull-Request-Review zu verfolgen, das außerhalb des Anwendungsbereichs liegt. Weitere Informationen findest Du unter „[Öffnen eines Issue aus einem Kommentar](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." - Erstelle Issue-Vorlagen, um Mitarbeitern zu helfen, aussagekräftige Issues zu erstellen. Weitere Informationen findest Du unter „[Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates)“ diff --git a/translations/de-DE/content/github/managing-your-work-on-github/index.md b/translations/de-DE/content/github/managing-your-work-on-github/index.md index 17156e7774..85e695ac7e 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/index.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/index.md @@ -17,15 +17,11 @@ versions: {% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} - {% link_in_list /deleting-an-issue %} - {% link_in_list /opening-an-issue-from-a-comment %} {% link_in_list /opening-an-issue-from-code %} - {% link_in_list /transferring-an-issue-to-another-repository %} {% link_in_list /pinning-an-issue-to-your-repository %} - {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} @@ -43,9 +39,7 @@ versions: {% link_in_list /linking-a-repository-to-a-project-board %} {% link_in_list /about-automation-for-project-boards %} {% link_in_list /configuring-automation-for-project-boards %} - {% link_in_list /copying-a-project-board %} - {% link_in_list /closing-a-project-board %} {% link_in_list /reopening-a-closed-project-board %} {% link_in_list /deleting-a-project-board %} diff --git a/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index 3d6842eb3b..92e100bcdf 100644 --- a/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/de-DE/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -25,6 +25,7 @@ Mithilfe von Suchbegriffen zu Issues und Pull Requests kannst Du: - Issues und Pull Requests filtern, die bestimmte Personen umfassen, sie jedoch nicht zwangsläufig [**@erwähnen**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams): `state:open type:issue involves:octocat`, - Issues und Pull Requests nach Bearbeiter filtern: `state:open type:issue assignee:octocat`, - Issues und Pull Requests nach Kennzeichnung filtern: `state:open type:issue label:"bug"`. +- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} Für Issues kannst Du die Suche auf für folgendes benutzen: diff --git a/translations/de-DE/content/github/receiving-notifications-about-activity-on-github/index.md b/translations/de-DE/content/github/receiving-notifications-about-activity-on-github/index.md index 4893fcdc3b..29e6de18d9 100644 --- a/translations/de-DE/content/github/receiving-notifications-about-activity-on-github/index.md +++ b/translations/de-DE/content/github/receiving-notifications-about-activity-on-github/index.md @@ -14,16 +14,10 @@ versions: {% link_in_list /choosing-the-delivery-method-for-your-notifications %} {% topic_link_in_list /managing-your-notifications %} {% link_in_list /marking-notifications-as-read %} - {% link_in_list /saving-notifications-for-later %} - {% link_in_list /subscribing-to-and-unsubscribing-from-notifications %} - {% link_in_list /listing-the-issues-and-pull-requests-youre-subscribed-to %} - {% link_in_list /watching-and-unwatching-repositories %} - {% link_in_list /watching-and-unwatching-releases-for-a-repository %} - {% link_in_list /watching-and-unwatching-team-discussions %} {% link_in_list /listing-the-repositories-youre-watching %} diff --git a/translations/de-DE/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/de-DE/content/github/searching-for-information-on-github/about-searching-on-github.md index 1d31fb0a4d..7d740b9768 100644 --- a/translations/de-DE/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/de-DE/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -41,7 +41,8 @@ You can search for the following information across all repositories you can acc - [Repositorys](/articles/searching-for-repositories) - [Themen](/articles/searching-topics) -- [Issues und Pull Requests](/articles/searching-issues-and-pull-requests) +- [Issues and pull requests](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} +- [Discussions](/github/searching-for-information-on-github/searching-discussions){% endif %} - [Code](/articles/searching-code) - [Commits](/articles/searching-commits) - [Users](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/de-DE/content/github/searching-for-information-on-github/index.md b/translations/de-DE/content/github/searching-for-information-on-github/index.md index 83be0daff7..e2fa94d269 100644 --- a/translations/de-DE/content/github/searching-for-information-on-github/index.md +++ b/translations/de-DE/content/github/searching-for-information-on-github/index.md @@ -26,6 +26,7 @@ versions: {% link_in_list /searching-code %} {% link_in_list /searching-commits %} {% link_in_list /searching-issues-and-pull-requests %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /searching-discussions %} {% link_in_list /searching-github-marketplace %}{% endif %} {% link_in_list /searching-users %} {% link_in_list /searching-for-packages %} diff --git a/translations/de-DE/content/github/searching-for-information-on-github/searching-discussions.md b/translations/de-DE/content/github/searching-for-information-on-github/searching-discussions.md new file mode 100644 index 0000000000..a2b861d7ed --- /dev/null +++ b/translations/de-DE/content/github/searching-for-information-on-github/searching-discussions.md @@ -0,0 +1,110 @@ +--- +title: Searching discussions +intro: You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github).“ + +{% data reusables.search.syntax_tips %} + +### Suche nach Titel, Textteil oder Kommentaren + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| Qualifizierer | Beispiel | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +### Suche innerhalb der Repositorys eines Benutzers oder einer Organisation + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| Qualifizierer | Beispiel | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +### Filter by repository visibility + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. Weitere Informationen findest Du unter „[Über Sichtbarkeit von Repositorys](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +| Qualifier | Example | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +### Suche nach Autor + +The `author` qualifier finds discussions created by a certain user. + +| Qualifizierer | Beispiel | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +### Suche nach Kommentierer + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| Qualifizierer | Beispiel | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +### Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| Qualifizierer | Beispiel | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +### Suche nach Anzahl der Kommentare + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +### Suche nach Anzahl der Interaktionen + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +### Suche nach Anzahl der Reaktionen + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +### Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +### Weiterführende Informationen + +- „[Suchergebnisse sortieren](/articles/sorting-search-results/)“ diff --git a/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index f7afc70ea8..20b559c982 100644 --- a/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/de-DE/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -203,7 +203,7 @@ Mit dem Kennzeichner `comments` in Verbindung mit dem [„Größer-als“-, „K | Qualifizierer | Beispiel | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3C100&type=Issues) sucht geschlossene Issues mit mehr als 100 Kommentaren. | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) sucht geschlossene Issues mit mehr als 100 Kommentaren. | | | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) sucht Issues mit 500 bis 1.000 Kommentaren. | ### Suche nach Anzahl der Interaktionen diff --git a/translations/de-DE/content/github/searching-for-information-on-github/searching-topics.md b/translations/de-DE/content/github/searching-for-information-on-github/searching-topics.md index e3b3a6627b..3f25693241 100644 --- a/translations/de-DE/content/github/searching-for-information-on-github/searching-topics.md +++ b/translations/de-DE/content/github/searching-for-information-on-github/searching-topics.md @@ -26,7 +26,7 @@ Wenn Sie in Repositorys bestimmte Themen suchen, um zu Projekten beizutragen, od Der Suchkennzeichner `is:featured` grenzt das Suchergebnis auf die Themen mit den meisten Repositorys auf {% data variables.product.product_name %} ein. Diese Themen werden auch auf „https://github.com/topics/“ vorgestellt. -Der Qualifizierer `is:curated` grenzt das Suchergebnis auf Themen ein, zu denen Community-Mitglieder zusätzliche Informationen hinzugefügt haben. Weitere Informationen findest Du im Explore-Repository auf „https://github.com/github/explore“. +Der Qualifizierer `is:curated` grenzt das Suchergebnis auf Themen ein, zu denen Community-Mitglieder zusätzliche Informationen hinzugefügt haben. For more information, see the [explore repository](https://github.com/github/explore). Mit dem Datumsparameter und dem Qualifizierer `created:` kannst Du Themen nach ihrem Erstellungsdatum filtern, und mit `repositories:n` kannst Du nach der Anzahl der einem Thema zugeordneten Repositorys filtern. Beide Qualifizierer arbeiten mit [„Größer als“-, „Kleiner als“- und Bereichsqualifizierern](/articles/understanding-the-search-syntax). diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 78f7111387..fc6c2bb2ac 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -8,7 +8,9 @@ versions: ### Informationen zur Abrechnung für {% data variables.product.prodname_actions %} -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} + +{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." Minuten werden jeden Monat zurückgesetzt, während Speichernutzung dies nicht tut. @@ -69,8 +71,8 @@ Deine {% data variables.product.prodname_actions %}-Nutzung teilt das bestehende ### Über Ausgabenlimits -Standardmäßig wird Dein Konto ein Ausgabenlimit von 0 $ für die Nutzung von {% data variables.product.prodname_actions %} haben. Um die Nutzung von Minuten und Speicher für private Repositories über die Kontingente Deines Kontos hinaus zu ermöglichen, kannst Du das Ausgabenlimit erhöhen oder unbegrenzte Ausgaben zulassen. Weitere Informationen findest Du unter „[Ausgabenlimits für {% data variables.product.prodname_actions %} verwalten](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)." +{% data reusables.github-actions.actions-spending-limit-detailed %} -{% data reusables.github-actions.spending-limit-enterprise-account %} +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 reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 2e1963a2a6..32b5054987 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -10,6 +10,8 @@ versions: {% data reusables.package_registry.packages-billing %} +{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." + {% data reusables.package_registry.container-registry-beta-billing-note %} Die Datenübertragung wird jeden Monat zurückgesetzt, während Speichernutzung dies nicht tut. @@ -50,8 +52,8 @@ Deine {% data variables.product.prodname_registry %}-Nutzung teilt das bestehend ### Über Ausgabenlimits -Standardmäßig wird Dein Konto ein Ausgabenlimit von 0 $ für die Nutzung von {% data variables.product.prodname_registry %} haben. Um die Nutzung von Speicher und Datenübertragung für private Pakete über die Kontingente Deines Kontos hinaus zu ermöglichen, kannst Du das Ausgabenlimit erhöhen oder unbegrenzte Ausgaben zulassen. Weitere Informationen findest Du unter „[Ausgabenlimit für {% data variables.product.prodname_registry %} verwalten](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." +{% data reusables.package_registry.packages-spending-limit-detailed %} -{% data reusables.package_registry.spending-limit-enterprise-account %} +For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md index ef1d245ede..99a7cd4f3e 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md @@ -9,6 +9,8 @@ versions: {% data reusables.sponsors.sponsorship-details %} +{% data reusables.sponsors.no-fees %} + {% data reusables.dotcom_billing.view-all-subscriptions %} ### Weiterführende Informationen 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 4e7030def2..e010eeacc4 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 @@ -18,11 +18,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. Weitere Informationen findest Du unter „[Ein Studentenentwicklungspaket beantragen](/articles/applying-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/teach-and-learn-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. Verifizierte akademische Fakultäten können {% data variables.product.prodname_team %} für den Unterricht oder die akademische Forschung beantragen. 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/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/). ### 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 b6a2029e96..4db4b616ee 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 @@ -7,24 +7,24 @@ versions: free-pro-team: '*' --- +{% 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 %} + ### Sponsoring herabstufen -Wenn Du ein Sponsoring herabstufst, wird die Änderung zum nächsten Abrechnungsdatum wirksam. {% data reusables.sponsors.no-refunds %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. Klicken Sie rechts auf der Seite neben der ausgewählten Stufe auf **Edit** (Bearbeiten). ![Schaltfläche „Edit tier" (Bearbeiten der Stufe)](/assets/images/help/billing/edit-tier-button.png) +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### Sponsoring beenden -Wenn Du ein Sponsoring beendest, wird die Änderung zum nächsten Abrechnungsdatum wirksam. {% data reusables.sponsors.no-refunds %} - {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.billing %} +{% 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/managing-your-spending-limit-for-github-actions.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 273c2e989c..cd6248a3dc 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -8,13 +8,15 @@ versions: ### Über Ausgabenlimits für {% data variables.product.prodname_actions %} -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} -Du kannst ein höheres Ausgabenlimit festlegen oder für einige Konten unbegrenzte Ausgaben zulassen. Wenn Du für Deine Organisation oder Dein Enterprise-Konto per Rechnung bezahlst, kannst Du für Überschreitungen im Voraus bezahlen, um ein höheres Ausgabenlimit festzulegen. Das Ausgabenlimit gilt für deine kombinierten Überschreitungen für {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %}. Weitere Informationen zur Preisgestaltung für {% data variables.product.prodname_actions %}-Nutzung findest du unter „[Über die Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." +{% data reusables.github-actions.actions-spending-limit-brief %} -Sobald Du ein Ausgabenlimit von über 0 $ gesetzt hast, bist Du für alle Überschreitungen verantwortlich, die in der Vergangenheit aufgetreten sind. Wenn Dein Unternehmen beispielsweise {% data variables.product.prodname_team %} verwendet, keine Überschreitungen zulässt, und Workflow-Artefakte erstellt, die Deinen Speicherverbrauch für den Monat von 1,9 GB auf 2,1 GB erhöht, wirst Du leicht mehr Speicher als die 2 GB nutzen, die Dein Produkt enthält. +{% 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)." -Da Du keine Überschreitungen zugelassen hast, wird Dein nächster Versuch, eine Version des Pakets zu veröffentlichen, fehlschlagen. Du wirst keine Rechnung für die Überschreitung um 0,1 GB für diesen Monat erhalten. Wenn Du jedoch Überschreitungen in einem zukünftigen Monat aktivierst, wird Deine erste Rechnung die 0,1 GB Überschreitung der Vergangenheit enthalten, zusätzlich zu allen Überschreitungen für den aktuellen Abrechnungszeitraum. +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. Wenn Dein Unternehmen beispielsweise {% data variables.product.prodname_team %} verwendet, keine Überschreitungen zulässt, und Workflow-Artefakte erstellt, die Deinen Speicherverbrauch für den Monat von 1,9 GB auf 2,1 GB erhöht, wirst Du leicht mehr Speicher als die 2 GB nutzen, die Dein Produkt enthält. + +Because you have not enabled overages, your next attempt to create a workflow artifact will fail. Du wirst keine Rechnung für die Überschreitung um 0,1 GB für diesen Monat erhalten. 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. ### Das Ausgabenlimit für {% data variables.product.prodname_actions %} für Dein Benutzerkonto verwalten @@ -30,8 +32,6 @@ Jeder kann das Ausgabenlimit für {% data variables.product.prodname_actions %} Organisationsinhaber und Abrechnungsmanager können das Ausgabenlimit von {% data variables.product.prodname_actions %} für eine Organisation verwalten. -Wenn Du Dein Organisationskonto per Rechnung bezahlst, kannst Du das Ausgabenlimit für dieses Konto auf {% data variables.product.product_name %} nicht verwalten. Wenn Du Repositorys im Besitz Deiner Organisation erlauben willst, {% data variables.product.prodname_actions %} über die in ihren Konten enthaltenen Speicher oder Datenübertragungen hinaus zu benutzen, kannst Du für Überschreitungen im Voraus bezahlen. Da Überschreitungen im Voraus bezahlt werden müssen, kannst Du keine unbegrenzten Ausgaben für Konten aktivieren, die per Rechnung bezahlt werden. Dein Ausgabenlimit beträgt 150 % des Betrags, den Du im Voraus bezahlt hast. Wenn Du Fragen hast, [wende Dich an unser Kundendienstteam](https://enterprise.github.com/contact). - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ Wenn Du Dein Organisationskonto per Rechnung bezahlst, kannst Du das Ausgabenlim Enterprise-Inhaber und Abrechnungsmanager können das Ausgabenlimit von {% data variables.product.prodname_actions %} für ein Enterprise-Konto verwalten. -{% data reusables.github-actions.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 311573263d..d6cadae2cc 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/de-DE/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -10,11 +10,13 @@ versions: {% data reusables.package_registry.packages-billing %} -Du kannst ein höheres Ausgabenlimit festlegen oder für einige Konten unbegrenzte Ausgaben zulassen. Wenn Du für Deine Organisation oder Dein Enterprise-Konto per Rechnung bezahlst, kannst Du für Überschreitungen im Voraus bezahlen, um ein höheres Ausgabenlimit festzulegen. Das Ausgabenlimit gilt für deine kombinierten Überschreitungen für {% data variables.product.prodname_registry %} und {% data variables.product.prodname_actions %}. Weitere Informationen zur Preisgestaltung für {% data variables.product.prodname_registry %}-Nutzung findest du unter „[Über die Abrechnung für {% 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-spending-limit-brief %} -Sobald Du ein Ausgabenlimit von über 0 $ gesetzt hast, bist Du für alle Überschreitungen verantwortlich, die in der Vergangenheit aufgetreten sind. Wenn Dein Unternehmen beispielsweise {% data variables.product.prodname_team %} verwendet, keine Überschreitungen zulässt, und Workflow-Artefakte erstellt, die Deinen Speicherverbrauch für den Monat von 1,9 GB auf 2,1 GB erhöht, wird die Veröffentlichung leicht mehr Speicher als die 2 GB nutzen, die Dein Produkt enthält. +{% 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)." -Da Du keine Überschreitungen zugelassen hast, wird Dein nächster Versuch, eine Version des Pakets zu veröffentlichen, fehlschlagen. Du wirst keine Rechnung für die Überschreitung um 0,1 GB für diesen Monat erhalten. Wenn Du jedoch Überschreitungen in einem zukünftigen Monat aktivierst, wird Deine erste Rechnung die 0,1 GB Überschreitung der Vergangenheit enthalten, zusätzlich zu allen Überschreitungen für den aktuellen Abrechnungszeitraum. +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. Wenn Dein Unternehmen beispielsweise {% data variables.product.prodname_team %} verwendet, keine Überschreitungen zulässt, und Workflow-Artefakte erstellt, die Deinen Speicherverbrauch für den Monat von 1,9 GB auf 2,1 GB erhöht, wird die Veröffentlichung leicht mehr Speicher als die 2 GB nutzen, die Dein Produkt enthält. + +Da Du keine Überschreitungen zugelassen hast, wird Dein nächster Versuch, eine Version des Pakets zu veröffentlichen, fehlschlagen. Du wirst keine Rechnung für die Überschreitung um 0,1 GB für diesen Monat erhalten. 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. ### Das Ausgabenlimit für {% data variables.product.prodname_registry %} für Dein Benutzerkonto verwalten @@ -30,8 +32,6 @@ Jeder kann das Ausgabenlimit für {% data variables.product.prodname_registry %} Organisationsinhaber und Abrechnungsmanager können das Ausgabenlimit von {% data variables.product.prodname_registry %} für eine Organisation verwalten. -Wenn Du Dein Organisationskonto per Rechnung bezahlst, kannst Du das Ausgabenlimit für dieses Konto auf {% data variables.product.product_name %} nicht verwalten. Wenn Du Repositorys im Besitz Deiner Organisation erlauben willst, {% data variables.product.prodname_registry %} über die in ihren Konten enthaltenen Speicher oder Datenübertragungen hinaus zu benutzen, kannst Du für Überschreitungen im Voraus bezahlen. Da Überschreitungen im Voraus bezahlt werden müssen, kannst Du keine unbegrenzten Ausgaben für Konten aktivieren, die per Rechnung bezahlt werden. Dein Ausgabenlimit beträgt 150 % des Betrags, den Du im Voraus bezahlt hast. Wenn Du Fragen hast, [wende Dich an unser Kundendienstteam](https://enterprise.github.com/contact). - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ Wenn Du Dein Organisationskonto per Rechnung bezahlst, kannst Du das Ausgabenlim Enterprise-Inhaber und Abrechnungsmanager können das Ausgabenlimit von {% data variables.product.prodname_registry %} für ein Enterprise-Konto verwalten. -{% data reusables.package_registry.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 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 3c894c01ca..4cebdf56d4 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 @@ -7,12 +7,15 @@ versions: free-pro-team: '*' --- -Wenn Du Dein Sponsoring heraufstufst, wird die Änderung sofort wirksam. {% data reusables.sponsors.prorated-sponsorship %} +{% data reusables.sponsors.org-sponsors-release-phase %} -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. Klicken Sie rechts auf der Seite neben der ausgewählten Stufe auf **Edit** (Bearbeiten). ![Schaltfläche „Edit tier" (Bearbeiten der Stufe)](/assets/images/help/billing/edit-tier-button.png) +### About sponsorship upgrades + +Wenn Sie Ihr Sponsoring upgraden, wird die Änderung sofort wirksam. {% data reusables.sponsors.prorated-sponsorship %} + +### Sponsoring upgraden + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.update-sponsorship %} +{% data reusables.sponsors.update-sponsorship %} \ No newline at end of file diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md index f665191f58..a0e143f30f 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md @@ -20,7 +20,7 @@ versions: ### 1. Sichere die Inhalte Deiner Organisation -Wenn Du eine Organisation gelöscht hast, kann GitHub **Deine Inhalte nicht wiederherstellen.**. Bevor Du also Deine Organisation löschst, stelle sicher, dass Du eine Kopie aller Repositorys, Wikis und Issues des Kontos besitzt. +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 diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md index 34dbb9b4ab..6e9202b6f5 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -19,4 +19,4 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.oauth_app_access %} 5. 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). ![Schaltfläche „Remove confirmation" (Bestätigen der Entfernung)](/assets/images/help/settings/settings-third-party-confirm-disable.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/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md index f7af313fee..0e3b701d17 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -20,42 +20,30 @@ versions: {% link_in_list /creating-a-new-organization-from-scratch %} {% link_in_list /accessing-your-organizations-settings %} {% link_in_list /about-your-organizations-news-feed %} - {% link_in_list /viewing-insights-for-your-organization %} - {% topic_link_in_list /managing-membership-in-your-organization %} - {% link_in_list /inviting-users-to-join-your-organization %} {% link_in_list /canceling-or-editing-an-invitation-to-join-your-organization %} {% link_in_list /adding-people-to-your-organization %} - {% link_in_list /removing-a-member-from-your-organization %} {% link_in_list /reinstating-a-former-member-of-your-organization %} - {% link_in_list /can-i-create-accounts-for-people-in-my-organization %} - {% topic_link_in_list /managing-peoples-access-to-your-organization-with-roles %} {% link_in_list /permission-levels-for-an-organization %} {% link_in_list /maintaining-ownership-continuity-for-your-organization %} {% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %} - {% link_in_list /adding-a-billing-manager-to-your-organization %} {% link_in_list /removing-a-billing-manager-from-your-organization %} - {% link_in_list /removing-a-billing-manager-from-your-organization %} {% 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 %} @@ -66,9 +54,7 @@ versions: {% topic_link_in_list /managing-access-to-your-organizations-repositories %} {% link_in_list /repository-permission-levels-for-an-organization %} {% link_in_list /setting-base-permissions-for-an-organization %} - {% link_in_list /viewing-people-with-access-to-your-repository %} - {% link_in_list /managing-an-individuals-access-to-an-organization-repository %} {% link_in_list /managing-team-access-to-an-organization-repository %} {% link_in_list /adding-outside-collaborators-to-repositories-in-your-organization %} @@ -84,83 +70,54 @@ versions: {% link_in_list /managing-an-individuals-access-to-an-organization-project-board %} {% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %} {% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %} - {% topic_link_in_list /managing-access-to-your-organizations-apps %} {% link_in_list /adding-github-app-managers-in-your-organization %} {% link_in_list /removing-github-app-managers-from-your-organization %} - {% topic_link_in_list /managing-organization-settings %} - {% link_in_list /verifying-your-organizations-domain %} - {% link_in_list /renaming-an-organization %} {% link_in_list /transferring-organization-ownership %} {% link_in_list /restricting-repository-creation-in-your-organization %} {% link_in_list /setting-permissions-for-deleting-or-transferring-repositories %} {% link_in_list /restricting-repository-visibility-changes-in-your-organization %} {% link_in_list /managing-the-forking-policy-for-your-organization %} - {% link_in_list /disabling-or-limiting-github-actions-for-your-organization %} {% link_in_list /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 %} - - + {% link_in_list /allowing-people-to-delete-issues-in-your-organization %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /managing-discussion-creation-for-repositories-in-your-organization %}{% endif %} {% link_in_list /setting-team-creation-permissions-in-your-organization %} - - {% link_in_list /managing-scheduled-reminders-for-your-organization %} - - {% link_in_list /managing-the-default-branch-name-for-repositories-in-your-organization %} - - {% link_in_list /managing-default-labels-for-repositories-in-your-organization %} - - {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} - - {% link_in_list /managing-the-display-of-member-names-in-your-organization %} - + {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} - {% link_in_list /integrating-jira-with-your-organization-project-board %} - - {% link_in_list /upgrading-to-the-corporate-terms-of-service %} - {% topic_link_in_list /migrating-to-improved-organization-permissions %} {% link_in_list /converting-an-owners-team-to-improved-organization-permissions %} {% link_in_list /converting-an-admin-team-to-improved-organization-permissions %} {% link_in_list /migrating-admin-teams-to-improved-organization-permissions %} - {% topic_link_in_list /restricting-access-to-your-organizations-data %} {% link_in_list /about-oauth-app-access-restrictions %} {% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /approving-oauth-apps-for-your-organization %} {% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %} - {% topic_link_in_list /keeping-your-organization-secure %} {% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %} {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} - {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} {% link_in_list /managing-secret-scanning-for-your-organization %} - {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} - {% link_in_list /restricting-email-notifications-to-an-approved-domain %} - {% link_in_list /reviewing-the-audit-log-for-your-organization %} {% link_in_list /reviewing-your-organizations-installed-integrations %} - {% topic_link_in_list /managing-saml-single-sign-on-for-your-organization %} {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} {% link_in_list /about-scim %} @@ -170,17 +127,12 @@ versions: {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} {% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %} - {% link_in_list /managing-team-synchronization-for-your-organization %} - {% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %} {% topic_link_in_list /granting-access-to-your-organization-with-saml-single-sign-on %} {% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %} {% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %} - - {% topic_link_in_list /managing-git-access-to-your-organizations-repositories %} {% link_in_list /about-ssh-certificate-authorities %} {% link_in_list /managing-your-organizations-ssh-certificate-authorities %} - diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..e389d8c0b4 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Managing discussion creation for repositories in your organization +intro: You can choose the permission levels that members require to create discussions in repositories owned by your organization. +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Allowing or disallowing users with read access to create discussions + +By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. 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/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index cea3fa740d..06737d53fe 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -9,29 +9,39 @@ versions: ### About management of security and analysis settings {% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. - {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% endif %} - -### Enabling or disabling features for existing repositories +### 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 %} -5. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -6. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) -### Enabling or disabling features for new repositories +The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. + +### Enabling or disabling a feature for all existing repositories + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) +1. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) +1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + +### Enabling or disabling a feature for all new repositories when they are added + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + +### Allowing Dependabot to access private repositories + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) +1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. +1. Click **Select repositories**. -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..11703e2205 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,23 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +--- + +{% 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)" \ No newline at end of file diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 90559508e4..af053937e7 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -55,6 +55,9 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late | Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} | Die Anzeige von Abhängigkeiten-Einblicke einer Organisation verwalten (siehe „[Die Sichtbarkeit der Abhängigkeiten-Einblicke Deiner Organisation ändern](/articles/changing-the-visibility-of-your-organizations-dependency-insights)“) | **X** | | |{% endif %} | 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](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | | Manage security and analysis settings (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)" for details) | **X** | | | | [SAML Single Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on) aktivieren und erzwingen | **X** | | | diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 46fe98c8f3..0108aee948 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -114,7 +114,19 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben | [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** | +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} ### Weiterführende Informationen diff --git a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 1c3a69af50..fcb5bd5ba7 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/de-DE/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -81,7 +81,9 @@ Each category has a set of associated actions that you can filter on. For exampl Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} -{% data reusables.search.date_gt_lt %} For example: +{% data reusables.search.date_gt_lt %} + +For example: * `created:2014-07-08` finds all events that occurred on July 8th, 2014. * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. @@ -105,25 +107,53 @@ Using the qualifier `country`, you can filter events in the audit log based on t {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -### Using the Audit log API +### 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 API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} +**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 API to keep copies of your audit log data and monitor: -* Access to your organization or repository settings. -* Changes in permissions. -* Added or removed users in an organization, repository, or team. -* Users being promoted to admin. -* Changes to permissions of a GitHub App. +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. +{% 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 as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +{% 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)" in the REST API documentation. + +{% endif %} + ### Audit log actions An overview of some of the most common actions that are recorded as events in the audit log. @@ -213,6 +243,28 @@ An overview of some of the most common actions that are recorded as events in th | `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). +{% 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. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| Action | Description +|---------|---------------------------- +| `clone` | Triggered when a repository is cloned. +| `fetch` | Triggered when changes are fetched from a repository. +| `push` | Triggered when changes are pushed to a repository. + +{% endif %} + #### `hook` category actions | Action | Description @@ -500,8 +552,20 @@ For more information, see "[Restricting publication of {% data variables.product | 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)") +| `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 organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") +| 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 %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index 0cf94c216b..75b55ac4db 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and{% endif %}private repositories, with specific details of your activity in private repositories anonymized. Weitere Informationen finden Sie unter „[Private Beiträge in Ihrem Profil veröffentlichen oder verbergen](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)“. +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. Weitere Informationen finden Sie unter „[Private Beiträge in Ihrem Profil veröffentlichen oder verbergen](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)“. {% note %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/index.md index 41119a4ada..7d38dd5993 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/index.md @@ -14,41 +14,28 @@ versions: {% topic_link_in_list /managing-user-account-settings %} {% link_in_list /about-your-personal-dashboard %} + {% link_in_list /managing-your-theme-settings %} {% link_in_list /changing-your-github-username %} - {% link_in_list /merging-multiple-user-accounts %} {% link_in_list /converting-a-user-into-an-organization %} - {% link_in_list /deleting-your-user-account %} {% link_in_list /permission-levels-for-a-user-account-repository %} {% link_in_list /permission-levels-for-user-owned-project-boards %} {% link_in_list /managing-the-default-branch-name-for-your-repositories %} {% link_in_list /managing-security-and-analysis-settings-for-your-user-account %} - {% link_in_list /managing-access-to-your-user-accounts-project-boards %} - + {% link_in_list /managing-access-to-your-user-accounts-project-boards %} {% link_in_list /integrating-jira-with-your-personal-projects %} - - {% link_in_list /best-practices-for-leaving-your-company %} - - {% link_in_list /what-does-the-available-for-hire-checkbox-do %} - {% topic_link_in_list /managing-email-preferences %} {% link_in_list /adding-an-email-address-to-your-github-account %} {% link_in_list /changing-your-primary-email-address %} {% link_in_list /setting-a-backup-email-address %} {% link_in_list /setting-your-commit-email-address %} - {% link_in_list /blocking-command-line-pushes-that-expose-your-personal-email-address %} - {% link_in_list /remembering-your-github-username-or-email %} - {% link_in_list /types-of-emails-github-sends %} - - {% link_in_list /managing-marketing-emails-from-github %} - {% topic_link_in_list /managing-access-to-your-personal-repositories %} {% link_in_list /inviting-collaborators-to-a-personal-repository %} {% link_in_list /removing-a-collaborator-from-a-personal-repository %} @@ -58,9 +45,7 @@ versions: {% link_in_list /about-organization-membership %} {% link_in_list /accessing-an-organization %} {% link_in_list /viewing-peoples-roles-in-an-organization %} - {% link_in_list /requesting-organization-approval-for-oauth-apps %} - {% link_in_list /publicizing-or-hiding-organization-membership %} {% link_in_list /managing-your-scheduled-reminders %} {% link_in_list /removing-yourself-from-an-organization %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md new file mode 100644 index 0000000000..fc29fa5774 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -0,0 +1,22 @@ +--- +title: Managing your theme settings +intro: You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode. +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Theme settings is currently in beta and subject to change. + +{% endnote %} + +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. + +{% data reusables.user_settings.access_settings %} +1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) + +### Weiterführende Informationen + +- „[Design für {% data variables.product.prodname_desktop %} festlegen](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)“ diff --git a/translations/de-DE/content/github/site-policy/github-additional-product-terms.md b/translations/de-DE/content/github/site-policy/github-additional-product-terms.md index 8baf03897b..496257fdb2 100644 --- a/translations/de-DE/content/github/site-policy/github-additional-product-terms.md +++ b/translations/de-DE/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: November 13, 2020 +Version Effective Date: December 14, 2020 Wenn Sie ein Konto erstellen, erhalten Sie Zugriff auf viele verschiedene Features und Produkte, die alle Teil des Dienstes sind. Da viele dieser Features und Produkte unterschiedliche Funktionen bieten, erfordern sie möglicherweise zusätzliche Geschäftsbedingungen, die für dieses Feature oder dieses Produkt spezifisch sind. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -46,13 +46,11 @@ GitHub Pages unterliegen Bandbreiten- und Nutzungsbeschränkungen und sind für ### 5. Actions und Pakete #### a. Verwendung von Actions -GitHub Actions ermöglicht es Ihnen, benutzerdefinierte Softwareentwicklungs-Lebenszyklus-Workflows direkt in Ihrem GitHub Repository zu erstellen. Each Account comes with included compute and storage quantities for use with Actions, depending on your Account plan, which can be found in the [Actions documentation](/actions). Your Actions compute usage is displayed within [your account settings](https://github.com/settings/billing), and you will be notified by email in advance of reaching the limit of your included quantities. Wenn Sie Actions über die in Ihrem Paket enthaltenen Datenmengen hinaus verwenden möchten, können Sie [enable overages (Überschreitungen aktivieren)](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions) aktivieren. +GitHub Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. -Die Nutzungsberechnung für enthaltene und bezahlte Mengen wird in Minuten anhand der Art von Aktionen berechnet, die Sie ausführen (z.B. Linux, Windows, macOS). Die Minuten, die für den Auftrag oder die Aufgabe jeder Aktion verwendet werden, werden auf die nächste Minute aufgerundet. Bei inbegriffenen Mengen und abhängig von der Art der Aktion kann ein Multiplikator auf die Zeit angewandt werden, die für die Ausführung jedes Auftrags oder jeder Aufgabe benötigt wird, bevor auf die nächste Minute aufgerundet wird. Zusätzliche Minuten werden zum [angegebenen Preis pro Minute ](https://github.com/features/actions) basierend auf der Art der von Ihnen ausgeführten Aktionen berechnet. Actions und Packages teilen sich Speicher, und Ihre Speichernutzung wird in Ihren [Kontoeinstellungen](https://github.com/settings/billing) angezeigt. For additional details about included quantity usage calculations, see the [Actions documentation](/actions). - -Actions und jegliche Elemente des Action-Dienstes dürfen nicht unter Missachtung der Vereinbarung, der [Richtlinie für die zulässige Verwendung](/github/site-policy/github-acceptable-use-policies), oder der GitHub-Actions [Diensteinschränkungen](/actions/reference/usage-limits-billing-and-administration/#usage-limits) verwendet werden. Actions sollte außerdem nicht für Folgendes verwendet werden: +Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions). Actions sollte außerdem nicht für Folgendes verwendet werden: - cryptomining; -- die Nutzung unserer Server, um Dienste, Geräte, Daten, Konten oder Netzwerke zu stören oder zu versuchen, diese zu stören, oder um unbefugten Zugang zu erlangen oder dies zu versuchen (es sei denn, dies wurde im Rahmen des [GitHub Bug Bounty-Programms](https://bounty.github.com) genehmigt) +- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); - the provision of a stand-alone or integrated application or service offering Actions or any elements of Actions for commercial purposes; - any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or - jegliche weiteren Aktivitäten ohne Bezug zu Produktion, Tests, Bereitstellung oder Veröffentlichung des Software-Projekts, das mit dem Repository verknüpft ist, in dem GitHub Actions verwendet werden. @@ -60,16 +58,7 @@ Actions und jegliche Elemente des Action-Dienstes dürfen nicht unter Missachtun Um Verstöße gegen diese Einschränkungen und Missbrauch von GitHub Actions zu verhindern, kann GitHub Ihre Verwendung von GitHub Actions überwachen. Der Missbrauch von GitHub Actions kann zur Kündigung von Aufträgen oder zu Beschränkungen Ihrer Möglichkeiten bei der Nutzung von GitHub Actions führen. #### b. Verwendung von Packages -GitHub Packages kann zum Herunterladen, Veröffentlichen und Verwalten von Content-Paketen verwendet werden. Jeder Kontoplan umfasst die mitgelieferten Bandbreiten- und Speichermengen für die Verwendung mit Packages, entsprechend der [Packages-Dokumentation](/github/managing-packages-with-github-package-registry/about-github-package-registry). Der Speicherplatz für Actions und Packages wird von den beiden Dienst-Funktionen gemeinsam genutzt. Die Speicher- und Bandbreitennutzung wird unter [Kontoeinstellungen](https://github.com/settings/billing) angezeigt, und Sie werden per E-Mail benachrichtigt, bevor Sie das Limit Ihrer inbegriffenen Menge erreichen. Wenn Sie Packages über die in Ihrem Paket enthaltenen Bandbreiten- und Speichermengen hinaus verwenden möchten, können Sie [Überschreitungen aktivieren](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages) aktivieren. - -Die Bandbreitennutzung wird auf der Grundlage der Datenmenge berechnet, die über Packages aus Ihren Repositorys übertragen wird, jedoch zählen Package-Transfers über Actions nicht zu Ihren inkludierten oder bezahlten Mengen. Packages bandwidth usage is limited by the [Acceptable Use Policy](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use), and included bandwidth quantities are determined by your [account plan](https://github.com/pricing). - -Der Speicherplatz für Actions und Packages wird von den beiden Dienst-Funktionen gemeinsam genutzt. Die Speichernutzung wird im Laufe des Monats als gewichteter Durchschnitt berechnet und nicht jeden Monat zurückgesetzt. Public and private repositories have different included storage quantities, and the included quantities for private repositories depend on your [account plan](https://github.com/pricing). - -#### c. Zahlung und Abrechnung für Actions und Packages -Die Abrechnung für Actions und Packages erfolgt auf Basis der Nutzung. Zusätzliche Mengen von Actions oder Packages können nicht separat erworben werden. Als Kunde mit monatlicher Rechnungsstellung müssen Sie eine Zahlungsart hinterlegt haben, mit der Sie für zusätzliche Mengen dieser Servicefunktionen zahlen können. Die Abrechnung erfolgt auf monatlicher, fortlaufender Basis auf der Grundlage Ihres Verbrauchs im Vormonat, es sei denn, die Abrechnung erfolgt per Rechnung. Rechnungskunden müssen die Gebühren innerhalb von dreißig (30) Tagen ab dem Datum der GitHub-Rechnung zahlen. Für Kunden, die für Service-Feature-Überschreitungen im Voraus bezahlen, werden nicht verwendete Prepaid-Minuten nicht auf den nächsten Abrechnungszeitraum übertragen und nicht zurückerstattet. - -Sie können ein monatliches Ausgabelimit Ihren [Kontoeinstellungen](https://github.com/settings/billing/cost_management) festlegen. Sie werden im Voraus per E-Mail benachrichtigt, wenn Sie die Grenze Ihrer enthaltenen Mengen und die angegebene Ausgabengrenze Ihrer bezahlten Zusatzmengen erreichen. +GitHub Packages is billed on a usage basis. The [Packages documentation](/packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies). ### 6. Learning Lab @@ -108,3 +97,13 @@ We need the legal right to submit your contributions to the GitHub Advisory Data #### b. Lizenz für das GitHub Advisory Database The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by . + +### 13. GitHub Enterprise Server + +#### a. SQL Server Images + +You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Die Microsoft Corporation kann SQL Server-Images jederzeit deaktivieren. + +#### b. Third-party components + +Die Software umfasst Komponenten, für die Dritte GitHub eine Lizenz gewähren. Dazu zählt auch Software, für die GitHub den Quellcode der entsprechenden Komponenten verfügbar machen muss. Der Quellcode entsprechender Komponenten wird auf Anfrage bereitgestellt. diff --git a/translations/de-DE/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/de-DE/content/github/site-policy/github-enterprise-service-level-agreement.md index 15059a6ed8..7bd6578655 100644 --- a/translations/de-DE/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/de-DE/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -8,22 +8,22 @@ versions: free-pro-team: '*' --- -**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the GitHub Enterprise Cloud service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). +**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the applicable GitHub service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). -For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. +For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. ## Uptime Guarantee -“**Uptime**” is the percentage of total possible minutes the Service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the Service. The Uptime calculation for each Service Feature is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. +“**Uptime**” is the percentage of total possible minutes the applicable GitHub service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service. The Uptime calculation for each Service Feature that may be included with the applicable GitHub service is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. -| **Service Feature** | **Uptime Calculation** | **Definitionen** | **Service Credits Calculation** | -| --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -| The **Service** includes the following Service Features:
  • Issues
  • Pull Requests
  • Git Operations
  • API Requests
  • Webhooks
  • Pages
  • Actions
  • Packages
| (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
  • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than 99.9%, but greater than 99.0%.

    OR

  • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
| | -| **Actions** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

“**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | -| **Packages** | Transfers Uptime = same as Actions

Storage Uptime = 100% - Average Error Rate*

*The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

“**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | +| **Service Feature** | **Uptime Calculation** | **Definitionen** | **Service Credits Calculation** | +| -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | +| **Issues**,
**Pull Requests**,
**Git Operations**,
**API Requests**,
**Webhooks**,
**Pages** | (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
  • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than 99.9%, but greater than 99.0%.

    OR

  • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
| | +| **Actions** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

“**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | +| **Packages** | Transfers Uptime = same as Actions

Storage Uptime = 100% - Average Error Rate*

*The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

“**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | ## Ausnahmen -Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. +Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the applicable GitHub service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Service Credits Redemption If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). diff --git a/translations/de-DE/content/github/site-policy/github-registered-developer-agreement.md b/translations/de-DE/content/github/site-policy/github-registered-developer-agreement.md index e603b1c91e..901d4a7fee 100644 --- a/translations/de-DE/content/github/site-policy/github-registered-developer-agreement.md +++ b/translations/de-DE/content/github/site-policy/github-registered-developer-agreement.md @@ -86,7 +86,7 @@ Diese Vereinbarung ist eine rechtliche Vereinbarung zwischen Ihnen ("Sie") und G 13. **Eigentumsrechte** - Sie erklären sich damit einverstanden, dass GitHub und seine Lizenzgeber alle Rechte, Titel und Anteile an des API, den Pre-Release-Materialien und allen anderen GitHub-Produkten und Diensten, alle Informationen und Daten in Bezug auf ihre Konfigurationen und Kombinationen sowie alle Änderungen an und Bearbeitungen von den vorgenannten Produkten und Diensten besitzen. Sie dürfen keine Urheberrechts- oder andere Eigentumsrechtshinweise, die wir auf dem API, Pre-Release-Materialien oder anderen Produkten und Diensten von GitHub setzen oder integrieren, entfernen, verändern, verdecken oder verschleiern. + Sie erklären sich damit einverstanden, dass GitHub und seine Lizenzgeber alle Rechte, Titel und Anteile an des API, den Pre-Release-Materialien und allen anderen GitHub-Produkten und Diensten, alle Informationen und Daten in Bezug auf ihre Konfigurationen und Kombinationen sowie alle Änderungen an und Bearbeitungen von den vorgenannten Produkten und Diensten besitzen. You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services. 14. **Benutzer von Regierungsbehörden** 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 f9226848ae..33d7eba808 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 @@ -9,7 +9,9 @@ versions: ### Informationen zu {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.sponsorship-details %}{% data reusables.sponsors.no-fees %} Weitere Informationen findest Du unter „[ Informationen zur Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." +{% data reusables.sponsors.sponsorship-details %} + +{% 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)“. {% data reusables.sponsors.you-can-be-a-sponsored-developer %} Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_sponsors %} für Open-Source-Mitwirkende](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" und „[{% data variables.product.prodname_sponsors %} für Dein Benutzerkonto einrichten](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)." @@ -25,7 +27,7 @@ Wenn du ein unterstützter Entwickler oder eine unterstütze Organisation wirst, {% endnote %} -Der {% data variables.product.prodname_matching_fund %} zielt darauf ab, Mitgliedern der {% data variables.product.prodname_dotcom %}-Community zu helfen, die Open-Source-Software entwickeln, welche die [{% data variables.product.prodname_dotcom %}-Community-Richtlinien](/github/site-policy/github-community-guidelines) fördert. Unterstützte Organisationen sind nicht für {% data variables.product.prodname_matching_fund %} berechtigt. +Der {% data variables.product.prodname_matching_fund %} zielt darauf ab, Mitgliedern der {% data variables.product.prodname_dotcom %}-Community zu helfen, die Open-Source-Software entwickeln, welche die [{% data variables.product.prodname_dotcom %}-Community-Richtlinien](/github/site-policy/github-community-guidelines) fördert. Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}. Um für {% data variables.product.prodname_matching_fund %} berechtigt zu sein, musst Du ein Profil erstellen, das eine Community anzieht, die Dich langfristig unterstützen wird. Weitere Informationen zur Erstellung eines guten Profils findest Du unter „[Deine Profildetails für {% data variables.product.prodname_sponsors %} bearbeiten](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)." @@ -35,8 +37,6 @@ Um für {% data variables.product.prodname_matching_fund %} berechtigt zu sein, 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. -Derzeit können nur Einzelpersonen Entwickler und Organisationen unterstützen. Wenn Deine Organisation daran interessiert ist, Entwickler zu unterstützen, lass uns wissen, indem Du uns über [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors) kontaktierst. - ### Weiterführende Informationen - „[Unterstützung von Open-Source-Mitarbeitern](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" - „[Sponsoring durch {% data variables.product.prodname_sponsors %} erhalten](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)" diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md new file mode 100644 index 0000000000..57b1b5a4d6 --- /dev/null +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md @@ -0,0 +1,13 @@ +--- +title: Attributing sponsorships to your organization +intro: 'You can attribute the sponsorships paid by one of your organizations to another organization.' +versions: + free-pro-team: '*' +permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization. +--- + +1. Navigate to the organization whose sponsorships you want to attribute to another organization. +1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png) +1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png) +1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png) +1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md index 2b5862f9c8..9ffddba745 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -13,38 +13,20 @@ versions: {% data reusables.sponsors.maximum-tier %} -### Deinem „unterstützter Entwickler"-Profil eine Stufe hinzufügen +### Eine Stufe hinzufügen -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} -### Deinem „unterstützte Organisation"-Profil eine Stufe hinzufügen +### Editing or retiring a tier -{% data reusables.sponsors.navigate-to-org-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 %} - -### Eine Stufe in Deinem „unterstützter Entwickler"-Profil bearbeiten oder zurückziehen - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} - -### Eine Stufe in Deinem „unterstützte Organisation"-Profil bearbeiten oder zurückziehen - -{% data reusables.sponsors.navigate-to-org-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 %} +{% data reusables.sponsors.retire-tier %} \ No newline at end of file diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md index a2e73d7a30..20448972dd 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md @@ -5,11 +5,13 @@ versions: free-pro-team: '*' --- -Damit Du Änderungen wie zum Beispiel die Kündigung eines Sponsorings am Ende der Zahlungsperiode überwachen kannst, kannst Du Webhooks für Deine unterstützten Benutzer- oder Organisations-Konten erstellen. Wenn Du einen Webhook für Dein unterstütztes Benutzer- oder Organisationskonto einrichtest, erhältst Du Updates, wenn Sponsorings erstellt, bearbeitet oder gelöscht werden. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship). +### About webhooks for events in your sponsored account -### Webhooks für Dein unterstütztes Benutzerkonto verwalten +Damit Du Änderungen wie zum Beispiel die Kündigung eines Sponsorings am Ende der Zahlungsperiode überwachen kannst, kannst Du Webhooks für Deine unterstützten Benutzer- oder Organisations-Konten erstellen. When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship). -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +### Managing webhooks for events in your sponsored account + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-webhooks-tab %} {% data reusables.sponsors.add-webhook %} {% data reusables.sponsors.add-payload-url %} @@ -17,18 +19,4 @@ Damit Du Änderungen wie zum Beispiel die Kündigung eines Sponsorings am Ende d {% data reusables.sponsors.webhook-secret-token %} {% data reusables.sponsors.add-active-triggers %} {% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} - -### Webhooks für Deine unterstützte Organisation verwalten - -Organisationsinhaber können Webhooks für unterstützte Organisationen konfigurieren. - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-webhooks-tab %} -{% data reusables.sponsors.add-webhook %} -{% data reusables.sponsors.add-payload-url %} -{% data reusables.sponsors.webhook-content-formatting %} -{% data reusables.sponsors.webhook-secret-token %} -{% data reusables.sponsors.add-active-triggers %} -{% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} +{% data reusables.sponsors.manage-existing-webhooks %} \ No newline at end of file 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 c166c3c940..697a21acb8 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 @@ -7,22 +7,15 @@ versions: free-pro-team: '*' --- +### About sponsorship updates + Deine Sponsoren können auswählen, ob sie per E-Mail über Deine Arbeit auf dem Laufenden gehalten werden möchten. Weitere Informationen findest Du unter „[Sponsoring verwalten](/articles/managing-your-sponsorship).“ -Die Aktualisierung erfolgt über die primäre E-Mail-Adresse Deines Benutzerkontos oder über die `noreply@github.com`-E-Mail-Adresse des Organisations-Kontos. 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. Weitere Informationen findest Du unter „[Deine Commit-E-Mail-Adresse festlegen](/articles/setting-your-commit-email-address).“ +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).“ -### Die Sponsoren Deines Benutzerkontos kontaktieren +### Deine Sponsoren kontaktieren -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.sponsors-updates-tab %} -{% data reusables.sponsors.draft-new-update %} -{% data reusables.sponsors.send-update-to-sponsors %} -{% data reusables.sponsors.write-sponsor-update %} -{% data reusables.sponsors.publish-sponsor-update %} - -### Die Sponsoren Deiner Organisation kontaktieren - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.sponsors-updates-tab %} {% data reusables.sponsors.draft-new-update %} {% data reusables.sponsors.send-update-to-sponsors %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md index 63a0d3c2a7..94797029bc 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md @@ -10,30 +10,17 @@ versions: ### Über Sponsoren-Profile -Dein {% data variables.product.prodname_sponsors %}-Profil informiert potentielle Sponsoren, warum sie Dich unterstützten sollten. Personen sehen Dein Sponsorenprofil, wenn sie auf die **Sponsor**-Schaltfläche auf Deinem persönlichen Profil oder dem Organisationsprofil klicken. Wir empfehlen Dir, die folgenden Informationen einzuschließen. +Dein {% data variables.product.prodname_sponsors %}-Profil informiert potentielle Sponsoren, warum sie Dich unterstützten sollten. People see your sponsor profile when they click the **Sponsor** button on your profile. Wir empfehlen Dir, die folgenden Informationen einzuschließen. -- Open-Source-Arbeit, zu der Du beiträgst. -- Warum Du Dich für Open-Source-Entwicklung einsetzt. +- Open-Source-Arbeit, zu der Du beiträgst +- Warum Du Dich für Open-Source-Entwicklung einsetzt -Du kannst auch Ziele setzen, um zu erklären, was die unterschiedlichen Ebenen des Sponsorings Dir erlauben werden, für die Community zu tun. +### Editing your profile details -### Profil für unterstützten Entwickler bearbeiten - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### Profil für unterstützte Organisation bearbeiten - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.meet-the-team %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} +{% data reusables.sponsors.save-profile %} \ No newline at end of file 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 5cee24fa9d..a13d432e72 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 @@ -16,6 +16,7 @@ versions: {% topic_link_in_list /sponsoring-open-source-contributors %} {% link_in_list /sponsoring-an-open-source-contributor %} {% link_in_list /managing-your-sponsorship %} + {% link_in_list /attributing-sponsorships-to-your-organization %} {% topic_link_in_list /receiving-sponsorships-through-github-sponsors %} {% link_in_list /about-github-sponsors-for-open-source-contributors %} {% link_in_list /setting-up-github-sponsors-for-your-user-account %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md index 4d4d61c512..2ed27f359d 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md @@ -13,14 +13,8 @@ Du kannst Deine Auszahlungen von {% data variables.product.prodname_sponsors %} {% data reusables.sponsors.payout-info %} -### Anzeigen und Bearbeiten von Auszahlungsinformationen für Dein unterstütztes Benutzerkonto +### Viewing and editing payout information -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} - -### Anzeigen und Bearbeiten von Auszahlungsinformationen für Dein unterstütztes Organisationskonto - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} +{% data reusables.sponsors.edit-bank-information %} \ No newline at end of file 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 f8ce7c02fb..e117c4cb0f 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 @@ -1,27 +1,19 @@ --- title: Deine Sponsoring-Ziele verwalten -intro: Du kannst Ziele für das Profil als unterstützter Entwickler oder als unterstützte Organisationen setzen, um der Community zu helfen, die Auswirkungen zu verstehen, die das Sponsorings auf Dich hat. +intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you. versions: free-pro-team: '*' --- ### Über Sponsoring-Ziele -Du kannst ein Finanzierungsziel für Dein unterstütztes Entwickler- oder Organisationsprofil festlegen und das Ziel mit Deiner Community teilen. Ziele helfen Dir, die Auswirkungen zu verstehen, die Du in der Open-Source-Community hast, und Deine Präsenz im {% data variables.product.prodname_sponsors %}-Programm zu erweitern. +You can set a funding goal for your sponsored account and share the goal with your community. Ziele helfen Dir, die Auswirkungen zu verstehen, die Du in der Open-Source-Community hast, und Deine Präsenz im {% data variables.product.prodname_sponsors %}-Programm zu erweitern. 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. -### Ein Ziel für eine unterstützte Organisation festlegen +### Setting a goal -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.set-a-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### Ein Ziel für einen unterstützten Entwickler setzen - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.set-a-goal %} {% data reusables.sponsors.select-goal-type %} @@ -31,6 +23,7 @@ Du kannst Ziele setzen für die Anzahl der Sponsoren, die Du suchst, oder die fi Wenn Du ein Ziel bearbeitest, kannst du kein Ziel wählen, das Du bereits erreicht hast. Wenn Du beispielsweise bereits 5 Sponsoren hast, kannst du Dein Ziel nicht dahingehend bearbeiten, dass Du nur 4 Sponsoren suchst. +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.select-goal-type %} @@ -40,6 +33,7 @@ Wenn Du ein Ziel bearbeitest, kannst du kein Ziel wählen, das Du bereits erreic Wenn Du ein Ziel zurückziehst, kannst Du es nicht mehr reaktivieren. Du musst stattdessen ein neues Ziel erstellen. +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.retire-goal %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md index b3168138d7..46b4f877c4 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -1,42 +1,35 @@ --- title: Sponsoring verwalten -intro: Du kannst verwalten, wer Dein Sponsoring sehen kann, und festlegen, ob Du per E-Mail Aktualisierungen von unterstützten Open-Source-Mitwirkenden erhalten möchtest. +intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account. redirect_from: - /articles/managing-your-sponsorship versions: free-pro-team: '*' --- -Weitere Informationen zum Ändern Deiner Sponsoring-Stufe findest Du unter „[Sponsoring heraufstufen](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship).“ +{% data reusables.sponsors.org-sponsors-release-phase %} -### Die Datenschutzeinstellung für Dein Entwickler-Sponsoring verwalten +### Die Datenschutzeinstellung für Ihr Sponsoring verwalten -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} {% data reusables.sponsors.who-can-see-your-sponsorship %} {% data reusables.sponsors.update-sponsorship %} -### Die Datenschutzeinstellung für Dein Organisations-Sponsoring verwalten +### Managing email updates for your sponsorship -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.who-can-see-your-sponsorship %} +You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address. + +{% data reusables.sponsors.manage-updates-for-orgs %} + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} +{% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.update-sponsorship %} -### E-Mail-Aktualisierungen eines unterstützten Entwicklers verwalten +### Weiterführende Informationen -Du kannst auswählen, ob ein unterstützter Entwickler Dir E-Mails mit Aktualisierungen zu seiner Arbeit senden darf. Der unterstützte Entwickler kann nicht auf Deine E-Mail-Adresse zugreifen. - -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} -{% data reusables.sponsors.developer-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} - -### E-Mail-Aktualisierungen einer unterstützten Organisation verwalten - -Du kannst auswählen, ob eine unterstützte Organisation Dir E-Mails mit Aktualisierungen zu ihrer Arbeit senden darf. Die unterstützten Organisation kann nicht auf Deine E-Mail-Adresse zugreifen. - -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.org-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} +- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" +- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)" \ No newline at end of file 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 0bb773fa38..151b82c082 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 @@ -25,7 +25,7 @@ Um {% data variables.product.prodname_sponsors %} als ein einzelner Mitwirkender ### Dein Profil als unterstützte Organisation vervollständigen -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ Um {% data variables.product.prodname_sponsors %} als ein einzelner Mitwirkender {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% 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 %} @@ -54,7 +54,7 @@ Als unterstützte Organisation musst Du Auszahlungen auf ein dediziertes Bankkon {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} For more information about setting up Stripe Connect using Open Collective, see [Setting up {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) in the Open Collective Docs. @@ -63,7 +63,7 @@ For more information about setting up Stripe Connect using Open Collective, see {% data reusables.sponsors.tax-form-information-org %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -75,7 +75,7 @@ Bevor Deine Organisation eine unterstütze Organisation werden kann, muss Du 2FA ### Deinen Antrag bei {% data variables.product.prodname_dotcom %} zur Genehmigung einreichen -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %} {% data reusables.sponsors.github-review-app %} 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 86a9bfe0ef..13d2dedb3a 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 @@ -26,7 +26,7 @@ Wenn Du ein Bankkonto in einer unterstützten Region hast, wird {% data variable Nachdem {% data variables.product.prodname_dotcom %} Deine Bewerbung überprüft hat, kannst Du Dein Profil als unterstützter Entwickler aufsetzen, damit Personen beginnen können, Dich zu unterstützen. -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ Nachdem {% data variables.product.prodname_dotcom %} Deine Bewerbung überprüft {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} @@ -54,14 +54,14 @@ Wenn Du in einer unterstützen Region lebst, kannst Du diesen Anweisungen folgen {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} ### Deine Steuerinformationen einreichen {% data reusables.sponsors.tax-form-information-dev %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -73,7 +73,7 @@ Bevor Du ein unterstützter Entwickler werden kannst, musst Du die 2FA für Dein ### Deinen Antrag bei {% data variables.product.prodname_dotcom %} zur Genehmigung einreichen -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 4. Klicke auf **Request approval** (Genehmigung beantragen). ![Schaltfläche „Request approval" (Beantragen der Genehmigung)](/assets/images/help/sponsors/request-approval-button.png) {% data reusables.sponsors.github-review-app %} 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 430eb59b5f..d023e9cd4e 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 @@ -7,17 +7,32 @@ redirect_from: - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer versions: free-pro-team: '*' +permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization. --- -### Über die Unterstützung von Entwicklern und Organisationen +{% data reusables.sponsors.org-sponsors-release-phase %} -{% data reusables.sponsors.sponsorship-details %}{% data reusables.sponsors.no-fees %} Weitere Informationen findest Du unter „[ Informationen zur Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." +### About sponsorships -Wenn Du einen Open-Source-Mitwirkenden unterstützt, wird diese Änderung sofort wirksam. {% data reusables.sponsors.prorated-sponsorship %} +{% data reusables.sponsors.sponsorship-details %} -Wenn der unterstützte Open-Source-Mitwirkende Deine Stufe zurückzieht, wird die Stufe für Dich solange Gültigkeit behalten, bis Du eine andere Stufe auswählst oder Dein Abonnement kündigst. Weitere Informationen findest Du unter „[Sponsoring heraufstufen](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship).“ +You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons. +- Sustaining specific libraries that your organization's work depends on +- Investing in the ecosystem you rely on as a organization (such as blockchain) +- Developing brand awareness as an organization that values open source +- Thanking open source developers for building libraries that complement the product your organization offers -Wenn der Open-Source-Mitwirkende, den du unterstützen möchtest, kein Profil als unterstützter Entwickler oder als unterstützte Organisation hat, kannst Du den Mitwirkenden ermutigen, ein entsprechendes Profil zu erstellen. 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)" und „[{% 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)." +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). + +{% data 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 %} + +{% data reusables.sponsors.manage-updates-for-orgs %} + +If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. Weitere Informationen finden Sie unter „[Sponsoring heraufstufen](/articles/upgrading-a-sponsorship)“ und „[Sponsoring herabstufen](/articles/downgrading-a-sponsorship)“. + +If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. 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)" und „[{% 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)." {% data reusables.sponsors.sponsorships-not-tax-deductible %} @@ -27,30 +42,20 @@ Wenn der Open-Source-Mitwirkende, den du unterstützen möchtest, kein Profil al {% endnote %} -### Entwickler unterstützten +### Sponsoring an account -Bevor Du einen Entwickler unterstützten kannst, musst Du einen verifizierte E-Mail-Adresse haben. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/github/getting-started-with-github/verifying-your-email-address).“ +Before you can sponsor an account, you must have a verified email address. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/github/getting-started-with-github/verifying-your-email-address).“ -1. Navigieren Sie auf {% data variables.product.product_name %} zu dem Profil des Entwicklers, den Sie sponsern möchten. -2. Klicke unter dem Namen des Entwicklers auf **Sponsor** (Unterstützen). ![Schaltfläche „Sponsor“ (Sponsern)](/assets/images/help/profile/sponsor-button.png) +1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor. +1. Navigate to your sponsorship dashboard for the account. + - To sponsor a developer, under the developer's name, click **Sponsor**. ![Schaltfläche „Sponsor“ (Unterstützen)](/assets/images/help/profile/sponsor-button.png) + - To sponsor an organization, to the right of the 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.select-a-tier %} +{% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} ![Schaltfläche „Edit payment" (Bearbeiten der Zahlungsdetails)](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) {% data reusables.sponsors.who-can-see-your-sponsorship %} ![Optionsfelder, um auszuwählen, wer Dein Sponsoring sehen kann](/assets/images/help/sponsors/who-can-see-sponsorship.png) -{% data reusables.sponsors.developer-sponsored-choose-updates %} -7. Klicken Sie auf **Sponsor _DEVELOPER_** (Unterstütze ENTWICKLER). ![Schaltfläche „Sponsor developer" (Unterstützen eines Entwicklers)](/assets/images/help/sponsors/sponsor-developer-button.png) - -### Eine Organisation unterstützen - -Bevor Du eine Organisation unterstützten kannst, musst Du einen verifizierte E-Mail-Adresse haben. Weitere Informationen findest Du unter „[Eigene E-Mail-Adresse verifizieren](/github/getting-started-with-github/verifying-your-email-address).“ - -1. Navigiere auf {% data variables.product.product_name %} zur Seite der Organisation, die Du unterstützen möchtest. -2. Klicke neben dem Namen der Organisation auf **Sponsor** (Unterstützen). ![Schaltfläche „Sponsor“ (Sponsern)](/assets/images/help/sponsors/sponsor-org-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.select-sponsorship-billing %} - ![Schaltfläche „Edit payment" (Bearbeiten der Zahlungsdetails)](/assets/images/help/sponsors/edit-org-sponsorship-payment-button.png) -{% data reusables.sponsors.who-can-see-your-sponsorship %} - ![Optionsfelder, um auszuwählen, wer Dein Sponsoring sehen kann](/assets/images/help/sponsors/who-can-see-org-sponsorship.png) -{% data reusables.sponsors.org-sponsored-choose-updates %} -7. Klicke auf **Sponsor _ORGANIZATION_** (Unterstütze ORGANISATION). ![Schaltfläche „Sponsor organization" (Unterstützen einer Organisation)](/assets/images/help/sponsors/sponsor-org-confirm-button.png) +{% data reusables.sponsors.choose-updates %} +{% data reusables.sponsors.sponsor-account %} diff --git a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 1cd43eefcd..9e2a747ffe 100644 --- a/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/de-DE/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -7,34 +7,25 @@ versions: free-pro-team: '*' --- +### About sponsors and sponsorships + Du kannst Analysen zu Deinen aktuellen und vergangenen Sponsorings einsehen, die Zahlungen, die Du von Sponsoren erhalten hast, und Ereignisse, wie beispielsweise Kündigungen oder Sponsoren-Stufenänderungen für Deine Sponsorings. Du kannst auch Aktivitäten wie neue Sponsorings oder geänderte und gekündigte Sponsorings ansehen. Du kannst die Liste der Aktivitäten nach Datum filtern. Du kannst die Sponsoring-Daten Deines Kontos auch im CSV- oder JSON-Format exportieren. -Du hast auf alle diese Informationen von Deinem Sponsoren-Dashboard her Zugriff. - -### Dein Sponsoren-Dashboard anzeigen - -1. Klicke in der rechten oberen Ecke einer beliebigen Seite auf Dein Profilfoto und klicke dann auf **{% data variables.product.prodname_sponsors %}**. ![Schaltfläche {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. Klicke in der angezeigten Liste rechts neben dem Konto oder der Organisation, dessen Sponsoren-Dashboard Du anzeigen möchtest, auf **Dashboard**. ![Schaltfläche „Developer sponsors dashboard" (Dashboard Entwickler-Sponsoren)](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) - ### Sponsoren und Sponsoring anzeigen -1. Navigiere zu Deinem Sponsoren-Dashboard, siehe dazu „[Dein Sponsoren-Dashboard anzeigen](#viewing-your-sponsors-dashboard)". -{% data reusables.sponsors.navigate-to-sponsors-tab %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. Optional kannst Du Deine Sponsoren nach Stufe filtern. verwende dazu das Dropdownmenü **Filter**, klicke auf **Active tiers** (Aktive Stufen) oder **Retired tiers** (zurückgezogene Stufen), und wähle eine Stufe aus. ![Dropdownmenü zum Filtern nach Stufe](/assets/images/help/sponsors/filter-drop-down.png) ### Letzte Sponsoring-Aktivitäten anzeigen -1. Navigiere zu Deinem Sponsoren-Dashboard, siehe dazu „[Dein Sponsoren-Dashboard anzeigen](#viewing-your-sponsors-dashboard)". +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. Klicke in der linken Seitenleiste auf **Activity** (Aktivitäten). ![Registerkarte „Activity" (Aktivitäten)](/assets/images/help/sponsors/activity-tab.png) ### Deine Sponsoring-Daten exportieren -1. Navigiere zu Deinem Sponsoren-Dashboard, siehe dazu „[Dein Sponsoren-Dashboard anzeigen](#viewing-your-sponsors-dashboard)". +If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsors-tab %} 1. Klicke auf **Export all** (Alles exportieren). ![Schaltfläche „Export all" (Alles exportieren)](/assets/images/help/sponsors/export-all.png) - - Diese Schaltfläche wird nicht angezeigt, wenn Du keine Sponsoren hast. - -1. Wähle einen Zeitrahmen und ein Format für die zu exportierenden Daten und klicke dann auf **Start export** (Export starten). ![Optionen für den Datenexport](/assets/images/help/sponsors/export-your-sponsors.png) - - {% data variables.product.prodname_dotcom %} startet den Datenexport für alle deine Sponsoren für den gewählten Monat. Du wirst kurz danach eine E-Mail mit einem Anhang mit den Daten erhalten. Nachdem der Export abgeschlossen ist, kannst Du einen weiteren Monat mit Daten exportieren. Du kannst bis zu 10 Datensätze pro Stunde für alle Deine unterstützten Organisationen oder Benutzerkonten exportieren. +1. Wähle einen Zeitrahmen und ein Format für die zu exportierenden Daten und klicke dann auf **Start export** (Export starten). ![Optionen für den Datenexport](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/de-DE/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/de-DE/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 851792daf2..7034e6b56b 100644 --- a/translations/de-DE/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/de-DE/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -36,8 +36,8 @@ Wenn Du bei der Erstellung eines Repository-Klons einen Ordner in ein separates {% endwindows %} - `BRANCH-NAME`: The default branch for your current project, for example, `main` or `gh-pages`. ```shell - $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME - # Filtere den spezifischen Branch in Deinem Verzeichnis und entferne leere Commits + $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME + # Filter the specified branch in your directory and remove empty commits > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) > Ref 'refs/heads/BRANCH-NAME' was rewritten ``` 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 ee6e10f5bc..1a66878f1a 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 @@ -21,6 +21,10 @@ 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)." +{% 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: @@ -41,7 +45,8 @@ 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. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +- 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 diff --git a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/index.md b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/index.md index baae04ea51..fa569dd75a 100644 --- a/translations/de-DE/content/github/visualizing-repository-data-with-graphs/index.md +++ b/translations/de-DE/content/github/visualizing-repository-data-with-graphs/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repository-graphs %} {% link_in_list /viewing-a-summary-of-repository-activity %} {% link_in_list /viewing-a-projects-contributors %} - {% link_in_list /viewing-traffic-to-a-repository %} - {% topic_link_in_list /analyzing-changes-to-a-repositorys-content %} {% link_in_list /visualizing-commits-in-a-repository %} {% link_in_list /visualizing-additions-and-deletions-to-content-in-a-repository %} {% topic_link_in_list /understanding-connections-between-repositories %} {% link_in_list /viewing-a-repositorys-network %} {% link_in_list /listing-the-forks-of-a-repository %} - {% link_in_list /about-the-dependency-graph %} {% link_in_list /exploring-the-dependencies-of-a-repository %} - diff --git a/translations/de-DE/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index fb00e2a7d8..34faab8c6b 100644 --- a/translations/de-DE/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/de-DE/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -51,7 +51,7 @@ Dein Design umfasst standardmäßige Layouts, Includes und Stylesheets, die auto 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: page + layout: post title: "POST TITLE" date: YYYY-MM-DD hh:mm:ss -0000 categories: CATEGORY-1 CATEGORY-2 diff --git a/translations/de-DE/content/github/working-with-github-pages/index.md b/translations/de-DE/content/github/working-with-github-pages/index.md index e04e090ef7..23ce7daa00 100644 --- a/translations/de-DE/content/github/working-with-github-pages/index.md +++ b/translations/de-DE/content/github/working-with-github-pages/index.md @@ -23,15 +23,11 @@ versions: {% topic_link_in_list /getting-started-with-github-pages %} {% link_in_list /about-github-pages %} {% link_in_list /creating-a-github-pages-site %} - {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} - {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} - {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} - {% link_in_list /unpublishing-a-github-pages-site %} {% topic_link_in_list /setting-up-a-github-pages-site-with-jekyll %} {% link_in_list /about-github-pages-and-jekyll %} @@ -42,9 +38,7 @@ versions: {% link_in_list /adding-a-theme-to-your-github-pages-site-using-jekyll %} {% link_in_list /about-jekyll-build-errors-for-github-pages-sites %} {% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %} - {% topic_link_in_list /configuring-a-custom-domain-for-your-github-pages-site %} {% link_in_list /about-custom-domains-and-github-pages %} {% link_in_list /managing-a-custom-domain-for-your-github-pages-site %} {% link_in_list /troubleshooting-custom-domains-and-github-pages %} - diff --git a/translations/de-DE/content/github/working-with-github-support/index.md b/translations/de-DE/content/github/working-with-github-support/index.md index fd9d726609..2ea3e30f7c 100644 --- a/translations/de-DE/content/github/working-with-github-support/index.md +++ b/translations/de-DE/content/github/working-with-github-support/index.md @@ -2,6 +2,7 @@ title: Mit dem GitHub-Support arbeiten redirect_from: - /categories/working-with-github-support + - /forum versions: free-pro-team: '*' --- diff --git a/translations/de-DE/content/graphql/README.md b/translations/de-DE/content/graphql/README.md new file mode 100644 index 0000000000..f29fbc5131 --- /dev/null +++ b/translations/de-DE/content/graphql/README.md @@ -0,0 +1,10 @@ +# GraphQL + +The `/content/graphql` directory is where the GitHub GraphQL API docs live! + +* The `/content/graphql/guides` and `/content/graphql/overview` directories contain articles that are human-editable. +* The `/content/graphql/reference` directory contains an article for each GraphQL data type used in the GitHub GraphQL API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/graphql/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/graphql/README.md`](/lib/graphql/README.md). + + **As a result, we cannot accept contributions to GraphQL API reference content in this repository.** diff --git a/translations/de-DE/content/graphql/overview/explorer.md b/translations/de-DE/content/graphql/overview/explorer.md index f87b12b44e..74540b78a4 100644 --- a/translations/de-DE/content/graphql/overview/explorer.md +++ b/translations/de-DE/content/graphql/overview/explorer.md @@ -7,6 +7,6 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +layout: graphql-explorer --- -You can access GitHub's GraphQL Explorer at https://developer.github.com/v4/explorer. diff --git a/translations/de-DE/content/packages/guides/about-github-container-registry.md b/translations/de-DE/content/packages/guides/about-github-container-registry.md new file mode 100644 index 0000000000..fe5f23d6c3 --- /dev/null +++ b/translations/de-DE/content/packages/guides/about-github-container-registry.md @@ -0,0 +1,94 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/about-github-container-registry + - /packages/managing-container-images-with-github-container-registry +versions: + free-pro-team: '*' +--- + +{% note %} + +**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)." + +{% endnote %} + +### Informationen zu {% 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)." + +{% data variables.product.prodname_github_container_registry %} has different hosting locations, permission, and visibility than other package registries. + +| | Package registries | {% data variables.product.prodname_github_container_registry %} +| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Hosting locations | You can host multiple packages in one repository. | You can host multiple container images in one organization or user account. | +| Permissions | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. | + Visibility | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | Anonymous access | N/A | You can access public container images anonymously. + +For more information, see "[About scopes and permissions for {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)." + +### Unterstützte Formate + +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: + +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) + +The {% data variables.product.prodname_github_container_registry %} hosts containers at `ghcr.io/OWNER/IMAGE-NAME`. + +| Paketclient | Sprache | Paketformat | Beschreibung | +| ----------- | ------- | ------------ | ----------------------------------- | +| docker | N/A | `Dockerfile` | Docker-Containermanagementplattform | + + +#### Manifest Lists/Image Indexes + +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. + +### Visibility and access permissions for container images + +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. + +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. + +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. + +| Permission role | Access description | +| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| Read (Gelesen) | Can download package.
Can read package metadata. | +| Schreiben | Can upload and download this package.
Can read and write package metadata. | +| Verwalten | Can upload, download, delete, and manage this package.
Can read and write package metadata.
Can grant package permissions. | + +For more information, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." + +### About tokens + +To install or publish a package, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. + +| Scope | Beschreibung | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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)." | + +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)." + +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)." + +### Informationen zur Abrechnung für {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.billing-for-container-registry %} + +### Support kontaktieren + +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). + +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: + +* 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. diff --git a/translations/de-DE/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md b/translations/de-DE/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md new file mode 100644 index 0000000000..1d66526320 --- /dev/null +++ b/translations/de-DE/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md @@ -0,0 +1,69 @@ +--- +title: Configuring access control and visibility for container images +intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### Configuring access to container images for your personal account + +If you have admin permissions to a user-account owned container image, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)." + +{% data reusables.package_registry.package-settings-from-user-level %} +1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a user account. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) +1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) + +The selected users will automatically be given access and don't need to accept an invitation first. + +### Configuring access to container images for an organization + +If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)." + +If your package is owned by an organization and private, then you can only give access to other organization members or teams. + +For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% data reusables.package_registry.package-settings-from-org-level %} +1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) +1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) + +The selected users or teams will automatically be given access and don't need to accept an invitation first. + +### Configuring visibility of container images for your personal account + +When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings. + +A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. + +{% data reusables.package_registry.package-settings-from-user-level %} +5. Under "Danger Zone", choose a visibility setting: + - To make the container image visible to anyone, click **Make public**. + {% warning %} + + **Warning:** Once you make a package public, you cannot make it private again. + + {% endwarning %} + - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) + +### Configuring visibility of container images for an organization + +When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings. + +A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. + +For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% data reusables.package_registry.package-settings-from-org-level %} +5. Under "Danger Zone", choose a visibility setting: + - To make the container image visible to anyone, click **Make public**. + {% warning %} + + **Warning:** Once you make a package public, you cannot make it private again. + + {% endwarning %} + - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/de-DE/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md new file mode 100644 index 0000000000..ece0d0f81d --- /dev/null +++ b/translations/de-DE/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -0,0 +1,195 @@ +--- +title: Configuring Apache Maven for use with GitHub Packages +intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Bei {% data variables.product.prodname_registry %} authentifizieren + +{% 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 Apache Maven by editing your *~/.m2/settings.xml* file to include your personal access token. Create a new *~/.m2/settings.xml* file if one doesn't exist. + +In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your personal access token. + +In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}*REPOSITORY* with the name of the repository you'd like to publish a package to or install a package from, and *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. + +If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag. + +{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` +{% endif %} + +#### #### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Ein Paket veröffentlichen + +{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example:test` in a repository called `OWNER/test`. + +If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository. + +For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + +1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing `OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. + +{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation enabled: + {% endif %} + ``` + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + ``` + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation disabled: + ``` + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + ``` + {% endif %} +2. Publish the package. + + ```shell + $ mvn deploy + ``` + +{% data reusables.package_registry.viewing-packages %} + +### Ein Paket installieren + +To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation. + +{% data reusables.package_registry.authenticate-step %} +2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package. + + ``` + + + com.example + test + 1.0.0-SNAPSHOT + + + ``` +3. Installieren Sie das Paket. + + ```shell + $ mvn install + ``` + +### Weiterführende Informationen + +- „[Gradle für die Verwendung mit {% data variables.product.prodname_registry %} konfigurieren](/packages/guides/configuring-gradle-for-use-with-github-packages)" +- "[Deleting a package](/packages/manage-packages/deleting-a-package/)" diff --git a/translations/de-DE/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-docker-for-use-with-github-packages.md new file mode 100644 index 0000000000..e32d52aead --- /dev/null +++ b/translations/de-DE/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -0,0 +1,213 @@ +--- +title: Configuring Docker for use with GitHub Packages +intro: 'Sie können den Docker-Client für die Nutzung von {% data variables.product.prodname_registry %} zum Veröffentlichen und Abrufen von Docker-Images konfigurieren.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Bei {% data variables.product.prodname_registry %} authentifizieren + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +{% if enterpriseServerVersions contains currentVersion %} + +Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." + +{% endif %} + +### Bei {% data variables.product.prodname_registry %} authentifizieren + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Authenticating with a personal access token + +{% data reusables.package_registry.required-scopes %} + +You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command. + +To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file. + +{% if currentVersion == "free-pro-team@latest" %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + ``` +{% endraw %} +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + +To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. + +For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)." + +#### #### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publishing an image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% note %} + +**Note:** Image names must only use lowercase letters. + +{% endnote %} + +{% data variables.product.prodname_registry %} unterstützt mehrere Top-Level-Docker-Images pro Repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. + +{% data reusables.package_registry.viewing-packages %} + +1. Determine the image name and ID for your docker image using `docker images`. + ```shell + $ docker images + > < > + > REPOSITORY TAG IMAGE ID CREATED SIZE + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + ``` +2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, and *VERSION* with package version at build time. +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + If you haven't already built a docker image for the package, build the image, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with package version at build time, and PATH to the image if it isn't in the current working directory. + ``` + {% endif %} +3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time, +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% else %} + ```shell + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} +4. Publish the image to +{% data variables.product.prodname_registry %}. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} + {% note %} + + **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. + + {% endnote %} + +#### Example publishing a Docker image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} + +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` + +{% endif %} + +You can publish a new Docker image for the first time and name it `monalisa`. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +# Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . + +# Pusht das Image zu {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} +```shell +# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` +{% endif %} + +### Downloading an image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %} and *TAG_NAME* with tag for the image you want to install. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% else %} +```shell +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} + +{% note %} + +**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. + +{% endnote %} + +### Weiterführende Informationen + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/de-DE/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md new file mode 100644 index 0000000000..12c2c3fee6 --- /dev/null +++ b/translations/de-DE/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -0,0 +1,197 @@ +--- +title: Configuring `dotnet` CLI for use with GitHub Packages +intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages + - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Bei {% data variables.product.prodname_registry %} authentifizieren + +{% data reusables.package_registry.authenticate-packages %} + +#### Authenticating with a personal access token + +{% data reusables.package_registry.required-scopes %} + +To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client. + +You must replace: +- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}. +- `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 %} +- `HOSTNAME` with the host name for your {% data variables.product.prodname_ghe_server %} instance. + +If your instance has subdomain isolation enabled: +{% endif %} + +```xml + + + + + + + + + + + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://github.com/octo-org/octo-cats-and-dogs + + + +``` +{% endif %} + +#### #### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Ein Paket veröffentlichen + +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file. When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Create a new project. + ```shell + dotnet new console --name OctocatApp + ``` +3. Add your project's specific information to your project's file, which ends in *.csproj*. You must replace: + - `OWNER` with the name of the user or organization account that owns the repository containing your project. + - `REPOSITORY` with the name of the repository containing the package you want to publish. + - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion %} + - `HOSTNAME` with the host name for your {% data variables.product.prodname_ghe_server %} instance.{% endif %} + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + ``` +4. Package the project. + ```shell + dotnet pack --configuration Release + ``` + +5. Publish the package using the `key` you specified in the *nuget.config* file. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" + ``` + +### Publishing multiple packages to the same repository + +To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. + +For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository: + +``` xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +### Ein Paket installieren + +Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. + +{% data reusables.package_registry.authenticate-step %} + +2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use: + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + ``` + +3. Install the packages with the `restore` command. + ```shell + dotnet restore + ``` + +### Weiterführende Informationen + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/de-DE/content/packages/guides/configuring-gradle-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-gradle-for-use-with-github-packages.md new file mode 100644 index 0000000000..09354365b1 --- /dev/null +++ b/translations/de-DE/content/packages/guides/configuring-gradle-for-use-with-github-packages.md @@ -0,0 +1,215 @@ +--- +title: Configuring Gradle for use with GitHub Packages +intro: 'You can configure Gradle to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Bei {% data variables.product.prodname_registry %} authentifizieren + +{% 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 Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your personal access token. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository. + +{% if enterpriseServerVersions contains currentVersion %} +Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your +{% data variables.product.prodname_ghe_server %} instance. +{% endif %} + +Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. + +{% note %} + +**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)." + +{% endnote %} + +##### Example using Gradle Groovy for a single package in a repository + +```shell +plugins { + id("maven-publish") +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } +} +``` + +##### Example using Gradle Groovy for multiple packages in the same repository + +```shell +plugins { + id("maven-publish") apply false +} + +subprojects { + apply plugin: "maven-publish" + publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } + } +} +``` + +##### Example using Kotlin DSL for a single package in the same repository + +```shell +plugins { + `maven-publish` +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } +} +``` + +##### Example using Kotlin DSL for multiple packages in the same repository + +```shell +plugins { + `maven-publish` apply false + } + + subprojects { + apply(plugin = "maven-publish") + configure { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://maven.pkg.github.com/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } + } + } +``` + + #### Authenticating with the `GITHUB_TOKEN` + + {% data reusables.package_registry.package-registry-with-github-tokens %} + + For more information about using `GITHUB_TOKEN` with Maven, see "[Publishing Java packages with Maven](/actions/language-and-framework-guides/publishing-java-packages-with-maven#publishing-packages-to-github-packages)." + + ### Publishing a package + + {% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository. + + {% data reusables.package_registry.viewing-packages %} + + {% data reusables.package_registry.authenticate-step %} + 2. After creating your package, you can publish the package. + + ```shell + $ gradle publish + ``` + +### Ein Paket installieren + +You can install a package by adding the package as a dependency to your project. Weitere Informationen finden Sie unter „[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)“ (Abhängigkeiten festlegen) in der Gradle-Dokumentation. + +{% data reusables.package_registry.authenticate-step %} +2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. + + Example using Grady Groovy: + ```shell + dependencies { + implementation 'com.example:package' + } + ``` + Example using Kotlin DSL: + ```shell + dependencies { + implementation("com.example:package") + } + ``` + +3. Add the maven plugin to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. + + Example using Grady Groovy: + ```shell + plugins { + id 'maven' + } + ``` + Example using Kotlin DSL: + ```shell + plugins { + `maven` + } + ``` + + 3. Installieren Sie das Paket. + + ```shell + $ gradle install + ``` + +### Weiterführende Informationen + +- "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)" +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/de-DE/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-npm-for-use-with-github-packages.md new file mode 100644 index 0000000000..550c4294e9 --- /dev/null +++ b/translations/de-DE/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -0,0 +1,203 @@ +--- +title: Configuring npm for use with GitHub Packages +intro: 'Sie können NPM für die Veröffentlichung von Paketen auf {% data variables.product.prodname_registry %} und für die Nutzung von auf {% data variables.product.prodname_registry %} gespeicherten Paketen als Abhängigkeiten in einem NPM-Projekt konfigurieren.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Bei {% data variables.product.prodname_registry %} authentifizieren + +{% 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 npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token. + +To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +$ npm login --registry=https://npm.pkg.github.com +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address. + +If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +$ npm login --scope=@OWNER --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} + +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +#### #### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Ein Paket veröffentlichen + +{% note %} + +**Note:** Package names and scopes must only use lowercase letters. + +{% endnote %} + +By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. Ein Paket namens `@my-org/test` würde beispielsweise im Repository `my-org/test` auf {% data variables.product.prodname_dotcom %} veröffentlicht. You can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation. + +You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)." + +Die Scope-Zuordnung für Ihr Projekt können Sie entweder über die lokale *.npmrc*-Datei im Projekt oder die Option `publishConfig` in der Datei *package.json* festlegen. {% data variables.product.prodname_registry %} only supports scoped npm packages. Pakete mit Scopes weisen Namen im Format `@owner/name` auf. Pakete mit Scopes beginnen immer mit dem Symbol `@`. You may need to update the name in your *package.json* to use the scoped name. Beispiel: `"name": "@codertocat/hello-world-npm"`. + +{% data reusables.package_registry.viewing-packages %} + +#### Publishing a package using a local *.npmrc* file + +You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +1. Überprüfen Sie den Namen Ihres Pakets in der Datei *package.json* Ihres Projekts. Das Feld `name` (Name) muss den Scope und den Namen des Pakets enthalten. For example, if your package is called "test", and you are publishing to the "My-org" +{% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`. +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +#### Publishing a package using `publishConfig` in the *package.json* file + +You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. Weitere Informationen finden Sie unter „[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)“ in der NPM-Dokumentation. + +1. Bearbeiten Sie die Datei *package.json* für Ihr Paket, und fügen Sie den Eintrag `publishConfig` hinzu. + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation enabled: + {% endif %} + ```shell + "publishConfig": { + "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + }, + ``` + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation disabled: + ```shell + "publishConfig": { + "registry":"https://HOSTNAME/_registry/npm/" + }, + ``` + {% endif %} +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +### Publishing multiple packages to the same repository + +To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package. + +To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. + +{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name. + +```shell +"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", +``` + +### Ein Paket installieren + +You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation. + +By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." + +You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. Weitere Informationen finden Sie unter „[npm-scope](https://docs.npmjs.com/misc/scope) in der npm-Dokumentation. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency. + + ``` + { + "name": "@my-org/server", + "version": "1.0.0", + "description": "Server app that uses the @octo-org/octo-app package", + "main": "index.js", + "author": "", + "license": "MIT", + "dependencies": { + "@octo-org/octo-app": "1.0.0" + } + } + ``` +5. Installieren Sie das Paket. + + ```shell + $ npm install + ``` + +#### Pakete von anderen Organisationen installieren + +Standardmäßig können Sie nur {% data variables.product.prodname_registry %}-Pakete von einer Organisation verwenden. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}/OWNER +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +registry=https://HOSTNAME/_registry/npm/OWNER +@OWNER:registry=https://HOSTNAME/_registry/npm/ +@OWNER:registry=https://HOSTNAME/_registry/npm/ +``` +{% endif %} + +### Weiterführende Informationen + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/de-DE/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/de-DE/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md new file mode 100644 index 0000000000..07f259d125 --- /dev/null +++ b/translations/de-DE/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -0,0 +1,148 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Vorrausetzungen + +- You must have rubygems 2.4.1 or higher. To find your rubygems version: + + ```shell + $ gem --version + ``` + + - You must have bundler 1.6.4 or higher. To find your Bundler version: + ```shell + $ bundle --version + Bundler version 1.13.7 + ``` + + - Install keycutter to manage multiple credentials. To install keycutter: + ```shell + $ gem install keycutter + ``` + +### Bei {% data variables.product.prodname_registry %} authentifizieren + +{% 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. + +```shell +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. + +```shell +--- +:backtrace: false +:bulk_threshold: 1000 +:sources: +- https://rubygems.org/ +- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ +:update_sources: true +:verbose: true + +``` + +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 %} + +```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 %} + +### Ein Paket veröffentlichen + +{% 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. Weitere Informationen zum Erstellen einer Gem finden Sie unter „[Eine eigene Gem erstellen](http://guides.rubygems.org/make-your-own-gem/)“ in der RubyGems-Dokumentation. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Build the package from the *gemspec* to create the *.gem* package. + ```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 %} + + ```shell + $ gem push --key github \ + --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem + ``` + +### 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.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } +``` + +### Ein Paket installieren + +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 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 %} + + ``` + source "https://rubygems.org" + + gem "rails" + + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do + gem "GEM NAME" + end + ``` + +3. 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). + + ``` + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" + source "https://rubygems.org" + + gem "rails" + gem "GEM NAME" + ``` + +4. Installieren Sie das Paket: + ```shell + $ gem install octo-gem --version "0.1.1" + ``` + +### Weiterführende Informationen + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/de-DE/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/de-DE/content/packages/guides/connecting-a-repository-to-a-container-image.md new file mode 100644 index 0000000000..f22346e111 --- /dev/null +++ b/translations/de-DE/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -0,0 +1,83 @@ +--- +title: Connecting a repository to a container image +intro: 'You can link a repository with a container image locally and on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image +versions: + free-pro-team: '*' +--- + +When you link a container image with a repository, the package landing page will show information and links from the repository, such as the README. + +To connect a repository and a container image on {% data variables.product.prodname_dotcom %}, they must share the same owner on {% data variables.product.prodname_dotcom %}. For example, both `my_repo` and `hello_docker` are owned by the user `monalisa`: +```shell +https://github.com/monalisa/my_repo +https://github.com/monalisa/hello_docker +``` + +### Connecting a repository to a user-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Connecting a repository to an organization-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Connecting a repository to a container image on the command line + +1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details: + + ```shell + LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + ``` + For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile: + ```shell + LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + ``` + For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. + +2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`. + + ```shell + $ docker build -t hello_docker . + ``` +3. Optionally, review details for the Docker image you want to tag. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +4. Tag your Docker image with your desired image name and hosting destination. + ```shell + $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG + ``` + Ein Beispiel: + ```shell + $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest + ``` + +5. If you haven't already, authenticate to + +{% data variables.product.prodname_github_container_registry %}. For more information, see "[Authenticating to GitHub Container Registry](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-github-container-registry)." + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + > Login Succeeded + ``` + {% endraw %} +6. Push your container image to {% data variables.product.prodname_github_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG + ``` + Ein Beispiel: + ```shell + $ docker push ghcr.io/monalisa/hello_docker:latest + ``` diff --git a/translations/de-DE/content/packages/guides/container-guides-for-github-packages.md b/translations/de-DE/content/packages/guides/container-guides-for-github-packages.md new file mode 100644 index 0000000000..31b8f63889 --- /dev/null +++ b/translations/de-DE/content/packages/guides/container-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Container guides for GitHub Packages +shortTitle: Container guides for GitHub Packages +intro: 'You can publish and retrieve Docker images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/de-DE/content/packages/guides/deleting-a-container-image.md b/translations/de-DE/content/packages/guides/deleting-a-container-image.md new file mode 100644 index 0000000000..33451deeaa --- /dev/null +++ b/translations/de-DE/content/packages/guides/deleting-a-container-image.md @@ -0,0 +1,33 @@ +--- +title: Deleting a container image +intro: 'You can delete a version of a private container image using GraphQL or on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### About package deletion + +You can remove an entire container image or a specific version on {% data variables.product.prodname_dotcom %}. To delete a container image, you must use the UI. Using GraphQL to delete a container image is not supported at this time. + +To delete a container image, you must have admin permissions to the container image. + +When deleting public packages, be aware that you may break projects that depend on your package. + +### Deleting a version of a user-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Deleting a version of an organization-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) diff --git a/translations/de-DE/content/packages/guides/enabling-improved-container-support.md b/translations/de-DE/content/packages/guides/enabling-improved-container-support.md new file mode 100644 index 0000000000..448141c5a5 --- /dev/null +++ b/translations/de-DE/content/packages/guides/enabling-improved-container-support.md @@ -0,0 +1,39 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/enabling-improved-container-support +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)“. + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + + ![Options to enable public or private packages ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/de-DE/content/packages/guides/index.md b/translations/de-DE/content/packages/guides/index.md new file mode 100644 index 0000000000..6844bc5d87 --- /dev/null +++ b/translations/de-DE/content/packages/guides/index.md @@ -0,0 +1,33 @@ +--- +title: Leitfäden +shortTitle: Leitfäden +intro: 'These guides help you configure {% data variables.product.prodname_actions %} or your package client to work with {% data variables.product.prodname_registry %}.' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem + - /packages/using-github-packages-with-your-projects-ecosystem +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Inhaltsverzeichnis + +{% topic_link_in_list /package-client-guides-for-github-packages %} + {% link_in_list /using-github-packages-with-github-actions %} + {% link_in_list /configuring-apache-maven-for-use-with-github-packages %} + {% link_in_list /configuring-gradle-for-use-with-github-packages %} + {% link_in_list /configuring-npm-for-use-with-github-packages %} + {% link_in_list /configuring-dotnet-cli-for-use-with-github-packages %} + {% link_in_list /configuring-rubygems-for-use-with-github-packages %} +{% topic_link_in_list /container-guides-for-github-packages %} + {% link_in_list /configuring-docker-for-use-with-github-packages %} + {% link_in_list /about-github-container-registry %} + {% link_in_list /migrating-to-github-container-registry-for-docker-images %} + {% link_in_list /enabling-improved-container-support %} + {% link_in_list /configuring-access-control-and-visibility-for-container-images %} + {% link_in_list /connecting-a-repository-to-a-container-image %} + {% link_in_list /pushing-and-pulling-docker-images %} + {% link_in_list /deleting-a-container-image %} + diff --git a/translations/de-DE/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md b/translations/de-DE/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md new file mode 100644 index 0000000000..7f24eb0c3c --- /dev/null +++ b/translations/de-DE/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md @@ -0,0 +1,115 @@ +--- +title: Migrating to GitHub Container Registry for Docker images +intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate to the new {% data variables.product.prodname_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images +versions: + free-pro-team: '*' +--- + +### Key differences between {% data variables.product.prodname_github_container_registry %} and the Docker package registry + +{% data reusables.package_registry.container-registry-beta %} + +The {% data variables.product.prodname_github_container_registry %} supersedes the existing Packages Docker registry and is optimized to support some of the unique needs of containers. + +{% data reusables.package_registry.container-registry-feature-highlights %} + +Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)“. + +### Billing changes + +{% data reusables.package_registry.billing-for-container-registry %} + +### Domain changes + +The domain for the {% data variables.product.prodname_container_registry %} is `ghcr.io`. + +| Registry | Example URL | +| ----------------------------------------------------------------- | --------------------------------------------------- | +| {% data variables.product.prodname_registry %} Docker registry | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` | +| {% data variables.product.prodname_github_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME` | + +### Authenticating with the container registry + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}. + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Migrating a Docker image using the Docker CLI + +To move Docker images that you host on {% data variables.product.prodname_registry %} Docker registry, you must republish the images to {% data variables.product.prodname_container_registry %}. We recommend republishing your existing Docker images using the command line on your local machine. + +1. Sign in to the Docker registry using a temporary PAT with at least the `read:packages` scope. This PAT will only be used to sign in to the Docker registry to pull down images and can be deleted afterward. + {% raw %} + ```shell + $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin + ``` + {% endraw %} +2. Pull down the image you'd like to migrate, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with tag for the image you want to install. For example, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` pulls the latest tag of the `octoshift/octoshift` image in the octo-org organization. + ```shell + $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + +3. Re-tag the image with the new domain and a new image name. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. Use the same URL that you used in the previous step for the SOURCE URL. Replace the TARGET_OWNER with the user or organization that you are migrating the container image to and replace the TARGET_IMAGE_NAME with the new {% data variables.product.prodname_container_registry %} image name. + ```shell + $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION + ``` + +4. Sign in to the new + +{% data variables.product.prodname_container_registry %}. We recommend creating a new PAT limited to the `read:packages` and `write:packages` scopes since you no longer need the `repo` scope and your previous PAT may not have the `write:packages` scope. + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + ``` + {% endraw %} +5. Push your re-tagged image to the {% data variables.product.prodname_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION + ``` + +### Updating your {% data variables.product.prodname_actions %} workflow + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers. + +1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)." + +2. In your {% data variables.product.prodname_actions %} workflow file, update the package url from `https://docker.pkg.github.com` to `ghcr.io`. + +3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. {% data variables.product.prodname_github_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und speichern](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)“. + +4. In your {% data variables.product.prodname_actions %} workflow file, update the authentication PAT by replacing your Docker registry PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) with a new variable for your {% data variables.product.prodname_container_registry %} PAT, such as {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}. + +#### Example of updated workflow + +If part of your workflow accessed a Docker image hosted by the Docker registry like this: + +{% raw %} +```yaml +echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin +docker pull docker.pkg.github.com/github/octoshift/octoshift:latest +docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest +docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA +``` +{% endraw %} + +Then you'll need to update your workflow with the new {% data variables.product.prodname_container_registry %} URL and PAT like this: + +{% raw %} +```yaml +# new login with new container registry url and PAT +echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin +# new container registry urls added +docker pull ghcr.io/github/octoshift:latest +docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest +docker push ghcr.io/github/octoshift:$GITHUB_SHA +``` +{% endraw %} diff --git a/translations/de-DE/content/packages/guides/package-client-guides-for-github-packages.md b/translations/de-DE/content/packages/guides/package-client-guides-for-github-packages.md new file mode 100644 index 0000000000..6f77e8b9bd --- /dev/null +++ b/translations/de-DE/content/packages/guides/package-client-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Package client guides for GitHub Packages +shortTitle: Package client guides for GitHub Packages +intro: 'You can publish and retrieve package client images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/de-DE/content/packages/guides/pushing-and-pulling-docker-images.md b/translations/de-DE/content/packages/guides/pushing-and-pulling-docker-images.md new file mode 100644 index 0000000000..7300ce4eb5 --- /dev/null +++ b/translations/de-DE/content/packages/guides/pushing-and-pulling-docker-images.md @@ -0,0 +1,106 @@ +--- +title: Pushing and pulling Docker images +intro: 'You can store and manage Docker images in {% data variables.product.prodname_github_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +### Bei {% data variables.product.prodname_github_container_registry %} authentifizieren + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Pushing container images + +This example pushes the latest version of `IMAGE-NAME`. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +This example pushes the `2.5` version of the image. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 + ``` + +When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + +### Pulling container images + +#### Pull by digest + +To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value. + +1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:` + ```shell + $ docker inspect ghcr.io/OWNER/IMAGE_NAME + ``` +2. Remove image locally as needed. + ```shell + $ docker rmi ghcr.io/OWNER/IMAGE_NAME.latest + ``` + +3. Pull the container image with `@YOUR_SHA_VALUE` after the image name. + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs + ``` + +#### Pull by name + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME + ``` + +#### Pull by name and version + +Docker CLI example showing an image pulled by its name and the `1.14.1` version tag: + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1 + > 5e35bd43cf78: Pull complete + > 0c48c2209aab: Pull complete + > fd45dd1aad5a: Pull complete + > db6eb50c2d36: Pull complete + > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e + > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 + > ghcr.io/orgname/image-name/release:1.14.1 + ``` + +#### Pull by name and latest version + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest + > latest: Pulling from user/image-name + > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 + > Status: Downloaded newer image for ghcr.io/user/image-name:latest + > ghcr.io/user/image-name:latest + ``` + +### Building container images + +This example builds the `hello_docker` image: + ```shell + $ docker build -t hello_docker . + ``` + +### Tagging container images + +1. Find the ID for the Docker image you want to tag. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +2. Tag your Docker image using the image ID and your desired image name and hosting destination. + ```shell + $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest + ``` 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 new file mode 100644 index 0000000000..bb4ed48ec6 --- /dev/null +++ b/translations/de-DE/content/packages/guides/using-github-packages-with-github-actions.md @@ -0,0 +1,54 @@ +--- +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 %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions + - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About {% data variables.product.prodname_registry %} with {% 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)." + +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 %} + +{% 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)." + +{% endif %} + +#### Authenticating to package registries on {% 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. + +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)." + +### Publishing a package using an action + +You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. + +{% data reusables.package_registry.actions-configuration %} + +### 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 %} + +{% 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 %} diff --git a/translations/de-DE/content/packages/index.md b/translations/de-DE/content/packages/index.md index e00d89f22a..c40765a9dc 100644 --- a/translations/de-DE/content/packages/index.md +++ b/translations/de-DE/content/packages/index.md @@ -2,31 +2,46 @@ title: GitHub Packages Documentation shortTitle: GitHub Packages intro: 'Learn to safely publish and consume packages, store your packages alongside your code, and share your packages privately with your team or publicly with the open source community. You can also automate your packages with {% data variables.product.prodname_actions %}.' +introLinks: + quickstart: /packages/quickstart + reference: /packages/manage-packages featuredLinks: - gettingStarted: - - /packages/publishing-and-managing-packages/about-github-packages - - /packages/getting-started-with-github-container-registry/about-github-container-registry - - /packages/getting-started-with-github-container-registry - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/publishing-and-managing-packages/publishing-a-package - - /packages/publishing-and-managing-packages/installing-a-package + guides: + - /packages/learn-github-packages + - /packages/guides/using-github-packages-with-github-actions + - /packages/manage-packages/installing-a-package popular: - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-apache-maven-for-use-with-github-packages + guideCards: + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/guides/enabling-improved-container-support + - /packages/guides/configuring-rubygems-for-use-with-github-packages +changelog: + - + title: Packages container support is an opt-in beta + date: '2020-11-17' + href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support + - + title: Organization admins access to containers + date: '2020-11-16' + href: https://github.blog/changelog/2020-11-16-packages-organization-admins-access-to-containers/ + - + title: Packages now respects IP allow list settings + date: '2020-11-12' + href: https://github.blog/changelog/2020-11-12-packages-now-respects-ip-allow-list-settings/ redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry - /github/managing-packages-with-github-package-registry +layout: product-landing versions: free-pro-team: '*' enterprise-server: '>=2.22' --- -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% link_with_intro /getting-started-with-github-container-registry %} -{% link_with_intro /managing-container-images-with-github-container-registry %} -{% link_with_intro /publishing-and-managing-packages %} -{% link_with_intro /using-github-packages-with-your-projects-ecosystem %} + + + + diff --git a/translations/de-DE/content/packages/learn-github-packages/about-github-packages.md b/translations/de-DE/content/packages/learn-github-packages/about-github-packages.md new file mode 100644 index 0000000000..a5ad7b873e --- /dev/null +++ b/translations/de-DE/content/packages/learn-github-packages/about-github-packages.md @@ -0,0 +1,166 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/about-github-package-registry + - /github/managing-packages-with-github-package-registry/about-github-package-registry + - /github/managing-packages-with-github-packages/about-github-packages + - /packages/publishing-and-managing-packages/about-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Informationen zu {% data variables.product.prodname_registry %} + +{% data variables.product.prodname_registry %} is a package hosting service, fully integrated with {% data variables.product.prodname_dotcom %}. {% 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.prodname_dotcom %}. + +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. + +You can host multiple packages in one repository and see more information about each package by viewing the package's README, download statistics, version history, and more. + +{% if currentVersion == "free-pro-team@latest" %} +When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)“. + +{% data reusables.package_registry.container-registry-beta %} + +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + +{% endif %} + +#### Pakete anzeigen + +You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. Weitere Informationen findest Du unter „[Anzeigen von Paketen](/packages/manage-packages/viewing-packages)." + +#### About package permissions and visibility + +| | Package registries | +| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Hosting locations | You can host multiple packages in one repository. | +| Permissions | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | +| Visibility | {% data reusables.package_registry.public-or-private-packages %} + +{% if currentVersion == "free-pro-team@latest" %} +### Informationen zur Abrechnung für {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.packages-billing %}{% data reusables.package_registry.packages-spending-limit-brief %} Weitere Informationen findest Du 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)." + +{% data reusables.package_registry.container-registry-beta-billing-note %} +{% endif %} + +### Unterstützte Clients und Formate + +{% 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 + +{% 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" %} +| Sprache | Beschreibung | Paketformat | Paketclient | 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-Tool für die Build-Automatisierung für Java | `build.gradle` oder `build.gradle.kts` | `gradle` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | NuGet-Paketmanagement für .NET | `nupkg` | `dotnet` CLI | `nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | + +{% else %} + +With subdomain isolation enabled on {% data variables.product.product_location %}: + +| Sprache | Beschreibung | Paketformat | Paketclient | 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-Tool für die Build-Automatisierung für Java | `build.gradle` oder `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | NuGet-Paketmanagement für .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 %}: + +| Sprache | Beschreibung | Paketformat | Paketclient | 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-Tool für die Build-Automatisierung für Java | `build.gradle` oder `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | NuGet-Paketmanagement für .NET | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` | + +{% note %} + +**Note:** Docker is not supported when subdomain isolation is disabled. + +{% endnote %} + +For more information about subdomain isolation, see "[Enabling subdomain isolation](/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)." + +{% 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)." +{% endif %} +### Bei {% data variables.product.prodname_registry %} authentifizieren + +{% data reusables.package_registry.authenticate-packages %} + +### About scopes and permissions for package registries + +To install or publish a package, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. + +Ein Beispiel: +- 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.prodname_dotcom %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted. Weitere Informationen findest Du unter „[Ein Paket löschen](/packages/manage-packages/deleting-a-package)." + +| Scope | Beschreibung | Repository permissions | +| ----------------- | ------------------------------------------------------------------------------------------------- | ---------------------- | +| `read:packages` | Download and install packages from {% data variables.product.prodname_registry %} | Lesen | +| `write:packages` | Upload and publish packages to {% data variables.product.prodname_registry %} | schreiben | +| `delete:packages` | Delete specified versions of private packages from {% data variables.product.prodname_registry %} | verwalten | +| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write, or 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. + +Weitere Informationen findest Du unter: +- "[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)" + +### Managing packages + +You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." + +You can 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)." + +### Support kontaktieren + +{% 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). + +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: + +* 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 + +{% else %} +If you need support for +{% data variables.product.prodname_registry %}, please contact your site administrators. + +{% endif %} diff --git a/translations/de-DE/content/packages/learn-github-packages/core-concepts-for-github-packages.md b/translations/de-DE/content/packages/learn-github-packages/core-concepts-for-github-packages.md new file mode 100644 index 0000000000..9def261152 --- /dev/null +++ b/translations/de-DE/content/packages/learn-github-packages/core-concepts-for-github-packages.md @@ -0,0 +1,28 @@ +--- +title: Core concepts for GitHub Packages +intro: 'Below is a list of common {% data variables.product.prodname_registry %} terms we use across our sites and documentation.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Package + +A package is a self-contained and reusable piece of software that includes code and metadata that a developer bundles together in a common place for others to use. A package's metadata may include the version number, name, and the code's dependencies. Packages simplify using and distributing solutions to common problems such as needing frameworks for developing or testing a project, linters to improve code quality, or industry-standard machine learning tools to power your application. Packages exist in many ecosystems. For example, you can package Node.js and Java code or container images. + +### Container + +A container is a unit of software designed to reliably deploy software in a standardized way on any platform. A container operates as an isolated virtual environment or instance that can run various software packages and components on the same host kernel as your operating system. Containers use fewer resources than virtual machines because they don't need to include their own virtual hardware to run. Containers are created using a container image file, such as a Dockerfile, and a container client or runtime program. + +### Container image + +A container image is a type of package archive that specifies the software requirements to run an app from a container. A container image typically includes the app's code, libraries, and runtime instructions. To ensure that the same image details are used wherever an image is deployed and run, a container image is automatically versioned and cannot be changed once a container image is built in a container. + +### Docker-Container + +A Docker container is a type of open source container built on the Docker platform. Docker's original image format has become the OCI (Open Container Initiative) Image Specification. For more information, see the "[Docker documentation](https://docs.docker.com/get-started/overview/)." diff --git a/translations/de-DE/content/packages/learn-github-packages/index.md b/translations/de-DE/content/packages/learn-github-packages/index.md new file mode 100644 index 0000000000..a21e10fe4c --- /dev/null +++ b/translations/de-DE/content/packages/learn-github-packages/index.md @@ -0,0 +1,16 @@ +--- +title: Learn GitHub Packages +shortTitle: Learn GitHub Packages +intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.' +redirect_from: + - /packages/getting-started-with-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /about-github-packages %} +{% link_in_list /core-concepts-for-github-packages %} +{% link_in_list /publishing-a-package %} diff --git a/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md b/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md new file mode 100644 index 0000000000..0eb09c4b75 --- /dev/null +++ b/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md @@ -0,0 +1,37 @@ +--- +title: Ein Paket veröffentlichen +intro: 'You can publish a package to {% data variables.product.prodname_registry %} to make the package available for others to download and re-use.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-a-package + - /packages/publishing-and-managing-packages/publishing-a-package +permissions: Anyone with write permissions for a repository can publish a package to that repository. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About published packages + +You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. GitHub provides metadata for each version, such as the publication date, download activity, and recent versions. Eine Beispiel für eine Paketseite findest Du unter [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). + +{% data reusables.package_registry.public-or-private-packages %} A repository can contain more than one package. To prevent confusion, make sure the README and description clearly provide information about each package. + +{% if currentVersion == "free-pro-team@latest" %} +If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. +{% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +{% endif %} + +### Ein Paket veröffentlichen + +You can publish a package to {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. + +1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +2. Authenticate to {% data variables.product.prodname_registry %} using your access token and the instructions for your package client. +3. Publish the package using the instructions for your package client. + +For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)." + +Nachdem Du ein Paket veröffentlicht hast, kannst Du das Paket auf {% data variables.product.prodname_dotcom %} ansehen. For more information, see “[Viewing packages](/packages/publishing-and-managing-packages/viewing-packages).” diff --git a/translations/de-DE/content/packages/manage-packages/deleting-a-package.md b/translations/de-DE/content/packages/manage-packages/deleting-a-package.md new file mode 100644 index 0000000000..26ec6cab51 --- /dev/null +++ b/translations/de-DE/content/packages/manage-packages/deleting-a-package.md @@ -0,0 +1,81 @@ +--- +title: Ein Paket löschen +intro: 'You can delete a version of a private package using GraphQL or on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/deleting-a-package + - /packages/publishing-and-managing-packages/deleting-a-package +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% if currentVersion == "free-pro-team@latest" %} +### About container image deletion + +To delete a container image package on {% data variables.product.product_name %}, see "[Deleting a container image](/packages/guides/deleting-a-container-image)." + +{% endif %} + +### About private package deletion + +You can only delete a specified version of a private package on {% data variables.product.prodname_dotcom %} or with the GraphQL API. To remove an entire private package from appearing on {% data variables.product.prodname_dotcom %}, you must delete every version of the package first. + +{% if currentVersion == "free-pro-team@latest" %} +### About public package deletion + +To avoid breaking projects that may depend on your packages, you cannot delete an entire public package or specific versions of a public package. + +Under special circumstances, such as for legal reasons or to conform with GDPR standards, you can ask {% data variables.contact.github_support %} to delete a public package for you, using [our contact form](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry). + +{% else %} + +At this time, {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} does not support deleting public packages. + +{% endif %} + +### Deleting a version of a private package on {% data variables.product.product_name %} + +To delete a private package version, you must have admin permissions in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +3. Click the name of the package that you want to delete. ![Paketname](/assets/images/help/package-registry/select-pkg-cloud.png) +4. On the right, use the **Edit package** drop-down and select "Manage versions". ![Paketname](/assets/images/help/package-registry/manage-versions.png) +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Deleting a version of a private package with GraphQL + +Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#about-tokens)." + +Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token. + +{% if currentVersion == "free-pro-team@latest" %} +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +https://api.github.com/graphql +``` + +{% else %} + +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +HOSTNAME/graphql +``` + +{% endif %} + +To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `registryPackagesForQuery` connection. You will need a token with the `read:packages` and `repo` scopes. You will need a token with the `read:packages` and `repo` scopes. + +For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/v4/mutation/deletepackageversion/)." + +You cannot delete an entire package, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %} diff --git a/translations/de-DE/content/packages/manage-packages/index.md b/translations/de-DE/content/packages/manage-packages/index.md new file mode 100644 index 0000000000..7f313028a1 --- /dev/null +++ b/translations/de-DE/content/packages/manage-packages/index.md @@ -0,0 +1,18 @@ +--- +title: Managing GitHub packages +shortTitle: Managing GitHub packages +intro: 'You can publish new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-and-managing-packages + - /github/packages/publishing-and-managing-packages + - /packages/publishing-and-managing-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /viewing-packages %} +{% link_in_list /installing-a-package %} +{% link_in_list /deleting-a-package %} diff --git a/translations/de-DE/content/packages/manage-packages/installing-a-package.md b/translations/de-DE/content/packages/manage-packages/installing-a-package.md new file mode 100644 index 0000000000..3cdd777c30 --- /dev/null +++ b/translations/de-DE/content/packages/manage-packages/installing-a-package.md @@ -0,0 +1,29 @@ +--- +title: Ein Paket installieren +intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/installing-a-package + - /packages/publishing-and-managing-packages/installing-a-package +permissions: Anyone with read permissions for a repository can install a package from that repository. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About package installation + +You can search {% data variables.product.prodname_dotcom %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)." + +After you find a package, you can read the package's description and installation and usage instructions on the package page. + +### Ein Paket installieren + +You can install a package from {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. + +1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[About tokens](/packages/publishing-and-managing-packages/about-github-packages#about-tokens)." +2. Install the package using the instructions for your package client. + +For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)." diff --git a/translations/de-DE/content/packages/manage-packages/viewing-packages.md b/translations/de-DE/content/packages/manage-packages/viewing-packages.md new file mode 100644 index 0000000000..b59533ad41 --- /dev/null +++ b/translations/de-DE/content/packages/manage-packages/viewing-packages.md @@ -0,0 +1,50 @@ +--- +title: Pakete anzeigen +intro: 'Du kannst Details zu Paketen sehen, die in einem Repository veröffentlicht wurden, und die Ergebnisse nach Organisation oder Benutzer einschränken.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/viewing-packages + - /packages/publishing-and-managing-packages/viewing-packages +permissions: Alle Personen mit Leseberechtigung in einem Repository können die Pakete des Repository einsehen. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Pakete eines Repository einsehen + +Pakete müssen auf der Repository-Ebene installiert werden, aber Du kannst alle Pakete in einer Organisation einsehen sowie alle Pakete, die Du veröffentlicht hast. {% data reusables.package_registry.package-page-info %} + +### Pakete eines Repository einsehen + +Du kannst alle Pakete in einem Repository sehen und nach einem bestimmten Paket im Repository suchen. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + +### Pakete einer Organisation einsehen + +Du kannst alle Pakete einsehen, die in einer Organisation installiert sind, und nach einem bestimmten Paket suchen, das in den Repositorys einer Organisation installiert ist. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Klicken Sie unter dem Namen Ihrer Organisation auf +{% octicon "package" aria-label="The package icon" %} **Packages**. +{% data reusables.package_registry.navigate-to-packages %} + +### Deine Pakete einsehen + +Du kannst alle Pakete einsehen, die Du installiert hast, und in allen Organisationen und Repositorys nach einem bestimmten Paket suchen, das Du installiert hast. + +{% data reusables.profile.access_profile %} +2. Klicke oben auf der Profilseite in der Hauptnavigation auf **Packages** (Pakete). ![Registerkarte „Projects“ (Projekte)](/assets/images/help/package-registry/user-packages-tab.png) +{% data reusables.package_registry.navigate-to-packages %} + +### Weiterführende Informationen + +- "[Suche nach Paketen](/github/searching-for-information-on-github/searching-for-packages)" diff --git a/translations/de-DE/content/packages/quickstart.md b/translations/de-DE/content/packages/quickstart.md new file mode 100644 index 0000000000..ac2d06d837 --- /dev/null +++ b/translations/de-DE/content/packages/quickstart.md @@ -0,0 +1,110 @@ +--- +title: Quickstart for GitHub Packages +intro: 'Publish to {% data variables.product.prodname_registry %} in 5 minutes or less with {% data variables.product.prodname_actions %}.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Einführung + +You only need an existing {% data variables.product.prodname_dotcom %} repository to publish a package to {% data variables.product.prodname_registry %}. In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}. Feel free to create a new repository for this Quickstart. You can use it to test this and future {% data variables.product.prodname_actions %} workflows. + +### Publishing your package + +1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. Create a private repository if you’d like to delete this package later, public packages cannot be deleted. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clone the repository to your local machine. + {% raw %} + ```shell + $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git + $ cd YOUR-REPOSITORY + ``` + {% endraw %} +3. Create an `index.js` file and add a basic alert to say "Hello world!" + {% raw %} + ```javascript{:copy} + alert("Hello, World!"); + ``` + {% endraw %} +4. Initialize an npm package. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0` if you do not have any tests. Commit your changes and push them to +{% data variables.product.prodname_dotcom %}. + {% raw %} + ```shell + $ npm init + ... + package name: @YOUR-USERNAME/YOUR-REPOSITORY + ... + test command: exit 0 + ... + + $ npm install + $ git add index.js package.json package-lock.json + $ git commit -m "initialize npm package" + $ git push + ``` + {% endraw %} +5. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `release-package.yml`. Weitere Informationen finden Sie unter „[Neue Dateien erstellen](/github/managing-files-in-a-repository/creating-new-files)“. +6. Copy the following YAML content into the `release-package.yml` file. + {% raw %} + ```yaml{:copy} + name: Node.js Package + + on: + release: + types: [created] + + jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm ci + - run: npm test + + publish-gpr: + needs: build + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + registry-url: https://npm.pkg.github.com/ + - run: npm ci + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + ``` + {% endraw %} +7. 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**. +8. **Merge** the pull request. +9. Navigate to the **Code** tab and create a new release to test the workflow. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." + +Creating a new release in your repository triggers the workflow to build and test your code. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. + +### Viewing your published package + +Packages are published at the repository level. You can see all the packages in a repository and search for a specific package. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + + +### Installing a published package + +Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)." + +### Nächste Schritte: + +The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more. + +Combining {% data variables.product.prodname_registry %} and {% 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_registry %} and {% data variables.product.prodname_actions %}: + +- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions +- "[Guides](/packages/guides)" for specific uses cases and examples diff --git a/translations/de-DE/content/rest/README.md b/translations/de-DE/content/rest/README.md new file mode 100644 index 0000000000..55aaa5edda --- /dev/null +++ b/translations/de-DE/content/rest/README.md @@ -0,0 +1,10 @@ +# REST + +The `/content/rest` directory is where the GitHub REST API docs live! + +* The `/content/rest/guides` and `/content/rest/overview` directories contain regular articles. These are human-editable. +* The `/content/rest/reference` directory contains an article for each group of endpoints in the GitHub REST API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/rest/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/rest/README.md`](/lib/rest/README.md). + + **As a result, we cannot accept contributions to REST API reference content in this repository.** 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 4934a7d00c..dcc0dc6dea 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 @@ -373,7 +373,7 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]! [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore [issues-api]: /rest/reference/issues -[link-header]: http://www.w3.org/wiki/LinkHeader/ +[link-header]: https://www.w3.org/wiki/LinkHeader [conditional-requests]: /rest#conditional-requests [rate-limiting]: /rest#rate-limiting [rate-limiting]: /rest#rate-limiting diff --git a/translations/de-DE/content/rest/overview/api-previews.md b/translations/de-DE/content/rest/overview/api-previews.md index e4d6a1e383..01b907bb1f 100644 --- a/translations/de-DE/content/rest/overview/api-previews.md +++ b/translations/de-DE/content/rest/overview/api-previews.md @@ -53,7 +53,7 @@ Create, list, update, and delete environments for pre-receive hooks. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### Integrations -Manage [integrations](/early-access/integrations/) through the API. +Manage [integrations](/v3/integrations) through the API. **Custom media type:** `machine-man-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/) {% endif %} diff --git a/translations/de-DE/content/rest/overview/libraries.md b/translations/de-DE/content/rest/overview/libraries.md index 169441d839..c44db06aa8 100644 --- a/translations/de-DE/content/rest/overview/libraries.md +++ b/translations/de-DE/content/rest/overview/libraries.md @@ -72,7 +72,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby diff --git a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md index accaa33077..53f7c5a4e0 100644 --- a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md @@ -262,13 +262,15 @@ You can then expand these templates using something like the [uri_template][uri] ### Pagination -Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/rest/reference/activity#events) for example. +Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `page` parameter. For some resources, you can also set a custom page size up to 100 with the `per_page` parameter. Note that for technical reasons not all endpoints respect the `per_page` parameter, see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -Note that page numbering is 1-based and that omitting the `?page` parameter will return the first page. +Note that page numbering is 1-based and that omitting the `page` parameter will return the first 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. For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. @@ -280,13 +282,17 @@ For more information on pagination, check out our guide on [Traversing with Pagi {% endnote %} -The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information: +The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information. Ein Beispiel: 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). The possible `rel` values are: diff --git a/translations/de-DE/content/rest/overview/troubleshooting.md b/translations/de-DE/content/rest/overview/troubleshooting.md index 2f20648606..862149fcd3 100644 --- a/translations/de-DE/content/rest/overview/troubleshooting.md +++ b/translations/de-DE/content/rest/overview/troubleshooting.md @@ -52,7 +52,7 @@ curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos #### Calls to OAuth Authorizations API -If you're making [OAuth Authorization API](/enterprise-server@2.22/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: +If you're making [OAuth Authorization API](/enterprise-server/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: ```bash curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}' diff --git a/translations/de-DE/content/rest/reference/enterprise-admin.md b/translations/de-DE/content/rest/reference/enterprise-admin.md index 2a653ff069..0fbf117ef0 100644 --- a/translations/de-DE/content/rest/reference/enterprise-admin.md +++ b/translations/de-DE/content/rest/reference/enterprise-admin.md @@ -57,6 +57,16 @@ The current version of your enterprise is returned in the response header of eve {% endif %} +{% if currentVersion == "free-pro-team@latest" %} + +## Auditprotokoll + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ## Billing diff --git a/translations/de-DE/content/rest/reference/index.md b/translations/de-DE/content/rest/reference/index.md index 0d12f1a8a1..21e0d376ae 100644 --- a/translations/de-DE/content/rest/reference/index.md +++ b/translations/de-DE/content/rest/reference/index.md @@ -15,8 +15,6 @@ versions: {% link_in_list /apps %} {% link_in_list /billing %} {% link_in_list /checks %} - - {% link_in_list /codes-of-conduct %} {% link_in_list /code-scanning %} {% link_in_list /emojis %} @@ -39,6 +37,7 @@ versions: {% link_in_list /repos %} {% link_in_list /scim %} {% link_in_list /search %} +{% link_in_list /secret-scanning %} {% link_in_list /teams %} {% link_in_list /users %} {% link_in_list /permissions-required-for-github-apps %} diff --git a/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md b/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md index f0d51a1304..387c4192b5 100644 --- a/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/de-DE/content/rest/reference/permissions-required-for-github-apps.md @@ -819,10 +819,19 @@ _Teams_ * [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) - {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Permission on "secret scanning alerts" + +- [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) + +- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read) + +- [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permission on "security events" - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) diff --git a/translations/de-DE/content/rest/reference/secret-scanning.md b/translations/de-DE/content/rest/reference/secret-scanning.md new file mode 100644 index 0000000000..6c266b8488 --- /dev/null +++ b/translations/de-DE/content/rest/reference/secret-scanning.md @@ -0,0 +1,12 @@ +--- +title: Secret scanning +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.secret-scanning.api-beta %} + +The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a private repository. For more information on secret scanning for private repositories, see "[Securing your repository](/github/administering-a-repository/securing-your-repository)." + +{% include rest_operations_at_current_path %} diff --git a/translations/de-DE/data/glossaries/external.yml b/translations/de-DE/data/glossaries/external.yml index 05299e1c40..957eaf642c 100644 --- a/translations/de-DE/data/glossaries/external.yml +++ b/translations/de-DE/data/glossaries/external.yml @@ -390,7 +390,7 @@ - term: main description: >- - The default development branch. Whenever you create a Git repository, a branch named "main" is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. + The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. - term: Master description: >- diff --git a/translations/de-DE/data/products.yml b/translations/de-DE/data/products.yml index 3f033072dc..a135c5c659 100644 --- a/translations/de-DE/data/products.yml +++ b/translations/de-DE/data/products.yml @@ -5,10 +5,12 @@ productsInOrder: - github - verwalten + - discussions - actions - Pakete - developers - rest - graphql - insights + - education - desktop diff --git a/translations/de-DE/data/release-notes/2-20/0.yml b/translations/de-DE/data/release-notes/2-20/0.yml new file mode 100644 index 0000000000..5623123354 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/0.yml @@ -0,0 +1,44 @@ +--- +date: '2020-02-11' +sections: + features: + - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" + - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" + - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + changes: + - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/1.yml b/translations/de-DE/data/release-notes/2-20/1.yml new file mode 100644 index 0000000000..e303f5525e --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/1.yml @@ -0,0 +1,21 @@ +--- +date: '2020-02-27' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + bugs: + - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/10.yml b/translations/de-DE/data/release-notes/2-20/10.yml new file mode 100644 index 0000000000..58a38245c0 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/10.yml @@ -0,0 +1,21 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" + - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/11.yml b/translations/de-DE/data/release-notes/2-20/11.yml new file mode 100644 index 0000000000..0bdd30cf96 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/11.yml @@ -0,0 +1,19 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/12.yml b/translations/de-DE/data/release-notes/2-20/12.yml new file mode 100644 index 0000000000..5b286392f5 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/12.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + bugs: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + changes: + - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/13.yml b/translations/de-DE/data/release-notes/2-20/13.yml new file mode 100644 index 0000000000..7388ff5103 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/13.yml @@ -0,0 +1,22 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/14.yml b/translations/de-DE/data/release-notes/2-20/14.yml new file mode 100644 index 0000000000..d33fe2b58d --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/14.yml @@ -0,0 +1,13 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/15.yml b/translations/de-DE/data/release-notes/2-20/15.yml new file mode 100644 index 0000000000..aa3c664487 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/15.yml @@ -0,0 +1,24 @@ +date: '2020-08-26' +sections: + security_fixes: + - >- + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, + https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} + - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + bugs: + - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' + changes: + - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/16.yml b/translations/de-DE/data/release-notes/2-20/16.yml new file mode 100644 index 0000000000..4ca63bc213 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/16.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/17.yml b/translations/de-DE/data/release-notes/2-20/17.yml new file mode 100644 index 0000000000..5f3bf87a25 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/17.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/18.yml b/translations/de-DE/data/release-notes/2-20/18.yml new file mode 100644 index 0000000000..3aab7ba337 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/18.yml @@ -0,0 +1,26 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/19.yml b/translations/de-DE/data/release-notes/2-20/19.yml new file mode 100644 index 0000000000..b686131852 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/19.yml @@ -0,0 +1,14 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/2.yml b/translations/de-DE/data/release-notes/2-20/2.yml new file mode 100644 index 0000000000..78e2faa7e1 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/2.yml @@ -0,0 +1,28 @@ +--- +date: '2020-03-10' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + bugs: + - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + changes: + - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/20.yml b/translations/de-DE/data/release-notes/2-20/20.yml new file mode 100644 index 0000000000..0cf4def9e0 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/20.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/21.yml b/translations/de-DE/data/release-notes/2-20/21.yml new file mode 100644 index 0000000000..4b970a92ee --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/21.yml @@ -0,0 +1,15 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/22.yml b/translations/de-DE/data/release-notes/2-20/22.yml new file mode 100644 index 0000000000..099ce93b0d --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/22.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/3.yml b/translations/de-DE/data/release-notes/2-20/3.yml new file mode 100644 index 0000000000..23c25312e5 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/3.yml @@ -0,0 +1,15 @@ +--- +date: '2020-03-12' +sections: + bugs: + - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/4.yml b/translations/de-DE/data/release-notes/2-20/4.yml new file mode 100644 index 0000000000..0f06a203cd --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/4.yml @@ -0,0 +1,18 @@ +--- +date: '2020-03-25' +sections: + bugs: + - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/5.yml b/translations/de-DE/data/release-notes/2-20/5.yml new file mode 100644 index 0000000000..44115fdc71 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/5.yml @@ -0,0 +1,20 @@ +--- +date: '2020-04-07' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + bugs: + - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/6.yml b/translations/de-DE/data/release-notes/2-20/6.yml new file mode 100644 index 0000000000..568f19954f --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/6.yml @@ -0,0 +1,27 @@ +--- +date: '2020-04-23' +sections: + security_fixes: + - '**HIGH**: OpenSSL has been updated to address [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 %}' + - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + bugs: + - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" + - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + changes: + - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% 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: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/7.yml b/translations/de-DE/data/release-notes/2-20/7.yml new file mode 100644 index 0000000000..b377d90b66 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/7.yml @@ -0,0 +1,21 @@ +--- +date: '2020-05-05' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + bugs: + - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' + - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/8.yml b/translations/de-DE/data/release-notes/2-20/8.yml new file mode 100644 index 0000000000..510bf779fb --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/8.yml @@ -0,0 +1,20 @@ +--- +date: '2020-05-19' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + bugs: + - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-20/9.yml b/translations/de-DE/data/release-notes/2-20/9.yml new file mode 100644 index 0000000000..326818d711 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-20/9.yml @@ -0,0 +1,17 @@ +--- +date: '2020-06-02' +sections: + security_fixes: + - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + bugs: + - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/0.yml b/translations/de-DE/data/release-notes/2-21/0.yml new file mode 100644 index 0000000000..cfd8a069f8 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/0.yml @@ -0,0 +1,72 @@ +--- +date: '2020-06-09' +sections: + features: + - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + security_fixes: + - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + bugs: + - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' + changes: + - 'The web notifications interface, including new [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - 'Admins can [enable security alerts](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' + - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/1.yml b/translations/de-DE/data/release-notes/2-21/1.yml new file mode 100644 index 0000000000..9b802bd1f3 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/1.yml @@ -0,0 +1,20 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/10.yml b/translations/de-DE/data/release-notes/2-21/10.yml new file mode 100644 index 0000000000..65b5d9c64c --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/10.yml @@ -0,0 +1,15 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/11.yml b/translations/de-DE/data/release-notes/2-21/11.yml new file mode 100644 index 0000000000..ce20fbe36a --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/11.yml @@ -0,0 +1,18 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/12.yml b/translations/de-DE/data/release-notes/2-21/12.yml new file mode 100644 index 0000000000..c347bb7aca --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/12.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/13.yml b/translations/de-DE/data/release-notes/2-21/13.yml new file mode 100644 index 0000000000..06e910bb50 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/13.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/2.yml b/translations/de-DE/data/release-notes/2-21/2.yml new file mode 100644 index 0000000000..bdac746dbc --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/2.yml @@ -0,0 +1,20 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/3.yml b/translations/de-DE/data/release-notes/2-21/3.yml new file mode 100644 index 0000000000..dd4ccbbb5e --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/3.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% 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: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/4.yml b/translations/de-DE/data/release-notes/2-21/4.yml new file mode 100644 index 0000000000..e90460c88e --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/4.yml @@ -0,0 +1,27 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" + - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/5.yml b/translations/de-DE/data/release-notes/2-21/5.yml new file mode 100644 index 0000000000..444cf28527 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/5.yml @@ -0,0 +1,15 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/6.yml b/translations/de-DE/data/release-notes/2-21/6.yml new file mode 100644 index 0000000000..8638d1d9cd --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/6.yml @@ -0,0 +1,26 @@ +date: '2020-08-26' +sections: + security_fixes: + - >- + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, + https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} + - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + bugs: + - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' + - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' + changes: + - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/7.yml b/translations/de-DE/data/release-notes/2-21/7.yml new file mode 100644 index 0000000000..69134720e7 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/7.yml @@ -0,0 +1,14 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/8.yml b/translations/de-DE/data/release-notes/2-21/8.yml new file mode 100644 index 0000000000..b7bf410b13 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/8.yml @@ -0,0 +1,16 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + bugs: + - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-21/9.yml b/translations/de-DE/data/release-notes/2-21/9.yml new file mode 100644 index 0000000000..46656c9e6b --- /dev/null +++ b/translations/de-DE/data/release-notes/2-21/9.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/de-DE/data/release-notes/2-22/0.yml b/translations/de-DE/data/release-notes/2-22/0.yml new file mode 100644 index 0000000000..cb67278fca --- /dev/null +++ b/translations/de-DE/data/release-notes/2-22/0.yml @@ -0,0 +1,130 @@ +--- +intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. +date: '2020-09-23' +sections: + features: + - + heading: GitHub Actions Beta + notes: + - | + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + + You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + - + heading: GitHub Packages Beta + notes: + - | + [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + - + heading: Advanced Security Code Scanning Beta + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. + + Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + - + heading: Pull Request Retargeting + notes: + - | + When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + - + heading: Suspend and Unsuspend an App Installation + notes: + - | + Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + - + heading: Improved Large Scale Performance + notes: + - | + We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% 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 %}'' + + Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + - + heading: View All of Your Users + notes: + - | + For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](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: Administration Changes + notes: + - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} + - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](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 %}' + - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% 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 %} + - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% 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: Security Changes + notes: + - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](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 %} + - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - + heading: Developer Changes + notes: + - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' + - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' + - + heading: Users and organizations can add Twitter usernames to their GitHub profiles + notes: + - '[Developers and organizations can now add their Twitter username to their profile](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: API Changes + notes: + - | + #### Graduated Previews + + The following previews are now an official part of the API: + * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} + * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} + - | + #### GraphQL Schema Changes + + * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + bugs: + - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + deprecations: + - + heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020** That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + #- type: Backup and Disaster recovery + #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} + - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} + - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a 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 %}' + - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/de-DE/data/release-notes/2-22/1.yml b/translations/de-DE/data/release-notes/2-22/1.yml new file mode 100644 index 0000000000..fbd3988c3d --- /dev/null +++ b/translations/de-DE/data/release-notes/2-22/1.yml @@ -0,0 +1,71 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - | + The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - | + Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + - | + Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + - | + System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + - | + The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + - | + `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + - | + Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + - | + Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + - | + Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + - | + When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + - | + The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + - | + OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + - | + Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + - | + On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + - | + When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + - | + When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + - | + Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + - | + Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + - | + The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + - | + Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + - | + A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + - | + When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + - | + [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + - | + GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management 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: + - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} + - GitHub App Manifests now include the `request_oauth_on_install` field. {% 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: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/de-DE/data/release-notes/2-22/2.yml b/translations/de-DE/data/release-notes/2-22/2.yml new file mode 100644 index 0000000000..dc36b39e12 --- /dev/null +++ b/translations/de-DE/data/release-notes/2-22/2.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + bugs: + - | + If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + - | + A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} + - | + On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + - | + When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + - | + Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} + - | + The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + - | + On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/de-DE/data/release-notes/2-22/3.yml b/translations/de-DE/data/release-notes/2-22/3.yml new file mode 100644 index 0000000000..45442a5d4b --- /dev/null +++ b/translations/de-DE/data/release-notes/2-22/3.yml @@ -0,0 +1,23 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - | + **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + - | + **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + - | + Packages have been updated to the latest security versions. {% 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: + - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/de-DE/data/release-notes/2-22/4.yml b/translations/de-DE/data/release-notes/2-22/4.yml new file mode 100644 index 0000000000..e97737ee0b --- /dev/null +++ b/translations/de-DE/data/release-notes/2-22/4.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + bugs: + - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} diff --git a/translations/de-DE/data/release-notes/2-22/5.yml b/translations/de-DE/data/release-notes/2-22/5.yml new file mode 100644 index 0000000000..0520df862f --- /dev/null +++ b/translations/de-DE/data/release-notes/2-22/5.yml @@ -0,0 +1,22 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' + - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/de-DE/data/reusables/accounts/create-account.md b/translations/de-DE/data/reusables/accounts/create-account.md new file mode 100644 index 0000000000..6beb7c99ab --- /dev/null +++ b/translations/de-DE/data/reusables/accounts/create-account.md @@ -0,0 +1,2 @@ +1. Rufen Sie die [Preisübersicht]({% data variables.product.pricing_url %}) von {% data variables.product.product_name %} auf. +2. Lies die Informationen zu den von {% data variables.product.product_name %} angebotenen Produkten und Abonnements, und klicke dann unter dem Abonnement, das Dich interessiert, auf die Schaltfläche „Upgrade“. diff --git a/translations/de-DE/data/reusables/actions/actions-not-verified.md b/translations/de-DE/data/reusables/actions/actions-not-verified.md index 2ab85ce6c1..3107e5a79f 100644 --- a/translations/de-DE/data/reusables/actions/actions-not-verified.md +++ b/translations/de-DE/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations, but unlike verified apps, {% data variables.product.prodname_dotcom %} does not review or verify individual actions listed in {% data variables.product.prodname_marketplace %}. +Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/de-DE/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/de-DE/data/reusables/actions/actions-packages-set-spending-limit.md new file mode 100644 index 0000000000..61c572965c --- /dev/null +++ b/translations/de-DE/data/reusables/actions/actions-packages-set-spending-limit.md @@ -0,0 +1 @@ +You can set a specific spending limit or, for some accounts, allow unlimited spending. Das Ausgabenlimit gilt für deine kombinierten Überschreitungen für {% data variables.product.prodname_registry %} und {% data variables.product.prodname_actions %}. diff --git a/translations/de-DE/data/reusables/actions/visualization-beta.md b/translations/de-DE/data/reusables/actions/visualization-beta.md new file mode 100644 index 0000000000..ee3ad11ef4 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/visualization-beta.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** The workflow visualization graph for {% data variables.product.prodname_actions %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-api-info.md b/translations/de-DE/data/reusables/audit_log/audit-log-api-info.md new file mode 100644 index 0000000000..088bfa010e --- /dev/null +++ b/translations/de-DE/data/reusables/audit_log/audit-log-api-info.md @@ -0,0 +1,5 @@ +* Zugriff auf Deine Organisation oder Deine Repository-Einstellungen +* Changes in permissions +* Added or removed users in an organization, repository, or team +* Users being promoted to admin +* Changes to permissions of a {% data variables.product.prodname_github_app %} diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/de-DE/data/reusables/audit_log/audit-log-git-events-retention.md new file mode 100644 index 0000000000..3f1584bf91 --- /dev/null +++ b/translations/de-DE/data/reusables/audit_log/audit-log-git-events-retention.md @@ -0,0 +1 @@ +The audit log retains Git events for 7 days. This is shorter than other audit log events, which can be retained for 90 days. diff --git a/translations/de-DE/data/reusables/classroom/about-assignments.md b/translations/de-DE/data/reusables/classroom/about-assignments.md new file mode 100644 index 0000000000..65a3506229 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/about-assignments.md @@ -0,0 +1 @@ +Each assignment has a title and an optional deadline. You can choose the visibility of repositories that {% data variables.product.prodname_classroom %} creates and choose access permissions. You can also automatically grade assignments and create a dedicated space to discuss the assignment with the student. diff --git a/translations/de-DE/data/reusables/classroom/about-autograding.md b/translations/de-DE/data/reusables/classroom/about-autograding.md new file mode 100644 index 0000000000..04ed2b067c --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/about-autograding.md @@ -0,0 +1 @@ +You can use autograding to automatically check a student's work for an assignment on {% data variables.product.prodname_classroom %}. You configure tests for an assignment, and the tests run immediately every time a student pushes to an assignment repository on {% data variables.product.product_location %}. The student can view the test results, make changes, and push to see new results. diff --git a/translations/de-DE/data/reusables/classroom/about-classrooms.md b/translations/de-DE/data/reusables/classroom/about-classrooms.md new file mode 100644 index 0000000000..5d19bbb44a --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/about-classrooms.md @@ -0,0 +1 @@ +A classroom in {% data variables.product.prodname_classroom %} is where teachers and students interact during a course. Teachers can create a student roster for the classroom, then create, assign, review, and grade assignments within the classroom. diff --git a/translations/de-DE/data/reusables/classroom/about-online-ides.md b/translations/de-DE/data/reusables/classroom/about-online-ides.md new file mode 100644 index 0000000000..43818e691f --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/about-online-ides.md @@ -0,0 +1 @@ +You can optionally configure an assignment to use an online integrated development environment (IDE). Online IDEs allow your students to write code, run programs, and collaborate in a browser, without installing Git and a full development toolchain on the student's computer. If you choose an online IDE for an assignment, students can still check out and run code locally on a computer with the necessary software. diff --git a/translations/de-DE/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/de-DE/data/reusables/classroom/assignments-classroom-prerequisite.md new file mode 100644 index 0000000000..06284dad51 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-classroom-prerequisite.md @@ -0,0 +1 @@ +You must create a classroom before you can create an assignment. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." diff --git a/translations/de-DE/data/reusables/classroom/assignments-click-pencil.md b/translations/de-DE/data/reusables/classroom/assignments-click-pencil.md new file mode 100644 index 0000000000..820afd5260 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-click-pencil.md @@ -0,0 +1 @@ +1. To the right of the assignment you want to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing assignment in list of assignments](/assets/images/help/classroom/assignments-click-pencil.png) diff --git a/translations/de-DE/data/reusables/classroom/assignments-group-definition.md b/translations/de-DE/data/reusables/classroom/assignments-group-definition.md new file mode 100644 index 0000000000..3143cddc70 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-group-definition.md @@ -0,0 +1 @@ +A group assignment is collaborative coursework for groups of students on {% data variables.product.prodname_classroom %}. diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/de-DE/data/reusables/classroom/assignments-guide-assign-a-deadline.md new file mode 100644 index 0000000000..6e8e29cc11 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-assign-a-deadline.md @@ -0,0 +1,5 @@ +Optionally, you can assign a deadline to the assignment. Under "Deadline (optional)", click in the text field, then use the date picker to assign a deadline. + +
+ Date picker for assignment deadline +
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-an-online-ide.md new file mode 100644 index 0000000000..54858178a5 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -0,0 +1,5 @@ +To choose an online IDE for the assignment, select the **Select an online IDE** drop-down menu, then click the IDE you'd like your students to use. + +
+ Using the 'Select an online IDE' drop-down menu to click an online IDE for the assignment +
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-template-repository.md new file mode 100644 index 0000000000..15bcb66cb5 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-template-repository.md @@ -0,0 +1,5 @@ +Under "Add a template repository to give students starter code", select the **Select a repository** drop-down, then type a search query. In the list of results, click the template repository you'd like to use for starter code. + +
+ Using the 'Select a repository' drop-down menu to find a template repository to use as starter code for an assignment +
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 new file mode 100644 index 0000000000..3f4f17e1b2 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -0,0 +1,9 @@ +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)." + +Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. + +
+ Visibility options for assignment repositories +
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-basics.md new file mode 100644 index 0000000000..b82d19fe8e --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-basics.md @@ -0,0 +1,7 @@ +
+ +When you're done, click **Continue** to configure starter code and a development environment for the assignment. + +
+ 'Continue' button +
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md new file mode 100644 index 0000000000..4607b61065 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md @@ -0,0 +1,7 @@ +
+ +When you're done, click **Continue** to configure automatic grading and feedback for the project. + +
+ 'Continue' button +
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/de-DE/data/reusables/classroom/assignments-guide-click-create-assignment-button.md new file mode 100644 index 0000000000..935d73f5df --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-click-create-assignment-button.md @@ -0,0 +1,5 @@ +To create the assignment, click **Create assignment**. + +
+ 'Create assignment' button +
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/de-DE/data/reusables/classroom/assignments-guide-create-review-pull-request.md new file mode 100644 index 0000000000..5cc14ee9ff --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-create-review-pull-request.md @@ -0,0 +1,5 @@ +To create pull requests for the discussion of feedback, select **Enable feedback pull requests**. + +
+ Checkbox for 'Enable feedback pull requests' +
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/de-DE/data/reusables/classroom/assignments-guide-create-the-assignment.md new file mode 100644 index 0000000000..051e169c57 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -0,0 +1,5 @@ +To create an assignment, sign into {% data variables.product.prodname_classroom_with_url %} and navigate to a classroom. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click **New assignment**. + +
+ The 'New assignment' button +
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/de-DE/data/reusables/classroom/assignments-guide-intro-for-environment.md new file mode 100644 index 0000000000..bda2c39723 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-intro-for-environment.md @@ -0,0 +1 @@ +Optionally, decide whether to provide empty repositories or starter code, and preconfigure a development environment for your students. diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md b/translations/de-DE/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md new file mode 100644 index 0000000000..6290d808ad --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md @@ -0,0 +1,3 @@ +{% data reusables.classroom.classroom-enables-invitation-urls %} + +{% data reusables.classroom.invitation-url-warning %} diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/de-DE/data/reusables/classroom/assignments-guide-prevent-changes.md new file mode 100644 index 0000000000..9ef39a18b9 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-prevent-changes.md @@ -0,0 +1,7 @@ +You can prevent students from changing files that contain tests for autograding, or other important files in the assignment repository. + +Under "Protected file paths", type relative paths within the repository to protect. + +
+ Text field for typing protected file paths +
\ No newline at end of file diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/de-DE/data/reusables/classroom/assignments-guide-using-autograding.md new file mode 100644 index 0000000000..5f50beec64 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-guide-using-autograding.md @@ -0,0 +1,23 @@ +{% data reusables.classroom.about-autograding %} For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." + +{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} For more information, see "[Grading methods](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)." + +
+ Using the 'Add test' drop-down menu to click a grading method +
+ +
+ +Define the parameters of your test case, like the name, commands, inputs, outputs, timeout, and points. When you're done, click **Save test case**. + +
+ 'Save test case' button for an autograding test +
+ +
+ +You can add more tests with the **Add test** drop-down menu, and you can edit or delete existing tests with {% octicon "pencil" aria-label="The pencil icon" %} or {% octicon "trash" aria-label="The trash icon" %}. + +
+ Pencil and trash icons to edit or delete an autograding test +
\ No newline at end of file diff --git a/translations/de-DE/data/reusables/classroom/assignments-individual-definition.md b/translations/de-DE/data/reusables/classroom/assignments-individual-definition.md new file mode 100644 index 0000000000..33425ae2c3 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-individual-definition.md @@ -0,0 +1 @@ +An individual assignment is coursework for each student who participates in a course on {% data variables.product.prodname_classroom %}. The student is intended to complete an individual assignment without help from other students. diff --git a/translations/de-DE/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/de-DE/data/reusables/classroom/assignments-to-prevent-submission.md new file mode 100644 index 0000000000..62bd9cc2da --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-to-prevent-submission.md @@ -0,0 +1 @@ +To prevent acceptance or submission of an assignment by students, deselect **Enable assignment invitation URL**. To edit the assignment, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment**. diff --git a/translations/de-DE/data/reusables/classroom/assignments-type-a-title.md b/translations/de-DE/data/reusables/classroom/assignments-type-a-title.md new file mode 100644 index 0000000000..20d32397ac --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/assignments-type-a-title.md @@ -0,0 +1,5 @@ +Type a title for the assignment. Optionally, click {% octicon "pencil" aria-label="The pencil icon" %} to edit the prefix. + +
+ Assignment title and prefix +
diff --git a/translations/de-DE/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/de-DE/data/reusables/classroom/classroom-creates-group-repositories.md new file mode 100644 index 0000000000..10cdc5924a --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/classroom-creates-group-repositories.md @@ -0,0 +1 @@ +For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.product_name %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. diff --git a/translations/de-DE/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/de-DE/data/reusables/classroom/classroom-creates-individual-repositories.md new file mode 100644 index 0000000000..4108abf9ad --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -0,0 +1 @@ +When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.product_name %}. diff --git a/translations/de-DE/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/de-DE/data/reusables/classroom/classroom-enables-invitation-urls.md new file mode 100644 index 0000000000..1b357c3a2d --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/classroom-enables-invitation-urls.md @@ -0,0 +1 @@ +By default, {% data variables.product.prodname_classroom %} enables an invitation URL for each assignment you create. Students can accept and submit the assignment while the invitation URL is enabled. You can share the URL with your students on your LMS, course homepage, or wherever you post assignments. Students can also navigate to the assignment on {% data variables.product.prodname_classroom %} if the student has already accepted an assignment for the classroom. diff --git a/translations/de-DE/data/reusables/classroom/click-assignment-in-list.md b/translations/de-DE/data/reusables/classroom/click-assignment-in-list.md new file mode 100644 index 0000000000..347d0bc108 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/click-assignment-in-list.md @@ -0,0 +1 @@ +1. In the list of assignments, click the assignment you want to view. ![Assignment in list of assignments for an classroom](/assets/images/help/classroom/click-assignment-in-list.png) diff --git a/translations/de-DE/data/reusables/classroom/click-classroom-in-list.md b/translations/de-DE/data/reusables/classroom/click-classroom-in-list.md new file mode 100644 index 0000000000..fe7d091cdc --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/click-classroom-in-list.md @@ -0,0 +1 @@ +1. In the list of classrooms, click the classroom you want to view. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) diff --git a/translations/de-DE/data/reusables/classroom/click-settings.md b/translations/de-DE/data/reusables/classroom/click-settings.md new file mode 100644 index 0000000000..9fe6b33d6b --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/click-settings.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" tab for classroom](/assets/images/help/classroom/click-settings.png) diff --git a/translations/de-DE/data/reusables/classroom/click-students.md b/translations/de-DE/data/reusables/classroom/click-students.md new file mode 100644 index 0000000000..13df0b1e40 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/click-students.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**. !["Students" tab for classroom](/assets/images/help/classroom/click-students.png) diff --git a/translations/de-DE/data/reusables/classroom/for-more-information-about-assignment-creation.md b/translations/de-DE/data/reusables/classroom/for-more-information-about-assignment-creation.md new file mode 100644 index 0000000000..8fd113d763 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/for-more-information-about-assignment-creation.md @@ -0,0 +1 @@ +For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." 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 new file mode 100644 index 0000000000..e554d4b605 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md @@ -0,0 +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. 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/classroom/invitation-url-warning.md b/translations/de-DE/data/reusables/classroom/invitation-url-warning.md new file mode 100644 index 0000000000..f85e808ddc --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/invitation-url-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning**: Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a user account on {% data variables.product.product_name %} with an identifier in your roster. + +{% endwarning %} diff --git a/translations/de-DE/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/de-DE/data/reusables/classroom/readme-contains-button-for-online-ide.md new file mode 100644 index 0000000000..fac85f79f1 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -0,0 +1 @@ +When a student accepts an assignment with an online IDE, the assignment repository will include a _README.md_ file with a special button at the top of the file. The button links the student directly to the workspace in the online IDE. diff --git a/translations/de-DE/data/reusables/classroom/sign-into-github-classroom.md b/translations/de-DE/data/reusables/classroom/sign-into-github-classroom.md new file mode 100644 index 0000000000..578bf7213e --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/sign-into-github-classroom.md @@ -0,0 +1 @@ +1. Sign into {% data variables.product.prodname_classroom_with_url %}. diff --git a/translations/de-DE/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/de-DE/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md new file mode 100644 index 0000000000..2486daf0a4 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md @@ -0,0 +1 @@ +Under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. diff --git a/translations/de-DE/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/de-DE/data/reusables/classroom/you-can-choose-a-template-repository.md new file mode 100644 index 0000000000..40eb9d273b --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -0,0 +1 @@ +You can optionally choose a template repository as starter code for the assignment. The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}. diff --git a/translations/de-DE/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/de-DE/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md new file mode 100644 index 0000000000..e9592fb832 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md @@ -0,0 +1 @@ +You can automatically create a pull request where you can provide feedback and answer a student's questions about an assignment. For more information about the review of changes in a pull request, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)." diff --git a/translations/de-DE/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md b/translations/de-DE/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md new file mode 100644 index 0000000000..af5be0c098 --- /dev/null +++ b/translations/de-DE/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md @@ -0,0 +1 @@ +You may want to predefine the default settings for the assignment repositories that {% data variables.product.prodname_classroom %} creates from a template repository. For example, you may want to disable issues, define labels for pull requests, or protect a branch in some or all of the repositories. diff --git a/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md b/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md new file mode 100644 index 0000000000..b8d2b78cbc --- /dev/null +++ b/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md @@ -0,0 +1,3 @@ +When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)." + +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file 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 85dbb4b2b4..6826353069 100644 --- a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md +++ b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md @@ -1,20 +1,23 @@ -| Paketmanager | Supports vendoring | -| -------------------------------- |:------------------:| -| Bundler: `bundler` | **X** | -| Cargo: `cargo` | | -| Composer: `composer` | | -| Docker: `docker` | | -| Elm: `elm` | | -| git submodule: `gitsubmodule` | | -| GitHub Actions: `github-actions` | | -| Go modules: `gomod` | **X** | -| Gradle: `gradle` | | -| Maven: `maven` | | -| Mix: `mix` | | -| npm: `npm` | | -| NuGet: `nuget` | | -| pip: `pip` | | -| Terraform: `terraform` | | +The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. + +| Paketmanager | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | +| -------------------------------- |:-----------------------------------------------------------------:|:---------:| +| Bundler: `bundler` | | **✓** | +| Cargo: `cargo` | **✓** | | +| Composer: `composer` | **✓** | | +| Docker: `docker` | **✓** | | +| Elixir: `hex` | | | +| Elm: `elm` | **✓** | | +| git submodule: `gitsubmodule` | **✓** | | +| GitHub Actions: `github-actions` | **✓** | | +| Go modules: `gomod` | **✓** | **✓** | +| Gradle: `gradle` | **✓** | | +| Maven: `maven` | **✓** | | +| Mix: `mix` | **✓** | | +| npm: `npm` | **✓** | | +| NuGet: `nuget` | **✓** | | +| pip: `pip` | | | +| Terraform: `terraform` | **✓** | | {% note %} diff --git a/translations/de-DE/data/reusables/discussions/about-categories-and-formats.md b/translations/de-DE/data/reusables/discussions/about-categories-and-formats.md new file mode 100644 index 0000000000..a17ca2ca53 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/about-categories-and-formats.md @@ -0,0 +1 @@ +All discussions must be created in a category, and repository administrators and maintainers define the categories for a repository. Categories can contain open-ended conversations, or conversations with a question/answer format. diff --git a/translations/de-DE/data/reusables/discussions/about-discussions.md b/translations/de-DE/data/reusables/discussions/about-discussions.md new file mode 100644 index 0000000000..c61b8b0f0a --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/about-discussions.md @@ -0,0 +1 @@ +Discussions are an open forum for conversation among maintainers and the community for a project on {% data variables.product.product_name %}. diff --git a/translations/de-DE/data/reusables/discussions/beta.md b/translations/de-DE/data/reusables/discussions/beta.md new file mode 100644 index 0000000000..0cb46374f7 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Hinweis:** {% data variables.product.prodname_discussions %} befindet sich derzeit in der Beta-Version und kann sich jederzeit verändern. + +{% endnote %} diff --git a/translations/de-DE/data/reusables/discussions/click-discussion-in-list.md b/translations/de-DE/data/reusables/discussions/click-discussion-in-list.md new file mode 100644 index 0000000000..8156c86331 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/click-discussion-in-list.md @@ -0,0 +1 @@ +1. In the list of discussions, click the discussion you want to view. ![Discussion in list of discussions for a repository](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/de-DE/data/reusables/discussions/discussions-tab.md b/translations/de-DE/data/reusables/discussions/discussions-tab.md new file mode 100644 index 0000000000..67795aa5ae --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/discussions-tab.md @@ -0,0 +1 @@ +1. Under your repository name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. !["Discussions" tab for a repository](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/translations/de-DE/data/reusables/discussions/edit-categories.md b/translations/de-DE/data/reusables/discussions/edit-categories.md new file mode 100644 index 0000000000..6f4f6af574 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/edit-categories.md @@ -0,0 +1 @@ +1. To the right of "Categories", click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing categories](/assets/images/help/discussions/click-edit-categories.png) diff --git a/translations/de-DE/data/reusables/discussions/edit-category-details.md b/translations/de-DE/data/reusables/discussions/edit-category-details.md new file mode 100644 index 0000000000..8004b70314 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/edit-category-details.md @@ -0,0 +1 @@ +Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." diff --git a/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md new file mode 100644 index 0000000000..187af0ad37 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -0,0 +1,5 @@ +You can enable or disable discussions for a repository. + +{% data reusables.repositories.navigate-to-repo %} +1. Klicke unter Deinem Repository-Namen auf {% octicon "gear" aria-label="The gear icon" %} **Settings** (Einstellungen). ![Schaltfläche „Repository settings" (Repository-Einstellungen)](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", select **Discussions**. ![Checkbox under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/de-DE/data/reusables/discussions/github-recognizes-members.md b/translations/de-DE/data/reusables/discussions/github-recognizes-members.md new file mode 100644 index 0000000000..b6874b910d --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/github-recognizes-members.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. diff --git a/translations/de-DE/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/de-DE/data/reusables/discussions/marking-a-comment-as-an-answer.md new file mode 100644 index 0000000000..bdefffdea0 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -0,0 +1,14 @@ +You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +When you mark a question as an answer, {% data variables.product.product_name %} will highlight the comment and replies to the comment to help visitors quickly find the answer. + +![Comment marked as answer to a discussion](/assets/images/help/discussions/comment-marked-as-answer.png) + +You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the unanswered discussion you want to mark as answered. ![Unanswered discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the discussion, find the comment you want to mark as the answer. +1. In the upper-right corner of the comment, click {% octicon "check-circle" aria-label="The circular check icon" %}. !["Mark as answer" circular check icon for marking comment as answer in a discussion](/assets/images/help/discussions/comment-mark-as-answer-button.png) +1. Optionally, to unmark a comment as the answer, click {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. diff --git a/translations/de-DE/data/reusables/discussions/repository-category-limit.md b/translations/de-DE/data/reusables/discussions/repository-category-limit.md new file mode 100644 index 0000000000..293d3632b5 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/repository-category-limit.md @@ -0,0 +1 @@ +Each repository can have up to 10 categories. diff --git a/translations/de-DE/data/reusables/discussions/starting-a-discussion.md b/translations/de-DE/data/reusables/discussions/starting-a-discussion.md new file mode 100644 index 0000000000..242e3abf9b --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/starting-a-discussion.md @@ -0,0 +1,6 @@ +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Click **New discussion**. !["New discussion" button within the "Discussions" tab for a repository](/assets/images/help/discussions/new-discussion-button.png) +1. Select the **Select Category** drop-down menu, and click a category for your discussion. !["Select Category" drop-down menu and list of available categories in a repository](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) +1. Type a title and body for your discussion. ![Text fields for new discussion's title and body](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) diff --git a/translations/de-DE/data/reusables/discussions/you-can-categorize-discussions.md b/translations/de-DE/data/reusables/discussions/you-can-categorize-discussions.md new file mode 100644 index 0000000000..bb05316d77 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/you-can-categorize-discussions.md @@ -0,0 +1 @@ +You can categorize discussions to help community members begin conversations in the right place, and to help community members find related discussions. diff --git a/translations/de-DE/data/reusables/discussions/you-can-convert-an-issue.md b/translations/de-DE/data/reusables/discussions/you-can-convert-an-issue.md new file mode 100644 index 0000000000..1421256e1f --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/you-can-convert-an-issue.md @@ -0,0 +1 @@ +If an issue turns out to be a question or open-ended conversation instead of a work item to track and prioritize, you can convert the issue to a discussion. diff --git a/translations/de-DE/data/reusables/discussions/you-can-use-discussions.md b/translations/de-DE/data/reusables/discussions/you-can-use-discussions.md new file mode 100644 index 0000000000..27c1ba7cb2 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/you-can-use-discussions.md @@ -0,0 +1 @@ +You can use discussions to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/discussions/you-cannot-convert-a-discussion.md b/translations/de-DE/data/reusables/discussions/you-cannot-convert-a-discussion.md new file mode 100644 index 0000000000..9e9b687b67 --- /dev/null +++ b/translations/de-DE/data/reusables/discussions/you-cannot-convert-a-discussion.md @@ -0,0 +1 @@ +You cannot convert a discussion to an issue. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-unpaid-account.md index 8d52e3374d..42f8f0f0e2 100644 --- a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-unpaid-account.md +++ b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-unpaid-account.md @@ -2,4 +2,4 @@ Wenn Dein Konto ausstehende unbezahlte Gebühren aufweist: * Der Speicher oder die Minuten, die in Deinem Konto für {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %} enthalten sind, werden nicht zurückgesetzt, bis die Zahlung erfolgreich verarbeitet wurde. * Für Konten mit verfügbarem Speicher oder verfügbaren Minuten im aktuellen Abrechnungszeitraum werden {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %} weiterhin verfügbar sein bis die eingeschlossene Nutzung erreicht ist. -* Für Konten, welche die eingeschlossene Nutzung für {% data variables.product.prodname_actions %} oder {% data variables.product.prodname_registry %} im aktuellen Abrechnungszeitraum erreicht haben, werden sowohl {% data variables.product.prodname_actions %} wie auch {% data variables.product.prodname_registry %} deaktiviert werden, um weitere Überschreitungen zu verhindern. Wenn Du Dein Konto per Rechnung bezahlst, musst du [Dein Kundendienstteam kontaktieren](https://enterprise.github.com/contact), um die Zahlung zu verarbeiten und Deine Nutzung zurückzusetzen. +* Für Konten, welche die eingeschlossene Nutzung für {% data variables.product.prodname_actions %} oder {% data variables.product.prodname_registry %} im aktuellen Abrechnungszeitraum erreicht haben, werden sowohl {% data variables.product.prodname_actions %} wie auch {% data variables.product.prodname_registry %} deaktiviert werden, um weitere Überschreitungen zu verhindern. 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 ef5133da41..07fa77c6a3 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 „[Informationen zu {% data variables.product.prodname_education %}](https://education.github.com/partners/schools)“. +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 „[Informationen zu {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)“. diff --git a/translations/de-DE/data/reusables/education/apply-for-team.md b/translations/de-DE/data/reusables/education/apply-for-team.md index d3fecd2cda..0b4fc2dd78 100644 --- a/translations/de-DE/data/reusables/education/apply-for-team.md +++ b/translations/de-DE/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Melden Sie sich kostenlos für[{% data variables.product.prodname_team %}](/articles/github-s-products) an, was unbegrenzte Benutzer- und private Repositorys ermöglicht. Weitere Informationen findest Du unter „[Einen Lehrer- oder Forscherrabatt beantragen](/articles/applying-for-an-educator-or-researcher-discount).“ +- Melden Sie sich kostenlos für[{% data variables.product.prodname_team %}](/articles/github-s-products) an, was unbegrenzte Benutzer- und private Repositorys ermöglicht. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." diff --git a/translations/de-DE/data/reusables/education/click-get-teacher-benefits.md b/translations/de-DE/data/reusables/education/click-get-teacher-benefits.md new file mode 100644 index 0000000000..25bbacd747 --- /dev/null +++ b/translations/de-DE/data/reusables/education/click-get-teacher-benefits.md @@ -0,0 +1 @@ +1. Under "Individuals", click **Get teacher benefits**. !["Get teacher benefits" on {% data variables.product.prodname_education %} homepage](/assets/images/help/education/click-get-teacher-benefits.png) diff --git a/translations/de-DE/data/reusables/education/educator-requirements.md b/translations/de-DE/data/reusables/education/educator-requirements.md new file mode 100644 index 0000000000..30c969f084 --- /dev/null +++ b/translations/de-DE/data/reusables/education/educator-requirements.md @@ -0,0 +1,6 @@ +To apply for an educator or researcher discount, you must meet the following requirements. + +- Lehrer, Universitätsmitglied oder Forscher sein. +- Have a verifiable school-issued email address. +- Upload documents that prove your school affiliation. +- Have a user account on {% data variables.product.product_name %}. diff --git a/translations/de-DE/data/reusables/gated-features/discussions.md b/translations/de-DE/data/reusables/gated-features/discussions.md new file mode 100644 index 0000000000..5ada0a25ee --- /dev/null +++ b/translations/de-DE/data/reusables/gated-features/discussions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_discussions %} is available in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/de-DE/data/reusables/github-actions/actions-billing.md b/translations/de-DE/data/reusables/github-actions/actions-billing.md index 5e2f301f51..ce71eadc8a 100644 --- a/translations/de-DE/data/reusables/github-actions/actions-billing.md +++ b/translations/de-DE/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. Für private Repositorys erhält jedes {% data variables.product.prodname_dotcom %} Konto eine bestimmte Menge von kostenlosen Minuten und Speicher, abhängig vom Produkt, das mit dem Konto verwendet wird. +{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. Für private Repositorys erhält jedes {% data variables.product.prodname_dotcom %} Konto eine bestimmte Menge von kostenlosen Minuten und Speicher, abhängig vom Produkt, das mit dem Konto verwendet wird. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/de-DE/data/reusables/github-actions/actions-on-examples.md b/translations/de-DE/data/reusables/github-actions/actions-on-examples.md index 9ed6e21997..c6d2556336 100644 --- a/translations/de-DE/data/reusables/github-actions/actions-on-examples.md +++ b/translations/de-DE/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -##### **Beispiel mit einem einzelnen Ereignis** +##### Beispiel mit einem einzelnen Ereignis ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -##### **Beispiel mit einer Ereignisliste** +##### Beispiel mit einer Ereignisliste ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -##### **Beispiel für die Verwendung mehrerer Ereignisse mit Aktivitätstypen oder Konfigurationen** +##### Beispiel für die Verwendung mehrerer Ereignisse mit Aktivitätstypen oder Konfigurationen Wenn Du Aktivitätstypen oder Konfigurationen für ein Ereignis angeben musst, musst Du jedes Ereignis separat konfigurieren. Du musst einen Doppelpunkt (`:`) an alle Ereignisse anhängen, einschließlich Ereignisse ohne Konfiguration. diff --git a/translations/de-DE/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/de-DE/data/reusables/github-actions/actions-spending-limit-brief.md new file mode 100644 index 0000000000..20d912fb21 --- /dev/null +++ b/translations/de-DE/data/reusables/github-actions/actions-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/de-DE/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/de-DE/data/reusables/github-actions/actions-spending-limit-detailed.md new file mode 100644 index 0000000000..e50f91f8d0 --- /dev/null +++ b/translations/de-DE/data/reusables/github-actions/actions-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.github-actions.actions-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where a workflow is run. Gutscheine für Dein Konto gelten nicht für {% data variables.product.prodname_actions %}-Überschreitungen. diff --git a/translations/de-DE/data/reusables/github-actions/contacting-support.md b/translations/de-DE/data/reusables/github-actions/contacting-support.md index 249000fe19..39c9203989 100644 --- a/translations/de-DE/data/reusables/github-actions/contacting-support.md +++ b/translations/de-DE/data/reusables/github-actions/contacting-support.md @@ -1,4 +1,4 @@ -Wenn Du Hilfe für irgendwelche Themen in Bezug auf Workflow-Konfigurationen brauchst, beispielsweise zu Syntax, {% data variables.product.prodname_dotcom %}-gehostete Läufer oder Bauvorgänge, suche nach einen vorhandenen Thema oder starte ein neues im [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} Board](https://github.community/c/github-actions). +If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). Wenn Sie Feedback oder Feature-Anfragen zu {% data variables.product.prodname_actions %} abgeben möchten, teilen Sie diese in den {% data variables.contact.contact_feedback_actions %}. diff --git a/translations/de-DE/data/reusables/github-actions/macos-runner-preview.md b/translations/de-DE/data/reusables/github-actions/macos-runner-preview.md index 88a2d482c4..e6db4f8803 100644 --- a/translations/de-DE/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/de-DE/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The MacOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the MacOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/de-DE/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/de-DE/data/reusables/github-actions/publish-to-maven-workflow-step.md index 15b5012f66..b424977238 100644 --- a/translations/de-DE/data/reusables/github-actions/publish-to-maven-workflow-step.md +++ b/translations/de-DE/data/reusables/github-actions/publish-to-maven-workflow-step.md @@ -1 +1 @@ -Führt den `mvn -B deploy` Befehl aus um das `ossrh` Repository zu veröffentlichen. Die Umgebungsvariable `MAVEN_USERNAME` wird mit dem Inhalt Deines Geheimnisses `OSSRH_USERNAME` gefüllt, und die Umgebungsvariable `MAVEN_PASSWORD` wird mit dem Inhalt Deines Geheimnisses `OSSRH_TOKEN` gefüllt. +Runs the `mvn --batch-mode deploy` command to publish to the `ossrh` repository. Die Umgebungsvariable `MAVEN_USERNAME` wird mit dem Inhalt Deines Geheimnisses `OSSRH_USERNAME` gefüllt, und die Umgebungsvariable `MAVEN_PASSWORD` wird mit dem Inhalt Deines Geheimnisses `OSSRH_TOKEN` gefüllt. diff --git a/translations/de-DE/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/de-DE/data/reusables/github-actions/publish-to-packages-workflow-step.md index 8c832b711a..0f75ff91a4 100644 --- a/translations/de-DE/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ b/translations/de-DE/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -Führt den Befehl `mvn -B deploy` aus, um nach {% data variables.product.prodname_registry %} zu veröffentlichen. Die `GITHUB_TOKEN`-Umgebungsvariable wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses gesetzt. +Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. Die `GITHUB_TOKEN`-Umgebungsvariable wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses gesetzt. diff --git a/translations/de-DE/data/reusables/github-insights/download-latest-release.md b/translations/de-DE/data/reusables/github-insights/download-latest-release.md index 4456c96520..9597327658 100644 --- a/translations/de-DE/data/reusables/github-insights/download-latest-release.md +++ b/translations/de-DE/data/reusables/github-insights/download-latest-release.md @@ -1,3 +1,3 @@ -1. Navigiere vom Anwendungsserver aus zum neuesten Release von {% data variables.product.prodname_insights %} auf der [Release-Seite](https://github.com/github/insights-releases/releases/latest) für `github/insights-releases`. +1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the Releases page for `github/insights-releases`. 2. Um den neuesten Release herunterzuladen, klicke unter „Assets" (Objekte) auf `insights-VERSION.tar.gz`. ![Installations-Objekt](/assets/images/help/insights/installation-tgz.png) 3. Entpacke das Verzeichnis. diff --git a/translations/de-DE/data/reusables/marketplace/app-transfer-to-org-for-verification.md b/translations/de-DE/data/reusables/marketplace/app-transfer-to-org-for-verification.md new file mode 100644 index 0000000000..0621a9e6e9 --- /dev/null +++ b/translations/de-DE/data/reusables/marketplace/app-transfer-to-org-for-verification.md @@ -0,0 +1 @@ +If you want to sell an app that's owned by your user account, first you'll need to transfer the app to an organization, and then request verification for a listing created by the organization. diff --git a/translations/de-DE/data/reusables/marketplace/free-plan-note.md b/translations/de-DE/data/reusables/marketplace/free-plan-note.md new file mode 100644 index 0000000000..bf63caa53d --- /dev/null +++ b/translations/de-DE/data/reusables/marketplace/free-plan-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** If you're listing an app on {% data variables.product.prodname_marketplace %}, you can't list your app with a free pricing plan if you offer a paid service outside of {% data variables.product.prodname_marketplace %}. + +{% endnote %} diff --git a/translations/de-DE/data/reusables/marketplace/launch-with-free.md b/translations/de-DE/data/reusables/marketplace/launch-with-free.md index 15230e218b..2151c241cc 100644 --- a/translations/de-DE/data/reusables/marketplace/launch-with-free.md +++ b/translations/de-DE/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can submit both an unverified and verified app. This will allow you to launch with a free version of your app. Once GitHub verifies your app, your listing will change from unverified to verified in {% data variables.product.prodname_marketplace %} and GitHub will publish your new pricing plans. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/de-DE/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/de-DE/data/reusables/marketplace/marketplace-billing-ui-requirements.md index 9c02badeae..5aa91ca839 100644 --- a/translations/de-DE/data/reusables/marketplace/marketplace-billing-ui-requirements.md +++ b/translations/de-DE/data/reusables/marketplace/marketplace-billing-ui-requirements.md @@ -1,7 +1,7 @@ -- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} must be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} It's highly recommended to allow customers to re-enable their previous plan. -- Customers must be able to upgrade from your app's UI if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` -- Customers must be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. -- Customers must be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: +- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} should be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} It's highly recommended to allow customers to re-enable their previous plan. +- Customers should be able to upgrade from your app's user interface if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` +- Customers should be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. +- Customers should be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: - Current plan and price. - New plans purchased. - Upgrades, downgrades, cancellations, and the number of remaining days in a free trial. diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-packages.md b/translations/de-DE/data/reusables/package_registry/authenticate-packages.md index 2344fb8cb3..fc1e022411 100644 --- a/translations/de-DE/data/reusables/package_registry/authenticate-packages.md +++ b/translations/de-DE/data/reusables/package_registry/authenticate-packages.md @@ -3,7 +3,7 @@ You need an access token to publish, install, and delete packages. Du kannst ein {% if currentVersion == "free-pro-team@latest" %} To authenticate using a {% data variables.product.prodname_actions %}-workflow: -- For package registries (`PACKAGE-REGISTRY.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`), you can use a `GITHUB_TOKEN`. +- 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. {% else %} To authenticate to diff --git a/translations/de-DE/data/reusables/package_registry/billing-for-container-registry.md b/translations/de-DE/data/reusables/package_registry/billing-for-container-registry.md index 7cf8e2459f..479e2d5b55 100644 --- a/translations/de-DE/data/reusables/package_registry/billing-for-container-registry.md +++ b/translations/de-DE/data/reusables/package_registry/billing-for-container-registry.md @@ -1,3 +1,3 @@ -During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." +During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-docker-for-use-with-github-packages)." After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the container registry. 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)." diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-beta-billing-note.md b/translations/de-DE/data/reusables/package_registry/container-registry-beta-billing-note.md index 0cc72194ac..2a50aed2c5 100644 --- a/translations/de-DE/data/reusables/package_registry/container-registry-beta-billing-note.md +++ b/translations/de-DE/data/reusables/package_registry/container-registry-beta-billing-note.md @@ -1,5 +1,5 @@ {% note %} -**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)“. +**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)“. {% endnote %} diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-beta.md b/translations/de-DE/data/reusables/package_registry/container-registry-beta.md index 24313880ba..6bd738198e 100644 --- a/translations/de-DE/data/reusables/package_registry/container-registry-beta.md +++ b/translations/de-DE/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" and "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} diff --git a/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md index 2df9364c31..a23fdc598b 100644 --- a/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md +++ b/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -1,5 +1,5 @@ {% warning %} -**Note:** The {% data variables.product.prodname_registry %} Docker registry will be superseded by {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} in a future {% data variables.product.product_name %} release{% endif %}.{% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" and "[Getting started with {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry)."{% endif %} +**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 %} {% endwarning %} diff --git a/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md index b0cddc8bcb..3b74dd6c78 100644 --- a/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md +++ b/translations/de-DE/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/package_registry/packages-billing.md b/translations/de-DE/data/reusables/package_registry/packages-billing.md index b7c471206b..d5c7ac5186 100644 --- a/translations/de-DE/data/reusables/package_registry/packages-billing.md +++ b/translations/de-DE/data/reusables/package_registry/packages-billing.md @@ -1 +1 @@ -Die {% data variables.product.prodname_registry %}-Nutzung ist für öffentliche Pakete kostenlos. Für private Pakete erhält jedes {% data variables.product.product_name %}-Konto eine bestimmte Menge an kostenlosem Speicher und Datenübertragung, abhängig vom Produkt, das mit dem Konto verwendet wird. Standardmäßig wird Dein Konto ein Ausgabenlimit von $0 haben, was die zusätzliche Nutzung von Speicher oder Datenübertragung verhindert, wenn Du die eingeschlossenen Beträge erreicht hast. Wenn Du Dein Ausgabenlimit über den Standardwert von $0 erhöhst, werden Dir alle zusätzlichen Speicher oder Datenübertragungen, auch als Überschreitungen bezeichnet, bis zu Deinem Ausgabenlimit in Rechnung gestellt. Gutscheine für Dein Konto gelten nicht für {% data variables.product.prodname_registry %}-Überschreitungen. +Die {% data variables.product.prodname_registry %}-Nutzung ist für öffentliche Pakete kostenlos. Für private Pakete erhält jedes {% data variables.product.product_name %}-Konto eine bestimmte Menge an kostenlosem Speicher und Datenübertragung, abhängig vom Produkt, das mit dem Konto verwendet wird. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/de-DE/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/de-DE/data/reusables/package_registry/packages-spending-limit-brief.md new file mode 100644 index 0000000000..ea07621d29 --- /dev/null +++ b/translations/de-DE/data/reusables/package_registry/packages-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/de-DE/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/de-DE/data/reusables/package_registry/packages-spending-limit-detailed.md new file mode 100644 index 0000000000..11e1b70e6c --- /dev/null +++ b/translations/de-DE/data/reusables/package_registry/packages-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.package_registry.packages-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. Gutscheine für Dein Konto gelten nicht für {% data variables.product.prodname_registry %}-Überschreitungen. diff --git a/translations/de-DE/data/reusables/package_registry/required-scopes.md b/translations/de-DE/data/reusables/package_registry/required-scopes.md index 3d877ad14f..b7b5f8ebf4 100644 --- a/translations/de-DE/data/reusables/package_registry/required-scopes.md +++ b/translations/de-DE/data/reusables/package_registry/required-scopes.md @@ -1 +1 @@ -Du musst ein persönliches Zugriffstoken mit dem entsprechenden Geltungsbereich verwenden, um Pakete in {% data variables.product.prodname_registry %} zu veröffentlichen und zu installieren. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +Du musst ein persönliches Zugriffstoken mit dem entsprechenden Geltungsbereich verwenden, um Pakete in {% data variables.product.prodname_registry %} zu veröffentlichen und zu installieren. Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)." diff --git a/translations/de-DE/data/reusables/package_registry/viewing-packages.md b/translations/de-DE/data/reusables/package_registry/viewing-packages.md index 5e4ea66f46..9b8fc3c8b4 100644 --- a/translations/de-DE/data/reusables/package_registry/viewing-packages.md +++ b/translations/de-DE/data/reusables/package_registry/viewing-packages.md @@ -1 +1 @@ -Nachdem Du ein Paket veröffentlicht hast, kannst Du das Paket auf {% data variables.product.prodname_dotcom %} ansehen. Weitere Informationen findest Du unter „[Anzeigen von Paketen](/packages/publishing-and-managing-packages/viewing-packages)." +Nachdem Du ein Paket veröffentlicht hast, kannst Du das Paket auf {% data variables.product.prodname_dotcom %} ansehen. Weitere Informationen findest Du unter „[Anzeigen von Paketen](/packages/manage-packages/viewing-packages)." diff --git a/translations/de-DE/data/reusables/repositories/dependency-review.md b/translations/de-DE/data/reusables/repositories/dependency-review.md new file mode 100644 index 0000000000..e780074c3c --- /dev/null +++ b/translations/de-DE/data/reusables/repositories/dependency-review.md @@ -0,0 +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)." +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-job-superlinter.md b/translations/de-DE/data/reusables/repositories/navigate-to-job-superlinter.md index 17fcbc8ecc..f08d2b37a6 100644 --- a/translations/de-DE/data/reusables/repositories/navigate-to-job-superlinter.md +++ b/translations/de-DE/data/reusables/repositories/navigate-to-job-superlinter.md @@ -1,5 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. Klicke in der linken Seitenleiste auf den Auftrag, den Du sehen willst. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% else %} 1. Klicke in der linken Seitenleiste auf den Auftrag, den Du sehen willst. ![Select a workflow job](/assets/images/help/repository/workflow-job.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/de-DE/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/de-DE/data/reusables/repositories/two-dot-diff-comparison-example-urls.md index 8e00d179bd..1a25944892 100644 --- a/translations/de-DE/data/reusables/repositories/two-dot-diff-comparison-example-urls.md +++ b/translations/de-DE/data/reusables/repositories/two-dot-diff-comparison-example-urls.md @@ -1 +1 @@ -Beispielsweise verwendet diese URL die gekürzten siebenstelligen SHA-Codes um die Commits `c3a414e` und `faf7c6f` zu vergleichen: `https://github.com/github/linguist/compare/c3a414e..faf7c6f.` +For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`. diff --git a/translations/de-DE/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/de-DE/data/reusables/repositories/view-failed-job-results-superlinter.md index 434994a169..d436c99e66 100644 --- a/translations/de-DE/data/reusables/repositories/view-failed-job-results-superlinter.md +++ b/translations/de-DE/data/reusables/repositories/view-failed-job-results-superlinter.md @@ -1,5 +1,8 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Any failed steps are automatically expanded to display the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png) +1. Any failed steps are automatically expanded to display the results. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %} +![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png){% endif %} {% else %} 1. Expand the **Run Super-Linter** step to view the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results.png) {% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/repositories/view-specific-line-superlinter.md b/translations/de-DE/data/reusables/repositories/view-specific-line-superlinter.md index 11a0a73f53..9a63e35805 100644 --- a/translations/de-DE/data/reusables/repositories/view-specific-line-superlinter.md +++ b/translations/de-DE/data/reusables/repositories/view-specific-line-superlinter.md @@ -1,5 +1,10 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Klicke bei Bedarf auf die Zeilennummer des Schritts, um einen Link zu einer bestimmten Zeile in den Logs zu erhalten. You can then copy the link from the address bar of your web browser. ![Schaltfläche zum Kopieren des Links](/assets/images/help/repository/copy-link-button-updated.png) +1. Klicke bei Bedarf auf die Zeilennummer des Schritts, um einen Link zu einer bestimmten Zeile in den Logs zu erhalten. You can then copy the link from the address bar of your web browser. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Schaltfläche zum Kopieren des Links](/assets/images/help/repository/copy-link-button-updated-2.png) + {% else %} + ![Schaltfläche zum Kopieren des Links](/assets/images/help/repository/copy-link-button-updated.png) + {% endif %} {% else %} 1. Klicke bei Bedarf auf die Zeilennummer des Schritts, um einen Link zu einer bestimmten Zeile in den Logs zu erhalten. You can then copy the link from the address bar of your web browser. ![Schaltfläche zum Kopieren des Links](/assets/images/help/repository/copy-link-button.png) {% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/search/date_gt_lt.md b/translations/de-DE/data/reusables/search/date_gt_lt.md index ef4b10461b..57a206f28c 100644 --- a/translations/de-DE/data/reusables/search/date_gt_lt.md +++ b/translations/de-DE/data/reusables/search/date_gt_lt.md @@ -1 +1 @@ -Datumsangaben unterstützen [„größer als", „kleiner als" und Bereichsqualifizierer](/articles/understanding-the-search-syntax). +When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." diff --git a/translations/de-DE/data/reusables/secret-scanning/api-beta.md b/translations/de-DE/data/reusables/secret-scanning/api-beta.md new file mode 100644 index 0000000000..510473ea8d --- /dev/null +++ b/translations/de-DE/data/reusables/secret-scanning/api-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The {% data variables.product.prodname_secret_scanning %} API is currently in beta and subject to change. + +{% endnote %} diff --git a/translations/de-DE/data/reusables/sponsors/billing-switcher.md b/translations/de-DE/data/reusables/sponsors/billing-switcher.md new file mode 100644 index 0000000000..4831c34a3b --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/billing-switcher.md @@ -0,0 +1 @@ +1. Optionally, to manage your sponsorship on behalf of an organization, in the upper-left corner, use the **Personal settings** drop-down menu, and click the organization. ![Drop-down menu to switch accounts for settings](/assets/images/help/sponsors/billing-account-switcher.png) diff --git a/translations/de-DE/data/reusables/sponsors/change-tier.md b/translations/de-DE/data/reusables/sponsors/change-tier.md index a8858558bf..7a83c876c8 100644 --- a/translations/de-DE/data/reusables/sponsors/change-tier.md +++ b/translations/de-DE/data/reusables/sponsors/change-tier.md @@ -1 +1 @@ -1. Unter „{% data variables.product.prodname_sponsors %}", rechts neben dem unterstützten Open-Source-Mitarbeiter, klicke neben Deinem gespendeten Betrag auf {% octicon "triangle-down" aria-label="The down triangle octicon" %}, dann klicke auf **Change tier** (Stufe ändern). ![Schaltfläche „Change tier" (Stufe ändern)](/assets/images/help/billing/edit-sponsor-billing.png) +1. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored account, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your tier amount, then click **Change tier**. ![Schaltfläche „Change tier" (Stufe ändern)](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/de-DE/data/reusables/sponsors/choose-updates.md b/translations/de-DE/data/reusables/sponsors/choose-updates.md new file mode 100644 index 0000000000..ade59cf05b --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/choose-updates.md @@ -0,0 +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) diff --git a/translations/de-DE/data/reusables/sponsors/manage-sponsorship.md b/translations/de-DE/data/reusables/sponsors/manage-sponsorship.md new file mode 100644 index 0000000000..b6373aa759 --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/manage-sponsorship.md @@ -0,0 +1 @@ +1. To the right of your current tier, click **Manage**. ![Schaltfläche „Manage your sponsorship" (Verwalte Dein Sponsoring)](/assets/images/help/sponsors/manage-your-sponsorship-button.png) \ No newline at end of file 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 new file mode 100644 index 0000000000..0cd08d5382 --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md @@ -0,0 +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)." diff --git a/translations/de-DE/data/reusables/sponsors/maximum-tier.md b/translations/de-DE/data/reusables/sponsors/maximum-tier.md index b29b42fb82..ba34168bf8 100644 --- a/translations/de-DE/data/reusables/sponsors/maximum-tier.md +++ b/translations/de-DE/data/reusables/sponsors/maximum-tier.md @@ -1 +1 @@ -Der Höchstpreis beträgt 6000 USD pro Monat. +Der Höchstpreis beträgt 12,000 USD pro Monat. diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsored-account.md new file mode 100644 index 0000000000..def70f43f1 --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsored-account.md @@ -0,0 +1 @@ +1. On {% data variables.product.product_name %}, navigate to the sponsored account's profile. diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-dashboard.md new file mode 100644 index 0000000000..acd677932f --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-dashboard.md @@ -0,0 +1,2 @@ +1. Klicke in der rechten oberen Ecke einer beliebigen Seite auf Dein Profilfoto und klicke dann auf **{% data variables.product.prodname_sponsors %}**. ![Schaltfläche {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) +2. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**. ![Schaltfläche „Developer sponsors dashboard" (Dashboard Entwickler-Sponsoren)](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) diff --git a/translations/de-DE/data/reusables/sponsors/no-fees.md b/translations/de-DE/data/reusables/sponsors/no-fees.md index 484d10068e..d76e208205 100644 --- a/translations/de-DE/data/reusables/sponsors/no-fees.md +++ b/translations/de-DE/data/reusables/sponsors/no-fees.md @@ -1 +1 @@ -{% data variables.product.prodname_sponsors %} erhebt keine Gebühren für das Sponsoring von Benutzerkonten, so dass 100% dieser Sponsorenbeiträge an den unterstützten Entwickler oder die unterstützte Organisation gehen. +{% data variables.product.prodname_sponsors %} erhebt keine Gebühren für das Sponsoring von Benutzerkonten, so dass 100% dieser Sponsorenbeiträge an den unterstützten Entwickler oder die unterstützte Organisation gehen. The 10% fee for sponsorships from organizations is waived during the beta. diff --git a/translations/de-DE/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/de-DE/data/reusables/sponsors/org-sponsors-release-phase.md new file mode 100644 index 0000000000..75983073a4 --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/org-sponsors-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Sponsoring on behalf of an organization is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md b/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md new file mode 100644 index 0000000000..f201de957c --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md @@ -0,0 +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 diff --git a/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md b/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md index b539ac6147..56a047d867 100644 --- a/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md @@ -1 +1 @@ -Du wirst für die Zeit bis zu Deinem nächsten regulären Abrechnungsdatum sofort mit einem anteiligen Betrag belastet. +If you're sponsoring on behalf of your user account, you will immediately be charged a prorated amount for the time until your next regular billing date. If you're sponsoring on behalf of an organization, you can choose to pay the prorated amount or make the full monthly payment. diff --git a/translations/de-DE/data/reusables/sponsors/sponsor-account.md b/translations/de-DE/data/reusables/sponsors/sponsor-account.md new file mode 100644 index 0000000000..a7caeaa488 --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/sponsor-account.md @@ -0,0 +1 @@ +1. Click **Sponsor _ACCOUNT_**. ![Schaltfläche „Sponsor“ (Unterstützen)](/assets/images/help/sponsors/sponsor-developer-button.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/sponsors/sponsorship-dashboard.md b/translations/de-DE/data/reusables/sponsors/sponsorship-dashboard.md new file mode 100644 index 0000000000..e0dfd2e8bd --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/sponsorship-dashboard.md @@ -0,0 +1,4 @@ +1. Navigate to your sponsorship dashboard for the account. + - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![Schaltfläche „Sponsoring“](/assets/images/help/profile/sponsoring-button.png) + - If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![Schaltfläche „Sponsoring“](/assets/images/help/sponsors/org-sponsoring-button.png) +1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/de-DE/data/reusables/sponsors/sponsorship-details.md b/translations/de-DE/data/reusables/sponsors/sponsorship-details.md index c610757ea8..6776f06131 100644 --- a/translations/de-DE/data/reusables/sponsors/sponsorship-details.md +++ b/translations/de-DE/data/reusables/sponsors/sponsorship-details.md @@ -1 +1 @@ -Jeder mit einem {% data variables.product.product_name %}-Konto kann jeden mit einem „unterstützter Entwickler"-Profil oder einem „unterstütze Organisation"-Profil durch eine wiederkehrende monatliche Zahlung unterstützen. Du kannst aus mehreren Sponsoring-Stufen mit monatlichen Zahlungsbeträgen und Vorteilen wählen, die vom unterstützten Entwickler oder der unterstützten Organisation festgelegt werden. 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 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/webhooks/app_always_desc.md b/translations/de-DE/data/reusables/webhooks/app_always_desc.md new file mode 100644 index 0000000000..d52aaebe58 --- /dev/null +++ b/translations/de-DE/data/reusables/webhooks/app_always_desc.md @@ -0,0 +1 @@ +`installation` | `object` | The {% data variables.product.prodname_github_app %} installation. diff --git a/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_properties.md new file mode 100644 index 0000000000..5c5efddebb --- /dev/null +++ b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -0,0 +1,4 @@ +| Schlüssel | Typ | Beschreibung | +| --------- | -------- | -------------------------------------------------------------------------------------------- | +| `action` | `string` | die Aktion, die durchgeführt wurde. This can be either `created`, `resolved`, or `reopened`. | +| `Warnung` | `Objekt` | The secret scanning alert involved in the event. | diff --git a/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md new file mode 100644 index 0000000000..5da7e75271 --- /dev/null +++ b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -0,0 +1 @@ +Activity related to secret scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see “[About secret scanning](/github/administering-a-repository/about-secret-scanning).” diff --git a/translations/de-DE/data/ui.yml b/translations/de-DE/data/ui.yml index a1fbeca8d7..543dbe9632 100644 --- a/translations/de-DE/data/ui.yml +++ b/translations/de-DE/data/ui.yml @@ -7,7 +7,7 @@ header: release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: Wir veröffentlichen regelmäßig Aktualisierungen unserer Dokumentation, und die Übersetzung dieser Seite kann noch im Gange sein. Die neuesten Informationen findest Du in der englischsprachigen Dokumentation. Informieren Sie uns bitte, falls auf dieser Seite ein Problem mit den Übersetzungen vorliegt. localization_in_progress: Hallo, Entdecker! An dieser Seite wird aktiv gearbeitet, oder sie wird noch übersetzt. Die neuesten und genauesten Informationen findest Du in unserer englischsprachigen Dokumentation. - early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' + early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' search: need_help: Benötigen Sie Hilfe? placeholder: Themen, Produkte suchen … @@ -56,6 +56,14 @@ contribution_cta: button: Make a contribution or: Oder, to_guidelines: learn how to contribute. +enterprise_releases_list: + title: Enterprise Server Releases + currently_supported: Currently supported + currently_supported_message: See GitHub Enterprise for information about the latest release. + deprecated: Deprecated + deprecated_message: 'These docs remain available but are no longer maintained:' + deprecated_developer: Deprecated on developer.github.com + deprecated_developer_message: 'These docs remain available on the legacy developer site but are no longer maintained:' products: graphql: reference: @@ -123,3 +131,4 @@ footer: product_landing: quick_start: Schnellstart reference_guides: Reference guides + overview: Übersicht diff --git a/translations/de-DE/data/variables/action_code_examples.yml b/translations/de-DE/data/variables/action_code_examples.yml index a5b26266eb..317c8d5fe4 100644 --- a/translations/de-DE/data/variables/action_code_examples.yml +++ b/translations/de-DE/data/variables/action_code_examples.yml @@ -1,12 +1,4 @@ --- -- - title: Starter workflows - description: Workflow files for helping people get started with GitHub Actions - languages: TypeScript - href: actions/starter-workflows - tags: - - official - - Workflow - title: Example services description: Example workflows using service containers @@ -334,3 +326,10 @@ - monorepo - copybara - Workflow +- + title: Deploy static files to GitHub Pages + description: GitHub Action to publish website to GitHub Pages automatically + languages: 'TypeScript, JavaScript' + href: peaceiris/actions-gh-pages + tags: + - publishing diff --git a/translations/de-DE/data/variables/command_line.yml b/translations/de-DE/data/variables/command_line.yml index 805c67903e..5d1f568716 100644 --- a/translations/de-DE/data/variables/command_line.yml +++ b/translations/de-DE/data/variables/command_line.yml @@ -1,5 +1,5 @@ --- -#Use this variable wherever backticks are necessary: https://github.com/github/docs-internal/pull/1176#discussion-diff-19853931 +#Use this variable wherever backticks are necessary backticks: >- {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} #Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!) diff --git a/translations/de-DE/data/variables/discussions_community_examples.yml b/translations/de-DE/data/variables/discussions_community_examples.yml new file mode 100644 index 0000000000..8b3594f2ec --- /dev/null +++ b/translations/de-DE/data/variables/discussions_community_examples.yml @@ -0,0 +1,38 @@ +--- +- + #Images and descriptions are pulled directly from the repo + repo: vercel/next.js + description: The React Framework +- + repo: gatsbyjs/gatsby + description: Build blazing fast, modern apps and websites with React +- + repo: nodejs/node + description: Node.js JavaScript runtime ✨🐢🚀✨ +- + repo: tailwindlabs/tailwindcss + description: A utility-first CSS framework for rapid UI development. +- + repo: laravel/framework + description: Laravel is a web application framework with expressive, elegant syntax. +- + repo: prisma/prisma + description: Modern database access (ORM alternative) for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite +- + repo: dotnet/csharplang + description: 'The official repo for the design of the C# programming language' +- + repo: home-assistant/frontend + description: '🍭 Frontend for Home Assistant' +- + repo: jspsych/jsPsych + description: A JavaScript library for creating and running behavioral experiments in a web browser +- + repo: adonisjs/core + description: '🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence' +- + repo: ImageMagick/ImageMagick + description: '🧙‍♂️ ImageMagick 7' +- + repo: react-hook-form/react-hook-form + description: '📋 React Hooks for forms validation (Web + React Native)' diff --git a/translations/de-DE/data/variables/product.yml b/translations/de-DE/data/variables/product.yml index cb7f6f3384..411bb22546 100644 --- a/translations/de-DE/data/variables/product.yml +++ b/translations/de-DE/data/variables/product.yml @@ -37,7 +37,10 @@ prodname_unified_search: 'gemeinsame Suche' #GitHub Education prodname_education: 'GitHub Education' prodname_education_community: 'Education Community' +prodname_education_community_with_url: 'the [GitHub Education Community](https://education.github.community)' prodname_classroom: 'GitHub Classroom' +prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)' +prodname_campus_program: 'GitHub Campus Program' prodname_student_pack: 'GitHub Student Developer Pack' #GitHub CLI prodname_cli: 'GitHub CLI' @@ -69,6 +72,8 @@ ae_azure_ad_app_link: 'the [GitHub AE application](https://azuremarketplace.micr prodname_actions: 'GitHub Actions' #GitHub Debug prodname_debug: 'GitHub Debug' +#GitHub Discussions +prodname_discussions: 'GitHub Discussions' #GitHub Packages prodname_registry: 'GitHub Packages' prodname_github_container_registry: 'GitHub Container Registry' 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 788a53ead4..2c1eb510df 100644 --- a/translations/ja-JP/content/actions/creating-actions/about-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/about-actions.md @@ -30,11 +30,11 @@ versions: DockerコンテナのアクションとJavaScriptのアクションをビルドできます。 アクションには、アクションの入力、出力、およびメインのエントリポイントを定義するメタデータファイルが必要です。 このメタデータのファイル名は`action.yml`もしくは`action.yaml`でなければなりません。 詳しい情報については、「[{% data variables.product.prodname_actions %} のメタデータ構文](/articles/metadata-syntax-for-github-actions)」を参照してください。 -| 種類 | オペレーティングシステム | -| ---------- | ------------------- | -| Dockerコンテナ | Linux | -| JavaScript | Linux、MacOS、Windows | -| 複合実行ステップ | Linux、MacOS、Windows | +| 種類 | オペレーティングシステム | +| ---------- | --------------------- | +| Dockerコンテナ | Linux | +| JavaScript | Linux, macOS, Windows | +| 複合実行ステップ | Linux, macOS, Windows | #### Docker コンテナーアクション 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 533872851e..37554afa8f 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 @@ -227,6 +227,10 @@ jobs: ``` {% endraw %} -リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 "Hello Mona the Octocat"、または`who-to-greet` 入力に指定した名前とタイムスタンプがログに出力されます。 +リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/docker-action-workflow-run-updated.png) +{% else %} ![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/docker-action-workflow-run.png) +{% endif %} 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 8267e77f3e..d6d02ce5c4 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 @@ -176,7 +176,7 @@ git tag -a -m "My first action release" v1 git push --follow-tags ``` -`node_modules` ディレクトリをチェックインする代わりに、[`@vercel/ncc`](https://github.com/vercel/ncc) というツールを使用して、コードとモジュールを配信用の 1 つのファイルにコンパイルすることができます。 +Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. 1. ターミナルで次のコマンドを実行し、`vercel/ncc` をインストールします: `npm i -g @vercel/ncc` @@ -256,9 +256,11 @@ jobs: ``` {% endraw %} -リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 "Hello Mona the Octocat"、または`who-to-greet` 入力に指定した名前とタイムスタンプがログに出力されます。 +リポジトリから [**Actions**] タブをクリックして、最新のワークフロー実行を選択します。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} ![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/javascript-action-workflow-run-updated.png) {% else %} ![ワークフローでアクションを使用しているスクリーンショット](/assets/images/help/repository/javascript-action-workflow-run.png) 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 c5e5fceb58..d6c213db58 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 @@ -22,19 +22,19 @@ Docker及びJavaScriptアクションにはメタデータファイルが必要 アクションのメタデータファイルはYAML構文を使います。 YAMLについて詳しくない場合は、「[Learn YAML in five minutes (5分で学ぶYAML)](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)」をお読みください。 -### **`name`** +### `name` **必須**アクションの名前。 {% data variables.product.prodname_dotcom %}は`name`を**Actions**タブに表示して、それぞれのジョブのアクションを見て区別しやすくします。 -### **`作者`** +### `作者` **オプション** アクションの作者の名前。 -### **`説明`** +### `説明` **必須** アクションの短い説明。 -### **`inputs`** +### `inputs` **オプション** inputsパラメーターを使うと、アクションが実行時に使うデータを指定できます。 {% data variables.product.prodname_dotcom %}は、inputsパラメータを環境変数として保存します。 大文字が使われているInputsのidは、実行時に小文字に変換されます。 inputsのidには小文字を使うことをおすすめします。 @@ -57,23 +57,23 @@ inputs: たとえば、ワークフローがnumOctocats及びoctocatEyeColorという入力を定義すると、アクションのコードはこれらの入力の値を`INPUT_NUMOCTOCATS`及び`INPUT_OCTOCATEYECOLOR`という環境変数で読み取れます。 -#### **`inputs.`** +#### `inputs.` **必須** `文字列型`の識別子で、入力と結びつけられます。 ``の値は、入力のメタデータのマップです。 ``は、`inputs`オブジェクト内でユニークな識別子でなければなりません。 ``は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。 -#### **`inputs..description`** +#### `inputs..description` **必須** 入力パラメーターの`文字列`での説明。 -#### **`inputs..required`** +#### `inputs..required` **必須** この入力パラメーターがアクションに必須かどうかを示す`論理値`。 パラメーターが必須の場合は`true`に設定してください。 -#### **`inputs..default`** +#### `inputs..default` **オプション** デフォルト値を示す`文字列`。 デフォルト値は、入力パラメーターがワークフローファイルで指定されたなかった場合に使われます。 -### **`outputs`** +### `outputs` **オプション** アクションが設定するデータを宣言できる出力パラメータ。 ワークフローで後に実行されるアクションは、先行して実行されたアクションが設定した出力データを利用できます。 たとえば、2つの入力を加算(x + y = z)するアクションがあれば、そのアクションは他のアクションが入力として利用できる合計値(z)を出力できます。 @@ -87,15 +87,15 @@ outputs: description: '入力の合計' ``` -#### **`outputs.`** +#### `outputs.` **必須** `文字列型`の識別子で、出力と結びつけられます。 ``の値は、出力のメタデータのマップです。 ``は、`outputs`オブジェクト内でユニークな識別子でなければなりません。 ``は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。 -#### **`outputs..description`** +#### `outputs..description` **必須** 出力パラメーターの`文字列`での説明。 -### 複合実行ステップアクションのための **`outputs`** +### `outputs` for composite run steps actions **オプション** `outputs` `outputs.` および `outputs..description`（「[{% data variables.product.prodname_actions %} の `outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)」を参照）と同じパラメーターを使用しますが、`value` トークンも含まれます。 @@ -116,12 +116,12 @@ runs: ``` {% endraw %} -#### **`outputs.`** +#### `outputs..value` **必須** 出力パラメーターがマップされる値。 これを `string` またはコンテキスト付きの式に設定できます。 たとえば、`steps` コンテキストを使用して、出力の `value` をステップの出力値に設定できます。 コンテキストと式の構文の使用方法について詳しくは、「[{% data variables.product.prodname_actions %} のコンテキストと式の構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 -### JavaScriptアクションのための**`runs`** +### `runs` for JavaScript actions **必須** アクションのコードと、コードを実行するのに使われるアプリケーションへのパスを設定します。 @@ -133,15 +133,15 @@ runs: main: 'main.js' ``` -#### **`runs.using`** +#### `runs.using` **必須** [`main`](#runsmain)で指定されたコードを実行するのに使われるアプリケーション。 -#### **`runs.main`** +#### `runs.main` **必須** アクションのコードを含むファイル。 [`using`](#runsusing)で指定されたアプリケーションがこのファイルを実行します。 -#### **`pre`** +#### `pre` **オプション** `main:`アクションが開始される前の、ジョブの開始時点でスクリプトを実行できるようにします。 たとえば、`pre:`を使って必要なセットアップスクリプトを実行できます。 [`using`](#runsusing)構文を使って指定されたアプリケーションがこのファイルを実行します。 `pre:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。 @@ -155,7 +155,7 @@ runs: post: 'cleanup.js' ``` -#### **`pre-if`** +#### `pre-if` **オプション** `pre:`アクションの実行条件を定義できるようにしてくれます。 `pre:`アクションは、`pre-if`内の条件が満たされたときにのみ実行されます。 設定されなかった場合、`pre-if`のデフォルトは`always()`になります。 まだステップは実行されていないので、`step`コンテキストは利用できないことに注意してください。 @@ -166,7 +166,7 @@ runs: pre-if: 'runner.os == linux' ``` -#### **`post`** +#### `post` **オプション** `main:`アクションの終了後、ジョブの終わりにスクリプトを実行できるようにします。 たとえば、`post:`を使って特定のプロセスを終了させたり、不要なファイルを削除したりできます。 [`using`](#runsusing)構文を使って指定されたアプリケーションがこのファイルを実行します。 @@ -181,7 +181,7 @@ runs: `post:`アクションはデフォルトで常に実行されますが、`post-if`を使ってこれをオーバーライドすることができます。 -#### **`post-if`** +#### `post-if` **オプション** `post:`アクションの実行条件を定義できるようにしてくれます。 `post:`アクションは、`post-if`内の条件が満たされたときにのみ実行されます。 設定されなかった場合、`post-if`のデフォルトは`always()`になります。 @@ -192,19 +192,19 @@ runs: post-if: 'runner.os == linux' ``` -### 複合実行ステップアクションのための **`runs`** +### `runs` for composite run steps actions **必須** 複合アクションへのパス、およびコードの実行に使用されるアプリケーションを設定します。 -#### **`runs.using`** +#### `runs.using` **必須** 複合実行ステップアクションを使用するには、これを「`composite`」に設定します。 -#### **`runs.steps`** +#### `runs.steps` **必須** このアクションで実行する予定の実行ステップ。 -##### **`runs.steps.run`** +##### `runs.steps.run` **必須** 実行するコマンド。 これは、インラインでも、アクションリポジトリ内のスクリプトでもかまいません。 ```yaml @@ -227,27 +227,27 @@ runs: 詳しい情報については、「[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)」を参照してください。 -##### **`runs.steps.shell`** +##### `runs.steps.shell` **必須** コマンドを実行するシェル。 [こちら](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)にリストされている任意のシェルを使用できます。 -##### **`runs.steps.name`** +##### `runs.steps.name` **オプション** 複合実行ステップの名前。 -##### **`runs.steps.id`** +##### `runs.steps.id` **オプション** ステップの一意の識別子。 `id`を使って、コンテキストのステップを参照することができます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 -##### **`runs.steps.env`** +##### `runs.steps.env` **オプション** そのステップのみの環境変数の `map` を設定します。 ワークフローに保存されている環境変数を変更する場合は、複合実行ステップで {% if currentVersion == "free-pro-team@latest" または currentVersion ver_gt "enterprise-server@2.22" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} を使用します。 -##### **`runs.steps.working-directory`** +##### `runs.steps.working-directory` **オプション** コマンドを実行する作業ディレクトリを指定します。 -### Dockerアクションのための**`runs`** +### `runs` for Docker actions **必須** Dockerアクションのために使われるイメージを設定します。 @@ -267,11 +267,11 @@ runs: image: 'docker://debian:stretch-slim' ``` -#### **`runs.using`** +#### `runs.using` **必須** この値は`'docker'`に設定しなければなりません。 -#### **`pre-entrypoint`** +#### `pre-entrypoint` **オプション** `entrypoint`アクションが始まる前にスクリプトを実行できるようにしてくれます。 たとえば、`pre-entrypoint:`を使って必要なセットアップスクリプトを実行できます。 {% data variables.product.prodname_actions %}は`docker run`を使ってこのアクションを起動し、同じベースイメージを使う新しいコンテナ内でスクリプトを実行します。 これはすなわち、ランタイムの状態はメインの`entrypoint`コンテナとは異なるということで、必要な状態はワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスしなければなりません。 `pre-entrypoint:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。 @@ -289,21 +289,21 @@ runs: entrypoint: 'main.sh' ``` -#### **`runs.image`** +#### `runs.image` **必須** アクションを実行するためにコンテナとして使われるDockerイメージ。 この値には、Dockerのベースイメージ名、自分のリポジトリ中のローカル`Dockerfile`、Docker Hubあるいはその他のレジストリ中のパブリックなイメージを指定できます。 自分のリポジトリにローカルな`Dockerfile`を参照するには、アクションのメタデータファイルに対する相対的なパスを使ってください。 `docker`アプリケーションがこのファイルを実行します。 -#### **`runs.env`** +#### `runs.env` **オプション** コンテナの環境に設定する環境変数のキー/値のマップを指定します。 -#### **`runs.entrypoint`** +#### `runs.entrypoint` **オプション** `Dockerfile`中のDockerの`ENTRYPOINT`をオーバーライドします。あるいは、もしそれが指定されていなかった場合に設定します。 `entrypoint`は、`Dockerfile`で`ENTRYPOINT`が指定されていない場合や、`ENTRYPOINT`命令をオーバーライドしたい場合に使ってください。 `entrypoint`を省略すると、Dockerの`ENTRYPOINT`命令で指定されたコマンドが実行されます。 Dockerの`ENTRYPOINT`命令には、_shell_形式と_exec_形式があります。 Dockerの`ENTRYPOINT`のドキュメンテーションは、`ENTRYPOINT`の_exec_形式を使うことを勧めています。 `entrypoint`の実行に関する詳しい情報については、「[{% data variables.product.prodname_actions %}のDockerfileサポート](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)」を参照してください。 -#### **`post-entrypoint`** +#### `post-entrypoint` **オプション** `run.entrypoint`アクションが完了した後に、クリーンアップスクリプトを実行できるようにしてくれます。 {% data variables.product.prodname_actions %}はこのアクションを起動するのに`docker run`を使います。 {% data variables.product.prodname_actions %}はスクリプトを同じベースイメージを使って新しいコンテナ内で実行するので、ランタイムの状態はメインの`entrypoint`コンテナとは異なります。 必要な状態には、ワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスできます。 `post-entrypoint:`アクションはデフォルトで常に実行されますが、[`post-if`](#post-if)を使ってこれをオーバーライドすることができます。 @@ -317,7 +317,7 @@ runs: post-entrypoint: 'cleanup.sh' ``` -#### **`runs.args`** +#### `runs.args` **オプション** Dockerコンテナへの入力を定義する文字列の配列。 入力には、ハードコードされた文字列を含めることができます。 {% data variables.product.prodname_dotcom %}は、コンテナの起動時に`args`をコンテナの`ENTRYPOINT`に渡します。 @@ -343,7 +343,7 @@ runs: ``` {% endraw %} -### **`branding`** +### `branding` アクションをパーソナライズして見分けられるようにするために、カラーと[Feather](https://feathericons.com/)アイコンを使ってバッジを作ることができます。 バッジは、[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)内のアクション名の隣に表示されます。 @@ -355,11 +355,11 @@ branding: color: 'green' ``` -#### **`branding.color`** +#### `branding.color` バッジの背景カラー。 `white`、`yellow`、`blue`、`green`、`orange`、`red`、`purple`、`gray-dark`のいずれか。 -#### **`branding.icon`** +#### `branding.icon` 利用する[Feather](https://feathericons.com/)アイコンの名前。 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 5672b2da89..d78c6b8040 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 @@ -25,7 +25,11 @@ versions: そうすれば、プルリクエストをレビューする際には、ワークフローの実行を見て生成された成果物をダウンロードできるでしょう。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down-updated.png) +{% else %} ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down.png) +{% endif %} こうすれば、プルリクエスト中のコードを自分のマシン上で実行できるので、プルリクエストのデバッグやテストに役立ちます。 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 9f5b4290f4..cc681c5aab 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 @@ -53,7 +53,7 @@ jobs: with: java-version: 1.8 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -85,7 +85,7 @@ steps: with: java-version: 1.8 - name: Run the Maven verify phase - run: mvn -B verify --file pom-ci.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -108,7 +108,7 @@ steps: key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} restore-keys: ${{ runner.os }}-m2 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -125,7 +125,7 @@ Mavenは通常、JAR、EAR、WARのような出力ファイルを`target`ディ steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 - - run: mvn -B package --file pom.xml + - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 with: 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 546480993e..30c070c4ea 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 @@ -60,7 +60,11 @@ jobs: * `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory. * `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. 例: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png) + {% else %} ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png) + {% endif %} * `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following: ``` 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 b12bbedcfc..3e6a7ad009 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 @@ -84,7 +84,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -143,7 +143,7 @@ jobs: with: java-version: 1.8 - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` @@ -182,7 +182,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish to the Maven Central Repository - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -191,7 +191,7 @@ jobs: with: java-version: 1.8 - name: Publish to GitHub Packages - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` 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 612853d6ef..7bde7bd386 100644 --- a/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ja-JP/content/actions/guides/publishing-nodejs-packages.md @@ -8,8 +8,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data variables.product.prodname_actions %} の支払いを管理する diff --git a/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 9b9bf3610d..9bf8f04fcd 100644 --- a/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ja-JP/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,8 +11,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data variables.product.prodname_actions %} の支払いを管理する diff --git a/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ja-JP/content/actions/guides/storing-workflow-data-as-artifacts.md index b617b0a5d6..649df5503d 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 @@ -108,8 +108,6 @@ versions: パス: output/test/code-coverage.html ``` -![ワークフローアップロード成果物ワークフロー実行の画像](/assets/images/help/repository/upload-build-test-artifact.png) - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### カスタムアーティファクトの保持期間を設定する @@ -237,7 +235,12 @@ versions: エコー 結果は $value ``` +The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![ジョブ間でデータを受け渡して数学を実行するワークフロー](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% else %} ![ジョブ間でデータを受け渡して数学を実行するワークフロー](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +{% endif %} {% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 14c67673f8..e78ba9eec5 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 @@ -87,7 +87,7 @@ versions: - Windows Server 2016 64-bit - Windows Server 2019 64-bit -#### MacOS +#### macOS - macOS 10.13 (High Sierra)以降 diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md index 7b7d410a0c..3117a1d378 100644 --- a/translations/ja-JP/content/actions/index.md +++ b/translations/ja-JP/content/actions/index.md @@ -41,6 +41,7 @@ changelog: title: Self-Hosted Runner Group Access Changes date: '2020-10-16' href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ +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/ @@ -69,18 +70,18 @@ versions:

Code examples

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

Sorry, there is no result for

+

Sorry, there is no result for

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

Learn how to add a code example {% octicon "arrow-right" %}
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 942a486a05..4c3f682206 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 @@ -204,13 +204,18 @@ YAML 構文を使用してワークフローファイルを作成する方法を ### ジョブのアクティビティを表示する -ジョブの実行が開始されると、{% data variables.product.prodname_dotcom %} で各ステップのアクティビティを表示できます。 +Once your job has started running, you can {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}. {% data reusables.repositories.navigate-to-repo %} 1. リポジトリ名の下で**Actions（アクション）**をクリックしてください。 ![リポジトリに移動](/assets/images/help/images/learn-github-actions-repository.png) 1. 左サイドバーで、表示するワークフローをクリックします。 ![ワークフロー結果のスクリーンショット](/assets/images/help/images/learn-github-actions-workflow.png) 1. [Workflow runs] で、表示する実行の名前をクリックします。 ![ワークフロー実行のスクリーンショット](/assets/images/help/images/learn-github-actions-run.png) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Select job](/assets/images/help/images/overview-actions-result-navigate.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. View the results of each step. ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. ジョブ名をクリックして、各ステップの結果を確認します。 ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result-updated.png) {% else %} 1. ジョブ名をクリックして、各ステップの結果を確認します。 ![ワークフロー実行の詳細のスクリーンショット](/assets/images/help/images/overview-actions-result.png) 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 b20d30b1ab..5b9152ac2a 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 @@ -54,6 +54,8 @@ versions: **警告:** コミット SHA の短いバージョンは安全ではないため、アクションの Git リファレンスの指定には使用しないでください。 リポジトリネットワークの仕組みにより、どのユーザもリポジトリをフォークし、短い SHA と衝突するよう細工されたコミットをプッシュできます。 これにより、その SHA の後続のクローンがあいまいなコミットになるため失敗します。 その結果、短縮された SHA を使用するワークフローはすぐに失敗します。 {% endwarning %} + + * **アクションのソースコードを監査する** アクションが想定どおりにリポジトリとシークレットのコンテンツを処理していることを確認します。 たとえば、シークレットが意図しないホストに送信されていないか、または誤ってログに記録されていないかを確認します。 @@ -92,10 +94,14 @@ versions: そのため、[{% data variables.product.product_name %} のパブリックリポジトリにセルフホストランナーを使用することはほとんどありません](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)。これは、ユーザがリポジトリに対してプルリクエストを開き、環境を危険にさらす可能性があるためです。 同様に、プライベートリポジトリでセルフホストランナーを使用する場合は注意してください。リポジトリをフォークして PR を開くことができるユーザ（一般にリポジトリへの読み取りアクセス権を持つユーザ）は、シークレットへのアクセスと、リポジトリへの書き込みアクセス許可を付与する、より特権的な `GITHUB_TOKEN` を取得して、セルフホストのランナー環境を危険にさらすことができるためです。 +When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。 + 次のように、セルフホストランナーマシンの環境も考慮する必要があります。 - セルフホストランナーとして設定されたマシンにはどのような機密情報が存在するか。 たとえば、SSH 秘密鍵、API アクセストークンなどです。 - マシンが機密性の高いサービスにネットワークアクセス可能か。 たとえば、Azure または AWS メタデータサービスなどです。 この環境での機密情報量は最小限に抑える必要があります。ワークフローを呼び出すことができるすべてのユーザがこの環境にアクセスできることを常に意識しておいてください。 +Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. + ### Auditing {% data variables.product.prodname_actions %} events 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. @@ -130,5 +136,3 @@ The following tables describe the {% data variables.product.prodname_actions %} | `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. | - - diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md index 1dd6be4f07..641cd4b668 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -17,8 +17,13 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} -{% data reusables.repositories.view-run %} -1. ワークフローの右上隅にある [**ワークフローのキャンセル**] をクリックします。 ![[Cancel check suite] ボタン](/assets/images/help/repository/cancel-check-suite.png) +1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel. ![ワークフローの実行の名前](/assets/images/help/repository/in-progress-run.png) +1. ワークフローの右上隅にある [**ワークフローのキャンセル**] をクリックします。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![[Cancel check suite] ボタン](/assets/images/help/repository/cancel-check-suite-updated.png) +{% else %} + ![[Cancel check suite] ボタン](/assets/images/help/repository/cancel-check-suite.png) +{% endif %} ### ワークフロー実行をキャンセルするために {% data variables.product.prodname_dotcom %} が実行するステップ diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 59f6eb8e7d..7b5bb2e735 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -19,4 +19,9 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. [**Artifacts**] の下で、ダウンロードするアーティファクトをクリックします。 ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down.png) +1. [**Artifacts**] の下で、ダウンロードするアーティファクトをクリックします。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down-updated.png) + {% else %} + ![成果物のダウンロードのドロップダウンメニュー](/assets/images/help/repository/artifact-drop-down.png) + {% endif %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/index.md b/translations/ja-JP/content/actions/managing-workflow-runs/index.md index cac7f39a3f..988cc40d9d 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/index.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/index.md @@ -18,6 +18,7 @@ versions: {% data variables.product.prodname_actions %} の支払いを管理する {% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% link_in_list /using-the-visualization-graph %}{% endif %} {% link_in_list /viewing-workflow-run-history %} {% link_in_list /using-workflow-run-logs %} {% link_in_list /manually-running-a-workflow %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md index c7f511cd52..c1f12a08d0 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -16,4 +16,4 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. ワークフローの右上隅にある [**Re-run jobs**] ドロップダウンメニューを使用して、[**Re-run all jobs**] を選択します。 ![[Re-run checks] ドロップダウンメニュー](/assets/images/help/repository/rerun-checks-drop-down.png) +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 955cdc6b49..6b5f85b900 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -26,7 +26,13 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. [**Artifacts**] で、削除するアーティファクトの横にある {% octicon "trashcan" aria-label="The trashcan icon" %} をクリックします。 ![成果物の削除のドロップダウンメニュー](/assets/images/help/repository/actions-delete-artifact.png) +1. Under **Artifacts**, click +{% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![成果物の削除のドロップダウンメニュー](/assets/images/help/repository/actions-delete-artifact-updated.png) + {% else %} + ![成果物の削除のドロップダウンメニュー](/assets/images/help/repository/actions-delete-artifact.png) + {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### アーティファクトの保持期間を設定する diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md new file mode 100644 index 0000000000..c3cefc5f38 --- /dev/null +++ b/translations/ja-JP/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -0,0 +1,21 @@ +--- +title: Using the visualization graph +intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data variables.product.prodname_actions %} の支払いを管理する +{% data reusables.actions.visualization-beta %} +{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} + +1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies. ![Workflow graph](/assets/images/help/images/workflow-graph.png) + +2. Click on a job to view the job log. ![Workflow graph](/assets/images/help/images/workflow-graph-job.png) diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 4a1293271a..5f94cedce9 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -44,7 +44,12 @@ versions: {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. ログ出力の右上隅にある [**Search logs**] 検索ボックスに、検索語句を入力します。 ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box-updated.png) +1. ログ出力の右上隅にある [**Search logs**] 検索ボックスに、検索語句を入力します。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box-updated-2.png) +{% else %} + ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box-updated.png) +{% endif %} {% else %} 1. 検索に含めたい各ステップを展開するには、そのステップをクリックします。![ステップの名前](/assets/images/help/repository/failed-check-step.png) 1. ログ出力の右上隅にある [**Search logs**] 検索ボックスに、検索語句を入力します。 ![ログを検索するための検索ボックス](/assets/images/help/repository/search-log-box.png) @@ -61,8 +66,12 @@ versions: {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 1. 右上隅にある -{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、[**Download log archive**] を選択します。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![[Download logs] ドロップダウンメニュー](/assets/images/help/repository/download-logs-drop-down-updated-2.png) + {% else %} ![[Download logs] ドロップダウンメニュー](/assets/images/help/repository/download-logs-drop-down-updated.png) + {% endif %} {% else %} 1. 右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、[**Download log archive**] を選択します。 @@ -78,8 +87,20 @@ versions: {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. 右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。 ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) -2. ログファイルを削除するには、**Delete all logs（すべてのログを削除）**ボタンをクリックして、確認の要求を見てください 。 ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) ログを削除すると、**Delete all logs（すべてのログを削除）**ボタンはなくなり、ワークフローの実行中にログファイルが残っていないことを示します。 +1. 右上隅にある +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) + {% else %} + ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) + {% endif %} +2. ログファイルを削除するには、**Delete all logs（すべてのログを削除）**ボタンをクリックして、確認の要求を見てください 。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png) + {% else %} + ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) + {% endif %} +After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. {% else %} 1. 右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。 ![水平ケバブアイコン](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png) 2. ログファイルを削除するには、**Delete all logs（すべてのログを削除）**ボタンをクリックして、確認の要求を見てください 。 ![Delete all logs](/assets/images/help/repository/delete-all-logs.png)ログが削除されると、[**Delete all logs**] ボタンが削除され、ワークフローの実行にログファイルが残っていないことを示します。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md index cdedcc2c06..6b30dc01b0 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -15,7 +15,7 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. ジョブの概要の下で、ジョブの実行時間を表示できます。 請求対象となるジョブの実行時間を表示するには、[**Run and billable time details**] をクリックします。 ![実行および支払請求可能な時間の詳細リンク](/assets/images/help/repository/view-run-billable-time.png) +1. ジョブの概要の下で、ジョブの実行時間を表示できます。 To view details about the billable job execution time, click the time under **Billable time**. ![実行および支払請求可能な時間の詳細リンク](/assets/images/help/repository/view-run-billable-time.png) {% note %} diff --git a/translations/ja-JP/content/actions/quickstart.md b/translations/ja-JP/content/actions/quickstart.md index a384b01cfd..18dfa49480 100644 --- a/translations/ja-JP/content/actions/quickstart.md +++ b/translations/ja-JP/content/actions/quickstart.md @@ -59,7 +59,11 @@ versions: {% 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 コードベースジョブ](/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 %} ### その他のスターターワークフロー @@ -101,7 +105,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o # When the event is triggered, GitHub Actions will run the jobs indicated jobs: say_hello: - # Uses a ubuntu-lates runner to complete the requested steps + # Uses a ubuntu-latest runner to complete the requested steps runs-on: ubuntu-latest steps: - run: | diff --git a/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md index a357a3a933..f7f02d16d9 100644 --- a/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,7 +75,7 @@ env: - `a-Z` または `_` で始まる。 - `a-Z` 、`0-9`、 `-`、または`_`が続く。 -#### **`github` コンテキスト** +#### `github` コンテキスト `github` コンテキストは、ワークフローの実行および、その実行をトリガーしたイベントの情報を含みます。 ほとんどの `github` コンテキストデータは、環境変数で読み取ることができます。 環境変数に関する詳しい情報については、「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」を参照してください。 @@ -103,7 +103,7 @@ env: | `github.workflow` | `string` | ワークフローの名前。 ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | | `github.workspace` | `string` | [`checkout`](https://github.com/actions/checkout)アクションを使う際の、ステップにとってのデフォルトのワーキングディレクトリであり、リポジトリのデフォルトの場所です。 | -#### **`env`コンテキスト** +#### `env`コンテキスト `env`コンテキストには、ワークフロー、ジョブ、ステップで設定された環境変数が含まれます。 ワークフローでの環境変数の設定に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)」を参照してください。 @@ -117,7 +117,7 @@ env: | `env.` | `string` | 特定の環境変数の値。 | -#### **`job` コンテキスト** +#### `job` コンテキスト `job` コンテキストは、現在実行中のジョブに関する情報を含みます。 @@ -133,7 +133,7 @@ env: | `job.services..ports` | `オブジェクト` | サービスコンテナの公開ポート。 | | `job.status` | `string` | ジョブの現在の状態。 `success`、`failure`、`cancelled` のいずれかの値をとります。 | -#### **`steps` コンテキスト** +#### `steps` コンテキスト `steps` コンテキストは、すでに実行中のジョブ内のステップに関する情報を含みます。 @@ -145,7 +145,7 @@ env: | `steps..outcome` | `string` | [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error)が適用される前の完了したステップの結果。 `success`、`failure`、`cancelled`、`skipped`のいずれかの値をとります。 `continue-on-error`のステップが失敗すると、`outcome`は`failure`になりますが、最終的な`conclusion`は`success`になります。 | | `steps..outputs.` | `string` | 特定の出力の値。 | -#### **`runner`コンテキスト** +#### `runner`コンテキスト `runner`コンテキストには、現在のジョブを実行しているランナーに関する情報が含まれています。 @@ -155,7 +155,7 @@ env: | `runner.temp` | `string` | ランナー用のテンポラリディレクトリのパス。 このディレクトリは、セルフホストランナーの場合であっても、各ジョブの開始時点では空であることが保証されています。 | | `runner.tool_cache` | `string` | {% data variables.product.prodname_dotcom %}ホストランナーにプレインストールされているいくつかのツールを含むディレクトリのパス。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 | -#### **`needs`コンテキスト** +#### `needs`コンテキスト `needs`コンテキストは、現在のジョブの依存関係として定義されたすべてのジョブからの出力を含みます。 ジョブの依存関係の定義に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)」を参照してください。 diff --git a/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md index 76307822e2..02d4025f52 100644 --- a/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/ja-JP/content/actions/reference/events-that-trigger-workflows.md @@ -137,9 +137,9 @@ jobs: #### `repository_dispatch` -| webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------- | ---------- | -------------------------- | --------------- | -| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | `GITHUB_REF` ブランチ上の直近のコミット | ディスパッチを受信したブランチ | +| webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------------------- | ---------- | ----------------- | ------------ | +| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | デフォルトブランチの直近のコミット | デフォルトブランチ | {% data reusables.github-actions.branch-requirement %} @@ -699,6 +699,8 @@ on: {% data reusables.webhooks.workflow_run_desc %} +{% data reusables.github-actions.branch-requirement %} + | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------- | ---------- | ----------------- | ------------ | | [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - n/a | デフォルトブランチの直近のコミット | デフォルトブランチ | diff --git a/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md index 4f1bccce82..cf44d43c68 100644 --- a/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/reference/specifications-for-github-hosted-runners.md @@ -63,8 +63,8 @@ Windowsの仮想マシンは、ユーザアカウント制御（UAC）が無効 * [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md) * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md) -* [MacOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) -* [MacOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) +* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) {% data reusables.github-actions.ubuntu-runner-preview %} {% data reusables.github-actions.macos-runner-preview %} diff --git a/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md index cfee0dd76f..1617fb429b 100644 --- a/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/reference/workflow-syntax-for-github-actions.md @@ -21,17 +21,17 @@ versions: ワークフローファイルは、リポジトリの`.github/workflows`ディレクトリに保存する必要があります。 -### **`name`** +### `name` ワークフローの名前。 {% data variables.product.prodname_dotcom %}では、リポジトリのアクションページにワークフローの名前が表示されます。 `name`を省略すると、{% data variables.product.prodname_dotcom %}はリポジトリのルートに対するワークフローファイルの相対パスをその値に設定します。 -### **`on`** +### `on` **必須** ワークフローをトリガーする{% data variables.product.prodname_dotcom %}イベントの名前。 指定できるのは、1つのイベント`string`、複数イベントの`array`、イベント`types`の`array`です。あるいは、ワークフローをスケジュールする、またはワークフロー実行を特定のファイルやタグ、ブランチ変更に限定するイベント設定`map`も指定できます。 使用可能なイベントの一覧は、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows)」を参照してください。 {% data reusables.github-actions.actions-on-examples %} -### **`on..types`** +### `on..types` ワークフローの実行をトリガーする特定のアクティビティ。 ほとんどの GitHub イベントは、2 つ以上のアクティビティタイプからトリガーされます。 たとえば、releaseリソースに対するイベントは、release が `published`、`unpublished`、`created`、`edited`、`deleted`、または `prereleased` の場合にトリガーされます。 `types`キーワードを使用すると、ワークフローを実行させるアクティブの範囲を狭くすることができます。 webhook イベントをトリガーするアクティビティタイプが1つだけの場合、`types`キーワードは不要です。 @@ -45,7 +45,7 @@ on: types: [published, created, edited] ``` -### **`on..`** +### `on..` `push`および`pull_request`イベントを使用する場合、特定のブランチまたはタグで実行するワークフローを設定できます。 `pull_request`では、ベース上のブランチ及びタグだけが評価されます。 `tags`もしくは`branches`だけを定義すると、定義されていないGit refに影響するイベントに対して、ワークフローが実行されません。 @@ -112,7 +112,7 @@ on: - '!releases/**-alpha' ``` -### **`on..paths`** +### `on..paths` `push` および `pull_request` イベントを使用する場合、1 つ以上の変更されたファイルが `paths-ignore` にマッチしない場合や、1 つ以上の変更されたファイルが、設定された `paths` にマッチする場合にワークフローを実行するように設定できます。 タグへのプッシュに対して、パスのフィルタは評価されません。 @@ -179,13 +179,13 @@ on: 詳しい情報については「[プルリクエスト中のブランチの比較について](/articles/about-comparing-branches-in-pull-requests)」を参照してください。 -### **`on.schedule`** +### `on.schedule` {% data reusables.repositories.actions-scheduled-workflow-example %} cron構文に関する詳しい情報については、「[ワークフローをトリガーするイベント](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)」を参照してください。 -### **`env`** +### `env` ワークフロー中のすべてのジョブやステップから利用できる環境変数の`map`です。 1つのジョブあるいはステップからだけ利用できる環境変数を設定することもできます。 詳しい情報については「[`jobs..env`](#jobsjob_idenv)」及び「[`jobs..steps.env`](#jobsjob_idstepsenv)を参照してください。 @@ -198,13 +198,13 @@ env: SERVER: production ``` -### **`defaults`** +### `defaults` デフォルト設定の`map`で、ワークフロー中のすべてのジョブに適用されます。 1つのジョブだけで利用できるデフォルト設定を設定することもできます。 詳しい情報については[`jobs..defaults`](#jobsjob_iddefaults)を参照してください。 {% data reusables.github-actions.defaults-override %} -### **`defaults.run`** +### `defaults.run` ワークフロー中のすべての[`run`](#jobsjob_idstepsrun)ステップに対するデフォルトの`shell`及び`working-directory`オプションを提供することができます。 1つのジョブだけで利用できる`run`のデフォルト設定を設定することもできます。 詳しい情報については[`jobs..defaults.run`](#jobsjob_iddefaultsrun)を参照してください。 このキーワード中では、コンテキストや式を使うことはできません。 @@ -219,7 +219,7 @@ defaults: working-directory: scripts ``` -### **`jobs`** +### `jobs` 1つのワークフロー実行は、1つ以上のジョブからなります。 デフォルトでは、ジョブは並行して実行されます。 ジョブを逐次的に実行するには、`jobs..needs`キーワードを使用して他のジョブに対する依存関係を定義します。 @@ -229,7 +229,7 @@ defaults: ワークフローの実行中で動作しているジョブのユニークな識別子が必要な場合は、{% data variables.product.prodname_dotcom %} APIが利用できます。 詳しい情報については、「[ワークフロージョブ](/rest/reference/actions#workflow-jobs)」を参照してください。 -### **`jobs.`** +### `jobs.` 各ジョブには、対応するIDがあります。 `job_id`キーは文字列型で、その値はジョブの設定データのマップとなるものです。 ``は、`jobs`オブジェクトごとに一意の文字列に置き換える必要があります。 ``は、英字または`_`で始める必要があり、英数字と`-`、`_`しか使用できません。 @@ -243,15 +243,15 @@ jobs: name: My second job ``` -### **`jobs..name`** +### `jobs..name` {% data variables.product.prodname_dotcom %}に表示されるジョブの名前。 -### **`jobs..needs`** +### `jobs..needs` -このジョブの実行前に正常に完了する必要があるジョブを示します。 文字列型または文字列の配列です。 1つのジョブが失敗した場合、失敗したジョブを続行するような条件文を使用していない限り、そのジョブを必要としている他のジョブはすべてスキップされます。 +このジョブの実行前に正常に完了する必要があるジョブを示します。 文字列型または文字列の配列です。 If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. -#### サンプル +#### Example requiring dependent jobs to be successful ```yaml jobs: @@ -270,7 +270,21 @@ jobs: 2. `job2` 3. `job3` -### **`jobs..runs-on`** +#### Example not requiring dependent jobs to be successful + +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + if: always() + 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)." + +### `jobs..runs-on` **必須** ジョブを実行するマシンの種類。 マシンは{% data variables.product.prodname_dotcom %}ホストランナーあるいはセルフホストランナーのいずれかです。 @@ -286,10 +300,10 @@ jobs: {% data reusables.github-actions.ubuntu-runner-preview %} -##### **サンプル** +##### サンプル ```yaml -runs-on: ubuntu-latest +ランオン:Ubuntu-最新 ``` 詳しい情報については「[{% data variables.product.prodname_dotcom %}ホストランナーの仮想環境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」を参照してください。 @@ -298,7 +312,7 @@ runs-on: ubuntu-latest {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -##### **サンプル** +##### サンプル ```yaml runs-on: [self-hosted, linux] @@ -306,7 +320,7 @@ runs-on: [self-hosted, linux] 詳しい情報については「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)」及び「[ワークフロー内でのセルフホストランナーの利用](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)」を参照してください。 -### **`jobs..outputs`** +### `jobs..outputs` ジョブからの出力の`map`です。 ジョブの出力は、そのジョブに依存しているすべての下流のジョブから利用できます。 ジョブの依存関係の定義に関する詳しい情報については[`jobs..needs`](#jobsjob_idneeds)を参照してください。 @@ -314,7 +328,7 @@ runs-on: [self-hosted, linux] 依存するジョブでジョブの出力を使いたい場合には、`needs`コンテキストが利用できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)」を参照してください。 -#### **サンプル** +#### サンプル {% raw %} ```yaml @@ -338,13 +352,13 @@ jobs: ``` {% endraw %} -### **`jobs..env`** +### `jobs..env` ジョブ中のすべてのステップから利用できる環境変数の`map`です。 ワークフロー全体あるいは個別のステップのための環境変数を設定することもできます。 詳しい情報については「[`env`](#env)」及び「[`jobs..steps.env`](#jobsjob_idstepsenv)」を参照してください。 {% data reusables.repositories.actions-env-var-note %} -#### **サンプル** +#### サンプル ```yaml jobs: @@ -353,13 +367,13 @@ jobs: FIRST_NAME: Mona ``` -### **`jobs..defaults`** +### `jobs..defaults` ジョブ中のすべてのステップに適用されるデフォルト設定の`map`。 ワークフロー全体に対してデフォルト設定を設定することもできます。 詳しい情報については[`defaults`](#defaults)を参照してください。 {% data reusables.github-actions.defaults-override %} -### **`jobs..defaults.run`** +### `jobs..defaults.run` ジョブ中のすべての`run`ステップにデフォルトの`shell`と`working-directory`を提供します。 このセクションではコンテキストと式は許されていません。 @@ -379,13 +393,13 @@ jobs: working-directory: scripts ``` -### **`jobs..if`** +### `jobs..if` 条件文の`if`を使って、条件が満たされなければジョブを実行しないようにできます。 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。 {% data reusables.github-actions.expression-syntax-if %} 詳しい情報については「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 -### **`jobs..steps`** +### `jobs..steps` 1つのジョブには、`steps` (ステップ) と呼ばれる一連のタスクがあります。 ステップでは、コマンドを実行する、設定タスクを実行する、あるいはリポジトリやパブリックリポジトリ、Dockerレジストリで公開されたアクションを実行することができます。 すべてのステップでアクションを実行するとは限りませんが、すべてのアクションはステップとして実行されます。 各ステップは、ランナー環境のそれ自体のプロセスで実行され、ワークスペースとファイルシステムにアクセスします。 ステップはそれ自体のプロセスで実行されるため、環境変数を変更しても、ステップ間では反映されません。 {% data variables.product.prodname_dotcom %}には、ジョブを設定して完了するステップが組み込まれています。 @@ -415,17 +429,17 @@ jobs: ``` {% endraw %} -#### **`jobs..steps.id`** +### `jobs..steps.id` ステップの一意の識別子。 `id`を使って、コンテキストのステップを参照することができます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 -#### **`jobs..steps.if`** +### `jobs..steps.if` 条件文の`if`を使って、条件が満たされなければステップを実行しないようにできます。 条件文を作成するには、サポートされている任意のコンテキストや式が使えます。 {% data reusables.github-actions.expression-syntax-if %} 詳しい情報については「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 -##### コンテキストの使用例 +#### コンテキストの使用例 このステップは、イベントの種類が`pull_request`でイベントアクションが`unassigned`の場合にのみ実行されます。 @@ -436,7 +450,7 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -##### ステータスチェック関数の使用例 +#### ステータスチェック関数の使用例 `my backup step`は、ジョブの前のステップが失敗した場合にのみ実行されます。 詳しい情報については、「[{% data variables.product.prodname_actions %} のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)」を参照してください。 @@ -449,11 +463,11 @@ steps: uses: actions/heroku@1.0.0 ``` -#### **`jobs..steps.name`** +### `jobs..steps.name` {% data variables.product.prodname_dotcom %}で表示されるステップの名前。 -#### **`jobs..steps.uses`** +### `jobs..steps.uses` ジョブでステップの一部として実行されるアクションを選択します。 アクションとは、再利用可能なコードの単位です。 ワークフロー、パブリックリポジトリ、または[公開されているDockerコンテナイメージ](https://hub.docker.com/)と同じリポジトリで定義されているアクションを使用できます。 @@ -466,7 +480,7 @@ Git ref、SHA、またはDockerタグ番号を指定して、使用している アクションは、JavaScriptのファイルもしくはDockerコンテナです。 使用するアクションがDockerコンテナの場合は、Linux環境で実行する必要があります。 詳細については[`runs-on`](#jobsjob_idruns-on)を参照してください。 -##### バージョンされたアクションを使用する例 +#### バージョンされたアクションを使用する例 ```yaml steps: @@ -480,7 +494,7 @@ steps: - uses: actions/setup-node@main ``` -##### パブリックアクションを使用する例 +#### パブリックアクションを使用する例 `{owner}/{repo}@{ref}` @@ -498,7 +512,7 @@ jobs: uses: actions/aws@v2.0.1 ``` -##### サブディレクトリのパブリックアクションを使用する例 +#### サブディレクトリのパブリックアクションを使用する例 `{owner}/{repo}/{path}@{ref}` @@ -512,7 +526,7 @@ jobs: uses: actions/aws/ec2@main ``` -##### ワークフローと同じリポジトリにあるアクションを使用する例 +#### ワークフローと同じリポジトリにあるアクションを使用する例 `./path/to/dir` @@ -528,7 +542,7 @@ jobs: uses: ./.github/actions/my-action ``` -##### Docker Hubアクションを使用する例 +#### Docker Hubアクションを使用する例 `docker://{image}:{tag}` @@ -542,7 +556,7 @@ jobs: 私の最初のステップ: docker://alpine:3.8 ``` -##### Dockerパブリックレジストリアクションを使用する例 +#### Dockerパブリックレジストリアクションを使用する例 `docker://{host}/{image}:{tag}` @@ -556,7 +570,7 @@ jobs: uses: docker://gcr.io/cloud-builders/gradle ``` -#### **`jobs..steps.run`** +### `jobs..steps.run` オペレーティングシステムのシェルを使用してコマンドラインプログラムを実行します。 `name`を指定しない場合、ステップ名はデフォルトで`run`コマンドで指定された文字列になります。 @@ -588,7 +602,7 @@ jobs: working-directory: ./temp ``` -##### 特定のシェルを使用する +#### 特定のシェルを使用する `shell`キーワードを使用して、ランナーのオペレーティングシステムのデフォルトシェルを上書きできます。 組み込みの`shell`キーワードを使用するか、カスタムセットのシェルオプションを定義することができます。 @@ -601,7 +615,7 @@ jobs: | Windows | `cmd` | {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.cmd`を追加し、`{0}`を置き換えます。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | | Windows | `powershell` | これはWindowsで使われるデフォルトのシェルです。 デスクトップPowerShellです。 {% data variables.product.prodname_dotcom %}はスクリプト名に拡張子`.ps1`を追加します。 | `powershell -command ". '{0}'"`. | -##### bashを使用してスクリプトを実行する例 +#### bashを使用してスクリプトを実行する例 ```yaml steps: @@ -610,7 +624,7 @@ steps: shell: bash ``` -##### Windowsの`cmd`を使用してスクリプトを実行する例 +#### Windowsの`cmd`を使用してスクリプトを実行する例 ```yaml steps: @@ -619,7 +633,7 @@ steps: shell: cmd ``` -##### PowerShell Coreを使用してスクリプトを実行する例 +#### PowerShell Coreを使用してスクリプトを実行する例 ```yaml steps: @@ -628,7 +642,7 @@ steps: shell: pwsh ``` -##### Python scriptを実行する例 +#### Python scriptを実行する例 ```yaml steps: @@ -639,11 +653,11 @@ steps: shell: python ``` -##### カスタムシェル +#### カスタムシェル `command […options] {0} [..more_options]`を使用すると、テンプレート文字列に`shell`値を設定できます。 {% data variables.product.prodname_dotcom %}は、空白区切りで最初の文字列をコマンドとして解釈し、`{0}`にある一時的なスクリプトのファイル名を挿入します。 -##### 終了コードとエラーアクションの環境設定 +#### 終了コードとエラーアクションの環境設定 組み込みのshellキーワードについては、{% data variables.product.prodname_dotcom %}がホストする実行環境で以下のデフォルトが提供されます。 シェルスクリプトを実行する際には、以下のガイドラインを使ってください。 @@ -661,11 +675,11 @@ steps: - 各エラーコードをチェックしてそれぞれに対応するスクリプトを書く以外、フェイルファースト動作を完全にオプトインする方法はないようです。 デフォルトでその動作を指定することはできないため、この動作はスクリプトに記述する必要があります。 - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. この動作は、これ以前の`sh`および`pwsh`のデフォルト動作と内部的に一貫しており、`cmd.exe`のデフォルトなので、この動作には影響しません。 -#### **`jobs..steps.with`** +### `jobs..steps.with` アクションによって定義される入力パラメータの`map`。 各入力パラメータはキー/値ペアです。 入力パラメータは環境変数として設定されます。 変数の前には`INPUT_`が付けられ、大文字に変換されます。 -##### サンプル +#### サンプル `hello_world`アクションで定義される3つの入力パラメータ (`first_name`、`middle_name`、`last_name`) を定義します。 `hello-world`アクションからは、これらの入力変数は`INPUT_FIRST_NAME`、`INPUT_MIDDLE_NAME`、`INPUT_LAST_NAME`という環境変数としてアクセスできます。 @@ -681,11 +695,11 @@ jobs: last_name: Octocat ``` -#### **`jobs..steps.with.args`** +### `jobs..steps.with.args` Dockerコンテナへの入力を定義する`文字列`。 {% data variables.product.prodname_dotcom %}は、コンテナの起動時に`args`をコンテナの`ENTRYPOINT`に渡します。 このパラメータは、`文字列の配列`をサポートしません。 -##### サンプル +#### サンプル {% raw %} ```yaml @@ -704,11 +718,11 @@ steps: 1. `args`を指定せずにアクションを利用できるよう、デフォルトを使ってください。 1. アクションが`--help`フラグやそれに類するものを備えている場合は、アクションを自己ドキュメント化するためのデフォルトとして利用してください。 -#### **`jobs..steps.with.entrypoint`** +### `jobs..steps.with.entrypoint` `Dockerfile`中のDockerの`ENTRYPOINT`をオーバーライドします。あるいは、もしそれが指定されていなかった場合に設定します。 shellやexec形式を持つDockerの`ENTRYPOINT`命令とは異なり、`entrypoint`キーワードは実行する実行可能ファイルを定義する単一の文字列だけを受け付けます。 -##### サンプル +#### サンプル ```yaml steps: @@ -720,7 +734,7 @@ steps: The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. -#### **`jobs..steps.env`** +### `jobs..steps.env` ランナー環境でステップが使う環境変数を設定します。 ワークフロー全体あるいはジョブのための環境変数を設定することもできます。 詳しい情報については「[`env`](#env)」及び「[`jobs..env`](#jobsjob_idenv)」を参照してください。 @@ -728,7 +742,7 @@ The `entrypoint` keyword is meant to be used with Docker container actions, but パブリックなアクションは、READMEファイル中で期待する環境変数を指定できます。 環境変数に秘密情報を設定しようとしている場合、秘密情報は`secrets`コンテキストを使って設定しなければなりません。 詳しい情報については「[環境変数の利用](/actions/automating-your-workflow-with-github-actions/using-environment-variables)」及び「[{% data variables.product.prodname_actions %}のコンテキストと式構文](/actions/reference/context-and-expression-syntax-for-github-actions)」を参照してください。 -##### サンプル +#### サンプル {% raw %} ```yaml @@ -741,23 +755,23 @@ steps: ``` {% endraw %} -#### **`jobs..steps.continue-on-error`** +### `jobs..steps.continue-on-error` ステップが失敗してもジョブが失敗にならないようにします。 `true`に設定すれば、このステップが失敗した場合にジョブが次へ進めるようになります。 -#### **`jobs..steps.timeout-minutes`** +### `jobs..steps.timeout-minutes` プロセスがkillされるまでにステップが実行できる最大の分数。 -### **`jobs..timeout-minutes`** +### `jobs..timeout-minutes` {% data variables.product.prodname_dotcom %}で自動的にキャンセルされるまでジョブを実行する最長時間 (分)。 デフォルト: 360 -### **`jobs..strategy`** +### `jobs..strategy` strategy (戦略) によって、ジョブのビルドマトリクスが作成されます。 各ジョブを実行する環境のバリエーションを定義できます。 -#### **`jobs..strategy.matrix`** +### `jobs..strategy.matrix` 様々なジョブの設定のマトリックスを定義できます。 マトリックスによって、単一のジョブの定義内の変数の置き換えを行い、複数のジョブを作成できるようになります。 たとえば、マトリックスを使って複数のサポートされているバージョンのプログラミング言語、オペレーティングシステム、ツールに対するジョブを作成できます。 マトリックスは、ジョブの設定を再利用し、設定した各マトリクスに対してジョブを作成します。 @@ -767,7 +781,7 @@ strategy (戦略) によって、ジョブのビルドマトリクスが作成 `matrix`を定義する順序は意味を持ちます。 最初に定義したオプションは、ワークフロー中で最初に実行されるジョブになります。 -##### 複数のバージョンの Node.js を使用して実行する例 +#### 複数のバージョンの Node.js を使用して実行する例 設定オプションに配列を指定すると、マトリクスを指定できます。 たとえばランナーがNode.jsのバージョン6、8、10,をサポートしている場合、これらのバージョンの配列を`matrix`で指定できます。 @@ -789,7 +803,7 @@ steps: {% data variables.product.prodname_dotcom %}ホストランナーを使う場合にNode.jsのバージョンを設定する方法としては、`setup-node`アクションをおすすめします。 詳しい情報については[`setup-node`](https://github.com/actions/setup-node)アクションを参照してください。 -##### 複数のオペレーティングシステムで実行する例 +#### 複数のオペレーティングシステムで実行する例 複数のランナーオペレーティングシステムでワークフローを実行するマトリックスを作成できます。 複数のマトリックス設定を指定することもできます。 この例では、6つのジョブのマトリックスを作成します。 @@ -814,7 +828,7 @@ steps: {% data variables.product.prodname_dotcom %}ホストランナーでサポートされている設定オプションについては、「[{% data variables.product.prodname_dotcom %}の仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」を参照してください。 -##### 組み合わせに追加の値が含まれる例 +#### 組み合わせに追加の値が含まれる例 既存のビルドマトリクスジョブに、設定オプションを追加できます。 たとえば、`windows-latest` を使うジョブで`node` のバージョン 4 を実行しているときに、`npm` の特定のバージョンを使いたい場合は、`include` を使って追加のオプションを指定できます。 @@ -834,7 +848,7 @@ strategy: ``` {% endraw %} -##### 新しい組み合わせを含む例 +#### 新しい組み合わせを含む例 `include`を使って新しいジョブを追加し、マトリックスを構築できます。 マッチしなかったincludeの設定があれば、マトリックスに追加されます。 たとえば、`node`のバージョン12を使って複数のオペレーティングシステム上でビルドを行い、追加で実験的なジョブをUbuntu上でnodeバージョン13で行いたいなら、`include`を使ってこの追加のジョブを指定できます。 @@ -852,7 +866,7 @@ strategy: ``` {% endraw %} -##### マトリクスから設定を除外する例 +#### マトリクスから設定を除外する例 `exclude` オプションを使って、ビルドマトリクスに定義されている特定の設定を削除できます。 `exclude` を使うと、ビルドマトリクスにより定義されたジョブが削除されます。 ジョブの数は、指定する配列に含まれるオペレーティングシステム (`os`) の外積から、任意の減算 (`exclude`) で引いたものです。 @@ -882,11 +896,11 @@ You can add custom environment variables for each test combination by using the {% data reusables.github-actions.matrix-variable-example %} -### **`jobs..strategy.fail-fast`** +### `jobs..strategy.fail-fast` `true`に設定すると、いずれかの`matrix`ジョブが失敗した場合に{% data variables.product.prodname_dotcom %}は進行中のジョブをすべてキャンセルします。 デフォルト: `true` -### **`jobs..strategy.max-parallel`** +### `jobs..strategy.max-parallel` `matrix`ジョブ戦略を使用するとき、同時に実行できるジョブの最大数。 デフォルトでは、{% data variables.product.prodname_dotcom %}は{% data variables.product.prodname_dotcom %}がホストしている仮想マシン上で利用できるrunnerに応じてできるかぎりの数のジョブを並列に実行します。 @@ -895,7 +909,7 @@ strategy: max-parallel: 2 ``` -### **`jobs..continue-on-error`** +### `jobs..continue-on-error` ジョブが失敗した時に、ワークフローの実行が失敗にならないようにします。 `true`に設定すれば、ジョブが失敗した時にワークフローの実行が次へ進めるようになります。 @@ -920,7 +934,7 @@ strategy: ``` {% endraw %} -### **`jobs..container`** +### `jobs..container` ジョブの中で、まだコンテナを指定していない手順を実行するコンテナ。 スクリプトアクションとコンテナアクションの両方を使うステップがある場合、コンテナアクションは同じボリュームマウントを使用して、同じネットワーク上にある兄弟コンテナとして実行されます。 @@ -950,16 +964,17 @@ jobs: container: node:10.16-jessie ``` -#### **`jobs..container.image`** +### `jobs..container.image` アクションを実行するコンテナとして使用するDockerイメージ。 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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..container.credentials`** + +### `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -##### サンプル +#### サンプル {% raw %} ```yaml @@ -972,15 +987,15 @@ container: {% endraw %} {% endif %} -#### **`jobs..container.env`** +### `jobs..container.env` コンテナ中の環境変数の`map`を設定します。 -#### **`jobs..container.ports`** +### `jobs..container.ports` コンテナで公開するポートの`array`を設定します。 -#### **`jobs..container.volumes`** +### `jobs..container.volumes` 使用するコンテナにボリュームの`array`を設定します。 volumes (ボリューム) を使用すると、サービス間で、または1つのジョブのステップ間でデータを共有できます。 指定できるのは、名前付きDockerボリューム、匿名Dockerボリューム、またはホスト上のバインドマウントです。 @@ -990,7 +1005,7 @@ container: ``は、ホストマシン上のボリューム名または絶対パス、``はコンテナでの絶対パスです。 -##### サンプル +#### サンプル ```yaml volumes: @@ -999,11 +1014,11 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..container.options`** +### `jobs..container.options` 追加のDockerコンテナリソースのオプション。 オプションの一覧は、「[`docker create`のオプション](https://docs.docker.com/engine/reference/commandline/create/#options)」を参照してください。 -### **`jobs..services`** +### `jobs..services` {% data reusables.github-actions.docker-container-os-support %} @@ -1033,16 +1048,17 @@ services: - 6379/tcp ``` -#### **`jobs..services..image`** +### `jobs..services..image` アクションを実行するサービスコンテナとして使用するDockerイメージ。 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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..services..credentials`** + +### `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -##### サンプル +#### サンプル {% raw %} ```yaml @@ -1061,15 +1077,15 @@ services: {% endraw %} {% endif %} -#### **`jobs..services..env`** +### `jobs..services..env` サービスコンテナ中の環境変数の`map`を設定します。 -#### **`jobs..services..ports`** +### `jobs..services..ports` サービスコンテナで公開するポートの`array`を設定します。 -#### **`jobs..services..volumes`** +### `jobs..services..volumes` 使用するサービスコンテナにボリュームの`array`を設定します。 volumes (ボリューム) を使用すると、サービス間で、または1つのジョブのステップ間でデータを共有できます。 指定できるのは、名前付きDockerボリューム、匿名Dockerボリューム、またはホスト上のバインドマウントです。 @@ -1079,7 +1095,7 @@ services: ``は、ホストマシン上のボリューム名または絶対パス、``はコンテナでの絶対パスです。 -##### サンプル +#### サンプル ```yaml volumes: @@ -1088,7 +1104,7 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..services..options`** +### `jobs..services..options` 追加のDockerコンテナリソースのオプション。 オプションの一覧は、「[`docker create`のオプション](https://docs.docker.com/engine/reference/commandline/create/#options)」を参照してください。 diff --git a/translations/ja-JP/content/admin/configuration/index.md b/translations/ja-JP/content/admin/configuration/index.md index cfd7016798..1540ac7709 100644 --- a/translations/ja-JP/content/admin/configuration/index.md +++ b/translations/ja-JP/content/admin/configuration/index.md @@ -31,9 +31,7 @@ versions: {% link_in_list /enabling-private-mode %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} - {% link_in_list /configuring-applications %} - {% link_in_list /troubleshooting-ssl-errors %} {% link_in_list /configuring-time-synchronization %} {% link_in_list /command-line-utilities %} @@ -54,11 +52,7 @@ versions: {% link_in_list /connecting-github-enterprise-server-to-github-enterprise-cloud %} {% link_in_list /enabling-unified-search-between-github-enterprise-server-and-githubcom %} {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %} - {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %} {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} - - {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} - diff --git a/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md index c78787cf46..46d774cada 100644 --- a/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/ja-JP/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -37,7 +37,7 @@ versions: ``` - On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace *`UUID`* with a UUID you retrieved in the previous step. ```shell - $ ghe-repl-teardown -u UUNID + $ ghe-repl-teardown -u UUID ``` ### 参考リンク 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 f053f0cda7..4ab38b54c0 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 @@ -24,7 +24,7 @@ If your machine has access to both systems at the same time, you can do the sync ### 必要な環境 -* Before using the 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](/github/setting-up-and-managing-organizations-and-teams/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. 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。 ### Example: Using the `actions-sync` tool diff --git a/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 2e5fa0dbed..33e41103dc 100644 --- a/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ja-JP/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -1,6 +1,6 @@ --- title: Setting up the tool cache on self-hosted runners without internet access -intro: 'To use the the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' +intro: 'To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' redirect_from: - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access versions: diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md index d98717ea2f..5a24e43e76 100644 --- a/translations/ja-JP/content/admin/index.md +++ b/translations/ja-JP/content/admin/index.md @@ -28,3 +28,5 @@ versions: {% link_with_intro /packages %} {% link_with_intro /enterprise-support %} + +{% link_with_intro /release-notes %} diff --git a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md index 7a6384cef9..dbb8a037a7 100644 --- a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md +++ b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md @@ -15,7 +15,7 @@ An enterprise account allows you to manage multiple organizations{% if enterpris - 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) +- 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 reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." diff --git a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md index edc4af0c75..4262c20194 100644 --- a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md +++ b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop.md @@ -21,7 +21,7 @@ versions: インストールと認証の詳細については、「[{% data variables.product.prodname_desktop %} の設定](/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop)」を参照してください。 ### パート 2: 新しいリポジトリを作成する -{% data variables.product.prodname_desktop %} に関連付けられたリポジトリがない場合は、「Let's get started!」ビューが表示されます。ここでは、チュートリアルリポジトリの作成と複製、インターネットからの既存のリポジトリの複製、新しいリポジトリの作成、またはハードドライブからの既存のリポジトリの追加を選択できます。 ![The Let's get started! screen](/assets/images/help/desktop/lets-get-started.png) +{% data variables.product.prodname_desktop %} に関連付けられたリポジトリがない場合は、「Let's get started!」ビューが表示されます。ここでは、チュートリアルリポジトリの作成と複製、インターネットからの既存のリポジトリの複製、新しいリポジトリの作成、またはハードドライブからの既存のリポジトリの追加を選択できます。 ![さあ、始めましょう！ screen](/assets/images/help/desktop/lets-get-started.png) #### チュートリアルリポジトリの作成とクローン {% data variables.product.prodname_desktop %} を使用して練習する最初のプロジェクトとして、チュートリアルリポジトリを作成してクローンすることをお勧めします。 @@ -54,7 +54,7 @@ versions: ![GitHub Desktop を探索する](/assets/images/help/desktop/getting-started-guide/explore-github-desktop.png) #### 変更と履歴 -左サイドバーには、[**Changes**] ビューと [**History**] ビューが表示されています。 ![The Changes and History tabs](/assets/images/help/desktop/changes-and-history.png) +左サイドバーには、[**Changes**] ビューと [**History**] ビューが表示されています。 ![[Changes] および [History] タブ](/assets/images/help/desktop/changes-and-history.png) - [**Changes**] ビューは、現在のブランチで変更を行い、まだローカルリポジトリにコミットしていないファイルが表示されます。 ビューの下部には、[Summary] および [Description] テキストボックスのあるボックスと [**Commit to BRANCH**] ボタンがあります。 これが、新しい変更をコミットする場所です。 [**Commit to BRANCH**] ボタンは動的で、変更をコミットするブランチが表示されます。 ![コミットエリア](/assets/images/help/desktop/getting-started-guide/commit-area.png) @@ -81,17 +81,17 @@ versions: 3. {% data variables.product.prodname_desktop %} で、[**Changes**] ビューに移動します。 ファイルのリストに、_README.md_ が表示されているはずです。 _README.md_ ファイルの左側にあるチェックマークは、ファイルに加えた変更がコミットの一部になることを示しています。 今後、複数のファイルに変更を行って、そのうちの一部のファイルのみの変更をコミットしたい場合があるかもしれません。 ファイルの横にあるチェックマークをクリックすると、そのファイルはコミットに含まれません。 ![変更を表示する](/assets/images/help/desktop/getting-started-guide/viewing-changes.png) 4. [**Changes**] リストの下に、コミットメッセージを入力します。 プロフィール画像の右側で、コミットについて簡潔な説明を入力します。 ここでは _README.md_ ファイルを変更するので、「プロジェクトの目的について情報を追加する」などがコミットの要約として良いかもしれません。 概要の下に、コミットの変更詳しい説明を入力できる [Description] テキストフィールドが表示されます。これは、プロジェクトの履歴を振り返ったり、変更理由を確認するときに役立ちます。 今は _README.md_ ファイルの基本的な更新を行っているところなので、この内容は飛ばしてもかまいません。 ![コミットメッセージ](/assets/images/help/desktop/getting-started-guide/commit-message.png) -5. [**Commit to BRANCH NAME**] をクリックします。 コミットボタンには現在のブランチが表示されるので、必要なブランチに確実にコミットできます。 ![Commit to branch](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png) +5. [**Commit to BRANCH NAME**] をクリックします。 コミットボタンには現在のブランチが表示されるので、必要なブランチに確実にコミットできます。 ![ブランチへのコミット](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png) 6. 変更を {% data variables.product.product_name %} のリモートリポジトリにプッシュするには、[**Push origin**] をクリックします。 ![[Push origin]](/assets/images/help/desktop/getting-started-guide/push-to-origin.png) - [**Push origin**] ボタンは、リポジトリを {% data variables.product.product_name %} に公開する際にクリックしたボタンと同じです。 このボタンは、Git ワークフローの現在の場所に基づいてコンテキストが変わります。 ボタンが `Push origin` に変わり、横に `1` と表示されます。これは、{% data variables.product.product_name %} にプッシュされていないコミットが 1 つあることを示しています。 - **Push origin** の「origin」は、`origin` というリモートに変更をプッシュしていることを示しています。この場合は、{% data variables.product.prodname_dotcom_the_website %} 上のプロジェクトのリポジトリです。 {% data variables.product.product_name %} に何か新しいコミットをプッシュするまで、お手元のコンピューターにあるプロジェクトのリポジトリと、{% data variables.product.prodname_dotcom_the_website %} にあるプロジェクトのリポジトリには違いがあります。 これにより、ローカルで作業し、準備ができたときにのみ変更を {% data variables.product.prodname_dotcom_the_website %} にプッシュできます。 -7. [**Changes**] ビューの右側のウィンドウに、次に実行可能なアクションの提案が表示されます。 ブラウザで {% data variables.product.product_name %} のリポジトリを開くには、[**View on {% data variables.product.product_name %}**] をクリックします。 ![Available actions](/assets/images/help/desktop/available-actions.png) +7. [**Changes**] ビューの右側のウィンドウに、次に実行可能なアクションの提案が表示されます。 ブラウザで {% data variables.product.product_name %} のリポジトリを開くには、[**View on {% data variables.product.product_name %}**] をクリックします。 ![利用可能なアクション](/assets/images/help/desktop/available-actions.png) 8. ブラウザで、[**2 commits**] をクリックします。 {% data variables.product.product_name %} にあるリポジトリの、コミットのリストが表示されます。 最初のコミットは、{% data variables.product.prodname_desktop %} で行ったコミットである必要があります。 ![2 つのコミットをクリック](/assets/images/help/desktop/getting-started-guide/click-two-commits.png) ### おわりに これで、リポジトリの作成、{% data variables.product.product_name %} へのリポジトリの公開、コミットの実行、{% data variables.product.product_name %} への変更のプッシュが完了しました。 作成やコラボレーションを行う他のプロジェクトに貢献するときに、これと同じワークフローを使用することができます。 ### 参考リンク -- "[Learning about Git](/github/using-git/learning-about-git)" -- "[Learning about {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" -- "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)" +- 「[Git について学ぶ](/github/using-git/learning-about-git)」 +- 「[{% data variables.product.prodname_dotcom %} について学ぶ](/github/getting-started-with-github/learning-about-github)」 +- 「[{% data variables.product.prodname_dotcom %} を使ってみる](/github/getting-started-with-github)」 diff --git a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md index 1f2433e347..75211b6e43 100644 --- a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md +++ b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop.md @@ -13,95 +13,95 @@ versions: {% data variables.product.prodname_desktop %} を始める前に、Git と {% data variables.product.prodname_dotcom %} の基本を理解しておくと便利です。 詳しい情報については、次の記事を参照してください。 -- "[Learning about Git](/github/using-git/learning-about-git)" -- "[Learning about {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" -- "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)" +- 「[Git について学ぶ](/github/using-git/learning-about-git)」 +- 「[{% data variables.product.prodname_dotcom %} について学ぶ](/github/getting-started-with-github/learning-about-github)」 +- 「[{% data variables.product.prodname_dotcom %} を使ってみる](/github/getting-started-with-github)」 -{% data variables.product.prodname_desktop %} is an open source project. You can see the roadmap, contribute to the project, or open an issue to provide feedback or feature requests. For more information, see the [`desktop/desktop`](https://github.com/desktop/desktop) repository. +{% data variables.product.prodname_desktop %} はオープンソースプロジェクトです。 ロードマップの確認、プロジェクトへの貢献、および Issue をオープンしてフィードバックや機能のリクエストを提供することができます。 詳しい情報については、[`desktop/desktop`](https://github.com/desktop/desktop) を参照してください。 -### Part 1: Installing and authenticating -{% data variables.product.prodname_desktop %} は、サポートされている任意のオペレーティングシステムにインストールできます。 For more information, see "[Supported operating systems](/desktop/getting-started-with-github-desktop/supported-operating-systems)." +### パート 1: インストールと認証 +{% data variables.product.prodname_desktop %} は、サポートされている任意のオペレーティングシステムにインストールできます。 詳しい情報については、「[サポートされているオペレーティングシステム](/desktop/getting-started-with-github-desktop/supported-operating-systems)」を参照してください。 -To install {% data variables.product.prodname_desktop %}, visit the download page for [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). 詳しい情報については「[{% data variables.product.prodname_desktop %}のインストール](/desktop/installing-and-configuring-github-desktop/installing-github-desktop)」を参照してください。 +{% data variables.product.prodname_desktop %} をインストールするには、[{% data variables.product.prodname_desktop %}](https://desktop.github.com/) のダウンロードページにアクセスします。 詳しい情報については「[{% data variables.product.prodname_desktop %}のインストール](/desktop/installing-and-configuring-github-desktop/installing-github-desktop)」を参照してください。 -After you have installed {% data variables.product.prodname_desktop %}, you can authenticate the application with your account on {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}. Authenticating allows you to connect to remote repositories on {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}. +{% data variables.product.prodname_desktop %} をインストールした後、{% data variables.product.prodname_dotcom %} または {% data variables.product.prodname_enterprise %} のアカウントでアプリケーションを認証できます。 認証されると、{% data variables.product.prodname_dotcom %} または {% data variables.product.prodname_enterprise %} のリモートリポジトリに接続できます。 {% mac %} -1. Before you can authenticate to {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}, you will need an account. For more information about creating an account, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)" or contact your {% data variables.product.prodname_enterprise %} site administrator. +1. {% data variables.product.prodname_dotcom %} または {% data variables.product.prodname_enterprise %} に認証する前に、アカウントが必要になります。 アカウントの作成の詳細については、「 [新しい {% data variables.product.prodname_dotcom %} アカウントにサインアップする](/github/getting-started-with-github/signing-up-for-a-new-github-account)」を参照するか、{% data variables.product.prodname_enterprise %} のサイト管理者にお問い合わせください。 -2. In the {% data variables.product.prodname_desktop %} drop-down menu, click **Preferences**. In the preferences window, click **Accounts** and follow the steps to sign in. For more information on authenticating, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." ![GitHubのサインインボタン](/assets/images/help/desktop/mac-sign-in-github.png) +2. [{% data variables.product.prodname_desktop %}] ドロップダウンメニューで、[**Preferences**] をクリックします。 設定ウィンドウで、[**Accounts**] をクリックし、手順に従ってサインインします。 認証の詳細については、「[{% data variables.product.prodname_dotcom %} への認証を行う](/desktop/getting-started-with-github-desktop/authenticating-to-github)」を参照してください。 ![GitHubのサインインボタン](/assets/images/help/desktop/mac-sign-in-github.png) {% endmac %} {% windows %} -1. Before you can authenticate to {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}, you will need an account. For more information about creating an account, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)" or contact your {% data variables.product.prodname_enterprise %} site administrator. +1. {% data variables.product.prodname_dotcom %} または {% data variables.product.prodname_enterprise %} に認証する前に、アカウントが必要になります。 アカウントの作成の詳細については、「 [新しい {% data variables.product.prodname_dotcom %} アカウントにサインアップする](/github/getting-started-with-github/signing-up-for-a-new-github-account)」を参照するか、{% data variables.product.prodname_enterprise %} のサイト管理者にお問い合わせください。 -2. In the File drop-down menu, click **Options**. In the options window, click **Accounts** and follow the steps to sign in. For more information on authenticating, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." ![GitHubのサインインボタン](/assets/images/help/desktop/windows-sign-in-github.png) +2. [File] ドロップダウンメニューで、[**Options**] をクリックします。 オプションウィンドウで、[**Accounts**] をクリックし、手順に従ってサインインします。 認証の詳細については、「[{% data variables.product.prodname_dotcom %} への認証を行う](/desktop/getting-started-with-github-desktop/authenticating-to-github)」を参照してください。 ![GitHubのサインインボタン](/assets/images/help/desktop/windows-sign-in-github.png) {% endwindows %} -### Part 2: Configuring and customizing {% data variables.product.prodname_desktop %} -After you install {% data variables.product.prodname_desktop %}, you can configure and customize the app to best suit your needs. +### パート 2: {% data variables.product.prodname_desktop %} のカスタマイズと設定 +{% data variables.product.prodname_desktop %} のインストール後、ニーズに最も合うようにアプリを設定してカスタマイズできます。 {% mac %} -You can connect or remove accounts on {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}, choose a default text editor or shell, edit your Git configuration, change the appearance of {% data variables.product.prodname_desktop %}, customize system dialogs, and set privacy preferences in the {% data variables.product.prodname_desktop %} Preferences window. 詳しい情報については、「[基本的な設定](/desktop/getting-started-with-github-desktop/configuring-basic-settings)」を参照してください。 +{% data variables.product.prodname_dotcom %} または {% data variables.product.prodname_enterprise %} でのアカウントの接続または削除、デフォルトのテキストエディタやシェルの選択、Git 設定の編集、{% data variables.product.prodname_desktop %} の外観の変更、システムダイアログのカスタマイズ、{% data variables.product.prodname_desktop %} の [Preferences] ウィンドウでのプライバシー設定ができます。 詳しい情報については、「[基本的な設定](/desktop/getting-started-with-github-desktop/configuring-basic-settings)」を参照してください。 - ![The basic settings in the Preference window](/assets/images/help/desktop/mac-appearance-tab-themes.png) + ![[Preference] ウィンドウの基本設定](/assets/images/help/desktop/mac-appearance-tab-themes.png) {% endmac %} {% windows %} -You can connect or remove accounts on {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}, choose a default text editor or shell, edit your Git configuration, change the appearance of {% data variables.product.prodname_desktop %}, customize system dialogs, and set privacy preferences in the {% data variables.product.prodname_desktop %} Options window. 詳しい情報については、「[基本的な設定](/desktop/getting-started-with-github-desktop/configuring-basic-settings)」を参照してください。 +{% data variables.product.prodname_dotcom %} または {% data variables.product.prodname_enterprise %} でのアカウントの接続または削除、デフォルトのテキストエディタやシェルの選択、Git 設定の編集、{% data variables.product.prodname_desktop %} の外観の変更、システムダイアログのカスタマイズ、{% data variables.product.prodname_desktop %} の [Options] ウィンドウでのプライバシー設定ができます。 詳しい情報については、「[基本的な設定](/desktop/getting-started-with-github-desktop/configuring-basic-settings)」を参照してください。 - ![The basic settings in the Options window](/assets/images/help/desktop/windows-appearance-tab-themes.png) + ![[Options] ウィンドウの基本設定](/assets/images/help/desktop/windows-appearance-tab-themes.png) {% endwindows %} -### Part 3: Contributing to projects with {% data variables.product.prodname_desktop %} -After installing, authenticating, and configuring the app, you are ready to start using {% data variables.product.prodname_desktop %}. You can create, add, or clone repositories and use {% data variables.product.prodname_desktop %} to manage contributions to your repositories. +### パート 3: {% data variables.product.prodname_desktop %} でプロジェクトに貢献する +アプリをインストール、認証、設定すると、{% data variables.product.prodname_desktop %} を使用開始できます。 リポジトリを作成、追加、またはクローンし、{% data variables.product.prodname_desktop %} を使用してリポジトリへのコントリビューションを管理できます。 -#### Creating, adding, and cloning repositories -You can create a new repository by selecting the File menu and clicking **New repository...**. For more information, see "[Creating your first repository using {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop)." +#### リポジトリの作成、追加、クローン作成 +[File] メニューを選択し、[**New repository...**] をクリックすると、新しいリポジトリを作成できます。 詳しい情報については、「[{% data variables.product.prodname_desktop %} を使用して最初のリポジトリを作成する](/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop)」を参照してください。 -You can add a repository from your local computer by selecting the File menu and clicking **Add Local Repository...**. For more information, see "[Adding a repository from your local computer to {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop)." +[File] メニューを選択し、[**Add Local Repository...**] をクリックすると、ローカルコンピューターからリポジトリを追加できます。 詳しい情報については、「[ローカルコンピューターから {% data variables.product.prodname_desktop %} にリポジトリを追加する](/desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop)」を参照してください。 -You can clone a repository from {% data variables.product.prodname_dotcom %} by selecting the File menu and clicking **Clone Repository...**. For more information, see "[Cloning and Forking Repositories from {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)." +[File] メニューを選択し、[**Clone Repository...**] をクリックすると、{% data variables.product.prodname_dotcom %} からリポジトリのクローンを作成できます。 詳しい情報については、「[{% data variables.product.prodname_desktop %} からのリポジトリのクローンとフォーク](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)」を参照してください。 {% mac %} - ![The File menu options for creating, adding, and cloning repositories](/assets/images/help/desktop/mac-file-menu.png) + ![リポジトリの作成、追加、およびクローン作成に関する [File] メニューオプション](/assets/images/help/desktop/mac-file-menu.png) {% endmac %} {% windows %} - ![The File menu options for creating, adding, and cloning repositories](/assets/images/help/desktop/windows-file-menu.png) + ![リポジトリの作成、追加、およびクローン作成に関する [File] メニューオプション](/assets/images/help/desktop/windows-file-menu.png) {% endwindows %} #### ブランチでの変更 -You can use {% data variables.product.prodname_desktop %} to create a branch of a project. Branches isolate your development work from other branches in the repository, so that you can safely experiment with changes. 詳しい情報については、「[ブランチを管理する](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches)」を参照してください。 +{% data variables.product.prodname_desktop %} を使用して、プロジェクトのブランチを作成できます。 ブランチは、開発作業をリポジトリ内の他のブランチから分離するため、変更を安全に試すことができます。 詳しい情報については、「[ブランチを管理する](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches)」を参照してください。 - ![The New Branch button](/assets/images/help/desktop/new-branch-button-mac.png) + ![[New Branch] ボタン](/assets/images/help/desktop/new-branch-button-mac.png) -After you make changes to a branch, you can review them in {% data variables.product.prodname_desktop %} and make a commit to keep track of your changes. 詳しい情報については「[プロジェクトに対する変更のコミットとレビュー](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project)」を参照してください。 +ブランチに変更を加えた後、{% data variables.product.prodname_desktop %} で確認し、変更の追跡のためにコミットすることができます。 詳しい情報については「[プロジェクトに対する変更のコミットとレビュー](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project)」を参照してください。 - ![Viewing and making commits](/assets/images/help/desktop/commit-button.png) + ![コミットの表示と作成](/assets/images/help/desktop/commit-button.png) -If you want to access your changes remotely or share them with other people, you can push your commits to {% data variables.product.prodname_dotcom %}. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} への変更をプッシュする](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github)」を参照してください。 +変更にリモートでアクセスしたり、他のユーザと共有したりする場合は、コミットを {% data variables.product.prodname_dotcom %} にプッシュします。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} への変更をプッシュする](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github)」を参照してください。 -#### Collaborating with {% data variables.product.prodname_desktop %} -You can use {% data variables.product.prodname_desktop %} to create issues or pull requests to collaborate on projects with other people. Issues help you keep track of ideas and discuss possible changes to projects. Pull requests let you share your proposed changes with others, receive feedback, and merge changes into a project. For more information, see "[Creating an issue or pull request](/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request)."'' +#### {% data variables.product.prodname_desktop %} とのコラボレーション +{% data variables.product.prodname_desktop %} を使用して、問題を作成したり、リクエストをプルして他のユーザとプロジェクトでコラボレーションしたりすることができます。 Issue は、アイデアを追跡し、プロジェクトに加えられる可能性のある変更について議論する際に役立ちます。 プルリクエストを使用すると、提案された変更を他のユーザと共有したり、フィードバックを受け取ったり、変更をプロジェクトにマージしたりすることができます。 詳しい情報については、「[Issue またはプルリクエストを作成する](/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request)」を参照してください。 -You can view your own or your collaborator's pull requests in {% data variables.product.prodname_desktop %}. Viewing a pull request in {% data variables.product.prodname_desktop %} lets you see any proposed changes and make additional changes by opening the project's files and repositories in your default text editor. For more information, see "[Viewing a pull request in {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop)." +自分またはコラボレータのプルリクエストは、{% data variables.product.prodname_desktop %} で見ることができます。 {% data variables.product.prodname_desktop %} でプルリクエストを表示し、デフォルトのテキストエディタでプロジェクトのファイルとリポジトリを開くと、提案された変更を確認して、追加の変更を加えることができます。 詳しい情報については、「[{% data variables.product.prodname_desktop %} のプルリクエストを表示する](/desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop)」を参照してください。 -#### Keeping your local repository in sync -When you make changes to your local repositories or when other people make changes to the remote repositories, you will need to sync your local copy of the project with the remote repository. {% data variables.product.prodname_desktop %} can keep your local copy of a project in sync with the remote version by pushing and pulling commits. 詳しい情報については、「[ブランチを同期する](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)」を参照してください。 +#### ローカルリポジトリの同期を維持する +ローカルリポジトリに変更を加える場合、または他のユーザがリモートリポジトリに変更を加える場合は、プロジェクトのローカルコピーをリモートリポジトリと同期する必要があります。 {% data variables.product.prodname_desktop %} は、コミットをプッシュおよびプルすることにより、プロジェクトのローカルコピーをリモートバージョンと同期させることができます。 詳しい情報については、「[ブランチを同期する](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)」を参照してください。 ### 参考リンク -- "[Installing and authenticating to {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop)" -- "[Contributing and collaborating using {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop)" +- 「[{% data variables.product.prodname_desktop %} へのインストールと認証](/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop)」 +- 「[{% data variables.product.prodname_desktop %} を使用した貢献とコラボレーション](/desktop/contributing-and-collaborating-using-github-desktop)」 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 99b290bb34..c2229e0e70 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 @@ -73,10 +73,12 @@ versions: | `plan` | 「[ユーザの取得](/rest/reference/users#get-a-user)」エンドポイントを使用してユーザの GitHub プランについての情報を取得するためのアクセス権を付与します。 `none`、`read` のいずれかです。 | | [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | さまざまなプルリクエストエンドポイントへのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | [Repository Webhooks API](/rest/reference/repos#hooks) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | [Projects API](/rest/reference/projects) へのアクセス権を付与します。 `none`、`read`、`write`、`admin` のいずれかです。 | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | [Projects API](/rest/reference/projects) へのアクセス権を付与します。 `none`、`read`、`write`、`admin` のいずれかです。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | [Secret scanning API](/rest/reference/secret-scanning) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | [Code scanning API](/rest/reference/code-scanning/) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。{% endif %} | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | [Contents API](/rest/reference/repos#contents) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | [Starring API](/rest/reference/activity#starring) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | -| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | [Statuses API](/rest/reference/repos#statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | +| [`ステータス`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | [Statuses API](/rest/reference/repos#statuses) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | [Team Discussions API](/rest/reference/teams#discussions) および [Team Discussion Comments API](/rest/reference/teams#discussion-comments) へのアクセス権を付与します。 `none`、`read`、`write` のいずれかです。 | | `vulnerability_alerts` | リポジトリ内の脆弱性のある依存関係に対するセキュリティアラートを受信するためのアクセス権を付与します。 詳細は「[脆弱性のある依存関係に対するセキュリティアラートについて](/articles/about-security-alerts-for-vulnerable-dependencies)」を参照。 `none`、`read` のいずれかです。 | | `Watch` | リストへのアクセス権を付与し、ユーザがサブスクライブするリポジトリの変更を許可します。 `none`、`read`、`write` のいずれかです。 | 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 0f0f89156e..0a23419f37 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 @@ -37,15 +37,15 @@ Checks API は、新しいコードがリポジトリにプッシュされるた * パート 1: Checks API を使用して CI サーバー用のフレームワークをセットアップする。 * Checks API イベントを受信するサーバーとして GitHub App を構成します。 * 新たにプッシュされたコミットをリポジトリが受信した時に、CI テスト用の新しいチェック実行を作成します。 - * Re-run check runs when a user requests that action on GitHub. + * ユーザが GitHub でチェック実行のアクションをリクエストした時に、チェック実行を再実行します。 * パート 2: 文法チェッカー CI テストを追加して、作成した CI サーバーフレームワークを基に構築する。 - * Update a check run with a `status`, `conclusion`, and `output` details. - * Create annotations on lines of code that GitHub displays in the **Checks** and **Files Changed** tab of a pull request. - * Automatically fix linter recommendations by exposing a "Fix this" button in the **Checks** tab of the pull request. + * `status`、`conclusion`、`output` の情報を入力して、チェック実行を更新します。 + * プルリクエストの [**Checks**] および [**Files Changed**] タブで GitHub が表示する、コードの行のアノテーションを作成します。 + * プルリクエストの [**Checks**] タブに [Fix this] ボタンを表示して、文法チェッカーによる推奨事項を自動的に適用します。 このクイックスタートを完了したときに Checks API CI サーバーがどのように動作するかを理解するには、以下のデモをご覧ください。 -![Demo of Checks API CI sever quickstart](/assets/images/github-apps/github_apps_checks_api_ci_server.gif) +![Checks API CI サーバークイックスタートのデモ](/assets/images/github-apps/github_apps_checks_api_ci_server.gif) ### 必要な環境 @@ -195,7 +195,7 @@ $ ruby template_server.rb さて、それではアプリケーションをインストールしたリポジトリにあるプルリクエストを開いてください。 アプリケーションは応答し、プルリクエストのチェック実行を作成するはずです。 [**Checks**] タブをクリックすると、画面が以下のようになっているはずです。 -![Queued check run](/assets/images/github-apps/github_apps_queued_check_run.png) +![キューに入ったチェック実行](/assets/images/github-apps/github_apps_queued_check_run.png) [Checks] タブに他のアプリケーションが表示されている場合は、チェックに対して**読み取りおよび書き込み**アクセス権を持ち、**Check suite** および **Check run** イベントにサブスクライブしている他のアプリケーションをリポジトリにインストールしているものと思われます。 @@ -203,11 +203,11 @@ $ ruby template_server.rb ### ステップ 1.4. チェック実行を更新する -`create_check_run` メソッドが実行されると、メソッドは GitHub に新しいチェック実行を作成するよう依頼します。 Github がチェック実行の作成を完了すると、`created` アクションの `check_run` webhook イベントを受信します。 このイベントは、チェックの実行が始まる合図です。 +`create_check_run` メソッドが実行されると、メソッドは GitHub に新しいチェック実行を作成するよう依頼します。 Github がチェック実行の作成を完了すると、`created` アクションの `check_run` webhook イベントを受信します。 このイベントは、チェックの実行を開始する合図です。 イベントハンドラーを更新し、`created` アクションを待ち受けるようにしましょう。 イベントハンドラーを更新する際、`rerequested` アクションに条件を追加できます。 誰かが [Re-run] ボタンをクリックして GitHub 上で単一のテストを再実行すると、GitHub はアプリケーションに `rerequested` チェック実行イベントを送信します。 チェック実行が `rerequested` の場合、すべてのプロセスを開始し、新しいチェック実行を作成します。 -To include a condition for the event in the `post '/event_handler'` ルートに `check_run` イベントの条件を含めるには、`case request.env['HTTP_X_GITHUB_EVENT']` の下に次のコードを追加します。 +`post '/event_handler'` ルートに `check_run` イベントの条件を含めるには、`case request.env['HTTP_X_GITHUB_EVENT']` の下に次のコードを追加します。 ``` ruby when 'check_run' @@ -309,7 +309,7 @@ end このコードがしていることを説明しましょう。 まず、チェック実行のステータスを `in_progress` に更新し、`started_at` の時刻を現在の時刻に設定します。 このクイックスタートの[パート 2](#part-2-creating-the-octo-rubocop-ci-test)では、実際の CI テストを開始するコードを `***** RUN A CI TEST *****` の下に追加します。 今はこのセクションをプレースホルダーとして残しておきましょう。そうすると、続くコードが CI のプロセスを成功させ、すべてのテストに合格したことをシミュレートすることになります。 最後に、コードはチェック実行のステータスを再び `completed` に更新します。 -You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. `conclusion` はチェック実行の結果を要約するもので、`success`、`failure`、`neutral`、`cancelled`、`timed_out`、`action_required` のいずれかになります。 この結果 (conclusion) は `success` に、`completed_at` の時刻は現在の時刻に、ステータスは `completed` に設定します。 +「[チェック実行を更新する](/rest/reference/checks#update-a-check-run)」 ドキュメントに、`completed` のステータスを指定すると、`conclusion` と `completed_at` のパラメータが必須となることが書かれています。 `conclusion` はチェック実行の結果を要約するもので、`success`、`failure`、`neutral`、`cancelled`、`timed_out`、`action_required` のいずれかになります。 この結果 (conclusion) は `success` に、`completed_at` の時刻は現在の時刻に、ステータスは `completed` に設定します。 チェックが行っていることについてより詳しく指定することもできますが、それは次のセクションで行うことにします。 では、`template_server.rb` を実行して、このコードを再びテストしましょう。 @@ -319,7 +319,7 @@ $ ruby template_server.rb 開いたプルリクエストに移動し、[**Checks**] タブをクリックします。 左上隅にある [Re-run all] ボタンをクリックしてください。 チェック実行が `pending` から `in_progress` に移動し、`success` で終わることが確認できるはずです。 -![Completed check run](/assets/images/github-apps/github_apps_complete_check_run.png) +![完了したチェック実行](/assets/images/github-apps/github_apps_complete_check_run.png) ### パート2. Octo RuboCop CI テストを作成する @@ -327,7 +327,7 @@ $ ruby template_server.rb * コードのスタイルを確認する文法チェック * コードの整形 -* Replaces the native Ruby linting capabilities using `ruby -w` +* `ruby -w` を使用するネイティブの Ruby 文法チェック機能を置き換える さて、Checks API を受信し、チェック実行を作成するために作ったインターフェースができあがったところで、今度は CI テストを実装するチェック実行を作成しましょう。 @@ -337,7 +337,7 @@ Checks API を使用すると、ステータス、画像、要約、アノテー アノテーションとは、リポジトリのコードの特定の行についての情報です。 アノテーションを使用すると、追加情報を表示したいコードの部分を細かく指定して、それを視覚化できます。 この情報は、たとえばコメント、エラー、警告など何でも構いません。 このクイックスタートでは、RuboCop のエラーを視覚化するためにアノテーションを使用します。 -リクエストされたアクションを利用るため、アプリケーション開発者はプルリクエストの [**Checks**] タブにボタンを作成できます。 このボタンがクリックされると、そのクリックにより GitHub App に `requested_action` `check_run` イベントが送信されます。 アプリケーションが行うアクションは、アプリケーション開発者が自由に設定できます。 このクイックスタートでは、RuboCop が見つけたエラーを修正するようユーザがリクエストするためのボタンを追加する方法について説明します。 RuboCop はコマンドラインオプションによるエラーの自動的な修正をサポートしており、ここでは `requested_action` を設定して、このオプションを使用できるようにします。 +リクエストされたアクションを利用するため、アプリケーション開発者はプルリクエストの [**Checks**] タブにボタンを作成できます。 このボタンがクリックされると、そのクリックにより GitHub App に `requested_action` `check_run` イベントが送信されます。 アプリケーションが実行するアクションは、アプリケーション開発者が自由に設定できます。 このクイックスタートでは、RuboCop が見つけたエラーを修正するようユーザがリクエストするためのボタンを追加する方法について説明します。 RuboCop はコマンドラインオプションによるエラーの自動的な修正をサポートしており、ここでは `requested_action` を設定して、このオプションを使用できるようにします。 さあ、始めましょう！ このセクションでは、以下のステップを完了させます。 @@ -435,9 +435,9 @@ clone_repository(full_repo_name, repository, head_sha) ### ステップ 2.3. RuboCop を実行する -これでうまくいきました。 You're cloning the repository and creating check runs using your CI server. それではいよいよ [RuboCop 文法チェッカー](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) と [Checks API アノテーション](/rest/reference/checks#create-a-check-run)の核心に迫ります。 +これでうまくいきました。 リポジトリをクローンし、CI サーバーを使用してチェック実行を作成しようという段階にまで到達しました。 それではいよいよ [RuboCop 文法チェッカー](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) と [Checks API アノテーション](/rest/reference/checks#create-a-check-run)の核心に迫ります。 -次のコードは、RuboCop を実行し、スタイル コード エラーを JSON フォーマットで保存します。 Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete. +次のコードは、RuboCop を実行し、スタイル コード エラーを JSON フォーマットで保存します。 [前のステップ](#step-22-cloning-the-repository) で追加した`clone_repository` への呼び出しの下と、チェック実行を更新するコードの上に追加して完了です。 ``` ruby # Run RuboCop on all files in the repository @@ -694,46 +694,46 @@ updated_check_run = @installation_client.patch( さて、これで CI テストのステータスに基づいて結論を設定し、RuboCop の結果からの出力を追加しました。あなたは CI テストを作成したのです。 おめでとうございます。 🙌 -また、上記のコードは、`actions` オブジェクトを介して CI サーバーに[リクエストされたアクション](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/)という機能も追加しています。 {% if currentVersion == "free-pro-team@latest" %}(Note this is not related to [GitHub Actions](/actions).) {% endif %}リクエストされたアクションは、追加のアクションを実行するためにチェック実行をリクエストできるボタンを GitHub の [**Checks**] タブに追加します。 The additional action is completely configurable by your app. For example, because RuboCop has a feature to automatically fix the errors it finds in Ruby code, your CI server can use a requested actions button to allow people to request automatic error fixes. When someone clicks the button, the app receives the `check_run` event with a `requested_action` action. Each requested action has an `identifier` that the app uses to determine which button was clicked. +また、上記のコードは、`actions` オブジェクトを介して CI サーバーに[リクエストされたアクション](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/)という機能も追加しています。 {% if currentVersion == "free-pro-team@latest" %}(Note this is not related to [GitHub Actions](/actions).) {% endif %}リクエストされたアクションは、追加のアクションを実行するためにチェック実行をリクエストできるボタンを GitHub の [**Checks**] タブに追加します。 追加のアクションは、アプリケーションが自由に設定できます。 たとえば、RuboCop には Ruby のコードで見つかったエラーを自動的に修正する機能があるので、CI サーバーはリクエストされたアクションボタンを使用して、自動的なエラー修正をユーザが許可することができます。 このボタンをクリックすると、アプリケーションは `requested_action` アクションで `check_run` イベントを受け取ります。 リクエストされた各アクションには、どのボタンがクリックされたかアプリケーションが判断するために使用する `identifier` があります。 -The code above doesn't have RuboCop automatically fix errors yet. You'll add that in the next section. But first, take a look at the CI test that you just created by starting up the `template_server.rb` server again and creating a new pull request: +上記のコードには、まだ RuboCop が自動的にエラーを修正する処理がありません。 この処理については、次のセクションで追加します。 しかしまずは、`template_server.rb` サーバーを再起動して新しいプルリクエストを作成し、さきほど作成した CI テストを見てみましょう。 ```shell $ ruby template_server.rb ``` -The annotations will show up in the **Checks** tab. +アノテーションは [**Checks**] タブに表示されます。 -![Check run annotations in the checks tab](/assets/images/github-apps/github_apps_checks_annotations.png) +![[Checks] タブのチェック実行アノテーション](/assets/images/github-apps/github_apps_checks_annotations.png) -Notice the "Fix this" button that you created by adding a requested action. +リクエストされたアクションを追加することにより作成された [Fix this] ボタンに注目してください。 ![チェック実行のリクエストされたアクションのボタン](/assets/images/github-apps/github_apps_checks_fix_this_button.png) -If the annotations are related to a file already included in the PR, the annotations will also show up in the **Files changed** tab. +すでにプルリクエストに含まれているファイルにアノテーションが関連している場合、そのアノテーションは [**Files changed**] タブにも表示されます。 -![Check run annotations in the files changed tab](/assets/images/github-apps/github_apps_checks_annotation_diff.png) +![ファイルが変更されたタブのチェック実行アノテーション](/assets/images/github-apps/github_apps_checks_annotation_diff.png) ### ステップ 2.6. RuboCop のエラーを自動的に修正する -If you've made it this far, kudos! 👏 You've already created a CI test. In this section, you'll add one more feature that uses RuboCop to automatically fix the errors it finds. You already added the "Fix this" button in the [previous section](#step-25-updating-the-check-run-with-ci-test-results). Now you'll add the code to handle the `requested_action` check run event triggered when someone clicks the "Fix this" button. +ここまで来たのはすごいですよ！ 👏 あなたはもう CI テストを作成しました。 このセクションでは、もう 1 つの機能を追加します。RuboCop を使用して、見つけたエラーを自動的に修正するために使用するための機能です。 すでに[前のセクション](#step-25-updating-the-check-run-with-ci-test-results)で、[Fix this] ボタンを追加しました。 ここでは、ユーザが [Fix this] ボタンをクリックしたときにトリガーされる、`requested_action` チェック実行イベントを処理するコードを追加します。 -The RuboCop tool [offers](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic. +RuboCop ツールには、見つけたエラーを自動的に修正する `--auto-correct` コマンドラインオプションの [機能](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) があります。 `--auto-correct` 機能を使用すると、サーバー上のローカルファイルに更新が適用されます。 RuboCop がこの作業をやってのけた後は、その変更を GitHub にプッシュする必要があります。 -To push to a repository, your app must have write permissions for "Repository contents." You set that permission back in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) to **Read & write**, so you're all set. +リポジトリにブッシュするには、アプリケーションに [Repository contents] への書き込み権限が必要です。 この権限については、[ステップ 2.2. リポジトリをクローンする](#step-22-cloning-the-repository)で既に [**Read & write**] に設定しているので、もう準備は整っています。 -In order to commit files, Git must know which [username](/articles/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. 例: +ファイルをコミットするには、どの[ユーザ名](/articles/setting-your-username-in-git/)と[メールアドレス](/articles/setting-your-commit-email-address-in-git/)をコミットに関連付けるか Git が知っている必要があります。 `.env` ファイルにあと 2 つの環境変数を追加して、名前 (`GITHUB_APP_USER_NAME`) とメールアドレス (`GITHUB_APP_USER_EMAIL`) の設定を保存します。 アプリケーションにはあなたの名前を付けることもできます。この例では、メールアドレスは何でも構いません。 例: ``` GITHUB_APP_USER_NAME=Octoapp GITHUB_APP_USER_EMAIL=octoapp@octo-org.com ``` -Once you've updated your `.env` file with the name and email of the author and committer, you'll be ready to add code to read the environment variables and set the Git configuration. You'll add that code soon. +作者およびコミッターの、名前およびメールアドレスを入力して `.env` ファイルを更新したら、環境変数を読み取るコードを追加し、Git の設定を行う準備が整いました。 このコードは、もうすぐ追加することになります。 -When someone clicks the "Fix this" button, your app receives the [check run webhook](/webhooks/event-payloads/#check_run) with the `requested_action` action type. +ユーザが [Fix this] ボタンをクリックすると、アプリケーションは `requested_action` アクションタイプの [check run webhook](/webhooks/event-payloads/#check_run) を受信します。 -In [Step 1.4. Updating a check run](#step-14-updating-a-check-run) you updated the your `event_handler` to handle look for actions in the `check_run` event. You already have a case statement to handle the `created` and `rerequested` action types: +[ステップ 1.4. チェック実行を更新する](#step-14-updating-a-check-run)では、`check_run` イベント内の検索アクションを処理するため、`event_handler` を更新しました。 そのため、`created` と `rerequested` のアクションタイプを処理する case 文は既に存在します。 ``` ruby when 'check_run' @@ -748,14 +748,14 @@ when 'check_run' end ``` -Add another `when` statement after the `rerequested` case to handle the `rerequested_action` event: +`rerequested` の条件の後に、 `rerequested_action` イベントを処理するためもう 1 つ `when` 文を追加します。 ``` ruby when 'requested_action' take_requested_action ``` -This code calls a new method that will handle all `requested_action` events for your app. Add the following method to the helper methods section of your code: +このコードは、アプリケーションのすべての `requested_action` イベントを処理する新しいメソッドを呼び出します。 以下のメソッドをコードのヘルパーメソッドセクションに追加します。 ``` ruby # Handles the check run `requested_action` event @@ -790,11 +790,11 @@ def take_requested_action end ``` -The code above clones a repository just like the code you added in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository). An `if` statement checks that the requested action's identifier matches the RuboCop button identifier (`fix_rubocop_notices`). When they match, the code clones the repository, sets the Git username and email, and runs RuboCop with the option `--auto-correct`. The `--auto-correct` option applies the changes to the local CI server files automatically. +上記のコードは、[ステップ 2.2. リポジトリをクローンする](#step-22-cloning-the-repository)で追加したようなコードと同様、リポジトリをクローンします。 `if` 文は、リクエストされたアクションの識別子が、RuboCop ボタンの識別子 (`fix_rubocop_notices`) と一致するかを確認します。 一致する場合、 このコードはリポジトリをクローンし、Git ユーザ名とメールアドレスを設定し、`--auto-correct` オプションを指定して RuboCop を実行します。 `--auto-correct` オプションは、ローカルの CI サーバーファイルに変更を自動的に適用します。 -The files are changed locally, but you'll still need to push them to GitHub. You'll use the handy `ruby-git` gem again to commit all of the files. Git has a single command that stages all modified or deleted files and commits them: `git commit -a`. To do the same thing using `ruby-git`, the code above uses the `commit_all` method. Then the code pushes the committed files to GitHub using the installation token, using the same authentication method as the Git `clone` command. Finally, it removes the repository directory to ensure the working directory is prepared for the next event. +ファイルはローカルで変更されますが、それを GitHub にプッシュする必要はあります。 便利な `ruby-git` gem を再び使用し、全てのファイルをコミットしましょう。 Git には、変更または削除されたすべてのファイルをステージングし、それらをコミットする `git commit -a` というコマンドがあります。 `ruby-git` を使用して同じことを行うため、上記のコードは `commit_all` メソッドを使用しています。 それから、このコードは Git の `clone` コマンドと同じ認証方式を使用し、インストールトークンを使用して GitHub にコミットしたファイルをプッシュします。 最後に、リポジトリディレクトリを削除して、ワーキングディレクトリが次のイベントに備えるようにします。 -これで完了です。 The code you have written now completes your Checks API CI server. 💪 Restart your `template_server.rb` server again and create a new pull request: +これで完了です。 Checks API CI サーバーのコードがついに完成しました。 💪 `template_server.rb` サーバーをもう一度再起動し、新しいプルリクエストを次の通り作成しましょう。 ```shell $ ruby template_server.rb @@ -802,21 +802,21 @@ $ ruby template_server.rb {% data reusables.apps.sinatra_restart_instructions %} -This time, click the "Fix this" button to automatically fix the errors RuboCop found from the **Checks** tab. +今回は、[Fix this] ボタンをクリックすると、RuboCop が [**Checks**] タブから見つけたエラーを自動的に修正します。 -In the **Commits** tab, you'll see a brand new commit by the username you set in your Git configuration. You may need to refresh your browser to see the update. +[**Commits**] タブには、Git コンフィグレーションで設定したユーザ名による新たなコミットが表示されています。 更新を確認するには、ブラウザを更新する必要がある場合があります。 -![A new commit to automatically fix Octo RuboCop notices](/assets/images/github-apps/github_apps_new_requested_action_commit.png) +![Octo RuboCop の通知を自動的に修正する新しいコミット](/assets/images/github-apps/github_apps_new_requested_action_commit.png) -Because a new commit was pushed to the repo, you'll see a new check suite for Octo RuboCop in the **Checks** tab. But this time there are no errors because RuboCop fixed them all. 🎉 +新たなコミットがリポジトリにプッシュされたので、[**Checks**] タブに Octo RuboCop の新しいチェックスイートが表示されています。 しかし今回はエラーがありません。RuboCop がエラーをすべて修正したからです。 🎉 -![No check suite or check run errors](/assets/images/github-apps/github_apps_checks_api_success.png) +![チェックスイート、チェック実行のエラーなし](/assets/images/github-apps/github_apps_checks_api_success.png) -You can find the completed code for the app you just built in the `server.rb` file in the [Creating CI tests with the Checks API](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) repository. +ここであなたか構築したアプリケーションの完成したコードは、[Checks API で CI テストを作成する](https://github.com/github-developer/creating-ci-tests-with-the-checks-api)のリポジトリの `server.rb` ファイルにあります。 ### ステップ 2.7. セキュリティのヒント -The template GitHub App code already has a method to verify incoming webhook payloads to ensure they are from a trusted source. If you are not validating webhook payloads, you'll need to ensure that when repository names are included in the webhook payload, the webhook does not contain arbitrary commands that could be used maliciously. The code below validates that the repository name only contains Latin alphabetic characters, hyphens, and underscores. To provide you with a complete example, the complete `server.rb` code available in the [companion repository](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) for this quickstart includes both the method of validating incoming webhook payloads and this check to verify the repository name. +GitHub App コードのテンプレートには、受信した webhook ペイロードを検証して、信頼できるソースからのものであることを確認するためのメソッドが最初から用意されています。 webhook ペイロードを検証しない場合、リポジトリ名が webhook ペイロードに含まれる際には、その webhook が悪意をもって使用されかねない任意のコマンドを確実に含まないようにする必要があります。 以下のコードは、リポジトリ名に含まれる文字がラテン文字、ハイフン、アンダースコアのみであることを検証します。 完全なサンプルを提供するため、[コンパニオンリポジトリ](https://github.com/github-developer/creating-ci-tests-with-the-checks-api)で入手できる、このクイックスタートのための完成した `server.rb` コードには、受信する webhook ペイロードを検証するメソッドと、リポジトリ名を検証するためのここで挙げたチェックの両方が含まれています。 ``` ruby # This quickstart example uses the repository name in the webhook with @@ -834,39 +834,39 @@ end Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}. -* **Q:** アプリケーションが GitHub にコードをプッシュしません。 I don't see the fixes that RuboCop automatically makes! +* **Q:** アプリケーションが GitHub にコードをプッシュしません。 RuboCop が自動的に行う修正が表示されません。 - **A:** Make sure you have **Read & write** permissions for "Repository contents," and that you are cloning the repository with your installation token. [ステップ 2.2. Cloning the repository](#step-22-cloning-the-repository) for details. + **A:** [Repository contents] に対する **Read & write** 権限があること、およびインストールトークンでリポジトリをクローンしていることを確認します。 [ステップ 2.2. リポジトリをクローンする](#step-22-cloning-the-repository)を参照してください。 -* **Q:** I see an error in the `template_server.rb` debug output related to cloning my repository. +* **Q:** リポジトリのクローンに関する、`template_server.rb` デバッグ出力にエラーが表示されます。 - **A:** If you see the following error, you haven't deleted the checkout of the repository in one or both of the `initiate_check_run` or `take_requested_action` methods: + **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.: ``` - Compare your code to the `server.rb` file to ensure you have the same code in your `initiate_check_run` and `take_requested_action` methods. + コードを `server.rb` ファイルと比較し、`initiate_check_run` および `take_requested_action` メソッドと同じコードがあることを確認してください。 -* **Q:** New check runs are not showing up in the "Checks" tab on GitHub. +* **Q:** 新しいチェック実行が、GitHub の [Checks] タブで表示されません。 - **A:** Restart Smee and re-run your `template_server.rb` server. + **A:** Smee を再起動し、`template_server.rb` サーバーを再実行してください。 -* **Q:** I do not see the "Re-run all" button in the "Checks" tab on GitHub. +* **Q:** [Re-run all] ボタンが、GitHub の [Checks] タブで表示されません。 - **A:** Restart Smee and re-run your `template_server.rb` server. + **A:** Smee を再起動し、`template_server.rb` サーバーを再実行してください。 ### おわりに -After walking through this guide, you've learned the basics of using the Checks API to create a CI server! To review, you: +このガイドの手順を一通り終えたら、Checks API を使用して CI サーバーを作成することの基本が習得できています。 To review, you: -* Configured your server to receive Checks API events and create check runs. -* Used RuboCop to check code in repositories and create annotations for the errors. -* Implemented a requested action that automatically fixes linter errors. +* Checks API イベントを受信し、チェック実行を作成するようサーバーを設定しました。 +* リポジトリ内のコードをチェックし、エラーのアノテーションを作成するため RuboCop を使用しました。 +* 文法エラーを自動的に修正する、リクエストされたアクションを実装しました。 ### 次のステップ Here are some ideas for what you can do next: -* Currently, the "Fix this" button is always displayed. Update the code you wrote to display the "Fix this" button only when RuboCop finds errors. -* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch. +* 現在、[Fix this] ボタンは常に表示されています。 ここまで書いたコードを更新し、RuboCop がエラーを見つけた時にのみ [Fix this] ボタンが表示されるようにしましょう。 +* RuboCop がファイルを head ブランチに直接コミットしないようにしたい場合、head ブランチに基づいて新しいブランチで[プルリクエストを作成する](/rest/reference/pulls#create-a-pull-request)ようにコードを更新できます。 diff --git a/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md b/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md index 90a725ed17..59c7538b04 100644 --- a/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/differences-between-github-apps-and-oauth-apps.md @@ -1,6 +1,6 @@ --- title: GitHub App と OAuth App の違い -intro: 'Understanding the differences between {% data variables.product.prodname_github_app %}s and {% data variables.product.prodname_oauth_app %}s will help you decide which app you want to create. An {% data variables.product.prodname_oauth_app %} acts as a GitHub user, whereas a {% data variables.product.prodname_github_app %} uses its own identity when installed on an organization or on repositories within an organization.' +intro: '{% data variables.product.prodname_github_app %} と {% data variables.product.prodname_oauth_app %} の違いについて知っておくと、どちらのアプリケーションを作成するかを決めるために役立ちます。 {% data variables.product.prodname_oauth_app %} は GitHub ユーザとして振る舞う一方、{% data variables.product.prodname_github_app %} は Organization または Organization 内のリポジトリにインストールされた場合、自らのアイデンティティを用います。' redirect_from: - /early-access/integrations/integrations-vs-oauth-applications/ - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type/ @@ -11,35 +11,35 @@ versions: github-ae: '*' --- -### Who can install GitHub Apps and authorize OAuth Apps? +### GitHub App のインストール、OAuth App の承認が可能なユーザ -You can install GitHub Apps in your personal account or organizations you own. If you have admin permissions in a repository, you can install GitHub Apps on organization accounts. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. +GitHub App は、個人アカウントおよび自分が所有する Organization にインストールできます。 リポジトリの管理者権限がある場合には、GitHub App を Organization のアカウントにインストールできます。 GitHub App がリポジトリにインストールされていて、Organization の権限を要求している場合、Organization のオーナーはアプリケーションを承認する必要があります。 {% data reusables.apps.app_manager_role %} -By contrast, users _authorize_ OAuth Apps, which gives the app the ability to act as the authenticated user. For example, you can authorize an OAuth App that finds all notifications for the authenticated user. You can always revoke permissions from an OAuth App. +それに対し、ユーザは OAuth App を_承認_します。これにより、アプリケーションは認証されたユーザとして振る舞うことができます。 たとえば、認証されたユーザに対するすべての通知を検索する OAuth App を承認できます。 OAuth App の権限はいつでも取り消すことができます。 {% data reusables.apps.deletes_ssh_keys %} -| GitHub Apps | OAuth Apps | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| You must be an organization owner or have admin permissions in a repository to install a GitHub App on an organization. If a GitHub App is installed in a repository and requires organization permissions, the organization owner must approve the application. | You can authorize an OAuth app to have access to resources. | -| You can install a GitHub App on your personal repository. | You can authorize an OAuth app to have access to resources. | -| You must be an organization owner, personal repository owner, or have admin permissions in a repository to uninstall a GitHub App and remove its access. | You can delete an OAuth access token to remove access. | -| You must be an organization owner or have admin permissions in a repository to request a GitHub App installation. | If an organization application policy is active, any organization member can request to install an OAuth App on an organization. An organization owner must approve or deny the request. | +| GitHub Apps | OAuth App | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | +| Organization に GitHub App をインストールするには、Organization のオーナーであるか管理者権限を所有している必要があります。 GitHub App がリポジトリにインストールされていて、Organization の権限を要求している場合、Organization のオーナーはアプリケーションを承認する必要があります。 | OAuth App を認証し、リソースへのアクセス権限を与えることができます。 | +| GitHub App は個人のリポジトリにインストールできます。 | OAuth App を認証し、リソースへのアクセス権限を与えることができます。 | +| GitHub App をアンインストールしてアクセス権限を削除するには、Organization のオーナーであるか、個人リポジトリの所有者であるか、リポジトリの管理者権限を所有している必要があります。 | OAuth アクセストークンを削除して、アクセス権限を削除することができます。 | +| GitHub App のインストールを要求するには、Organization のオーナーであるかリポジトリの管理者権限を所有している必要があります。 | Organization のアプリケーションポリシーが有効である場合、その Organization の任意のメンバーが OAuth App のインストールを要求できます。 Organization のオーナーは、その要求を承認または拒否する必要があります。 | ### What can GitHub Apps and OAuth Apps access? -Account owners can use a {% data variables.product.prodname_github_app %} in one account without granting access to another. For example, you can install a third-party build service on your employer's organization, but decide not to grant that build service access to repositories in your personal account. A GitHub App remains installed if the person who set it up leaves the organization. +アカウントの所有者は、別のアカウントにアクセス権限を与えることなく {% data variables.product.prodname_github_app %} を使用できます。 たとえば、サードパーティ製のビルドサービスを従業員の Organization にインストールしつつ、そのビルドサービスに個人アカウントにあるリポジトリへのアクセスを許可しないことができます。 GitHub App をセットアップした人が Organization から離れても、その GitHub App はインストールされたままになります。 -An _authorized_ OAuth App has access to all of the user's or organization owner's accessible resources. +_承認された_ OAuth App は、 ユーザまたは Organization のオーナーがアクセス可能なすべてのリソースにアクセスできます。 -| GitHub Apps | OAuth Apps | +| GitHub Apps | OAuth App | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Installing a GitHub App grants the app access to a user or organization account's chosen repositories. | Authorizing an OAuth App grants the app access to the user's accessible resources. For example, repositories they can access. | -| The installation token from a GitHub App loses access to resources if an admin removes repositories from the installation. | An OAuth access token loses access to resources when the user loses access, such as when they lose write access to a repository. | -| Installation access tokens are limited to specified repositories with the permissions chosen by the creator of the app. | An OAuth access token is limited via scopes. | -| GitHub Apps can request separate access to issues and pull requests without accessing the actual contents of the repository. | OAuth Apps need to request the `repo` scope to get access to issues, pull requests, or anything owned by the repository. | +| GitHub App をインスールすると、アプリケーションはユーザまたは Organization アカウントの指定したリポジトリにアクセス可能になります。 | OAuth App を承認すると、アプリケーションはユーザがアクセス可能なリソースにアクセスできます。 （例: リポジトリ） | +| 管理者がインストールからリポジトリを削除した場合、GitHub App のインストールトークンはリソースにアクセスできなくなります。 | リポジトリへの書き込みアクセスを失ったときなど、ユーザがアクセスを失ったとき、OAuth アクセストークンはリソースにアクセスできなくなります。 | +| インストールアクセストークンは、アプリケーションの作成者が指定したリポジトリの、選択した権限に制限されます。 | OAuth アクセストークンは、スコープにより制限されます。 | +| GitHub App は、リポジトリの実際のコンテンツにアクセスすることなく、Issue やプルリクエストへの個別のアクセスを要求できます。 | OAuth App は、Issue やプルリクエストなど、リポジトリが所有するリソースにアクセスするには `repo` スコープをリクエストする必要があります。 | | GitHub Apps aren't subject to organization application policies. A GitHub App only has access to the repositories an organization owner has granted. | If an organization application policy is active, only an organization owner can authorize the installation of an OAuth App. If installed, the OAuth App gains access to anything visible to the token the organization owner has within the approved organization. | | A GitHub App receives a webhook event when an installation is changed or removed. This tells the app creator when they've received more or less access to an organization's resources. | OAuth Apps can lose access to an organization or repository at any time based on the granting user's changing access. The OAuth App will not inform you when it loses access to a resource. | @@ -51,7 +51,7 @@ An _authorized_ OAuth App has access to all of the user's or organization owner' {% endnote %} -| GitHub Apps | OAuth Apps | +| GitHub Apps | OAuth App | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A GitHub App can request an installation access token by using a private key with a JSON web token format out-of-band. | An OAuth app can exchange a request token for an access token after a redirect via a web request. | | An installation token identifies the app as the GitHub Apps bot, such as @jenkins-bot. | An access token identifies the app as the user who granted the token to the app, such as @octocat. | @@ -64,7 +64,7 @@ An _authorized_ OAuth App has access to all of the user's or organization owner' Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to request access only to what they need. For example, a Continuous Integration (CI) GitHub App can request read access to repository content and write access to the status API. Another GitHub App can have no read or write access to code but still have the ability to manage issues, labels, and milestones. OAuth Apps can't use granular permissions. -| アクセス | GitHub Apps (`read` or `write` permissions) | OAuth Apps | +| アクセス | GitHub Apps (`read` or `write` permissions) | OAuth App | | ------------------------------------------------------- | --------------------------------------------------------- | -------------------------------------------- | | **For access to public repositories** | Public repository needs to be chosen during installation. | `public_repo` scope. | | **For access to repository code/contents** | リポジトリコンテンツ | `repo` scope. | @@ -76,21 +76,21 @@ Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to requ ### Repository discovery -| GitHub Apps | OAuth Apps | +| GitHub Apps | OAuth App | | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | GitHub Apps can look at `/installation/repositories` to see repositories the installation can access. | OAuth Apps can look at `/user/repos` for a user view or `/orgs/:org/repos` for an organization view of accessible repositories. | | GitHub Apps receive webhooks when repositories are added or removed from the installation. | OAuth Apps create organization webhooks for notifications when a new repository is created within an organization. | ### webhook -| GitHub Apps | OAuth Apps | +| GitHub Apps | OAuth App | | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | By default, GitHub Apps have a single webhook that receives the events they are configured to receive for every repository they have access to. | OAuth Apps request the webhook scope to create a repository webhook for each repository they needs to receive events from. | | GitHub Apps receive certain organization-level events with the organization member's permission. | OAuth Apps request the organization webhook scope to create an organization webhook for each organization they need to receive organization-level events from. | ### Git access -| GitHub Apps | OAuth Apps | +| GitHub Apps | OAuth App | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | GitHub Apps ask for repository contents permission and use your installation token to authenticate via [HTTP-based Git](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth Apps ask for `write:public_key` scope and [Create a deploy key](/rest/reference/repos#create-a-deploy-key) via the API. You can then use that key to perform Git commands. | | The token is used as the HTTP password. | The token is used as the HTTP username. | @@ -101,7 +101,7 @@ Machine user accounts are OAuth-based user accounts that segregate automated sys Bot accounts are specific to GitHub Apps and are built into every GitHub App. -| GitHub Apps | OAuth Apps | +| GitHub Apps | OAuth App | | --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | GitHub App bots do not consume a {% data variables.product.prodname_enterprise %} seat. | A machine user account consumes a {% data variables.product.prodname_enterprise %} seat. | | Because a GitHub App bot is never granted a password, a customer can't sign into it directly. | A machine user account is granted a username and password to be managed and secured by the customer. | diff --git a/translations/ja-JP/content/developers/apps/installing-github-apps.md b/translations/ja-JP/content/developers/apps/installing-github-apps.md index 0daf74da0b..d2a4745e08 100644 --- a/translations/ja-JP/content/developers/apps/installing-github-apps.md +++ b/translations/ja-JP/content/developers/apps/installing-github-apps.md @@ -1,6 +1,6 @@ --- -title: Installing GitHub Apps -intro: 'When your app is public, anyone can install your app on their repository through {% if currentVersion == "free-pro-team@latest" %} the {% data variables.product.prodname_marketplace %} or {% endif %}an installation URL. When your app is private, you can only install the app on repositories that you own.' +title: GitHub Appのインストール +intro: 'アプリケーションがパブリックなら、{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_marketplace %}あるいは{% endif %}インストールURLを通じて、誰でも自分のリポジトリにそのアプリケーションをインストールできます。 アプリケーションがプライベートの場合は、あなたが所有するリポジトリにあなただけがそのアプリケーションをインストールできます。' redirect_from: - /apps/installing-github-apps versions: @@ -11,53 +11,53 @@ versions: {% note %} -**Note:** Your {% data variables.product.prodname_github_app %} will have access to any repositories the app creates, even if someone only installs your app on selected repositories. +**ノート:** {% data variables.product.prodname_github_app %}は、誰かがアプリケーションを選択したリポジトリにだけインストールした場合でも、アプリケーションが作成するすべてのリポジトリにアクセスできます。 {% endnote %} -### Installing your private GitHub App on your repository +### プライベートなGitHub Appのリポジトリへのインストール -Once you create a private GitHub App, you can install it on one of your org or user repositories. For more information, see "[Private installation flow](/apps/managing-github-apps/making-a-github-app-public-or-private/#private-installation-flow)." +プライベートなGitHub Appを作成した場合、自分のOrganizationあるいはユーザリポジトリにそれをインストールできます。 詳しい情報については「[プライベートインストールのフロー](/apps/managing-github-apps/making-a-github-app-public-or-private/#private-installation-flow)」を参照してください。 -1. From the [GitHub Apps settings page](https://github.com/settings/apps), select your app. -2. In the left sidebar, click **Install App**. -3. Click **Install** next to the organization or user account containing the correct repository. -4. Install the app on all repositories or select repositories. ![App installation permissions](/assets/images/install_permissions.png) -5. Once installed, you will see configuration options for the app on your selected account. You can make changes here, or repeat the previous steps to install the app on another account. +1. [GitHub Appsの設定ページ](https://github.com/settings/apps)から、アプリケーションを選択してください。 +2. 左のサイドバーで、**Install App（アプリケーションのインストール）**をクリックしてください。 +3. 適切なリポジトリを含むOrganizationもしくはユーザアカウントの隣の** Install（インストール）**をクリックしてください。 +4. すべてのリポジトリ、もしくは選択したリポジトリにアプリケーションをインストールしてください。 ![アプリケーションのインストール権限](/assets/images/install_permissions.png) +5. インストールが終わると、選択したアカウントでアプリケーションの設定オプションが表示されます。 ここで変更をすることも、あるいは先のステップを繰り返して他のアカウントへアプリケーションをインストールすることもできます。 {% if currentVersion == "free-pro-team@latest" %} -### Offering your app in the GitHub Marketplace +### GitHub Marketplaceでのアプリケーションの提供 -You can offer a paid or free version of your app in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), where people can search for and view details about your app. {% data variables.product.prodname_marketplace %} automatically installs a GitHub App when an order is complete. +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace)では有料あるいは無料バージョンのアプリケーションを提供でき、ユーザがアプリケーションについて検索したり表示したりできます。 {% data variables.product.prodname_marketplace %}は注文が完了すると、自動的にGitHub Appをインストールします。 -See "[Getting started with GitHub Marketplace](/marketplace/getting-started/)" to learn more about listing your app on {% data variables.product.prodname_marketplace %}. +{% data variables.product.prodname_marketplace %}上でのアプリケーションのリストに関してさらに学ぶには、「[GitHub Marketplaceの利用を始める](/marketplace/getting-started/)」を参照してください。 -To learn more about how users can install your app from {% data variables.product.prodname_marketplace %}, see "[Purchasing and installing apps in GitHub Marketplace](/articles/purchasing-and-installing-apps-in-github-marketplace)". +{% data variables.product.prodname_marketplace %}からユーザがアプリケーションをインストールする方法の詳細については、「[GitHub Marketplaceでのアプリケーションの購入とインストール](/articles/purchasing-and-installing-apps-in-github-marketplace)」を参照してください。 {% endif %} -### Allowing people to install your public app on their repository +### ユーザがパブリックなアプリケーションをリポジトリにインストールできるようにする -You can enable others to install your public app by providing the installation URL in places like your app's homepage. You can then point to your app's homepage from the landing page on GitHub. +アプリケーションのホームページのような場所にインストールURLを提供して、パブリックなアプリケーションをユーザがインストールできるようにすることができます。 そして、GitHub上のランディングページからアプリケーションのホームページを指すようにできます。 - If you are migrating from an OAuth App to a GitHub App, you can use query parameters to preselect the repositories and account when installing the GitHub App. See "[Migrating OAuth Apps to GitHub Apps](/apps/migrating-oauth-apps-to-github-apps/)" to learn more. + OAuth AppからGitHub Appに移行しているなら、GitHub Appをインストールする際にリポジトリとアカウントを事前選択するよう、クエリパラメータを利用できます。 詳細については「[OAuth AppからGitHub Appへの移行](/apps/migrating-oauth-apps-to-github-apps/)」を参照してください。 -These steps assume you have [built a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/): +以下のステップでは、[{% data variables.product.prodname_github_app %}を構築](/apps/building-github-apps/)済みであるものとしています。 -1. From the [GitHub Apps settings page](https://github.com/settings/apps), select the public app you want to configure for others to install. -2. In "Homepage URL," type the URL for your app's homepage and click **Save changes**. ![Homepage URL](/assets/images/github-apps/github_apps_homepageURL.png) -3. GitHub provides a landing page for your app that includes a link to your app's "Homepage URL." To visit the landing page on GitHub, copy the URL from "Public link" and paste it into a browser. ![Public link](/assets/images/github-apps/github_apps_public_link.png) -4. Create a homepage for your app that includes the app installation URL: `{% data variables.product.oauth_host_code %}/apps//installations/new`. +1. [GitHub Appの設定ページ](https://github.com/settings/apps)から、他のユーザがインストールできるように設定したいパブリックなアプリケーションを選択してください。 +2. "Homepage URL（ホームページのURL）"にアプリケーションのホームページのURLを入力し、**Save changes（変更を保存）**をクリックしてください。 ![ホームページのURL](/assets/images/github-apps/github_apps_homepageURL.png) +3. GitHubは、アプリケーションの「ホームページURL」へのリンクを含むアプリケーションのためのランディングページを提供します。 GitHub上のランディングページにアクセスするには、「Public link（公開リンク）」からURLをコピーし、ブラウザに貼り付けてください。 ![公開リンク](/assets/images/github-apps/github_apps_public_link.png) +4. `{% data variables.product.oauth_host_code %}/apps//installations/new`というアプリケーションのインストールURLを含む、アプリケーションのためのホームページを作成してください。 -### Authorizing users during installation +### インストール中のユーザの認可 -You can simplify the authorization process by completing it during app installation. To do this, select **Request user authorization (OAuth) during installation** when creating or modifying your app in GitHub. See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" to learn more. +認可のプロセスは、アプリケーションのインストール中に完了させることでシンプルにできます。 そのためには、GitHub上でアプリケーションを作成もしくは変更する際に**Request user authorization (OAuth) during installation（インストール中にユーザの認可（OAuth）をリクエスト）**を選択してください。 詳細については「[GitHub Appの作成](/apps/building-github-apps/creating-a-github-app/)を参照してください。 -Once someone has installed your app, you will need to get an access token for the user. See steps 2 and 3 in "[Identifying users on your site](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)" to learn more. -### Preserving an application state during installation +誰かがアプリケーションをインストールしたら、そのユーザのアクセストークンを取得する必要があります。 詳細については「[サイトでのユーザの特定](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)」のステップ2と3を参照してください。 +### インストール中のアプリケーションの状態の保持 -You can provide a `state` parameter in an app's installation URL to preserve the state of the application page and return people back to that state after they install, authenticate, or accept updates to your GitHub App. For example, you could use the `state` to correlate an installation to a user or account. +アプリケーションのインストールURLに`state`パラメータを提供して、アプリケーションページの状態を保持して、インストールや認可、GitHub Appの更新を受け付けた後にその状態に戻れるようにできます。 たとえば、`state`を使ってインストールをユーザあるいはアカウントと関連づけることができます。 -To preserve a state, add it to the installation URL: +状態を保持するには、インストールURLに追加します。 `{% data variables.product.oauth_host_code %}/apps//installations/new?state=AB12t` diff --git a/translations/ja-JP/content/developers/apps/making-a-github-app-public-or-private.md b/translations/ja-JP/content/developers/apps/making-a-github-app-public-or-private.md index 3d32c8b321..5e1bd5a3b1 100644 --- a/translations/ja-JP/content/developers/apps/making-a-github-app-public-or-private.md +++ b/translations/ja-JP/content/developers/apps/making-a-github-app-public-or-private.md @@ -1,5 +1,5 @@ --- -title: Making a GitHub App public or private +title: GitHub Appをパブリックまたはプライベートにする intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps/ @@ -13,24 +13,24 @@ versions: github-ae: '*' --- -For authentication information, see "[Authenticating with GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)." +認証の情報については「[GitHub Appでの認証](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)」を参照してください。 -### Public installation flow +### パブリックのインストールフロー -Public installation flows have a landing page where users begin the installation flow. This link is provided in the "Public link" field when setting up your GitHub App. For more information, see "[Installing GitHub Apps](/apps/installing-github-apps/)." +パブリックのインストールフローには、ユーザがインストールフローを開始するためのランディングページがあります。 このリンクは、GitHub Appをセットアップする際に「Public link（パブリックリンク）」フィールドに提供されます。 詳しい情報については「[GitHub Appのインストール](/apps/installing-github-apps/)」を参照してください。 -### Private installation flow +### プライベートのインストールフロー -Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private, or internal, GitHub Apps can only be installed on the user or organization account of the owner. +プライベートインストールフローを利用すれば、GitHub Appのオーナーだけがそのアプリケーションをインストールできます。 そのGitHub Appに関する限定的な情報はパブリックなページに存在しますが、**インストール**ボタンはOrganizationの管理者もしくはGitHub Appが個人のアカウントによって所有されている場合はそのユーザアカウントからのみ利用できます。 プライベート、もしくはインターナルのGitHub Appは、オーナーのユーザ、もしくはオーナーのOrganizationアカウントにのみインストールできます。 -### Changing who can install your GitHub App +### GitHub Appをインストールできるユーザの変更 -To change who can install the GitHub App: +GitHub Appをインストールできるユーザを変更するには以下のようにします。 {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -3. Select the GitHub App whose installation option you want to change. ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png) +3. インストールオプションを変更したいGitHub Appを選択してください。 ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. Depending on the installation option of your GitHub App, click either **Make public** or **Make internal**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png) -6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App internal**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. GitHub Appのインストールオプションに応じて、**Make public（パブリックにする）**もしくは**Make internal（インターナルにする）**をクリックしてください。 ![GitHub Appのインストールオプションを変更するボタン](/assets/images/github-apps/github_apps_make_public.png) +6. GitHub Appのインストールオプションに応じて、**Yes, make this GitHub App public（はい、このGitHub Appをパブリックにしてください）**もしくは**Yes, make this GitHub App internal（はい、このGitHub Appをインターナルにしてください）**をクリックしてください。 ![インストールオプションの変更の確認ボタン](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/ja-JP/content/developers/apps/managing-github-apps.md b/translations/ja-JP/content/developers/apps/managing-github-apps.md index fb3b9c3934..a13a774b14 100644 --- a/translations/ja-JP/content/developers/apps/managing-github-apps.md +++ b/translations/ja-JP/content/developers/apps/managing-github-apps.md @@ -1,6 +1,6 @@ --- -title: Managing GitHub Apps -intro: 'After you create and register a GitHub App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.' +title: GitHub Appの管理 +intro: 'GitHub Appを作成して登録した後、そのアプリケーションを変更したり、権限を変更したり、所有権を移譲したり、アプリケーションを削除したりできます。' mapTopic: true redirect_from: - /apps/building-integrations/managing-github-apps/ diff --git a/translations/ja-JP/content/developers/apps/managing-oauth-apps.md b/translations/ja-JP/content/developers/apps/managing-oauth-apps.md index e1bf769ded..56c2cc3d31 100644 --- a/translations/ja-JP/content/developers/apps/managing-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/managing-oauth-apps.md @@ -1,6 +1,6 @@ --- -title: Managing OAuth Apps -intro: 'After you create and register an OAuth App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.' +title: OAuth Appの管理 +intro: 'OAuth Appを作成して登録した後、そのアプリケーションを変更したり、権限を変更したり、所有権を移譲したり、アプリケーションを削除したりできます。' mapTopic: true redirect_from: - /apps/building-integrations/managing-oauth-apps/ diff --git a/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 0c3349fd79..9164c407bf 100644 --- a/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/ja-JP/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -1,6 +1,6 @@ --- -title: Migrating OAuth Apps to GitHub Apps -intro: 'Learn about the advantages of migrating your {% data variables.product.prodname_oauth_app %} to a {% data variables.product.prodname_github_app %} and how to migrate an {% data variables.product.prodname_oauth_app %} that isn''t listed on {% data variables.product.prodname_marketplace %}.' +title: OAuth AppからGitHub Appへの移行 +intro: '{% data variables.product.prodname_oauth_app %}を{% data variables.product.prodname_github_app %}へ移行することの利点と、{% data variables.product.prodname_marketplace %}にリストされていない{% data variables.product.prodname_oauth_app %}の移行方法について学んでください。' redirect_from: - /apps/migrating-oauth-apps-to-github-apps versions: @@ -10,92 +10,92 @@ versions: --- -This article provides guidelines for existing integrators who are considering migrating from an OAuth App to a GitHub App. +この記事は、OAuth AppをGitHub Appに移行することを検討している既存のインテグレーターにガイドラインを提供します。 -### Reasons for switching to GitHub Apps +### GitHub Appに切り替える理由 -[GitHub Apps](/apps/) are the officially recommended way to integrate with GitHub because they offer many advantages over a pure OAuth-based integration: +[GitHub App](/apps/)は、GitHubとの統合のための公式に推奨されている方法です。これは、純粋なOAuthベースのインテグレーションと比べて多くの利点を提供するためです。 -- [Fine-grained permissions](/apps/differences-between-apps/#requesting-permission-levels-for-resources) target the specific information a GitHub App can access, allowing the app to be more widely used by people and organizations with security policies than OAuth Apps, which cannot be limited by permissions. -- [Short-lived tokens](/apps/differences-between-apps/#token-based-identification) provide a more secure authentication method over OAuth tokens. An OAuth token does not expire until the person who authorized the OAuth App revokes the token. GitHub Apps use tokens that expire quickly, creating a much smaller window of time for compromised tokens to be in use. -- [Built-in, centralized webhooks](/apps/differences-between-apps/#webhooks) receive events for all repositories and organizations the app can access. Conversely, OAuth Apps require configuring a webhook for each repository and organization accessible to the user. -- [Bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts) don't consume a {% data variables.product.product_name %} seat and remain installed even when the person who initially installed the app leaves the organization. -- Built-in support for OAuth is still available to GitHub Apps using [user-to-server endpoints](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). -- Dedicated [API rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) for bot accounts scale with your integration. -- Repository owners can [install GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) on organization repositories. If a GitHub App's configuration has permissions that request an organization's resources, the org owner must approve the installation. -- Open Source community support is available through [Octokit libraries](/rest/overview/libraries) and other frameworks such as [Probot](https://probot.github.io/). -- Integrators building GitHub Apps have opportunities to adopt earlier access to APIs. +- GitHub Appがアクセスできる特定の情報をターゲットにする[詳細な権限](/apps/differences-between-apps/#requesting-permission-levels-for-resources)。権限で制限できないOAuth App以上のセキュリティポリシーの下で、より広範囲なユーザやOrganizationにアプリケーションを利用してもらうことができる。 +- [短時間有効なトークン](/apps/differences-between-apps/#token-based-identification)によって、OAuthトークンよりもセキュアな認証方式を提供できる。 OAuthトークンは、OAuth Appを認可したユーザがトークンを取り消すまで、期限切れにならない。 GitHub Appsは素早く期限切れになるトークンを使用し、侵害されたトークンが利用される時間枠を小さくできる。 +- [ビルトインの集中型webhook](/apps/differences-between-apps/#webhooks)は、アプリケーションがアクセスできるすべてのリポジトリとOrganizationに対するイベントを受信する。 逆に、OAuth AppはユーザがアクセスできるそれぞれのリポジトリとOrganizationに対してwebhookを設定する必要がある。 +- [ボットアカウント](/apps/differences-between-apps/#machine-vs-bot-accounts)は{% data variables.product.product_name %}のシートを消費せず、最初にアプリケーションをインストールしたユーザがOrganizationを離れてもインストールされたままにしておける。 +- OAuthのビルトインサポートは、[ユーザからサーバーへのエンドポイント](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)を使って、GitHub Appでも利用できる。 +- ボットアカウント専用の[APIレート制限](/apps/building-github-apps/understanding-rate-limits-for-github-apps/)は、インテグレーションとともにスケールする。 +- リポジトリの所有者は、Organizationのリポジトリに[GitHub Appをインストール](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps)できる。 GitHub Appの設定にOrganizationのリソースをリクエストする権限があれば、Organizaitionのオーナーはそのインストールを承認しなければならない。 +- [ Octokitライブラリ](/rest/overview/libraries)や、[Robot](https://probot.github.io/)のような他のフレームワークを通じてオープンソースコミュニティのサポートがある。 +- GitHub Appを構築するインテグレーターは、APIへの早期アクセスを採用する機会がある。 -### Converting an OAuth App to a GitHub App +### OAuth AppからGitHub Appへの変換 -These guidelines assume that you have a registered OAuth App{% if currentVersion == "free-pro-team@latest" %} that may or may not be listed in GitHub Marketplace{% endif %}. At a high level, you'll need to follow these steps: +以下のガイドラインは、{% if currentVersion == "free-pro-team@latest" %}GitHub Marketplaceにリストされている、あるいはされていない{% endif %}登録済みのOAuth Appがあることを前提としています。 高いレベルでは、以下のステップに従う必要があります。 -1. [Review the available API endpoints for GitHub Apps](#review-the-available-api-endpoints-for-github-apps) -1. [Design to stay within API rate limits](#design-to-stay-within-api-rate-limits) -1. [Register a new GitHub App](#register-a-new-github-app) -1. [Determine the permissions your app requires](#determine-the-permissions-your-app-requires) -1. [Subscribe to webhooks](#subscribe-to-webhooks) -1. [Understand the different methods of authentication](#understand-the-different-methods-of-authentication) -1. [Direct users to install your GitHub App on repositories](#direct-users-to-install-your-github-app-on-repositories) -1. [Remove any unnecessary repository hooks](#remove-any-unnecessary-repository-hooks) -1. [Encourage users to revoke access to your OAuth app](#encourage-users-to-revoke-access-to-your-oauth-app) +1. [GitHub Appで利用できるAPIエンドポイントのレビュー](#review-the-available-api-endpoints-for-github-apps) +1. [APIレート制限内に留まるための設計](#design-to-stay-within-api-rate-limits) +1. [新しいGitHub Appの登録](#register-a-new-github-app) +1. [アプリケーションが必要とする権限の決定](#determine-the-permissions-your-app-requires) +1. [webhookのサブスクライブ](#subscribe-to-webhooks) +1. [様々な認証方法の理解](#understand-the-different-methods-of-authentication) +1. [リポジトリにGitHub Appをインストールするようにユーザに指示](#direct-users-to-install-your-github-app-on-repositories) +1. [不必要なリポジトリフックの削除](#remove-any-unnecessary-repository-hooks) +1. [OAuth Appへのアクセスの取り消しをユーザに促す](#encourage-users-to-revoke-access-to-your-oauth-app) -#### Review the available API endpoints for GitHub Apps +#### GitHub Appで利用できるAPIエンドポイントのレビュー -While the majority of [REST API](/rest) endpoints and [GraphQL](/graphql) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/rest/overview/endpoints-available-for-github-apps) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. +[REST API](/rest)エンドポイントと[GraphQL](/graphql)クエリの大部分は、今日GitHub Appから利用できますが、まだいくつかのエンドポイントは有効にする過程にあります。 [利用可能なRESTエンドポイント](/rest/overview/endpoints-available-for-github-apps)をレビューして、必要なエンドポイントがGitHub Appと互換性があることを確認してください。 GitHub Appで利用できるAPIエンドポイントの中には、ユーザの代わりにアプリケーションが動作できるようにするものがあることに注意してください。 GitHub Appがユーザとして認証されるようにするエンドポイントのリストについては、「[ユーザからサーバーへのリクエスト](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)」を参照してください。 -We recommend reviewing the list of API endpoints you need as early as possible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_app %}s. +必要なAPIエンドポイントのリストのレビューは、できるだけ早く行うことをおすすめします。 まだ{% data variables.product.prodname_github_app %}から利用できないエンドポイントで必要なものがある場合は、サポートにお知らせください。 -#### Design to stay within API rate limits +#### APIレート制限内に留まるための設計 -GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/rest#conditional-requests) or consolidate requests by using the [GraphQL API V4](/graphql). +GitHub Appは[レート制限に対するスライディングルール](/apps/building-github-apps/understanding-rate-limits-for-github-apps/)を利用します。これは、Organization中のリポジトリ及びユーザ数に基づいて増加できます。 また、GitHub Appは[GraphQL V4](/graphql)を利用することで、[条件リクエスト](/rest#conditional-requests)あるいは統合リクエストを利用することもできます。 -#### Register a new GitHub App +#### 新しいGitHub Appの登録 -Once you've decided to make the switch to Github Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). +GitHub Appへ切り替えすることを決めたら、[新しいGitHub Appを作成](/apps/building-github-apps/)しなければなりません。 -#### Determine the permissions your app requires +#### アプリケーションが必要とする権限の決定 -When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/rest/reference/permissions-required-for-github-apps)" for a list of the permissions needed for each endpoint available to GitHub Apps. +GitHub Appを登録する際には、アプリケーションのコードが使用する各エンドポイントが必要とする権限を選択しなければなりません。 GitHub Appで利用できる各エンドポイントが必要とする権限のリストについては「[GitHub Appの権限](/rest/reference/permissions-required-for-github-apps)」を参照してください。 -In your GitHub App's settings, you can specify whether your app needs `No Access`, `Read-only`, or `Read & Write` access for each permission type. The fine-grained permissions allow your app to gain targeted access to the subset of data you need. We recommend specifying the smallest set of permissions possible that provides the desired functionality. +GitHub Appの設定で、アプリケーションがそれぞれの権限の種類について`No Access`、`Read-only`、`Read & Write`アクセスを必要とするかを指定できます。 詳細な権限を使用することで、アプリケーションは必要なデータのサブセットにターゲットを絞ってアクセスできるようになります。 必要な機能を提供する、可能な限り最小の権限セットを指定することをおすすめします。 -#### Subscribe to webhooks +#### webhookのサブスクライブ -After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a Github App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. +新しいGitHub Appを作成し、その権限を選択したら、サブスクライブさせたいwebhookイベントを選択できます。 webhookをサブスクライブする方法を学ぶには、「[GitHub Appの権限の編集](/apps/managing-github-apps/editing-a-github-app-s-permissions/)」を参照してください。 -#### Understand the different methods of authentication +#### 様々な認証方法の理解 -GitHub Apps primarily use a token-based authentication that expires after a short amount of time, providing more security than an OAuth token that does not expire. It’s important to understand the different methods of authentication available to you and when you need to use them: +GitHub Appは、短時間で期限切れとなるトークンベースの認証を主に利用し、期限切れにならないOAuthトークンよりも高いセキュリティを提供します。 利用可能な様々な認証方法と、それらをいつ使う必要があるかを理解しておくことが重要です。 -* A **JSON Web Token (JWT)** [authenticates as the GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app). For example, you can authenticate with a **JWT** to fetch application installation details or exchange the **JWT** for an **installation access token**. -* An **installation access token** [authenticates as a specific installation of your GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) (also called server-to-server requests). For example, you can authenticate with an **installation access token** to open an issue or provide feedback on a pull request. -* An **OAuth access token** can [authenticate as a user of your GitHub App](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site) (also called user-to-server requests). For example, you can use an OAuth access token to authenticate as a user when a GitHub App needs to verify a user’s identity or act on a user’s behalf. +* **JSON Web Token (JWT)**は[GitHub Appとして認証](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)されます。 たとえば、**JWT**で認証を受けてアプリケーションのインストールの詳細をフェッチしたり、**JWT**を**インストールアクセストークン**と交換したりできます。 +* **インストールアクセストークン**は、[GitHub Appの特待のインストールとして認証](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)されます（これはサーバーからサーバーへのリクエストとも呼ばれます）。 たとえば、**インストールアクセストークン**で認証を受けて、Issueをオープンしたり、Pull Requestにフィードバックを提供したりできます。 +* **OAuthアクセストークン** は[GitHub Appのユーザとして認証](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)を受けることができます（ユーザからサーバーへのリクエストとも呼ばれます）。 たとえば、GitHub Appがユーザのアイデンティティを検証したり、ユーザの代わりに振る舞わなければならない場合に、OAuthアクセストークンを使ってユーザとして認証を受けることができます。 -The most common scenario is to authenticate as a specific installation using an **installation access token**. +最も一般的なシナリオは、**インストールアクセストークン**を使って特定のインストールとして認証を受けることです。 -#### Direct users to install your GitHub App on repositories +#### リポジトリにGitHub Appをインストールするようにユーザに指示 -Once you've made the transition from an OAuth App to a GitHub App, you will need to let users know that the GitHub App is available to install. For example, you can include an installation link for the GitHub App in a call-to-action banner inside your application. To ease the transition, you can use query parameters to identify the user or organization account that is going through the installation flow for your GitHub App and pre-select any repositories your OAuth App had access to. This allows users to easily install your GitHub App on repositories you already have access to. +OAuth AppからGitHub Appへの移行をしたら、GitHub Appがインストールできるようになったことをユーザに知らせなければなりません。 たとえば、アプリケーション中の行動喚起のバナーに、GitHub Appのインストールリンクを含めることができます。 移行を容易にするために、GitHub Appのインストールフローを通じて存在する、ユーザもしくはOrganizationアカウントを特定するクエリパラメータを使い、OAuth Appがアクセスできた任意のリポジトリを事前選択しておけます。 こうすることで、ユーザはすでにアクセスできるリポジトリにGitHub Appを容易にインストールできるようになります。 -##### Query parameters +##### クエリパラメータ -| 名前 | 説明 | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `suggested_target_id` | **Required**: ID of the user or organization that is installing your GitHub App. | -| `repository_ids[]` | Array of repository IDs. If omitted, we select all repositories. The maximum number of repositories that can be pre-selected is 100. | +| 名前 | 説明 | +| --------------------- | -------------------------------------------------------------- | +| `suggested_target_id` | **必須**: GitHub AppをインストールしようとしているユーザもしくはOrganizationのID。 | +| `repository_ids[]` | リポジトリIDの配列。 省略された場合、すべてのリポジトリが選択されます。 事前選択できるリポジトリ数は、最大で100です。 | -##### Example URL +##### URLの例 ``` https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID ``` -You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) and [List organization repositories](/rest/reference/repos#list-organization-repositories) endpoints. +`YOUR_APP_NAME`をGitHub Appの名前で、`ID_OF_USER_OR_ORG`をターゲットユーザもしくはOrganizationのIDで置き換え、最大で100個のリポジトリID（`REPO_A_ID`及び`REPO_B_ID`）を含めなければなりません。 OAuth Appがアクセスできるリポジトリのリストを取得するには、[認証されたユーザのためのリポジトリのリスト](/rest/reference/repos#list-repositories-for-the-authenticated-user)及び[Organizationのリポジトリのリスト](/rest/reference/repos#list-organization-repositories)エンドポイントを使ってください。 -#### Remove any unnecessary repository hooks +#### 不必要なリポジトリフックの削除 -Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) on those repositories that were created by your OAuth App. +GitHub Appがリポジトリにインストールされたら、従来のOAuth Appによって作成された不要なwebhookを削除する必要があります。 どちらのアプリケーションも同じリポジトリにインストールされていると、ユーザにとっては機能が重複するかもしれません。 webhookを削除するには、`repositories_added`アクションの[`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories)を待ち受け、それらのリポジトリ上にOAuth Appによって作成された[リポジトリwebhookを削除](/rest/reference/repos#delete-a-repository-webhook)できます。 -#### Encourage users to revoke access to your OAuth app +#### OAuth Appへのアクセスの取り消しをユーザに促す -As your GitHub App installation base grows, consider encouraging your users to [revoke access](/articles/authorizing-oauth-apps/) to the legacy OAuth integration. +GitHub Appのインストールベースが増大してきたら、ユーザに従来のOAuthインテグレーションへの[アクセスを取り消す](/articles/authorizing-oauth-apps/)ように促すことを検討してください。 diff --git a/translations/ja-JP/content/developers/apps/modifying-a-github-app.md b/translations/ja-JP/content/developers/apps/modifying-a-github-app.md index f4352682e8..cbc36af6e7 100644 --- a/translations/ja-JP/content/developers/apps/modifying-a-github-app.md +++ b/translations/ja-JP/content/developers/apps/modifying-a-github-app.md @@ -1,5 +1,5 @@ --- -title: Modifying a GitHub App +title: GitHub Appの変更 intro: '{% data reusables.shortdesc.modifying_github_apps %}' redirect_from: - /apps/building-integrations/managing-github-apps/modifying-a-github-app/ @@ -14,5 +14,5 @@ versions: {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. In "Basic information", modify the GitHub App information that you'd like to change. ![Basic information section for your GitHub App](/assets/images/github-apps/github_apps_basic_information.png) -6. [**Save changes**] をクリックします。 ![Button to save changes for your GitHub App](/assets/images/github-apps/github_apps_save_changes.png) +5. 「Basic information（基本情報）」で、修正したいGitHub Appの情報を変更してください。 ![GitHub Appの基本情報セクション](/assets/images/github-apps/github_apps_basic_information.png) +6. [**Save changes（変更を保存）**] をクリックします。 ![GitHub Appの変更保存ボタン](/assets/images/github-apps/github_apps_save_changes.png) diff --git a/translations/ja-JP/content/developers/apps/modifying-an-oauth-app.md b/translations/ja-JP/content/developers/apps/modifying-an-oauth-app.md index 5463c5f995..8424bd15fe 100644 --- a/translations/ja-JP/content/developers/apps/modifying-an-oauth-app.md +++ b/translations/ja-JP/content/developers/apps/modifying-an-oauth-app.md @@ -1,5 +1,5 @@ --- -title: Modifying an OAuth App +title: OAuth Appの変更 intro: '{% data reusables.shortdesc.modifying_oauth_apps %}' redirect_from: - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app/ @@ -14,6 +14,5 @@ versions: {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.oauth_apps %} {% data reusables.user-settings.modify_oauth_app %} -1. Modify the -{% data variables.product.prodname_oauth_app %} information that you'd like to change. +1. 修正したい{% data variables.product.prodname_oauth_app %}の情報を変更してください。 {% data reusables.user-settings.update_oauth_app %} diff --git a/translations/ja-JP/content/developers/apps/rate-limits-for-github-apps.md b/translations/ja-JP/content/developers/apps/rate-limits-for-github-apps.md index 31607e2e14..49d2daa6f4 100644 --- a/translations/ja-JP/content/developers/apps/rate-limits-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/rate-limits-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: Rate limits for GitHub Apps +title: GitHub Appのレート制限 intro: '{% data reusables.shortdesc.rate_limits_github_apps %}' redirect_from: - /early-access/integrations/rate-limits/ @@ -12,13 +12,13 @@ versions: github-ae: '*' --- -### Server-to-server requests +### さーばーからサーバーへのリクエスト {% if currentVersion == "free-pro-team@latest" %} -Different server-to-server request rate limits apply to {% data variables.product.prodname_github_app %}s if the app is installed on organizations or repositories owned by a {% data variables.product.prodname_ghe_cloud %} account. +{% data variables.product.prodname_ghe_cloud %}アカウントが所有するOrganizationもしくはリポジトリにアプリエーションがインストールされた場合、様々なサーバーからサーバーへのリクエストのレート制限が{% data variables.product.prodname_github_app %}に適用されます。 -#### Normal server-to-server rate limits +#### 通常のサーバーからサーバーへのレート制限 {% endif %} @@ -26,32 +26,32 @@ Different server-to-server request rate limits apply to {% data variables.produc {% if currentVersion == "free-pro-team@latest" %} -#### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits +#### {% data variables.product.prodname_ghe_cloud %}のサーバーからサーバーへのレート制限 -{% data variables.product.prodname_github_app %}s that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +{% data variables.product.prodname_ghe_cloud %}アカウントが所有するOrganizationもしくはリポジトリにインストールされ、サーバーからサーバーへのリクエストを発行する{% data variables.product.prodname_github_app %}は、1時間あたり15,000リクエストのレート制限を持ちます。 {% endif %} -### User-to-server requests +### ユーザからサーバーへのリクエスト -{% data variables.product.prodname_github_app %}s can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests. +{% data variables.product.prodname_github_app %}[ユーザの代わりに](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps)動作し、ユーザからサーバーへのリクエストを発行することができます。 {% if currentVersion == "free-pro-team@latest" %} -Different user-to-server request rate limits apply to {% data variables.product.prodname_github_app %}s if the app is installed on organizations or repositories owned by a {% data variables.product.prodname_ghe_cloud %} account and the authenticated user also belongs to the same {% data variables.product.prodname_ghe_cloud %} account. +アプリケーションが{% data variables.product.prodname_ghe_cloud %}アカウントが所有するOrganiozationもしくはリポジトリにインストールされ、認証されたユーザが同じ{% data variables.product.prodname_ghe_cloud %}アカウントに属しているなら、様々なユーザからサーバーへのリクエストのレート制限が{% data variables.product.prodname_github_app %}に適用されます。 -#### Normal user-to-server rate limits +#### 通常のユーザからサーバーへのレート制限 {% endif %} -User-to-server requests are rate limited at 5,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's{% if currentVersion == "github-ae@latest" %} token{% else %} username and password{% endif %} share the same quota of 5,000 requests per hour for that user. +ユーザからサーバーへのリクエストは、1時間あたり及び認証されたユーザごとに5,000リクエストのレート制限を受けます。 そのユーザが認可したすべてのOAuthアプリケーション、そのユーザが所有する個人アクセストークン、そのユーザの{% if currentVersion == "github-ae@latest" %}トークン{% else %}ユーザ名及びパスワード{% endif %}で認証されたリクエストは、そのユーザに対する1時間あたり5,000リクエストの同じクォータを共有します。 {% if currentVersion == "free-pro-team@latest" %} -#### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits +#### {% data variables.product.prodname_ghe_cloud %}のユーザからサーバーへのレート制限 -When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. +ユーザが{% data variables.product.prodname_ghe_cloud %}アカウントに属している場合、同じ{% data variables.product.prodname_ghe_cloud %}アカウントに所有されているリソースへのユーザからサーバーへのリクエストは、1時間あたり認証されたユーザごとに15,000リクエストのレート制限を受けます。 そのユーザが認可したすべてのOAuthアプリケーション、そのユーザが所有する個人アクセストークン、そのユーザのユーザ名及びパスワードで認証された{% data variables.product.prodname_ghe_cloud %}リクエストは、そのユーザに対する1時間あたり5,000リクエストの同じクォータを共有します。 {% endif %} -For more detailed information about rate limits, see "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" for REST API and "[Resource limitations](/graphql/overview/resource-limitations)" for GraphQL API. +レート制限に関する詳細な情報については、REST APIについては「[レート制限](/rest/overview/resources-in-the-rest-api#rate-limiting)」を、GraphQL APIについては「[リソース制限](/graphql/overview/resource-limitations)」を参照してください。 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 8d6e4c0d5d..e7a5814f24 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 @@ -1,6 +1,6 @@ --- -title: Refreshing user-to-server access tokens -intro: 'To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens.' +title: '　ユーザからサーバーへのアクセストークンの更新' +intro: '定期的なトークンのローテーションを強制し、侵害されたトークンの影響を抑えるために、ユーザアクセストークンの期限を利用するように{% data variables.product.prodname_github_app %}を設定できます。' redirect_from: - /apps/building-github-apps/refreshing-user-to-server-access-tokens versions: @@ -13,28 +13,28 @@ versions: {% data reusables.pre-release-program.expiring-user-access-tokens-beta %} -### About expiring user access tokens +### ユーザアクセストークンの期限切れについて -To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens. For more information on making user-to-server requests, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +定期的なトークンのローテーションを強制し、侵害されたトークンの影響を抑えるために、ユーザアクセストークンの期限を利用するように{% data variables.product.prodname_github_app %}を設定できます。 ユーザからサーバーへのリクエストの発行に関する詳しい情報については、「[GitHub Appのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。 -Expiring user tokens expire after 8 hours. When you receive a new user-to-server access token, the response will also contain a refresh token, which can be exchanged for a new user token and refresh token. Refresh tokens are valid for 6 months. +期限切れになるユーザトークンは、8時間で期限切れになります。 新しいユーザからサーバーへのアクセストークンを受信すると、レスポンスにはリフレッシュトークンも含まれます。このリフレッシュトークンは、新しいユーザトークン及びリフレッシュトークンと交換できます。 リフレッシュトークンは、6ヶ月間有効です。 -### Renewing a user token with a refresh token +### リフレッシュトークンでのユーザトークンの更新 -To renew an expiring user-to-server access token, you can exchange the `refresh_token` for a new access token and `refresh_token`. +期限切れになるユーザからサーバーへのアクセストークンを更新するには、`refresh_token`を新しいアクセストークン及び`refresh_token`と交換できます。 `POST https://github.com/login/oauth/access_token` -This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)." +このコールバックリクエストは、新しいアクセストークンと新しいリフレッシュトークンを送信してきます。 このコールバックリクエストは、一時的な`code`をアクセストークンと交換するために使うOAuthのリクエストに似ています。 詳しい情報については「[GitHub Appsのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)」及び「[認証の基本](/rest/guides/basics-of-authentication#providing-a-callback)」を参照してください。 #### パラメータ -| 名前 | 種類 | 説明 | -| --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `refresh_token` | `string` | **Required.** The token generated when the {% data variables.product.prodname_github_app %} owner enables expiring tokens and issues a new user access token. | -| `grant_type` | `string` | **Required.** Value must be `refresh_token` (required by the OAuth specification). | -| `client_id` | `string` | **Required.** The client ID for your {% data variables.product.prodname_github_app %}. | -| `client_secret` | `string` | **Required.** The client secret for your {% data variables.product.prodname_github_app %}. | +| 名前 | 種類 | 説明 | +| --------------- | -------- | ---------------------------------------------------------------------------------------------------------------- | +| `refresh_token` | `string` | **必須。** {% data variables.product.prodname_github_app %}のオーナーが期限切れするトークンを有効化し、新しいユーザアクセストークンを発行したときに生成されるトークン。 | +| `grant_type` | `string` | **必須。** 値は`refresh_token`でなければならない（OAuthの仕様で必須）。 | +| `client_id` | `string` | **必須。** {% data variables.product.prodname_github_app %}のクライアントID。 | +| `client_secret` | `string` | **必須。**{% data variables.product.prodname_github_app %}のクライアントシークレット。 | #### レスポンス @@ -48,25 +48,25 @@ This callback request will send you a new access token and a new refresh token. "token_type": "bearer" } ``` -### Configuring expiring user tokens for an existing GitHub App +### 既存のGitHub Appに対する期限切れするユーザトークンの設定。 -You can enable or disable expiring user-to-server authorization tokens from your {% data variables.product.prodname_github_app %} settings. +期限切れするユーザからサーバーへの認可トークンの有効化や無効化は、{% data variables.product.prodname_github_app %}設定から行えます。 {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -4. Click **Edit** next to your chosen {% data variables.product.prodname_github_app %}. ![Settings to edit a GitHub App](/assets/images/github-apps/edit-test-app.png) -5. In the left sidebar, click **Beta Features**. ![Beta Features menu option](/assets/images/github-apps/beta-features-option.png) -6. Next to "User-to-server token expiration", click **Opt-in** or **Opt-out**. This setting may take a couple of seconds to apply. +4. 選択した{% data variables.product.prodname_github_app %}の隣の**Edit（編集）**をクリックしてください。 ![GitHub Appを編集する設定](/assets/images/github-apps/edit-test-app.png) +5. 左のサイドバーで、**Beta Features（ベータの機能）**をクリックしてください。 ![ベータ機能のメニューオプション](/assets/images/github-apps/beta-features-option.png) +6. 「User-to-server token expiration（ユーザからサーバーへのトークンの有効期限）」の隣の**Opt-in（オプトイン）**もしくは**Opt-out（オプトアウト）**をクリックしてください。 この設定が適用されるまで、数秒かかることがあります。 -### Opting out of expiring tokens for new GitHub Apps +### 新しいGitHub Appでの期限切れになるトークンのオプトアウト -When you create a new {% data variables.product.prodname_github_app %}, by default your app will use expiring user-to-server access tokens. +新しい{% data variables.product.prodname_github_app %}を作成する際には、デフォルトでそのアプリケーションは期限切れになるユーザからサーバーへのアクセストークンを使用します。 -If you want your app to use non-expiring user-to-server access tokens, you can deselect "Expire user authorization tokens" on the app settings page. +アプリケーションに期限切れにならないユーザからサーバーへのアクセストークンを使わせたい場合には、アプリケーションの設定ページで"Expire user authorization tokens（ユーザ認可トークンの期限切れ）"を選択を解除できます。 ![GitHub App のセットアップ中に期限付きユーザトークンをオプトインするオプション](/assets/images/github-apps/expire-user-tokens-selection.png) -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. +ユーザからサーバーへの認可トークンを使用する既存の{% data variables.product.prodname_github_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/)." +既存の{% data variables.product.prodname_github_app %}に対して期限切れになるユーザトークンを有効化するためには、8時間で期限切れになる新しいユーザトークンを再発行するためにOAuthフローを通じてユーザを送信し、リフレッシュトークンを使って新しいアクセストークンとリフレッシュトークンを取得するためのリクエストを発行する必要があります。 詳しい情報については「[GitHub Appのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。 diff --git a/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md b/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md index 1080d22f14..bbab98d9c1 100644 --- a/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ja-JP/content/developers/apps/scopes-for-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Scopes for OAuth Apps +title: OAuth Appのスコープ intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps/ @@ -11,20 +11,20 @@ versions: github-ae: '*' --- -When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form. +OAuth AppをGitHub上でセットアップする際には、要求されたスコープが認可フォーム上でユーザに表示されます。 {% note %} -**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +**ノート:** GitHub Appを構築しているなら、認可リクエストでスコープを提供する必要はありません。 このことに関する詳細については「[GitHub Appのユーザの特定と認可](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください、 {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -If your -{% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)." +{% data variables.product.prodname_oauth_app %}が +CLIツールなどであり、ブラウザにアクセスできないなら、アプリケーションの認可のためにユーザに対してスコープを指定する必要はありません。 詳しい情報については「[OAuth Appの認可](/developers/apps/authorizing-oauth-apps#device-flow)」を参照してください。 {% endif %} -Check headers to see what OAuth scopes you have, and what the API action accepts: +どのOAuthスコープを所有しているか、そしてAPIアクションが何を受け付けるかを知るには、ヘッダを確認してください。 ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I @@ -33,51 +33,52 @@ X-OAuth-Scopes: repo, user X-Accepted-OAuth-Scopes: user ``` -* `X-OAuth-Scopes` lists the scopes your token has authorized. -* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for. +* `X-OAuth-Scopes`はトークンが認可したスコープをリストします。 +* `X-Accepted-OAuth-Scopes`は、アクションがチェックするスコープをリストします。 -### Available scopes +### 利用できるスコープ -| 名前 | 説明 | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | -|  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | -|  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | -|  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} -| **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | -|  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | -|  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | -| **`admin:org`** | Fully manage the organization and its teams, projects, and memberships. | -|  `write:org` | Read and write access to organization membership, organization projects, and team membership. | -|  `read:org` | Read-only access to organization membership, organization projects, and team membership. | -| **`admin:public_key`** | Fully manage public keys. | -|  `write:public_key` | Create, list, and view details for public keys. | -|  `read:public_key` | List and view details for public keys. | -| **`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user. | -| **`gist`** | Grants write access to gists. | -| **`通知`** | Grants:
* read access to a user's notifications
* mark as read access to threads
* watch and unwatch access to a repository, and
* read, write, and delete access to thread subscriptions. | -| **`ユーザ`** | Grants read/write access to profile info only. Note that this scope includes `user:email` and `user:follow`. | -|  `read:user` | Grants access to read a user's profile data. | -|  `user:email` | Grants read access to a user's email addresses. | -|  `user:follow` | Grants access to follow or unfollow other users. | -| **`delete_repo`** | Grants access to delete adminable repositories. | -| **`write:discussion`** | Allows read and write access for team discussions. | -|  `read:discussion` | Allows read access for team discussions.{% if currentVersion == "free-pro-team@latest" %} -| **`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)". | -| **`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)". | -| **`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "[Deleting packages](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} -| **`admin:gpg_key`** | Fully manage GPG keys. | -|  `write:gpg_key` | Create, list, and view details for GPG keys. | -|  `read:gpg_key` | List and view details for GPG keys.{% if currentVersion == "free-pro-team@latest" %} -| **`ワークフロー`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes, see https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token for details.{% endif %} +| 名前 | 説明 | +| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **`(スコープなし)`** | パブリックな情報への読み取りのみのアクセスを許可します（パブリックなユーザのプロフィール情報、パブリックリポジトリの情報、Gist）。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| **`site_admin`** | サイト管理者に[{% data variables.product.prodname_ghe_server %}の管理APIエンドポイント](/rest/reference/enterprise-admin)へのアクセスを許可します。{% endif %} +| **`repo`** | プライベート及びパブリックなリポジトリへの完全なアクセスを許可します。 これにはコード、コミットのステータス、リポジトリ及びOrganizationのプロジェクト、招待、コラボレータ、Teamのメンバーシップの追加、デプロイメントのステータス、パブリック及びプライベートのリポジトリとOrganizationのためのリポジトリwebhookが含まれます。 また、ユーザプロジェクトを管理する機能も許可します。 | +|  `repo:status` | パブリック及びプライベートのリポジトリのコミットステータスの読み書きアクセスを許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザあるいはサービスにプライベートリポジトリのコミットステータスへのアクセスを許可したい場合のみです。 | +|  `repo_deployment` | パブリック及びプライベートのリポジトリに対する[デプロイメントステータス](/rest/reference/repos#deployments)へのアクセスを許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*他のユーザあるいはサービスにデプロイメントステータスへのアクセスを許可したい場合のみです。 | +|  `public_repo` | アクセスをパブリックリポジトリのみに制限します。 これには、コード、コミットステータス、リポジトリプロジェクト、コラボレータ、パブリックリポジトリ及びOrganizationのデプロイメントステータスへの読み書きアクセスが含まれます。 パブリックリポジトリにStarするためにも必要です。 | +|  `repo:invite` | リポジトリでのコラボレーションへの招待の承認／拒否を許可します。 このスコープが必要になるのは、コードへのアクセスを許可*することなく*招待へのアクセスをユーザあるいはサービスに許可する場合のみです。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +|  `security_events` | 許可:
[{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)中のセキュリティイベントへの読み書きアクセス。
[{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)中のセキュリティイベントへの読み書きアクセス。{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)中のセキュリティイベントへの読み書きアクセスを許可します。{% endif %} +| **`admin:repo_hook`** | パブリック及びプライベートリポジトリのリポジトリフックへの読み書き、ping、削除アクセスを許可します。 `repo`及び`public_repo`スコープは、リポジトリフックを含むリポジトリへの完全なアクセスを許可します。 アクセスをリポジトリフックのみに限定するには、`admin:repo_hook`スコープを使ってください。 | +|  `write:repo_hook` | パブリック及びプライベートリポジトリ内のフックへの読み書き及びpingアクセスを許可します。 | +|  `read:repo_hook` | パブリック及びプライベートリポジトリ内のフックへの読み取り及びpingアクセスを許可します。 | +| **`admin:org`** | OrganizationとそのTeam、プロジェクト、メンバーシップを完全に管理できます。 | +|  `write:org` | Organizationのメンバーシップ、Organizationのプロジェクト、Teamのメンバーシップへの読み書きアクセス。 | +|  `read:org` | Organizationのメンバーシップ、Organizationのプロジェクト、Teamのメンバーシップへの読み取りのみのアクセス。 | +| **`admin:public_key`** | 公開鍵を完全に管理できます。 | +|  `write:public_key` | 公開鍵の作成、リスト、詳細の表示。 | +|  `read:public_key` | 公開鍵のリストと詳細の表示。 | +| **`admin:org_hook`** | Organizationフックへの読み書き、ping、削除アクセスを許可します。 **ノート:** OAuthトークンがこれらのアクションを行えるのは、OAuth Appが作成したOrganizationフックに対してのみです。 個人アクセストークンがこれらのアクションを行えるのは、ユーザが作成したOrganizationフックに対してのみです。 | +| **`gist`** | Gistへの書き込みアクセスを許可します。 | +| **`notifications`** | 許可するアクセス:
* ユーザの通知に対する読み取りアクセス
* スレッドへの既読アクセス
* リポジトリへのWatch及びWatch解除のアクセス
* スレッドのサブスクリプションに対する読み書き及び削除アクセス。 | +| **`user`** | プロフィール情報にのみ読み書きアクセスを許可します。 このスコープには`user:email`と`user:follow`が含まれることに注意してください。 | +|  `read:user` | ユーザのプロフィールデータへの読み取りアクセスを許可します。 | +|  `user:email` | ユーザのメールアドレスへの読み取りアクセスを許可します。 | +|  `user:follow` | 他のユーザのフォローあるいはフォロー解除のアクセスを許可します。 | +| **`delete_repo`** | 管理可能なリポジトリの削除アクセスを許可します。 | +| **`write:discussion`** | Teamのディスカッションの読み書きアクセスを許可します。 | +|  `read:discussion` | Teamのディスカッションの読み取りアクセスを許可します。{% if currentVersion == "free-pro-team@latest" %} +| **`write:packages`** | {% data variables.product.prodname_registry %}でのパッケージのアップロードあるいは公開のアクセスを許可します。 詳しい情報については「[パッケージの公開](/github/managing-packages-with-github-packages/publishing-a-package)」を参照してください。 | +| **`read:packages`** | {% data variables.product.prodname_registry %}からのパッケージのダウンロードあるいはインストールのアクセスを許可します。 詳しい情報については「[パッケージのインストール](/github/managing-packages-with-github-packages/installing-a-package)」を参照してください。 | +| **`delete:packages`** | {% data variables.product.prodname_registry %}からのパッケージの削除アクセスを許可します。 詳しい情報については「[パッケージの削除](/github/managing-packages-with-github-packages/deleting-a-package)」を参照してください。{% endif %} +| **`admin:gpg_key`** | GPGキーを完全に管理できます。 | +|  `write:gpg_key` | GPGキーの作成、リスト、詳細の表示ができます。 | +|  `read:gpg_key` | GPGキーのリストと詳細の表示ができます。{% if currentVersion == "free-pro-team@latest" %} +| **`workflow`** | {% data variables.product.prodname_actions %}のワークフローファイルの追加と更新機能を許可します。 同じリポジトリ内の他のブランチに同じファイル（パスと内容が同じ）が存在する場合、ワークフローファイルはこのスコープがなくてもコミットできます。 ワークフローファイルは異なるスコープのセットを持ちうる`GITHUB_TOKEN`を公開できます。詳細については https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token を参照してください。{% endif %} {% note %} -**Note:** Your OAuth App can request the scopes in the initial redirection. You can specify multiple scopes by separating them with a space: +**ノート:**OAuth Appは最初のリダイレクトでスコープをリクエストできます。 スコープは、空白で区切って複数指定できます。 https://github.com/login/oauth/authorize? client_id=...& @@ -85,16 +86,16 @@ X-Accepted-OAuth-Scopes: user {% endnote %} -### Requested scopes and granted scopes +### リクエストされたスコープと許可されたスコープ -The `scope` attribute lists scopes attached to the token that were granted by the user. Normally, these scopes will be identical to what you requested. However, users can edit their scopes, effectively granting your application less access than you originally requested. Also, users can edit token scopes after the OAuth flow is completed. You should be aware of this possibility and adjust your application's behavior accordingly. +`scope`属性は、トークンに添付された、ユーザが許可したスコープをリストします。 通常、これらのスコープはリクエストされたものと同じになります。 しかし、ユーザはスコープを編集でき、実質的にアプリケーションに対して元々リクエストされたよりも少ないアクセスだけを許可できます。 また、ユーザはOAuthフローが完了した後にトークンのスコープを編集することもできます。 この可能性を認識しておき、対応してアプリケーションの動作を調整しなければなりません。 -It's important to handle error cases where a user chooses to grant you less access than you originally requested. For example, applications can warn or otherwise communicate with their users that they will see reduced functionality or be unable to perform some actions. +元々リクエストされたよりも少ないアクセスをユーザが許可した場合のエラーケースを処理することは重要です。 たとえば、アプリケーションはユーザに対し、機能が低下したり、行えないアクションがでてくることを警告したり、知らせたりすることができます。 -Also, applications can always send users back through the flow again to get additional permission, but don’t forget that users can always say no. +また、アプリケーションはいつでもユーザをフローに戻して追加の権限を得ようとすることができますが、ユーザは常に拒否できることを忘れないようにしてください。 -Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which provides tips on handling modifiable token scopes. +変更できるトークンのスコープの扱いに関するヒントが提供亜sレテイル、[認証の基礎ガイド](/guides/basics-of-authentication/)を参照してください。 -### Normalized scopes +### 正規化されたスコープ -When requesting multiple scopes, the token is saved with a normalized list of scopes, discarding those that are implicitly included by another requested scope. For example, requesting `user,gist,user:email` will result in a token with `user` and `gist` scopes only since the access granted with `user:email` scope is included in the `user` scope. +複数のスコープがリクエストされた場合、トークンは正規化されたスコープのリストとともに保存され、リクエストされた他のスコープに暗黙のうちに含まれているスコープは破棄されます。 たとえば`user,gist,user:email`をリクエストすると、トークンには`user`と`gist`スコープだけが含まれます。これは、`user:email`スコープで許可されるアクセスは`user`スコープに含まれているためです。 diff --git a/translations/ja-JP/content/developers/apps/setting-permissions-for-github-apps.md b/translations/ja-JP/content/developers/apps/setting-permissions-for-github-apps.md index 222dfb1728..5d8ce09ff5 100644 --- a/translations/ja-JP/content/developers/apps/setting-permissions-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/setting-permissions-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: Setting permissions for GitHub Apps +title: GitHub Appの権限の設定 intro: '{% data reusables.shortdesc.permissions_github_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps/ @@ -11,10 +11,10 @@ versions: github-ae: '*' --- -When you create a GitHub App, you can select the permissions it needs to access end user data. Permissions can also be added and removed. For more information, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." +GitHub Appを作成する際に、そのアプリケーションがエンドユーザのデータにアクセスするために必要な権限を選択できます。 権限は、追加することも削除することもできます。 詳しい情報については「[GitHub Appの権限の編集](/apps/managing-github-apps/editing-a-github-app-s-permissions/)」を参照してください。 ### メタデータ権限 -By default, GitHub Apps have `Read-only` access to metadata endpoints. Metadata is a collection of read-only endpoints that provide general information about resources that the authorized installation can access. +デフォルトでは、GitHub Appはメタデータエンドポイントに`Read-only`のアクセスを持ちます。 メタデータは、読み取りのみのエンドポイントの集合で、認可されたインストールからアクセスできるリソースに関する一般的な情報を提供します。 -{% data reusables.apps.metadata-permissions %} For a list of metadata endpoints, see "[Metadata permissions](/rest/reference/permissions-required-for-github-apps#metadata-permissions)." +{% data reusables.apps.metadata-permissions %} メタデータエンドポイントのリストについては、「[メタデータの権限](/rest/reference/permissions-required-for-github-apps#metadata-permissions)」を参照してください。 diff --git a/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index 568bf41543..25e7b8ee8d 100644 --- a/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/ja-JP/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -1,6 +1,6 @@ --- -title: Setting up your development environment to create a GitHub App -intro: 'Learn the foundations for extending and building new {% data variables.product.prodname_github_apps %}.' +title: GitHub Appを作成するための開発環境のセットアップ +intro: '新しい{% data variables.product.prodname_github_apps %}を拡張して構築するための基礎を学んでください。' redirect_from: - /apps/quickstart-guides/setting-up-your-development-environment versions: @@ -12,142 +12,142 @@ versions: ### はじめに -This guide will walk through the steps needed to configure a GitHub App and run it on a server. GitHub Apps require some setup steps to manage webhook events and connect the app registration on GitHub to your code. The app in this guide serves as a foundation that you can use to extend and build new GitHub Apps. +このガイドは、GitHub Appを設定してサーバー上で実行するために必要なステップを案内します。 GitHub Appには、webhookイベントを管理し、GitHub上のアプリケーションの登録をコードに接続するためのセットアップのステップが必要です。 このガイドのアプリケーションは、拡張して新しいGitHub Appを構築するための基盤の役目を果たします。 -By the end of this guide you'll have registered a GitHub App and set up a web server to receive webhook events. You'll learn how to use a tool called Smee to capture webhook payloads and forward them to your local development environment. The template app you'll configure in this section won't do anything special yet, but it will serve as a framework you can use to start writing app code using the API or complete other [quickstart guides](/apps/quickstart-guides/). {% if currentVersion == "free-pro-team@latest" %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %} +このガイドを終えれば、GitHub Appを登録し、webhookイベントを受信するためのWebサーバーをセットアップできます。 Smeeというツールを使ってwebhookペイロードをキャプチャし、ローカルの開発環境に転送する方法を学びます。 このセクションで設定するテンプレートのアプリケーションは特別なことはしませんが、APIを使ってアプリケーションコードを書きはじめたり、他の[クイックスタートガイド](/apps/quickstart-guides/)を完了させたりするために使用できるフレームワークとして働きます。 {% if currentVersion == "free-pro-team@latest" %} アプリケーションの成功例は、[GitHub Marketplace](https://github.com/marketplace)や[Works with GitHub](https://github.com/works-with)で調べることができます。{% endif %} -After completing this project you will understand how to authenticate as a GitHub App and an installation, and how those authentication methods are different. +このプロジェクトを完了すると、GitHub App及びインストールとして認証を受ける方法と、それらの認証方法の違いを理解できます。 -Here are the steps you'll take to configure the template GitHub App: +以下のステップで、テンプレートのGitHub Appを設定できます。 -1. [Start a new Smee channel](#step-1-start-a-new-smee-channel) -1. [Register a new GitHub App](#step-2-register-a-new-github-app) -1. [Save your private key and App ID](#step-3-save-your-private-key-and-app-id) -1. [Prepare the runtime environment](#step-4-prepare-the-runtime-environment) -1. [Review the GitHub App template code](#step-5-review-the-github-app-template-code) -1. [Start the server](#step-6-start-the-server) -1. [Install the app on your account](#step-7-install-the-app-on-your-account) +1. [新しいSmeeチャンネルの開始](#step-1-start-a-new-smee-channel) +1. [新しいGitHub Appの登録](#step-2-register-a-new-github-app) +1. [秘密鍵とApp IDの保存](#step-3-save-your-private-key-and-app-id) +1. [ランタイム環境の準備](#step-4-prepare-the-runtime-environment) +1. [GitHub Appのテンプレートコードのレビュー](#step-5-review-the-github-app-template-code) +1. [サーバーの起動](#step-6-start-the-server) +1. [アカウントへのアプリケーションのインストール](#step-7-install-the-app-on-your-account) {% data reusables.apps.app-ruby-guides %} ### 必要な環境 -You may find it helpful to have a basic understanding of the following: +以下に関する基本的な理解があると役立つでしょう。 * [GitHub Apps](/apps/about-apps) * [webhook](/webhooks) -* [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/rest) +* [プログラミング言語のRuby](https://www.ruby-lang.org/en/) +* [REST API](/rest) * [Sinatra](http://sinatrarb.com/) -But you can follow along at any experience level. We'll link out to information you need along the way! +とはいえ、経験のレベルにかかわらず見ていくことはできます。 その過程で必要な情報にはリンクしていきます！ -Before you begin, you'll need to clone the repository with the template code used in this quickstart. Open your Terminal app and find a directory where you'd like to store the code. Run this command to clone the [GitHub App template](https://github.com/github-developer/github-app-template) repository: +始める前に、このクイックスタートで使われるテンプレートコードのリポジトリをクローンする必要があります。 ターミナルアプリケーションを開いて、コードを保存したいディレクトリに移動してください。 以下のコマンドを実行して、[GitHub Appテンプレート](https://github.com/github-developer/github-app-template)リポジトリをクローンしてください。 ```shell $ git clone https://github.com/github-developer/github-app-template.git ``` -### ステップ 1. Start a new Smee channel +### ステップ 1. 新しいSmeeチャンネルの開始 -To help GitHub send webhooks to your local machine without exposing it to the internet, you can use a tool called Smee. First, go to https://smee.io and click **Start a new channel**. If you're already comfortable with other tools that expose your local machine to the internet like [ngrok](https://dashboard.ngrok.com/get-started) or [localtunnel](https://localtunnel.github.io/www/), feel free to use those. +ローカルのマシンをインターネットに公開することなく、GitHubがwebhookを送信するのを支援するために、Smeeというツールが利用できます。 まず https://smee.io にアクセスして、**Start a new channel**をクリックしてください。 [ngrok](https://dashboard.ngrok.com/get-started)や[localtunnel](https://localtunnel.github.io/www/)のような、ローカルマシンをインターネットに公開してくれる他のツールに慣れているなら、それらを使ってもかまいません。 ![The Smee new channel button](/assets/images/smee-new-channel.png) -Starting a new Smee channel creates a unique domain where GitHub can send webhook payloads. You'll need to know this domain for the next step. Here is an example of a unique domain at `https://smee.io/qrfeVRbFbffd6vD`: +新しいSmeeのチャンネルを起動すると、GitHubがwebhookペイロードを送信できるユニークなドメインが作成されます。 次のステップで必要なので、このドメインを知っておく必要があります。 ユニークなドメインの例は`https://smee.io/qrfeVRbFbffd6vD`といったものです。 ![A Smee unique channel](/assets/images/smee-unique-domain.png) -Next, go back to the Terminal and follow these steps to run the Smee command-line interface (CLI) client: +次に、ターミナルに戻って以下のステップに従い、Smeeのコマンドラインインターフェース（CLI）クライアントを実行してください。 {% note %} -**Note:** The following steps are slightly different than the "Use the CLI" instructions you'll see in your Smee channel page. You do **not** need to follow the "Use the Node.js client" or "Using Probot's built-in support" instructions. +**ノート:** 以下のステップは、Smeeチャンネルのページに表示される"Use the CLI"の指示とはやや異なっています。 "Use the Node.js client"あるいは"Using Probot's built-in support"の指示に従う必要は**ありません**。 {% endnote %} -1. Install the client: +1. クライアントをインストールします。 ```shell $ npm install --global smee-client ``` -2. Run the client (replacing `https://smee.io/qrfeVRbFbffd6vD` with your own domain): +2. クライアントを実行します（`https://smee.io/qrfeVRbFbffd6vD`を自分のドメインで置き換えてください）。 ```shell $ smee --url https://smee.io/qrfeVRbFbffd6vD --path /event_handler --port 3000 ``` - You should see output like the following: + 以下のように出力されるでしょう。 ```shell Forwarding https://smee.io/qrfeVRbFbffd6vD to http://127.0.0.1:3000/event_handler Connected https://smee.io/qrfeVRbFbffd6vD ``` -The `smee --url ` command tells Smee to forward all webhook events received by the Smee channel to the Smee client running on your computer. The `--path /event_handler` option forwards events to the `/event_handler` route, which we'll cover in a [later section](#step-5-review-the-github-app-template-code). The `--port 3000` option specifies port 3000, which is the port your server will be listening to. Using Smee, your machine does not need to be open to the public internet to receive webhooks from GitHub. You can also open that Smee URL in your browser to inspect webhook payloads as they come in. +`smee --url `というコマンドは、Smeeに対してSmeeのチャンネルが受信したすべてのwebhookイベントを、コンピューター上で動作するSmeeクライアントに転送するように指示しています。 `--path /event_handler`オプションは、イベントを`/event_handler`というルートに転送します。このルートについては[後のセクション](#step-5-review-the-github-app-template-code)で取り上げます。 `--port 3000`オプションはポート3000を指定しており、サーバーはこのポートで待ち受けます。 Smeeを使えば、GitHubからのwebhookを受信するためにあなたのマシンがパブリックなインターネットに対してオープンである必要はありません。 また、ブラウザでSmeeのURLを開いて、受信したwebhookのペイロードを調べることもできます。 -We recommend leaving this Terminal window open and keeping Smee connected while you complete the rest of the steps in this guide. Although you _can_ disconnect and reconnect the Smee client without losing your unique domain (unlike ngrok), you may find it easier to leave it connected and do other command-line tasks in a different Terminal window. +このターミナルのウィンドウは開いたままにしておき、このガイドの残りのステップを完了させるまでの間、Smeeに接続したままにしておくことをおすすめします。 ユニークなドメインを失うことなくSmeeのクライアントの接続を切って、接続しなおすことも_できます_が（ngrokとは違って）、これは接続したままにしておいて、別のターミナルウィンドウで他のコマンドラインのタスクを行うようにするほうが簡単でしょう。 -### ステップ 2. Register a new GitHub App +### ステップ 2. 新しいGitHub Appの登録 -If you don't yet have a GitHub account, now is a [great time to join](https://github.com/join). Don't forget to verify your email before continuing! To register a new app, visit the [app settings page](https://github.com/settings/apps) in your GitHub profile, and click **New GitHub App**. +まだGitHubのアカウントを持っていないなら、ここが[参加する時です](https://github.com/join)。 続行する前にメールを確認するのを忘れないようにしてください! 新しいアプリケーションを登録するには、自分のGitHubのプロフィール内の[アプリケーション設定ペー委](https://github.com/settings/apps)にアクセスし、**New GitHub App**をクリックしてください。 ![GitHub website, showing the **New App**](/assets/images/new-app.png) -You'll see a form where you can enter details about your app. See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" for general information about the fields on this page. For the purposes of this guide, you'll need to enter specific data in a few fields: +表示されるフォームで、アプリケーションの詳細を入力できます。 このページのフィールドに関する一般的な情報については「[GitHub Appの作成](/apps/building-github-apps/creating-a-github-app/)」を参照してください。 このガイドについては、いくつかのフィールドに特定のデータを入力する必要があります。 {% note %} -**Note:** You can always update these settings later to point to a hosted server. +**ノート:** これらの設定はいつでも更新して、ホストされたサーバーを指すようにできます。 {% endnote %} -* For the "Homepage URL", use the domain issued by Smee. 例: +* "Homepage URL（ホームページのURL）"には、Smeeが発行したドメインを使用してください。 例: ![Form with Smee domain filled in for homepage URL](/assets/images/homepage-url.png) -* For the "Webhook URL", again use the domain issued by Smee. 例: +* "Webhook URL（webhookのURL）"には、やはりSmeeが発行したドメインを使ってください。 例: ![Form with Smee domain filled in for webhook URL](/assets/images/webhook-url.png) -* For the "Webhook secret", create a password to secure your webhook endpoints. This should be something that only you (and GitHub, via this form) know. The secret is important because you will be receiving payloads from the public internet, and you'll use this secret to verify the webhook sender. Note that the GitHub App settings say the webhook secret is optional, which is true in most cases, but for the template app code to work, you must set a webhook secret. +* "Webhook secret（webhookのシークレット）"には、webhookのエンドポイントを保護するパスワードを作成してください。 これは、あなた（そしてこのフォームを介してGitHub）だけが知っているものにするべきです。 パブリックなインターネットから受信したペイロードで、webhookの送信者を検証するのに使われるので、このシークレットは重要です。 GitHub Appの設定ではこのwebhookのシークレットはオプションとなっており、これはほとんどの場合正しいですが、このテンプレートのアプリケーションコードを動作させるためには、webhookのシークレットは設定しなければなりません。 ![Form with webhook secret filled in](/assets/images/webhook-secret.png) -* On the Permissions & Webhooks page, you can specify a set of permissions for your app, which determines how much data your app has access to. Leave this page with its default values. If you decide to extend this template app, you can update these permissions later. +* Permissions & Webhooks（権限とwebhook）ページでは、アプリケーションの権限セットを指定できます。これによって、アプリケーションがどれだけのデータにアクセスできるかが決まります。 このページはデフォルト値のままにしておいてください。 このテンプレートアプリケーションを拡張することにしたら、後でこれらの権限を更新できます。 -* At the bottom of the Permissions & Webhooks page, specify whether this is a private app or a public app. This refers to who can install it: just you, or anyone in the world? For now, leave the app as private by selecting **Only on this account**. +* Permissions & Webhooks（権限とwebhook）ページの下部で、これがプライベートのアプリケーションなのか、パブリックのアプリケーションなのかを指定してください。 これは、アプリケーションを誰がインストールできるのか、すなわちあなただけなのか、誰でもできるのかを指します。 この時点では、**Only on this account（このアカウントのみ）**を選択して、アプリケーションをプライベートのままにしておいてください。 ![GitHub App privacy](/assets/images/create_app.png) -Click **Create GitHub App** to create your app! +**Create GitHub App（GitHub Appの作成）**をクリックして、アプリケーションを作成してください! -### ステップ 3. Save your private key and App ID +### ステップ 3. 秘密鍵とApp IDの保存 -After you create your app, you'll be taken back to the [app settings page](https://github.com/settings/apps). You have two more things to do here: +アプリケーションを作成すると、[アプリケーションの設定ページ](https://github.com/settings/apps)に戻されます。 ここで行うことがあと2つあります。 -* **Generate a private key for your app.** This is necessary to authenticate your app later on. Scroll down on the page and click **Generate a private key**. Save the resulting PEM file (called something like _`app-name`_-_`date`_-private-key.pem) in a directory where you can find it again. +* **アプリケーションの秘密鍵の生成。**これは後でアプリケーションを認証するために必要です。 ページをスクロールダウンして、**Generate a private key（秘密鍵の生成）**をクリックしてください。 生成されたPEMファイル（_`app-name`_-_`date`_-private-key.pemというような名前）を、また見つけられるディレクトリに保存してください。 ![The private key generation dialog](/assets/images/private_key.png) -* **Note the app ID GitHub has assigned your app.** You'll need this to prepare your runtime environment. +* **GitHubがアプリケーションに割り当てたApp IDを記録してください。**これは、ランタイム環境を準備するのに必要になります。 Your app's ID number -### ステップ 4. Prepare the runtime environment +### ステップ 4. ランタイム環境の準備 -To keep your information secure, we recommend putting all your app-related secrets in your computer's memory where your app can find them, rather than putting them directly in your code. A handy development tool called [dotenv](https://github.com/bkeepers/dotenv) loads project-specific environment variables from a `.env` file to `ENV`. Never check your `.env` file into GitHub. This is a local file that stores sensitive information that you don't want on the public internet. The `.env` file is already included in the repository's [`.gitignore`](/articles/ignoring-files/) file to prevent that. +情報を保護するために、アプリケーションに関するすべてのシークレットは、直接コードに埋め込むのではなく、アプリケーションが見つけることができるコンピュータのメモリ中に置いておくことをおすすめします。 [dotenv](https://github.com/bkeepers/dotenv)という便利な開発ツールは、プロジェクトに固有の変数を`.env`ファイルから`ENV`にロードしてくれます。 `.env`ファイルは、決してGitHubにチェックインしないでください。 これは、パブリックなインターネット上にさらしたくない機密情報を保存するローカルファイルです。 そうならないようにするために、すでに`.env`はリポジトリの[`.gitignore`](/articles/ignoring-files/)に含まれています。 -The template code you downloaded in the [Prerequisites section](#prerequisites) already has an example file called `.env-example`. Rename the example file from `.env-example` to `.env` or create a copy of the `.env-example` file called `.env`. You haven't installed dotenv yet, but you will install it later in this quickstart when you run `bundle install`. **Note:** Quickstarts that reference the steps in this guide may include additional environment variables in the `.env-example` file. Reference the quickstart guide for the project you've cloned on GitHub for guidance setting those additional environment variables. +[必要な環境のセクション](#prerequisites)でダウンロードしたテンプレートコードには、`.env-example`というサンプルのファイルが用意されています。 このサンプルのファイルの名前を`.env-example`から`.env`に変更するか、`.env`というファイルを`.env-example`をコピーして作成してください。 まだdotenvはインストールしていませんが、このクイックスタートで後に`bundle install`を実行する際にインストールします。 **ノート:**このガイドのステップを参照するクイックスタートは、`.env-example`に追加の環境変数を含んでいることがあります。 それらの追加の環境変数を設定するためのガイダンスについては、GitHub上でクローンしたプロジェクトのクイックスタートガイドを参照してください。 -You need to add these variables to the `.env` file: +以下の変数を`.env`ファイルに追加しなければなりません。 -* _`GITHUB_PRIVATE_KEY`_: Add the private key you [generated and saved previously](#step-3-save-your-private-key-and-app-id). Open the `.pem` file with a text editor or use the command line to display the contents of the file: `cat path/to/your/private-key.pem`. Copy the entire contents of the file as the value of `GITHUB_PRIVATE_KEY` in your `.env` file. **Note:** Because the PEM file is more than one line you'll need to add quotes around the value like the example below. -* _`GITHUB_APP_IDENTIFIER`_: Use the app ID you noted in the previous section. -* _`GITHUB_WEBHOOK_SECRET`_: Add your webhook secret. +* _`GITHUB_PRIVATE_KEY`_: [以前に生成して保存した](#step-3-save-your-private-key-and-app-id)秘密鍵を追加してください。 テキストエディタで`.pem`ファイルを開くか、コマンドラインから`cat path/to/your/private-key.pem`としてファイルの内容を表示してください。 ファイルの内容全体を`.env`ファイル中の`GITHUB_PRIVATE_KEY`の値としてコピーしてください。 **ノート:** PEMファイルには複数行があるので、以下の例のように引用符を値の周りに追加しなければなりません。 +* _`GITHUB_APP_IDENTIFIER`_: 前セクションで記録したApp IDを使ってください。 +* _`GITHUB_WEBHOOK_SECRET`_: webhookのシークレットを追加してください。 -Here is an example `.env` file: +以下は`.env`ファイルの例です。 ``` PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY----- @@ -159,68 +159,68 @@ GITHUB_APP_IDENTIFIER=12345 GITHUB_WEBHOOK_SECRET=your webhook secret ``` -### ステップ 5. Review the GitHub App template code +### ステップ 5. GitHub Appのテンプレートコードのレビュー -The template app code already contains some code that every GitHub App will need. This sections walks you through the code that already exists in the GitHub App template. There aren't any steps that you need to complete in this section. If you're already familiar with the template code, you can skip ahead to "[Step 6. Start the server](#step-6-start-the-server)." +テンプレートのアプリケーションコードには、すべてのGitHub Appが必要とする多少のコードがすでに含まれています。 このセクションでは、GitHub Appのテンプレートにすでにあるコードを見ていきます。 このセクションで完了しなければならないステップはありません。 テンプレートコードにすでに馴染んでいるなら、「[ステップ 6 サーバーの起動](#step-6-start-the-server)」までスキップできます。 -Open up the `template_server.rb` file in your favorite text editor. You'll see comments throughout this file that provide additional context for the template code. We recommend reading those comments carefully and even adding your own comments to accompany new code you write. +好きなテキストエディタで`template_server.rb`ファイルを開いてください。 このファイルには、全体を通じてテンプレートコードの追加のコンテキストを提供するコメントがあります。 これらのコメントを注意深く読んで、さらには作成する新しいコードに添えて独自のコメントを追加することをおすすめします。 -At the top of the file you'll see `set :port 3000`, which sets the port used when starting the web server to match the port you redirected your webhook payloads to in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." +ファイルの先頭には`set :port 3000`があります。これは、Webサーバーを起動するときに使われるポートを設定して、「[ステップ1 新しいSmeeチャンネルの開始](#step-1-start-a-new-smee-channel)"でwebhookのペイロードをリダイレクトしたポートと一致させます。 -The next code you'll see is the `class GHApp < Sintra::Application` declaration. You'll write all of the code for your GitHub App inside this class. +次に出てくるコードは`class GHApp < Sintra::Application`という宣言です。 GitHub Appのすべてのコードは、このクラスの中に書いていきます。 -Out of the box, the class in the template does the following things: -* [Read the environment variables](#read-the-environment-variables) -* [Turn on logging](#turn-on-logging) -* [Define a before filter](#define-a-before-filter) -* [Define the route handler](#define-a-route-handler) -* [Define the helper methods](#define-the-helper-methods) +そのままの状態では、テンプレート中のこのクラスは以下のことを行います。 +* [環境変数の読み取り](#read-the-environment-variables) +* [ロギングの有効化](#turn-on-logging) +* [ビフォアフィルタの定義](#define-a-before-filter) +* [ルートハンドラの定義](#define-a-route-handler) +* [ヘルパーメソッドの定義](#define-the-helper-methods) -#### Read the environment variables +#### 環境変数の読み取り -The first thing that this class does is read the three environment variables you set in "[Step 4. Prepare the runtime environment](#step-4-prepare-the-runtime-environment)" and store them in variables to use later: +このクラスが最初に行うのは、「[ステップ4 ランタイム環境の準備](#step-4-prepare-the-runtime-environment)」で設定した3つの環境変数を読み取り、後で使うために変数に設定することです。 ``` ruby -# Expects that the private key in PEM format. Converts the newlines +#秘密鍵はPEMフォーマットであることを期待する。 改行を変換する。 PRIVATE_KEY = OpenSSL::PKey::RSA.new(ENV['GITHUB_PRIVATE_KEY'].gsub('\n', "\n")) -# Your registered app must have a secret set. The secret is used to verify +# 登録されたアプリケーションにはシークレットが設定されていなければならない。 このシークレットは検証に使われる # that webhooks are sent by GitHub. WEBHOOK_SECRET = ENV['GITHUB_WEBHOOK_SECRET'] -# The GitHub App's identifier (type integer) set when registering an app. +# アプリケーションの登録時に設定されたGitHub Appの識別子(型はinteger)。 APP_IDENTIFIER = ENV['GITHUB_APP_IDENTIFIER'] ``` -#### Turn on logging +#### ロギングの有効化 -Next is a code block that enables logging during development, which is the default environment in Sinatra. This code turns on logging at the `DEBUG` level to show useful output in the Terminal while you are developing the app: +次は、Sinatraにおけるデフォルトの環境である開発の間、ロギングを有効にするコードブロックです。 このコードは`DEBUG`レベルでロギングを有効化し、アプリケーションの開発の間、ターミナルに有益な出力を行います。 ``` ruby -# Turn on Sinatra's verbose logging during development +# Sinatraの詳細なロギングを開発の間有効にする configure :development do set :logging, Logger::DEBUG end ``` -#### Define a before filter +#### ビフォアフィルタの定義 -Sinatra uses [before filters](https://github.com/sinatra/sinatra#filters) that allow you to execute code before the route handler. The `before` block in the template calls four [helper methods](https://github.com/sinatra/sinatra#helpers). The template app defines those helper methods in a [later section](#define-the-helper-methods). +Sinatraは、ルートハンドラよりも先にコードを実行できるようにしてくれる[ビフォアフィルタ](https://github.com/sinatra/sinatra#filters)を使います。 テンプレート中の`before`ブロックは、4つの[ヘルパーメソッド](https://github.com/sinatra/sinatra#helpers)を呼びます。 このテンプレートアプリケーションでは、これらのヘルパーメソッドは[後のセクション](#define-the-helper-methods)で定義します。 ``` ruby -# Before each request to the `/event_handler` route +# `/event_handler`ルートへの各リクエストの前 before '/event_handler' do get_payload_request(request) verify_webhook_signature authenticate_app - # Authenticate the app installation in order to run API operations + # API操作を実行するために、アプリケーションのインストールを認証 authenticate_installation(@payload) end ``` -#### Define a route handler +#### ルートハンドラの定義 -An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. +テンプレートコードには、空のルートが含まれています。 このコードは、`/event_handler`ルートへのすべての`POST`リクエストを処理します。 このクイックスタートではこのイベントハンドラは書きませんが、このテンプレートアプリケーションの拡張方法の例については他の[クイックスタートガイド](/apps/quickstart-guides/)を参照してください。 ``` ruby post '/event_handler' do @@ -228,58 +228,58 @@ post '/event_handler' do end ``` -#### Define the helper methods +#### ヘルパーメソッドの定義 -The helper methods in this template do most of the heavy lifting. Four helper methods are defined in this section of the code. +このテンプレートのヘルパーメソッドは、最も難しい処理のほとんどを行います。 コードのこのセクションでは、4つのヘルパーメソッドが定義されています。 -##### Handling the webhook payload +##### webhookペイロードの処理 -The first method `get_payload_request` captures the webhook payload and converts it to JSON format, which makes accessing the payload's data much easier. +最初のメソッドである`get_payload_request`は、webhookのペイロードをキャプチャしてJSON形式に変換し、ペイロードのデータにアクセスしやすくします。 -##### Verifying the webhook signature +##### webhookの署名の検証 -The second method `verify_webhook_signature` performs verification of the webhook signature to ensure that GitHub generated the event. To learn more about the code in the `verify_webhook_signature` helper method, see "[Securing your webhooks](/webhooks/securing/)." If the webhooks are secure, this method will log all incoming payloads to your Terminal. The logger code is helpful in verifying your web server is working but you can always remove it later. +2番目のメソッドの`verify_webhook_signature`は、webhookの署名を検証して、そのイベントがGitHubが生成したものであることを確認します。 `verify_webhook_signature`ヘルパーメソッド中のコードについてさらに学ぶには、「[webhookをセキュアにする](/webhooks/securing/)」を参照してください。 webhookがセキュアであれば、このメソッドは受け取ったペイロードのすべてをターミナルに出力します。 ロガーのコードはWebサーバーが動作していることを確認するのに役立ちますが、後でいつでも取り除くことができます。 -##### Authenticating as a GitHub App +##### GitHub Appとしての認証 -To make API calls, you'll be using the [Octokit library](http://octokit.github.io/octokit.rb/). Doing anything interesting with this library will require you, or rather your app, to authenticate. GitHub Apps have two methods of authentication: +API呼び出しを行うには、[Octokitライブラリ](http://octokit.github.io/octokit.rb/)を使います。 このライブラリで何か面白いことを行うには、あなた、あるいはむしろアプリケーションが認証を受ける必要があります。 GitHub Appには2つの認証方法があります。 -- Authenticating as a GitHub App using a [JSON Web Token (JWT)](https://jwt.io/introduction). -- Authenticating as a specific installation of a GitHub App using an installation access token. +- [JSON Webトークン (JWT)](https://jwt.io/introduction)を使ってGitHub Appとして認証を受ける。 +- インストールアクセストークンを使って特定のGitHub Appのインストールとして認証を受ける。 -You'll learn about authenticating as an installation in the [next section](#authenticating-as-an-installation). +インストールとしての認証については[次のセクション](#authenticating-as-an-installation)で学びます。 -[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) lets you do a couple of things: +[GitHub Appとして認証を受ける](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)と、いくつかのことができるようになります。 - * You can retrieve high-level management information about your GitHub App. + * GitHub Appに関する高レベルの管理情報を取得できます。 * アプリケーションのインストールのため、アクセストークンをリクエストできます。 -For example, you would authenticate as a GitHub App to retrieve a list of the accounts (organization and personal) that have installed your app. But this authentication method doesn't allow you to do much with the API. To access a repository's data and perform operations on behalf of the installation, you need to authenticate as an installation. To do that, you'll need to authenticate as a GitHub App first to request an installation access token. +たとえば、GitHub Appとして認証を受けて、そのアプリケーションをインストールしたアカウント（Organization及び個人）のリストを取得できます。 しかし、この認証方法ではAPIを使って多くのことは行えません。 インストールの代わりにリポジトリのデータにアクセスして操作を行うには、インストールとして認証を受けなければなりません。 そのためには、まずGitHub Appとして認証を受けて、インストールアクセストークンをリクエストしなければなりません。 -Before you can use the Octokit.rb library to make API calls, you'll need to initialize an [Octokit client](http://octokit.github.io/octokit.rb/Octokit/Client.html) authenticated as a GitHub App. The `authenticate_app` helper method does just that! +API呼び出しを発行するためにOctokit.rbライブラリを使えるようになる前に、GitHub Appとして認証された[Octokit client](http://octokit.github.io/octokit.rb/Octokit/Client.html)を初期化しなければなりません。 `authenticate_app`ヘルパーメソッドがまさにそれを行ってくれます! ``` ruby -# Instantiate an Octokit client authenticated as a GitHub App. -# GitHub App authentication requires that you construct a -# JWT (https://jwt.io/introduction/) signed with the app's private key, -# so GitHub can be sure that it came from the app an not altered by -# a malicious third party. +# GitHub Appとして認証されたOctokitクライアントを初期化する。 +# GitHub Appの認証には、アプリケーションの秘密鍵で署名された +# JWT (https://jwt.io/introduction/)を構築して、それがアプリケーション +# から来ており、悪意あるサードパーティによって改変されていない +# ことをGitHubが確認できるようにする必要がある。 def authenticate_app payload = { - # The time that this JWT was issued, _i.e._ now. + # このJWTが発行された時刻。たとえば今。 iat: Time.now.to_i, - # JWT expiration time (10 minute maximum) + # JWTの有効期限(最大10分) exp: Time.now.to_i + (10 * 60), - # Your GitHub App's identifier number + # GitHub Appの識別番号 iss: APP_IDENTIFIER } - # Cryptographically sign the JWT + # 暗号的に JWTに署名 jwt = JWT.encode(payload, PRIVATE_KEY, 'RS256') - # Create the Octokit client, using the JWT as the auth token. + # JWTを認証トークンとして使ってOctokitクライアントを作成。 @app_client ||= Octokit::Client.new(bearer_token: jwt) end ``` @@ -311,7 +311,7 @@ With this method in place, each time your app receives a new webhook payload, it Now you're ready to start making API calls! -### ステップ 6. Start the server +### ステップ 6. サーバーの起動 Your app doesn't _do_ anything yet, but at this point, you can get it running on the server. @@ -353,7 +353,7 @@ Once the server is running, you can test it by going to `http://localhost:3000` This is good! Even though it's an error page, it's a _Sinatra_ error page, which means your app is connected to the server as expected. You're seeing this message because you haven't given the app anything else to show. -### ステップ 7. Install the app on your account +### ステップ 7. アカウントへのアプリケーションのインストール You can test that the server is listening to your app by triggering an event for it to receive. A simple event you can test is installing the app on your GitHub account, which should send the [`installation`](/webhooks/event-payloads/#installation) event. If the app receives it, you should see some output in the Terminal tab where you started `template_server.rb`. @@ -361,7 +361,7 @@ To install the app, visit the [app settings page](https://github.com/settings/ap You'll be asked whether to install the app on all repositories or selected repositories. If you don't want to install the app on _all_ of your repositories, that's okay! You may want to create a sandbox repository for testing purposes and install your app there. -App installation permissions +アプリケーションのインストール権限 After you click **Install**, look at the output in your Terminal. You should see something like this: @@ -420,9 +420,9 @@ Here are a few common problems and some suggested solutions. If you run into any * **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm installing the app on a repository on GitHub, but I don't see any output in the Terminal window where I'm running the server. - **A:** You may not be running the Smee client, or you may not have the correct Smee domain in your GitHub App settings. First check to make sure the Smee client is running in a Terminal tab. If that's not the problem, visit your [app settings page](https://github.com/settings/apps) and check the fields shown in "[Step 2. Register a new GitHub App](#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u ` command in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." + **A:** You may not be running the Smee client, or you may not have the correct Smee domain in your GitHub App settings. First check to make sure the Smee client is running in a Terminal tab. If that's not the problem, visit your [app settings page](https://github.com/settings/apps) and check the fields shown in "[Step 2. Register a new GitHub App](#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u ` command in "[Step 1. 新しいSmeeチャンネルの開始](#step-1-start-a-new-smee-channel)"でwebhookのペイロードをリダイレクトしたポートと一致させます。 -* **Q:** I'm getting seeing an `Octokit::NotFound` 404 error in my debug output: +* **Q:** I'm getting an `Octokit::NotFound` 404 error in my debug output: ``` 2018-12-06 15:00:56 - Octokit::NotFound - POST https://api.github.com/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token: ``` diff --git a/translations/ja-JP/content/developers/apps/using-the-github-api-in-your-app.md b/translations/ja-JP/content/developers/apps/using-the-github-api-in-your-app.md index 3b206f1718..226c8991f9 100644 --- a/translations/ja-JP/content/developers/apps/using-the-github-api-in-your-app.md +++ b/translations/ja-JP/content/developers/apps/using-the-github-api-in-your-app.md @@ -22,19 +22,19 @@ This project will walk you through the following: {% data reusables.apps.app-ruby-guides %} -Once you've worked through the steps, you'll be ready to develop other kinds of integrations using the full suite of GitHub APIs. {% if currentVersion == "free-pro-team@latest" %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %} +Once you've worked through the steps, you'll be ready to develop other kinds of integrations using the full suite of GitHub APIs. {% if currentVersion == "free-pro-team@latest" %} アプリケーションの成功例は、[GitHub Marketplace](https://github.com/marketplace)や[Works with GitHub](https://github.com/works-with)で調べることができます。{% endif %} ### 必要な環境 -You may find it helpful to have a basic understanding of the following: +以下に関する基本的な理解があると役立つでしょう。 * [GitHub Apps](/apps/about-apps) * [webhook](/webhooks) -* [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/rest) +* [プログラミング言語のRuby](https://www.ruby-lang.org/en/) +* [REST API](/rest) * [Sinatra](http://sinatrarb.com/) -But you can follow along at any experience level. We'll link out to information you need along the way! +とはいえ、経験のレベルにかかわらず見ていくことはできます。 その過程で必要な情報にはリンクしていきます！ Before you begin, you'll need to do the following: diff --git a/translations/ja-JP/content/developers/github-marketplace/about-github-marketplace.md b/translations/ja-JP/content/developers/github-marketplace/about-github-marketplace.md index a7fd7721f3..962a7f114f 100644 --- a/translations/ja-JP/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/ja-JP/content/developers/github-marketplace/about-github-marketplace.md @@ -1,6 +1,6 @@ --- title: GitHub Marketplaceについて -intro: '{% data variables.product.prodname_marketplace %}に参加する前に、アプリケーションをレビューに備えるための基本を学んでください。' +intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.' redirect_from: - /apps/marketplace/getting-started/ - /marketplace/getting-started @@ -14,52 +14,41 @@ versions: {% data reusables.actions.actions-not-verified %} -{% data variables.product.prodname_marketplace %}での{% data variables.product.prodname_actions %}の公開について学ぶには、「[GitHub Marketplaceでのactionsの公開](/actions/creating-actions/publishing-actions-in-github-marketplace)」を参照してください。 +To learn about publishing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." ### アプリケーション -{% data variables.product.prodname_marketplace %}において、検証済み及び未検証のアプリケーションをリストできます。 未検証のアプリケーションは、検証済みのアプリケーションに{% data variables.product.prodname_dotcom %}が求めるセキュリティ、テスト、検証のサイクルを通っていません。 +Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only listings that are verified by {% data variables.product.company_short %} can include paid plans. For more information, see "[About verified creators](/developers/github-marketplace/about-verified-creators)." -検証済みのアプリケーションは、{% data variables.product.prodname_marketplace %}で緑のバッジが付きます。 未検証のアプリケーションは、リストの隣に灰色のバッジが付き、無料のアプリケーションとしてのみ利用できます。 +If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)." -![検証済みの緑と未検証の灰色のバッジ](/assets/images/marketplace/marketplace_verified_badges.png) - -{% data variables.product.prodname_marketplace %}のアプリケーションの作成に関心があるものの、{% data variables.product.prodname_github_apps %}や{% data variables.product.prodname_oauth_app %}については初心者なら、「[アプリケーションの構築](/apps/)」を参照してください。 - -{% data reusables.marketplace.github_apps_preferred %}、{% data variables.product.prodname_marketplace %}ではOAuthと{% data variables.product.prodname_github_app %}をどちらもリストできます。 詳細については「[GitHubとOAuthのアプリケーションの違い](/apps/differences-between-apps/)」を参照してください。 OAuthから{% data variables.product.prodname_github_apps %}への切り替えについてさらに学ぶには、[OAuth Appsから{% data variables.product.prodname_github_app %}への移行](/apps/migrating-oauth-apps-to-github-apps/)を参照してください。 +{% data reusables.marketplace.github_apps_preferred %}、{% data variables.product.prodname_marketplace %}ではOAuthと{% data variables.product.prodname_github_app %}をどちらもリストできます。 For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_app %}s to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." {% data variables.product.prodname_marketplace %}に関する質問がある場合は、{% data variables.contact.contact_support %}に直接お問い合わせください。 -#### 未検証のアプリケーション +### Publishing an app to {% data variables.product.prodname_marketplace %} -未検証のアプリケーションは、「[{% data variables.product.prodname_marketplace %}でのアプリケーションのリストの要件](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)」を満たしていたり、「[セキュリティレビューのプロセス](/marketplace/getting-started/security-review-process/)」を通る必要はありません。 +When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: -{% data reusables.marketplace.unverified-apps %} 有料プランを公開すると、未検証のアプリケーションはサブミットできなくなります。 未検証のアプリケーションを公開する前には、有料プランを削除するか、有料プランをドラフトモードにしておかなければなりません。 +1. Review your app carefully to ensure that it will behave as expected in other repositories and that it follows best practice guidelines. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)." -{% data variables.product.prodname_marketplace %}で未検証のアプリケションをリストするには、「[{% data variables.product.prodname_marketplace %}上でリスト](/marketplace/listing-on-github-marketplace/)」を作成し、それを未検証のリストとしてサブミットするだけです。 +1. Add webhook events to the app to track user billing requests. For more information about the {% data variables.product.prodname_marketplace %} API, webhook events, and billing requests, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.launch-with-free %} +1. Create a draft {% data variables.product.prodname_marketplace %} listing. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -#### 検証済みアプリケーション +1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -すでにアプリケーションを構築済みで、{% data variables.product.prodname_marketplace %}に検証済みのリストをサブミットしたい場合には、以下から始めてください。 +1. Check whether your app meets the requirements for listing on {% data variables.product.prodname_marketplace %} as a free or a paid app. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." -1. [{% data variables.product.prodname_marketplace %}を始める](/marketplace/getting-started/)
要件、ガイドライン、アプリケーションのサブミットのプロセスについて学んでください。 +1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -1. [{% data variables.product.prodname_marketplace %} APIとのインテグレーション](/marketplace/integrating-with-the-github-marketplace-api/)
アプリケーションを{% data variables.product.prodname_marketplace %}でリストできるようにするには、{% data variables.product.prodname_marketplace %} APIとwebhookイベントを使って支払いフローをインテグレーションしなければなりません。 +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}, requesting verification if you want to sell the app. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." -1. [{% data variables.product.prodname_marketplace %}でのリスト](/marketplace/listing-on-github-marketplace/)
ドラフトの{% data variables.product.prodname_marketplace %}のリストを作成し、webhookを設定し、価格プランをセットアップします。 +An onboarding expert will contact you with any questions or further steps. For example, if you have added a paid plan, you will need to complete the verification process and complete financial onboarding. As soon as your listing is approved the app is published to {% data variables.product.prodname_marketplace %}. -1. [アプリケーションの販売](/marketplace/selling-your-app/)
価格プラン、支払いサイクル、アプリケーションに対する{% data variables.product.prodname_dotcom %}カラの支払いの受け取り方を学んでください。 +### Seeing how your app is performing -1. [{% data variables.product.prodname_marketplace %}のインサイト](/marketplace/github-marketplace-insights/)
{% data variables.product.prodname_marketplace %}でのアプリケーションのパフォーマンスを見てください。 {% data variables.product.prodname_dotcom %}が収集したメトリクスを使ってマーケティングキャンペーンを導き、{% data variables.product.prodname_marketplace %}で成功してください。 +You can access metrics and transactions for your listing. 詳しい情報については、以下を参照してください。 -1. [{% data variables.product.prodname_marketplace %}のトランザクション](/marketplace/github-marketplace-transactions/)
{% data variables.product.prodname_marketplace %}のリストからトランザクションデータをダウンロードして見てください。 - -### アプリケーションのレビュー - -弊社は、{% data variables.product.prodname_marketplace %}から提供されているアプリケーションが安全であり、十分テストされていることを確実にしたいと考えています。 {% data variables.product.prodname_marketplace %}のオンボーディングスペシャリストがアプリケーションをレビューし、すべての要件を満たしていることを確認します。 アプリケーションをサブミットする前に、以下の記事のガイドラインに従ってください。 - - -* [{% data variables.product.prodname_marketplace %}でのアプリケーションのリストに対する要件](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) -* [セキュリティレビュープロセス](/marketplace/getting-started/security-review-process/) +- "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" +- "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" diff --git a/translations/ja-JP/content/developers/github-marketplace/about-verified-creators.md b/translations/ja-JP/content/developers/github-marketplace/about-verified-creators.md new file mode 100644 index 0000000000..6b550e6b19 --- /dev/null +++ b/translations/ja-JP/content/developers/github-marketplace/about-verified-creators.md @@ -0,0 +1,43 @@ +--- +title: About verified creators +intro: 'Each organization that wants to sell apps on {% data variables.product.prodname_marketplace %} must follow a verification process. Their identity is checked and their billing process reviewed.' +versions: + free-pro-team: '*' +--- + +### About verified creators + +A verified creator is an organization that {% data variables.product.company_short %} has checked. Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only organizations that are verified by {% data variables.product.company_short %} can sell apps. For more information about organizations, see "[About organizations](/github/setting-up-and-managing-organizations-and-teams/about-organizations)." + +The verification process aims to protect users. For example, it verifies the seller's identity, checks that their {% data variables.product.product_name %} organization is set up securely, and that they can be contacted for support. + +After passing the verification checks, any apps that the organization lists on {% data variables.product.prodname_marketplace %} are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. The organization can now add paid plans to any of their apps. Each app with a paid plan also goes through a financial onboarding process to check that it's set up to handle billing correctly. + +![verified creator badges](/assets/images/marketplace/marketplace_verified_creator_badges_apps.png) + +In addition to the verified creator badge, you'll also see badges for unverified and verified apps. These apps were published using the old method for verifying individual apps. + +![検証済みの緑と未検証の灰色のバッジ](/assets/images/marketplace/marketplace_verified_badges.png) + +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." + +### About the verification process + +The first time you request verification for a listing of one of your apps, you will enter the verification process. An onboarding expert will guide you through the process. This includes checking: + +- Profile information - The basic profile information is populated accurately and appropriately. +- Security - The organization has enabled two-factor authentication. +- Verified domain - The organization has verified the domain of the site URL. +- Purchase webhook event - The event is handled correctly by the app. + +When your organization is verified, all your apps are shown with a verified creator badge. You are now able to offer paid plans for any of your apps. + +For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% note %} + +**Note:** This verification process for apps replaces the previous process where individual apps were verified. The current process is similar to the verification process for actions. If you have apps that were verified under the old process, these will not be affected by the changes. The {% data variables.product.prodname_marketplace %} team will contact you with details of how to migrate to organization-based verification. + +{% endnote %} diff --git a/translations/ja-JP/content/developers/github-marketplace/billing-customers.md b/translations/ja-JP/content/developers/github-marketplace/billing-customers.md index 925d2cb0db..1beeed54f5 100644 --- a/translations/ja-JP/content/developers/github-marketplace/billing-customers.md +++ b/translations/ja-JP/content/developers/github-marketplace/billing-customers.md @@ -13,17 +13,17 @@ versions: ### 支払いを理解する -顧客は、アプリケーションの購入時に月次あるいは年次の支払いサイクルを選択できます。 顧客が行う支払いサイクルとプランの選択に対するすべての変更は、`marketplace_purchase`イベントを発生させます。 `marketplace_purchase` webhookのペイロードを参照すれば、顧客がどの支払いサイクルを選択したのか、そして次の支払日がいつ始まるのか（`effective_date`）を知ることができます。 webhookのペイロードに関する詳しい情報については「[{% data variables.product.prodname_marketplace %}のwebhookイベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を参照してください。 +顧客は、アプリケーションの購入時に月次あるいは年次の支払いサイクルを選択できます。 顧客が行う支払いサイクルとプランの選択に対するすべての変更は、`marketplace_purchase`イベントを発生させます。 `marketplace_purchase` webhookのペイロードを参照すれば、顧客がどの支払いサイクルを選択したのか、そして次の支払日がいつ始まるのか（`effective_date`）を知ることができます。 For more information about webhook payloads, see "[Webhook events for the {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)." ### アプリケーションのUIにおける支払いサービスの提供 -アプリケーションのWebサイトでは、顧客が以下のアクションを行えなければなりません。 -- 顧客は個人及びOrganizationアカウントで別々に{% data variables.product.prodname_marketplace %}のプランを変更したりキャンセルしたりできなければなりません。 +Customers should be able to perform the following actions from your app's website: +- Customers should be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. {% data reusables.marketplace.marketplace-billing-ui-requirements %} ### アップグレード、ダウングレード、キャンセルのための支払いサービス -明確で一貫性のある支払いプロセスを保つために、アップグレード、ダウングレード、キャンセルについて以下のガイドラインに従ってください。 {% data variables.product.prodname_marketplace %}の購入イベントに関する詳細な手順については「[支払いのフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)」を参照してください。 +明確で一貫性のある支払いプロセスを保つために、アップグレード、ダウングレード、キャンセルについて以下のガイドラインに従ってください。 For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." `marketplace_purchase` webhookの`effective_date`キーを使えば、プランの変更がいつ生じるのかを確認し、定期的に[プランのアカウントのリスト](/rest/reference/apps#list-accounts-for-a-plan)を同期できます。 @@ -33,7 +33,7 @@ versions: {% data reusables.marketplace.marketplace-failed-purchase-event %} -アプリケーションへのアップグレードやダウングレードのワークフローの構築に関する情報については「[プランのアップグレード及びダウングレード](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)」を参照してください。 +For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)." #### ダウングレードとキャンセル @@ -45,4 +45,4 @@ versions: {% data reusables.marketplace.cancellation-clarification %} - 顧客が後でプランを継続したくなった場合には、GitHubを通じてプランをアップグレードできるようにします。 -アプリケーションへのキャンセルのワークフローの構築に関する情報については「[プランのキャンセル](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)」を参照してください。 +For information about building cancellation workflows into your app, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." diff --git a/translations/ja-JP/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md b/translations/ja-JP/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md new file mode 100644 index 0000000000..4107fa4427 --- /dev/null +++ b/translations/ja-JP/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md @@ -0,0 +1,20 @@ +--- +title: Customer experience best practices for apps +intro: 'Guidelines for creating an app that will be easy to use and understand.' +shortTitle: Customer experience best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a good customer experience. + +### Customer communication + +- Marketing materials for the app should accurately represent the app's behavior. +- Apps should include links to user-facing documentation that describe how to set up and use the app. +- Customers should be able to see what type of plan they have in the billing, profile, or account settings section of the app. +- Customers should be able to install and use your app on both a personal account and an organization account. They should be able to view and manage the app on those accounts separately. + +### Plan management + +{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/ja-JP/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/ja-JP/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 170ba843a4..0921fa228c 100644 --- a/translations/ja-JP/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/ja-JP/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,8 +60,8 @@ versions: ### アプリケーションのサブミット -{% data variables.product.prodname_marketplace %}リストが完成したら、**Overview（概要）**ページからレビューのためにリストをサブミットできます。 「[{% data variables.product.prodname_marketplace %}の開発者契約](/articles/github-marketplace-developer-agreement/)」を読んで同意しなければなりません。続いて**Submit for review（レビューのためにサブミット）**をクリックできます。 レビューのためにアプリケーションをサブミットした後、{% data variables.product.prodname_marketplace %}のオンボーディングチームから、オンボーディングのプロセスに関する追加情報と併せて連絡が来ます。 オンボーディングとセキュリティレビューのプロセスに関する詳細については「[{% data variables.product.prodname_marketplace %}を使い始める](/marketplace/getting-started/)」を参照してください。 +{% data variables.product.prodname_marketplace %}リストが完成したら、**Overview（概要）**ページからレビューのためにリストをサブミットできます。 「[{% data variables.product.prodname_marketplace %}の開発者契約](/articles/github-marketplace-developer-agreement/)」を読んで同意しなければなりません。続いて**Submit for review（レビューのためにサブミット）**をクリックできます。 After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. オンボーディングとセキュリティレビューのプロセスに関する詳細については「[{% data variables.product.prodname_marketplace %}を使い始める](/marketplace/getting-started/)」を参照してください。 ### {% data variables.product.prodname_marketplace %}リストの削除 -アプリケーションを{% data variables.product.prodname_marketplace %}のリストに載せたくなくなったなら、リストを削除するために[marketplace@github.com](mailto:marketplace@github.com)に連絡してください。 +If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing. diff --git a/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index 5166af9deb..ac9edbac20 100644 --- a/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ja-JP/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -28,7 +28,7 @@ versions: `marketplace_purchase` webhookから`effective_date`と`marketplace_purchase`を読み取り、顧客が購入したプラン、支払いサイクルの開始時点、次の支払いサイクルの開始時点を判断してください。 -アプリケーションが無料トライアルを提供しているなら、webhookから`marketplace_purchase[on_free_trial]`属性を読んでください。 この値が`true`なら、アプリケーションは無料トライアルの開始日(`effective_date`)と、無料トライアルの終了日(`free_trial_ends_on`)を追跡しなければなりません。 アプリケーションのUIに無料トライアルの残日数を表示するのには、`free_trial_ends_on`の日付を使ってください。 これはバナーか、[支払いUI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui)のいずれでも行えます。 無料トライアルの終了前のキャンセルの処理方法を学ぶには、「[プランのキャンセル](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)」を参照してください。 無料トライアルの終了時点での無料トライアルから有料プランへの移行方法を知るには、「[プランのアップグレードとダウングレード](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)」を参照してください。 +アプリケーションが無料トライアルを提供しているなら、webhookから`marketplace_purchase[on_free_trial]`属性を読んでください。 この値が`true`なら、アプリケーションは無料トライアルの開始日(`effective_date`)と、無料トライアルの終了日(`free_trial_ends_on`)を追跡しなければなりません。 アプリケーションのUIに無料トライアルの残日数を表示するのには、`free_trial_ends_on`の日付を使ってください。 これはバナーか、[支払いUI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui)のいずれでも行えます。 To learn how to handle cancellations before a free trial ends, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." See "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)" to find out how to transition a free trial to a paid plan when a free trial expires. `marketplace_purchase`イベントペイロードの例については「[{% data variables.product.prodname_marketplace %} webhookイベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を参照してください。 diff --git a/translations/ja-JP/content/developers/github-marketplace/index.md b/translations/ja-JP/content/developers/github-marketplace/index.md index 67402d4a74..33a722a3a6 100644 --- a/translations/ja-JP/content/developers/github-marketplace/index.md +++ b/translations/ja-JP/content/developers/github-marketplace/index.md @@ -11,8 +11,10 @@ versions: {% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /about-github-marketplace %} + {% link_in_list /about-verified-creators %} {% link_in_list /requirements-for-listing-an-app %} - {% link_in_list /security-review-process-for-submitted-apps %} + {% link_in_list /security-best-practices-for-apps %} + {% link_in_list /customer-experience-best-practices-for-apps %} {% link_in_list /viewing-metrics-for-your-listing %} {% link_in_list /viewing-transactions-for-your-listing %} {% topic_link_in_list /using-the-github-marketplace-api-in-your-app %} @@ -27,7 +29,7 @@ versions: {% link_in_list /writing-a-listing-description-for-your-app %} {% link_in_list /setting-pricing-plans-for-your-listing %} {% link_in_list /configuring-a-webhook-to-notify-you-of-plan-changes %} - {% link_in_list /submitting-your-listing-for-review %} + {% link_in_list /submitting-your-listing-for-publication %} {% topic_link_in_list /selling-your-app-on-github-marketplace %} {% link_in_list /pricing-plans-for-github-marketplace-apps %} {% link_in_list /billing-customers %} diff --git a/translations/ja-JP/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/ja-JP/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md index f0d7d1d4af..5761c00a22 100644 --- a/translations/ja-JP/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/ja-JP/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -10,35 +10,45 @@ versions: -{% data variables.product.prodname_marketplace %}の価格プランは、無料、定額料金、ユニット単位にすることができ、GitHubは価格を米ドルでリストします。 顧客はGitHub.comを離れることなく、{% data variables.product.product_name %}アカウントに添付された支払い方法を使ってアプリケーションを購入します。 支払い処理を行うためのコードを書く必要はありませんが、購入イベントのための[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)は処理しなければなりません。 +{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to verified listings. + +Customers purchase your app using a payment method attached to their {% data variables.product.product_name %} account, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." {% data variables.product.prodname_marketplace %}上でリストしているアプリケーションが複数のプランのオプションを持っているなら、対応する価格プランをセットアップできます。 たとえばアプリケーションが2つのプランの選択肢としてオープンソースプランとプロプランを持っているなら、オープンソースプランに対して無料価格プランを、そしてプロプランに対して定額料金プランをセットアップできます。 それぞれの{% data variables.product.prodname_marketplace %}リストには、リストされたすべてのプランに対して年間及び月間の価格がなければなりません。 価格プランの作成方法に関する詳しい情報については「[{% data variables.product.prodname_marketplace %}リストの価格プランの設定](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)」を参照してください。 -{% note %} - -**ノート:**{% data variables.product.prodname_marketplace %}上でアプリケーションをリストする場合、{% data variables.product.prodname_marketplace %}の外部で有料サービスを提供しているなら無料プランでアプリケーションをリストすることはできません。 - -{% endnote %} +{% data reusables.marketplace.free-plan-note %} ### 価格プランの種類 -**無料プラン**は、完全に無料です。 無料プランをセットアップした場合、アプリケーションを利用するために無料プランを選択したユーザに課金することはできません。 リストでは無料と有料のプランをどちらも作成できます。 未検証の無料アプリケーションは、支払いフローを実装する必要はありません。 GitHubによって検証される無料アプリケーションは、新規の購入とキャンセルのための支払いフローを実装しなければなりませんが、無料トライアル、アップグレード、ダウングレードの支払いフローを実装する必要はありません。 無料のサービスとして{% data variables.product.prodname_marketplace %}にリスト済みのアプリケーションに有料プランを追加する場合は、そのアプリケーションをレビューのために再度サブミットしなければなりません。 +#### Free pricing plans -**定額料金プラン**は、月単位及び年単位で設定された料金を課金します。 +{% data reusables.marketplace.free-apps-encouraged %} -**ユニット単位の価格プラン**は、月単位あるいは年単位で、指定した単位に基づいて設定された料金を課金します。 「ユニット」には好きなもの（たとえばユーザ、シート、あるいは人）を指定できます。 +Free plans are completely free for users. 無料プランをセットアップした場合、アプリケーションを利用するために無料プランを選択したユーザに課金することはできません。 リストでは無料と有料のプランをどちらも作成できます。 -**Marketplace無料トライアル**は、OAuthあるいはGitHubアプリケーションを顧客に対して14日間の無料トライアルを提供します。 [Marketplaceの価格プランをセットアップ](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)する際に、このオプションを選択して定額料金あるいはユニット単位の価格プランに対して無料トライアルを提供できます。 +All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding. + +#### Paid pricing plans + +There are two types of paid pricing plan: + +- Flat rate pricing plans charge a set fee on a monthly and yearly basis. + +- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. 「ユニット」には好きなもの（たとえばユーザ、シート、あるいは人）を指定できます。 + +You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans. ### 無料トライアル -顧客はMarketplaceのリスト上の利用可能な任意の有料プランに対して無料トライアルを開始できますが、1つのMarketplace製品に対して複数の無料トライアルを作成することはできません。 +Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product. 無料トライアルの期間は固定の14日間です。 顧客はトライアル期間の終了の4日前（無料トライアルの11日目）に、プランがアップグレードされるという通知を受け取ります。 顧客は、キャンセルしないかぎり、無料トライアルの終わりにトライアルを行っていたプランに自動的に登録されます。 -アプリケーションで無料トライアルを処理する方法の詳細については「[新規の購入と無料トライアル](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)」を参照してください。 +For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)." {% note %} diff --git a/translations/ja-JP/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/ja-JP/content/developers/github-marketplace/requirements-for-listing-an-app.md index 3d38fbd3af..fa8fb924d2 100644 --- a/translations/ja-JP/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/ja-JP/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- title: アプリケーションのリストのための要件 -intro: '{% data variables.product.prodname_marketplace %}上のアプリケーションは、弊社の{% data variables.product.prodname_marketplace %}オンボーディングスペシャリストがリストを承認する前に、このページに記載されている要件概要を満たしていなければなりません。' +intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ @@ -12,49 +12,62 @@ versions: free-pro-team: '*' --- + +The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app. -レビューのためにアプリケーションをサブミットする前に、「[{% data variables.product.prodname_marketplace %}開発者契約](/articles/github-marketplace-developer-agreement/)」の条項を読んで同意しなければなりません。 {% data variables.product.product_name %}上の[ドラフトリスト](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)内の条項に同意しなければなりません。 アプリケーションをサブミットすると、オンボーディングプロセスに関するさらなる情報と共に{% data variables.product.prodname_marketplace %}オンボーディングスペシャリストの一人から連絡があり、アプリケーションをレビューして以下の要件を満たしていることを確認してくれます。 +### Requirements for all {% data variables.product.prodname_marketplace %} listings -### ユーザー体験 +All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -- {% data variables.product.prodname_github_app %}は、最低でも100個のインストールが必要です。 -- {% data variables.product.prodname_oauth_app %}は最低200ユーザが必要です。 +#### User experience requirements for all apps + +All listings should meet the following requirements, regardless of whether they are for a free or paid app. + +- Listings must not actively persuade users away from {% data variables.product.product_name %}. +- Listings must include valid contact information for the publisher. +- Listings must have a relevant description of the application. +- Listings must specify a pricing plan. - アプリケーションは顧客に価値を提供し、認証以外の方法でプラットフォームと統合されていなければなりません - アプリケーションケーションは{% data variables.product.prodname_marketplace %}で公開されなければならず、ベータや招待のみでの利用であってはなりません。 -- アプリケーションはユーザを{% data variables.product.product_name %}から積極的に離れさせるようにしてはなりません。 -- アプリケーションのマーケティング資料は、アプリケーションの動作を正確に表現していなければなりません。 -- アプリケーションは、アプリケーションのセットアップと利用の方法を述べたユーザ向けのドキュメンテーションへのリンクを含まなければなりません。 -- 顧客がアプリケーションを購入し、GitHubがそのユーザをアプリケーションのインストールURLにリダイレクトしたなら、アプリケーションはすぐにOAuthフローを開始しなければなりません。 詳細については「[新規購入や無料トライアルの取り扱い](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/#step-3-authorization)」を参照してください。 +- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -- 顧客はアプリケーションをインストールし、個人及びOrganization双方のアカウント上のリポジトリを選択できなければなりません。 顧客はそれらのアカウントを個別に表示及び管理できなければなりません。 +For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)." -### ブランドとリスト +#### Brand and listing requirements for all apps -- GitHubを使うアプリケーションは、「[{% data variables.product.product_name %} ロゴと利用](https://github.com/logos)」ガイドラインに従わなければなりません。 +- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)." - アプリケーションは、「[{% data variables.product.prodname_marketplace %}リストの説明の作成](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)」にある推奨事項を満たすロゴ、機能カード、スクリーンショット画像を持っていなければなりません。 - リストには、十分に書かれた文法上の誤りがない説明が含まれていなければなりません。 リストの作成のガイダンスとしては、「[{% data variables.product.prodname_marketplace %}リストの説明の作成](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)」を参照してください。 -### セキュリティ +To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)." -アプリケーションは、{% data variables.product.prodname_marketplace %}にリストされる前にセキュリティレビューを経ることになります。 レビューが成功するためには、「[セキュリティレビュープロセス](/marketplace/getting-started/security-review-process/)」にリストされている要件を満たし、セキュリティのベストプラクティスにしたがっていなければなりません。 レビュープロセスに関する情報については、[marketplace@github.com](mailto:marketplace@github.com)までお問い合わせください。 +### Considerations for free apps -### 支払いのフロー +{% data reusables.marketplace.free-apps-encouraged %} -アプリケーションは、[{% data variables.product.prodname_marketplace %} webhookイベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)を使って[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)を統合していなければなりません。 +### Requirements for paid apps -#### 無料アプリケーション +In addition to the requirements for all apps above, each app that you offer as a paid service on {% data variables.product.prodname_marketplace %} must also meet the following requirements: -{% data reusables.marketplace.free-apps-encouraged %}無料アプリケーションをリストするなら、以下の要件を満たさなければなりません。 +- {% data variables.product.prodname_github_app %}は、最低でも100個のインストールが必要です。 +- {% data variables.product.prodname_oauth_app %}は最低200ユーザが必要です。 +- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. +- Publishing organizations must have a verified domain and must enable two-factor authentication. 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.") -- 顧客はアプリケーションの支払い、プロフィール、アカウント設定のセクションで、無料プランがあるのを見ることができなければなりません。 -- 顧客がアプリケーションをキャンセルする際には、[プランのキャンセル](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)のためのフローに従わなければなりません。 +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the listing. -#### 有料アプリケーション +{% note %} -アプリケーションを有料サービスとして提供するためには、{% data variables.product.prodname_marketplace %}上でアプリケーションをリストする上で以下の要件を満たさなければなりません。 +The verification process is open to organizations. {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% endnote %} + +### Billing requirements for paid apps + +Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their {% data variables.product.product_name %} account. -- {% data variables.product.prodname_marketplace %}でアプリケーションを販売するには、GitHubの支払いシステムを使わなければなりません。 アプリケーションは支払いを処理する必要はありませんが、「[{% data variables.product.prodname_marketplace %} 購入イベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を使って新規の購入、アップグレード、ダウングレード、キャンセル、無料トライアルを管理しなければなりません。 これらのイベントをアプリケーションに統合する方法を学ぶには、「[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)」を参照してください。 GitHubの支払いシステムを使えば、顧客はGitHubを離れることなくアプリケーションを購入し、自分の{% data variables.product.product_name %}アカウントにすでに結合されている支払い方法でサービスに対する支払いを行えます。 - アプリケーションは、有料のサブスクリプションの購入について、月次及び年次の支払いをサポートしなければなりません。 - リストは、無料及び有料プランの任意の組み合わせを提供できます。 無料プランはオプションですが、推奨されます。 詳しい情報については「[{% data variables.product.prodname_marketplace %}リストの価格プランの設定](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)」を参照してください。 -{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/ja-JP/content/developers/github-marketplace/security-best-practices-for-apps.md b/translations/ja-JP/content/developers/github-marketplace/security-best-practices-for-apps.md new file mode 100644 index 0000000000..69965cb611 --- /dev/null +++ b/translations/ja-JP/content/developers/github-marketplace/security-best-practices-for-apps.md @@ -0,0 +1,59 @@ +--- +title: Security best practices for apps +intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/marketplace/getting-started/security-review-process/ + - /marketplace/getting-started/security-review-process + - /developers/github-marketplace/security-review-process-for-submitted-apps +shortTitle: Security best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a secure user experience. + +### 認可、認証、アクセスコントロール + +We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. 詳細については、「[GitHub AppsとOAuth Appsの違い](/apps/differences-between-apps/)」を参照してください。 +- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia. +- Apps should provide customers with a way to delete their account, without having to email or call a support person. +- アプリケーションは、異なる実装間でトークンを共有してはなりません。 たとえば、デスクトップのアプリケーションはWebベースのアプリケーションとは別のトークンを持つべきです。 個々のトークンを使うことで、それぞれのアプリケーションはGitHubのリソースに必要なアクセスを個別にリクエストできます。 +- ユーザの種類に応じて求められる機能によって、様々なユーザのロールを持たせてアプリケーションを設計してください。 たとえば、標準的なユーザは管理機能を利用できるべきではなく、支払いマネージャーはリポジトリのコードにプッシュアクセスできるべきではありません。 +- Apps should not share service accounts such as email or database services to manage your SaaS service. +- アプリケーションで使用されるすべてのサービスは、固有のログインとパスワードクレデンシャルを持たなければなりません。 +- プロダクションのホスティングインフラストラクチャへの管理権限でのアクセスは、管理業務を持つエンジニアや従業員にのみ与えられるべきです。 +- Apps should not use personal access tokens to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps): + - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/). + - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). + +### データの保護 + +- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git. +- Apps should store client ID and client secret keys securely. それらは[環境変数](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables)に保存することをおすすめします。 +- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub. +- Apps should not require the user to provide their GitHub password. +- アプリケーションは、トークン、クライアントID、クライアントシークレットを暗号化すべきです。 + +### ロギング及びモニタリング + +Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year. セキュリティログは以下を含まなければなりません。 + +- 認証及び認可イベント +- サービス設定の変更 +- オブジェクトの読み書き +- すべてのユーザ及びグループの権限変更 +- ロールの管理者への昇格 +- 各イベントに対する一貫したタイムスタンプ +- 記録されたすべてのアクションのソースユーザ、IPアドレス及びホスト名 + +### インシデントレスポンスのワークフロー + +To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. サードパーティのベンダを利用するよりは、自社内にセキュリティ及び運用インシデントレスポンスチームを持つことをおすすめします。 You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident. + +For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template. + +### 脆弱性管理とパッチ適用ワークフロー + +プロダクションインフラストラクチャーの定期的な脆弱性スキャンを行わなければなりません。 脆弱性スキャンの結果をトリアージし、脆弱性の修正までの期間を定義して同意しなければなりません。 + +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)." diff --git a/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 98b7790925..3f3d779875 100644 --- a/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/ja-JP/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -1,6 +1,6 @@ --- title: リストに対する価格プランの設定 -intro: '[アプリケーションを{% data variables.product.prodname_marketplace %}上でリストする](/marketplace/listing-on-github-marketplace/)際に、アプリケーションを無料のサービスとして提供するか、アプリケーションを販売するかを選択できます。 アプリケーションを販売することを計画するなら、様々な機能レベルに対して異なる価格プランを作成できます。' +intro: 'When you list your app on {% data variables.product.prodname_marketplace %}, you can choose to provide your app as a free service or sell your app. アプリケーションを販売することを計画するなら、様々な機能レベルに対して異なる価格プランを作成できます。' redirect_from: - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ @@ -17,57 +17,52 @@ versions: free-pro-team: '*' --- +### About setting pricing plans +If you want to sell an app on {% data variables.product.prodname_marketplace %}, you need to request verification when you publish the listing for your app. During the verification process, an onboarding expert checks the organization's identity and security settings. The onboarding expert will also take the organization through financial onboarding. For more information, see: "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% data variables.product.prodname_marketplace %} offers several different types of pricing plan. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." + +### About saving pricing plans + +You can save pricing plans in a draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish a pricing plan on a published listing, it's available for customers to purchase immediately. 最大で10の価格プランを公開できます。 + +For guidelines on billing customers, see "[Billing customers](/developers/github-marketplace/billing-customers)." ### 価格プランの作成 -{% data variables.product.prodname_marketplace %}が提供する価格プランの種類について学ぶには、「[{% data variables.product.prodname_marketplace %}の価格プラン](/marketplace/selling-your-app/github-marketplace-pricing-plans/)」を参照してください。 有益な支払いのガイドラインが「[アプリケーションの販売](/marketplace/selling-your-app/)」にもあります。 - -価格プランは、ドラフトまたは公開状態にできます。 {% data variables.product.prodname_marketplace %}のリストを承認のためにサブミットしていない場合、公開されたリストはアプリケーションが承認され、{% data variables.product.prodname_marketplace %}上でリストされるまではドラフトのリストと同様に機能します。 ドラフトのリストを利用すると、{% data variables.product.prodname_marketplace %}リストページで利用できるようにすることなく、新しい価格プランを作成して保存できます。 価格プランを公開すると、すぐに顧客が購入できるようになります。 最大で10の価格プランを公開できます。 - -{% data variables.product.prodname_marketplace %}リストの価格プランを作成するには、[{% data variables.product.prodname_marketplace %}リストページ](https://github.com/marketplace/manage)の左のサイドバーで**Plans and pricing（プラント価格）**をクリックしてください。 まだ{% data variables.product.prodname_marketplace %}リストを作成していないなら、「[ドラフトの{% data variables.product.prodname_marketplace %}リストの作成](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)」を読んで、作成方法を学んでください。 +{% data variables.product.prodname_marketplace %}リストの価格プランを作成するには、[{% data variables.product.prodname_marketplace %}リストページ](https://github.com/marketplace/manage)の左のサイドバーで**Plans and pricing（プラント価格）**をクリックしてください。 For more information, see "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)." **New draft plan（新規ドラフトプラン）**をクリックすると、価格プランをカスタマイズできるフォームが表示されます。 価格プランを作成するには、以下のフィールドを設定しなければなりません。 -#### Plan name（プラン名） +- **Plan name** - Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align with the plan's resources, the size of the company that will use the plan, or anything you'd like. -価格プランの名前は{% data variables.product.prodname_marketplace %}アプリケーションのランディングページに表示されます。 プランのリソース、プランを利用する企業の規模、あるいは好きなもの何にでもあわせて価格プランの名前をカスタマイズできます。 +- **Pricing models** - There are three types of pricing plan: free, flat-rate, and per-unit. All plans require you to process new purchase and cancellation events from the marketplace API. In addition, for paid plans: -#### Pricing models（価格モデル） + - You must set a price for both monthly and yearly subscriptions in US dollars. + - Your app must process plan change events. + - You must request verification to publish a listing with a paid plan. + - {% data reusables.marketplace.marketplace-pricing-free-trials %} -##### Free plans（無料プラン） + For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.free-apps-encouraged %} 無料プランでも、[新規購入](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)や[キャンセル](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)の支払いフローを処理する必要があります。 詳細については「[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)」を参照してください。 +- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. たとえば、価格プランがユニット単位であり、複数のシートを提供するなら、個人アカウントからOrganization内の人にシートを割り当てる方法はないので、**Organization accounts only（Organizationアカウントのみ）**が選択できるでしょう。 -##### Flat-rate plans（定額プラン） +- **Short description** - Write a brief summary of the details of the pricing plan. この説明には、そのプランが意図している顧客の種類や、プランに含まれるリソースなどが含まれることがあります。 -定額プランを使うと、顧客に対して定額でサービスを提供できます。 {% data reusables.marketplace.marketplace-pricing-free-trials %} +- **Bullets** - You can write up to four bullets that include more details about your pricing plan. この箇条書きでは、アプリケーションのユースケースを含めたり、プランに含まれるリソースや機能に関するさらなる詳細をリストしたりすることができます。 -定額料金では、米ドルで月額及び年額のサブスクリプションに対して 価格を設定しなければなりません。 - -##### Per-unit plans（ユニット単位プラン） - -ユニット単位での価格を利用すると、ユニットごとにアプリケーションを提供できます。 たとえば、ユニットには人、シート、ユーザが使えます。 ユニットの名前を提供し、月額及び年額のサブスクリプションを米ドルで 設定しなければなりません。 - -#### Available for（利用の対象） - -{% data variables.product.prodname_marketplace %}の価格プランは、**Personal and organization accounts（個人及びOrganizationのアカウント）**、**Personal accounts only（個人アカウントのみ）**、**Organization accounts only（Organizationアカウントのみ）**のいずれかに適用できます。 たとえば、価格プランがユニット単位であり、複数のシートを提供するなら、個人アカウントからOrganization内の人にシートを割り当てる方法はないので、**Organization accounts only（Organizationアカウントのみ）**が選択できるでしょう。 - -#### Short description（短い説明） - -価格プランの詳細に関する簡単な概要を書いてください。 この説明には、そのプランが意図している顧客の種類や、プランに含まれるリソースなどが含まれることがあります。 - -#### Bullets（箇条書き） - -最大で4項目の箇条書きをして、価格プランに関する詳細を含めることができます。 この箇条書きでは、アプリケーションのユースケースを含めたり、プランに含まれるリソースや機能に関するさらなる詳細をリストしたりすることができます。 +{% data reusables.marketplace.free-plan-note %} ### {% data variables.product.prodname_marketplace %}リストの価格プランの変更 -{% data variables.product.prodname_marketplace %}プランの価格プランが不要になった場合、あるいは価格の細部を調整する必要が生じた場合、その価格プランを削除できます。 +If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it. ![価格プランを削除するボタン](/assets/images/marketplace/marketplace_remove_this_plan.png) -{% data variables.product.prodname_marketplace %}にリスト済みのアプリケーションの価格プランを公開すると、そのプランは変更できなくなります。 その代わりに、その価格プランを削除しなければなりません。 削除された価格プランを購入済みの顧客は、オプトアウトして新しい価格プランに移行するまでは、そのプランを使い続けます。 価格プランの詳細については、「[{% data variables.product.prodname_marketplace %}の価格プラン](/marketplace/selling-your-app/github-marketplace-pricing-plans/)」を参照してください。 +Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan and create a new plan. 削除された価格プランを購入済みの顧客は、オプトアウトして新しい価格プランに移行するまでは、そのプランを使い続けます。 価格プランの詳細については、「[{% data variables.product.prodname_marketplace %}の価格プラン](/marketplace/selling-your-app/github-marketplace-pricing-plans/)」を参照してください。 価格プランを削除すると、ユーザはそのプランを使ってアプリケーションを購入することはできなくなります。 削除されたプランの既存ユーザは、プランのサブスクリプションをキャンセルするまではそのプランに留まり続けます。 diff --git a/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-publication.md new file mode 100644 index 0000000000..bd66b6b202 --- /dev/null +++ b/translations/ja-JP/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -0,0 +1,37 @@ +--- +title: Submitting your listing for publication +intro: 'You can submit your listing for the {% data variables.product.prodname_dotcom %} community to use.' +redirect_from: + - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review + - /developers/github-marketplace/submitting-your-listing-for-review +versions: + free-pro-team: '*' +--- + + + +Once you've completed the listing for your app, you'll see two buttons that allow you to request publication of the listing with or without verification. The **Request** button for "Publish without verification" is disabled if you have published any paid pricing plans in the listing. + +![未検証及び検証済みリクエストボタン](/assets/images/marketplace/marketplace-request-button.png) + +{% data reusables.marketplace.launch-with-free %} + +After you submit your listing for review, an onboarding expert will reach out to you with additional information. + +For an overview of the process for creating and submitting a listing, see "[About {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)." + +### Prerequisites for publishing with verification + +Before you request verification of your listing, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your app. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +If you've met the requirements for listing and you've integrated with the {% data variables.product.prodname_marketplace %} API, go ahead and submit your listing. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Transferring an app to an organization before you submit](#transferring-an-app-to-an-organization-before-you-submit)" below. + +### Transferring an app to an organization before you submit + +You cannot sell an app that's owned by a user account. You need to transfer the app to an organization that is already a verified creator, or that can request verification for a listing for the app. For details, see: + +1. "[Creating an organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" + +1. "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" diff --git a/translations/ja-JP/content/developers/github-marketplace/testing-your-app.md b/translations/ja-JP/content/developers/github-marketplace/testing-your-app.md index 03cc9014c1..15cf792b11 100644 --- a/translations/ja-JP/content/developers/github-marketplace/testing-your-app.md +++ b/translations/ja-JP/content/developers/github-marketplace/testing-your-app.md @@ -1,6 +1,6 @@ --- title: アプリをテストする -intro: 'リストを{% data variables.product.prodname_marketplace %}にサブミットする前に、APIとwebhookを使ってアプリケーションをテストし、顧客に理想的な体験を提供できるようにすることをGitHubはおすすめします。 {% data variables.product.prodname_marketplace %}オンボーディングチームによる承認の前に、アプリケーションは[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)を十分に処理できなければなりません。' +intro: 'リストを{% data variables.product.prodname_marketplace %}にサブミットする前に、APIとwebhookを使ってアプリケーションをテストし、顧客に理想的な体験を提供できるようにすることをGitHubはおすすめします。 Before an onboarding expert approves your app, it must adequately handle the billing flows.' redirect_from: - /apps/marketplace/testing-apps-apis-and-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ @@ -13,7 +13,7 @@ versions: ### アプリケーションのテスト -[ドラフトの{% data variables.product.prodname_marketplace %}リスト](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)を使って、各[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)をシミュレートできます。 リストがドラフト状態にあるということは、まだそれが承認のためにサブミットされていないということです。 ドラフトの{% data variables.product.prodname_marketplace %}リストを使って行った購入は、実際の取引には_ならず_、GitHubはクレジットカードへの課金をしません。 +You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. リストがドラフト状態にあるということは、まだそれが承認のためにサブミットされていないということです。 ドラフトの{% data variables.product.prodname_marketplace %}リストを使って行った購入は、実際の取引には_ならず_、GitHubはクレジットカードへの課金をしません。 For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." #### 変更のテストのために開発アプリケーションをドラフトリストと使用する diff --git a/translations/ja-JP/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/ja-JP/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index 8fb4e33a30..564fb46e01 100644 --- a/translations/ja-JP/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/ja-JP/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -1,6 +1,6 @@ --- title: GitHub Marketplace APIのためのwebhookイベント -intro: '{% data variables.product.prodname_marketplace %}アプリケーションは、ユーザのプランに対する変更に関する情報を、Marketplaceの購入イベントwebhookから受け取ります。 Marketplaceの購入イベントは、ユーザが支払いプランの購入、キャンセル、変更をした場合にトリガーされます。 それぞれの種類のイベントへの対応方法の詳細については「[支払いフロー](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)」を参照してください。' +intro: '{% data variables.product.prodname_marketplace %}アプリケーションは、ユーザのプランに対する変更に関する情報を、Marketplaceの購入イベントwebhookから受け取ります。 Marketplaceの購入イベントは、ユーザが支払いプランの購入、キャンセル、変更をした場合にトリガーされます。' redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ diff --git a/translations/ja-JP/content/developers/overview/about-githubs-apis.md b/translations/ja-JP/content/developers/overview/about-githubs-apis.md index ed6731b247..23c746d51b 100644 --- a/translations/ja-JP/content/developers/overview/about-githubs-apis.md +++ b/translations/ja-JP/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,7 @@ versions: github-ae: '*' --- -GitHub APIには、[REST API](/rest)と[GraphQL API](/graphql)という2つの安定バージョンがあります。 - -REST APIを使う際には、[`Accept`ヘッダを介してv3をリクエスト](/rest/overview/media-types#request-specific-version)することをおすすめします。 - -GraphQL APIの利用に関する情報については[v4のドキュメント](/graphql)を参照してください。 +GitHub APIには、[REST API](/rest)と[GraphQL API](/graphql)という2つの安定バージョンがあります。 REST APIを使う際には、[`Accept`ヘッダを介してv3をリクエスト](/v3/media/#request-specific-version)することをおすすめします。 GraphQL APIの利用に関する情報については[v4のドキュメント](/graphql)を参照してください。 ## 非推奨のバージョン 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 5a84bc623b..002f317523 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 @@ -11,36 +11,36 @@ versions: --- -Events APIは、GitHub上のアクティビティによってトリガーされる様々な種類のイベントを返します。 Each event response contains shared properties, but has a unique `payload` object determined by its event type. The [Event object common properties](#event-object-common-properties) describes the properties shared by all events, and each event type describes the `payload` properties that are unique to the specific event. +Events APIは、GitHub上のアクティビティによってトリガーされる様々な種類のイベントを返します。 各イベントのレスポンスは共有プロパティを含むとともに、イベントの種類によって決まる固有の`payload`オブジェクトを持ちます。 [イベントオブジェクトの共通プロパティ](#event-object-common-properties)は、すべてのイベントが共有するプロパティを示すものであり、各イベントの種類にはそのイベントに固有の`payload`プロパティが示されています。 {% if currentVersion == "free-pro-team@latest" %} {% endif %} -### Event object common properties +### イベントオブジェクトの共通プロパティ -The event objects returned from the Events API endpoints have the same structure. +Events APIエンドポイントから返されるイベントオブジェクトは、同じ構造を持ちます。 -| Event API attribute name | 説明 | -| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | Unique identifier for the event. | -| `type` | The type of event. Events uses PascalCase for the name. | -| `actor` | The user that triggered the event. | -| `actor.id` | The unique identifier for the actor. | -| `actor.login` | The username of the actor. | -| `actor.display_login` | The specific display format of the username. | -| `actor.gravatar_id` | The unique identifier of the Gravatar profile for the actor. | -| `actor.url` | The REST API URL used to retrieve the user object, which includes additional user information. | -| `actor.avatar_url` | The URL of the actor's profile image. | -| `repo` | The repository object where the event occurred. | -| `repo.id` | The unique identifier of the repository. | -| `repo.name` | The name of the repository, which includes the owner and repository name. For example, `octocat/hello-world` is the name of the `hello-world` repository owned by the `octocat` user account. | -| `repo.url` | The REST API URL used to retrieve the repository object, which includes additional repository information. | -| `payload` | The event payload object is unique to the event type. See the event type below for the event API `payload` object. | +| Event API属性名 | 説明 | +| --------------------- | ---------------------------------------------------------------------------------------------------- | +| `id` | イベントの一意の識別子。 | +| `type` | イベントの種類。 イベントの名前にはPascalCaseが使われます。 | +| `actor` | イベントをトリガーしたユーザ。 | +| `actor.id` | アクターの一意の識別子。 | +| `actor.login` | アクターのユーザ名。 | +| `actor.display_login` | ユーザ名に特定の表示形式。 | +| `actor.gravatar_id` | アクターのGravatarプロフィールの一意の識別子。 | +| `actor.url` | 追加のユーザ情報を含むユーザオブジェクトの取得に使われるREST APIのURL。 | +| `actor.avatar_url` | アクターのプロフィール画像のURL。 | +| `repo` | イベントが発生したリポジトリオブジェクト。 | +| `repo.id` | リポジトリの一意の識別子。 | +| `repo.name` | リポジトリの名前。オーナーとリポジトリの名前が含まれる。 たとえば`octocat/hello-world`は、`octocat`ユーザアカウントが所有する`hello-world`リポジトリの名前。 | +| `repo.url` | 追加のリポジトリ情報を含むリポジトリオブジェクトの取得に使われるREST APIのURL。 | +| `payload` | イベントの種類に固有のイベントペイロードオブジェクト。 イベントAPIの`payload`オブジェクトについては、以下のイベントの種類を参照してください。 | -#### Example WatchEvent event object +#### WatchEventイベントのオブジェクトの例 -This example shows the format of the [WatchEvent](#watchevent) response when using the [Events API](/rest/reference/activity#events). +この例は、[Events API](/rest/reference/activity#events)を使用する際の[WatchEvent](#watchevent)のレスポンスの形式を示しています。 ``` Status: 200 OK @@ -85,7 +85,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.commit_comment_properties %} @@ -95,7 +95,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.create_properties %} @@ -105,7 +105,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.delete_properties %} @@ -115,7 +115,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.fork_properties %} @@ -125,7 +125,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.gollum_properties %} @@ -135,7 +135,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.issue_comment_webhook_properties %} {% data reusables.webhooks.issue_comment_properties %} @@ -146,7 +146,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.issue_event_api_properties %} {% data reusables.webhooks.issue_properties %} @@ -157,7 +157,7 @@ Link: ; rel="next", {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.member_event_api_properties %} {% data reusables.webhooks.member_properties %} @@ -166,9 +166,9 @@ Link: ; rel="next", {% data reusables.webhooks.public_short_desc %} -#### Event `payload` object +#### イベントの`payload`オブジェクト -This event returns an empty `payload` object. +このイベントは、空の`payload`オブジェクトを返します。 ### PullRequestEvent @@ -176,7 +176,7 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %} @@ -187,7 +187,7 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.pull_request_review_comment_event_api_properties %} {% data reusables.webhooks.pull_request_review_comment_properties %} @@ -198,22 +198,22 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -| キー | 種類 | 説明 | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `push_id` | `integer` | Unique identifier for the push. | -| `size` | `integer` | The number of commits in the push. | -| `distinct_size` | `integer` | The number of distinct commits in the push. | -| `ref` | `string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | -| `head` | `string` | The SHA of the most recent commit on `ref` after the push. | -| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][sha]` | `string` | コミットのSHA。 | -| `commits[][message]` | `string` | コミットメッセージ。 | -| `commits[][author]` | `オブジェクト` | The git author of the commit. | -| `commits[][author][name]` | `string` | The git author's name. | -| `commits[][author][email]` | `string` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | +| キー | 種類 | 説明 | +| -------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `push_id` | `integer` | プッシュの一意の識別子。 | +| `size` | `integer` | プッシュ中のコミット数。 | +| `distinct_size` | `integer` | プッシュ中の個別のコミット数。 | +| `ref` | `string` | プッシュされた完全な[`git ref`](/rest/reference/git#refs)。 例:`refs/heads/main`。 | +| `head` | `string` | プッシュ後の`ref`上の最新のコミットのSHA。 | +| `before` | `string` | プッシュ前の`ref` 上の最新のコミットのSHA。 | +| `commits` | `array` | プッシュされたコミットを示すコミットオブジェクトの配列。 （配列には最大で20のコミットが含まれる。 必要な場合は、追加のコミットを[Commits API](/rest/reference/repos#commits)を使ってフェッチできる。 この制限はタイムラインイベントにのみ適用され、webhookの配信には適用されない） | +| `commits[][sha]` | `string` | コミットのSHA。 | +| `commits[][message]` | `string` | コミットメッセージ。 | +| `commits[][author]` | `オブジェクト` | コミットのGit作者。 | +| `commits[][author][name]` | `string` | Git作者の名前。 | +| `commits[][author][email]` | `string` | Git作者のメールアドレス。 | +| `commits[][url]` | `url` | コミットAPIのリソースを指すURL。 | +| `commits[][distinct]` | `boolean` | このコミットが以前にプッシュされたいずれとも異なっているか。 | ### ReleaseEvent @@ -221,7 +221,7 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.release_event_api_properties %} {% data reusables.webhooks.release_properties %} @@ -231,7 +231,7 @@ This event returns an empty `payload` object. {% data reusables.webhooks.sponsorship_short_desc %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.sponsorship_event_api_properties %} {% data reusables.webhooks.sponsorship_properties %} @@ -243,6 +243,6 @@ This event returns an empty `payload` object. {% data reusables.webhooks.events_api_payload %} -#### Event `payload` object +#### イベントの`payload`オブジェクト {% data reusables.webhooks.watch_properties %} diff --git a/translations/ja-JP/content/developers/webhooks-and-events/index.md b/translations/ja-JP/content/developers/webhooks-and-events/index.md index 6fa6d2ed01..46cc4aae54 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/index.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/index.md @@ -1,6 +1,6 @@ --- -title: Webhooks and events -intro: 'You can set up, test, and secure webhooks so your integrations can subscribe and react to events on {% data variables.product.prodname_dotcom %}.' +title: webhook とイベント +intro: 'webhook をセットアップ、テスト、および保護して、統合が {% data variables.product.prodname_dotcom %} のイベントをサブスクライブして対応できるようにすることができます。' versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/ja-JP/content/developers/webhooks-and-events/issue-event-types.md b/translations/ja-JP/content/developers/webhooks-and-events/issue-event-types.md index 7a7a452b62..e1bc1716c0 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/issue-event-types.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/issue-event-types.md @@ -1,6 +1,6 @@ --- -title: Issue event types -intro: 'For the Issues Events API and Timeline API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.' +title: Issue イベントタイプ +intro: 'Issues イベント API とタイムライン API について、各イベントタイプ、{% data variables.product.prodname_dotcom %} でのトリガーアクション、および各イベントの一意のプロパティについて学びます。' redirect_from: - /v3/issues/issue-event-types versions: @@ -10,27 +10,27 @@ versions: --- -Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs. +Issue イベントは、Issue およびプルリクエストのアクティビティによってトリガーされ、[Issue イベント API](/rest/reference/issues#events) および[タイムラインイベント API](/rest/reference/issues#timeline) で使用できます。 各イベントタイプでは、イベントが Issue イベントやタイムラインイベント API で使用可能かどうかを指定します。 -GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both. +GitHub の REST API は、すべてのプルリクエストを Issue と見なしますが、すべての Issue がプルリクエストであるとは限りません。 このため、Issue イベントエンドポイントとタイムラインイベントエンドポイントは、レスポンスで Issue とプルリクエストの両方を返す場合があります。 プルリクエストには、`issue` オブジェクト内に `pull_request` プロパティがあります。 プルリクエストは Issue のため、リポジトリ内で Issue とプルリクエストの番号が重複することはありません。 たとえば、リポジトリで最初の Issue を開くと、番号は 1 になります。 次にプルリクエストを開くと、番号は 2 になります。 各イベントタイプでは、イベントがプルリクエスト、Issue、またはその両方で発生するかどうかを指定します。 -### Issue event object common properties +### Issue イベントオブジェクトの共通プロパティ -Issue events all have the same object structure, except events that are only available in the Timeline Events API. Some events also include additional properties that provide more context about the event resources. Refer to the specific event to for details about any properties that differ from this object format. +タイムラインイベント API でのみ使用可能なイベントを除いて、Issue イベントはすべて同じオブジェクト構造になっています。 一部のイベントには、イベントリソースに関するより多くのコンテキストを提供する追加のプロパティも含まれています。 このオブジェクト形式とは異なるプロパティの詳細については、特定のイベントを参照してください。 {% data reusables.issue-events.issue-event-common-properties %} ### added_to_project -The issue or pull request was added to a project board. {% data reusables.projects.disabled-projects %} +Issue またはプルリクエストがプロジェクトボードに追加された。 {% data reusables.projects.disabled-projects %} -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -40,171 +40,171 @@ The issue or pull request was added to a project board. {% data reusables.projec ### アサイン -The issue or pull request was assigned to a user. +Issueまたはプルリクエストがユーザに割り当てられた。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.assignee-properties %} ### automatic_base_change_failed -GitHub unsuccessfully attempted to automatically change the base branch of the pull request. +GitHub がプルリクエストのベースブランチを自動的に変更しようとしたが失敗した。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### automatic_base_change_succeeded -GitHub successfully attempted to automatically change the base branch of the pull request. +GitHub がプルリクエストのベースブランチを自動的に変更しようとした。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### base_ref_changed -The base reference branch of the pull request changed. +プルリクエストのベースリファレンスブランチが変更された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | | - ### Event object properties + ### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### closed -The issue or pull request was closed. When the `commit_id` is present, it identifies the commit that closed the issue using "closes / fixes" syntax. For more information about the syntax, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". +Issue またはプルリクエストがクローズされた。 `commit_id` が存在する場合、「closes / fixes」構文を使用して Issue をクローズしたコミットを識別します。 構文に関する詳しい情報については「[プルリクエストを Issue にリンクする](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)」を参照してください。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### コメント -A comment was added to the issue or pull request. +Issue またはプルリクエストにコメントが追加された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.timeline_events_object_properties %} -| 名前 | 種類 | 説明 | -| -------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -| `url` | `string` | The REST API URL to retrieve the issue comment. | -| `html_url` | `string` | The HTML URL of the issue comment. | -| `issue_url` | `string` | The HTML URL of the issue. | -| `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | -| `ユーザ` | `オブジェクト` | The person who commented on the issue. | -| `created_at` | `string` | The timestamp indicating when the comment was added. | -| `updated_at` | `string` | The timestamp indicating when the comment was updated or created, if the comment is never updated. | -| `author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment. | -| `body` | `string` | The comment body text. | -| `event` | `string` | The event value is `"commented"`. | -| `actor` | `オブジェクト` | The person who generated the event. | +| 名前 | 種類 | 説明 | +| -------------------- | --------- | ----------------------------------------------------------------------- | +| `url` | `string` | Issue コメントを取得する REST API URL。 | +| `html_url` | `string` | Issue コメントの HTML URL。 | +| `issue_url` | `string` | Issue の HTML URL。 | +| `id` | `integer` | イベントの一意の識別子。 | +| `node_id` | `string` | イベントの[グローバルノード ID](/graphql/guides/using-global-node-ids)。 | +| `ユーザ` | `オブジェクト` | この Issue についてコメントしたユーザ。 | +| `created_at` | `string` | コメントの追加日時を示すタイムスタンプ。 | +| `updated_at` | `string` | コメントが更新されていない場合に、コメントの更新または作成日時を示すタイムスタンプ。 | +| `author_association` | `string` | Issue のリポジトリでユーザが保持している権限。 たとえば、リポジトリの所有者がコメントを作成した場合、値は「`OWNER`」になります。 | +| `body` | `string` | コメント本文テキスト。 | +| `event` | `string` | イベントの値は `"commented"` です。 | +| `actor` | `オブジェクト` | イベントを生成したユーザ。 | ### committed -A commit was added to the pull request's `HEAD` branch. +プルリクエストの `HEAD` ブランチにコミットが追加された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.timeline_events_object_properties %} -| 名前 | 種類 | 説明 | -| ------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `sha` | `string` | The SHA of the commit in the pull request. | -| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | -| `url` | `string` | The REST API URL to retrieve the commit. | -| `html_url` | `string` | The HTML URL of the commit. | -| `作者` | `オブジェクト` | The person who authored the commit. | -| `コミッター` | `オブジェクト` | The person who committed the commit on behalf of the author. | -| `ツリー` | `オブジェクト` | The Git tree of the commit. | -| `message` | `string` | コミットメッセージ。 | -| `親` | `array of objects` | A list of parent commits. | -| `verfication` | `オブジェクト` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#signature-verification-object)." | -| `event` | `string` | The event value is `"committed"`. | +| 名前 | 種類 | 説明 | +| ------------- | ------------------ | ---------------------------------------------------------------------------------------------------- | +| `sha` | `string` | プルリクエスト内のコミットの SHA。 | +| `node_id` | `string` | イベントの[グローバルノード ID](/graphql/guides/using-global-node-ids)。 | +| `url` | `string` | コミットを取得する REST API URL。 | +| `html_url` | `string` | コミットの HTML URL。 | +| `作者` | `オブジェクト` | コミットの作者。 | +| `コミッター` | `オブジェクト` | 作者に代わってコミットしたユーザ。 | +| `ツリー` | `オブジェクト` | コミットの Git ツリー。 | +| `message` | `string` | コミットメッセージ。 | +| `親` | `array of objects` | 親コミットのリスト。 | +| `verfication` | `オブジェクト` | コミットの署名の検証結果。 詳しい情報については、「[署名検証オブジェクト](/rest/reference/git#signature-verification-object)」を参照してください。 | +| `event` | `string` | イベントの値は `"committed"` です。 | ### connected -The issue or pull request was linked to another issue or 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)". +Issue またはプルリクエストが、別の Issue またはプルリクエストにリンクされた。 詳しい情報については「[プルリクエストを Issue にリンクする](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### convert_to_draft -The pull request was converted to draft mode. +プルリクエストがドラフトモードに変換された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### converted_note_to_issue -The issue was created by converting a note in a project board to an issue. {% data reusables.projects.disabled-projects %} +Issue がプロジェクトボードのメモを Issue に変換して作成された。 {% data reusables.projects.disabled-projects %} -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -214,139 +214,139 @@ The issue was created by converting a note in a project board to an issue. {% da ### cross-referenced -The issue or pull request was referenced from another issue or pull request. +Issue またはプルリクエストが、別の Issue またはプルリクエストから参照された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.timeline_events_object_properties %} -| 名前 | 種類 | 説明 | -| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `actor` | `オブジェクト` | The person who generated the event. | -| `created_at` | `string` | The timestamp indicating when the cross-reference was added. | -| `updated_at` | `string` | The timestamp indicating when the cross-reference was updated or created, if the cross-reference is never updated. | -| `資料` | `オブジェクト` | The issue or pull request that added a cross-reference. | -| `source[type]` | `string` | This value will always be `"issue"` because pull requests are of type issue. Only cross-reference events triggered by issues or pull requests are returned in the Timeline Events API. To determine if the issue that triggered the event is a pull request, you can check if the `source[issue][pull_request` object exists. | -| `source[issue]` | `オブジェクト` | The `issue` object that added the cross-reference. | -| `event` | `string` | The event value is `"cross-referenced"`. | +| 名前 | 種類 | 説明 | +| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `actor` | `オブジェクト` | イベントを生成したユーザ。 | +| `created_at` | `string` | クロスリファレンスの追加日時を示すタイムスタンプ。 | +| `updated_at` | `string` | クロスリファレンスが更新されていない場合、クロスリファレンスの更新または作成時期を示すタイムスタンプ。 | +| `資料` | `オブジェクト` | クロスリファレンスを追加した Issue またはプルリクエスト。 | +| `source[type]` | `string` | プルリクエストは Issue タイプのため、この値は常に `"issue"` になります。 タイムラインイベント API では、Issue またはプルリクエストによってトリガーされたクロスリファレンスイベントのみが返されます。 イベントをトリガーした Issue がプルリクエストかどうかを判断するには、`source[issue][pull_request` オブジェクトの有無を確認します。 | +| `source[issue]` | `オブジェクト` | クロスリファレンスを追加した `issue` オブジェクト。 | +| `event` | `string` | イベントの値は `"cross-referenced"` です。 | ### demilestoned -The issue or pull request was removed from a milestone. +Issue またはプルリクエストがマイルストーンから削除された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} -`milestone` | `object` | The milestone object. `milestone[title]` | `string` | The title of the milestone. +`milestone` | `object` | マイルストーンオブジェクト。 `milestone[title]` | `string` | マイルストーンのタイトル。 ### deployed -The pull request was deployed. +プルリクエストがデプロイされた。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### deployment_environment_changed -The pull request deployment environment was changed. +プルリクエストのデプロイメント環境が変更された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### disconnected -The issue or pull request was unlinked from another issue or 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)". +Issue またはプルリクエストが、別の Issue またはプルリクエストからリンク解除された。 詳しい情報については「[プルリクエストを Issue にリンクする](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### head_ref_deleted -The pull request's `HEAD` branch was deleted. +プルリクエストの `HEAD` ブランチが削除された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### head_ref_restored -The pull request's `HEAD` branch was restored to the last known commit. +プルリクエストの `HEAD` ブランチが最後の既知のコミットに復元された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### labeled -A label was added to the issue or pull request. +Issue またはプルリクエストにラベルが追加された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.label-properties %} ### locked -The issue or pull request was locked. +Issue またはプルリクエストがロックされた。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% data reusables.pre-release-program.sailor-v-preview %} @@ -354,137 +354,137 @@ The issue or pull request was locked. {% endif %} {% data reusables.issue-events.issue-event-common-properties %} -`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided. +`lock_reason` | `string` | Issue またはプルリクエストの会話がロックされた理由（提供されている場合）。 ### メンション -The `actor` was `@mentioned` in an issue or pull request body. +`actor` が Issue またはプルリクエストの本文で `@mentioned` された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### marked_as_duplicate -A user with write permissions marked an issue as a duplicate of another issue, or a pull request as a duplicate of another pull request. +書き込み権限を持つユーザが、Issue を別の Issue の複製としてマークしたか、プルリクエストを別のプルリクエストの複製としてマークした。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### merged -The pull request was merged. The `commit_id` attribute is the SHA1 of the `HEAD` commit that was merged. The `commit_repository` is always the same as the main repository. +プルリクエストがマージされた。 `commit_id` 属性は、マージされた `HEAD` コミットのSHA1 です。 `commit_repository` は、常にメインリポジトリと同じです。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### milestoned -The issue or pull request was added to a milestone. +Issue またはプルリクエストがマイルストーンに追加された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} -`milestone` | `object` | The milestone object. `milestone[title]` | `string` | The title of the milestone. +`milestone` | `object` | マイルストーンオブジェクト。 `milestone[title]` | `string` | マイルストーンのタイトル。 ### moved_columns_in_project -The issue or pull request was moved between columns in a project board. {% data reusables.projects.disabled-projects %} +Issue またはプルリクエストがプロジェクトボードの列間で移動された。 {% data reusables.projects.disabled-projects %} -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.project-card-properties %} -`previous_column_name` | `string` | The name of the column the issue was moved from. +`previous_column_name` | `string` | Issue の移動元の列の名前。 ### ピン止め済み -The issue was pinned. +Issue がピン留めされた。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### ready_for_review -A pull request was created that is not in draft mode. +ドラフトモードではないプルリクエストが作成された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### referenced -The issue was referenced from a commit message. The `commit_id` attribute is the commit SHA1 of where that happened and the commit_repository is where that commit was pushed. +Issue がコミットメッセージから参照された。 `commit_id` 属性は、発生した場所のコミット SHA1 であり、commit_repository は、そのコミットがプッシュされた場所です。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### removed_from_project -The issue or pull request was removed from a project board. {% data reusables.projects.disabled-projects %} +Issue またはプルリクエストがプロジェクトボードから削除された。 {% data reusables.projects.disabled-projects %} -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.pre-release-program.starfox-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -494,176 +494,176 @@ The issue or pull request was removed from a project board. {% data reusables.pr ### renamed -The issue or pull request title was changed. +Issue またはプルリクエストのタイトルが変更された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} -`rename` | `object` | The name details. `rename[from]` | `string` | The previous name. `rename[to]` | `string` | The new name. +`rename` | `object` | 名前の詳細。 `rename[from]` | `string` | 以前の名前。 `rename[to]` | `string` | 新しい名前。 ### reopened -The issue or pull request was reopened. +Issue またはプルリクエストが再開された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### review_dismissed -The pull request review was dismissed. +プルリクエストのレビューが却下された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-dismissed-properties %} ### review_requested -A pull request review was requested. +プルリクエストのレビューがリクエストされた。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-request-properties %} ### review_request_removed -A pull request review request was removed. +プルリクエストのレビューリクエストが削除された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.review-request-properties %} ### reviewed -The pull request was reviewed. +プルリクエストがレビューされた。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • プルリクエスト
| | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • プルリクエスト
| | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.timeline_events_object_properties %} -| 名前 | 種類 | 説明 | -| -------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | -| `ユーザ` | `オブジェクト` | The person who commented on the issue. | -| `body` | `string` | The review summary text. | -| `commit_id` | `string` | The SHA of the latest commit in the pull request at the time of the review. | -| `submitted_at` | `string` | The timestamp indicating when the review was submitted. | -| `state` | `string` | The state of the submitted review. Can be one of: `commented`, `changes_requested`, or `approved`. | -| `html_url` | `string` | The HTML URL of the review. | -| `pull_request_url` | `string` | The REST API URL to retrieve the pull request. | -| `author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment. | -| `_links` | `オブジェクト` | The `html_url` and `pull_request_url`. | -| `event` | `string` | The event value is `"reviewed"`. | +| 名前 | 種類 | 説明 | +| -------------------- | --------- | ----------------------------------------------------------------------- | +| `id` | `integer` | イベントの一意の識別子。 | +| `node_id` | `string` | イベントの[グローバルノード ID](/graphql/guides/using-global-node-ids)。 | +| `ユーザ` | `オブジェクト` | この Issue についてコメントしたユーザ。 | +| `body` | `string` | レビューの概要テキスト。 | +| `commit_id` | `string` | レビュー時のプルリクエストの最新コミットの SHA。 | +| `submitted_at` | `string` | レビューの送信日時を示すタイムスタンプ。 | +| `state` | `string` | サブミットされたレビューの状態。 `commented`、`changes_requested`、`approved` のいずれかになります。 | +| `html_url` | `string` | レビューの HTML URL。 | +| `pull_request_url` | `string` | プルリクエストを取得する REST API URL。 | +| `author_association` | `string` | Issue のリポジトリでユーザが保持している権限。 たとえば、リポジトリの所有者がコメントを作成した場合、値は「`OWNER`」になります。 | +| `_links` | `オブジェクト` | `html_url` および `pull_request_url`。 | +| `event` | `string` | イベントの値は `"reviewed"` です。 | ### subscribed -Someone subscribed to receive notifications for an issue or pull request. +誰かが Issue またはプルリクエストの通知を受信するようにサブスクライブした。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### transferred -The issue was transferred to another repository. +Issue が別のリポジトリに転送された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### unassigned -A user was unassigned from the issue. +ユーザが Issue から割り当て解除された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.assignee-properties %} ### unlabeled -A label was removed from the issue. +Issue からラベルが削除された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} {% data reusables.issue-events.label-properties %} ### unlocked -The issue was unlocked. +Issue がロック解除された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} {% data reusables.pre-release-program.sailor-v-preview %} @@ -671,62 +671,62 @@ The issue was unlocked. {% endif %} {% data reusables.issue-events.issue-event-common-properties %} -`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided. +`lock_reason` | `string` | Issue またはプルリクエストの会話がロックされた理由（提供されている場合）。 ### unmarked_as_duplicate -An issue that a user had previously marked as a duplicate of another issue is no longer considered a duplicate, or a pull request that a user had previously marked as a duplicate of another pull request is no longer considered a duplicate. +ユーザが以前に別の Issue の複製としてマークした Issue が重複と見なされなくなった。または、ユーザが以前に別のプルリクエストの複製としてマークしたプルリクエストが重複と見なされなくなった。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### unpinned -The issue was unpinned. +Issue がピン留め解除された。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} ### サブスクライブ解除 -Someone unsubscribed from receiving notifications for an issue or pull request. +誰かが Issue またはプルリクエストの通知を受信しないようにサブスクライブ解除した。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} {% if currentVersion == "free-pro-team@latest" %} ### user_blocked -An organization owner blocked a user from the organization. This was done [through one of the blocked user's comments on the issue](/articles/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment). +Organization のオーナーがユーザを Organization からブロックした。 これは、[Issue に関するブロックされたユーザのコメントの 1 つを介して](/articles/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment)行われました。 -#### Availability +#### 利用の可否 -| Issue type | Issue events API | Timeline events API | -|:-------------------------- |:----------------:|:-------------------:| -|
  • 問題
  • プルリクエスト
| **X** | **X** | +| Issue タイプ | Issue イベント API | タイムラインイベント API | +|:-------------------------- |:--------------:|:--------------:| +|
  • 問題
  • プルリクエスト
| **X** | **X** | -#### Event object properties +#### イベントオブジェクトのプロパティ {% data reusables.issue-events.issue-event-common-properties %} 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 5586858312..4c5782e34e 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 @@ -1,6 +1,6 @@ --- -title: Securing your webhooks -intro: 'Ensure your server is only receiving the expected {% data variables.product.prodname_dotcom %} requests for security reasons.' +title: webhook のセキュリティ保護 +intro: 'セキュリティ上の理由から、サーバーが想定されているる {% data variables.product.prodname_dotcom %} リクエストのみを受信していることを確認する必要があります。' redirect_from: - /webhooks/securing versions: @@ -11,41 +11,41 @@ versions: -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. +ペイロードを受信するようにサーバーが設定されると、設定したエンドポイントに送信されたペイロードがリッスンされます。 セキュリティ上の理由から、GitHub からのリクエストに制限することをお勧めします。 これを行うにはいくつかの方法があります。たとえば、GitHub の IP アドレスからのリクエストを許可することですが、はるかに簡単な方法は、シークレットトークンを設定して情報を検証することです。 {% data reusables.webhooks.webhooks-rest-api-links %} -### Setting your secret token +### シークレットトークンを設定する -You'll need to set up your secret token in two places: GitHub and your server. +シークレットトークンは、GitHub とサーバーの 2 か所に設定する必要があります。 -To set your token on GitHub: +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. webhook を設定しているリポジトリに移動します。 +2. シークレットテキストボックスに入力します。 エントロピーの高いランダムな文字列を使用します (たとえば、`ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` を端末で取得することによって)。 ![webhook シークレットトークンフィールド](/assets/images/webhook_secret_token.png) +3. [**Update Webhook**] をクリックします。 -Next, set up an environment variable on your server that stores this token. Typically, this is as simple as running: +次に、このトークンを保存する環境変数をサーバーに設定します。 通常、これは実行と同じくらい簡単です。 ```shell $ export SECRET_TOKEN=your_token ``` -**Never** hardcode the token into your app! +トークンをアプリケーションにハードコーディング**しないでください**。 -### Validating payloads from GitHub +### 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 %}. +シークレットトークンが設定されると、{% data variables.product.product_name %} はそれを使用して各ペイロードでハッシュ署名を作成します。 このハッシュ署名は、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`X-Hub-Signature-256`{% elsif currentVersion ver_lt "enterprise-server@2.23" %}`X-Hub-Signature` として各リクエストのヘッダに含まれています{% endif %}。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} {% note %} -**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. +**注釈:** 下位互換性のために、SHA-1 ハッシュ関数を使用して生成される `X-Hub-Signature` ヘッダーも含まれています。 可能であれば、セキュリティを向上させるために `X-Hub-Signature-256` ヘッダを使用することをお勧めします。 以下は、`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: +たとえば、webhook をリッスンする基本的なサーバーがある場合、次のように設定されている可能性があります。 ``` ruby require 'sinatra' @@ -57,7 +57,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: +目的は、`SECRET_TOKEN` を使用してハッシュを計算し、結果が {% data variables.product.product_name %} のハッシュと一致することを確認することです。 {% data variables.product.product_name %} は HMAC hex digest を使用してハッシュを計算するため、サーバーを次のように再設定できます。 ``` ruby post '/payload' do @@ -79,10 +79,10 @@ 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: +言語とサーバーの実装は、この例で使用したコードとは異なる場合があります。 ただし、次のようないくつかの非常に重要な事項があります。 -* 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. +* どの実装を使用する場合でも、ハッシュ署名は {% 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 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`][secure_compare] のようなメソッドは、「一定時間」の文字列比較を実行します。これは、通常の等式演算子に対する特定のタイミング攻撃を軽減するのに役立ちます。 [secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare diff --git a/translations/ja-JP/content/developers/webhooks-and-events/testing-webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/testing-webhooks.md index 1a3b1fb164..1d54b52861 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/testing-webhooks.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/testing-webhooks.md @@ -1,6 +1,6 @@ --- title: webhookのテスト -intro: 'Review your webhook deliveries on {% data variables.product.prodname_dotcom %}, including the HTTP Request and payload as well as the response.' +intro: '{% data variables.product.prodname_dotcom %} で webhook のデリバリを確認します。これには、HTTP リクエストとペイロード、およびレスポンスが含まれます。' redirect_from: - /webhooks/testing versions: @@ -10,28 +10,28 @@ versions: --- -Now that you've [configured your local server](/webhooks/configuring/), you might be interested in pushing your code to the limits. To that end, GitHub's webhooks view provides some tooling for testing your deployed payloads. +[ローカルサーバーを設定](/webhooks/configuring/)したら、次にコードを制限までプッシュしてみることができます。 そのために、GitHub の webhook ビューは、デプロイされたペイロードをテストするためのツールを提供しています。 -### Listing recent deliveries +### 最近のデリバリの一覧表示 -Every webhook has its own "Recent Deliveries" section, which lists, at a glance whether a delivery was successful (green check) or failed (red x). You can also identify when each delivery was attempted. +すべての webhook には独自の \[Recent Deliveries\] (最近のデリバリ) セクションがあり、デリバリの成功（緑色のチェック）や失敗（赤色の x）が一目でわかります。 また、各デリバリの試行時期を特定することもできます。 -{% data variables.product.product_name %} keeps a log of each webhook delivery for {% if currentVersion == "free-pro-team@latest" %} 30 {% else %} 8 {% endif %} days. +{% data variables.product.product_name %} は、各 webhook デリバリのログを {% if currentVersion == "free-pro-team@latest" %} 30 {% else %} 8 {% endif %} 日間保持します。 ![[Recent Deliveries] ビュー](/assets/images/webhooks_recent_deliveries.png) -### Digging into results +### 結果を詳しく確認する -By expanding an individual delivery, you'll be able to witness *precisely* what information GitHub is attempting to send to your server. This includes both the HTTP Request and Response. +個別のデリバリを展開すると、GitHub がサーバーに送信しようとしている情報を*正確に*確認できます。 これには、HTTP リクエストとレスポンスの両方が含まれます。 -#### Request +#### リクエスト -The webhook delivery view provides information on which Headers were sent by GitHub. It also includes details about the JSON payload. +webhook デリバリ ビューには、GitHub によって送信されたヘッダに関する情報が表示されます。 これには、JSON ペイロードに関する詳細も含まれています。 -![Viewing a payload request](/assets/images/payload_request_tab.png) +![ペイロードリクエストの表示](/assets/images/payload_request_tab.png) #### レスポンス -The response tab lists how your server replied once it received the payload from GitHub. This includes the status code, the headers, and any additional data within the response body. +[Response] タブには、サーバーが GitHub からペイロードを受信した後の応答方法が一覧表示されます。 これには、ステータスコード、ヘッダ、およびレスポンス本文内の追加データが含まれます。 ![ペイロードレスポンスの表示](/assets/images/payload_response_tab.png) diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md index 77798fb53d..5cb9f75a8a 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -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: webhook イベントとペイロード +intro: 'webhook イベントごとに、イベントの発生日時、ペイロードの例、およびペイロードオブジェクトパラメータに関する説明を確認できます。' product: '{% data reusables.gated-features.enterprise_account_webhooks %}' redirect_from: - /early-access/integrations/webhooks/ @@ -19,44 +19,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. 詳しい情報については「[webhook を作成する](/webhooks/creating/)」を参照してください。 +このページに表示されているイベントをサブスクライブする webhook を作成できます。 各 webhook イベントには、webhook プロパティの説明とペイロードの例が含まれています。 詳しい情報については「[webhook を作成する](/webhooks/creating/)」を参照してください。 -### Webhook payload object common properties +### webhook ペイロードオブジェクトの共通プロパティ -Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections. +各 webhook イベントペイロードには、イベント固有のプロパティも含まれています。 固有のプロパティは、個々のイベントタイプのセクションにあります。 -| キー | 種類 | 説明 | -| -------- | -------- | ---------------------------------------------------------------------------------------------------------------- | -| `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. +| キー | 種類 | 説明 | +| -------- | -------- | ---------------------------------------------------------------------- | +| `action` | `string` | ほとんどの webhook ペイロードには、イベントをトリガーした特定のアクティビティを含む `action` プロパティが含まれています。 | +{% data reusables.webhooks.sender_desc %} このプロパティは、すべての webhook ペイロードに含まれています。 +{% data reusables.webhooks.repo_desc %} イベントがリポジトリ内のアクティビティから発生した場合、webhook ペイロードには `repository` プロパティが含まれます。 {% 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 %} 詳しい情報については、「[{% 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. +webhook イベントの一意のプロパティは、[イベント API](/rest/reference/activity#events) を使用するときに `payload` プロパティにあるプロパティと同じです。 例外の 1 つは、[`push` イベント](#push) です。 `push` イベント webhook ペイロードの一意のプロパティとイベント API の`payload` プロパティは異なります。 webhook ペイロードには、より詳細な情報が含まれています。 {% 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. +**注釈:** ペイロードの上限は 25 MB です。 イベントにより大きなペイロードが生成された場合、webhook は起動しません。 これは、たとえば多数のブランチまたはタグが一度にプッシュされた場合の `create` イベントで発生する可能性があります。 確実にデリバリが行われるよう、ペイロードサイズを監視することをお勧めします。 {% endtip %} -#### Delivery headers +#### デリバリヘッダ -HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers: +webhook によって設定されている URL エンドポイントに配信される HTTP POST ペイロードには、いくつかの特別なヘッダが含まれています。 -| ヘッダ | 説明 | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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 %} +| ヘッダ | 説明 | +| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `X-GitHub-Event` | デリバリをトリガーしたイベントの名前。 | +| `X-GitHub-Delivery` | デリバリを識別するための [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier)。{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| `X-GitHub-Enterprise-Version` | HTTP POST ペイロードを送信した {% data variables.product.prodname_ghe_server %} インスタンスのバージョン。 | +| `X-GitHub-Enterprise-Host` | HTTP POST ペイロードを送信した {% data variables.product.prodname_ghe_server %} インスタンスのホスト名。{% endif %}{% if currentVersion != "github-ae@latest" %} +| `X-Hub-Signature` | このヘッダは、webhook が [`secret`](/rest/reference/repos#create-hook-config-params) で設定されている場合に送信されます。 これはリクエスト本文の HMAC hex digest であり、SHA-1 ハッシュ関数と HMAC `key`としての `secret` を使用して生成されます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} `X-Hub-Signature` は、既存の統合との互換性のために提供されているため、より安全な `X-Hub-Signature-256` を代わりに使用することをお勧めします。{% 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` | このヘッダは、webhook が [`secret`](/rest/reference/repos#create-hook-config-params) で設定されている場合に送信されます。 これはリクエスト本文の HMAC hex digest であり、SHA-256 ハッシュ関数と HMAC `key` としての `secret` を使用して生成されます。{% endif %} -Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. +また、リクエストの `User-Agent` には、プレフィックスに `GitHub-Hookshot/` が付けられます。 -#### Example delivery +#### デリバリの例 ```shell > POST /payload HTTP/1.1 @@ -103,13 +103,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 +#### 利用の可否 -- 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. +- リポジトリ webhook は、リポジトリ内の `created` および `completed` イベントタイプのペイロードのみを受信します +- Organization webhook は、リポジトリで `created` および `completed` イベントタイプのペイロードのみを受信します +- `checks:read` 権限のある {% data variables.product.prodname_github_app %} は、アプリがインストールされているリポジトリで発生する `created` および `completed` イベントのペイロードを受信します。 `rerequested` および `requested_action` イベントタイプを受信するには、アプリケーションに `checks:write` 権限が必要です。 `rerequested` および `requested_action` イベントタイプのペイロードは、リクエストされている {% data variables.product.prodname_github_app %} にのみ送信されます。 `checks:write` のある {% data variables.product.prodname_github_app %} は、この webhook イベントに自動的にサブスクライブされます。 -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.check_run_properties %} {% data reusables.webhooks.repo_desc %} @@ -117,7 +117,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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.check_run.created }} @@ -127,13 +127,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 +#### 利用の可否 -- 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. +- リポジトリ webhook は、リポジトリ内の `completed` イベントタイプのペイロードのみを受信します +- Organization webhook は、リポジトリで `completed` イベントタイプのペイロードのみを受信します +- `checks:read` 権限のある {% data variables.product.prodname_github_app %} は、アプリがインストールされているリポジトリで発生する `created` および `completed` イベントのペイロードを受信します。 `requested` および `rerequested` イベントタイプを受信するには、アプリケーションに `checks:write` 権限が必要です。 `requested` および `rerequested` イベントタイプのペイロードは、リクエストされている {% data variables.product.prodname_github_app %} にのみ送信されます。 `checks:write` のある {% data variables.product.prodname_github_app %} は、この webhook イベントに自動的にサブスクライブされます。 -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.check_suite_properties %} {% data reusables.webhooks.repo_desc %} @@ -141,30 +141,30 @@ 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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.check_suite.completed }} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### code_scanning_alert {% data reusables.webhooks.code_scanning_alert_event_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `security_events :read` permission +- リポジトリ webhook +- Organization webhook +- `security_events :read` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### 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. +`sender` | `object` | `action` が `reopened_by_user` または `closed_by_user` の場合、`sender` オブジェクトは、イベントをトリガーしたユーザになります。 `sender` オブジェクトは、他のすべてのアクションでは空になっています。 -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }} @@ -172,13 +172,13 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {% data reusables.webhooks.commit_comment_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- リポジトリ webhook +- Organization webhook +- `contents` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.commit_comment_properties %} {% data reusables.webhooks.repo_desc %} @@ -186,7 +186,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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.commit_comment.created }} {% endif %} @@ -195,11 +195,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. +webhook イベントは、登録したドメインの特異性に基づいてトリガーされます。 たとえば、サブドメイン (`https://subdomain.example.com`) を登録すると、サブドメインの URL のみがこのイベントをトリガーします。 ドメイン (`https://example.com`) を登録すると、ドメインとすべてのサブドメインの URL がこのイベントをトリガーします。 新しいコンテンツ添付ファイルを作成するには、「[コンテンツ添付ファイルの作成](/rest/reference/apps#create-a-content-attachment)」を参照してください。 -Only {% data variables.product.prodname_github_app %}s can receive this event. {% data variables.product.prodname_github_app %}s must have the `content_references` `write` permission to subscribe to this event. +このイベントを受信できるのは {% data variables.product.prodname_github_app %} のみです。 {% data variables.product.prodname_github_app %} には、このイベントをサブスクライブするための `content_references` `write` 権限が必要です。 -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.content_reference.created }} @@ -209,17 +209,17 @@ 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. +**注釈:** 一度に 3 つ以上のタグをプッシュすると、このイベントの webhook を受信しません。 {% endnote %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- リポジトリ webhook +- Organization webhook +- `contents` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.create_properties %} {% data reusables.webhooks.repo_desc %} @@ -227,7 +227,7 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.create }} @@ -237,17 +237,17 @@ 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. +**注釈:** 一度に 3 つ以上のタグを削除すると、このイベントの webhook を受信しません。 {% endnote %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- リポジトリ webhook +- Organization webhook +- `contents` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.delete_properties %} {% data reusables.webhooks.repo_desc %} @@ -255,7 +255,7 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.delete }} @@ -263,19 +263,19 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.deploy_key_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks +- リポジトリ webhook +- Organization webhook -#### Webhook payload object +#### 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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.deploy_key.created }} @@ -283,24 +283,24 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.deployment_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `deployments` permission +- リポジトリ webhook +- Organization webhook +- `deployments` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| `action` | `string` | 実行されたアクション。 Can be `created`.{% endif %} -| `deployment` | `オブジェクト` | The [deployment](/rest/reference/repos#list-deployments). | +| キー | 種類 | 説明 | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| `action` | `string` | 実行されたアクション。 `created` を指定可。{% endif %} +| `deployment` | `オブジェクト` | [デプロイメント](/rest/reference/repos#list-deployments)。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.deployment }} @@ -308,28 +308,28 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.deployment_status_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `deployments` permission +- リポジトリ webhook +- Organization webhook +- `deployments` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| `action` | `string` | 実行されたアクション。 Can be `created`.{% endif %} -| `deployment_status` | `オブジェクト` | 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` | `オブジェクト` | The [deployment](/rest/reference/repos#list-deployments) that this status is associated with. | +| キー | 種類 | 説明 | +| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} +| `action` | `string` | 実行されたアクション。 `created` を指定可。{% endif %} +| `deployment_status` | `オブジェクト` | [デプロイメントステータス](/rest/reference/repos#list-deployment-statuses)。 | +| `deployment_status["state"]` | `string` | 新しい状態。 `pending`、`success`、`failure`、`error` のいずれかを指定可。 | +| `deployment_status["target_url"]` | `string` | ステータスに追加されたオプションのリンク。 | +| `deployment_status["description"]` | `string` | オプションの人間可読の説明がステータスに追加。 | +| `deployment` | `オブジェクト` | このステータスが関連付けられている [デプロイメント](/rest/reference/repos#list-deployments)。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.deployment_status }} @@ -339,17 +339,17 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.enterprise_short_desc %} -#### Availability +#### 利用の可否 -- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." +- GitHub Enterprise webhook。 詳しい情報については「[グローバル webhook](/rest/reference/enterprise-admin#global-webhooks/)」を参照してください。 -#### Webhook payload object +#### webhook ペイロードオブジェクト | キー | 種類 | 説明 | | -------- | -------- | ----------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 Can be `anonymous_access_enabled` or `anonymous_access_disabled`. | +| `action` | `string` | 実行されたアクション。 `anonymous_access_enabled`、`anonymous_access_disabled` のいずれかを指定可。 | -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }} @@ -359,13 +359,13 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.fork_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- リポジトリ webhook +- Organization webhook +- `contents` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.fork_properties %} {% data reusables.webhooks.repo_desc %} @@ -373,28 +373,28 @@ Only {% data variables.product.prodname_github_app %}s can receive this event. { {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### 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. +{% data variables.product.prodname_github_app %} の承認を取り消すと、このイベントが発生します。 {% data variables.product.prodname_github_app %} は、デフォルトでこの webhook を受信し、このイベントをサブスクライブ解除できません。 -{% 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 %}{% data variables.product.prodname_github_app %} 認証を必要とするユーザからサーバーへのリクエストの詳細については、「[{% data variables.product.prodname_github_app %} のユーザーの識別と認証](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)」を参照してください。 -#### Availability +#### 利用の可否 -- {% data variables.product.prodname_github_app %}s +- {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| -------- | -------- | ----------------------------- | -| `action` | `string` | 実行されたアクション。 Can be `revoked`. | +| キー | 種類 | 説明 | +| -------- | -------- | --------------------------- | +| `action` | `string` | 実行されたアクション。 `revoked` を指定可。 | {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }} @@ -402,13 +402,13 @@ When someone revokes their authorization of a {% data variables.product.prodname {% data reusables.webhooks.gollum_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- リポジトリ webhook +- Organization webhook +- `contents` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.gollum_properties %} {% data reusables.webhooks.repo_desc %} @@ -416,7 +416,7 @@ When someone revokes their authorization of a {% data variables.product.prodname {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.gollum }} @@ -433,22 +433,22 @@ When someone revokes their authorization of a {% data variables.product.prodname {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@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/)." +**注釈:** {% data reusables.pre-release-program.suspend-installation-beta %} 詳しい情報については、「[{% data variables.product.prodname_github_app %} のインストールをサスペンドする](/apps/managing-github-apps/suspending-a-github-app-installation/)」を参照してください。 {% endnote %} {% endif %} -#### Availability +#### 利用の可否 -- {% data variables.product.prodname_github_app %}s +- {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.installation_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.installation.deleted }} @@ -462,17 +462,17 @@ When someone revokes their authorization of a {% data variables.product.prodname {% endnote %} -#### Availability +#### 利用の可否 -- {% data variables.product.prodname_github_app %}s +- {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.installation_repositories_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.installation_repositories.added }} @@ -480,13 +480,13 @@ When someone revokes their authorization of a {% data variables.product.prodname {% data reusables.webhooks.issue_comment_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `issues` permission +- リポジトリ webhook +- Organization webhook +- `issues` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.issue_comment_webhook_properties %} {% data reusables.webhooks.issue_comment_properties %} @@ -495,7 +495,7 @@ When someone revokes their authorization of a {% data variables.product.prodname {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.issue_comment.created }} @@ -503,13 +503,13 @@ When someone revokes their authorization of a {% data variables.product.prodname {% data reusables.webhooks.issues_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `issues` permission +- リポジトリ webhook +- Organization webhook +- `issues` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.issue_webhook_properties %} {% data reusables.webhooks.issue_properties %} @@ -518,7 +518,7 @@ When someone revokes their authorization of a {% data variables.product.prodname {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example when someone edits an issue +#### Issue 編集時の webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.issues.edited }} @@ -526,48 +526,48 @@ When someone revokes their authorization of a {% data variables.product.prodname {% data reusables.webhooks.label_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `metadata` permission +- リポジトリ webhook +- Organization webhook +- `metadata` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ---------------------- | -------- | ------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be `created`, `edited`, or `deleted`. | -| `ラベル` | `オブジェクト` | The label that was added. | -| `変更` | `オブジェクト` | 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`. | +| キー | 種類 | 説明 | +| ---------------------- | -------- | ------------------------------------------------------------ | +| `action` | `string` | 実行されたアクション. `created`、`edited`、`deleted` のいずれかを指定可。 | +| `ラベル` | `オブジェクト` | ラベルが追加された。 | +| `変更` | `オブジェクト` | アクションが `edited` の場合のラベルへの変更。 | +| `changes[name][from]` | `string` | The previous version of the name if the action was `edited`. | +| `changes[color][from]` | `string` | アクションが `edited` の場合の以前のバージョンの色。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### 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/)." +GitHub Marketplace の購入に関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については、「[GitHub Marketplace](/marketplace/)」を参照してください。 -#### Availability +#### 利用の可否 -- {% data variables.product.prodname_github_app %}s +- {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- | -| `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.
| +| キー | 種類 | 説明 | +| -------- | -------- | ------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | [GitHub Marketplace](https://github.com/marketplace) プランに対して実行されたアクション。 次のいずれかになります。
  • 「purchased」- GitHub Marketplace プランを購入しました。 変更はアカウントですぐに有効になります。
  • 「pending_change」- GitHub Marketplace プランをダウングレードまたはキャンセルしたときに、アカウントで変更が発生することを示す「pending_change」イベントを受け取ります。 新しいプランまたはキャンセルは、支払いサイクルの終了時に有効になります。 「キャンセル」または「変更」イベントタイプは、支払いサイクルが終了し、キャンセルまたは新しいプランが有効になると送信されます。
  • 「pending_change_cancelled」- 保留中の変更をキャンセルしました。 保留中の変更には、支払いサイクルの終了時に有効になるプランのキャンセルとダウングレードが含まれます。
  • 「changed」- GitHub Marketplace プランをアップグレードまたはダウングレードしたため、変更がアカウントですぐに有効になります。
  • 「cancelled」- GitHub Marketplace プランをキャンセルし、最後の支払いサイクルが終了しました。 変更はアカウントですぐに有効になります。
| -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/). +このペイロードと各タイプの `action` のペイロードの詳細については、「[{% data variables.product.prodname_marketplace %} webhook イベント](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)」を参照してください。 -#### Webhook payload example when someone purchases the plan +#### プラン購入時の webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} @@ -577,13 +577,13 @@ For a detailed description of this payload and the payload for each type of `act {% data reusables.webhooks.member_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `members` permission +- リポジトリ webhook +- Organization webhook +- `members` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.member_webhook_properties %} {% data reusables.webhooks.member_properties %} @@ -592,7 +592,7 @@ For a detailed description of this payload and the payload for each type of `act {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.member.added }} @@ -600,43 +600,43 @@ For a detailed description of this payload and the payload for each type of `act {% data reusables.webhooks.membership_short_desc %} -#### Availability +#### 利用の可否 -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `members` permission +- Organization webhook +- `members` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.membership_properties %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.membership.removed }} ### メタ情報 -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. +このイベントが設定されている webhook が削除されました。 このイベントは、イベントがインストールされている特定のフックへの変更のみをリッスンします。 したがって、メタイベントを受信するフックごとに選択する必要があります。 -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks +- リポジトリ webhook +- Organization webhook -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| --------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 Can be `deleted`. | -| `hook_id` | `integer` | The id of the modified webhook. | -| `フック` | `オブジェクト` | The modified webhook. This will contain different keys based on the type of webhook it is: repository, organization, business, app, or GitHub Marketplace. | +| キー | 種類 | 説明 | +| --------- | --------- | ------------------------------------------------------------------------------------------------------------ | +| `action` | `string` | 実行されたアクション。 `deleted` を指定可。 | +| `hook_id` | `integer` | 変更された webhook の ID。 | +| `フック` | `オブジェクト` | 変更された webhook。 これには、webhook のタイプ (リポジトリ、Organization、ビジネス、アプリケーション、または GitHub Marketplace) に基づいて異なるキーが含まれます。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.meta.deleted }} @@ -644,13 +644,13 @@ The webhook this event is configured on was deleted. This event will only listen {% data reusables.webhooks.milestone_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission +- リポジトリ webhook +- Organization webhook +- `pull_requests` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.milestone_properties %} {% data reusables.webhooks.repo_desc %} @@ -658,7 +658,7 @@ The webhook this event is configured on was deleted. This event will only listen {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.milestone.created }} @@ -666,25 +666,25 @@ The webhook this event is configured on was deleted. This event will only listen {% data reusables.webhooks.organization_short_desc %} -#### Availability +#### 利用の可否 {% 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 +- GitHub Enterprise webhook は、`created` および `deleted` イベントのみを受信します。 詳しい情報については「[グローバル webhook](/rest/reference/enterprise-admin#global-webhooks/)」を参照してください。{% endif %} +- Organization webhook は、`deleted`、`added`、`removed`、`renamed`、`invited` イベントのみを受信します +- `members` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `action` | `string` | 実行されたアクション. Can be one of:{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, or `member_invited`. | -| `招待` | `オブジェクト` | The invitation for the user or email if the action is `member_invited`. | -| `membership` | `オブジェクト` | The membership between the user and the organization. Not present when the action is `member_invited`. | +| キー | 種類 | 説明 | +| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション. {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} `created`、{% endif %} `deleted`、`renamed`、`member_added`、`member_removed`、`member_invited` のいずれかを指定可。 | +| `招待` | `オブジェクト` | アクションが `member_invited` の場合、ユーザへの招待またはメール。 | +| `membership` | `オブジェクト` | ユーザと Organization 間のメンバーシップ。 アクションが `member_invited` の場合は存在しません。 | {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.organization.member_added }} @@ -694,42 +694,42 @@ The webhook this event is configured on was deleted. This event will only listen {% data reusables.webhooks.org_block_short_desc %} -#### Availability +#### 利用の可否 -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `organization_administration` permission +- Organization webhook +- `organization_administration` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| -------------- | -------- | --------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 Can be `blocked` or `unblocked`. | -| `blocked_user` | `オブジェクト` | Information about the user that was blocked or unblocked. | +| キー | 種類 | 説明 | +| -------------- | -------- | -------------------------------------------- | +| `action` | `string` | 実行されたアクション。 `blocked`、`unblocked` のいずれかを指定可。 | +| `blocked_user` | `オブジェクト` | ブロックまたはブロック解除されたユーザに関する情報。 | {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.org_block.blocked }} ### package -Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. +{% data variables.product.prodname_registry %} に関連するアクティビティ。 {% data reusables.webhooks.action_type_desc %} 詳しい情報については、「[Organization ユーザをブロックする](/rest/reference/orgs#blocking)」REST API を参照してください。 {% data variables.product.prodname_registry %} の詳細については、「[{% data variables.product.prodname_registry %} を使用してパッケージを管理する](/github/managing-packages-with-github-packages)」を参照してください。 -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks +- リポジトリ webhook +- Organization webhook -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.package_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.package.published }} {% endif %} @@ -738,24 +738,24 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.page_build_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `pages` permission +- リポジトリ webhook +- Organization webhook +- `pages` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ----- | --------- | -------------------------------------------------------------------------------------- | -| `id` | `integer` | The unique identifier of the page build. | -| `ビルド` | `オブジェクト` | The [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds) itself. | +| キー | 種類 | 説明 | +| ----- | --------- | -------------------------------------------------------------------------- | +| `id` | `integer` | ページビルドの一意の識別子。 | +| `ビルド` | `オブジェクト` | [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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.page_build }} @@ -763,25 +763,25 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.ping_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s receive a ping event with an `app_id` used to register the app +- リポジトリ webhook +- Organization webhook +- {% data variables.product.prodname_github_app %} は、アプリの登録に使用される `app_id` を使用して ping イベントを受信します -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| -------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `zen` | `string` | Random string of GitHub zen. | -| `hook_id` | `integer` | The ID of the webhook that triggered the ping. | -| `フック` | `オブジェクト` | 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. | +| キー | 種類 | 説明 | +| -------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `zen` | `string` | GitHub zen のランダムな文字列。 | +| `hook_id` | `integer` | ping をトリガーした webhook の ID。 | +| `フック` | `オブジェクト` | [webhook 設定](/rest/reference/repos#get-a-repository-webhook)。 | +| `hook[app_id]` | `integer` | 新しい {% data variables.product.prodname_github_app %} を登録すると、{% data variables.product.product_name %} は登録時に指定した **webhook URL** に ping イベントを送信します。 イベントには、アプリケーションの[認証](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/)に必要な `app_id` が含まれています。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.ping }} @@ -789,13 +789,13 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.project_card_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission +- リポジトリ webhook +- Organization webhook +- `repository_projects` または `organization_projects` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.project_card_properties %} {% data reusables.webhooks.repo_desc %} @@ -803,7 +803,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.project_card.created }} @@ -811,13 +811,13 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.project_column_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission +- リポジトリ webhook +- Organization webhook +- `repository_projects` または `organization_projects` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.project_column_properties %} {% data reusables.webhooks.repo_desc %} @@ -825,7 +825,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.project_column.created }} @@ -833,13 +833,13 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.project_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `repository_projects` or `organization_projects` permission +- リポジトリ webhook +- Organization webhook +- `repository_projects` または `organization_projects` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.project_properties %} {% data reusables.webhooks.repo_desc %} @@ -847,7 +847,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.project.created }} @@ -855,13 +855,13 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.public_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `metadata` permission +- リポジトリ webhook +- Organization webhook +- `metadata` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト | キー | 種類 | 説明 | | -- | -- | -- | @@ -871,7 +871,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.public }} @@ -879,13 +879,13 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.pull_request_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission +- リポジトリ webhook +- Organization webhook +- `pull_requests` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.pull_request_webhook_properties %} {% data reusables.webhooks.pull_request_properties %} @@ -894,9 +894,9 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 -Deliveries for `review_requested` and `review_request_removed` events will have an additional field called `requested_reviewer`. +`review_requested` イベントと `review_request_removed` イベントのデリバリには、`requested_reviewer` という追加のフィールドがあります。 {{ webhookPayloadsForCurrentVersion.pull_request.opened }} @@ -904,13 +904,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have {% data reusables.webhooks.pull_request_review_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission +- リポジトリ webhook +- Organization webhook +- `pull_requests` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.pull_request_review_properties %} {% data reusables.webhooks.repo_desc %} @@ -918,7 +918,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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }} @@ -926,13 +926,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have {% data reusables.webhooks.pull_request_review_comment_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `pull_requests` permission +- リポジトリ webhook +- Organization webhook +- `pull_requests` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.pull_request_review_comment_webhook_properties %} {% data reusables.webhooks.pull_request_review_comment_properties %} @@ -941,7 +941,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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }} @@ -951,48 +951,48 @@ 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. +**注釈:** 一度に 3 つ以上のタグをプッシュすると、このイベントの webhook を受信しません。 {% 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. +**注釈**: 表に続く webhook ペイロードの例は、表に記載されているイベント API ペイロードとは大幅に異なります。 違いの中でも、webhook ペイロードには `sender` オブジェクトと `pusher` オブジェクトの両方が含まれています。 送信者とプッシャーは `push` イベントを開始した同じユーザですが、`sender` オブジェクトには詳細が含まれています。 {% endtip %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- リポジトリ webhook +- Organization webhook +- `contents` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ref` | `string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | -| `before` | `string` | The SHA of the most recent commit on `ref` before the push. | -| `after` | `string` | The SHA of the most recent commit on `ref` after the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][id]` | `string` | コミットのSHA。 | -| `commits[][timestamp]` | `string` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `string` | コミットメッセージ。 | -| `commits[][author]` | `オブジェクト` | The git author of the commit. | -| `commits[][author][name]` | `string` | The git author's name. | -| `commits[][author][email]` | `string` | The git author's email address. | -| `commits[][url]` | `url` | URL that points to the commit API resource. | -| `commits[][distinct]` | `boolean` | Whether this commit is distinct from any that have been pushed before. | -| `commits[][added]` | `array` | An array of files added in the commit. | -| `commits[][modified]` | `array` | An array of files modified by the commit. | -| `commits[][removed]` | `array` | An array of files removed in the commit. | -| `pusher` | `オブジェクト` | The user who pushed the commits. | +| キー | 種類 | 説明 | +| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `ref` | `string` | プッシュされた完全な [`git ref`](/rest/reference/git#refs)。 例: `refs/heads/main`。 | +| `before` | `string` | プッシュ前の`ref` 上の最新のコミットのSHA。 | +| `after` | `string` | プッシュ後の`ref`上の最新のコミットのSHA。 | +| `commits` | `array` | プッシュされたコミットを示すコミットオブジェクトの配列。 （配列には最大で20のコミットが含まれる。 必要に応じて、[Commits API](/rest/reference/repos#commits) を使用して追加のコミットをフェッチできます。 この制限はタイムラインイベントにのみ適用され、webhookの配信には適用されない） | +| `commits[][id]` | `string` | コミットのSHA。 | +| `commits[][timestamp]` | `string` | コミットの ISO 8601 タイムスタンプ。 | +| `commits[][message]` | `string` | コミットメッセージ。 | +| `commits[][author]` | `オブジェクト` | コミットのGit作者。 | +| `commits[][author][name]` | `string` | Git作者の名前。 | +| `commits[][author][email]` | `string` | Git作者のメールアドレス。 | +| `commits[][url]` | `url` | コミットAPIのリソースを指すURL。 | +| `commits[][distinct]` | `boolean` | このコミットが以前にプッシュされたいずれとも異なっているか。 | +| `commits[][added]` | `array` | コミットに追加されたファイルの配列。 | +| `commits[][modified]` | `array` | コミットによって変更されたファイルの配列。 | +| `commits[][removed]` | `array` | コミットから削除されたファイルの配列。 | +| `pusher` | `オブジェクト` | コミットをプッシュしたユーザ。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.push }} @@ -1000,13 +1000,13 @@ Deliveries for `review_requested` and `review_request_removed` events will have {% data reusables.webhooks.release_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `contents` permission +- リポジトリ webhook +- Organization webhook +- `contents` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.release_webhook_properties %} {% data reusables.webhooks.release_properties %} @@ -1015,20 +1015,20 @@ Deliveries for `review_requested` and `review_request_removed` events will have {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### 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. +このイベントは、{% data variables.product.prodname_github_app %} が「[リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」エンドポイントに `POST` リクエストを送信したときに発生します。 -#### Availability +#### 利用の可否 -- {% data variables.product.prodname_github_app %}s must have the `contents` permission to receive this webhook. +- この webhook を受信するには、{% data variables.product.prodname_github_app %} に `contents` 権限が必要です。 -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.repository_dispatch }} {% endif %} @@ -1037,44 +1037,44 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% data reusables.webhooks.repository_short_desc %} -#### Availability +#### 利用の可否 -- 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` +- リポジトリ webhook は、`deleted` を除くすべてのイベントタイプを受け取ります +- Organization webhook +- `metadata` 権限のある {% data variables.product.prodname_github_app %} は、`deleted` を除くすべてのイベントタイプを受信します -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| -------- | -------- | -------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
| +| キー | 種類 | 説明 | +| -------- | -------- | ---------------------------------------------------- | +| `action` | `string` | 実行されたアクション. これは次のいずれかになります。
  • 「created」- リポジトリが作成されます。
  • 「deleted」- リポジトリが削除されます。
  • 「archived」- リポジトリがアーカイブされます。
  • 「unarchived」- リポジトリがアーカイブ解除されます。
    • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
  • 「anonymous_access_enabled」- リポジトリは [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)、「anonymous_access_disabled」 - リポジトリは [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
    • {% endif %}
  • 「edited」- リポジトリの情報が編集されます。
  • 「renamed」- リポジトリの名前が変更されます。
  • 「transferred」- リポジトリが転送されます。
  • 「publicized」- リポジトリが公開されます。
  • 「privatized」- リポジトリが非公開になります。
| {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### 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 %} 個人リポジトリでこのイベントを受信するには、インポートする前に空のリポジトリを作成する必要があります。 このイベントは、[GitHub Importer](/articles/importing-a-repository-with-github-importer/) または[Source imports API](/rest/reference/migrations#source-imports) のいずれかを使用してトリガーできます。 -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks +- リポジトリ webhook +- Organization webhook -#### Webhook payload object +#### 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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.repository_import }} @@ -1082,65 +1082,90 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% data reusables.webhooks.repository_vulnerability_alert_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks +- リポジトリ webhook +- Organization webhook -#### Webhook payload object +#### 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 +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }} {% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### secret_scanning_alert + +{% data reusables.webhooks.secret_scanning_alert_event_short_desc %} + +#### 利用の可否 + +- リポジトリ webhook +- Organization webhook +- `secret_scanning_alerts:read` 権限のある {% data variables.product.prodname_github_app %} + +#### 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` | `action` が `resolved` または `reopened` の場合、`sender` オブジェクトは、イベントをトリガーしたユーザになります。 `sender` オブジェクトは、他のすべてのアクションでは空になっています。 + +#### webhook ペイロードの例 + +{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} +{% endif %} + ### 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/)." +セキュリティアドバイザリに関連するアクティビティ。 セキュリティアドバイザリは、GitHub 上のソフトウェアのセキュリティ関連の脆弱性に関する情報を提供します。 セキュリティアドバイザリデータセットは、GitHub セキュリティアラートにも役立ちます。「[脆弱性のある依存関係のセキュリティアラートについて](/articles/about-security-alerts-for-vulnerable-dependencies/)」を参照してください。 -#### Availability +#### 利用の可否 -- {% data variables.product.prodname_github_app %}s with the `security_events` permission +- `security_events` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ------------------- | -------- | ----------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. The action can be one of `published`, `updated`, or `performed` for all new events. | -| `security_advisory` | `オブジェクト` | The details of the security advisory, including summary, description, and severity. | +| キー | 種類 | 説明 | +| ------------------- | -------- | ------------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション. アクションは、すべての新しいイベントに対して `published`、`updated`、`performed` のいずれかを指定可。 | +| `security_advisory` | `オブジェクト` | 概要、説明、重要度などの、セキュリティアドバイザリの詳細。 | -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.security_advisory.published }} {% if currentVersion == "free-pro-team@latest" %} -### sponsorship +### スポンサーシップ {% 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)". +スポンサーシップ webhook は、{% data variables.product.prodname_dotcom %} でのみ作成できます。 詳しい情報については、「[スポンサー付きアカウントのイベントの webhook を設定する](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)」を参照してください。 -#### Availability +#### 利用の可否 -- Sponsored accounts +- スポンサー付きアカウント -#### Webhook payload object +#### 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 +#### スポンサーシップ作成時の webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.sponsorship.created }} -#### Webhook payload example when someone downgrades a sponsorship +#### スポンサーシップのダウングレード時の webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }} @@ -1150,19 +1175,19 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ {% data reusables.webhooks.star_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks +- リポジトリ webhook +- Organization webhook -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.star_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.star.created }} @@ -1170,28 +1195,28 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ {% data reusables.webhooks.status_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `statuses` permission +- リポジトリ webhook +- Organization webhook +- `statuses` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ------------ | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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`. | -| `説明` | `string` | The optional human-readable description added to the status. | -| `target_url` | `string` | The optional link added to the status. | -| `ブランチ` | `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. | +| キー | 種類 | 説明 | +| ------------ | --------- | ------------------------------------------------------------------------------------------------------------- | +| `id` | `integer` | ステータスの一意の識別子。 | +| `sha` | `string` | コミット SHA。 | +| `state` | `string` | 新しい状態。 `pending`、`success`、`failure`、`error` のいずれかを指定可。 | +| `説明` | `string` | オプションの人間可読の説明がステータスに追加。 | +| `target_url` | `string` | ステータスに追加されたオプションのリンク。 | +| `ブランチ` | `array` | ステータスの SHA を含むブランチオブジェクトの配列。 各ブランチには特定の SHA が含まれていますが、SHA がブランチの先頭である場合とそうでない場合があります。 配列には最大 10 個のブランチが含まれます。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.status }} @@ -1199,29 +1224,29 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ {% data reusables.webhooks.team_short_desc %} -#### Availability +#### 利用の可否 -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `members` permission +- Organization webhook +- `members` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ----------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be one of `created`, `deleted`, `edited`, `added_to_repository`, or `removed_from_repository`. | -| `Team` | `オブジェクト` | The team itself. | -| `変更` | `オブジェクト` | 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`. | -| `リポジトリ` | `オブジェクト` | 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. | +| キー | 種類 | 説明 | +| ----------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション. `created`、 `deleted`、`edited`、`added_to_repository`、`removed_from_repository` のいずれかを指定可。 | +| `Team` | `オブジェクト` | Team 自体。 | +| `変更` | `オブジェクト` | アクションが `edited` の場合の Team への変更。 | +| `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` | アクションが `edited` の場合の以前のバージョンのTeam プライバシー。 | +| `changes[repository][permissions][from][admin]` | `boolean` | アクションが `edited` の場合の、リポジトリに対する以前のバージョンの Team メンバーの `admin` 権限。 | +| `changes[repository][permissions][from][pull]` | `boolean` | アクションが `edited` の場合の、リポジトリに対する以前のバージョンの Team メンバーの `pull` 権限。 | +| `changes[repository][permissions][from][push]` | `boolean` | アクションが `edited` の場合の、リポジトリに対する以前のバージョンの Team メンバーの `push` 権限。 | +| `リポジトリ` | `オブジェクト` | アクションが `added_to_repository`、`removeed_from_repository`、`edited` の場合の、Team の範囲に追加または削除されたリポジトリ。 `edited` アクションの場合、`repository` には、リポジトリに対する Team の新しい権限レベルも含まれます。 | {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.team.added_to_repository }} @@ -1229,23 +1254,23 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ {% data reusables.webhooks.team_add_short_desc %} -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `members` permission +- リポジトリ webhook +- Organization webhook +- `members` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ------ | -------- | ----------------------------------------------------------------------------------------------------------------- | -| `Team` | `オブジェクト` | The [team](/rest/reference/teams) that was modified. **Note:** Older events may not include this in the payload. | +| キー | 種類 | 説明 | +| ------ | -------- | --------------------------------------------------------------------------- | +| `Team` | `オブジェクト` | 変更された [Team](/rest/reference/teams)。 **注釈:** 古いイベントではペイロードに含まていれない場合があります。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.team_add }} @@ -1253,12 +1278,12 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_ ### ユーザ -When a user is `created` or `deleted`. +ユーザが `created` または `deleted` を指定した場合。 -#### Availability -- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." +#### 利用の可否 +- GitHub Enterprise webhook。 詳しい情報については「[グローバル webhook](/rest/reference/enterprise-admin#global-webhooks/)」を参照してください。 -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.user.created }} @@ -1268,15 +1293,15 @@ When a user is `created` or `deleted`. {% 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. +イベントのアクターは、リポジトリに Star を付けた[ユーザ](/rest/reference/users)であり、イベントのリポジトリは、Star を付けた[リポジトリ](/rest/reference/repos)です。 -#### Availability +#### 利用の可否 -- Repository webhooks -- Organization webhooks -- {% data variables.product.prodname_github_app %}s with the `metadata` permission +- リポジトリ webhook +- Organization webhook +- `metadata` 権限のある {% data variables.product.prodname_github_app %} -#### Webhook payload object +#### webhook ペイロードオブジェクト {% data reusables.webhooks.watch_properties %} {% data reusables.webhooks.repo_desc %} @@ -1284,20 +1309,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 +#### 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. 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_dispatch)」を参照してください。 +このイベントは、 ユーザが GitHub でワークフローの実行をトリガーするか、「[ワークフローディスパッチイベントの作成](/rest/reference/actions/#create-a-workflow-dispatch-event)」エンドポイントに `POST` リクエストを送信したときに発生します。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_dispatch)」を参照してください。 -#### Availability +#### 利用の可否 -- {% data variables.product.prodname_github_app %}s must have the `contents` permission to receive this webhook. +- この webhook を受信するには、{% data variables.product.prodname_github_app %} に `contents` 権限が必要です。 -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} @@ -1305,22 +1330,22 @@ 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)." +{% data variables.product.prodname_actions %} ワークフロー実行がリクエスト済または完了したとき。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_run)」を参照してください。 -#### Availability +#### 利用の可否 -- {% data variables.product.prodname_github_app %}s with the `actions` or `contents` permissions. +- `actions` または `contents`権限のある {% data variables.product.prodname_github_app %}. -#### Webhook payload object +#### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| -------- | -------- | ---------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event. | +| キー | 種類 | 説明 | +| -------- | -------- | ---------------------------------------------------------------------- | +| `action` | `string` | ほとんどの webhook ペイロードには、イベントをトリガーした特定のアクティビティを含む `action` プロパティが含まれています。 | {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.sender_desc %} -#### Webhook payload example +#### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.workflow_run }} {% endif %} diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks.md index f12f4c93b6..a5f6c79d2b 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks.md @@ -1,6 +1,6 @@ --- title: webhook -intro: 'Learn to set up, test, and secure webhooks to integrate with {% data variables.product.prodname_dotcom %}.' +intro: '{% data variables.product.prodname_dotcom %} と統合するための webhook のセットアップ、テスト、およびセキュリティ保護について学びます。' mapTopic: true versions: free-pro-team: '*' 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 new file mode 100644 index 0000000000..398032e196 --- /dev/null +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -0,0 +1,54 @@ +--- +title: About discussions +intro: Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About discussions + +With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools. + +- Share announcements and information, gather feedback, plan, and make decisions +- Ask questions, discuss and answer the questions, and mark the discussions as answered +- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows + +![Discussions tab for a repository](/assets/images/help/discussions/hero.png) + +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. 詳細は「[Organization のリポジトリ権限レベル](/github/setting-up-and-managing-organizations-and-teams/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)." + +### About categories and formats for discussions + +{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %} + +For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %} + +For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +### Best practices for discussions + +As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)." + +Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." + +### フィードバックを送る + +You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). + +### 参考リンク + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- 「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」 +- [コメントと会話の管理](/github/building-a-strong-community/moderating-comments-and-conversations) +- 「[{% data variables.product.prodname_dotcom %} での安全性を維持する](/github/building-a-strong-community/maintaining-your-safety-on-github)」 diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md new file mode 100644 index 0000000000..a07f2f4fb9 --- /dev/null +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -0,0 +1,48 @@ +--- +title: Collaborating with maintainers using discussions +shortTitle: Collaborating with maintainers +intro: You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion. +permissions: People with read permissions to a repository can start and participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About collaboration with maintainers using discussions + +{% data reusables.discussions.about-discussions %} If you use or contribute to a project, you can start a discussion to make suggestions and engage with maintainers and community members about your plans, questions, ideas, and feedback. For more information, see "[‎About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +{% data reusables.discussions.about-categories-and-formats %} Repository administrators and project maintainers can delete a discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)." + +{% data reusables.discussions.github-recognizes-members %} These members appear in a list of the most helpful contributors to the project's discussions. As your project grows, you can grant higher access permissions to active members of your community. For more information, see "[Granting higher permissions to top contributors](/discussions/guides/granting-higher-permissions-to-top-contributors)" + +![Most helpful contributors to discussions for a project](/assets/images/help/discussions/most-helpful.png) + +For more information about participation in discussions, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +### 必要な環境 + +To collaborate with maintainers using discussions, a repository administrator or project maintainer must enable discussions for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Starting a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Filtering the list of discussions + +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the **Search all discussions** field, type a search query. Optionally, to the right of the search field, click a button to further filter the results. ![Search bar and buttons for filtering discussions](/assets/images/help/discussions/search-and-filter-controls.png) +1. In the list of discussions, click the discussion you want to view. ![Discussion search results](/assets/images/help/discussions/search-result.png) + +### Converting an issue to a discussion + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)." + +### 参考リンク + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- 「[{% data variables.product.prodname_dotcom %} での安全性を維持する](/github/building-a-strong-community/maintaining-your-safety-on-github)」 diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md new file mode 100644 index 0000000000..44aed03c8b --- /dev/null +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/index.md @@ -0,0 +1,14 @@ +--- +title: Collaborating with your community using discussions +shortTitle: Collaborating using discussions +intro: Gather and discuss your project with community members and other maintainers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /about-discussions %} +{% link_in_list /participating-in-a-discussion %} +{% link_in_list /collaborating-with-maintainers-using-discussions %} + diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md new file mode 100644 index 0000000000..b0a504de9d --- /dev/null +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -0,0 +1,31 @@ +--- +title: Participating in a discussion +intro: You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}. +permissions: People with read permissions to a repository can participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About participation in a discussion + +{% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)." + +You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)." + +### 必要な環境 + +Discussions must be enabled for the repository for you to participate in a discussion in the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Creating a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Marking a comment as an answer + +Discussion authors and users with the triage role or greater for a repository can mark a comment as the answer to a discussion in the repository. + +{% data reusables.discussions.marking-a-comment-as-an-answer %} 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 new file mode 100644 index 0000000000..c56aa23743 --- /dev/null +++ b/translations/ja-JP/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -0,0 +1,49 @@ +--- +title: Best practices for community conversations on GitHub +shortTitle: Best practices for community conversations +intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to a discussion when you are ready to scope out the work.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Community conversations in {% data variables.product.prodname_discussions %} + +Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository and gather diverse feedback and ideas more quickly. You can help drive a productive conversation by: + +- Asking pointed questions and follow-up questions to garner specific feedback +- Capture a diverse experience and distill it down to main points +- Open an issue to take action based on the conversation, where applicable + +For more information about opening an issue and cross-referencing a discussion, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." + +### Learning about conversations on GitHub + +You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have. + +You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and spike out a project's specific details before committing it to an issue, which can then be scoped. Discussions are useful for teams if: +- You are in the discovery phase of a project and are still learning which director your team wants to go in +- You want to collect feedback from a wider community about a project +- You want to keep bug fixes, feature requests, and general conversations separate + +Issueは、バグレポートや計画された改善など、プロジェクトの特定の詳細についての議論に役立ちます。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 プルリクエストでは、提案された変更に直接コメントできます。 詳しい情報については[プルリクエストについて](/articles/about-pull-requests)及び[プルリクエストへコメントする](/articles/commenting-on-a-pull-request)を参照してください。 + +{% data reusables.organizations.team-discussions-purpose %}詳しい情報については「[Team ディスカッションについて](/articles/about-team-discussions)」を参照してください。 + +### Following contributing guidelines + +Before you open a discussion, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project. + +詳しい情報については、「[健全なコントリビューションを促すプロジェクトをセットアップする](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)」を参照してください。 + +### 次のステップ + +To continue learning about {% data variables.product.prodname_discussions %} and quickly create a discussion for your community, see "[Quickstart for {% data variables.product.prodname_discussions %}](/discussions/quickstart)." + +### 参考リンク + +- [健全なコントリビューションを促すプロジェクトをセットアップする](/articles/setting-up-your-project-for-healthy-contributions) +- 「[テンプレートを使用して便利な Issue およびプルリクエストを推進する](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)」 +- [コメントと会話の管理](/articles/moderating-comments-and-conversations) +- [{% data variables.product.prodname_dotcom %}での執筆](/articles/writing-on-github) diff --git a/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md new file mode 100644 index 0000000000..d664ce0f95 --- /dev/null +++ b/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -0,0 +1,20 @@ +--- +title: Finding discussions across multiple repositories +intro: 'You can easily access every discussion you''ve created or participated in across multiple repositories.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Finding discussions + +1. {% data variables.product.prodname_dotcom_the_website %}に移動します。 +1. In the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your discussions**. !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. + +### 参考リンク + +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" 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 new file mode 100644 index 0000000000..12d69aa931 --- /dev/null +++ b/translations/ja-JP/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -0,0 +1,32 @@ +--- +title: Granting higher permissions to top contributors +intro: 'Repository administrators can promote any community member to a moderator and maintainer.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### はじめに + +The most helpful contributors for the past 30 days are highlighted on the {% data variables.product.prodname_discussions %} dashboard, based on how many comments were marked as answers by other community members. Helpful contributors can help drive a healthy community and moderate and guide the community space in addition to maintainers. + +### Step 1: Audit your discussions top contributors + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Compare the list of contributors with their access permissions to see who qualifies to moderate the discussion. + +### Step 2: Review permission levels for discussions + +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)." + +### Step 3: Change permissions levels for top contributors + +You can change a contributor's permission levels to give them more access to the tooling they need to moderate GitHub Discussions. To change a person's or team's permission levels, see "[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)." + +### Step 4: Notify community members of elevated access + +When you change a collaborators permission level, they will receive a notification for the change. diff --git a/translations/ja-JP/content/discussions/guides/index.md b/translations/ja-JP/content/discussions/guides/index.md new file mode 100644 index 0000000000..71359c1a02 --- /dev/null +++ b/translations/ja-JP/content/discussions/guides/index.md @@ -0,0 +1,31 @@ +--- +title: Discussions guides +shortTitle: ガイド +intro: 'Discover pathways to get started or learn best practices for participating or monitoring your community''s discussions.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Getting started with discussions + +{% link_in_list /about-discussions %} +{% link_in_list /best-practices-for-community-conversations-on-github %} +{% link_in_list /finding-discussions-across-multiple-repositories %} + +### Administering discussions + +{% link_in_list /granting-higher-permissions-to-top-contributors %} + + + + + diff --git a/translations/ja-JP/content/discussions/index.md b/translations/ja-JP/content/discussions/index.md new file mode 100644 index 0000000000..66dca4f270 --- /dev/null +++ b/translations/ja-JP/content/discussions/index.md @@ -0,0 +1,55 @@ +--- +title: GitHub Discussions Documentation +beta_product: true +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.' +introLinks: + quickstart: /discussions/quickstart +featuredLinks: + guides: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + gettingStarted: + - /discussions/quickstart + guideCards: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + popular: + - /discussions/guides/granting-higher-permissions-to-top-contributors + - /discussions/guides/best-practices-for-community-conversations-on-github + - /discussions/guides/finding-discussions-across-multiple-repositories + - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions + - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository +product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +layout: product-landing +versions: + free-pro-team: '*' +--- + + + + + + + +{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} +{% if discussionsCommunityExamples %} +
+

Communities using discussions

+ +
+ {% 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" %} +
+
+{% endif %} diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md new file mode 100644 index 0000000000..8ccb2875b2 --- /dev/null +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/index.md @@ -0,0 +1,13 @@ +--- +title: Managing discussions for your community +shortTitle: Managing discussions +intro: 'You can enable and configure discussions for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /managing-discussions-in-your-repository %} +{% link_in_list /managing-categories-for-discussions-in-your-repository %} +{% link_in_list /moderating-discussions %} diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md new file mode 100644 index 0000000000..5fe66db589 --- /dev/null +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md @@ -0,0 +1,56 @@ +--- +title: Managing categories for discussions in your repository +intro: You can categorize the discussions in your repository to organize conversations for your community members, and you can choose a format for each category. +permissions: Repository administrators and people with write or greater access to a repository can enable discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About categories for discussions + +{% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} + +Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations.{% data reusables.discussions.repository-category-limit %} + +For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +### Default categories + +| カテゴリ | Purpose | 種類 | +|:--------------- |:-------------------------------------------------------------------- |:--------------------- | +| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion | +| 💡Ideas | Ideas to change or improve the project | Open-ended discussion | +| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer | +| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion | + +### Creating a category + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.edit-categories %} +1. Click **New category**. !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png) +1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png) +1. ** Create（作成）**をクリックしてください。 !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png) + +### Editing a category + +You can edit a category to change the category's emoji, title, description, and discussion format. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} +![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png) +1. [**Save changes**] をクリックします。 !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +### Deleting a category + +When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png) +1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png) +1. Click **Delete & Move**. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png) 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 new file mode 100644 index 0000000000..23c2b87a17 --- /dev/null +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -0,0 +1,94 @@ +--- +title: Managing discussions in your repository +intro: You can categorize, spotlight, transfer, or delete the discussions in a repository. +permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About management of discussions + +{% 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)." + +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](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)." + +For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/github/building-a-strong-community/moderating-comments-and-conversations)." + +### 必要な環境 + +To manage discussions in a repository, discussions must be enabled for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Changing the category for a discussion + +You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" article. + +You can also move a discussion to a different category. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) + +### Pinning a discussion + +You can pin up to four important discussions above the list of discussions for the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png) +1. Optionally, customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Editing a pinned discussion + +Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Unpinning a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) +1. Read the warning, then click **Unpin discussion**. !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png) + +### Transferring a discussion + +To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png) +1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Click **Transfer discussion**. !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png) + +### Deleting a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png) +1. Read the warning, then click **Delete this discussion**. !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) + +### Converting issues based on labels + +You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Next to the label you want to convert to issues, click **Convert issues**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md new file mode 100644 index 0000000000..2c91d32d89 --- /dev/null +++ b/translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -0,0 +1,39 @@ +--- +title: Moderating discussions +intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, and converting issues to discussions. and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct to discussions.' +permissions: People with triage access to a repository can moderate discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About moderating discussions + +{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you 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. + +### Marking a comment as an answer + +{% data reusables.discussions.marking-a-comment-as-an-answer %} + +### Locking discussions + +It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository will still be able to comment on the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the discussion you want to lock. ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the right margin of a discussion, click **Lock conversation**. +1. Read the information about locking conversations and click **Lock conversation on this discussion**. +1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**. + +### Converting an issue to a discussion + +When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository can bulk convert issues based on labels. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to convert. +1. In the right margin of an issue, click **Convert to discussion**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/ja-JP/content/discussions/quickstart.md b/translations/ja-JP/content/discussions/quickstart.md new file mode 100644 index 0000000000..1a9d5ce3ae --- /dev/null +++ b/translations/ja-JP/content/discussions/quickstart.md @@ -0,0 +1,58 @@ +--- +title: Quickstart for GitHub Discussions +intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository and start conversations with your community.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### はじめに + +{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike issues. Discussions enable fluid, open conversation in a public forum. + +Discussions give a space for more collaborative conversations by connecting and giving a more centralized area to connect and find information. + +### Enabling {% data variables.product.prodname_discussions %} on your repository + +Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public repositories. + +When you first enable a {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. + +{% data reusables.repositories.navigate-to-repo %} +1. リポジトリ名の下で{% octicon "gear" aria-label="The gear icon" %} **Settings（設定）**をクリックしてください。 ![Public settings button](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", click **Set up discussions**. ![Set up a discussion button under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png) +1. Under "Start a new discussion," edit the template to align with the resources and tone you want to set for your community. +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) + +### Welcoming contributions to your discussions + +You can welcome your community and introduce a new way to communicate in a repository by creating a welcome post and pin the post to your {% data variables.product.prodname_discussions %} page. Pinning and locking discussions helps people know that a post is meant as an announcement. You can use announcements as a way to link people to more resources and offer guidance for opening discussions in your community. For more information about pinning a discussion, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + + +### Setting up community guidelines for contributors + +You can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. You can also update the repository's README to communicate expectations on when collaborators should open an issue or discussion. + +For more information about providing guidelines for your project, see "[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and "[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Creating a new discussion + +Anyone with access to a repository can create a discussion. + +{% data reusables.discussions.starting-a-discussion %} + +### Organizing discussions into relevant categories + +Repository owners and people with write access can create new categories to keep discussions organized. Collaborators participating and creating new discussions can group discussions into the most relevant existing categories. Discussions can also be recategorized after they are created. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" + +### Promoting healthy conversations + +People with write permissions for a repository can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +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)." + +### 次のステップ + +Once there is a clear path to scope work out and move an idea from concept to reality, you can create an issue and start tracking your progress. For more information on creating an issue from a discussion, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." diff --git a/translations/ja-JP/content/education/guides.md b/translations/ja-JP/content/education/guides.md new file mode 100644 index 0000000000..e4edf7fc06 --- /dev/null +++ b/translations/ja-JP/content/education/guides.md @@ -0,0 +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 +versions: + free-pro-team: '*' +--- + +### Get started with {% 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. + +- [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/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) + +### Run a software development course with {% 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 %}. + +- [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) + +### Learn to develop software + +Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. + +- [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/teach-and-learn-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) + +### Contribute to the community + +Participate in the community, get training from {% data variables.product.company_short %}, and learn or teach new skills. + +- [{% data variables.product.prodname_education_community %}](https://education.github.community) +- [Campus Expertsについて](/education/teach-and-learn-with-github-education/about-campus-experts) +- [Campus Advisorsについて](/education/teach-and-learn-with-github-education/about-campus-advisors) diff --git a/translations/ja-JP/content/education/index.md b/translations/ja-JP/content/education/index.md new file mode 100644 index 0000000000..c3827df288 --- /dev/null +++ b/translations/ja-JP/content/education/index.md @@ -0,0 +1,45 @@ +--- +title: GitHub Education Documentation +shortTitle: Education +intro: "{% data variables.product.prodname_education %} helps you teach or learn software development with the tools and support of {% data variables.product.company_short %}'s platform and community." +introLinks: + quickstart: /education/quickstart +featuredLinks: + guides: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + guideCards: + - /github/getting-started-with-github/signing-up-for-a-new-github-account + - /github/getting-started-with-github/git-and-github-learning-resources + - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom + popular: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /desktop + - /github/getting-started-with-github/github-cli + - /education/manage-coursework-with-github-classroom/teach-with-github-classroom +changelog: + - + title: 'Try something new at Local Hack Day: Learn' + date: '2020-10-15' + href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ + - + title: 'Remote Education: Creating community through shared experiences' + date: '2020-09-24' + href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ + - + title: 'Remote Education: A series of best practices for online campus communities' + date: '2020-09-10' + href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ + - + title: Welcome to the inaugural class of MLH Fellows + date: '2020-06-24' + href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ +layout: product-landing +versions: + free-pro-team: '*' +--- + + + diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md new file mode 100644 index 0000000000..e285ea8f92 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -0,0 +1,31 @@ +--- +title: About using MakeCode Arcade with GitHub Classroom +shortTitle: About using MakeCode Arcade +intro: You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-makecode +--- + +### About MakeCode Arcade + +MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade. + +For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. + +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. + +### About submission of assignments with MakeCode Arcade + +By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.product.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen. + +![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) + +### 参考リンク + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md new file mode 100644 index 0000000000..15f050d0db --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: About using Repl.it with GitHub Classroom +shortTitle: About using Repl.it +intro: You can configure Repl.it as the online integrated development environment (IDE) for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-replit +--- + +### About Repl.it + +Repl.it is an online integrated development environment (IDE) that supports multiple programming languages. Students can write, edit, run, test, and debug code in a browser with Repl.it. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. + +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). + +For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. + +### About submission of assignments with Repl.it + +By default, Repl.it is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with Repl.it, students should push changes to {% data variables.product.product_location %} using the version control functionality in the left sidebar. + +![Repl.it version control functionality](/assets/images/help/classroom/ide-replit-version-control-button.png) + +For more information about using Git on Repl.it, see the [Repl.it + Git Tutorial](https://repl.it/talk/learn/Replit-Git-Tutorial/23331) on the Repl.it website. + +### 参考リンク + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md new file mode 100644 index 0000000000..386402e628 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: Basics of setting up GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %} basics' +intro: Learn how to set up your classroom, manage assignments, and configure time-saving automation. +versions: + free-pro-team: '*' +--- + +### Videos about {% data variables.product.prodname_classroom %} + +You can watch a series of short video tutorials about the configuration and use of {% data variables.product.prodname_classroom %}. To watch all videos as part of a continuous playlist, see the [{% data variables.product.prodname_classroom %} Getting Started Guide](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) on YouTube. + +For more information about terminology for {% data variables.product.prodname_classroom %}, see "[Glossary](/education/manage-coursework-with-github-classroom/glossary)". + +1. Getting started {% octicon "link-external" aria-label="The external link icon" %} +2. Adding your student roster {% octicon "link-external" aria-label="The external link icon" %} +3. Creating assignments + - Creating an assignment using a {% data variables.product.prodname_dotcom %} repository {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Microsoft MakeCode as your online IDE {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Repl.it as your online IDE {% octicon "link-external" aria-label="The external link icon" %} +4. How students complete assignments {% octicon "link-external" aria-label="The external link icon" %} +5. How teachers review assignments {% octicon "link-external" aria-label="The external link icon" %} +6. Creating group assignments {% octicon "link-external" aria-label="The external link icon" %} +7. Next steps to get started {% octicon "link-external" aria-label="The external link icon" %} +8. {% data variables.product.prodname_dotcom %} Teacher Toolbox {% octicon "link-external" aria-label="The external link icon" %} + +### 次のステップ + +For more information about teaching with {% data variables.product.prodname_classroom %}, see "[Teach with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom)." + +### 参考リンク + +- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md new file mode 100644 index 0000000000..bcc3541cf0 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md @@ -0,0 +1,50 @@ +--- +title: Configure default settings for assignment repositories +shortTitle: Configure defaults for assignment repositories +intro: You can use the Probot Settings app to configure the default settings for repositories that {% data variables.product.prodname_classroom %} creates for an assignment. +permissions: Organization owners can configure default settings for assignment repositories by installing a {% data variables.product.prodname_github_app %} for the organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/probot-settings +--- + +### About configuration of defaults for assignment repositories + +{% data variables.product.prodname_classroom %} creates a repository that belongs for each student or team that accepts an assignment. The repository belongs to the organization that you use for {% data variables.product.prodname_classroom %}. Assignment repositories can be empty, or you can use a template repository. For more information, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} + +With the Probot Settings app, you can create a file named _.github/settings.yml_ in a repository that contains a list of settings for the repository, and then install a {% data variables.product.prodname_github_app %} for your organization that automatically applies the settings to the repository. + +You can include _.github/settings.yml_ in a template repository that you use for an assignment in {% data variables.product.prodname_classroom %}. When an individual or team accepts the assignment, {% data variables.product.prodname_classroom %} creates the assignment repository, and the Settings app automatically applies the settings from _.github/settings.yml_. + +Probot is a a project, framework, and collection of free apps to automate {% data variables.product.product_name %}. A Probot app can listen to repository events, like the creation of new commits, comments, and issues, and automatically respond to the event. + +For more information, see the [Probot website](https://probot.github.io) and the [Settings app website](https://probot.github.io/apps/settings/). For more information about {% data variables.product.prodname_github_apps %}, see "[About apps](/developers/apps/about-apps)." + +### Adding the Settings app to your organization + +After you install the Probot Settings app for your organization, the app will apply the settings that you define in _.github/settings.yml_ for any repository in your organization, including new assignment repositories that {% data variables.product.prodname_classroom %} creates. + +1. Navigate to the [Settings app page](https://github.com/apps/settings). +1. Click **Install**, then click the organization that you use for {% data variables.product.prodname_classroom %}. Provide the app full access to all repositories owned by the organization. ![Installing the Probot Settings app](/assets/images/help/classroom/probot-settings.gif) + +### Configuring default settings for an assignment repository + +1. Create a template repository that contains a _.github/settings.yml_ file. For a complete list of settings, see the [README](https://github.com/probot/settings#github-settings) for the `probot/settings` repository. For more information about using a template repository for starter code in {% data variables.product.prodname_classroom %}, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + + {% warning %} + + **Warning:** Do not define `collaborators` in the _.github/settings.yml_ file for your template repository. {% data variables.product.prodname_classroom %} automatically grants teachers and teaching assistants access to assignment repositories. + + {% endwarning %} + +1. Create an assignment using the template repository containing _.github/settings.yml_ as the starter code. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +The Probot Settings app for your organization will now apply the settings you define in _.github/settings.yml_ within the template repository to every assignment repository that {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} creates for a student or team. + +### 参考リンク + +- [Probot apps](https://probot.github.io/apps/) +- [Probot documentation](https://probot.github.io/docs/) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md new file mode 100644 index 0000000000..16239d43de --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -0,0 +1,138 @@ +--- +title: Connect a learning management system to GitHub Classroom +intro: You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom + - /education/manage-coursework-with-github-classroom/connect-to-lms + - /education/manage-coursework-with-github-classroom/generate-lms-credentials + - /education/manage-coursework-with-github-classroom/setup-canvas + - /education/manage-coursework-with-github-classroom/setup-generic-lms + - /education/manage-coursework-with-github-classroom/setup-moodle +--- + +### About configuration of your LMS + +You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS. + +### 必要な環境 + +To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)." + +### Supported LMSes + +{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards. + +- LTI version 1.0 and/or 1.1 +- LTI Names and Roles Provisioning 1.X + +Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website. + +{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. + +- Canvas +- Google Classroom +- Moodle +- Sakai + +Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace + +### Generating configuration credentials for your classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster. + - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)." +1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**. ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. Read about connecting your LMS, then click **Connect to _LMS_**. +1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom. ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png) + +### Configuring a generic LMS + +You must configure the privacy settings for your LMS to allow external tools to receive roster information. + +1. Navigate to your LMS. +1. Configure an external tool. +1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}. + - Consumer key + - Shared secret + - Launch URL (sometimes called "tool URL" or similar) + +### Configuring Canvas + +You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). + +1. Sign into [Canvas](https://www.instructure.com/canvas/#login). +1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}. +1. 左のサイドバーで、**Settings（設定）**をクリックしてください。 +1. Click the **Apps** tab. +1. Click **View app configurations**. +1. Click **+App**. +1. Select the **Configuration Type** drop-down menu, and click **By URL**. +1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Canvas app configuration | Value or setting | + |:------------------------------------------------------------------------- |:------------------------------------------------------------------ | + | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} + | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled | + | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} + + {% note %} + + **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website. + + {% endnote %} + +1. **Submit（サブミット）**をクリックしてください。 +1. In the left sidebar, click **Home**. +1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}. + +### Configuring Moodle + +You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org). + +You must be using Moodle version 3.0 or greater. + +1. Sign into [Moodle](https://moodle.org/login/index.php). +1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}. +1. Click **Turn editing on**. +1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**. +1. Choose **External tool** and click **Add**. +1. In the "Activity name" field, type "GitHub Classroom". +1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**. +1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Moodle app configuration | Value or setting | + |:--------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_

**Note**: You can use any name, but we suggest this value for clarity. | + | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} + | **LTI version** | LTI 1.0/1.1 | + | **Default launch container** | New window | + | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} + +1. Scroll to and click **Services**. +1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**. +1. Scroll to and click **Privacy**. +1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**. +1. ページの下部で**Save changes（変更の保存）**をクリックしてください。 +1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**. +1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**. +1. At the bottom of the page, click **Save and return to course**. +1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity. + +### Importing a roster from your LMS + +For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + +### Disconnecting your LMS + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Connect to a learning management system (LMS)", click **Connection Settings**. !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**. !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) 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 new file mode 100644 index 0000000000..abbd937a0b --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -0,0 +1,145 @@ +--- +title: Create a group assignment +intro: 'You can create a collaborative assignment for teams of students who participate in your course.' +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/create-group-assignments +--- + +### About group assignments + +{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers. + +When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment. + +{% data reusables.classroom.classroom-creates-group-repositories %} + +{% data reusables.classroom.about-assignments %} + +You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. 詳細は「[Team について](/github/setting-up-and-managing-organizations-and-teams/about-teams)」を参照してください。 + +For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### 必要な環境 + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Defining teams for an assignment](#defining-teams-for-an-assignment) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +#### Defining teams for an assignment + +If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams. + +{% tip %} + +**ヒント**: + +- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course. + +- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members. + +{% endtip %} + +![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png) + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +### Providing feedback + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the team. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
+ Group assignment +
+ +### 次のステップ + +- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. + +- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### 参考リンク + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md new file mode 100644 index 0000000000..a5b2e6c39e --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -0,0 +1,19 @@ +--- +title: Create an assignment from a template repository +intro: You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments +--- + +You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. 詳細は「[テンプレートリポジトリを作成する](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)」を参照してください。 + +To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." + +### 参考リンク + +- "[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)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md new file mode 100644 index 0000000000..660c1da533 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -0,0 +1,124 @@ +--- +title: Create an individual assignment +intro: You can create an assignment for students in your course to complete individually. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment + - /education/manage-coursework-with-github-classroom/create-an-individual-assignment +--- + +### About individual assignments + +{% data reusables.classroom.assignments-individual-definition %} + +{% data reusables.classroom.classroom-creates-individual-repositories %} + +{% data reusables.classroom.about-assignments %} + +For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### 必要な環境 + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +### Providing feedback for an assignment + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the student. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
+ Individual assignment +
+ +### 次のステップ + +- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." + +- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### 参考リンク + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md new file mode 100644 index 0000000000..ca171e5612 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md @@ -0,0 +1,9 @@ +--- +title: Get started with GitHub Classroom +shortTitle: 始めましょう！ +intro: Learn how to configure and use {% data variables.product.prodname_classroom %} to administer your course. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/glossary.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/glossary.md new file mode 100644 index 0000000000..0a247aad2b --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/glossary.md @@ -0,0 +1,52 @@ +--- +title: 用語集 +intro: You can review explanations of terminology for {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +--- + +### . 譲渡 + +An assignment is coursework in {% data variables.product.prodname_classroom %}. A teacher can assign an assignment to an individual student or a group of students. Teachers can import starter code for the assignment, assign students, and create a deadline for each assignment. For more information, see the definitions for "[individual assignment](#individual-assignment)" and "[group assignment](#group-assignment)." + +--- + +### classroom + +A classroom is the basic unit of {% data variables.product.prodname_classroom %}. Teachers can use a classroom to organize and manage students, teaching assistants, and assignments for a single course. A classroom belongs to an organization on {% data variables.product.prodname_dotcom_the_website %}. To administer a classroom, you must be an organization owner for the organization on {% data variables.product.prodname_dotcom %}. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." + +--- + +### {% data variables.product.prodname_classroom %} + +{% data variables.product.prodname_classroom %} is a web application for educators that provides course administration tools integrated with {% data variables.product.prodname_dotcom %}. For more information, see the [{% data variables.product.prodname_classroom %}](https://classroom.github.com/) website. + +--- + +### group assignment + +{% data reusables.classroom.assignments-group-definition %} For more information, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +--- + +### identifier + +An identifier in {% data variables.product.prodname_classroom %} is a unique ID for a student participating in a course. For example, an identifier can be a student name, alphanumeric ID, or email address. + +--- + +### individual assignment + +{% data reusables.classroom.assignments-individual-definition %} For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +--- + +### roster + +A roster allows a teacher to manage students and assignment submissions in a classroom on {% data variables.product.prodname_classroom %}. Teachers can create a roster by entering a list of student identifiers, or by connecting {% data variables.product.prodname_classroom %} to a learning management system (LMS). For more information about identifiers, see the definition of "[identifier](#identifier)." For more information about connecting {% data variables.product.prodname_classroom %} to an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + +--- + +### 参考リンク + +- [{% data variables.product.prodname_dotcom %} 用語集](/github/getting-started-with-github/github-glossary) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/index.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/index.md new file mode 100644 index 0000000000..fd004e5101 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/index.md @@ -0,0 +1,32 @@ +--- +title: Manage coursework with GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %}' +intro: With {% data variables.product.prodname_classroom %}, you can use {% data variables.product.product_name %} to administer or participate in a course about software development. +versions: + free-pro-team: '*' +--- + +### 目次 + +{% topic_link_in_list /get-started-with-github-classroom %} + {% link_in_list /basics-of-setting-up-github-classroom %} + {% link_in_list /glossary %} + +{% topic_link_in_list /teach-with-github-classroom %} + {% link_in_list /manage-classrooms %} + {% link_in_list /create-an-individual-assignment %} + {% link_in_list /create-a-group-assignment %} + {% link_in_list /create-an-assignment-from-a-template-repository %} + {% link_in_list /leave-feedback-with-pull-requests %} + {% link_in_list /use-autograding %} + {% link_in_list /configure-default-settings-for-assignment-repositories %} + {% link_in_list /connect-a-learning-management-system-to-github-classroom %} + +{% topic_link_in_list /integrate-github-classroom-with-an-ide %} + {% link_in_list /integrate-github-classroom-with-an-online-ide %} + {% link_in_list /about-using-makecode-arcade-with-github-classroom %} + {% link_in_list /about-using-replit-with-github-classroom %} + {% link_in_list /run-student-code-in-an-online-ide %} + +{% topic_link_in_list /learn-with-github-classroom %} + {% link_in_list /view-autograding-results %} diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md new file mode 100644 index 0000000000..f4245ea672 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md @@ -0,0 +1,9 @@ +--- +title: Integrate GitHub Classroom with an IDE +shortTitle: Integrate with an IDE +intro: You can help your students write, test, and debug code by preconfiguring a development environment for assignment repositories on {% data variables.product.prodname_classroom %}. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md new file mode 100644 index 0000000000..fcab190c3e --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md @@ -0,0 +1,42 @@ +--- +title: Integrate GitHub Classroom with an online IDE +shortTitle: Integrate with an online IDE +intro: You can preconfigure a supported online integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/online-ide-integrations +--- + +### About integration with an online IDE + +{% data reusables.classroom.about-online-ides %} + +After a student accepts an assignment with an online IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary. + +![Button for online IDE in README.md for assignment repository](/assets/images/help/classroom/assignment-repository-ide-button-in-readme.png) + +### Supported online IDEs + +{% data variables.product.prodname_classroom %} supports the following online IDEs. You can learn more about the student experience for each IDE. + +| IDE | 詳細情報 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | +| Repl.it | "[About using Repl.it with GitHub Classroom](/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom)" | + +### Configuring an online IDE for an assignment + +You can choose the online IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an online IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Authorizing the OAuth app for an online IDE + +The first time you configure an assignment with an online IDE, you must authorize the OAuth app for the online IDE for your organization. + +!["Go grant access" button in popover for authorizing OAuth app for online IDE](/assets/images/help/classroom/assignment-ide-go-grant-access-button.png) + +For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. 詳しい情報については、「[OAuth App を認証する](/github/authenticating-to-github/authorizing-oauth-apps)」を参照してください。 + +### 参考リンク + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md new file mode 100644 index 0000000000..bca1150346 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Learn with GitHub Classroom +intro: You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md new file mode 100644 index 0000000000..c3d13bd2bc --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md @@ -0,0 +1,31 @@ +--- +title: Leave feedback with pull requests +intro: You can leave feedback for your students in a special pull request within the repository for each assignment. +permissions: People with read permissions to a repository can leave feedback in a pull request for the repository. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github +--- + +### About feedback pull requests for assignments + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +When you enable the pull request for feedback for an assignment, {% data variables.product.prodname_classroom %} will create a special pull request titled **Feedback** in the assignment repository for each student or team. The pull request automatically shows every commit that a student pushed to the assignment repository's default branch. + +### 必要な環境 + +To create and access the feedback pull request, you must enable the feedback pull request when you create the assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +### Leaving feedback in a pull request for an assignment + +{% data reusables.classroom.sign-into-github-classroom %} +1. In the list of classrooms, click the classroom with the assignment you want to review. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **Review**. ![Review button for assignment in list of submissions for an assignment](/assets/images/help/classroom/assignments-click-review-button.png) +1. Review the pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)." + +### 参考リンク + +- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](http://localhost:4000/en/free-pro-team@latest/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/manage-classrooms.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/manage-classrooms.md new file mode 100644 index 0000000000..bf6b8dcc5b --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -0,0 +1,106 @@ +--- +title: Manage classrooms +intro: You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}. +permissions: Organization owners can manage a classroom for an organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/archive-a-classroom +--- + +### About classrooms + +{% data reusables.classroom.about-classrooms %} + +![Classroom](/assets/images/help/classroom/classroom-hero.png) + +### About management of classrooms + +{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. + +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 classrom. 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)." + +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. + +### About classroom rosters + +Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course. + +When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment. + +![Classroom roster](/assets/images/help/classroom/roster-hero.png) + +### 必要な環境 + +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 authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. 詳しい情報については、「[OAuth App を認証する](/github/authenticating-to-github/authorizing-oauth-apps)」を参照してください。 + +### Creating a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **New classroom**. !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png) +{% data reusables.classroom.guide-create-new-classroom %} + +After you create a classroom, you can begin creating assignments for students. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Creating a roster for your classroom + +You can create a roster of the students who participate in your course. + +If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) +1. To create a roster manually, type your student identifiers. Optionally, click **Upload a CSV or text file** to upload a file containing the identifiers. ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png) +1. Click **Create roster**. !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png) + +### Adding students to the roster for your classroom + +Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classrom](#creating-a-roster-for-your-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To the right of "Classroom roster", click **Update students**. !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png) +1. Follow the instructions to add students to the roster. + - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**. ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) + +### Renaming a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Classroom name", type a new name for the classroom. ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png) +1. Click **Rename classroom**. !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png) + +### Archiving or unarchiving a classroom + +You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**. ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png) +1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**. ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) + +### Deleting a roster for a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Under "Delete this roster", click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png) +1. Read the warnings, then click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) + +### Deleting a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) +1. **警告を読みます**。 +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md new file mode 100644 index 0000000000..57e3f1e824 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md @@ -0,0 +1,21 @@ +--- +title: Run student code in an online IDE +intro: You can run the code from a student assignment within the online integrated development environment (IDE) that you configured for the assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/running-student-code +--- + +### About student code and online IDEs + +If you configure an online integrated development environment (IDE) for an assignment, you can run the code within the online IDE. You don't need to clone the assignment repository to your computer. + +For more information about online IDEs, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +### Running student code in the online IDE + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **View IDE**. !["View IDE" button for submission using an online IDE](/assets/images/help/classroom/assignments-click-view-ide.png) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md new file mode 100644 index 0000000000..6e051e9d2d --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Teach with GitHub Classroom +intro: Learn how to set up your classroom and assignments. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/use-autograding.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/use-autograding.md new file mode 100644 index 0000000000..6fd3f029b3 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/use-autograding.md @@ -0,0 +1,83 @@ +--- +title: Use autograding +intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers +--- + +### About autograding + +{% data reusables.classroom.about-autograding %} + +After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding. + +You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." + +You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment. + +![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png) + +### Grading methods + +There are two grading methods: input/output tests and run command tests. + +#### Input/output test + +An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result. + +| 設定 | 説明 | +|:------------------- |:------------------------------------------------------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate standard output for evaluation | +| **Inputs** | Standard input for run command | +| **Expected output** | The output that you want to see as standard output from the run command | +| **Comparison** | The type of comparison between the run command's output and the expected output

  • **Included**: Passes when the expected output appears
    anywhere in the standard output from the run command
  • **Exact**: Passes when the expected output is completely identical
    to the standard output from the run command
  • **Regex**: Passes if the regular expression in expected
    output matches against the standard output from the run command
| +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +#### Run command test + +A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure. + +{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`. + +| 設定 | 説明 | +|:----------------- |:------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate an exit code for evaluation | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +### Configuring autograding tests for an assignment + +You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests. + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.assignments-click-pencil %} +1. In the left sidebar, click **Grading and feedback**. !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) +1. Add, edit, or delete an autograding test. + - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png) +1. At the bottom of the page, click **Update assignment**. !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png) + +### Viewing logs from autograding tests + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of a submission, click **View test**. !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png) +1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)." + +### 参考リンク + +- [{% data variables.product.prodname_actions %} documentation](/actions) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/view-autograding-results.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/view-autograding-results.md new file mode 100644 index 0000000000..42a2c353d6 --- /dev/null +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/view-autograding-results.md @@ -0,0 +1,30 @@ +--- +title: View autograding results +intro: You can see results from autograding within the repository for your assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students +--- + +### About autograding + +Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.product.product_location %}. + +If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X. + +### Viewing autograding results for an assignment repository + +{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." + +The **Actions** tab shows the full history of test runs. + +!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png) + +You can click a specific test run to review log output, like compilation errors and test failures. + +![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) + +### 参考リンク + +- "[ステータスチェックについて](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/ja-JP/content/education/quickstart.md b/translations/ja-JP/content/education/quickstart.md new file mode 100644 index 0000000000..0601b0557a --- /dev/null +++ b/translations/ja-JP/content/education/quickstart.md @@ -0,0 +1,87 @@ +--- +title: Quickstart for GitHub Educators +intro: In about 15 minutes, teachers can get started with discounts, training, and tools for {% data variables.product.company_short %}, then create a classroom for the students in a software development course using {% data variables.product.prodname_classroom %}. +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +### はじめに + +Educators who teach a course on software development can use discounts, partnerships, training, and tools from {% data variables.product.prodname_education %} to effectively teach relevant skills to students. + +In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}. + +{% tip %} + +**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Applying for a student developer pack](/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack)." + +{% endtip %} + +### Creating accounts on {% data variables.product.product_name %} + +First, you'll need to create a free user account on {% data variables.product.product_name %}. + +{% data reusables.accounts.create-account %} +1. Follow the prompts to create your free user account. + +After you create your user account, create a free organization account. You'll use this organization account to create and manage classrooms {% data variables.product.prodname_classroom %}. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Follow the prompts to create a free organization. + +For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." + +### Applying for an educator discount + +Next, you'll sign up for discounts on services from {% data variables.product.company_short %}. {% data reusables.education.educator-requirements %} + +{% tip %} + +**Tip** In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website. + +{% endtip %} + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Set up {% data variables.product.prodname_classroom %} + +With your user account and organization account, you're ready to get started with {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %} is free to use. You can track and manage assignments, grade work automatically, and provide feedback to your students. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To authorize {% data variables.product.prodname_classroom %} to access your user account on {% data variables.product.prodname_dotcom %}, review the information, then click **Authorize {% data variables.product.prodname_classroom %}**. !["Authorize {% data variables.product.prodname_classroom %}" button for user account](/assets/images/help/classroom/setup-click-authorize-github-classroom.png) +1. Review the information. To authorize {% data variables.product.prodname_classroom %} to access your organization account on {% data variables.product.prodname_dotcom %}, click **Grant**. !["Grant" button for organization](/assets/images/help/classroom/setup-click-grant.png) + + {% tip %} + + **Tip**: If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. 詳しい情報については、「[OAuth App を認証する](/github/authenticating-to-github/authorizing-oauth-apps#oauth-apps-and-organizations)」を参照してください。 + + {% endtip %} + +1. Click **Authorize github**. ![Click "Authorize" button for organization](/assets/images/help/classroom/setup-click-authorize-github.png) + +### Create your classroom + +{% data reusables.classroom.about-classrooms %} + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **Create your first classroom** or **New classroom**. +{% data reusables.classroom.guide-create-new-classroom %} + +### 次のステップ + +You've created a classroom, and you're ready to enrich your course with {% data variables.product.product_name %} and {% data variables.product.prodname_classroom %}! 🎉 + +- Watch some videos about {% data variables.product.prodname_classroom %}. For more information, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." +- Manage your classrooms and classroom admins, and create a roster of students for your classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." +- Create an assignment for individual students or teams. {% data reusables.classroom.for-more-information-about-assignment-creation %} +- Write and implement automated tests to provide immediate feedback to students directly in assignment repositories. For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." +- Participate in {% data variables.product.prodname_education_community_with_url %}. diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-campus-advisors.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..4222d7d8e6 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-campus-advisors.md @@ -0,0 +1,17 @@ +--- +title: Campus Advisorsについて +intro: 'インストラクターあるいはメンターとして、Campus Advisorsトレーニング及びサポートと共に学校での{% data variables.product.prodname_dotcom %}の利用について学んでください。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +教授、教師、メンバーはCampus Advisorsオンライントレーニングを使ってGitと{% data variables.product.prodname_dotcom %}をマスターし、{% data variables.product.prodname_dotcom %}で生徒に教えるためのベストプラクティスを学ぶことができます。 詳しい情報については[Campus Advisors](https://education.github.com/teachers/advisors)を参照してください。 + +{% note %} + +**ノート：**インストラクターとして、学生のために{% data variables.product.prodname_dotcom %}のアカウントを作成することはできません。 学生は自分の{% data variables.product.prodname_dotcom %}アカウントを作成しなければなりません。 + +{% endnote %} diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-campus-experts.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..b16451b69f --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-campus-experts.md @@ -0,0 +1,11 @@ +--- +title: Campus Expertsについて +intro: '学生として、{% data variables.product.prodname_dotcom %}Campus Expertsトレーニングで学校の技術コミュニティと実社会のポートフォリオを構築するのに必要なスキルを学んでください。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %}Campus Expertsとして、公の場でのスピーチのスキル、テクニカルライティング、コミュニティのリーダーシップ、ソフトウェア開発のスキルを学んでください。 詳しい情報については[Campus Experts](https://education.github.com/students/experts)を参照してください。 diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..4a26a70835 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,31 @@ +--- +title: 教育者と研究者のためのGitHub Educationについて +intro: '{% data variables.product.prodname_education %}は、教室の内外で教育者や研究者がより効率的に働くことを支援するための様々なツールを提供します。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 教育者のための{% data variables.product.prodname_education %} + +あらゆるレベルの教育者のための {% data variables.product.prodname_education %} のツールとサービスで、以下のことができます: + - [{% data variables.product.prodname_classroom %}](https://classroom.github.com) を使ってコードを配布し、学生にフィードバックを与え、{% data variables.product.prodname_dotcom %} 上の課題を収集する。 + - 弊社の [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) に加わり、世界中の相手と技術教育における現在のトレンドについて議論する。 + - Git と {% data variables.product.prodname_dotcom %} を教えるための弊社の[オープンソースレッスン計画](https://education.github.community/t/open-source-lesson-plans/1591)にアクセスし、必要に応じて調整する。 + - 学生の教育のための素材が入った [{% data variables.product.prodname_dotcom %} のスワッグバッグをリクエスト](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33)する。 + {% data reusables.education.apply-for-team %} + +### 研究者のための {% data variables.product.prodname_education %} + +研究者のための {% data variables.product.prodname_education %} のツールとサービスで、以下のことができます: + - {% data variables.product.prodname_dotcom %} 上で世界中の人々と研究作業についてコラボレートする。 + - 世界中のアカデミックな組織が研究に {% data variables.product.prodname_dotcom %} をどのように使っているかを[学ぶ](https://education.github.com/stories)。 + {% data reusables.education.apply-for-team %} + +### 参考リンク + +- [学生向け {% data variables.product.prodname_education %}について](/articles/about-github-education-for-students) diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..f3424c0aed --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md @@ -0,0 +1,21 @@ +--- +title: 学生のためのGitHub Educationについて +intro: '{% data variables.product.prodname_education %} は学生に対し、{% data variables.product.prodname_dotcom %} のパートナーからのさまざまな開発者ツールへの無料アクセスを含む実世界の体験を提供します。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +学校のプロジェクトで{% data variables.product.prodname_dotcom %}を利用することは、他者とコラボレーションして実世界の体験を見てもらうためのポートフォリオを構築するための実際的な方法です。 + +{% data reusables.education.about-github-education-link %} + +{% data variables.product.prodname_dotcom %} アカウントを持つ誰もが、{% data variables.product.prodname_free_user %} での無制限のパブリックおよびプライベートリポジトリで協業できます。 学生は {% data variables.product.prodname_student_pack %} に応募することもできます。これはプロフェッショナルの開発者が使用するツールやサービスへの無料アクセスを提供します。 For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +あなたが FIRST robotics club のメンバーなら、あなたの指導者はチームが {% data variables.product.prodname_team %} を使って協力し合うことができるよう、教育者割引に応募できます。これによって、無制限のユーザとプライベートリポジトリが無料で提供されます。 For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." + +### 参考リンク + +- [教育者および研究者のための {% data variables.product.prodname_education %} について](/articles/about-github-education-for-educators-and-researchers) diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education.md new file mode 100644 index 0000000000..fe8cc86778 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/about-github-education.md @@ -0,0 +1,23 @@ +--- +title: GitHub Educationについて +intro: '{% data variables.product.prodname_education %} は、{% data variables.product.prodname_dotcom %} を学校のコミュニティのために最大限に活用したいと考える、特定のプログラム要件に同意する学校に対し、特別な無料製品を提供します。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +あなたの中等学校、大学、ブートキャンプは、特定の要件を満たすことに合意すれば、{% data variables.product.prodname_education %} を入手できます。これによって、{% data variables.product.prodname_dotcom %} から最大のメリットを享受できます。メリットとしては以下のものがあります: +- {% data variables.product.prodname_ghe_cloud %}、{% data variables.product.prodname_ghe_server %} +- 弊社の Campus Advisor プログラムと合わせて Git と {% data variables.product.prodname_dotcom %} をマスターするための教師トレーニング +- {% data variables.product.prodname_student_pack %} のような、プレミアムの {% data variables.product.prodname_education %} の機能への自動化されたアクセス +- Campus Experts プログラムをあわせた学生のためのリーダーシップ開発と技術トレーニング + +詳しい情報については[公式{% data variables.product.prodname_education %}](https://education.github.com/partners/schools)ページを参照してください。 + +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)." + +学生のリーダー及び教師に対するトレーニングプログラムについて詳しく学ぶには、[{% data variables.product.prodname_dotcom %}Campus Experts](https://education.github.com/students/experts)及び[ Campus Advisors](https://education.github.com/teachers/advisors)を参照してください。 + +あなたの学校が {% data variables.product.prodname_dotcom %} と {% data variables.product.prodname_education %} スクールとしてパートナーになっていない場合は、個別に {% 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/ja-JP/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..4ea378a753 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,53 @@ +--- +title: Apply for a student developer pack +intro: '学生は {% data variables.product.prodname_student_pack %} に応募できます。これには {% data variables.product.prodname_dotcom %} パートナーからの特典が含まれます。' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 要件 + +{% data variables.product.prodname_student_pack %} に適格であるには、以下を満たしていなければなりません: +- 高等学校、中等学校、大学、ホームスクールまたはそれに類似した教育機関で、学位を取得できるコースに現在在籍している +- 学校が発行した検証可能なメールアドレスを持っているか、現在の在学状況を証明するドキュメントをアップロードしている +- [{% data variables.product.prodname_dotcom %} のユーザアカウント](/articles/signing-up-for-a-new-github-account)を持っている +- 最低でも 13 歳以上であること + +あなたの在学状況を証明する書類には、学生証、授業計画、成績証明書、所属または登録を証明する書類などのコピーがあげられます。 + +学生としての在籍期間、定期的に現在の在学状況の再検証が求められることがあります。 + +{% note %} + +**メモ:** アカデミック割引をアカウント間で移譲することはできません。 割引を適用したいアカウントを複数持っているなら、ユーザアカウントを[マージ](/articles/merging-multiple-user-accounts)し、もしそうしたいなら残すアカウントの[名前を変更する](/articles/changing-your-github-username)ことを検討してください。 + +{% endnote %} + +{% data variables.product.prodname_student_pack %}の更新に関する詳しい情報については[期限切れと更新](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)を参照してください。 + +### {% data variables.product.prodname_student_pack %} への応募 + +{% data reusables.education.benefits-page %} +3. [Which best describes your academic status?（学業の状況を最もよく述べているのは？）] の下で、[** Student（学生）**] を選択してください。 ![学業の状況を選択](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### 期限切れと更新 + +{% data variables.product.prodname_student_pack %}アクセスが期限切れになった場合、まだあなたが適格であれば再応募できる場合があります。ただし、弊社のパートナーからの提供されているものの中には更新できないものがあります。 弊社のパートナーから期限付きで提供されているもののほとんどは、セットアップ後に開始されます。 詳しい情報については[{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)ページを参照してください。 + +無料の {% data variables.product.prodname_student_pack %} プランへのアクセス期限が切れる時期を知るには、アカウントの[支払い設定](https://github.com/settings/billing)にアクセスしてください。 + +### 参考リンク + +- 「[{% data variables.product.prodname_student_pack %} への応募が承認されなかった理由は？](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)」 +- [新しい {% data variables.product.prodname_dotcom %}アカウントへのサインアップ](/articles/signing-up-for-a-new-github-account) +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..579eefda81 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,57 @@ +--- +title: Apply for an educator or researcher discount +intro: '教育者もしくは研究者は、Organization アカウントに対して無料で {% data variables.product.prodname_team %} を受けるために応募できます。' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### 教育者および研究者に対する割引について + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### 教育者割引または研究者割引に応募する + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Organization をアップグレードする + +教育者もしくは研究者割引のリクエストが承認されると、学習コミュニティで利用する Organization を {% data variables.product.prodname_team %} にアップグレードできます。これで、無料で無制限のユーザとプライベートリポジトリの全ての機能が利用できるようになります。 既存の Organization をアップグレードするか、アップグレードする新しい Organization を作成できます。 + +#### 既存の Organization をアップグレードする + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### 新しい Organization をアップグレードする + +{% data reusables.education.upgrade-page %} +1. [{% octicon "plus" aria-label="The plus symbol" %} **Create an organization**] をクリックします。 ![[Create an organization] ボタン](/assets/images/help/education/create-org-button.png) +3. 情報を読んで、[**Create organization**] をクリックします。 ![[Create organization] ボタン](/assets/images/help/education/create-organization-button.png) +4. [Choose a plan] の下で、[**Choose {% data variables.product.prodname_free_team %}**] をクリックします。 +5. プロンプトに従って Organization を作成します。 +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### 参考リンク + +- [教育者あるいは研究者割引が承認されなかった理由は？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved) +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %}ビデオ](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/index.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/index.md new file mode 100644 index 0000000000..cbf8606525 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Teach and learn +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### 目次 + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..26a161bd6b --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub at your educational institution +intro: '{% data variables.product.prodname_education %} および学生やインストラクターのための弊社のさまざまなトレーニングプログラムを使って、学生、インストラクターや IT スタッフのために施設で {% data variables.product.prodname_dotcom %} を使うことのメリットを最大化してください。' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..2b7c04f77b --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub for your schoolwork +intro: '学生として、{% data variables.product.prodname_dotcom %} を使用して学校のプロジェクトで共同作業を行い、現場経験を積んでください。' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..81a8c43d48 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub in your classroom and research +intro: '教育者または研究者として、{% data variables.product.prodname_dotcom %} を使用して、教室、学生または研究グループなどで共同作業を行います。' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..12b6a447c5 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,67 @@ +--- +title: 学生用開発者パックの申請が承認されなかったのはなぜですか？ +intro: '{% data variables.product.prodname_student_pack %} の申請が承認されていない一般的な理由を確認し、正常に再申請するためのヒントを学んでください。' +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved + - /articles/why-was-my-application-for-a-student-developer-pack-denied/ + - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved + - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**ヒント:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### 所属文書の不明確な証明 + +アップロードした画像があなたの現在の学術ステータスを明確に識別していない場合は、学術ステータスのさらなる証明が必要です。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### 未確認ドメインを持つ学術メールの使用 + +学術メールアドレスに未検証ドメインが含まれている場合、学術ステータスのさらなる証明が必要となります。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### 緩い電子メールポリシーを持つ学校からの学術電子メールの使用 + +学校が有料学生登録の前にメールアドレスを発行する場合、学術ステータスのさらなる証明が必要となります。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +学校のドメインに関するその他の質問や懸念がある場合は、学校の IT スタッフにお問い合わせください。 + +### すでに使用されている学術メールアドレス + +別の {% data variables.product.prodname_dotcom %} アカウントの {% data variables.product.prodname_student_pack %} をリクエストするための学術メールアドレスが既に使用されていた場合、その割引が期限切れになるまでは、学術メールアドレスを再利用して別の {% data variables.product.prodname_student_pack %} を正常に申請することはできません。 + +{% note %} + +**メモ:** 複数の個別アカウントを維持することは、{% data variables.product.prodname_dotcom %} [利用規約](/articles/github-terms-of-service/#3-account-requirements)に反しています。 + +{% endnote %} + +複数の個人ユーザアカウントを持っている場合は、自分のアカウントをマージする必要があります。 割引を保持するには、割引を付与されたアカウントをそのままにします。 すべてのメールアドレスを保持アカウントに追加することで、保持アカウントの名前を変更したり、コントリビューション履歴を保存したりできます。 + +詳しい情報については、以下を参照してください。 +- 「[複数のユーザアカウントをマージする](/articles/merging-multiple-user-accounts)」 +- 「[{% data variables.product.prodname_dotcom %} ユーザ名を変更する](/articles/changing-your-github-username)」 +- 「[メールアドレスを {% data variables.product.prodname_dotcom %} アカウントに追加する](/articles/adding-an-email-address-to-your-github-account)」 + +### 対象外の学生ステータス + +以下の場合、{% data variables.product.prodname_student_pack %} の対象外となります: +- 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. +- 13 歳未満の場合。 + +インストラクターは、教室での使用に対して、{% data variables.product.prodname_education %} 割引を適用できます。 コーディングスクールやブートキャンプの学生は、学校が[{% data variables.product.prodname_dotcom %} キャンパスプログラム](https://education.github.com/schools)に参加した場合、{% data variables.product.prodname_student_pack %} を利用できるようになります。 + +### 参考リンク + +- 「[学生開発者パックに応募する](/articles/applying-for-a-student-developer-pack)」 +- "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/ja-JP/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/ja-JP/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..9672653829 --- /dev/null +++ b/translations/ja-JP/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,45 @@ +--- +title: 教育者または研究者割引の申請が承認されなかったのはなぜですか？ +intro: 教育者または研究者割引の申請が承認されていない一般的な理由を確認し、正常に再申請するためのヒントを学びます。 +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**ヒント:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### 所属文書の不明確な証明 + +アップロードした画像が現在の学校または大学での雇用を明確に識別していない場合、教職員 ID または雇用確認書の別の画像を明瞭な情報と共にアップロードして再申請する必要があります。 + +{% data reusables.education.pdf-support %} + +### 未確認ドメインを持つ学術メールの使用 + +学術メールアドレスに未確認ドメインが含まれている場合、学術ステータスの更なる証明が必要となります。 {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### 緩い電子メールポリシーを持つ学校からの学術電子メールの使用 + +学校の卒業生および退職した教職員が学校が発行したメールアドレスに一生アクセスできる場合は、学術ステータスの更なる証明が必要となります。 {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +学校のドメインに関するその他の質問や懸念がある場合は、学校のITスタッフにお問い合わせください。 + +### 学生以外が Student Developer Pack を申請する + +教育者や研究者は、[{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)に付属のパートナーオファーの対象にはなりません。 再度申し込む際には、ご自身の学術ステータスを説明するものとして必ず [**Faculty**] (教職員) を選択してください。 + +### 参考リンク + +- "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md index 7c56d142b9..43e77647c0 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -32,14 +32,14 @@ versions: ### サポートされているリポジトリとエコシステム +サポートされているパッケージマネージャーのいずれかの依存関係マニフェストまたはロックファイルを含むリポジトリのバージョン更新を設定できます。 For some package managers, you can also configure vendoring for dependencies. 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor) 」を参照してください。 + {% note %} -{% data reusables.dependabot.private-dependencies %} +{% 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. See the details in the table below. {% endnote %} -サポートされているパッケージマネージャーのいずれかの依存関係マニフェストまたはロックファイルを含むリポジトリのバージョン更新を設定できます。 For some package managers, you can also configure vendoring for dependencies. 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor) 」を参照してください。 - {% data reusables.dependabot.supported-package-managers %} リポジトリですでに依存関係管理にインテグレーションを使用している場合は、{% data variables.product.prodname_dependabot %} を有効にする前にそれを無効にする必要があります。 詳しい情報については、「[インテグレーションについて](/github/customizing-your-github-workflow/about-integrations)」を参照してください。 diff --git a/translations/ja-JP/content/github/administering-a-repository/about-secret-scanning.md b/translations/ja-JP/content/github/administering-a-repository/about-secret-scanning.md index 54820b441c..fe17372460 100644 --- a/translations/ja-JP/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/ja-JP/content/github/administering-a-repository/about-secret-scanning.md @@ -36,6 +36,7 @@ versions: - Databricks - Datadog - Discord +- Doppler - Dropbox - Dynatrace - Finicity @@ -79,6 +80,8 @@ If you're a repository administrator or an organization owner, you can enable {% Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." + 現在 {% data variables.product.product_name %} は、プライベートリポジトリをスキャンして、次のサービスプロバイダが発行したシークレットを探します。 - Adafruit @@ -90,6 +93,7 @@ Repository administrators and organization owners can grant users and team acces - CloudBees CodeShip - Databricks - Discord +- Doppler - Dropbox - Dynatrace - Finicity diff --git a/translations/ja-JP/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/ja-JP/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index 222804d1e3..1bb28091ca 100644 --- a/translations/ja-JP/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/ja-JP/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -290,7 +290,7 @@ updates: {% data reusables.dependabot.option-affects-security-updates %} ```yaml -# 「ignore」で維持する依存関係をカスタマイズする +# Customizing the dependencies to maintain with `ignore` version: 2 updates: @@ -300,15 +300,16 @@ updates: interval: "daily" ignore: - dependency-name: "express" - # Express の場合、バージョン 4 と 5 のすべての更新を無視する + # For Express, ignore all updates for version 4 and 5 versions: ["4.x", "5.x"] - # Loadash の場合、すべての更新を無視する - - dependency-name: "loadash" + # For Lodash, ignore all updates + - dependency-name: "lodash" ``` {% note %} -構成ファイルの `ignore` オプションにプライベート依存関係を追加しても、{% data variables.product.prodname_dependabot_version_updates %} はプライベート Git 依存関係またはプライベート Git レジストリを含むマニフェストの依存関係のバージョン更新を実行できません。 詳しい情報については、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot#supported-repositories-and-ecosystems)」を参照してください。 +**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-repositories)" 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/github/administering-a-repository/deleting-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/deleting-a-repository.md index 96a89634c7..82fa0260aa 100644 --- a/translations/ja-JP/content/github/administering-a-repository/deleting-a-repository.md +++ b/translations/ja-JP/content/github/administering-a-repository/deleting-a-repository.md @@ -17,7 +17,7 @@ versions: {% warning %} -**Warnings**: +**警告**: - Deleting a repository will **permanently** delete release attachments and team permissions. このアクションは取り消すことが**できません**。 - Deleting a private {% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}or internal {% endif %}repository will delete all forks of the repository. diff --git a/translations/ja-JP/content/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/ja-JP/content/github/administering-a-repository/enabling-and-disabling-version-updates.md index 6b2ebc9cab..c9fbb47900 100644 --- a/translations/ja-JP/content/github/administering-a-repository/enabling-and-disabling-version-updates.md +++ b/translations/ja-JP/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -14,14 +14,10 @@ versions: {% data reusables.dependabot.initial-updates %} 詳しい情報については、「[依存関係の更新をカスタマイズする](/github/administering-a-repository/customizing-dependency-updates)」をご覧ください。 +{% 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)." + ### Enabling {% data variables.product.prodname_dependabot_version_updates %} -{% note %} - -{% data reusables.dependabot.private-dependencies %} - -{% endnote %} - {% data reusables.dependabot.create-dependabot-yml %} 1. `package-ecosystem` を使用して、監視するパッケージマネージャーを指定します。 1. パッケージマネージャーごとに、以下を使用します。 diff --git a/translations/ja-JP/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/ja-JP/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md new file mode 100644 index 0000000000..2e14f6950f --- /dev/null +++ b/translations/ja-JP/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -0,0 +1,20 @@ +--- +title: Enabling or disabling GitHub Discussions for a repository +intro: 'You can use discussions in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.' +product: '{% data reusables.gated-features.discussions %}' +permissions: People with admin permissions to a repository can enable discussions for the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Enabling or disabling discussions for your repository + +{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} +1. To disable discussions, under "Features", unselect **Discussions**. + +### 参考リンク + +- "[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/github/administering-a-repository/index.md b/translations/ja-JP/content/github/administering-a-repository/index.md index a2a69f7065..fa25231660 100644 --- a/translations/ja-JP/content/github/administering-a-repository/index.md +++ b/translations/ja-JP/content/github/administering-a-repository/index.md @@ -12,36 +12,25 @@ versions: ### 目次 {% topic_link_in_list /managing-repository-settings %} - {% link_in_list /setting-repository-visibility %}{% if currentVersion == "free-pro-team@latest" %} - {% link_in_list /managing-teams-and-people-with-access-to-your-repository %}{% endif %} + {% link_in_list /setting-repository-visibility %} + {% link_in_list /managing-teams-and-people-with-access-to-your-repository %} {% link_in_list /classifying-your-repository-with-topics %} {% link_in_list /customizing-how-changed-files-appear-on-github %} {% link_in_list /about-email-notifications-for-pushes-to-your-repository %} - {% link_in_list /displaying-a-sponsor-button-in-your-repository %} - - {% link_in_list /customizing-your-repositorys-social-media-preview %} - - {% link_in_list /viewing-deployment-activity-for-your-repository %} - {% link_in_list /managing-the-forking-policy-for-your-repository %} - {% link_in_list /setting-the-default-branch %} - {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %} + {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /enabling-or-disabling-github-discussions-for-a-repository %}{% endif %} {% link_in_list /managing-git-lfs-objects-in-archives-of-your-repository %} {% link_in_list /enabling-anonymous-git-read-access-for-a-repository %} - - {% link_in_list /configuring-autolinks-to-reference-external-resources %} - {% link_in_list /renaming-a-repository %} {% link_in_list /transferring-a-repository %} {% link_in_list /deleting-a-repository %} - {% link_in_list /restoring-a-deleted-repository %} - {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} {% link_in_list /changing-the-default-branch %} @@ -50,9 +39,7 @@ versions: {% link_in_list /about-merge-methods-on-github %} {% link_in_list /configuring-commit-squashing-for-pull-requests %} {% link_in_list /configuring-commit-rebasing-for-pull-requests %} - {% link_in_list /managing-the-automatic-deletion-of-branches %} - {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} {% link_in_list /configuring-protected-branches %} @@ -65,31 +52,22 @@ versions: {% link_in_list /enabling-required-reviews-for-pull-requests %} {% link_in_list /about-required-commit-signing %} {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} {% link_in_list /enabling-force-pushes-to-a-protected-branch %} {% link_in_list /enabling-deletion-of-a-protected-branch %} - {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} {% link_in_list /viewing-your-repositorys-releases-and-tags %} {% link_in_list /linking-to-releases %} - {% link_in_list /comparing-releases %} - - {% link_in_list /automation-for-release-forms-with-query-parameters %} - - {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} {% link_in_list /configuring-secret-scanning-for-private-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} - - {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} {% link_in_list /about-dependabot-version-updates %} {% link_in_list /enabling-and-disabling-version-updates %} @@ -98,4 +76,3 @@ versions: {% link_in_list /customizing-dependency-updates %} {% link_in_list /configuration-options-for-dependency-updates %} {% link_in_list /keeping-your-actions-up-to-date-with-dependabot %} - diff --git a/translations/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 3dcb634f52..e5820aeac8 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 @@ -33,7 +33,7 @@ Organization のオーナーは、リポジトリの可視性を変更する機 {% note %} -**Note:** {% data reusables.gated-features.internal-repos %} +**注釈:** {% data reusables.gated-features.internal-repos %} {% endnote %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-anonymized-image-urls.md b/translations/ja-JP/content/github/authenticating-to-github/about-anonymized-image-urls.md index d41e16a2bd..fa7aee936a 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/about-anonymized-image-urls.md +++ b/translations/ja-JP/content/github/authenticating-to-github/about-anonymized-image-urls.md @@ -8,7 +8,7 @@ versions: free-pro-team: '*' --- -画像をホストするために、{% data variables.product.product_name %}は[オープンソースプロジェクトの Camo](https://github.com/atmos/camo) を使用します。 Camo generates an anonymous URL proxy for each image which hides your browser details and related information from other users. The URL starts `https://.githubusercontent.com/`, with different subdomains depending on how you uploaded the image. +画像をホストするために、{% data variables.product.product_name %}は[オープンソースプロジェクトの Camo](https://github.com/atmos/camo) を使用します。 Camo は、画像ごとに匿名の URL プロキシを生成し、ブラウザの詳細と関連情報を他のユーザから見えないようにします。 URL は `https://.githubusercontent.com/` で始まり、画像のアップロード方法に応じて異なるサブドメインがあります。 匿名化した画像URLを受け取った人は、直接であれ間接であれ、その画像を見ることができます。 機密の画像をプライベートにしておきたい場合は、Camoを使う代わりにそれらを認証が必要なプライベートなネットワークあるいはサーバーから提供するようにしてください。 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 58bb973e92..59f5a45e13 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 @@ -9,17 +9,17 @@ versions: ### {% data variables.product.prodname_dotcom %} への認証について -To keep your account secure, you must authenticate before you can access{% if currentVersion != "github-ae@latest" %} certain{% endif %} resources on {% data variables.product.product_name %}. {% data variables.product.product_name %} への認証を行うときは、自分が確かに本人であることを証明するために、固有の認証情報を提供または確認します。 +アカウントを安全に保つには、{% data variables.product.product_name %} の {% if currentVersion != "github-ae@latest" %} 特定 {% endif %} のリソースにアクセスする前に認証する必要があります。 {% data variables.product.product_name %} への認証を行うときは、自分が確かに本人であることを証明するために、固有の認証情報を提供または確認します。 {% data variables.product.product_name %} のリソースには、ブラウザ内、{% data variables.product.prodname_desktop %} または別のデスクトップアプリケーション経由、API 経由、またはコマンドライン経由など、さまざまな方法でアクセスできます。 {% data variables.product.product_name %} へのアクセス方法は、それぞれ異なる認証モードをサポートしています。 -- {% if currentVersion == "github-ae@latest" %}Your identity provider (IdP){% else %}Username and password with two-factor authentication{% endif %} +- {% if currentVersion == "github-ae@latest" %} ID プロバイダ (IdP) {% else %} 2 要素認証を使用したユーザ名とパスワード{% endif %} - 個人アクセストークン - SSH キー ### ブラウザで認証する -You can authenticate to {% data variables.product.product_name %} in your browser {% if currentVersion == "github-ae@latest" %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways. +IdP を使用して、ブラウザ {% if currentVersion == "github-ae@latest" %} で {% data variables.product.product_name %} に認証できます。 詳しい情報については、いくつかの方法で{% else %}「[SAML シングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」を参照してください。 - **ユーザ名とパスワードのみ** - {% data variables.product.product_name %} でユーザアカウントを作成するときにパスワードを作成します。 パスワードマネージャを使用して、ランダムで一意のパスワードを生成することをお勧めします。 詳しい情報については、「[強力なパスワードを作成する](/github/authenticating-to-github/creating-a-strong-password)」を参照してください。 @@ -34,7 +34,7 @@ You can authenticate to {% data variables.product.product_name %} in your browse ### API で認証する -You can authenticate with the API in different ways. +さまざまな方法で API を使用して認証できます。 - **個人アクセストークン** - テストなどの限られた状況では、個人アクセストークンを使用して API にアクセスできます。 個人アクセストークンを使用すると、いつでもアクセスを取り消すことができます。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。 @@ -51,4 +51,4 @@ You can authenticate with the API in different ways. * 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" %}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. 詳しい情報については、[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" %} 個人アクセストークンまたは 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 %} 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 dfa204a918..fd16a10fde 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,5 +1,5 @@ --- -title: SAMLのシングルサインオンでの認証について +title: About authentication with SAML single sign-on intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data variables.product.product_location %}{% elsif currentVersion == "free-pro-team@latest" %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% if currentVersion == "github-ae@latest" %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% if currentVersion == "free-pro-team@latest" %}To authenticate with the API or Git on the command line when an organization enforces SAML SSO, you must authorize your personal access token or SSH key.{% endif %}' product: '{% data reusables.gated-features.saml-sso %}' redirect_from: @@ -15,33 +15,33 @@ SAML SSO allows an enterprise owner to centrally control and secure access to {% {% data reusables.saml.you-must-periodically-authenticate %} -If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. +If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. {% endif %} {% if currentVersion == "free-pro-team@latest" %} -{% data reusables.saml.dotcom-saml-explanation %}Organization のオーナーは、{% data variables.product.prodname_dotcom %}でユーザアカウントを SAML SSO を使用する Organization に招待できます。これにより、Organization に貢献することができ、{% data variables.product.prodname_dotcom %}の既存の ID とコントリビューションを保持できます。 +{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your user account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. -SAML SSO を使用する Organization のリソースにアクセスすると、{% data variables.product.prodname_dotcom %}は認証のために Organization の SAML IdP にリダイレクトします。 IdP でアカウントが正常に認証されると、IdP は{% data variables.product.prodname_dotcom %}に戻り、Organization のリソースにアクセスできます。 +When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. {% data reusables.saml.outside-collaborators-exemption %} -最近ブラウザで Organization の SAML IdP が認証された場合、SAML SSO を使う {% data variables.product.prodname_dotcom %} の Organization へのアクセスは自動的に認可されます。 最近ブラウザで Organization の SAML IdP が認証されていない場合は、Organization にアクセスする前に SAML IdP で認証を受ける必要があります。 +If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. {% data reusables.saml.you-must-periodically-authenticate %} -SAML SSL を要求する Organization 内の保護されたコンテンツにアクセスするために API またはコマンドライン上の Git を利用するには、認可された個人のアクセストークンを HTTPS 経由で使うか、認可された SSH キーを使う必要があります。 {% data variables.product.prodname_oauth_app %} アクセストークンはデフォルトで認可されます。 +To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized personal access token over HTTPS or an authorized SSH key. {% data variables.product.prodname_oauth_app %} access tokens are authorized by default. -個人のアクセストークンあるいは SSH キーを持っていない場合、コマンドライン用の個人のアクセストークンを作成するか、新しい SSH キーを生成できます。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」または「[新しい SSH キーを生成して ssh-agent へ追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。 +If you don't have a personal access token or an SSH key, you can create a personal access token for the command line or generate a new SSH key. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -新しい、または既存の個人のアクセストークンか 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)」を参照してください。 +To use a new or existing personal access token or SSH key with an organization that enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -{% data variables.product.prodname_oauth_app %}を認証するたびにアクティブなSAML セッションが必要です。 +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %}. {% endif %} -### 参考リンク +### Further reading {% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} {% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md b/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md index a8a84ffbf4..10ef6e9044 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md +++ b/translations/ja-JP/content/github/authenticating-to-github/about-commit-signature-verification.md @@ -1,6 +1,6 @@ --- title: コミット署名の検証について -intro: 'Using GPG or S/MIME, you can sign tags and commits locally. それらのタグやコミットは検証済みとして {% data variables.product.product_name %}上でマークされ、他の人々がその変更が信頼できるソースから来たものと信頼できるようになります。' +intro: 'GPG または S/MIME を使用して、タグに署名し、ローカルでコミットできます。 それらのタグやコミットは検証済みとして {% data variables.product.product_name %}上でマークされ、他の人々がその変更が信頼できるソースから来たものと信頼できるようになります。' redirect_from: - /articles/about-gpg-commit-and-tag-signatures/ - /articles/about-gpg/ @@ -23,7 +23,7 @@ versions: {% data variables.product.product_name %}上の署名されたコミットあるいはタグの検証ステータスをチェックして、コミットの署名が検証されない理由を見ることができます。 詳細は「[コミットおよびタグの署名の検証のステータスをチェックする](/articles/checking-your-commit-and-tag-signature-verification-status)」を参照してください。 -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface, except for when you squash and merge a pull request that you are not the author of. {% data variables.product.product_name %}によって署名されたコミットは、{% data variables.product.product_name %}で認証済みのステータスになります。 署名は、https://github.com/web-flow.gpgから利用できる公開鍵を使ってローカルに検証できます。{% endif %} +{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} は自動的に GPG を使用して、{% data variables.product.product_name %} Web インターフェースを使用して行ったコミットに署名します。ただし、作者ではないプルリクエストを squash してマージする場合を除きます。 {% data variables.product.product_name %}によって署名されたコミットは、{% data variables.product.product_name %}で認証済みのステータスになります。 署名は、https://github.com/web-flow.gpgから利用できる公開鍵を使ってローカルに検証できます。{% endif %} ### GPG コミット署名の検証 @@ -60,9 +60,9 @@ S/MIME を使ってコミットに署名し、それらのコミットを {% dat ### ボットの署名検証 コミットの署名が必要な Organization および {% data variables.product.prodname_github_app %} は、コミットの署名にボットを利用できます。 コミットまたはタグが暗号的に検証可能なボット署名を持っている場合、{% data variables.product.product_name %} はそのコミットまたはタグを検証済みとしてマークします。 -Signature verification for bots will only work if the request is verified and authenticated as the +ボットの署名検証は、リクエストが -{% data variables.product.prodname_github_app %} or bot and contains no custom author information, custom committer information, and no custom signature information, such as Commits API. +{% data variables.product.prodname_github_app %} またはボットとして検証および認証され、カスタム作者情報、カスタムコミッタ情報、および Commits API などのカスタム署名情報が含まれていない場合にのみ機能します。 {% endif %} ### 参考リンク diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-ssh.md b/translations/ja-JP/content/github/authenticating-to-github/about-ssh.md index 1b1cd5ee6e..041f1d6621 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/about-ssh.md +++ b/translations/ja-JP/content/github/authenticating-to-github/about-ssh.md @@ -1,6 +1,6 @@ --- title: SSH について -intro: 'SSH プロトコルを利用すれば、リモートのサーバーやサービスに接続し、認証を受けられます。 With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.' +intro: 'SSH プロトコルを利用すれば、リモートのサーバーやサービスに接続し、認証を受けられます。 SSH キーを使用すると、アクセスのたびにユーザ名と個人アクセストークンを入力することなく {% data variables.product.product_name %} に接続できます。' redirect_from: - /articles/about-ssh versions: @@ -11,13 +11,13 @@ versions: SSH をセットアップする際には、[SSH キーを生成し、ssh-agent に追加](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)し、それから [ キーを自分の {% data variables.product.product_name %}アカウントに追加](/articles/adding-a-new-ssh-key-to-your-github-account)します。 SSH キーを ssh-agent に追加することで、パスフレーズの利用を通じて SSH キーに追加のセキュリティのレイヤーを持たせることができます。 詳しい情報については[SSH キーのパスフレーズを使う](/articles/working-with-ssh-key-passphrases)を参照してください。 -{% if currentVersion == "free-pro-team@latest" %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you'll need to authorize it first. 詳しい情報については、「[SAML シングルサインオンで使うために SSH キーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。{% endif %} +{% if currentVersion == "free-pro-team@latest" %} SAML シングルサインオンを利用している Organization が所有するリポジトリで SSH キーを使用するには、まずはそのキーを認証する必要があります。 詳しい情報については、「[SAML シングルサインオンで使うために SSH キーを認可する](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。{% endif %} 定期的に [SSH キーのリストをレビュー](/articles/reviewing-your-ssh-keys)し、不正になったものや悪用されたものを取り除くことをおすすめします。 {% if currentVersion == "free-pro-team@latest" %} -If you haven't used your SSH key for a year, then -{% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. 詳細は「[削除されたか存在しない SSH キー](/articles/deleted-or-missing-ssh-keys)」を参照してください。 +SSH キーを 1 年間使用していない場合、 +セキュリティ上の予防措置として、{% data variables.product.prodname_dotcom %} は使用されていない SSH キーを自動的に削除します。 詳細は「[削除されたか存在しない SSH キー](/articles/deleted-or-missing-ssh-keys)」を参照してください。 {% endif %} SSH 証明書を提供する Organization のメンバーである場合、{% data variables.product.product_name %} アカウントにあなたの証明書を追加することなく、その証明書で Organization のリポジトリにアクセスできます。 詳しい情報については、「[SSH 認証局について](/articles/about-ssh-certificate-authorities)」を参照してください。 diff --git a/translations/ja-JP/content/github/authenticating-to-github/about-two-factor-authentication.md b/translations/ja-JP/content/github/authenticating-to-github/about-two-factor-authentication.md index 2331a1071e..9162ba9b5d 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/about-two-factor-authentication.md +++ b/translations/ja-JP/content/github/authenticating-to-github/about-two-factor-authentication.md @@ -1,6 +1,6 @@ --- title: 2 要素認証について -intro: '{% data reusables.two_fa.about-2fa %} With 2FA, you have to log in with your username and password and provide another form of authentication that only you know or have access to.' +intro: '{% data reusables.two_fa.about-2fa %} 2FA では、ユーザ名とパスワードを使用してログインし、さらに自分だけが知っている、または利用できる別の形式の認証でログインする必要があります。' redirect_from: - /articles/about-two-factor-authentication versions: @@ -8,7 +8,7 @@ versions: enterprise-server: '*' --- -For {% data variables.product.product_name %}, the second form of authentication is a code that's generated by an application on your mobile device{% if currentVersion == "free-pro-team@latest" %} or sent as a text message (SMS){% endif %}. 2FA を有効化すると、{% data variables.product.product_name %}は誰かが {% data variables.product.product_name %}アカウントにサインインしようとすると認証コードを生成します。 誰かがアカウントサインインできるのは、パスワードを知っており、電話上の認証コードも利用できる場合のみです。 +{% data variables.product.product_name %} の場合、2 番目の認証の形式は、モバイルデバイス上のアプリケーションによって生成されるコード{% if currentVersion == "free-pro-team@latest" %}、またはテキストメッセージ (SMS) として送信されるコードになります{% endif %}。 2FA を有効化すると、{% data variables.product.product_name %}は誰かが {% data variables.product.product_name %}アカウントにサインインしようとすると認証コードを生成します。 誰かがアカウントサインインできるのは、パスワードを知っており、電話上の認証コードも利用できる場合のみです。 {% data reusables.two_fa.after-2fa-add-security-key %} @@ -34,6 +34,6 @@ For {% data variables.product.product_name %}, the second form of authentication ### Organization で 2 要素認証を要求する -Organization owners can require that organization members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators use two-factor authentication to secure their personal accounts. 詳しい情報については [Organization で 2 要素認証を要求する](/articles/requiring-two-factor-authentication-in-your-organization)を参照してください。 +Organization のオーナーは、Organization のメンバー{% if currentVersion == "free-pro-team@latest" %}、支払いマネージャー{% endif %}および外部のコラボレータが個人アカウントを保護するために 2 要素認証を使うことを要求できます。 詳しい情報については [Organization で 2 要素認証を要求する](/articles/requiring-two-factor-authentication-in-your-organization)を参照してください。 {% data reusables.two_fa.auth_methods_2fa %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md b/translations/ja-JP/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md index f395c21ae4..2a84026006 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md +++ b/translations/ja-JP/content/github/authenticating-to-github/accessing-github-using-two-factor-authentication.md @@ -15,7 +15,7 @@ versions: ### Web サイトへのサインインの際に 2FA コードを提供 -After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% if currentVersion == "free-pro-team@latest" %}a text message or{% endif %} your TOTP app. +パスワードを使用して {% data variables.product.product_name %} にサインインすると、{% if currentVersion == "free-pro-team@latest" %} テキストメッセージまたは{% endif %} TOTP アプリから認証コードを入力するように求められます。 {% data variables.product.product_name %}が 2FA 認証コードを再度求めるのは、ログアウトした場合、新しいデバイスを使う場合、またはセッションが期限切れになった場合のみです。 diff --git a/translations/ja-JP/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/ja-JP/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md index ac363d56f7..40413aeba4 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/ja-JP/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -19,13 +19,13 @@ versions: {% mac %} -1. SSH キーをクリップボードにコピーしてください。 +1. SSH 公開鍵をクリップボードにコピーします。 - 使用する SSH キーの名前がサンプルのコードとは違っている場合は、現在の設定に合わせてファイル名を修正してください。 キーをコピーする際には、改行や空白を追加しないでください。 + SSH 公開鍵のファイル名がサンプルコードと異なる場合は、現在の設定に一致するようにファイル名を変更してください。 キーをコピーする際には、改行や空白を追加しないでください。 ```shell $ pbcopy < ~/.ssh/id_ed25519.pub - # Copies the contents of the id_ed25519.pub file to your clipboard + # id_ed25519.pub ファイルの内容をクリップボードにコピーする ``` {% tip %} @@ -46,13 +46,13 @@ versions: {% windows %} -1. SSH キーをクリップボードにコピーしてください。 +1. SSH 公開鍵をクリップボードにコピーします。 - 使用する SSH キーの名前がサンプルのコードとは違っている場合は、現在の設定に合わせてファイル名を修正してください。 キーをコピーする際には、改行や空白を追加しないでください。 + SSH 公開鍵のファイル名がサンプルコードと異なる場合は、現在の設定に一致するようにファイル名を変更してください。 キーをコピーする際には、改行や空白を追加しないでください。 ```shell $ clip < ~/.ssh/id_ed25519.pub - # Copies the contents of the id_ed25519.pub file to your clipboard + # id_ed25519.pub ファイルの内容をクリップボードにコピーする ``` {% tip %} @@ -73,16 +73,16 @@ versions: {% linux %} -1. SSH キーをクリップボードにコピーしてください。 +1. SSH 公開鍵をクリップボードにコピーします。 - 使用する SSH キーの名前がサンプルのコードとは違っている場合は、現在の設定に合わせてファイル名を修正してください。 キーをコピーする際には、改行や空白を追加しないでください。 + SSH 公開鍵のファイル名がサンプルコードと異なる場合は、現在の設定に一致するようにファイル名を変更してください。 キーをコピーする際には、改行や空白を追加しないでください。 ```shell $ sudo apt-get install xclip # xclip をダウンロードしてインストールします。 If you don't have `apt-get`, you might need to use another installer (like `yum`) $ xclip -selection clipboard < ~/.ssh/id_ed25519.pub - # Copies the contents of the id_ed25519.pub file to your clipboard + # id_ed25519.pub ファイルの内容をクリップボードにコピーする ``` {% tip %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md b/translations/ja-JP/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md index 1121ac5d79..0b2e636839 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md +++ b/translations/ja-JP/content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md @@ -26,7 +26,7 @@ versions: ```shell $ gpg> adduid ``` -6. プロンプトに従って、本名、メールアドレス、あればコメントを入力してください。 エントリーは、`N`、`C`、`E` を選択して変更できます。 {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."{% endif %} +6. プロンプトに従って、本名、メールアドレス、あればコメントを入力してください。 エントリーは、`N`、`C`、`E` を選択して変更できます。 {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} 詳しい情報については、「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address)」を参照してください。{% endif %} ```shell Real Name: Octocat Email address: octocat@github.com diff --git a/translations/ja-JP/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md b/translations/ja-JP/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md index 261858f19c..9607892e71 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: SAMLシングルサインオンで認証する -intro: 'You can authenticate to {% if currentVersion == "free-pro-team@latest" %}a {% data variables.product.product_name %} organization {% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %} {% endif %}with SAML single sign-on (SSO){% if currentVersion == "free-pro-team@latest" %} and view your active sessions{% endif %}.' +intro: 'SAML シングルサインオン (SSO) {% if currentVersion == "free-pro-team@latest" %}を使用して {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} Organization{% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %} {% endif %} に対して認証し、アクティブなセッションを表示できます{% endif %}。' mapTopic: true product: '{% data reusables.gated-features.saml-sso %}' redirect_from: diff --git a/translations/ja-JP/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/ja-JP/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md index 6b3d217d5e..a708cf4712 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md @@ -15,7 +15,7 @@ versions: {% data reusables.user_settings.personal_access_tokens %} 3. 認可したいトークンの隣の [**Enable SSO**] (SSO を有効化) または [**Disable SSO**] (SSOを無効化) をクリックします。 ![SSO トークン認可ボタン](/assets/images/help/settings/sso-allowlist-button.png) 4. アクセストークンを認可する Organization を見つけます。 -4. Click **Authorize**. ![トークン認可ボタン](/assets/images/help/settings/token-authorize-button.png) +4. [**Authorize**] をクリックします。 ![トークン認可ボタン](/assets/images/help/settings/token-authorize-button.png) ### 参考リンク diff --git a/translations/ja-JP/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/ja-JP/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md index d5477cac31..fb63a24c25 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md @@ -20,7 +20,7 @@ versions: {% data reusables.user_settings.ssh %} 3. 認可したい SSH キーの隣の [**Enable SSO**] (SSO を有効化) または [**Disable SSO**] (SSOを無効化) をクリックします。 ![SSO トークン認可ボタン](/assets/images/help/settings/ssh-sso-button.png) 4. SSH キーを認可する Organization を見つけます。 -5. Click **Authorize**. ![トークン認可ボタン](/assets/images/help/settings/ssh-sso-authorize.png) +5. [**Authorize**] をクリックします。 ![トークン認可ボタン](/assets/images/help/settings/ssh-sso-authorize.png) ### 参考リンク diff --git a/translations/ja-JP/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md b/translations/ja-JP/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md index 9fd546d6fb..655895f523 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md +++ b/translations/ja-JP/content/github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status.md @@ -14,7 +14,7 @@ versions: 1. On -{% data variables.product.product_name %}, navigate to your pull request. +{% data variables.product.product_name %} 上で、プルリクエストに移動します。 {% data reusables.repositories.review-pr-commits %} 3. コミットの短縮版コミットハッシュの隣に、コミットの署名が検証されているかどうかを示すボックスがあります。 ![署名されたコミット](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) 4. コミットの署名について詳しい情報を表示するには、[**Verified**] または [**Unverified**] をクリックします。 ![検証された署名済みコミット](/assets/images/help/commits/gpg-signed-commit_verified_details.png) diff --git a/translations/ja-JP/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md b/translations/ja-JP/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md index f1a1dfce55..dd3985bce5 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/ja-JP/content/github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods.md @@ -91,7 +91,7 @@ Recovery Accounts Elsewhere を使用して、あなたの {% data variables.pro アカウントリカバリトークンを生成し、パートナーリカバリプロバイダを利用して保存できます。 -1. Sign in to your Facebook account, then return to +1. Facebook アカウントにサインインしてから、 {% data variables.product.product_name %} の Enterprise 設定を使用してアナウンスバナーを設定することもできます。 {% data reusables.user_settings.access_settings %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/configuring-two-factor-authentication.md b/translations/ja-JP/content/github/authenticating-to-github/configuring-two-factor-authentication.md index 97427254a7..cd59943d2a 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/configuring-two-factor-authentication.md +++ b/translations/ja-JP/content/github/authenticating-to-github/configuring-two-factor-authentication.md @@ -11,14 +11,14 @@ versions: enterprise-server: '*' --- -You can configure two-factor authentication using a mobile app{% if currentVersion == "free-pro-team@latest" %} or via text message{% endif %}. また、セキュリティキーを追加することも可能です。 +モバイルアプリまたは {% if currentVersion == "free-pro-team@latest" %} テキストメッセージ{% endif %}を使って、2 要素認証を設定できます。 また、セキュリティキーを追加することも可能です。 -We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% if currentVersion == "free-pro-team@latest" %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device. +2 要素認証の設定には、時間ベースのワンタイムパスワード (TOTP) アプリケーションを使うことを強くおすすめします。{% if currentVersion == "free-pro-team@latest" %}TOTP アプリケーションは、特に米国外において、SMS より信頼性があります。{% endif %}TOTP アプリは、クラウド内にある認証コードのセキュアなバックアップをサポートしており、デバイスにアクセスできなくなった場合に回復できます。 {% warning %} **警告:** -- If you're a member{% if currentVersion == "free-pro-team@latest" %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.product.product_location %}. +- 2 要素認証が必要なメンバー{% if currentVersion == "free-pro-team@latest" %}、支払いマネージャー、{% endif %}または Organization のプライベートリポジトリへの外部コラボレーターは、2 要素認証を無効化する前に {% data variables.product.product_location %} で Organization から離脱する必要があります。 - 2 要素認証を無効化すると、Organization や Organization のプライベートリポジトリのフォークへのアクセスも失います。 Organization およびフォークへのアクセスを再取得するには、2 要素認証を再有効化し、Organization オーナーに連絡します。 {% endwarning %} @@ -45,8 +45,8 @@ We strongly recommend using a time-based one-time password (TOTP) application to 8. [Two-factor authentication] ページで、次のいずれかを実行します: - QR コードを、モバイルデバイスのアプリでスキャンする。 スキャン後、アプリは {% data variables.product.product_name %} で入力する 6 桁の数字を表示します。 - QR コードをスキャンできない場合は、[**enter this text code**] をクリックしてコードを表示し、それをコピーして {% data variables.product.product_name %} に手入力してください。 ![[enter this code] をクリック](/assets/images/help/2fa/totp-click-enter-code.png) -9. The TOTP mobile application saves your -{% data variables.product.product_name %} account and generates a new authentication code every few seconds. {% data variables.product.product_name %} の 2 要素認証ページでコードを入力し、[**Enable**] をクリックします。 +9. TOTP モバイルアプリケーションは、 +{% data variables.product.product_name %} アカウントを保存し、数秒ごとに新しい認証コードを生成します。 {% data variables.product.product_name %} の 2 要素認証ページでコードを入力し、[**Enable**] をクリックします。 ![[TOTP Enable] フィールド](/assets/images/help/2fa/totp-enter-code.png) {% data reusables.two_fa.test_2fa_immediately %} @@ -81,10 +81,10 @@ TOTP モバイルアプリを使って認証できない場合は、SMS メッ ほとんどのデバイスとブラウザでは、USB または NFC を介して物理セキュリティキーを使用できます。 一部のブラウザでは、デバイス上の指紋リーダー、顔認識、またはパスワード/ PIN をセキュリティキーとして使用できます。 -Authentication with a security key is *secondary* to authentication with a TOTP application{% if currentVersion == "free-pro-team@latest" %} or a text message{% endif %}. セキュリティキーをなくした場合でも、モバイルデバイスのコードを使ってサインインできます。 +セキュリティキーによる認証は、TOTP アプリケーション{% if currentVersion == "free-pro-team@latest" %}またはテキストメッセージ{% endif %}による認証の*二次的な*方法です。 セキュリティキーをなくした場合でも、モバイルデバイスのコードを使ってサインインできます。 -1. You must have already configured 2FA via a TOTP mobile app{% if currentVersion == "free-pro-team@latest" %} or via SMS{% endif %}. -2. Ensure that you have a WebAuthn compatible security key inserted into your computer. +1. TOTP モバイルアプリ{% if currentVersion == "free-pro-team@latest" %}または SMS{% endif %} 経由で、あらかじめ 2 要素認証を設定しておく必要があります。 +2. コンピュータに WebAuthn 準拠のセキュリティキーが挿入されていることを確認してください。 {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security %} 5. [Security keys] の隣にある [**Add**] をクリックします。 ![セキュリティキーの追加オプション](/assets/images/help/2fa/add-security-keys-option.png) diff --git a/translations/ja-JP/content/github/authenticating-to-github/connecting-with-third-party-applications.md b/translations/ja-JP/content/github/authenticating-to-github/connecting-with-third-party-applications.md index 4a7187703a..84da980b42 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/connecting-with-third-party-applications.md +++ b/translations/ja-JP/content/github/authenticating-to-github/connecting-with-third-party-applications.md @@ -52,17 +52,17 @@ versions: {% endtip %} -| データの種類 | 説明 | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| コミットのステータス | サードパーティアプリケーションに、コミットのステータスを報告するためのアクセスを許可できます。 コミットステータスのアクセスがあれば、アプリケーションはビルドが特定のコミットに対して成功したかどうかを判定できます。 アプリケーションは、コードにはアクセスできませんが、特定のコミットに対するステータス情報を読み書きできます。 | -| デプロイメント | Deployment status access allows applications to determine if a deployment is successful against a specific commit for public and private repositories. Applications won't have access to your code. | -| Gist | [Gist](https://gist.github.com) アクセスがあれば、アプリケーションはあなたのパブリックおよびシークレット Gist の両方を読み書きできます。 | -| フック | [webhook](/webhooks) アクセスがあれば、アプリケーションはあなたが管理するリポジトリ上のフックの設定を読み書きできます。 | -| 通知 | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. ただし、アプリケーションはリポジトリ内へはアクセスできません。 | -| Organization および Team | Organization および Team のアクセスがあれば、アプリケーションは Organization および Team のメンバー構成へのアクセスと管理ができます。 | -| 個人ユーザデータ | ユーザデータには、名前、メールアドレス、所在地など、ユーザプロファイル内の情報が含まれます。 | -| リポジトリ | リポジトリ情報には、コントリビュータの名前、あなたが作成したブランチ、リポジトリ内の実際のファイルなどが含まれます。 アプリケーションは、ユーザ単位でパブリックまたはプライベートリポジトリへのアクセスをリクエストできます。 | -| リポジトリの削除 | アプリケーションはあなたが管理するリポジトリの削除をリクエストできますが、コードにアクセスすることはできません。 | +| データの種類 | 説明 | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| コミットのステータス | サードパーティアプリケーションに、コミットのステータスを報告するためのアクセスを許可できます。 コミットステータスのアクセスがあれば、アプリケーションはビルドが特定のコミットに対して成功したかどうかを判定できます。 アプリケーションは、コードにはアクセスできませんが、特定のコミットに対するステータス情報を読み書きできます。 | +| デプロイメント | デプロイメントステータスにアクセスできれば、アプリケーションは、パブリックリポジトリおよびプライベートリポジトリの特定のコミットに対してデプロイメントが成功したかどうかを判断できます。 アプリケーションはコードにアクセスできなくなります。 | +| Gist | [Gist](https://gist.github.com) アクセスがあれば、アプリケーションはあなたのパブリックおよびシークレット Gist の両方を読み書きできます。 | +| フック | [webhook](/webhooks) アクセスがあれば、アプリケーションはあなたが管理するリポジトリ上のフックの設定を読み書きできます。 | +| 通知 | 通知アクセスがあれば、アプリケーションは Issue やプルリクエストへのコメントなど、あなたの {% data variables.product.product_name %} 通知を読むことができます。 ただし、アプリケーションはリポジトリ内へはアクセスできません。 | +| Organization および Team | Organization および Team のアクセスがあれば、アプリケーションは Organization および Team のメンバー構成へのアクセスと管理ができます。 | +| 個人ユーザデータ | ユーザデータには、名前、メールアドレス、所在地など、ユーザプロファイル内の情報が含まれます。 | +| リポジトリ | リポジトリ情報には、コントリビュータの名前、あなたが作成したブランチ、リポジトリ内の実際のファイルなどが含まれます。 アプリケーションは、ユーザ単位でパブリックまたはプライベートリポジトリへのアクセスをリクエストできます。 | +| リポジトリの削除 | アプリケーションはあなたが管理するリポジトリの削除をリクエストできますが、コードにアクセスすることはできません。 | ### 更新された権限のリクエスト 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 67d0f22555..9de5e820a3 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 @@ -14,7 +14,7 @@ versions: 個人アクセストークン（PAT）は、[GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) または[コマンドライン](#using-a-token-on-the-command-line)を使用するときに {% data variables.product.product_name %} への認証でパスワードの代わりに使用できます。 -{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. 詳しい情報については「[SAMLシングルサインオンでの認証について](/articles/about-authentication-with-saml-single-sign-on)」及び「[SAMLシングルサインオンで利用する個人アクセストークンの認可](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」を参照してください。{% endif %} +{% if currentVersion == "free-pro-team@latest" %}PAT を使用して、SAML SSO を使用する Organization が所有するリソースにアクセスする場合は、PAT を認証する必要があります。 詳しい情報については「[SAMLシングルサインオンでの認証について](/articles/about-authentication-with-saml-single-sign-on)」及び「[SAMLシングルサインオンで利用する個人アクセストークンの認可](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」を参照してください。{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %} @@ -28,7 +28,7 @@ versions: 5. トークンにわかりやすい名前を付けます。 ![トークンの説明フィールド](/assets/images/help/settings/token_description.png) 6. このトークンに付与するスコープ、すなわち権限を選択します。 トークンを使用してコマンドラインからリポジトリにアクセスするには、[**repo**] を選択します。 ![トークンスコープの選択](/assets/images/help/settings/token_scopes.gif) 7. [**Generate token**] をクリックします。 ![[Generate token] ボタン](/assets/images/help/settings/generate_token.png) -8. {% octicon "clippy" aria-label="The copy to clipboard icon" %}をクリックしてトークンをクリップボードにコピーします。 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 %} +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 %} {% 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 8ed8532f49..ff42c09898 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 @@ -9,7 +9,7 @@ versions: enterprise-server: '*' --- -{% data variables.product.product_name %}アカウントのパスワードは、以下の条件に従い選択または生成する必要があります: +{% data variables.product.product_name %} アカウントのパスワードを選択または生成する必要があります。パスワードの条件は次のとおりです。 - 数字と小文字アルファベットを含む場合は長さ 8 文字、または - 文字の組み合わせを考慮しない場合は長さ 16 文字 diff --git a/translations/ja-JP/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md b/translations/ja-JP/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md index 68d5508725..d7d5b9eaad 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md +++ b/translations/ja-JP/content/github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account.md @@ -12,7 +12,7 @@ versions: {% warning %} -**Warning:** If you're a member{% if currentVersion == "free-pro-team@latest" %}, billing manager,{% endif %} or outside collaborator to a public repository of an organization that requires two-factor authentication and you disable 2FA, you'll be automatically removed from the organization, and you'll lose your access to their repositories. Organization へのアクセスを再取得するには、2 要素認証を再有効化し、Organization オーナーに連絡します。 +**警告:** 2 要素認証を必要とする Organization のメンバー{% if currentVersion == "free-pro-team@latest" %}、支払いマネージャー{% endif %}、または Organization のパブリックリポジトリへの外部のコラボレータが 2 要素認証を無効化すると、Organization から自動的に削除され、リポジトリへのアクセスを失います。 Organization へのアクセスを再取得するには、2 要素認証を再有効化し、Organization オーナーに連絡します。 {% endwarning %} @@ -24,7 +24,7 @@ Organization から自分を削除するには: {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.security %} -3. Click **Disable**. ![[Disable two-factor authentication] ボタン](/assets/images/help/2fa/disable-two-factor-authentication.png) +3. [**Disable**] をクリックします。 ![[Disable two-factor authentication] ボタン](/assets/images/help/2fa/disable-two-factor-authentication.png) ### 参考リンク diff --git a/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-gpg-key.md b/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-gpg-key.md index edfd74bf96..3bab08d42e 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-gpg-key.md +++ b/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-gpg-key.md @@ -15,7 +15,7 @@ versions: {% note %} -**メモ:** 新しい GPG キーを生成する前にメールアドレスを検証しておいてください。 If you haven't verified your email address, you won't be able to sign commits and tags with GPG.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} +**メモ:** 新しい GPG キーを生成する前にメールアドレスを検証しておいてください。 メールアドレスを検証していないと、GPG を使用してコミットやタグに署名できません。{% if currentVersion == "free-pro-team@latest" %} 詳しい情報については、「[メールアドレスを検証する](/articles/verifying-your-email-address)」を参照してください。{% endif %} {% endnote %} @@ -38,7 +38,7 @@ versions: {% note %} - **メモ:** メールアドレスの入力を求められた場合は、GitHub アカウント用の検証済みメールアドレスを入力してください。 {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} For more information, see "[Verifying your email address](/articles/verifying-your-email-address)" and "[Setting your commit email address](/articles/setting-your-commit-email-address)."{% endif %} + **メモ:** メールアドレスの入力を求められた場合は、GitHub アカウント用の検証済みメールアドレスを入力してください。 {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} 詳しい情報については、「[メールアドレスを検証する](/articles/verifying-your-email-address)」および「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address)」を参照してください。{% endif %} {% endnote %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index cfa15cc3e1..0782e4f4d8 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/ja-JP/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -24,7 +24,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない ``` {% note %} - **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use: + **注釈:** Ed25519 アルゴリズムをサポートしないレガシーシステムを使用している場合は、以下を使用します。 ```shell $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` @@ -89,7 +89,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない $ touch ~/.ssh/config ``` - * Open your `~/.ssh/config` file, then modify the file, replacing `~/.ssh/id_ed25519` if you are not using the default location and name for your `id_ed25519` key. + * `~/.ssh/config` ファイルを開いて修正し、`id_ed25519` キーのデフォルトの場所と名前を使用していない場合は`~/.ssh/id_ed25519` を置き換えます。 ``` Host * @@ -100,7 +100,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない {% note %} - **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line. + **注釈:** キーにパスフレーズを追加しない場合は、`UseKeychain` 行を省略してください。 {% endnote %} @@ -110,7 +110,7 @@ SSH キーを使用するたびにパスフレーズを再入力したくない ``` {% note %} - **メモ: ** `-K` オプションは、`ssh-add` の Apple の標準バージョン内にあり、ssh-agent に SSH キーを追加する際にキーチェーンにパスフレーズを保存します。 If you chose not to add a passphrase to your key, run the command without the `-K` option. + **メモ: ** `-K` オプションは、`ssh-add` の Apple の標準バージョン内にあり、ssh-agent に SSH キーを追加する際にキーチェーンにパスフレーズを保存します。 キーにパスフレーズを追加しない場合は、`-K` オプションを指定せずにコマンドを実行します。 Apple の標準バージョンをインストールしていない場合は、エラーが発生する場合があります。 このエラーの解決方法についての詳細は、「[エラー: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)」を参照してください。 diff --git a/translations/ja-JP/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md b/translations/ja-JP/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md index ee37d20e2b..5586e8f893 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md +++ b/translations/ja-JP/content/github/authenticating-to-github/githubs-ssh-key-fingerprints.md @@ -9,7 +9,7 @@ versions: free-pro-team: '*' --- -These are {% data variables.product.prodname_dotcom %}'s public key fingerprints: +{% data variables.product.prodname_dotcom %} の公開鍵のフィンガープリントは次のとおりです。 - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) - `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA) diff --git a/translations/ja-JP/content/github/authenticating-to-github/index.md b/translations/ja-JP/content/github/authenticating-to-github/index.md index e509bba9b4..08631f9b2e 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/index.md +++ b/translations/ja-JP/content/github/authenticating-to-github/index.md @@ -1,7 +1,7 @@ --- title: GitHubへの認証方法 shortTitle: 認証 -intro: 'Keep your account and data secure with features like {% if currentVersion != "github-ae@latest" %}two-factor authentication, {% endif %}SSH{% if currentVersion != "github-ae@latest" %},{% endif %} and commit signature verification.' +intro: '{% if currentVersion != "github-ae@latest" %}2 要素認証、{% endif %}SSH{% if currentVersion != "github-ae@latest" %}、{% endif %}コミット署名検証などの機能を使用して、アカウントとデータを安全に保ちます。' redirect_from: - /categories/56/articles/ - /categories/ssh/ @@ -35,11 +35,9 @@ versions: {% link_in_list /reviewing-your-authorized-applications-oauth %} {% link_in_list /reviewing-your-security-log %} {% link_in_list /removing-sensitive-data-from-a-repository %} - {% link_in_list /about-anonymized-image-urls %} {% link_in_list /about-githubs-ip-addresses %} {% link_in_list /githubs-ssh-key-fingerprints %} - {% link_in_list /sudo-mode %} {% link_in_list /preventing-unauthorized-access %} {% topic_link_in_list /securing-your-account-with-two-factor-authentication-2fa %} @@ -48,18 +46,14 @@ versions: {% link_in_list /configuring-two-factor-authentication-recovery-methods %} {% link_in_list /accessing-github-using-two-factor-authentication %} {% link_in_list /recovering-your-account-if-you-lose-your-2fa-credentials %} - {% link_in_list /changing-two-factor-authentication-delivery-methods-for-your-mobile-device %} {% link_in_list /countries-where-sms-authentication-is-supported %} - {% link_in_list /disabling-two-factor-authentication-for-your-personal-account %} - {% topic_link_in_list /authenticating-with-saml-single-sign-on %} {% link_in_list /about-authentication-with-saml-single-sign-on %} {% link_in_list /authorizing-an-ssh-key-for-use-with-saml-single-sign-on %} {% link_in_list /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-your-active-saml-sessions %} - {% topic_link_in_list /connecting-to-github-with-ssh %} {% link_in_list /about-ssh %} {% link_in_list /checking-for-existing-ssh-keys %} @@ -68,13 +62,9 @@ versions: {% link_in_list /testing-your-ssh-connection %} {% link_in_list /working-with-ssh-key-passphrases %} {% topic_link_in_list /troubleshooting-ssh %} - {% link_in_list /using-ssh-over-the-https-port %} - {% link_in_list /recovering-your-ssh-key-passphrase %} - {% link_in_list /deleted-or-missing-ssh-keys %} - {% link_in_list /error-permission-denied-publickey %} {% link_in_list /error-bad-file-number %} {% link_in_list /error-key-already-in-use %} @@ -82,9 +72,7 @@ versions: {% link_in_list /error-permission-to-userrepo-denied-to-userother-repo %} {% link_in_list /error-agent-admitted-failure-to-sign %} {% link_in_list /error-ssh-add-illegal-option----k %} - {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %} - {% link_in_list /error-were-doing-an-ssh-key-audit %} {% topic_link_in_list /managing-commit-signature-verification %} {% link_in_list /about-commit-signature-verification %} diff --git a/translations/ja-JP/content/github/authenticating-to-github/managing-commit-signature-verification.md b/translations/ja-JP/content/github/authenticating-to-github/managing-commit-signature-verification.md index 8f223d08e2..b01dd4ec2e 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/managing-commit-signature-verification.md +++ b/translations/ja-JP/content/github/authenticating-to-github/managing-commit-signature-verification.md @@ -1,6 +1,6 @@ --- title: コミット署名の検証を管理する -intro: 'You can sign your work locally using GPG or S/MIME. {% data variables.product.product_name %} will verify these signatures so other people will know that your commits come from a trusted source.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} will automatically sign commits you make using the {% data variables.product.product_name %} web interface.{% endif %}' +intro: 'GPG または S/MIME を使用してローカルで作業に署名できます。 信頼できるソースによるコミットであることを他のユーザに知らせるために、{% data variables.product.product_name %} はこの署名を検証します。{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} は、{% data variables.product.product_name %} Web インターフェイスを使用して自動的にコミットに署名します。{% endif %}' redirect_from: - /articles/generating-a-gpg-key/ - /articles/signing-commits-with-gpg/ diff --git a/translations/ja-JP/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ja-JP/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md index ba4bc5ac7b..7b1362fbd6 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/ja-JP/content/github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -82,7 +82,7 @@ versions: 2. {% data variables.product.product_name %}アカウントに関連付けられているリカバリトークンをクリックします。 ![Facebook に格納されているリカバリトークンのリスト](/assets/images/help/settings/security-github-rae-token-on-facebook.png) 3. アカウントリカバリトークンを引き換えるため、[**Recover This Account**] をクリックします。 新しいウィンドウが開き、{% data variables.product.product_name %}に戻ります。 ![リカバリトークンについての情報を表示するモーダルボックスおよび [Recover This Account] ボタン](/assets/images/help/settings/security-recover-account-facebook.png) 4. お問い合わせ -{% data variables.contact.contact_support %} to let them know that your account recovery token is ready for review. +{% data variables.contact.contact_support %} に連絡して、アカウントリカバリトークンはレビューの準備ができていることを知らせます。 {% endif %} ### 参考リンク diff --git a/translations/ja-JP/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/ja-JP/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index 1eff9cc64e..7305dbe8d3 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/ja-JP/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -40,6 +40,12 @@ $ bfg --delete-files 機密データを含むファイル $ bfg --replace-text passwords.txt ``` +機密データが削除されたら、変更を {% data variables.product.product_name %} に強制的にプッシュする必要があります。 + +```shell +$ git push --force +``` + 完全な使用方法とダウンロード手順については、[BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) のドキュメントを参照してください。 #### filter-branch を使用する @@ -146,5 +152,5 @@ $ bfg --replace-text passwords.txt ### 参考リンク -- [`git filter-branch` man page](https://git-scm.com/docs/git-filter-branch) +- [`git filter-branch` メインページ](https://git-scm.com/docs/git-filter-branch) - [Pro Git：Git ツール - 履歴の書き換え](https://git-scm.com/book/en/Git-Tools-Rewriting-History) 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 cc63b95edb..2e084d0369 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 @@ -12,7 +12,7 @@ versions: ### セキュリティログにアクセスする -The security log lists all actions performed within the last 90 days{% if currentVersion ver_lt "enterprise-server@2.20" %}, up to 50{% endif %}. +セキュリティログには、過去 90 日間に実行されたすべてのアクションが{% if currentVersion ver_lt "enterprise-server@2.20" %}最大 50 件まで{% endif %}リストされます。 {% data reusables.user_settings.access_settings %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -33,24 +33,24 @@ The security log lists all actions performed within the last 90 days{% if curren ### セキュリティログでのイベントを理解する {% endif %} -The events listed in your security log are triggered by your actions. Actions are grouped into the following categories: +セキュリティログにリストされているイベントは、アクションによってトリガーされます。 アクションは次のカテゴリに分類されます。 -| カテゴリ名 | 説明 | -| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} -| [`account_recovery_token`](#account_recovery_token-category-actions) | | カテゴリ名 | 説明 [リカバリトークンの追加](/articles/configuring-two-factor-authentication-recovery-methods)に関連するすべての活動が対象です。 | -| [`支払い`](#billing-category-actions) | 自分の支払い情報に関連するすべての活動が対象です。 | -| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。 | +| カテゴリ名 | 説明 | +| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} +| [`account_recovery_token`](#account_recovery_token-category-actions) | | カテゴリ名 | 説明 [リカバリトークンの追加](/articles/configuring-two-factor-authentication-recovery-methods)に関連するすべての活動が対象です。 | +| [`支払い`](#billing-category-actions) | 自分の支払い情報に関連するすべての活動が対象です。 | +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。 | | [`marketplace_listing`](#marketplace_listing-category-actions) | {% data variables.product.prodname_marketplace %} に一覧表示しているアプリに関連するすべての活動が対象です。{% endif %} -| [`oauth_access`](#oauth_access-category-actions) | 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" %} +| [`oauth_access`](#oauth_access-category-actions) | 接続している [{% data variables.product.prodname_oauth_app %}](/articles/authorizing-oauth-apps) に関連するすべてのアクティビティが対象です。{% if currentVersion == "free-pro-team@latest" %} | [`payment_method`](#payment_method-category-actions) | {% data variables.product.prodname_dotcom %} プランに対する支払いに関連するすべての活動が対象です。{% endif %} -| [`profile_picture`](#profile_picture-category-actions) | 自分のプロファイル写真に関連するすべての活動が対象です。 | -| [`project`](#project-category-actions) | プロジェクト ボードに関連するすべての活動が対象です。 | -| [`public_key`](#public_key-category-actions) | [公開 SSH キー](/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-category-actions) | アカウントに関連するすべての活動が対象です。 | +| [`profile_picture`](#profile_picture-category-actions) | 自分のプロファイル写真に関連するすべての活動が対象です。 | +| [`project`](#project-category-actions) | プロジェクト ボードに関連するすべての活動が対象です。 | +| [`public_key`](#public_key-category-actions) | [公開 SSH キー](/articles/adding-a-new-ssh-key-to-your-github-account)に関連するすべての活動が対象です。 | +| [`repo`](#repo-category-actions) | 所有するリポジトリに関連するすべてのアクティビティが対象です。{% if currentVersion == "free-pro-team@latest" %} +| [`sponsors`](#sponsors-category-actions) | {% data variables.product.prodname_sponsors %} およびスポンサーボタンに関連するすべてのイベントが対象です (「[{% data variables.product.prodname_sponsors %} について](/articles/about-github-sponsors)」と「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| [`Team`](#team-category-actions) | 所属する Team に関連するすべてのアクティビティが対象です。{% endif %}{% if currentVersion != "github-ae@latest" %} +| [`two_factor_authentication`](#two_factor_authentication-category-actions) | [2 要素認証](/articles/securing-your-account-with-two-factor-authentication-2fa)に関連するすべてのアクティビティが対象です。{% endif %} +| [`ユーザ`](#user-category-actions) | アカウントに関連するすべての活動が対象です。 | {% if currentVersion == "free-pro-team@latest" %} @@ -61,13 +61,13 @@ The events listed in your security log are triggered by your actions. Actions ar {% endif %} -### Security log actions +### セキュリティログのアクション -An overview of some of the most common actions that are recorded as events in the security log. +セキュリティログにイベントとして記録される最も一般的なアクションの概要です。 {% if currentVersion == "free-pro-team@latest" %} -#### `account_recovery_token` category actions +#### `account_recovery_token` カテゴリアクション | アクション | 説明 | | --------------- | ----------------------------------------------------------------------------------------------------------- | @@ -75,20 +75,20 @@ An overview of some of the most common actions that are recorded as events in th | `recover` | 正常に[アカウント リカバリ トークンを引き換える](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)ときにトリガーされます。 | | `recover_error` | トークンが使用されているにもかかわらず {% data variables.product.prodname_dotcom %} がそれを有効にできないときにトリガーされます。 | -#### `billing` category actions +#### `billing` カテゴリアクション | アクション | 説明 | | --------------------- | -------------------------------------------------------------------------------------------------------------------- | | `change_billing_type` | {% data variables.product.prodname_dotcom %} の[支払い方法を変更する](/articles/adding-or-editing-a-payment-method)ときにトリガーされます。 | | `change_email` | [自分のメール アドレスを変更する](/articles/changing-your-primary-email-address)ときにトリガーされます。 | -#### `marketplace_agreement_signature` category actions +#### `marketplace_agreement_signature` カテゴリアクション | アクション | 説明 | | -------- | --------------------------------------------------------------------------------------- | | `create` | {% data variables.product.prodname_marketplace %} Developer Agreement に署名するときにトリガーされます。 | -#### `marketplace_listing` category actions +#### `marketplace_listing` カテゴリアクション | アクション | 説明 | | --------- | ----------------------------------------------------------------------------------- | @@ -100,7 +100,7 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} -#### `oauth_access` category actions +#### `oauth_access` カテゴリアクション | アクション | 説明 | | --------- | ---------------------------------------------------------------------------------------------------------------------------------------- | @@ -109,7 +109,7 @@ An overview of some of the most common actions that are recorded as events in th {% if currentVersion == "free-pro-team@latest" %} -#### `payment_method` category actions +#### `payment_method` カテゴリアクション | アクション | 説明 | | -------- | -------------------------------------------------------------------- | @@ -119,64 +119,64 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} -#### `profile_picture` category actions +#### `profile_picture` カテゴリアクション | アクション | 説明 | | -------- | ---------------------------------------------------------------------------- | | `update` | [自分のプロフィール写真を設定または更新する](/articles/setting-your-profile-picture/)ときにトリガーされます。 | -#### `project` category actions +#### `project` カテゴリアクション -| アクション | 説明 | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------- | -| `access` | プロジェクト ボードの可視性が変更されるときにトリガーされます。 | -| `create` | プロジェクト ボードが作成されるときにトリガーされます。 | -| `rename` | プロジェクトボードの名前が変更されるときにトリガーされます。 | -| `update` | プロジェクト ボードが更新されるときにトリガーされます。 | -| `delete` | プロジェクトボードが削除されるときにトリガーされます。 | -| `link` | リポジトリがプロジェクト ボードにリンクされるときにトリガーされます。 | -| `unlink` | リポジトリがプロジェクトボードからリンク解除されるときにトリガーされます。 | -| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed. | +| アクション | 説明 | +| ------------------------ | ----------------------------------------------------------------------- | +| `access` | プロジェクト ボードの可視性が変更されるときにトリガーされます。 | +| `create` | プロジェクト ボードが作成されるときにトリガーされます。 | +| `rename` | プロジェクトボードの名前が変更されるときにトリガーされます。 | +| `update` | プロジェクト ボードが更新されるときにトリガーされます。 | +| `delete` | プロジェクトボードが削除されるときにトリガーされます。 | +| `link` | リポジトリがプロジェクト ボードにリンクされるときにトリガーされます。 | +| `unlink` | リポジトリがプロジェクトボードからリンク解除されるときにトリガーされます。 | +| `update_user_permission` | 外部のコラボレータがプロジェクトボードに追加またはプロジェクトボードから削除されたとき、あるいは許可レベルが変更されたときにトリガーされます。 | -#### `public_key` category actions +#### `public_key` カテゴリアクション | アクション | 説明 | | -------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | `create` | [新たな公開 SSH キーを自分の {% data variables.product.product_name %} アカウントに追加する](/articles/adding-a-new-ssh-key-to-your-github-account)ときにトリガーされます。 | | `delete` | [公開 SSH キーを自分の {% data variables.product.product_name %} アカウントから削除する](/articles/reviewing-your-ssh-keys)ときにトリガーされます。 | -#### `repo` category actions +#### `repo` カテゴリアクション -| アクション | 説明 | -| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `access` | 自分が所有するリポジトリが["プライベート" から "パブリック" に切り替えられる](/articles/making-a-private-repository-public) (またはその逆) ときにトリガーされます。 | -| `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` | リポジトリのオーナーがリポジトリに[トピックを追加する](/articles/classifying-your-repository-with-topics)ときにトリガーされます。 | +| アクション | 説明 | +| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access` | 自分が所有するリポジトリが["プライベート" から "パブリック" に切り替えられる](/articles/making-a-private-repository-public) (またはその逆) ときにトリガーされます。 | +| `add_member` | {% data variables.product.product_name %} ユーザがリポジトリへの{% if currentVersion == "free-pro-team@latest" %}[共同アクセス権を保有するように招待される](/articles/inviting-collaborators-to-a-personal-repository){% else %}[共同アクセス権を付与される](/articles/inviting-collaborators-to-a-personal-repository){% endif %}ときにトリガーされます。 | +| `add_topic` | リポジトリのオーナーがリポジトリに[トピックを追加する](/articles/classifying-your-repository-with-topics)ときにトリガーされます。 | | `archived` | リポジトリのオーナーが[リポジトリをアーカイブする](/articles/about-archiving-repositories)ときにトリガーされます。{% if enterpriseServerVersions contains currentVersion %} -| `config.disable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが無効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。 | -| `config.enable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが有効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。 | -| `config.lock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロックされる](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。 | +| `config.disable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが無効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。 | +| `config.enable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが有効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。 | +| `config.lock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロックされる](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。 | | `config.unlock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロック解除される](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。{% endif %} -| `create` | [新たなリポジトリが作成される](/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" %} +| `create` | [新たなリポジトリが作成される](/articles/creating-a-new-repository)ときにトリガーされます。 | +| `destroy` | [リポジトリが削除される](/articles/deleting-a-repository)ときにトリガーされます。{% if currentVersion == "free-pro-team@latest" %} +| `disable` | リポジトリが無効になるときにトリガーされます ([残高不足](/articles/unlocking-a-locked-account)などの場合)。{% endif %}{% if currentVersion == "free-pro-team@latest" %} | `enable` | リポジトリが再び有効になるときにトリガーされます。{% endif %} -| `remove_member` | {% data variables.product.product_name %}ユーザが[リポジトリのコラボレーターではなくなる](/articles/removing-a-collaborator-from-a-personal-repository)ときにトリガーされます。 | -| `remove_topic` | リポジトリのオーナーがリポジトリからトピックを削除するときにトリガーされます。 | -| `rename` | [リポジトリの名前が変更される](/articles/renaming-a-repository)ときにトリガーされます。 | -| `移譲` | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。 | -| `transfer_start` | リポジトリの移譲が行われようとしているときにトリガーされます。 | -| `unarchived` | リポジトリのオーナーがリポジトリをアーカイブ解除するときにトリガーされます。 | +| `remove_member` | {% data variables.product.product_name %}ユーザが[リポジトリのコラボレーターではなくなる](/articles/removing-a-collaborator-from-a-personal-repository)ときにトリガーされます。 | +| `remove_topic` | リポジトリのオーナーがリポジトリからトピックを削除するときにトリガーされます。 | +| `rename` | [リポジトリの名前が変更される](/articles/renaming-a-repository)ときにトリガーされます。 | +| `移譲` | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。 | +| `transfer_start` | リポジトリの移譲が行われようとしているときにトリガーされます。 | +| `unarchived` | リポジトリのオーナーがリポジトリをアーカイブ解除するときにトリガーされます。 | {% if currentVersion == "free-pro-team@latest" %} -#### `sponsors` category actions +#### `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#sponsoring-a-developer)」を参照) | +| `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` | スポンサード開発者からメールで最新情報を受け取るかどうかを変更したときにトリガーされます (「[スポンサーシップを管理する](/articles/managing-your-sponsorship)」を参照) | | `sponsor_sponsorship_tier_change` | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照) | | `sponsored_developer_approve` | {% data variables.product.prodname_sponsors %}アカウントが承認されるとトリガーされます（「[ユーザアカウントに{% data variables.product.prodname_sponsors %}を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照） | @@ -190,7 +190,7 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} {% if currentVersion == "free-pro-team@latest" %} -#### `successor_invitation` category actions +#### `successor_invitation` カテゴリアクション | アクション | 説明 | | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -203,7 +203,7 @@ An overview of some of the most common actions that are recorded as events in th {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -#### `team` category actions +#### `team` カテゴリアクション | アクション | 説明 | | ------------------- | ------------------------------------------------------------------------------------------------------------- | @@ -217,7 +217,7 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} {% if currentVersion != "github-ae@latest" %} -#### `two_factor_authentication` category actions +#### `two_factor_authentication` カテゴリアクション | アクション | 説明 | | ---------- | ---------------------------------------------------------------------------------------------- | @@ -225,24 +225,24 @@ An overview of some of the most common actions that are recorded as events in th | `disabled` | 2 要素認証が無効になるときにトリガーされます。 | {% endif %} -#### `user` category actions +#### `user` カテゴリアクション -| アクション | 説明 | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_email` | Triggered when you {% if currentVersion != "github-ae@latest" %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}. | -| `create` | Triggered when you create a new user account.{% if currentVersion != "github-ae@latest" %} -| `change_password` | 自分のパスワードを変更するときにトリガーされます。 | -| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %} -| `hide_private_contributions_count` | [自分のプロファイルでプライベート コントリビューションを非表示にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)ときにトリガーされます。 | -| `login` | {% data variables.product.product_location %} にログインするときにトリガーされます | -| `failed_login` | 正常にログインできなかったときにトリガーされます | -| `remove_email` | メール アドレスを削除するときにトリガーされます。 | -| `rename` | Triggered when you rename your account.{% if currentVersion == "free-pro-team@latest" %} +| アクション | 説明 | +| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_email` | {% if currentVersion != "github-ae@latest" %}[新しいメールアドレスを追加する](/articles/changing-your-primary-email-address){% else %}新しいメールアドレスを追加する{% endif %}とトリガーされます。 | +| `create` | 新しいユーザアカウントを作成するとトリガーされます。{% if currentVersion != "github-ae@latest" %} +| `change_password` | 自分のパスワードを変更するときにトリガーされます。 | +| `forgot_password` | [パスワード のリセット](/articles/how-can-i-reset-my-password)を要求したときにトリガーされます。{% endif %} +| `hide_private_contributions_count` | [自分のプロファイルでプライベート コントリビューションを非表示にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)ときにトリガーされます。 | +| `login` | {% data variables.product.product_location %} にログインするときにトリガーされます | +| `failed_login` | 正常にログインできなかったときにトリガーされます | +| `remove_email` | メール アドレスを削除するときにトリガーされます。 | +| `rename` | アカウントの名前を変更するとトリガーされます。{% if currentVersion == "free-pro-team@latest" %} | `report_content` | [Issue または Pull Request、あるいは Issue、Pull Request、または Commit でのコメントを報告する](/articles/reporting-abuse-or-spam)ときにトリガーされます。{% endif %} -| `show_private_contributions_count` | 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 %} +| `show_private_contributions_count` | [自分のプロファイルでプライベート コントリビューションをパブリックにする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)ときにトリガーされます。{% if currentVersion != "github-ae@latest" %} +| `two_factor_requested` | {% data variables.product.product_name %} が[自分の 2 要素認証コード](/articles/accessing-github-using-two-factor-authentication)を要求するときにトリガーされます。{% endif %} -#### `user_status` category actions +#### `user_status` カテゴリアクション | アクション | 説明 | | --------- | ------------------------------------------------------------------------------------------------------------------------- | diff --git a/translations/ja-JP/content/github/authenticating-to-github/signing-commits.md b/translations/ja-JP/content/github/authenticating-to-github/signing-commits.md index 48db9d607c..d2a1f20e01 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/signing-commits.md +++ b/translations/ja-JP/content/github/authenticating-to-github/signing-commits.md @@ -1,6 +1,6 @@ --- title: コミットに署名する -intro: You can sign commits locally using GPG or S/MIME. +intro: GPG または S/MIME を使用してローカルでコミットに署名できます。 redirect_from: - /articles/signing-commits-and-tags-using-gpg/ - /articles/signing-commits-using-gpg/ @@ -41,7 +41,7 @@ Git バージョン 2.0.0 以降で、ローカルリポジトリでデフォル # ローカルコミットをリモートリポジトリにプッシュする ``` 4. On -{% data variables.product.product_name %}, navigate to your pull request. +{% data variables.product.product_name %} 上で、プルリクエストに移動します。 {% data reusables.repositories.review-pr-commits %} 5. ベリファイされた署名の詳しい情報を見るには、Verifiedをクリックします。 ![署名されたコミット](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) diff --git a/translations/ja-JP/content/github/authenticating-to-github/signing-tags.md b/translations/ja-JP/content/github/authenticating-to-github/signing-tags.md index f7d52aeeb5..80c0cd9513 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/signing-tags.md +++ b/translations/ja-JP/content/github/authenticating-to-github/signing-tags.md @@ -1,6 +1,6 @@ --- title: タグに署名する -intro: You can sign tags locally using GPG or S/MIME. +intro: GPG または S/MIME を使用してローカルでタグに署名できます。 redirect_from: - /articles/signing-tags-using-gpg/ - /articles/signing-tags diff --git a/translations/ja-JP/content/github/authenticating-to-github/telling-git-about-your-signing-key.md b/translations/ja-JP/content/github/authenticating-to-github/telling-git-about-your-signing-key.md index ffb451bf1b..75a42f5319 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/telling-git-about-your-signing-key.md +++ b/translations/ja-JP/content/github/authenticating-to-github/telling-git-about-your-signing-key.md @@ -1,6 +1,6 @@ --- title: Git へ署名キーを伝える -intro: "To sign commits locally, you need to inform Git that there's a GPG or X.509 key you'd like to use." +intro: "ローカルでコミットに署名するには、使用する GPG または X.509 キーがあることを Git に知らせる必要があります。" redirect_from: - /articles/telling-git-about-your-gpg-key/ - /articles/telling-git-about-your-signing-key diff --git a/translations/ja-JP/content/github/authenticating-to-github/updating-your-github-access-credentials.md b/translations/ja-JP/content/github/authenticating-to-github/updating-your-github-access-credentials.md index c8dcdb45a8..2dd7a94eda 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/updating-your-github-access-credentials.md +++ b/translations/ja-JP/content/github/authenticating-to-github/updating-your-github-access-credentials.md @@ -1,6 +1,6 @@ --- title: GitHub アクセス認証情報を更新する -intro: '{% data variables.product.product_name %} credentials include{% if currentVersion != "github-ae@latest" %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. 必要があれば、すべてのアクセス認証情報をリセットできます。' +intro: '{% data variables.product.product_name %} 認証情報は、{% if currentVersion != "github-ae@latest" %}パスワードだけではなく、{% endif %}{% data variables.product.product_name %} に伝達するのに使うアクセストークン、SSH キーおよびアプリケーション API トークンを含みます。 必要があれば、すべてのアクセス認証情報をリセットできます。' redirect_from: - /articles/rolling-your-credentials/ - /articles/how-can-i-reset-my-password/ @@ -14,7 +14,7 @@ versions: {% if currentVersion != "github-ae@latest" %} ### 新しいパスワードをリクエストする -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 %}. +1. 新しいパスワードをリクエストするには、{% 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. 個人 {% data variables.product.product_name %} アカウントに関連するメールアドレスを入力し、次に [**Send password reset email**] をクリックします。バックアップメールアドレスが設定されている場合、そのアドレスにメールが送られます。 ![パスワードリセットのメールリクエストダイアログ](/assets/images/help/settings/password-recovery-email-request.png) 3. パスワードをリセットするためのリンクがメールで届きます。 メールを受信してから 3 時間以内に、このリンクをクリックする必要があります。 弊社からメールが届かない場合、スパムフォルダを確認してください。 4. メールのリンクをクリックすると、新しいパスワードを入力するように求められます。 ![パスワードリカバリボックス](/assets/images/help/settings/password_recovery_page.png) diff --git a/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md b/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md index 7565e76b27..f5c583b985 100644 --- a/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md +++ b/translations/ja-JP/content/github/authenticating-to-github/working-with-ssh-key-passphrases.md @@ -58,7 +58,7 @@ elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then fi ``` -If your private key is not stored in one of the default locations (like `~/.ssh/id_rsa`), you'll need to tell your SSH authentication agent where to find it. キーを ssh-agent に追加するには、`ssh-add ~/path/to/my_key` と入力します。 詳細は「[新しい SSH キーを生成して ssh-agent に追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)」を参照してください。 +秘密鍵がデフォルトの場所 (`~/.ssh/id_rsa` など) に保存されていない場合は、SSH 認証エージェントにその場所を指定する必要があります。 キーを ssh-agent に追加するには、`ssh-add ~/path/to/my_key` と入力します。 詳細は「[新しい SSH キーを生成して ssh-agent に追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)」を参照してください。 {% tip %} diff --git a/translations/ja-JP/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md b/translations/ja-JP/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md index 565f26877a..acad17a3d6 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md +++ b/translations/ja-JP/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md @@ -13,7 +13,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -You can create default issue and pull request templates for your organization or user account. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/github/building-a-strong-community/creating-a-default-community-health-file)」を参照してください。 +Organization またはユーザアカウントのデフォルトの Issue とプルリクエストテンプレートを作成できます。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/github/building-a-strong-community/creating-a-default-community-health-file)」を参照してください。 {% endif %} @@ -26,7 +26,7 @@ Issueテンプレートビルダーを使ってリポジトリにIssueのテン テンプレートビルダーを使うと、各テンプレートに対してタイトルと説明を指定し、テンプレートの内容を追加し、リポジトリ中でそのテンプレートをデフォルトブランチにコミットするか、プルリクエストをオープンできます。 テンプレートビルダーは、新しい Issue ページにテンプレートを表示するのに必要となる YAML front matter マークアップを自動的に追加してくれます。 詳しい情報については、「[リポジトリ用に Issue テンプレートを設定する](/articles/configuring-issue-templates-for-your-repository)」を参照してください。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% data reusables.repositories.issue-template-config %} For more information, see "[Configuring issue templates for your repository](/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)." +{% data reusables.repositories.issue-template-config %}詳しい情報については、「[リポジトリ用に Issue テンプレートを設定する](/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)」を参照してください。 {% endif %} Issue テンプレートは、リポジトリのデフォルトブランチ中の隠しディレクトリ `.github/ISSUE_TEMPLATE` に保存されます。 テンプレートを他のブランチで作成した場合、それをコラボレーターが使うことはできません。 Issue テンプレートのファイル名では大文字と小文字は区別されません。拡張子は *.md* でなければなりません。 {% data reusables.repositories.valid-community-issues %} diff --git a/translations/ja-JP/content/github/building-a-strong-community/about-team-discussions.md b/translations/ja-JP/content/github/building-a-strong-community/about-team-discussions.md index 91f1fdb0b6..6bf572b9e9 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/about-team-discussions.md +++ b/translations/ja-JP/content/github/building-a-strong-community/about-team-discussions.md @@ -1,6 +1,6 @@ --- -title: Team ディスカッションについて -intro: 'Team は、Organization 内の Team のページ内のディスカッションポストにおける好きな話題について、計画をしたり、更新をしたり、議論をしたりできます。' +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 versions: @@ -11,35 +11,35 @@ versions: {% data reusables.organizations.team-discussions-purpose %} -Organization のメンバーは、誰でも Team のページにポストしたり、パブリックなディスカッションに参加したりできます。 {% data reusables.organizations.team-discussions-permissions %} +Any organization member can post on your team's page or participate in a public discussion. {% data reusables.organizations.team-discussions-permissions %} -![パブリックおよびプライベートのディスカッションを持つ Team ページのディスカッションタブ](/assets/images/help/organizations/team-page-discussions-tab.png) +![Discussions tab of team page with public and private discussions](/assets/images/help/organizations/team-page-discussions-tab.png) -Team のディスカッションにリンクを張って、別のところから参照できます。 重要なポストは Team のページにピン止めして、後で簡単に参照できます。 詳しい情報については[Team のディスカッションのピン止め](/articles/pinning-a-team-discussion)を参照してください。 +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](/articles/pinning-a-team-discussion)." -![ピン止めされたディスカッションを持つ、Team ページの [Pinned] ディスカッションタブ](/assets/images/help/organizations/team-discussions-pinned.png) +![Pinned discussions tab of team page with pinned discussion](/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)を参照してください。 +{% 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)." -### Team ディスカッションの通知 +### Notifications for team discussions -Team のページのパブリックなディスカッションに誰かがポストしたり返信したりしたとき、その Team のメンバーや子チームのメンバーは、メールあるいは Web 通知を受け取ります。 誰かが Team のページ上のプライベートなディスカッションにポストあるいは返信した場合は、その Team のメンバーだけが通知を受け取ります。 +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 %} -**ヒント:** 通知の設定によって、更新はメール、{% data variables.product.product_name %}上の Web 通知、あるいはその両方で受け取ることになります。 For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." +**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 %} -デフォルトでは、ユーザ名が Team のディスカッション内でメンションされると、ユーザ名をメンションしたポストと、そのポストに対する返信についての通知を受けることになります。 また、デフォルトでは、ポストに返信した場合、そのポストに対する他の返信についても通知を受け取ることになります。 +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. -Team のディスカッションに対する通知をオフにするには、特定のディスカッションのポストのサブスクライブを解除するか、Watch の解除あるいは特定の Team のディスカッションを完全に無視するよう通知設定を変更できます。 Team のディスカッションの Watch を解除している場合でも、特定のディスカッションのポストについての通知をサブスクライブすることはできます。 +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)." -### 参考リンク +### Further reading -- [{% data variables.product.prodname_dotcom %}での会話について](/articles/about-conversations-on-github) -- [Team について](/articles/about-teams) -- [Team ディスカッションの作成](/articles/creating-a-team-discussion) -- [Team ディスカッションの編集または削除](/articles/editing-or-deleting-a-team-discussion) +- "[About conversations on {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)" +- "[About teams](/articles/about-teams)" +- "[Creating a team discussion](/articles/creating-a-team-discussion)" +- "[Editing or deleting a team discussion](/articles/editing-or-deleting-a-team-discussion)" diff --git a/translations/ja-JP/content/github/building-a-strong-community/about-wikis.md b/translations/ja-JP/content/github/building-a-strong-community/about-wikis.md index 37d1af9743..a7b8c927dc 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/about-wikis.md +++ b/translations/ja-JP/content/github/building-a-strong-community/about-wikis.md @@ -15,9 +15,9 @@ versions: ウィキでは、{% data variables.product.product_name %} のあらゆる他の場所と同じようにコンテンツを書くことができます。 詳細は「[{% data variables.product.prodname_dotcom %} で書き、フォーマットしてみる](/articles/getting-started-with-writing-and-formatting-on-github)」を参照してください。 私たちは、さまざまなフォーマットを HTML に変更するのに[私たちのオープンソースマークアップライブラリ](https://github.com/github/markup)を使っているので、Markdown あるいはその他任意のサポートされているフォーマットで書くことができます。 -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}If you create a wiki in a public repository, the wiki is available to {% if enterpriseServerVersions contains currentVersion %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in an internal or private repository, {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}people{% elsif currentVersion == "github-ae@latest" %}enterprise members{% endif %} with access to the repository can also access the wiki. 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}パブリックリポジトリにenterprise を作成すると、{% if enterpriseServerVersions contains currentVersion %}{% data variables.product.product_location %} にアクセスできるユーザ{% else %}なら誰でもそのenterprise を利用できます{% endif %}。 {% endif %}内部またはプライベートリポジトリにenterprise を作成すると、リポジトリにアクセスできる{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}ユーザ{% elsif currentVersion == "github-ae@latest" %}Enterprise メンバー{% endif %}もenterprise にアクセスできます。 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。 -ウィキは、{% data variables.product.product_name %} 上で直接編集することも、ウィキのファイルをローカルで編集することもできます。 By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.product.product_location %} to contribute to a wiki in {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} repository. 詳細は「[ウィキへのアクセス権限を変更する](/articles/changing-access-permissions-for-wikis)」を参照してください。 +ウィキは、{% data variables.product.product_name %} 上で直接編集することも、ウィキのファイルをローカルで編集することもできます。 デフォルトでは、リポジトリへの書き込みアクセス権を持つユーザのみがウィキに変更を加えることができますが、{% data variables.product.product_location %} の全員が{% if currentVersion == "github-ae@latest" %}内部{% else %}パブリック{% endif %}リポジトリのウィキに貢献できるようにすることができます。 詳細は「[ウィキへのアクセス権限を変更する](/articles/changing-access-permissions-for-wikis)」を参照してください。 ### 参考リンク diff --git a/translations/ja-JP/content/github/building-a-strong-community/adding-a-license-to-a-repository.md b/translations/ja-JP/content/github/building-a-strong-community/adding-a-license-to-a-repository.md index 2e4912a9a3..7d62549979 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/adding-a-license-to-a-repository.md +++ b/translations/ja-JP/content/github/building-a-strong-community/adding-a-license-to-a-repository.md @@ -40,7 +40,7 @@ versions: 4. [**Edit new file**] タブで、使用したいライセンスの全文を貼り付けます。 {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} -7. コミットメッセージフィールドの下で、コミットを追加を現在のブランチか新しいブランチから選択してください。 If your current branch is `main`, you should choose to create a new branch for your commit and then create a pull request. For more information, see "[Creating a pull request](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request)". ![コミットブランチのオプション](/assets/images/help/repository/choose-commit-branch.png) +7. コミットメッセージフィールドの下で、コミットを追加を現在のブランチか新しいブランチから選択してください。 現在のブランチが `main` の場合、コミット先として新しいブランチを作成してからプルリクエストを作成する必要があります。 詳しい情報については、「[プルリクエストを作成する](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request)」を参照してください。 ![コミットブランチのオプション](/assets/images/help/repository/choose-commit-branch.png) 8. [**Commit new file**] をクリックします。 ![ブランチへのライセンスのコミット](/assets/images/help/repository/license-submit-tool.png) {% endif %} diff --git a/translations/ja-JP/content/github/building-a-strong-community/adding-or-editing-wiki-pages.md b/translations/ja-JP/content/github/building-a-strong-community/adding-or-editing-wiki-pages.md index 025d60e33b..b46748c9ed 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/adding-or-editing-wiki-pages.md +++ b/translations/ja-JP/content/github/building-a-strong-community/adding-or-editing-wiki-pages.md @@ -46,7 +46,7 @@ $ git clone https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.w # ローカルに wiki をクローン ``` -wiki をクローンした後は、新しいファイルの追加、既存のファイルの編集、変更のコミットができます。 You and your collaborators can create branches when working on wikis, but only changes pushed to the default branch will be made live and available to your readers. +wiki をクローンした後は、新しいファイルの追加、既存のファイルの編集、変更のコミットができます。 あなたとコラボレータは、Wiki で作業するときにブランチを作成できますが、デフォルトブランチにプッシュされた変更のみがライブになり、読者が利用できるようになります。 ### ウィキのファイル名について diff --git a/translations/ja-JP/content/github/building-a-strong-community/adding-support-resources-to-your-project.md b/translations/ja-JP/content/github/building-a-strong-community/adding-support-resources-to-your-project.md index 6aa851d6d6..74fe53b70d 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/adding-support-resources-to-your-project.md +++ b/translations/ja-JP/content/github/building-a-strong-community/adding-support-resources-to-your-project.md @@ -15,7 +15,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -You can create default support resources for your organization or user account. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/github/building-a-strong-community/creating-a-default-community-health-file)」を参照してください。 +Organization またはユーザアカウントのデフォルトのサポートリソースを作成できます。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/github/building-a-strong-community/creating-a-default-community-health-file)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 191dcbaa30..2fe42c6a28 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/translations/ja-JP/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -20,7 +20,7 @@ versions: ユーザをブロックすると、以下のようになります: - そのユーザによるあなたのフォローは止まります - ユーザがリポジトリの Watch を停止し、リポジトリのピン留めを解除します -- The user is not able to join any organizations you are an owner of +- ユーザはあなたがオーナーの Organization に参加できません - そのユーザによる Star 付けや Issue 割り当てはリポジトリから削除されます。 - リポジトリのユーザのフォークが削除されます - ユーザのリポジトリのフォークを削除します @@ -39,7 +39,7 @@ versions: - あなたのフォロー、あるいはあなたのコンテンツを自身のアクティビティフィードで見ること - Issue またはプルリクエストへの割り当て - あなたを自身のリポジトリにコラボレーターとして招待すること -- Invite you as a collaborator on a security advisory +- あなたをセキュリティアドバイザリのコラボレータとして招待すること - あなたのリポジトリをコメント中でクロス参照すること - リポジトリのフォーク、Watch、ピン留め、Star 付け - あなたをスポンサーすること diff --git a/translations/ja-JP/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md b/translations/ja-JP/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md index a6039533d0..a646f69ad9 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md +++ b/translations/ja-JP/content/github/building-a-strong-community/configuring-issue-templates-for-your-repository.md @@ -31,7 +31,7 @@ versions: 7. デフォルトの Issue タイトルを自動的に設定するには、リポジトリへの読み取りアクセスを持つ人に Issue を割り当てるか、ラベルを Issue テンプレートに適用し、こうした詳細な情報を [Optional additional information] の下に入力します。 このような詳細情報を Issue テンプレートに、`title`、`labels`、または `assignees` を YAML frontmatter フォーマットで使用して、追加することもできます。 ![Issue テンプレートの追加情報](/assets/images/help/repository/additional-issue-template-info.png) 8. テンプレートの編集とプレビューが終了したら、ページ右上隅にある [**Propose changes**] をクリックします。 ![[Propose changes] ボタン](/assets/images/help/repository/propose-changes-button.png) 9. 変更内容を説明するコミットメッセージを入力します。 ![Issue テンプレートコミットメッセージフィールド](/assets/images/help/repository/issue-template-commit-message-field.png) -10. コミットメッセージフィールドの下で、テンプレートを直接デフォルトブランチにコミットするか、新しいブランチを作成してプルリクエストを開くか判断します。 プルリクエストに関する詳しい情報については「[プルリクエストについて](/articles/about-pull-requests)」を参照してください。 ![Issue template commit to main or open pull request choice](/assets/images/help/repository/issue-template-commit-to-master-or-open-pull-request.png) +10. コミットメッセージフィールドの下で、テンプレートを直接デフォルトブランチにコミットするか、新しいブランチを作成してプルリクエストを開くか判断します。 プルリクエストに関する詳しい情報については「[プルリクエストについて](/articles/about-pull-requests)」を参照してください。 ![Issue テンプレートの main へのコミットかプルリクエストを開くかの選択](/assets/images/help/repository/issue-template-commit-to-master-or-open-pull-request.png) 11. **[Commit changes]** をクリックしてください。 変更がデフォルトブランチにマージされると、コントリビューターがリポジトリで新しい Issue を開くときにテンプレートを使用できるようになります。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} diff --git a/translations/ja-JP/content/github/building-a-strong-community/creating-a-default-community-health-file.md b/translations/ja-JP/content/github/building-a-strong-community/creating-a-default-community-health-file.md index 6f77705ea3..c4157ac34c 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/creating-a-default-community-health-file.md +++ b/translations/ja-JP/content/github/building-a-strong-community/creating-a-default-community-health-file.md @@ -1,6 +1,6 @@ --- -title: デフォルトのコミュニティ健全性ファイルを作成する -intro: 'CONTRIBUTING や CODE_OF_CONDUCT など、デフォルトのコミュニティ健全性ファイルを作成できます。 デフォルトのファイルは、そのような独自ファイルを持たないあらゆるパブリックリポジトリに使用されます。' +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.' 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,40 +9,43 @@ versions: enterprise-server: '*' --- -### デフォルトのコミュニティ健全性ファイルについて +### 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 %}. -{% data variables.product.product_name %}は、次のいずれかの場所にそのタイプの独自のファイルがないアカウントのパブリックリポジトリについては、デフォルトファイルを使用および表示します。 -- リポジトリのルート -- `.github` フォルダ -- `docs` フォルダ +{% 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 -たとえば、独自の CONTRIBUTING ファイルを持たないパブリックリポジトリに Issue やプルリクエストを作成する人は誰でも、デフォルトの CONTRIBUTING ファイルへのリンクが見られます。 If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used. +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. -デフォルトのファイルは `.github` リポジトリにのみ格納されるものであって、クローン、パッケージ、リポジトリ個別のダウンロードには含まれません。 +Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository. -### サポートされているファイルの種類 +### 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: -| コミュニティ健全性ファイル | 説明 | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% 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 ファイルは、人々がプロジェクトにどのように貢献すべきかを伝えます。 For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% if currentVersion == "free-pro-team@latest" %} -| *FUNDING.yml* | FUNDING ファイルは、あなたのオープンソースプロジェクトに対する資金提供のオプションについての認知度を高める目的で、リポジトリにスポンサーボタンを表示するためのものです。 詳細は「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照してください。{% endif %} -| Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Issue およびプルリクエストのテンプレートは、リポジトリで Issue およびプルリクエストを開くときに含める情報をカスタマイズして標準化します。 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* | SECURITY ファイルには、プロジェクトのセキュリティ脆弱性について責任を持って報告する方法が記載されています。 詳しい情報については「[リポジトリにセキュリティポリシーを追加する](/articles/adding-a-security-policy-to-your-repository)」を参照してください。{% endif %} -| *SUPPORT.md* | SUPPORT ファイルは、プロジェクトについて支援を受ける方法を伝えるためのものです。 詳しい情報については"[プロジェクトへのサポートリソースの追加](/articles/adding-support-resources-to-your-project/)"を参照してください。 | +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/)." -デフォルトのライセンスファイルを作成することはできません。 ライセンスファイルは、プロジェクトのクローン時、パッケージ時、またはダウンロード時に含められるよう、個々のリポジトリに追加する必要があります。 +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] ドロップダウンメニュー](/assets/images/help/repository/create-repository-owner.png) -3. リポジトリの名前として **.github** と入力し、任意で説明を入力します。 ![リポジトリ作成フィールド](/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). ![プライベートまたはパブリックのステータスを選択するラジオボタン](/assets/images/help/repository/create-repository-public-private.png) +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) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -7. リポジトリの中に、サポートされているコミュニティ健全性ファイルの 1 つを作成します。 Issue templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. その他のサポートされているファイルは、リポジトリのルートにある必要があります。 詳細は「[新しいファイルを作成する](/articles/creating-new-files/)」を参照してください。 +7. 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/)." diff --git a/translations/ja-JP/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md b/translations/ja-JP/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md index b6aa94a1f8..969cf345c7 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md +++ b/translations/ja-JP/content/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository.md @@ -15,7 +15,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -You can create default pull request templates for your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/github/building-a-strong-community/creating-a-default-community-health-file)」を参照してください。 +Organization {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}またはユーザアカウントのデフォルトのプルリクエストテンプレートを作成できます{% endif %}。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/github/building-a-strong-community/creating-a-default-community-health-file)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/github/building-a-strong-community/creating-a-team-discussion.md b/translations/ja-JP/content/github/building-a-strong-community/creating-a-team-discussion.md index 5fb7dfcbca..6123268dca 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/creating-a-team-discussion.md +++ b/translations/ja-JP/content/github/building-a-strong-community/creating-a-team-discussion.md @@ -17,7 +17,7 @@ versions: {% 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. Click **Comment**. ![新しい Team ディスカッションの [Comment] ボタン](/assets/images/help/projects/team-discussions-comment-button.png) +8. [**Comment**] をクリックします。 ![新しい Team ディスカッションの [Comment] ボタン](/assets/images/help/projects/team-discussions-comment-button.png) ### 参考リンク diff --git a/translations/ja-JP/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md b/translations/ja-JP/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md index 8f9a9e01f2..b3f5309ac2 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md +++ b/translations/ja-JP/content/github/building-a-strong-community/editing-or-deleting-a-team-discussion.md @@ -14,7 +14,7 @@ versions: {% data reusables.organizations.specific_team %} {% data reusables.organizations.team-discussions-tab %} 6. 編集または削除する Team ディスカッションの横にある {% octicon "kebab-horizontal" aria-label="The edit icon" %} をクリックします。 -7. Click **Edit**. オプションで、[**Delete**] をクリックします。 ![Team ディスカッションの編集ボタン](/assets/images/help/projects/edit-team-discussions-button.png) +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) ### 参考リンク diff --git a/translations/ja-JP/content/github/building-a-strong-community/editing-wiki-content.md b/translations/ja-JP/content/github/building-a-strong-community/editing-wiki-content.md index 3280b5328e..45cd369421 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/editing-wiki-content.md +++ b/translations/ja-JP/content/github/building-a-strong-community/editing-wiki-content.md @@ -33,7 +33,7 @@ versions: 3. ウィキ サイドバーを使って、変更したいページにアクセスし、[**Edit**] をクリックします。 4. ウィキ ツールバーで [**Image**] をクリックします。 ![ウィキの画像追加ボタン](/assets/images/help/wiki/wiki_add_image.png) 5. [Insert Image] ダイアログボックスで、画像の URL と代替テキスト (これは検索エンジンや画像リーダーで使われます) を入力します。 -6. Click **OK**. +6. [**OK**] をクリックします。 #### リポジトリでの画像へのリンク diff --git a/translations/ja-JP/content/github/building-a-strong-community/index.md b/translations/ja-JP/content/github/building-a-strong-community/index.md index 063f25564d..59b8731429 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/index.md +++ b/translations/ja-JP/content/github/building-a-strong-community/index.md @@ -13,21 +13,15 @@ versions: ### 目次 {% topic_link_in_list /setting-up-your-project-for-healthy-contributions %} - {% link_in_list /about-community-management-and-moderation %} {% link_in_list /about-community-profiles-for-public-repositories %} {% link_in_list /accessing-a-projects-community-profile %} {% link_in_list /adding-a-code-of-conduct-to-your-project %} - {% link_in_list /setting-guidelines-for-repository-contributors %} {% link_in_list /adding-a-license-to-a-repository %} {% link_in_list /adding-support-resources-to-your-project %} - {% link_in_list /creating-a-default-community-health-file %} - - {% link_in_list /encouraging-helpful-contributions-to-your-project-with-labels %} - {% topic_link_in_list /using-templates-to-encourage-useful-issues-and-pull-requests %} {% link_in_list /about-issue-and-pull-request-templates %} {% link_in_list /configuring-issue-templates-for-your-repository %} @@ -42,7 +36,6 @@ versions: {% link_in_list /tracking-changes-in-a-comment %} {% link_in_list /managing-how-contributors-report-abuse-in-your-organizations-repository %} {% link_in_list /managing-reported-content-in-your-organizations-repository %} - {% topic_link_in_list /maintaining-your-safety-on-github %} {% link_in_list /blocking-a-user-from-your-personal-account %} {% link_in_list /viewing-users-youve-blocked-from-your-personal-account %} @@ -51,7 +44,6 @@ versions: {% link_in_list /viewing-users-who-are-blocked-from-your-organization %} {% link_in_list /unblocking-a-user-from-your-organization %} {% link_in_list /reporting-abuse-or-spam %} - {% topic_link_in_list /documenting-your-project-with-wikis %} {% link_in_list /about-wikis %} {% link_in_list /adding-or-editing-wiki-pages %} @@ -60,10 +52,8 @@ versions: {% link_in_list /viewing-a-wikis-history-of-changes %} {% link_in_list /changing-access-permissions-for-wikis %} {% link_in_list /disabling-wikis %} - {% topic_link_in_list /collaborating-with-your-team %} {% link_in_list /about-team-discussions %} {% link_in_list /creating-a-team-discussion %} {% link_in_list /editing-or-deleting-a-team-discussion %} {% link_in_list /pinning-a-team-discussion %} - diff --git a/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md b/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md index 8cd6f9a55a..aa2fb9206c 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md +++ b/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-for-your-user-account.md @@ -1,26 +1,26 @@ --- -title: Limiting interactions for your user account -intro: 'You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your user account.' +title: ユーザアカウントの操作を制限する +intro: 'ユーザアカウントが所有するすべてのパブリックリポジトリ内の特定のユーザに対して、一定期間アクティビティ制限を適用することができます。' versions: free-pro-team: '*' -permissions: Anyone can limit interactions for their own user account. +permissions: 誰でも自分のユーザアカウントの操作を制限できます。 --- -### About temporary interaction limits +### 一時的なインタラクションの制限について -Limiting interactions for your user account enables temporary interaction limits for all public repositories owned by your user account. {% data reusables.community.interaction-limits-restrictions %} +ユーザアカウントのインタラクションを制限すると、ユーザアカウントが所有するすべてのパブリックリポジトリの一時的なインタラクション制限が有効になります。 {% data reusables.community.interaction-limits-restrictions %} -{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your public repositories. +{% data reusables.community.interaction-limits-duration %} 制限期間が過ぎると、ユーザはパブリックリポジトリで通常のアクティビティを再開できます。 {% data reusables.community.types-of-interaction-limits %} -When you enable user-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/articles/limiting-interactions-in-your-repository)." +ユーザ全体でアクティビティ制限を有効にした場合、個々のリポジトリに対して操作制限を有効化または無効化することはできません。 個々のリポジトリのアクティビティ制限方法について詳しくは、「[リポジトリでのインタラクションを制限する](/articles/limiting-interactions-in-your-repository)」を参照してください。 -You can also block users. For more information, see "[Blocking a user from your personal account](/github/building-a-strong-community/blocking-a-user-from-your-personal-account)." +ユーザをブロックすることもできます 詳しい情報については、「[個人アカウントでユーザをブロックする](/github/building-a-strong-community/blocking-a-user-from-your-personal-account)」を参照してください。 -### Limiting interactions for your user account +### ユーザアカウントの操作を制限する {% data reusables.user_settings.access_settings %} -1. In your user settings sidebar, under "Moderation settings", click **Interaction limits**. !["Interaction limits" tab in the user settings sidebar](/assets/images/help/settings/settings-sidebar-interaction-limits.png) +1. [User settings] サイドバーの [Moderation settings] で、[**Interaction limits**] をクリックします。 ![[User settings] サイドバーの [Interaction limits] タブ](/assets/images/help/settings/settings-sidebar-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![[Temporary interaction limits] のオプション](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png) \ No newline at end of file diff --git a/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md b/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md index 14887424dd..0fb52373aa 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md +++ b/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-in-your-organization.md @@ -1,35 +1,35 @@ --- title: Organization での操作を制限する -intro: 'You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your organization.' +intro: 'Organization が所有するすべてのパブリックリポジトリ内の特定のユーザに対して、一定期間アクティビティ制限を適用することができます。' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/limiting-interactions-in-your-organization - /articles/limiting-interactions-in-your-organization versions: free-pro-team: '*' -permissions: Organization owners can limit interactions in an organization. +permissions: Organization のオーナーは、Organization 内のインタラクションを制限できます。 --- -### About temporary interaction limits +### 一時的なインタラクションの制限について -Limiting interactions in your organization enables temporary interaction limits for all public repositories owned by the organization. {% data reusables.community.interaction-limits-restrictions %} +Organization 内のインタラクションを制限すると、Organization が所有するすべてのパブリックリポジトリに対して一時的なインタラクション制限が有効になります。 {% data reusables.community.interaction-limits-restrictions %} -{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your organization's public repositories. +{% data reusables.community.interaction-limits-duration %} 制限期間が過ぎると、Organization はパブリックリポジトリで通常のアクティビティを再開できます。 {% data reusables.community.types-of-interaction-limits %} -Members of the organization are not affected by any of the limit types. +Organization のメンバーは、いずれの制限タイプの影響も受けません。 -Organization 全体でアクティビティ制限を有効にした場合、個々のリポジトリに対して操作制限を有効化または無効化することはできません。 For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/articles/limiting-interactions-in-your-repository)." +Organization 全体でアクティビティ制限を有効にした場合、個々のリポジトリに対して操作制限を有効化または無効化することはできません。 個々のリポジトリのアクティビティ制限方法について詳しくは、「[リポジトリでのインタラクションを制限する](/articles/limiting-interactions-in-your-repository)」を参照してください。 -Organization owners can also block users for a specific amount of time. ブロックの期間が過ぎると、自動的にユーザのブロックは解除されます。 詳細は「[Organization からユーザをブロックする](/articles/blocking-a-user-from-your-organization)」を参照してください。 +Organization のオーナーは、特定の期間だけユーザをブロックすることもできます。 ブロックの期間が過ぎると、自動的にユーザのブロックは解除されます。 詳細は「[Organization からユーザをブロックする](/articles/blocking-a-user-from-your-organization)」を参照してください。 ### Organization での操作を制限する {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} -1. In the organization settings sidebar, click **Moderation settings**. !["Moderation settings" in the organization settings sidebar](/assets/images/help/organizations/org-settings-moderation-settings.png) -1. Under "Moderation settings", click **Interaction limits**. !["Interaction limits" in the organization settings sidebar](/assets/images/help/organizations/org-settings-interaction-limits.png) +1. [organization settings] サイトバーで、[**Moderation settings**] をクリックします。 ![[organization settings] サイトバーの [Moderation settings]](/assets/images/help/organizations/org-settings-moderation-settings.png) +1. [Moderation settings] で、[**Interaction limits**] をクリックします。 ![[organization settings] サイトバーの [Interaction limits] タブ](/assets/images/help/organizations/org-settings-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![[Temporary interaction limits] のオプション](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png) diff --git a/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md b/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md index a30d8176e1..4c289ee500 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md +++ b/translations/ja-JP/content/github/building-a-strong-community/limiting-interactions-in-your-repository.md @@ -1,30 +1,30 @@ --- title: リポジトリでのインタラクションを制限する -intro: 'You can temporarily enforce a period of limited activity for certain users on a public repository.' +intro: 'パブリックリポジトリ上の特定のユーザに対して、一定期間アクティビティ制限を適用することができます。' redirect_from: - /articles/limiting-interactions-with-your-repository/ - /articles/limiting-interactions-in-your-repository versions: free-pro-team: '*' -permissions: People with admin permissions to a repository can temporarily limit interactions in that repository. +permissions: リポジトリへの管理者権限を持つユーザは、そのリポジトリでのインタラクションを一時的に制限できます。 --- -### About temporary interaction limits +### 一時的なインタラクションの制限について {% data reusables.community.interaction-limits-restrictions %} -{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your repository. +{% data reusables.community.interaction-limits-duration %} 制限期間が過ぎると、ユーザはリポジトリで通常のアクティビティを再開できます。 {% data reusables.community.types-of-interaction-limits %} -You can also enable activity limitations on all repositories owned by your user account or an organization. If a user-wide or organization-wide limit is enabled, you can't limit activity for individual repositories owned by the account. For more information, see "[Limiting interactions for your user account](/github/building-a-strong-community/limiting-interactions-for-your-user-account)" and "[Limiting interactions in your organization](/github/building-a-strong-community/limiting-interactions-in-your-organization)." +ユーザアカウントまたは Organization が所有するすべてのリポジトリでアクティビティ制限を有効にすることもできます。 ユーザ全体または Organization 全体の制限が有効になっている場合、アカウントが所有する個々のリポジトリのアクティビティを制限することはできません。 詳しい情報については、「[ユーザアカウントのインタラクションを制限する](/github/building-a-strong-community/limiting-interactions-for-your-user-account)」と「[Organization 内のインタラクションを制限する](/github/building-a-strong-community/limiting-interactions-in-your-organization)」を参照してください。 ### リポジトリでのインタラクションを制限する {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. In the left sidebar, click **Moderation settings**. !["Moderation settings" in repository settings sidebar](/assets/images/help/repository/repo-settings-moderation-settings.png) -1. Under "Moderation settings", click **Interaction limits**. ![リポジトリの設定での [Interaction limits] ](/assets/images/help/repository/repo-settings-interaction-limits.png) +1. 左サイドバーで [**Moderation settings**] をクリックします。 ![[Repository settings] サイトバーの [Moderation settings]](/assets/images/help/repository/repo-settings-moderation-settings.png) +1. [Moderation settings] で、[**Interaction limits**] をクリックします。 ![リポジトリの設定での [Interaction limits] ](/assets/images/help/repository/repo-settings-interaction-limits.png) {% data reusables.community.set-interaction-limit %} ![[Temporary interaction limits] のオプション](/assets/images/help/repository/temporary-interaction-limits-options.png) diff --git a/translations/ja-JP/content/github/building-a-strong-community/locking-conversations.md b/translations/ja-JP/content/github/building-a-strong-community/locking-conversations.md index 99c3442d8d..30787ab199 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/locking-conversations.md +++ b/translations/ja-JP/content/github/building-a-strong-community/locking-conversations.md @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. 会話をロックするとき、理由を指定することもできます。これは誰にでも見ることができます。 +会話が全体的に非建設的になったときや、コミュニティの行動規範{% if currentVersion == "free-pro-team@latest" %} または GitHub の [コミュニティ ガイドライン](/articles/github-community-guidelines){% endif %} に違反しているときは、会話をロックすることが妥当です。 会話をロックするとき、理由を指定することもできます。これは誰にでも見ることができます。 会話をロックすると、リポジトリに対する読み取りアクセスを持つユーザなら誰でも見ることのできるタイムラインイベントが作成されます。 ただし、会話をロックしたユーザの名前は、リポジトリへの書き込みアクセスを持つユーザにしか見えません。 書き込みアクセスを持たないユーザから見ると、タイムラインイベントは匿名化されています。 @@ -29,7 +29,7 @@ It's appropriate to lock a conversation when the entire conversation is not cons - [健全なコントリビューションを促すプロジェクトをセットアップする](/articles/setting-up-your-project-for-healthy-contributions) - 「[テンプレートを使用して便利な Issue およびプルリクエストを推進する](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)」 -- "[Managing disruptive comments](/articles/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %} +- 「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」{% if currentVersion == "free-pro-team@latest" %} - 「[{% data variables.product.prodname_dotcom %} での安全性を維持する](/github/building-a-strong-community/maintaining-your-safety-on-github)」 - [悪用あるいはスパムのレポート](/articles/reporting-abuse-or-spam) - 「[リポジトリでのインタラクションを制限する](/github/building-a-strong-community/limiting-interactions-in-your-repository)」 diff --git a/translations/ja-JP/content/github/building-a-strong-community/managing-disruptive-comments.md b/translations/ja-JP/content/github/building-a-strong-community/managing-disruptive-comments.md index ffe251438d..9a7ef42307 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/managing-disruptive-comments.md +++ b/translations/ja-JP/content/github/building-a-strong-community/managing-disruptive-comments.md @@ -1,6 +1,6 @@ --- title: 混乱を生むコメントを管理する -intro: 'You can {% if currentVersion == "free-pro-team@latest" %}hide, edit,{% else %}edit{% endif %} or delete comments on issues, pull requests, and commits.' +intro: 'Issue、プルリクエスト、 およびコミットに対するコメントを{% if currentVersion == "free-pro-team@latest" %}非表示、編集{% else %}編集{% endif %}、削除できます。' redirect_from: - /articles/editing-a-comment/ - /articles/deleting-a-comment/ @@ -40,7 +40,7 @@ versions: リポジトリに対する書き込み権限があるユーザは、Issue、プルリクエスト、およびコミットに対するコメントを編集することができます。 -It's appropriate to edit a comment and remove content that doesn't contribute to the conversation and violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. +会話に関係がない、コミュニティの行動規範{% if currentVersion == "free-pro-team@latest" %}または GitHub の[コミュニティ ガイドライン](/articles/github-community-guidelines){% endif %}に違反している場合は、コメントを編集して内容を削除するのが妥当です。 コメントを編集する際には、削除した内容があった元の場所がわかるように記録し、オプションで削除の理由を示します。 @@ -60,7 +60,7 @@ It's appropriate to edit a comment and remove content that doesn't contribute to リポジトリに対する書き込み権限があるユーザは、Issue、プルリクエスト、 およびコミットに対するコメントを削除することができます。 Organization オーナー、チームメンテナ、コメント作成者は、チームのページのコメントを削除することもできます。 -コメントの削除は、モデレーターとしての最終手段です。 It's appropriate to delete a comment if the entire comment adds no constructive content to a conversation and violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. +コメントの削除は、モデレーターとしての最終手段です。 コメント全体が会話にとって建設的な内容ではない場合や、コミュニティの行動規範{% if currentVersion == "free-pro-team@latest" %}または GitHub の[コミュニティ ガイドライン](/articles/github-community-guidelines){% endif %}に違反している場合は、コメントを削除するのが妥当です。 コメントを削除すると、リポジトリに対する読み取りアクセスを持つユーザなら誰でも見ることのできるタイムラインイベントが作成されます。 ただし、コメントを削除したユーザの名前は、リポジトリへの書き込みアクセスを持つユーザにしか見えません。 書き込みアクセスを持たないユーザから見ると、タイムラインイベントは匿名化されています。 diff --git a/translations/ja-JP/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md b/translations/ja-JP/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md index f5eb288e50..3fab705e85 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/ja-JP/content/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository.md @@ -29,7 +29,7 @@ assignees: octocat ``` {% note %} -**Note:** If a front matter value includes a YAML-reserved character such as `:` , you must put the whole value in quotes. For example, `":bug: Bug"` or `":new: triage needed, :bug: bug"`. +**注釈:** フロントマター値に `:` などの YAML 予約文字が含まれている場合は、値全体を引用符で囲む必要があります。 たとえば、`":bug: Bug"` または `":new: triage needed, :bug: bug"` などです。 {% endnote %} diff --git a/translations/ja-JP/content/github/building-a-strong-community/reporting-abuse-or-spam.md b/translations/ja-JP/content/github/building-a-strong-community/reporting-abuse-or-spam.md index 3e6d7000c6..9211a12435 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/reporting-abuse-or-spam.md +++ b/translations/ja-JP/content/github/building-a-strong-community/reporting-abuse-or-spam.md @@ -27,16 +27,16 @@ versions: ### Issue やプルリクエストをレポートする 1. レポートする Issue またはプルリクエストに移動します。 -2. In the upper-right corner of the issue or pull request, click -{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}, then click **Report content**. +2. Issue またはプルリクエストの右上隅にある +{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} をクリックし、[**Report content**] をクリックします。 ![コメントをレポートするボタン](/assets/images/help/repository/menu-report-issue-or-pr.png) {% data reusables.community.report-content %} ### コメントをレポートする 1. レポートするコメントに移動します。 -2. In the upper-right corner of the comment, click -{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}, then click **Report content**. +2. コメントの右上隅にある +{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} をクリックし、[**Report content**] をクリックします。 ![コメントをレポートするオプションを含むケバブメニュー](/assets/images/help/repository/menu-report-comment.png) {% data reusables.community.report-content %} @@ -58,7 +58,7 @@ versions: - [健全なコントリビューションを促すプロジェクトをセットアップする](/articles/setting-up-your-project-for-healthy-contributions) - 「[テンプレートを使用して便利な Issue およびプルリクエストを推進する](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)」 -- "[Managing disruptive comments](/articles/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %} +- 「[混乱を生むコメントを管理する](/articles/managing-disruptive-comments)」{% if currentVersion == "free-pro-team@latest" %} - 「[ {% data variables.product.prodname_dotcom %} での安全性を維持する](/github/building-a-strong-community/maintaining-your-safety-on-github)」 - 「[リポジトリでのインタラクションを制限する](/github/building-a-strong-community/limiting-interactions-in-your-repository)」{% endif %} - 「[コメントの変更を追跡する](/articles/tracking-changes-in-a-comment)」 diff --git a/translations/ja-JP/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md b/translations/ja-JP/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md index e5118cded3..ddab5d0301 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md +++ b/translations/ja-JP/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md @@ -22,7 +22,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -You can create default contribution guidelines for your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/github/building-a-strong-community/creating-a-default-community-health-file)」を参照してください。 +Organization {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}またはユーザアカウントのデフォルトのコントリビューションガイドラインを作成できます{% endif %}。 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/github/building-a-strong-community/creating-a-default-community-health-file)」を参照してください。 {% endif %} @@ -56,6 +56,6 @@ You can create default contribution guidelines for your organization{% if curren - オープンガバメント [コントリビューションガイドライン](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md). ### 参考リンク -- The Open Source Guides' section "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% if currentVersion == "free-pro-team@latest" %} +- オープンソースガイドのセクション「[オープンソースプロジェクトを始める](https://opensource.guide/starting-a-project/)」{% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %} +- 「[リポジトリへのライセンスの追加](/articles/adding-a-license-to-a-repository)」{% endif %} diff --git a/translations/ja-JP/content/github/building-a-strong-community/tracking-changes-in-a-comment.md b/translations/ja-JP/content/github/building-a-strong-community/tracking-changes-in-a-comment.md index 9ba9b0f91a..cc9e58e676 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/tracking-changes-in-a-comment.md +++ b/translations/ja-JP/content/github/building-a-strong-community/tracking-changes-in-a-comment.md @@ -29,5 +29,5 @@ versions: ### 参考リンク -{% if currentVersion == "free-pro-team@latest" %}- "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)"{% endif %} +{% if currentVersion == "free-pro-team@latest" %}-「[乱用やスパムをレポートする](/articles/reporting-abuse-or-spam)」{% endif %} - 「[コメントを編集する](/articles/editing-a-comment)」 diff --git a/translations/ja-JP/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md b/translations/ja-JP/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md index 5194edf2a5..0adad96b41 100644 --- a/translations/ja-JP/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md +++ b/translations/ja-JP/content/github/building-a-strong-community/unblocking-a-user-from-your-personal-account.md @@ -22,7 +22,7 @@ versions: ### プロフィールページからのユーザのブロックの解除 {% data reusables.profile.user_profile_page_navigation %} -2. In the left sidebar, under the user's profile picture, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Unblock or report user**. ![ユーザリンクのブロックの解除または報告](/assets/images/help/profile/profile-unblock-or-report-user.png) +2. 左のサイドバーのユーザのプロフィール写真の下にある [{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}] をクリックしてから、[**Unblock or report user**] をクリックします。 ![ユーザリンクのブロックの解除または報告](/assets/images/help/profile/profile-unblock-or-report-user.png) 3. [**Unblock user**] をクリックします。 ![ユーザのブロックの解除あるいは悪用のレポートの選択肢を持つモーダルボックス](/assets/images/help/profile/profile-unblockuser.png) {% tip %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index 1a1a47b95e..8390cd0f94 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -13,9 +13,9 @@ versions: ### ブランチについて -Branches allow you to develop features, fix bugs, or safely experiment with new ideas in a contained area of your repository. +ブランチを使用すると、リポジトリ内の領域で機能を開発したり、バグを修正したり、新しいアイデアを安全に試したりすることができます。 -ブランチは常に既存のものから作成します。 Typically, you might create a new branch from the default branch of your repository. その後、他の人がリポジトリに加えた変更とは別に、新しいブランチで作業できます。 機能を構築するために作成するブランチは、通常、フィーチャブランチまたはトピックブランチと呼ばれます。 詳しい情報については[リポジトリ内でのブランチの作成と削除](/articles/creating-and-deleting-branches-within-your-repository/)を参照してください。 +ブランチは常に既存のものから作成します。 通常、リポジトリのデフォルトブランチから新しいブランチを作成します。 その後、他の人がリポジトリに加えた変更とは別に、新しいブランチで作業できます。 機能を構築するために作成するブランチは、通常、フィーチャブランチまたはトピックブランチと呼ばれます。 詳しい情報については[リポジトリ内でのブランチの作成と削除](/articles/creating-and-deleting-branches-within-your-repository/)を参照してください。 また、{% data variables.product.prodname_pages %}サイトを公開するためにブランチを使うこともできます。 詳しい情報については「[{% data variables.product.prodname_pages %}について](/articles/what-is-github-pages)」を参照してください。 @@ -23,9 +23,9 @@ Branches allow you to develop features, fix bugs, or safely experiment with new ### About the default branch -{% data reusables.branches.new-repo-default-branch %} The default branch is the branch that {% data variables.product.prodname_dotcom %} displays when anyone visits your repository. The default branch is also the initial branch that Git checks out locally when someone clones the repository. {% data reusables.branches.default-branch-automatically-base-branch %} +{% data reusables.branches.new-repo-default-branch %} デフォルトブランチは、誰かがあなたのリポジトリにアクセスしたときに {% data variables.product.prodname_dotcom %} が表示されるブランチです。 また、デフォルトブランチは、誰かがリポジトリのクローンを作成したときに Git がローカルでチェックアウトする最初のブランチでもあります。 {% data reusables.branches.default-branch-automatically-base-branch %} -By default, {% data variables.product.product_name %} names the default branch {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %} in any new repository. +デフォルトでは、{% data variables.product.product_name %} は新しいリポジトリのデフォルトブランチ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %} に名前を付けます。 {% data reusables.branches.set-default-branch %} @@ -74,8 +74,8 @@ By default, {% data variables.product.product_name %} names the default branch { - ブランチでステータスチェック必須が有効化されていると、必要なCIテストがすべてパスするまで、変更をブランチにマージできません。 詳しい情報については[ステータスチェックについて](/articles/about-status-checks)を参照してください。 - ブランチでプルリクエストレビュー必須が有効化されている場合、プルリクエストレビューポリシー中のすべての要求が満たされるまでは、ブランチに変更をマージできません。 詳しい情報については[プルリクエストのマージ](/articles/merging-a-pull-request)を参照してください。 - ブランチでコードオーナーからの必須レビューが有効化されており、プルリクエストがオーナーを持つコードを変更している場合、コードオーナーがプルリクエストを承認しなければ、そのプルリクエストはマージできません。 詳細は「[コードオーナーについて](/articles/about-code-owners)」を参照してください。 -- ブランチでコミット署名必須が有効化されている場合、署名および検証されていないコミットはブランチにプッシュできません。 For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)" and "[About required commit signing](/articles/about-required-commit-signing)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -- If you use {% data variables.product.prodname_dotcom %}'s conflict editor to fix conflicts for a pull request that you created from a protected branch, {% data variables.product.prodname_dotcom %} helps you to create an alternative branch for the pull request, so that your resolution of the conflicts can be merged. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} でマージコンフリクトを解決する](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)」を参照してください。{% endif %} +- ブランチでコミット署名必須が有効化されている場合、署名および検証されていないコミットはブランチにプッシュできません。 詳しい情報については、「[コミット署名の検証について](/articles/about-commit-signature-verification)」および「[必須のコミット署名について](/articles/about-required-commit-signing)」を参照してください。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +- {% data variables.product.prodname_dotcom %} のコンフリクトエディタを使用して、保護されたブランチから作成したプルリクエストのコンフリクトを修正する場合、{% data variables.product.prodname_dotcom %} はプルリクエストの代替ブランチを作成して、コンフリクトの解決をマージできるようにします。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} でマージコンフリクトを解決する](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)」を参照してください。{% endif %} ### 参考リンク diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md index bd7653e45f..8f86d032ea 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests.md @@ -39,7 +39,7 @@ diff の見方には複数の選択肢があります。 ![Diff の表示のオプションメニュー](/assets/images/help/pull_requests/diff-settings-menu.png) -To simplify reviewing changes in a large pull request, you can filter the diff to only show selected file types, show files you are a CODEOWNER of, hide files you have already viewed, or hide deleted files. 詳しい情報については、「[プルリクエスト内のファイルをファイルタイプでフィルタリングする](/articles/filtering-files-in-a-pull-request)」を参照してください。 +大規模なプルリクエスト中の変更のレビューを簡素化するために、選択されたファイルタイプだけを表示、CODEOWNERS であるファイルを表示、表示したことのあるファイルを非表示、または削除されたファイルを非表示にするように diff をフィルタリングできます。 詳しい情報については、「[プルリクエスト内のファイルをファイルタイプでフィルタリングする](/articles/filtering-files-in-a-pull-request)」を参照してください。 ![ファイルフィルタのドロップダウンメニュー](/assets/images/help/pull_requests/file-filter-menu.png) @@ -55,7 +55,7 @@ To simplify reviewing changes in a large pull request, you can filter the diff t プルリクエスト中でツードット diff をシミュレートし、各ブランチの最新バージョン同士の比較を見たい場合には、ベースブランチをトピックブランチにマージできます。そうすれば、ブランチ間の最後の共通の祖先が更新されます。 -For more information about Git commands to compare changes, see "[Git diff options](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)" from the _Pro Git_ book site. +変更を比較するための Git コマンドに関する詳しい情報については、_Pro Git_ ブックサイトの「[Git diff のオプション](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)」を参照してください。 ### diffが表示されない理由 - ファイルあるいは特定のファイルタイプの合計での制限を超えた。 詳しい情報については[リポジトリ中のコンテンツとdiffの表示の制限](/articles/limits-for-viewing-content-and-diffs-in-a-repository/#diff-limits)を参照してください。 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 2aa70d365a..ee79cb7497 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 @@ -20,7 +20,7 @@ Issueは、バグレポートや計画された改善など、プロジェクト ### コメント中のアイデアへの反応 -議論の中のアイデアに対する賛意や異議を示すことができます。 Team ディスカッション、Issue、プルリクエストのコメントや本体に反応を加えても、その会話をサブスクライブしている人には通知が送信されません。 For more information about subscriptions, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}." +議論の中のアイデアに対する賛意や異議を示すことができます。 Team ディスカッション、Issue、プルリクエストのコメントや本体に反応を加えても、その会話をサブスクライブしている人には通知が送信されません。 プランに関する詳しい情報については、{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」{% else %}「[通知のサブスクライブとサブスクライブ解除](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}」を参照してください。 ![反応を含むIssueの例](/assets/images/help/repository/issue-reactions.png) diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-forks.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-forks.md index a46944c328..601c61807a 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-forks.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-forks.md @@ -18,17 +18,17 @@ versions: {% data reusables.repositories.desktop-fork %} -フォークを削除しても、オリジナルの上流のリポジトリは削除されません。 You can make any changes you want to your fork—add collaborators, rename files, generate {% data variables.product.prodname_pages %}—with no effect on the original.{% if currentVersion == "free-pro-team@latest" %} You cannot restore a deleted forked repository. 詳しい情報については、「[削除されたリポジトリを復元する](/articles/restoring-a-deleted-repository)」を参照してください。{% endif %} +フォークを削除しても、オリジナルの上流のリポジトリは削除されません。 オリジナルに影響を与えることなく、コラボレータの追加、ファイル名の変更、{% data variables.product.prodname_pages %} の生成など、自分のフォークに必要な変更を加えることができます。{% if currentVersion == "free-pro-team@latest" %} 削除されたフォークリポジトリを復元することはできません。 詳しい情報については、「[削除されたリポジトリを復元する](/articles/restoring-a-deleted-repository)」を参照してください。{% endif %} オープンソースプロジェクトでは、フォークを使用して、上流のリポジトリに提供される前にアイデアや変更をイテレーションすることがよくあります。 ユーザ所有のフォークに変更を加え、作業を上流リポジトリと比較するプルリクエストをオープンすると、上流リポジトリへのプッシュアクセスできる人に対して、変更をプルリクエストブランチにプッシュする権限を付与することができます。 これにより、リポジトリメンテナがマージする前に、ユーザが所有するフォークからプルリクエストブランチに対してローカルでコミットを実行したり、テストを実行したりすることができるようになり、コラボレーションがスピードアップします。 Organization が所有するフォークにプッシュ権限を与えることはできません。 {% data reusables.repositories.private_forks_inherit_permissions %} -If you want to create a new repository from the contents of an existing repository but don't want to merge your changes upstream in the future, you can duplicate the repository or, if the repository is a template, use the repository as a template. 詳細は「[リポジトリを複製する](/articles/duplicating-a-repository)」および「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 +既存のリポジトリのコンテンツから新しいリポジトリを作成するが、将来にわたって変更を上流にマージしない場合、リポジトリを複製するか、リポジトリがテンプレートである場合は、リポジトリをテンプレートとして使うことができます。 詳細は「[リポジトリを複製する](/articles/duplicating-a-repository)」および「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 ### 参考リンク - [コラボレーティブ開発モデルについて](/articles/about-collaborative-development-models) - [フォークからプルリクエストを作成する](/articles/creating-a-pull-request-from-a-fork) -- [Open Source Guides](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} +- [オープンソースガイド](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/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 79dfc67957..e30c6c434a 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 @@ -13,11 +13,11 @@ versions: プルリクエストがオープンになった後、*読み取り*アクセスを持つすべてのユーザは、提案された変更をレビューしてコメントできます。 また、作者がプルリクエストから直接適用できるコード行への特定の変更を提案することもできます。 詳細は「[プルリクエストで提案された変更をレビューする](/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" %}You can specify a subset of team members to be automatically assigned in the place of the whole 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 のコードレビューの割り当てを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)」を参照してください。{% endif %} レビューにより、提案された変更についての議論がなされ、その変更がリポジトリのコントリビューションのガイドラインやその他の品質標準を満たすことを保証しやすくなります。 コードの特定の種類や領域に対して、どの個人や Team をオーナーとするかを、CODEOWNERS ファイルで定義できます。 プルリクエストが、定義されたオーナーを持っているコードを変更するものである場合、オーナーである個人あるいはTeam がレビューを担当するよう、自動的にリクエストされます。 詳細は「[コードオーナーについて](/articles/about-code-owners/)」を参照してください。 -{% if currentVersion == "free-pro-team@latest" %}You can schedule reminders for pull requests that need to be reviewed. 詳しい情報については、「[プルリクエストのスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)」を参照してください。{% endif %} +{% if currentVersion == "free-pro-team@latest" %} レビューが必要なプルリクエストのリマインダーをスケジュールできます。 詳しい情報については、「[プルリクエストのスケジュールされたリマインダーを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)」を参照してください。{% endif %} ![凝固メント付きの変更をリクエストするレビューのヘッダ](/assets/images/help/pull_requests/review-header-with-line-comment.png) diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md index 766df3a5e4..38e5bb51c2 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/about-pull-requests.md @@ -27,7 +27,7 @@ versions: 他のコントリビューターは、あなたが提案した変更をレビューしたり、レビューコメントを追加したり、プルリクエストのディスカッションにコントリビュートしたり、さらにはプルリクエストにコメントを追加したりできます。 {% if currentVersion == "free-pro-team@latest" %} -You can see information about the branch's current deployment status and past deployment activity on the "Conversation" tab. 詳細は「[リポジトリのデプロイメントアクティビティを表示する](/articles/viewing-deployment-activity-for-your-repository)」を参照してください。 +[Conversation] タブで、ブランチの現在のデプロイメントステータスや過去のデプロイメントのアクティビティに関する情報を確認することができます。 詳細は「[リポジトリのデプロイメントアクティビティを表示する](/articles/viewing-deployment-activity-for-your-repository)」を参照してください。 {% endif %} 提案された変更に満足したなら、プルリクエストをマージできます。 共有リポジトリモデルで作業している場合は、プルリクエストを作成し、あなたか他のユーザが、プルリクエストで指定したベースブランチにフィーチャブランチからの変更をマージします。 詳しい情報については[プルリクエストのマージ](/articles/merging-a-pull-request)を参照してください。 @@ -54,12 +54,12 @@ You can see information about the branch's current deployment status and past de {% data reusables.pull_requests.mark-ready-review %} プルリクエストはいつでもドラフトに変換できます。 詳しい情報については、「[プルリクエストのステージの変更](/articles/changing-the-stage-of-a-pull-request)」を参照してください。 -### Differences between commits on compare and pull request pages +### 比較とプルリクエストページのコミットの違い -The compare and pull request pages use different methods to calculate the diff for changed files: +比較とプルリクエストページは、次のような異なる方法で、変更されたファイルの diff を計算します。 -- Compare pages show the diff between the tip of the head ref and the current common ancestor (that is, the merge base) of the head and base ref. -- Pull request pages show the diff between the tip of the head ref and the common ancestor of the head and base ref at the time when the pull request was created. Consequently, the merge base used for the comparison might be different. +- 比較ページには、head ref のヒントと、head およびベース ref の現在の共通の先祖 (マージベース) との diff が表示されます。 +- プルリクエストページには、プルリクエストが作成されたときの head ref のヒントと、head およびベース ref の共通の先祖との diff が表示されます。 したがって、比較に使用されるマージベースは異なる場合があります。 ### 参考リンク diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md index b87661df59..7c8ec3c19d 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request.md @@ -23,7 +23,7 @@ versions: {% tip %} -**Tip:** When you open a pull request, {% data variables.product.product_name %} will set the base to the commit that branch references. If the branch is updated in the future, {% data variables.product.product_name %} will not update the base branch's commit. +**参考:** プルリクエストを開くと、{% data variables.product.product_name %} はそのブランチが参照するコミットにベースを設定します。 ブランチが今後更新される場合、{% data variables.product.product_name %} はベースブランチのコミットを更新しません。 {% endtip %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md index e8201eaf25..e9dcd81c8b 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: プルリクエストのステージの変更 -intro: 'You can mark a draft pull request as ready for review{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} or convert a pull request to a draft{% endif %}.' +intro: 'ドラフトのプルリクエストをレビューの準備完了 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} としてマークするか、プルリクエストをドラフトに変換することができます{% endif %}。' permissions: リポジトリへの書き込み権限を持つユーザとプルリクエストの作者は、プルリクエストのステージを変更できます。 product: '{% data reusables.gated-features.draft-prs %}' redirect_from: diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md index 37ee6b7762..b89f563ab4 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally.md @@ -19,7 +19,7 @@ versions: ### アクティブなプルリクエストをローカルで修正する {% data reusables.repositories.sidebar-pr %} -2. In the list of pull requests, click the pull request you'd like to modify.{% if currentVersion == "free-pro-team@latest" %} +2. プルリクエストのリストで、変更するプルリクエストをクリックします。{% if currentVersion == "free-pro-team@latest" %} 3. プルリクエストをオープンする場所を選択するには、[**Open with {% octicon "triangle-down" aria-label="The down triangle icon" %}**] ドロップダウンを選択して、いずれかのタブをクリックします。 ![Link to access command line pull request instructions](/assets/images/help/pull_requests/open-with-button.png){% else %} 3. マージボックスで、[**command line instructions**] をクリックします。 手順に従い、提案されたプルリクエストをローカルにダウンロードしてください。 ![コマンドラインのプルリクエスト手順へのリンク](/assets/images/help/pull_requests/pull_request_show_command_line_merge.png) 4. オプションで、提案された変更を {% data variables.product.prodname_desktop %} で表示するには、[**open this in {% data variables.product.prodname_desktop %}**] をクリックします。 ![Link to open a pull request locally in Desktop](/assets/images/help/desktop/open-pr-in-desktop.png){% endif %} @@ -45,7 +45,7 @@ versions: [main] $ git checkout BRANCHNAME > Switched to a new branch 'BRANCHNAME' ``` -7. これで、このブランチに対して任意の操作を実行できます。 You can run some local tests, or merge other branches into the branch. +7. これで、このブランチに対して任意の操作を実行できます。 ローカルテストを実行するか、他のブランチをブランチにマージすることができます。 8. 準備ができたら、新しいブランチをプッシュできます。 ```shell [pull-inactive-pull-request] $ git push origin BRANCHNAME diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md index fb88696c52..9683f6210f 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request.md @@ -55,5 +55,5 @@ Pull Request レビューへの行コメント追加に関する 詳しい情報 ### 参考リンク - 「[コードスニペットへのパーマリンクを作成する](/articles/creating-a-permanent-link-to-a-code-snippet/)」 -{% if currentVersion == "free-pro-team@latest" %}- "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)" +{% if currentVersion == "free-pro-team@latest" %}-「[乱用やスパムをレポートする](/articles/reporting-abuse-or-spam)」 {% endif %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index 2ef644157a..dad732d4c6 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -25,7 +25,7 @@ versions: 1. On -{% data variables.product.product_name %}, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created. +{% data variables.product.product_name %} で、プルリクエストブランチが作成されたフォーク (またはリポジトリのコピー) のメインページに移動します。 {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% tip %} @@ -69,7 +69,7 @@ versions: **ヒント:** 例も含めたプルリクエストブランチに関する詳しい情報については「[プルリクエストを作成する](/articles/creating-a-pull-request/#changing-the-branch-range-and-destination-repository)」を参照してください。 {% endtip %} -8. これで、このブランチに対して任意の操作を実行できます。 You can push new commits to it, run some local tests, or merge other branches into the branch. 自由に修正しましょう。 +8. これで、このブランチに対して任意の操作を実行できます。 新しいコミットのプッシュ、ローカルでのテスト、他のブランチからのマージを行うことができます。 自由に修正しましょう。 9. プルリクエストの head ブランチに変更をコミットした後、元のプルリクエストに直接、変更をプッシュできます。 この例では、head ブランチは `test-branch` です: ```shell $ git push origin test-branch diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md index 9598e1f509..58b2da57bb 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request.md @@ -1,6 +1,6 @@ --- title: プルリクエストの作成方法 -intro: 'リポジトリへの、変更の提案、または変更における共同作業をするには、プルリクエストを作成できます。 These changes are proposed in a *branch*, which ensures that the default branch only contains finished and approved work.' +intro: 'リポジトリへの、変更の提案、または変更における共同作業をするには、プルリクエストを作成できます。 これらの変更は「ブランチ」を介して提案され、デフォルトブランチには完成していて、かつ承認された作業のみが含まれるようにします。' redirect_from: - /articles/creating-a-pull-request versions: @@ -33,7 +33,7 @@ base リポジトリを変更するとき、プルリクエストの通知も変 {% tip %} -**Tips**: +**ヒント**: - 比較ビューを使用して、どの時間枠であっても比較対象として設定できます。 詳しい情報については「[コミットを比較する](/github/committing-changes-to-your-project/comparing-commits)」を参照してください。 - プロジェクトメンテナーはプルリクエストテンプレートをリポジトリに追加できます。 テンプレートにはプルリクエスト本文にある情報のプロンプトが含まれます。 詳しい情報については[Issue およびプルリクエストのテンプレートについて](/articles/about-issue-and-pull-request-templates)を参照してください。 diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md index a5e27985e7..5d70af478b 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -22,7 +22,11 @@ versions: {% data reusables.pull_requests.automatically-delete-branches %} -If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." +{% note %} + +**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." + +{% endnote %} If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)" or "[Closing a pull request](/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request)." diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/index.md index 8ab07bcdb5..0c8ac02e31 100644 --- a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/index.md +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/index.md @@ -29,9 +29,7 @@ versions: {% link_in_list /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility %} {% topic_link_in_list /collaborating-on-repositories-with-code-quality-features %} {% link_in_list /about-status-checks %} - {% link_in_list /working-with-pre-receive-hooks %} - {% topic_link_in_list /proposing-changes-to-your-work-with-pull-requests %} {% link_in_list /about-branches %} {% link_in_list /creating-and-deleting-branches-within-your-repository %} @@ -39,9 +37,7 @@ versions: {% link_in_list /about-comparing-branches-in-pull-requests %} {% link_in_list /creating-a-pull-request %} {% link_in_list /creating-a-pull-request-from-a-fork %} - {% link_in_list /changing-the-stage-of-a-pull-request %} - {% link_in_list /requesting-a-pull-request-review %} {% link_in_list /changing-the-base-branch-of-a-pull-request %} {% link_in_list /committing-changes-to-a-pull-request-branch-created-from-a-fork %} @@ -52,15 +48,12 @@ versions: {% topic_link_in_list /reviewing-changes-in-pull-requests %} {% link_in_list /about-pull-request-reviews %} {% link_in_list /reviewing-proposed-changes-in-a-pull-request %} - {% link_in_list /filtering-files-in-a-pull-request %} - {% link_in_list /finding-changed-methods-and-functions-in-a-pull-request %} {% link_in_list /commenting-on-a-pull-request %} {% link_in_list /viewing-a-pull-request-review %} - + {% link_in_list /reviewing-dependency-changes-in-a-pull-request %} {% link_in_list /incorporating-feedback-in-your-pull-request %} - {% link_in_list /approving-a-pull-request-with-required-reviews %} {% link_in_list /dismissing-a-pull-request-review %} {% link_in_list /checking-out-pull-requests-locally %} diff --git a/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md new file mode 100644 index 0000000000..b55ac06e48 --- /dev/null +++ b/translations/ja-JP/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -0,0 +1,74 @@ +--- +title: Reviewing dependency changes in a pull request +intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Dependency review is currently in beta and subject to change. + +{% endnote %} + +### About dependency review + +If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. + +Dependency review is available in: + +* All public repositories. +* Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[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)." + +Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. + +By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. {% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix them at some later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)." + +Dependency review supports the same languages and package management ecosystems as the dependency graph. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)」を参照してください。 + +### Reviewing dependencies in a pull request + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} + +1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. + + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + + {% note %} + + **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% endnote %} + +1. Check the dependencies listed in the dependency review. + + ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) + + Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name. + + The icon beside each dependency indicates whether the dependency has been added ({% octicon "diff-added" aria-label="Dependency added icon" %}), updated ({% octicon "diff-modified" aria-label="Dependency modified icon" %}), or removed ({% octicon "diff-removed" aria-label="Dependency removed icon" %}) in this pull request. + + Other information includes: + + * The version, or version range, of the new, updated, or deleted dependency. + * For a specific version of a dependency: + * The age of that release of the dependency. + * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency. + * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project. + + Where a dependency has a known vulnerability, the warning message includes: + + * A brief description of the vulnerability. + * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability. + * The severity of the vulnerability. + * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. + +1. You can return to the original view of the file by clicking the source diff button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) 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 4b78b8fdb8..5a58074239 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 @@ -29,6 +29,18 @@ versions: ![[Cancel review] ボタン](/assets/images/help/pull_requests/cancel-review-button.png) +{% if currentVersion == "free-pro-team@latest" %} +### Reviewing dependency changes + +If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. 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 reusables.repositories.changed-files %} + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) +{% endif %} + ### ファイルをレビュー済みとしてマークする ファイルのレビュー後は、そのファイルをレビュー済みとしてマークできます。マークしたファイルは折りたたまれます。 ファイルを表示後に変更すると、レビュー済みマークが解除されます。 @@ -53,8 +65,5 @@ versions: ### 参考リンク -- "[プルリクエストのレビューについて](/articles/about-pull-request-reviews)" -- [プルリクエストのための必須レビューについて](/articles/about-required-reviews-for-pull-requests) -- "[必須レビューで Pull Request を承認する](/articles/approving-a-pull-request-with-required-reviews)" -- [プルリクエストへのコメント](/articles/commenting-on-a-pull-request) -- 「[プルリクエストをレビューステータスでフィルタリングする](/articles/filtering-pull-requests-by-review-status)」 +- [プルリクエストのための必須レビューについて](/github/administering-a-repository/about-required-reviews-for-pull-requests) +- 「[プルリクエストをレビューステータスでフィルタリングする](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)」 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 fe2e847431..c84f34c0b4 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 @@ -60,7 +60,7 @@ versions: {% note %} -**Note:** {% data reusables.gated-features.internal-repos %} +**注釈:** {% data reusables.gated-features.internal-repos %} {% endnote %} diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/changing-a-commit-message.md b/translations/ja-JP/content/github/committing-changes-to-your-project/changing-a-commit-message.md index 7ee54074db..a25a0bb546 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/changing-a-commit-message.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/changing-a-commit-message.md @@ -46,7 +46,7 @@ Git で使うデフォルトのテキストエディタは、`core.editor` の {% endwarning %} -**Changing the message of the most recently pushed commit** +**直近でプッシュされたコミットのメッセージを変更する** 1. [上記の手順](/articles/changing-a-commit-message#commit-has-not-been-pushed-online)に従って、コミットメッセージを修正します。 2. `push --force` コマンドにより、古いコミットをフォースプッシュで上書きします。 @@ -54,7 +54,7 @@ Git で使うデフォルトのテキストエディタは、`core.editor` の $ git push --force example-branch ``` -**Changing the message of older or multiple commit messages** +**古いまたは複数のコミットメッセージを変更する** 複数のコミットまたは古いコミットの、メッセージを修正する必要がある場合は、インタラクティブなリベースを利用した後にフォースプッシュして、コミットの履歴を変更できます。 @@ -98,7 +98,7 @@ Git で使うデフォルトのテキストエディタは、`core.editor` の ``` 4. コミット一覧のファイルを保存して閉じます。 5. 生成された各コミットコミットファイルに、新しいコミットメッセージを入力し、ファイルを保存して閉じます。 -6. When you're ready to push your changes to GitHub, use the push --force command to force push over the old commit. +6. 変更を GitHub にプッシュする準備ができたら、push --force コマンドを使用して、古いコミットを強制的にプッシュします。 ```shell $ git push --force example-branch ``` diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/comparing-commits.md b/translations/ja-JP/content/github/committing-changes-to-your-project/comparing-commits.md index 1d0ebf66c7..496899d348 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/comparing-commits.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/comparing-commits.md @@ -27,9 +27,9 @@ compare の最も一般的な使い方は、新しいプルリクエストを開 ### タグを比較する -リリースタグを比較すると、前回のリリース以降のリポジトリへの変更が表示されます。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)."{% endif %} +リリースタグを比較すると、前回のリリース以降のリポジトリへの変更が表示されます。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} 詳しい情報については、「[リリースを比較する](/github/administering-a-repository/comparing-releases)」を参照してください。{% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page.{% else %} Instead of typing a branch name, type the name of your tag in the `compare` drop down menu.{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} タグを比較するには、ページ上部の [`compare`] ドロップダウンメニューからタグ名を選択します。{% else %}ブランチ名を入力する代わりに、[`compare`] ドロップダウンメニューにタグの名前を入力します。{% endif %} 2 つのタグ間を比較する例については、[こちらをクリック](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3)してください。 @@ -47,7 +47,7 @@ compare の最も一般的な使い方は、新しいプルリクエストを開 ベースリポジトリと、フォークした任意のリポジトリを比較できます。 これは、ユーザがプロジェクトにプルリクエストを実行したときに表示されるビューです。 -別のリポジトリにあるブランチを比較するには、ブランチの名前の前にユーザ名を付けてください。 For example, by specifying `octocat:main` for `base` and `octo-org:main` for `compare`, you can compare the `main` branch of the repositories respectively owned by `octocat` and `octo-org`. +別のリポジトリにあるブランチを比較するには、ブランチの名前の前にユーザ名を付けてください。 たとえば、`base` に `octocat:main` を指定し、`compare` に `octo-org:main` を指定することで、`octocat` と `octo-org` がそれぞれ所有するリポジトリの `main` ブランチを比較できます。 2 つのリポジトリ間を比較した例については、[こちらをクリック](https://github.com/octocat/linguist/compare/master...octo-org:master)してください。 diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md b/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md index 5fab151dec..c41b86f5ff 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors.md @@ -1,6 +1,6 @@ --- title: 複数の作者を持つコミットを作成する -intro: 'コミットのメッセージに、1 つ以上の "Co-authored-by" トレーラーを追加することで、1 つのコミットに複数の作者を追加できます。 Co-authored commits are visible on {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} and can be included in the profile contributions graph and the repository''s statistics{% endif %}.' +intro: 'コミットのメッセージに、1 つ以上の "Co-authored-by" トレーラーを追加することで、1 つのコミットに複数の作者を追加できます。 共作されたコミットは {% data variables.product.product_name %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} に表示され、プロファイルコントリビューショングラフとリポジトリの統計に含めることができます{% endif %}。' redirect_from: - /articles/creating-a-commit-with-multiple-authors versions: diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/index.md b/translations/ja-JP/content/github/committing-changes-to-your-project/index.md index 2c3f5fda80..3b167f7cfb 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/index.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/index.md @@ -16,9 +16,7 @@ versions: {% topic_link_in_list /creating-and-editing-commits %} {% link_in_list /about-commits %} {% link_in_list /creating-a-commit-with-multiple-authors %} - {% link_in_list /creating-a-commit-on-behalf-of-an-organization %} - {% link_in_list /changing-a-commit-message %} {% topic_link_in_list /viewing-and-comparing-commits %} {% link_in_list /commit-branch-and-tag-labels %} diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md b/translations/ja-JP/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md index 4f32ec15f6..b11b0349f0 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user.md @@ -3,7 +3,7 @@ title: コミットが間違ったユーザにリンクされているのはな redirect_from: - /articles/how-do-i-get-my-commits-to-link-to-my-github-account/ - /articles/why-are-my-commits-linked-to-the-wrong-user -intro: '{% data variables.product.product_name %} は、コミットヘッダのメールアドレスを使用して、コミットを GitHub ユーザにリンクします。 If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% if currentVersion != "github-ae@latest" %}, add an email address to your account email settings, or do both{% endif %}.' +intro: '{% data variables.product.product_name %} は、コミットヘッダのメールアドレスを使用して、コミットを GitHub ユーザにリンクします。 コミットが別のユーザにリンクされている、またはまったくリンクされていない場合は、ローカルの Git 設定 {% if currentVersion != "github-ae@latest" %} を変更するか、アカウントのメール設定にメールアドレスを追加するか、あるいはその両方を行う必要があります{% endif %}。' versions: free-pro-team: '*' enterprise-server: '*' @@ -19,10 +19,10 @@ versions: ### コミットは別のユーザにリンクされています -If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% if currentVersion == "github-ae@latest" %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. 古いコミットはリンクされません。 For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your {% data variables.product.product_name %} account to link future commits to your account. +コミットが別のユーザにリンクされている場合は、ローカルの Git 設定のメールアドレスが {% data variables.product.product_name %} 上のそのユーザのアカウントに接続されていることを意味します。 この場合、ローカルの Git 設定 {% if currentVersion == "github-ae@latest" %} のメールを {% data variables.product.product_name %} のアカウントに関連付けられたアドレスに変更して、今後のコミットをリンクすることができます。 古いコミットはリンクされません。 詳しい情報については、「[コミットメールアドレスを設定する](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)」を参照してください。{% else %}そして新しいメールアドレスを {% data variables.product.product_name %} アカウントに追加して、今後のコミットをアカウントにリンクします。 -1. To change the email address in your local Git configuration, follow the steps in "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". 複数のマシンで作業している場合は、各マシンでこの設定を変更する必要があります。 -2. Add the email address from step 2 to your account settings by following the steps in "[Adding an email address to your GitHub account](/articles/adding-an-email-address-to-your-github-account)".{% endif %} +1. ローカル Git 設定でメールアドレスを変更するには、「<[コミットメールアドレスを設定する](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)」の手順に従います。 複数のマシンで作業している場合は、各マシンでこの設定を変更する必要があります。 +2. 「[GitHub アカウントにメールアドレスを追加する](/articles/adding-an-email-address-to-your-github-account)」の手順に従って、ステップ 2 のメールアドレスをアカウント設定に追加します。{% endif %} これ以降のコミットは、あなたのアカウントにリンクされます。 @@ -35,12 +35,12 @@ If your commits are linked to another user, that means the email address in your 1. コミットメッセージリンクをクリックしてコミットに移動します。 ![コミットメッセージリンク](/assets/images/help/commits/commit-msg-link.png) 2. コミットがリンクされていない理由に関するメッセージを読むには、ユーザ名の右側にある青い {% octicon "question" aria-label="Question mark" %} の上にカーソルを合わせます。 ![コミットホバーメッセージ](/assets/images/help/commits/commit-hover-msg.png) - - **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% if currentVersion != "github-ae@latest" %}To link your commits, [add the email address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account).{% endif %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat. - - **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% if currentVersion != "github-ae@latest" %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} - - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% if currentVersion != "github-ae@latest" %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} + - **未確認の作者 (メールアドレスあり)** このメッセージにメールアドレスが表示される場合、コミットの作成に使用したアドレスは {% data variables.product.product_name %} のアカウントに接続されていません。 {% if currentVersion != "github-ae@latest" %}コミットをリンクするには、[メールアドレスを GitHub のメール設定に追加](/articles/adding-an-email-address-to-your-github-account)します。{% endif %} メールアドレスに Gravatar が関連付けられている場合、デフォルトの灰色の Octocat ではなく、コミットの横に Gravatar が表示されます。 + - **未確認の作者 (メールアドレスなし)** メールアドレスなしでこのメッセージが表示された場合は、{% data variables.product.product_name %} のアカウントに接続できない一般的なメールアドレスを使用しています。{% if currentVersion != "github-ae@latest" %} [Git でコミットメールアドレスを設定](/articles/setting-your-commit-email-address)してから、[してから、新しいアドレスを GitHub メール設定に追加](/articles/adding-an-email-address-to-your-github-account)して、今後のコミットをリンクする必要があります。 古いコミットはリンクされません。{% endif %} + - **無効なメール** ローカルの Git 設定のメールアドレスが空白であるか、メールアドレスとしてフォーマットされていません。{% if currentVersion != "github-ae@latest" %} [Gitでコミットメールアドレスを設定](/articles/setting-your-commit-email-address)してから、[してから、新しいアドレスをGitHubメール設定に追加](/articles/adding-an-email-address-to-your-github-account)して、今後のコミットをリンクする必要があります。 古いコミットはリンクされません。{% endif %} {% if currentVersion == "github-ae@latest" %} -You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. 古いコミットはリンクされません。 For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)." +ローカルの Git 設定のメールをアカウントに関連付けられたアドレスに変更して、今後のコミットをリンクすることができます。 古いコミットはリンクされません。 詳しい情報については、「[コミットメールアドレスを設定する](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)」を参照してください。 {% endif %} {% warning %} diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md index c22cb7a8b0..dd27a270ad 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-archiving-repositories.md @@ -21,7 +21,7 @@ versions: リポジトリがアーカイブされると、コラボレータや Team の追加や削除ができなくなります。 リポジトリへのアクセス権を持つコントリビューターは、プロジェクトをフォークするか Star を付けることだけができます。 -When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, and comments become read-only. アーカイブされたリポジトリに変更を加えるには、まずそのリポジトリのアーカイブ解除をしなければなりません。 +リポジトリがアーカイブされると、その Issue、プルリクエスト、コード、ラベル、マイルストーン、プロジェクト、wiki、リリース、コミット、タグ、ブランチ、リアクション、コードスキャンアラート、およびコメントが読み取り専用になります。 アーカイブされたリポジトリに変更を加えるには、まずそのリポジトリのアーカイブ解除をしなければなりません。 アーカイブされたリポジトリに対して検索ができます。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)を参照してください。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)を参照してください。 詳しい情報については[Issueやプルリクエストの検索](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)を参照してください。 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 01b8a59eda..df6710d6f7 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 @@ -21,10 +21,10 @@ versions: 管理者あるいはオーナー権限を持つ誰かがレビュー必須を有効化した場合、作者がリポジトリ中でプルリクエストをマージできるための条件としてコードオーナーからの承認を必須とすることもできます。 詳しい情報については、「[プルリクエストの必須レビューを有効にする](/github/administering-a-repository/enabling-required-reviews-for-pull-requests)」を参照してください。 -{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. 詳しい情報については、「[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 のコードレビューの割り当てを管理する](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)」を参照してください。{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -ファイルにコードオーナーがいる場合、プルリクエストをオープンする前にコードオーナーを確認できます。 In the repository, you can browse to the file and hover over +ファイルにコードオーナーがいる場合、プルリクエストをオープンする前にコードオーナーを確認できます。 リポジトリでは、ファイルを参照して {% octicon "shield-lock" aria-label="The edit icon" %}. ![リポジトリ内のファイルのコードオーナー](/assets/images/help/repository/code-owner-for-a-file.png) @@ -34,15 +34,15 @@ versions: CODEOWNERS ファイルを使うためには、コードオーナーを追加したいブランチで、リポジトリのルート、`docs/`、`.github/` のいずれかのディレクトリに `CODEOWNERS` という新しいファイルを作成してください。 -各CODEOWNERSファイルは、リポジトリ内の単一のブランチにコードオーナーを割り当てます。 Thus, you can assign different code owners for different branches, such as `@octo-org/codeowners-team` for a code base on the default branch and `@octocat` for a {% data variables.product.prodname_pages %} site on the `gh-pages` branch. +各CODEOWNERSファイルは、リポジトリ内の単一のブランチにコードオーナーを割り当てます。 したがって、デフォルトブランチのコードベースに `@octo-org/codeowners-team`、`gh-pages` ブランチの {% data variables.product.prodname_pages %} サイトに `@octocat` など、ブランチごとに異なるコードオーナーを割り当てることができます。 コードオーナーがレビューのリクエストを受け取るためには、CODEOWNERS ファイルがプルリクエストの base ブランチになければなりません。 たとえばリポジトリ中の`gh-pages`ブランチの、*.js*ファイルのコードオーナーとして`@octocat`を割り当てたなら、*.js*に変更を加えるプルリクエストがheadブランチと`gh-pages`の間でオープンされると、`@octocat`はレビューのリクエストを受けることになります。 ### CODEOWNERSの構文 -CODEOWNERS ファイルは、[gitignore](https://git-scm.com/docs/gitignore#_pattern_format) ファイルで使われているのと同じルールに従うパターンを利用します。 パターンの後には1つ以上の{% data variables.product.prodname_dotcom %}のユーザー名あるいはTeam名が続きます。これらの名前には標準の`@username`あるいは`@org/team-name`フォーマットが使われます。 たとえば `user@example.com` のような、ユーザの {% data variables.product.product_name %} アカウントに追加されたメールアドレスでユーザを参照することもできます。 +CODEOWNERS ファイルは、[一部の例外](#syntax-exceptions)を除いて、[gitignore](https://git-scm.com/docs/gitignore#_pattern_format) ファイルで使用されるルールのほとんどに従うパターンを使用します。 パターンの後には1つ以上の{% data variables.product.prodname_dotcom %}のユーザー名あるいはTeam名が続きます。これらの名前には標準の`@username`あるいは`@org/team-name`フォーマットが使われます。 たとえば `user@example.com` のような、ユーザの {% data variables.product.product_name %} アカウントに追加されたメールアドレスでユーザを参照することもできます。 -CODEOWNERS ファイルのいずれかの行に無効な構文が含まれている場合、そのファイルは検出されず、レビューのリクエストには使用されません。 無効な構文には、{% data variables.product.product_name %} に存在しないインラインコメントとユーザ名または Team 名が含まれます。 +CODEOWNERS ファイルのいずれかの行に無効な構文が含まれている場合、そのファイルは検出されず、レビューのリクエストには使用されません。 #### CODEOWNERS ファイルの例 ``` # これはコメントです。 @@ -79,11 +79,18 @@ docs/* docs@example.com # appsディレクトリ内のすべてのファイルのオーナーになります。 apps/ @octocat -# In this example, @doctocat owns any file in the `/docs` -# directory in the root of your repository and any of its -# subdirectories. +# この例では、@doctocatはリポジトリのルートにある +# `/docs` ディレクトリとそのサブディレクトリにある +# ファイルを所有しています。 /docs/ @doctocat ``` +#### 構文の例外 +gitignore ファイルには、CODEOWNERS ファイルでは動作しないいくつかの構文ルールがあります。 +- コメントではなくパターンとして扱われるように、`\` を使用して `#` で始まるパターンをエスケープする +- `!` を使用してパターンを否定する +- `[ ]` を使用して文字範囲を定義する + + ### 参考リンク diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-readmes.md index e6ae03cd1a..37c9bcee43 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-readmes.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-readmes.md @@ -13,9 +13,9 @@ versions: ### READMEについて -You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% if currentVersion == "free-pro-team@latest" %}, contribution guidelines, and a code of conduct{% elsif enterpriseServerVersions contains currentVersion %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions. +README ファイルをリポジトリに追加して、プロジェクトに関する重要な情報を伝えることができます。 README は、リポジトリライセンス {% if currentVersion == "free-pro-team@latest" %}、コントリビューションガイドライン、行動規範 {% elsif enterpriseServerVersions contains currentVersion %}、コントリビューションガイドライン {% endif %} とともに、プロジェクトへの要望を伝え、コントリビューションの管理を支援します。 -For more information about providing guidelines for your project, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." +プロジェクトのガイドラインの提供方法の詳細については、{% if currentVersion == "free-pro-team@latest" %}「[プロジェクトに行動規範を追加する](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)」および {% endif %}「[健全なコントリビューションのためのプロジェクトの設定](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)」を参照してください。 多くの場合、READMEはリポジトリへの訪問者が最初に目にするアイテムです。 通常、README ファイルには以下の情報が含まれています: - このプロジェクトが行うこと diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index acfc414f9d..8580c2d660 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -1,6 +1,6 @@ --- title: リポジトリについて -intro: リポジトリは、プロジェクトのフォルダーのようなものです。 プロジェクトのリポジトリにはプロジェクトのすべてのファイルが含まれ、各ファイルのリビジョン履歴が保存されます。 プロジェクトの作業をリポジトリ内で議論し、管理することもできます。 +intro: リポジトリには、プロジェクトのすべてのファイルと各ファイルの改訂履歴が含まれています。 リポジトリ内でプロジェクトの作業について話し合い、管理できます。 redirect_from: - /articles/about-repositories versions: @@ -17,14 +17,16 @@ versions: {% if currentVersion == "free-pro-team@latest" %} With -{% data variables.product.prodname_free_team %} for user accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. プライベートリポジトリの高度なツールを入手するには、 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、または {% data variables.product.prodname_ghe_cloud %} にアップグレードします。 {% data reusables.gated-features.more-info %} +ユーザアカウントと Organization の {% data variables.product.prodname_free_team %} を使用すると、完全な機能一式を備えた無制限のパブリックリポジトリ、または限定された機能一式を備えた無制限のプライベートリポジトリで無制限のコラボレータと連携できます。 プライベートリポジトリの高度なツールを入手するには、 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %}、または {% data variables.product.prodname_ghe_cloud %} にアップグレードします。 {% data reusables.gated-features.more-info %} {% else %} 各個人および Organization は、無制限のリポジトリを所有でき、すべてのリポジトリにコラボレータを何人でも招待できます。 {% endif %} -リポジトリの Issue、プルリクエスト、プロジェクトボードを使ってプロジェクトで他者とコラボレーションできます。 - -![octocat/Hello-World リポジトリのメインページ](/assets/images/help/repository/repo-main-page.png) +リポジトリを使用して、作業を管理し、他のユーザと共同作業を行うことができます。 +- Issue を使用して、ユーザフィードバックの収集、ソフトウェアバグの報告、および実行するタスクの整理を行うことができます。 詳しい情報については、「[Issue について](/github/managing-your-work-on-github/about-issues)」を参照してください。 +- {% data reusables.discussions.you-can-use-discussions %} +- プルリクエストを使用して、リポジトリへの変更を提案できます。 詳しい情報については[プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)を参照してください。 +- プロジェクトボードを使用して、Issue とプルリクエストを整理して優先順位を付けることができます。 詳細は「[プロジェクトボードについて](/github/managing-your-work-on-github/about-project-boards)」を参照してください。 {% data reusables.repositories.repo-size-limit %} 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 ca019efeb3..f5e9be4ff9 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 @@ -14,8 +14,8 @@ versions: github-ae: '*' --- -{% data variables.product.product_name %} uses the open source [Linguist library](https://github.com/github/linguist) to -determine file languages for syntax highlighting and repository statistics. Language statistics will update after you push changes to your default branch. +{% data variables.product.product_name %} は、オープンソースの [Linguist ライブラリ](https://github.com/github/linguist)を使用して、 +構文の強調表示とリポジトリ統計のファイル言語を決定します。 デフォルトブランチに変更をプッシュすると、言語統計が更新されます。 ファイルによっては特定しにくいものもあります。また、プロジェクトによっては、主たるコード以外のライブラリやベンダーファイルが含まれていることもあります。 誤った結果が返される場合は、Linguist の [トラブルシューティングガイド](https://github.com/github/linguist#troubleshooting)を調べてみてください。 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 fb18005a8b..163f732bd2 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 @@ -1,6 +1,6 @@ --- title: リポジトリの可視性について -intro: 'You can restrict who has access to a repository by choosing a repository''s visibility: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}public, internal, or private{% elsif currentVersion == "github-ae@latest" %}private or internal{% else %} public or private{% endif %}.' +intro: 'リポジトリの可視性を選択することで、リポジトリにアクセスできるユーザを制限できます{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}（パブリック、内部、プライベート{% elsif currentVersion == "github-ae@latest" %}{% else %}パブリックまたはプライベートなど）{% endif %}。' versions: free-pro-team: '*' enterprise-server: '*' @@ -9,15 +9,15 @@ versions: ### リポジトリの可視性について -{% if currentVersion == "github-ae@latest" %}When you create a repository owned by your user account, the repository is always private. When you create a repository owned by an organization, you can choose to make the repository private or internal.{% else %}When you create a repository, you can choose to make the repository public or private.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} If you're creating the repository in an organization{% if currentVersion == "free-pro-team@latest" %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %}{% endif %} +{% if currentVersion == "github-ae@latest" %} ユーザアカウント所有のリポジトリを作成すると、リポジトリは常にプライベートになります。 Organization 所有のリポジトリを作成するときに、プライベートリポジトリにするか内部リポジトリにするかを選択できます。{% else %}リポジトリを作成するときに、リポジトリをパブリックにするかプライベートにするかを選択できます。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} Enterprise アカウントが所有する Organization {% if currentVersion == "free-pro-team@latest" %} でリポジトリを作成している場合は{% endif %}、リポジトリを内部にすることもできます。{% endif %}{% endif %} {% if enterpriseServerVersions contains currentVersion %} If -{% data variables.product.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using {% data variables.product.product_location %}, including outside collaborators. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. {% if currentVersion ver_gt "enterprise-server@2.19" %} Internal repositories are accessible to enterprise members. 詳しい情報については、「[内部リポジトリについて](#about-internal-repositories)」を参照してください。{% endif %} +{% data variables.product.product_location %} はプライベートモードでもファイアウォールの内側にありません。インターネット上のすべてのユーザがパブリックリポジトリにアクセスできます。 そうではない場合、外部のコラボレータを含め、{% data variables.product.product_location %} を使用するすべてのユーザがパブリックリポジトリを利用できます。 プライベートリポジトリには、自分、明示的にアクセスを共有するユーザ、および Organization リポジトリの場合は特定の Organization メンバーのみがアクセスできます。 {% if currentVersion ver_gt "enterprise-server@2.19" %} Enterprise メンバーは内部リポジトリにアクセスできます。 詳しい情報については、「[内部リポジトリについて](#about-internal-repositories)」を参照してください。{% endif %} {% elsif currentVersion == "github-ae@latest" %} -Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to all enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." +プライベートリポジトリには、自分、明示的にアクセスを共有するユーザ、および Organization リポジトリの場合は特定の Organization メンバーのみがアクセスできます。 内部リポジトリには、すべての Enterprise メンバーがアクセスできます。 詳しい情報については、「[内部リポジトリについて](#about-internal-repositories)」を参照してください。 {% else %} -Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." +パブリックリポジトリには、インターネット上のすべてのユーザがアクセスできます。 プライベートリポジトリには、自分、明示的にアクセスを共有するユーザ、および Organization リポジトリの場合は特定の Organization メンバーのみがアクセスできます。 内部リポジトリには、Enterprise メンバーがアクセスできます。 詳しい情報については、「[内部リポジトリについて](#about-internal-repositories)」を参照してください。 {% endif %} Organization のオーナーは、Organization 内で作成されたすべてのリポジトリにいつでもアクセスできます。 詳細は「[Organization のリポジトリ権限レベル](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)」を参照してください。 @@ -29,15 +29,15 @@ Organization のオーナーは、Organization 内で作成されたすべての {% note %} -**Note:** {% data reusables.gated-features.internal-repos %} +**注釈:** {% data reusables.gated-features.internal-repos %} {% endnote %} {% data reusables.repositories.about-internal-repos %}インナーソースに関する詳しい情報については、{% data variables.product.prodname_dotcom %}のホワイトペーパー「[インナーソース入門](https://resources.github.com/whitepapers/introduction-to-innersource/)」を参照してください。 -All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% if currentVersion == "free-pro-team@latest" %}outside of the enterprise{% else %}who are not members of an organization{% endif %}, including outside collaborators on organization repositories. For more information, see {% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}"[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and {% endif %}"[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." +すべての Enterprise メンバーは内部リポジトリへの読み取り権限を持っていますが、内部リポジトリは、Organization リポジトリの外部のコラボレータを含む、Organization メンバーではない Enterprise 外{% else %}のユーザ {% if currentVersion == "free-pro-team@latest" %} には表示されません{% endif %}。 詳しい情報については、{% if currentVersion == "free-pro-team@latest" or "github-ae@latest" %}「[Enterprise アカウントのロール](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)」および{% endif %}「[Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization)」を参照してください。 {% data reusables.repositories.internal-repo-default %} -If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. +Enterprise が所有するすべての Organization からユーザが削除されると、そのユーザの内部リポジトリのフォークは自動的に削除されます。 {% endif %} diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md index e8f5d83340..b547873168 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/backing-up-a-repository.md @@ -1,6 +1,6 @@ --- title: リポジトリのバックアップ -intro: 'You can use{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Git and{% endif %} the API {% if currentVersion == "free-pro-team@latest" %}or a third-party tool {% endif %}to back up your repository.' +intro: '{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} Git と {% endif %}API {% if currentVersion == "free-pro-team@latest" %}、またはサードパーティツール{% endif %}を使用してリポジトリをバックアップできます。' redirect_from: - /articles/backing-up-a-repository versions: @@ -32,13 +32,13 @@ versions: - [プロジェクト](/rest/reference/projects#list-repository-projects) {% endif %} -Once you have {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). +バックアップするすべてのコンテンツの {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} ローカルバージョンを入手したら、zip アーカイブを作成してアーカイブを{% else %}ダウンロードしたり、外部ハードドライブにコピー{% endif %}したり、[Google Drive](https://www.google.com/drive/) や [Dropbox](https://www.dropbox.com/) などのクラウドベースのバックアップサービスにアップロードしたりすることができます。 {% if currentVersion == "free-pro-team@latest" %} ### サードパーティのバックアップツール リポジトリのバックアップを自動化するセルフサービスのツールはたくさんあります。 オプトアウトしておらず、誰でもデータにアクセスできるようにする {% data variables.product.product_name %} 上の_すべての_パブリックリポジトリをアーカイブするアーカイブプロジェクトとは異なり、バックアップツールは_特定の_リポジトリからデータをダウンロードし、新しいブランチまたはディレクトリ内に整理します。 アーカイブプロジェクトの詳細については、「[{% data variables.product.prodname_dotcom %} のコンテンツとデータのアーカイブについて](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)」を参照してください。 -You can back up all of a repository's Git data (such as project files and commit history), as well as much data from +ー -{% data variables.product.product_name %} (such as issues and pull requests), with [BackHub](https://github.com/marketplace/backhub), which creates daily recurring backups of your repositories with snapshots up to 30 days back in time. BackHub は {% data variables.product.prodname_marketplace %}から利用できます。 +[BackHub](https://github.com/marketplace/backhub) を使用すると、リポジトリのすべての Git データ（プロジェクトファイルやコミット履歴など）と {% data variables.product.product_name %} からの多くのデータ（Issue やプルリクエストなど）をバックアップできます。これにより、最大 30 日前までのスナップショットを使用して、リポジトリの日次の定期バックアップが作成されます。 BackHub は {% data variables.product.prodname_marketplace %}から利用できます。 {% endif %} diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md index 2f3ab95b40..b58cdc9740 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository.md @@ -1,6 +1,6 @@ --- title: リポジトリをクローンする -intro: 'When you create a repository on {% data variables.product.product_location %}, it exists as a remote repository. You can clone your repository to create a local copy on your computer and sync between the two locations.' +intro: '{% data variables.product.product_location %} にリポジトリを作成した場合、それはリモートリポジトリとなります。 リポジトリのクローンを作成して、コンピューター上にローカルコピーを作成し、これらの 2 つの場所の間で同期することができます。' redirect_from: - /articles/cloning-a-repository versions: @@ -11,16 +11,16 @@ versions: ### リポジトリのクローンについて -You can clone a repository from {% data variables.product.product_location %} to your local computer to make it easier to fix merge conflicts, add or remove files, and push larger commits. When you clone a repository, you copy the repository from {% data variables.product.product_location %} to your local machine. +{% data variables.product.product_location %} からローカルコンピューターにリポジトリのクローンを作成して、マージの競合の修正、ファイルの追加または削除、より大きなコミットのプッシュを簡単に行うことができます。 リポジトリのクローンを作成する場合は、リポジトリを {% data variables.product.product_location %} からローカルマシンにコピーします。 -リポジトリをクローンすると、その時点で {% data variables.product.product_location %} にあるすべてのリポジトリデータの完全なコピーがプルダウンされます。これには、プロジェクトのすべてのファイルとフォルダのすべてのバージョンも含まれます。 You can push your changes to the remote repository on {% data variables.product.product_location %}, or pull other people's changes from {% data variables.product.product_location %}. 詳しい情報については、「[一般的な Git コマンドを使用する](/github/using-git/using-common-git-commands)」を参照してください。 +リポジトリをクローンすると、その時点で {% data variables.product.product_location %} にあるすべてのリポジトリデータの完全なコピーがプルダウンされます。これには、プロジェクトのすべてのファイルとフォルダのすべてのバージョンも含まれます。 変更を {% data variables.product.product_location %} のリモートリポジトリにプッシュするか、他のユーザの変更を {% data variables.product.product_location %} からプルすることができます。 詳しい情報については、「[一般的な Git コマンドを使用する](/github/using-git/using-common-git-commands)」を参照してください。 -You can clone your existing repository or clone another person's existing repository to contribute to a project. +既存のリポジトリのクローンを作成することも、他のユーザの既存のリポジトリのクローンを作成してプロジェクトに貢献することもできます。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} {% tip %} -**Tip**: You can also clone a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo clone`](https://cli.github.com/manual/gh_repo_clone)" in the {% data variables.product.prodname_cli %} documentation. +**ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリのクローンを作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo clone`](https://cli.github.com/manual/gh_repo_clone)」を参照してください。 {% endtip %} {% endif %} @@ -47,7 +47,7 @@ You can clone your existing repository or clone another person's existing reposi 空のリポジトリにはファイルが含まれていません。 リポジトリを作成するときに README でリポジトリを初期化しない場合に多くあります。 {% data reusables.repositories.navigate-to-repo %} -2. HTTPS でコマンドラインを使用してリポジトリをクローンするには、[Quick setup] で {% octicon "clippy" aria-label="The clipboard icon" %} をクリックします。 To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. ![[Empty repository clone URL] ボタン](/assets/images/help/repository/empty-https-url-clone-button.png) +2. HTTPS でコマンドラインを使用してリポジトリをクローンするには、[Quick setup] で {% octicon "clippy" aria-label="The clipboard icon" %} をクリックします。 Organization の SSH 認証局から発行された証明書を含む SSH キーを使用してリポジトリのクローンを作成するには、[**SSH**]、{% octicon "clippy" aria-label="The clipboard icon" %} の順にクリックします。 ![[Empty repository clone URL] ボタン](/assets/images/help/repository/empty-https-url-clone-button.png) または、リポジトリをデスクトップにクローンするには、{% octicon "desktop-download" aria-label="The desktop download button" %} [**Set up in Desktop**] をクリックし、プロンプトに従ってクローンを完了します。 ![[Empty repository clone desktop] ボタン](/assets/images/help/repository/empty-desktop-clone-button.png) diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md index a57c85afa8..d5899873c3 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-new-repository.md @@ -24,7 +24,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} {% tip %} -**Tip**: You can also create a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. +**ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリを作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo create`](https://cli.github.com/manual/gh_repo_create)」を参照してください。 {% endtip %} {% endif %} @@ -35,9 +35,9 @@ versions: 3. [Owner] ドロップダウンで、リポジトリを作成するアカウントを選択します。 ![[Owner] ドロップダウンメニュー](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} -6. If you're not using a template, there are a number of optional items you can pre-populate your repository with. 既存のリポジトリを {% data variables.product.product_name %}にインポートする場合は、このようなオプションはどれも選択しないでください。マージコンフリクトが起きる可能性があります。 ユーザインターフェースを使用して新しいファイルを追加または作成する、またはコマンドラインを使用して後で新しいファイルを追加することができます。 詳細は「[コマンドラインを使って Git リポジトリをインポートする](/articles/importing-a-git-repository-using-the-command-line/)」、「[コマンドラインを使ってリポジトリにファイルを追加する](/articles/adding-a-file-to-a-repository-using-the-command-line)」、「[マージコンフリクトに対処する](/articles/addressing-merge-conflicts/)」を参照してください。 +6. テンプレートを使用していない場合は、リポジトリに自動入力できるオプションアイテムがいくつかあります。 既存のリポジトリを {% data variables.product.product_name %}にインポートする場合は、このようなオプションはどれも選択しないでください。マージコンフリクトが起きる可能性があります。 ユーザインターフェースを使用して新しいファイルを追加または作成する、またはコマンドラインを使用して後で新しいファイルを追加することができます。 詳細は「[コマンドラインを使って Git リポジトリをインポートする](/articles/importing-a-git-repository-using-the-command-line/)」、「[コマンドラインを使ってリポジトリにファイルを追加する](/articles/adding-a-file-to-a-repository-using-the-command-line)」、「[マージコンフリクトに対処する](/articles/addressing-merge-conflicts/)」を参照してください。 - 自分のプロジェクトについて説明するドキュメントである README を作成できます。 詳しい情報については「[README について](/articles/about-readmes/)」を参照してください。 - - 無視するルールを記載した *.gitignore* ファイルを作成できます。 For more information, see "[Ignoring files](/articles/ignoring-files)."{% if currentVersion == "free-pro-team@latest" %} + - 無視するルールを記載した *.gitignore* ファイルを作成できます。 詳しい情報については、「[ファイルを無視する](/articles/ignoring-files)」を参照してください。{% if currentVersion == "free-pro-team@latest" %} - 自分のプロジェクトにソフトウェアライセンスを追加することができます。 詳細は「[リポジトリのライセンス](/articles/licensing-a-repository)」を参照してください。{% endif %} {% data reusables.repositories.select-marketplace-apps %} {% data reusables.repositories.create-repo %} @@ -48,5 +48,5 @@ versions: ### 参考リンク - "[Organization のリポジトリへのアクセスを管理する](/articles/managing-access-to-your-organization-s-repositories)" -- [Open Source Guides](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} +- [オープンソースガイド](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md index 636af30680..cda4b31db2 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template.md @@ -9,14 +9,14 @@ versions: github-ae: '*' --- -### About repository templates +### リポジトリテンプレートついて リポジトリに対する読み取り権限があるユーザなら誰でも、テンプレートからリポジトリを作成できます。 詳細は「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照してください。 {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} {% tip %} -**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. +**ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリをテンプレートから作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo create`](https://cli.github.com/manual/gh_repo_create)」を参照してください。 {% endtip %} {% endif %} diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md index 7b480297f5..a3514094a2 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: テンプレートリポジトリを作成する -intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}, branches,{% endif %} and files.' +intro: '既存のリポジトリをテンプレートにして、自分や他のユーザが同じディレクトリ構造{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}、ブランチ、{% endif %}およびファイルで新しいリポジトリを生成できるようにすることができます。' permissions: リポジトリに対する管理者権限があるユーザなら誰でも、リポジトリをテンプレート化できます。 redirect_from: - /articles/creating-a-template-repository @@ -12,13 +12,13 @@ versions: {% note %} -**Note**: Your template repository cannot include files stored using {% data variables.large_files.product_name_short %}. +**注釈**: テンプレートリポジトリには、{% data variables.large_files.product_name_short %} を使用して保存されたファイルを含めることはできません。 {% endnote %} テンプレートリポジトリを作成するには、リポジトリを作成して、そのリポジトリをテンプレート化する必要があります。 リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 -After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." +リポジトリをテンプレートにすると、リポジトリにアクセスできるユーザは誰でも、デフォルトブランチと同じディレクトリ構造とファイルで新しいリポジトリを生成できます。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} また、リポジトリに他のすべてのブランチを含めることもできます。{% endif %} 詳しい情報については、「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md index 8049580087..6c28acbb3c 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md @@ -29,7 +29,7 @@ $ git clone https://{% data variables.command_line.codeblock %}/user/ remotes/origin/awesome > remotes/origin/more-work > remotes/origin/new-main @@ -39,7 +39,7 @@ $ git branch -a ```shell $ git checkout new-main -# Create and checkout a tracking branch +# 追跡ブランチを作成してチェックアウト > Branch new-main set up to track remote branch new-main from origin. > Switched to a new branch 'new-main' ``` diff --git a/translations/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 8e1d29c5aa..d19d1d91fd 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 @@ -1,6 +1,6 @@ --- title: 'Error: Repository not found' -intro: '{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}If you see this error when cloning a repository, it means that the repository does not exist or you do not have permission to access it.{% else %}If you see this error when cloning a repository, it means that the repository does not exist, you do not have permission to access it, or {% data variables.product.product_location %} is in private mode.{% endif %} There are a few solutions to this error, depending on the cause.' +intro: '{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}リポジトリのクローン作成時にこのエラーが表示される場合は、リポジトリが存在しないか、リポジトリにアクセスする権限がないことを示しています。{% else %}リポジトリのクローン作成時にこのエラーが表示される場合は、リポジトリが存在しないか、リポジトリにアクセスする権限がないか、{% data variables.product.product_location %} がプライベートモードになっていることを示しています。{% endif %} 原因に応じて、このエラーに対するいくつかの解決策があります。' redirect_from: - /articles/error-repository-not-found versions: diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md index d689d8e38e..884ee367be 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md @@ -45,16 +45,16 @@ HTTPS エラーの例を次に示します: ```shell $ git remote -v # 既存のリモートを表示する -> origin https://github.com/github/reactivecocoa.git (fetch) -> origin https://github.com/github/reactivecocoa.git (push) +> origin https://github.com/ghost/reactivecocoa.git (fetch) +> origin https://github.com/ghost/reactivecocoa.git (push) -$ git remote set-url origin https://github.com/github/ReactiveCocoa.git +$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git # 'origin' リモートの URL を変更する $ git remote -v # 新規 URL を検証する -> origin https://github.com/github/ReactiveCocoa.git (fetch) -> origin https://github.com/github/ReactiveCocoa.git (push) +> origin https://github.com/ghost/ReactiveCocoa.git (fetch) +> origin https://github.com/ghost/ReactiveCocoa.git (push) ``` もしくは、[{% data variables.product.prodname_desktop %}](https://desktop.github.com/) アプリケーションから URL を変更できます。 @@ -71,7 +71,7 @@ $ git remote -v {% tip %} -**ヒント**: リモートリポジトリを操作するときの毎回の認証情報の入力を省くには、[認証情報のキャッシュ](/github/using-git/caching-your-github-credentials-in-git)をオンにします。 If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail. +**ヒント**: リモートリポジトリを操作するときの毎回の認証情報の入力を省くには、[認証情報のキャッシュ](/github/using-git/caching-your-github-credentials-in-git)をオンにします。 すでに認証情報のキャッシュを使用している場合は、コンピューターに正しい認証情報がキャッシュされていることを確認してください。 認証情報が正しくない、または古い場合、認証に失敗します。 {% endtip %} diff --git a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/index.md index b46a83b3df..5b91d4c7d0 100644 --- a/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/index.md +++ b/translations/ja-JP/content/github/creating-cloning-and-archiving-repositories/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repositories %} {% link_in_list /about-repository-visibility %} {% link_in_list /creating-a-new-repository %} - {% link_in_list /creating-a-repository-from-a-template %} - {% link_in_list /about-readmes %} {% link_in_list /about-code-owners %} {% link_in_list /about-repository-languages %} {% link_in_list /licensing-a-repository %} - {% link_in_list /creating-a-template-repository %} - {% link_in_list /creating-an-issues-only-repository %} {% link_in_list /limits-for-viewing-content-and-diffs-in-a-repository %} {% link_in_list /duplicating-a-repository %} @@ -39,8 +35,6 @@ versions: {% topic_link_in_list /archiving-a-github-repository %} {% link_in_list /about-archiving-repositories %} {% link_in_list /archiving-repositories %} - {% link_in_list /about-archiving-content-and-data-on-github %} {% link_in_list /referencing-and-citing-content %} - {% link_in_list /backing-up-a-repository %} diff --git a/translations/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 1aa03ce681..2200537d9d 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,6 +1,6 @@ --- -title: リポジトリのライセンス -intro: 'GitHub のパブリックリポジトリは、オープンソース ソフトウェアの共有にも頻繁に利用されています。 リポジトリを真にオープンソースにしたければ、他のユーザが自由にそのソフトウェアを使用でき、変更や配布もできるように、ライセンスを付与する必要があります。' +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.' redirect_from: - /articles/open-source-licensing/ - /articles/licensing-a-repository @@ -9,86 +9,86 @@ versions: enterprise-server: '*' --- -### 適切なライセンスを選択する +### Choosing the right license -コードのライセンスについて理解しやすいように、[choosealicense.com](http://choosealicense.com) のページを用意しました。 ソフトウェアのライセンスは、ソースコードに対して許可されることとされないことを規定するものなので、十分な情報に基づいて決定することが重要です。 +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. -ライセンスの選択は義務ではありませんが、 ライセンスがない場合はデフォルトの著作権法が適用されます。つまり、ソースコードについては作者があらゆる権利を留保し、ソースコードの複製、配布、派生物の作成は誰にも許可されないということです。 オープンソースのプロジェクトを作成する場合は、オープンソース ライセンスを設定することを強くおすすめします。 プロジェクトに適したライセンスの選択に関する詳細な手引きは、[オープンソース ガイド](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project)に記載されています。 +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. {% 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. 詳細は「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」を参照してください。 +**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)." {% endnote %} -### ライセンスの置かれている場所を確認する +### Determining the location of your license -多くの場合、ライセンステキストはリポジトリのルートにある `LICENSE.txt` (または `LICENSE.md`) というファイルに書かれています。 [Hubot の例をこちらに示します](https://github.com/github/hubot/blob/master/LICENSE.md)。 +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). -プロジェクトによっては、ライセンスに関する情報は README に記載されています。 たとえばプロジェクトの README には、「当ライセンスは MIT ライセンスの規約に基づいて付与されています」などの文言が書かれていることがあります。 +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." -ベスト プラクティスとして、プロジェクトにはライセンス ファイルを含めることをお勧めします。 +As a best practice, we encourage you to include the license file with your project. -### ライセンス別に GitHub を検索する +### Searching GitHub by license type -`license` 修飾子と、正確なライセンス キーワードを使用すると、ライセンスまたはライセンス ファミリーに基づいてリポジトリをフィルタリングできます。 +You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword: -| ライセンス | ライセンス キーワード | -| ----- | ------------------------------------------------------------- | -| | 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` | +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` | -ファミリー ライセンス別で検索すると、結果にはそのファミリーのライセンスがすべて含まれます。 たとえば、`license:gpl` というクエリを実行した結果には、GNU General Public License v2.0 と GNU General Public License v3.0 でライセンスされているリポジトリが含まれます。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-by-license)を参照してください。 +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)." -### ライセンスを見つけてもらう +### Detecting a license -[オープンソースの Ruby Gem Licensee](https://github.com/benbalter/licensee) は、リポジトリの *LICENSE* ファイルを、既知のライセンスの候補リストと比較します。 Licensee には [ライセンス API](/rest/reference/licenses) も用意されており、 {% data variables.product.product_name %} のリポジトリがどのようにライセンスされているかを[深く理解できます](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 自分のリポジトリで使用しているライセンスが、[ライセンス選択のウェブサイト](http://choosealicense.com/appendix/)にリストされていない場合は、[ライセンスの追加をリクエストする](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)ことができます。 +[The open source Ruby gem Licensee](https://github.com/benbalter/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](http://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). -自分のリポジトリで使用しているライセンスが、ライセンス選択のウェブサイトにはリストされていて、リポジトリ ページのトップに明示的に表示されていない場合には、複数のライセンスが含まれるなど、複雑な状況が考えられます。 ライセンスを見つけてもらうために、*LICENSE* ファイルは単純にし、リポジトリの *README* ファイルなど、どこかでその複雑さに言及してください。 +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. -### 既存のライセンスでリポジトリにライセンスを適用する +### Applying a license to a repository with an existing license -ライセンスを選択できるのは、GitHub で新しいプロジェクトを作成するときだけです。 ブラウザを使って、手動でライセンスを追加できます。 リポジトリへのライセンスの追加についての詳しい情報は、「[リポジトリにライセンスを追加する](/articles/adding-a-license-to-a-repository)」を参照してください。 +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.com でのライセンス選択のスクリーンショット](/assets/images/help/repository/repository-license-picker.png) +![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png) -### 免責事項 +### Disclaimer -GitHub がオープンソース ライセンスへの取り組みで目指しているのは、ユーザが十分な情報に基づいて選択できるように基盤を作ることです。 GitHub は、オープンソース ライセンスとそれを使用しているプロジェクトについての情報をユーザが取得できるように、ライセンス情報を掲載しています。 その情報がお役に立つことを願っていますが、GitHub は法律の専門家ではなく、誤りがないとは言えません。 そのため、GitHub は情報を「現状有姿」で提供するものであり、GitHub で、または GitHub を通じて提供する情報またはライセンスについては何らの保証もせず、かかるライセンス情報の利用に起因する損害については責任を負いません。 コードに適したライセンスや、ライセンスに関する他の法的な問題について不明な点がある場合は、必ず専門家にご相談ください。 +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. -### 参考リンク +### Further reading - The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/ja-JP/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/ja-JP/content/github/customizing-your-github-workflow/about-github-marketplace.md index bd5d083e50..5ee86a477d 100644 --- a/translations/ja-JP/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/ja-JP/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -7,26 +7,27 @@ versions: free-pro-team: '*' --- -[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) では、[{% data variables.product.prodname_github_app %} および {% data variables.product.prodname_oauth_app %}](/apps/differences-between-apps/)、そして {% data variables.product.prodname_actions %} を含む無料および有料のツールを見つけ、ブラウズし、インストールできます。 +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) で、{% data variables.product.prodname_github_app %}、{% data variables.product.prodname_oauth_app %}、{% data variables.product.prodname_actions %} などの無料および有料ツールを見つけて確認し、インストールできます。 有料のツールを購入した場合、{% data variables.product.product_name %} のプランの支払いに使用しているのと同じ支払い情報でツールのプランに支払いをすることになり、通常の支払日に一つの課金を受けます。 詳しい情報については、[{% data variables.product.prodname_marketplace %}の支払いについて](/articles/about-billing-for-github-marketplace)を参照してください。 -ツールによっては、14 日間の無料トライアルを選択することもできます。 トライアルの間はいつでもキャンセルでき、課金されることはありませんが、自動的にツールへのアクセスは失われます。 有料プランは 14 日間のトライアルの終了時に開始されます。 詳しい情報については、[{% data variables.product.prodname_marketplace %}の支払いについて](/articles/about-billing-for-github-marketplace)を参照してください。 +一部のツールでは、14 日間の無料トライアルを選択することもできます。 トライアルの間はいつでもキャンセルでき、課金されることはありませんが、自動的にツールへのアクセスは失われます。 有料プランは 14 日間のトライアルの終了時に開始されます。 詳しい情報については、[{% data variables.product.prodname_marketplace %}の支払いについて](/articles/about-billing-for-github-marketplace)を参照してください。 -{% data variables.product.prodname_github_app %} や {% data variables.product.prodname_oauth_app %} は、検証できることも、検証できないこともあります。 検証されたアプリケーションは、{% data variables.product.prodname_dotcom %} が設定した特定の要件を満たし、{% data variables.product.prodname_marketplace %} のリストに載る前にセキュリティレビューを通過しています。 詳しい情報については、「[GitHub Marketplace にアプリケーションを載せるための要件](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)」を参照してください。 +### {% data variables.product.prodname_marketplace %} でツールを見つける -### {% data variables.product.prodname_marketplace %} 上の {% data variables.product.prodname_actions %} +他のユーザが作成したアプリやアクションを {% data variables.product.prodname_marketplace %} で検出、参照、インストールできます。「[{% data variables.product.prodname_marketplace %} を検索する](/github/searching-for-information-on-github/searching-github-marketplace)」を参照してください。 -{% data variables.product.prodname_marketplace %} で他の人が作成した {% data variables.product.prodname_actions %} を検出、参照、インストールできます。詳しくは、「[{% data variables.product.prodname_marketplace %} の検索](/github/searching-for-information-on-github/searching-github-marketplace)」を参照してください。 +{% data reusables.actions.actions-not-verified %} -アクションは誰でも {% data variables.product.prodname_marketplace %} にリストできます。 一部のアプリケーションとは異なり、{% data variables.product.prodname_marketplace %} にリストされた {% data variables.product.prodname_actions %} は、{% data variables.product.prodname_dotcom %} で検証されることはありません。 +誰でも {% data variables.product.prodname_marketplace %} に無料の {% data variables.product.prodname_github_app %} または {% data variables.product.prodname_oauth_app %} をリストできます。 有料アプリケーションのパブリッシャーは {% data variables.product.company_short %} によって検証され、これらのアプリケーションのリストには検証済みの作者バッジ {% octicon "verified" aria-label="Verified creator badge" %} が表示されます。 未検証および検証済みのアプリケーションのバッジも表示されます。 これらのアプリケーションは、個々のアプリケーションを検証する以前の方法を使用して公開されました。 現在のプロセスの詳細については、「[検証済みの作者について](/developers/github-marketplace/about-verified-creators)」および「[アプリケーションを一覧表示するための要件](/developers/github-marketplace/requirements-for-listing-an-app)」を参照してください。 ### {% data variables.product.prodname_marketplace %} でツールを構築およびリストする -{% data variables.product.prodname_marketplace %} にリストする独自のツールを作成する方法の詳細については、「[アプリ](/apps)」および「[{% data variables.product.prodname_actions %}](/actions)」を参照してください。 +{% data variables.product.prodname_marketplace %} にリストする独自のツールを作成する方法の詳細については、「[アプリ](/developers/apps)」および「[{% data variables.product.prodname_actions %}](/actions)」を参照してください。 ### 参考リンク - [{% data variables.product.prodname_marketplace %}でのアプリケーションの購入とインストール](/articles/purchasing-and-installing-apps-in-github-marketplace) - [{% data variables.product.prodname_marketplace %} アプリの支払いを管理する](/articles/managing-billing-for-github-marketplace-apps) - [{% data variables.product.prodname_marketplace %}のサポート](/articles/github-marketplace-support) +- 「[GitHub App と OAuth App の違い](/developers/apps/differences-between-github-apps-and-oauth-apps)」 diff --git a/translations/ja-JP/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md b/translations/ja-JP/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md index 9e9b899aec..e8059cb870 100644 --- a/translations/ja-JP/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md +++ b/translations/ja-JP/content/github/customizing-your-github-workflow/github-extensions-and-integrations.md @@ -10,7 +10,7 @@ versions: ### エディタツール -You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio. +Atom、Unity、Visual Studio などのサードパーティのエディタツール内で {% data variables.product.product_name %} リポジトリに接続できます。 #### {% data variables.product.product_name %} for Atom @@ -30,12 +30,12 @@ You can connect to {% data variables.product.product_name %} repositories within ### プロジェクト管理ツール -You can integrate your {% data variables.product.product_name %} personal account or organization with third-party project management tools, such as Jira or Slack. +{% data variables.product.product_name %} の個人アカウントまたは Organization を Jira や Slack などのサードパーティのプロジェクト管理ツールと統合できます。 #### Jira Cloud と {% data variables.product.product_name %}.com の統合 -Jira Cloud を個人または Organization のアカウントに統合すると、コミットとプルリクエストをスキャンし、メンションされている JIRA の Issue で、関連するメタデータとハイパーリンクを作成できます。 For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace. +Jira Cloud を個人または Organization のアカウントに統合すると、コミットとプルリクエストをスキャンし、メンションされている JIRA の Issue で、関連するメタデータとハイパーリンクを作成できます。 詳細については、Marketplace の[Jira 統合アプリケーション](https://github.com/marketplace/jira-software-github)にアクセスしてください。 -#### Slack and {% data variables.product.product_name %} integration +#### Slack と {% data variables.product.product_name %} の統合 -You can integrate Slack with your personal or organization account to subscribe for notifications, close or open issues, and provide rich references to issues and pull requests without leaving Slack. For more information, visit the [Slack integration app](https://github.com/marketplace/slack-github) in the marketplace. +Slack を個人アカウントまたは Organization アカウントと統合して、通知をサブスクライブし、Issue をクローズまたはオープンして、Slack を離れることなく Issue への豊富なリファレンスとプルリクエストを提供できます。 詳細については、Marketplace の[Slack 統合アプリケーション](https://github.com/marketplace/slack-github)にアクセスしてください。 diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md b/translations/ja-JP/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md index 0871503bf3..920bd242ca 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/about-billing-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: About billing for Codespaces -intro: 'When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage.' +title: Codespaces の支払いについて +intro: '{% data variables.product.prodname_codespaces %} が一般提供されると、ストレージとコンピューティングの使用量に対して課金されます。' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -10,18 +10,18 @@ versions: {% data reusables.codespaces.about-billing-for-codespaces %} -Compute costs are incurred only when a codespace is active. When you're using a codespace, the codespace is active. After 30 minutes of inactivity, a codespace becomes suspended automatically. +計算コストは、Codespaces がアクティブな場合にのみ発生します。 Codespaces を使用している場合、Codespaces はアクティブになっています。 30 分間操作がない場合、Codespaces は自動的に中断されます。 -Compute usage is billed per hour, at a rate that depends on your codespace's instance type. During the beta, {% data variables.product.prodname_codespaces %} offers a single, Linux instance type. At general availability, we'll support three Linux instance types. +コンピューティングの使用量は、Codespaces のインスタンスタイプに応じたレートで、1 時間あたりで課金されます。 ベータ期間中、{% data variables.product.prodname_codespaces %} は単一の Linux インスタンスタイプを提供します。 一般提供時には、3 つの Linux インスタンスタイプをサポートします。 -| Instance Type (Linux) | Per-hour rate | -| --------------------------------------- | ------------- | -| Basic (2 cores, 4GB RAM, 32 GB SSD) | $0.085 | -| Standard (4 cores, 8 GB RAM, 32 GB SSD) | $0.169 | -| Premium (8 cores, 16 GB RAM, 32 GB SSD) | $0.339 | +| インスタンスタイプ (Linux) | 1 時間あたりのレート | +| ---------------------------------- | ----------- | +| Basic (2 コア、4GB RAM、32 GB SSD) | $0.085 | +| Standard (4 コア、8 GB RAM、32 GB SSD) | $0.169 | +| Premium (8 コア、16 GB RAM、32 GB SSD) | $0.339 | -Compute pricing may vary for additional instance types and operating systems supported in the future. +コンピューティングの価格は、将来サポートされる追加のインスタンスタイプとオペレーティングシステムによって異なる場合があります。 -Each codespace also incurs monthly storage costs until you delete the codespace. Storage costs for all instance types are $0.10/GB-month. +各 Codespaces には、Codespaces を削除するまで毎月のストレージコストも発生します。 すべてのインスタンスタイプのストレージコストは、月額 $0.10/GB です。 -We'll share more information about any compute and storage usage included in each plan at general availability. +各プランに含まれるコンピューティングとストレージの使用状況に関する詳細情報は、一般提供時に共有されます。 diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/ja-JP/content/github/developing-online-with-codespaces/about-codespaces.md index 88ceb1b48b..24beb51bc1 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/about-codespaces.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/about-codespaces.md @@ -16,7 +16,7 @@ versions: ### {% data variables.product.prodname_codespaces %} について -{% data variables.product.prodname_codespaces %} is a cloud development environment available in your browser. codespace には、構文の強調表示とオートコンプリートを備えたテキストエディタ、ターミナル、デバッグツール、Git コマンドなど、特定のリポジトリ向けに開発する必要があるすべてのものが {% data variables.product.prodname_dotcom %} 内に含まれています。 codespace に {% data variables.product.prodname_vscode %} 拡張機能をインストールして、機能を追加することもできます。 +{% data variables.product.prodname_codespaces %} は、ブラウザで利用できるクラウド開発環境です。 codespace には、構文の強調表示とオートコンプリートを備えたテキストエディタ、ターミナル、デバッグツール、Git コマンドなど、特定のリポジトリ向けに開発する必要があるすべてのものが {% data variables.product.prodname_dotcom %} 内に含まれています。 codespace に {% data variables.product.prodname_vscode %} 拡張機能をインストールして、機能を追加することもできます。 {% data variables.product.prodname_codespaces %} を使用すると、開発者は簡単に新しい会社へ参加したり、オープンソースプロジェクトへ貢献したりすることができます。 プロジェクトメンテナはリポジトリを設定できるため、リポジトリの codespace を作成すると、プロジェクトの依存関係が自動的に含まれます。 環境設定に費やす時間を削減することで、コーディングをより素早く開始できます。 diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/ja-JP/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md index bee23a000d..6540fba7e1 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -15,15 +15,15 @@ versions: {% data reusables.codespaces.about-configuration %} -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes tools for Node.js, JavaScript, TypeScript, Python, C++, Java, C#, .NET Core, PHP, and PowerShell. For more information about the base Linux image, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) repository. +リポジトリで設定を定義しない場合、{% data variables.product.prodname_dotcom %} はベースの Linux イメージを使用して Codespaces を作成します。 The base Linux image includes tools for Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, PowerShell, Go, Ruby, and Rust. ベースの Linux イメージの詳細については、[`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) リポジトリを参照してください。 {% data reusables.codespaces.about-personalization %}{% data reusables.codespaces.codespace-config-order %}詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)」を参照してください。 プロジェクトタイプ用にビルド済みコンテナ設定を使用してデフォルトの codespace 設定を作成するか、プロジェクトのニーズに固有のカスタム設定を作成できます。 -{% data variables.product.prodname_codespaces %} uses settings contained in a configuration file named `devcontainer.json`. {% data reusables.codespaces.devcontainer-location %} +{% data variables.product.prodname_codespaces %} は、`devcontainer.json` という名前の設定ファイルに含まれている設定を使用します。 {% data reusables.codespaces.devcontainer-location %} -You can use your `devcontainer.json` to set default settings for the entire codespace environment, including the {% data variables.product.prodname_vscode %} editor, but you can also set editor-specific settings in a file named `.vscode/settings.json`. +`devcontainer.json` を使用して、{% data variables.product.prodname_vscode %} エディタを含む Codespaces 環境全体のデフォルト設定を行うことができますが、`.vscode/settings.json` という名前のファイルでエディタ固有の設定を行うこともできます。 リポジトリの codespace 設定への変更は、すべての新しい codespace にのみ適用され、既存の codespace には影響しません。 @@ -40,7 +40,7 @@ You can use your `devcontainer.json` to set default settings for the entire code ### カスタム codespace 設定を作成する -If none of the pre-built configurations meet your needs, you can create a custom configuration by adding a `devcontainer.json` file. {% data reusables.codespaces.devcontainer-location %} +ビルド済みの設定のいずれもニーズを満たさない場合は、`devcontainer.json` ファイルを追加してカスタム設定を作成できます。 {% data reusables.codespaces.devcontainer-location %} このファイルでは、サポートされている設定キーを使用して、codespace の環境の要素を指定できます。たとえば、{% data variables.product.prodname_vscode %} 拡張機能がインストールできます。 diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/developing-in-a-codespace.md b/translations/ja-JP/content/github/developing-online-with-codespaces/developing-in-a-codespace.md index abb4195c3d..3fb6da66c7 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/developing-in-a-codespace.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/developing-in-a-codespace.md @@ -15,29 +15,29 @@ versions: {% data reusables.codespaces.use-chrome %} 詳しい情報については、「[codespace のトラブルシューティング](/github/developing-online-with-codespaces/troubleshooting-your-codespace)」を参照してください。 -### Connecting to a codespace from {% data variables.product.prodname_vscode %} +### {% data variables.product.prodname_vscode %} から Codespaces に接続する {% data reusables.codespaces.connect-to-codespace-from-vscode %} -### Navigating to your codespace +### Codespaces に移動する {% data reusables.codespaces.navigate-to-codespaces %} 2. 開発する codespace の名前をクリックします。 ![codespace の名前](/assets/images/help/codespaces/click-name-codespace.png) -### Forwarding ports +### ポートを転送する -Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 3000, you can access the application from your browser to test and debug it. +ポート転送を使用すると、Codespaces 内で実行されている TCP ポートにアクセスできます。 たとえば、ポート 3000 で Web アプリケーションを実行している場合は、ブラウザからアプリケーションにアクセスして、テストとデバッグを行うことができます。 -When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards those ports. You can click on the URL in the terminal to open it in a browser. For example, if an application outputs `http://127.0.0.1:3000` or `http://localhost:3000` to the console, the log would automatically convert the output to a clickable URL for port 3000. +Codespaces 内で実行されているアプリケーションがポートをコンソールに出力すると、{% data variables.product.prodname_codespaces %} はローカルホストの URL パターンを検出し、それらのポートを自動的に転送します。 ターミナルの URL をクリックすると、ブラウザで開くことができます。 たとえば、アプリケーションが `http://127.0.0.1:3000` または `http://localhost:3000` をコンソールに出力する場合、ログは出力をポート 3000 のクリック可能な URL に自動的に変換します。 -![Automatic Port Forwarding](/assets/images/help/codespaces/automatic-port-forwarding.png) +![自動ポート転送](/assets/images/help/codespaces/automatic-port-forwarding.png) -Alternatively, you can also use any of the following ways to forward a port. +または、次のいずれかの方法を使用してポートを転送することもできます。 -* You can forward a port on demand by triggering the command palette (`shift command P` / `shift control P`) and typing "Codespaces: Forward Port". You can then enter the number of the port you want to forward. +* コマンドパレット (`shift command P` / `shift control P`) をトリガーし、「Codespaces: Forward Port」と入力すると、オンデマンドでポートを転送できます。 次に、転送するポートの番号を入力します。 - ![Command Palette Port Forwarding](/assets/images/help/codespaces/command-palette-port-forwarding.png) + ![コマンドパレットのポート転送](/assets/images/help/codespaces/command-palette-port-forwarding.png) -* You can automatically configure forwarded ports in a `.devcontainer.json` file using the `forwardPorts` property. +* `forwardPorts` プロパティを使用して、`.devcontainer.json` ファイルで転送ポートを自動的に設定できます。 -* You can add or remove forwarded ports within the Remote Explorer extension. From the Remote Explorer you can copy and paste the URLs for forwarded ports, allowing you to access them through your browser. +* Remote Explorer 拡張機能内で転送ポートを追加または削除できます。 Remote Explorer から転送されたポートの URL をコピーして貼り付けることができ、ブラウザからそれらにアクセスできます。 - ![Remote Explorer Port Forwarding](/assets/images/help/codespaces/remote-explorer-port-forwarding.png) + ![リモートエクスプローラのポート転送](/assets/images/help/codespaces/remote-explorer-port-forwarding.png) diff --git a/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md index 5814e4cdc1..645b4afb4a 100644 --- a/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/ja-JP/content/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code.md @@ -1,5 +1,5 @@ --- -title: Using Codespaces in Visual Studio Code +title: Visual Studio Code で Codespaces を使用する intro: '{% data variables.product.product_name %} のアカウントに {% data variables.product.prodname_github_codespaces %} 機能拡張を接続することにより、{% data variables.product.prodname_vscode %} で codespace を直接開発できます。' product: '{% data reusables.gated-features.codespaces %}' redirect_from: @@ -12,33 +12,33 @@ versions: ### 必要な環境 -To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. +{% data variables.product.prodname_vscode %} の Codespaces で直接開発するには、{% data variables.product.prodname_github_codespaces %} 機能拡張にサインインする必要があります。 {% data variables.product.prodname_github_codespaces %} 機能拡張には、{% data variables.product.prodname_vscode %} October 2020 Release 1.51 以降が必要です。 -1. Use the +1. ー -{% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. 詳しい情報については、{% data variables.product.prodname_vscode %} ドキュメントの「[Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)」を参照してください。 +{% data variables.product.prodname_vs %} Marketplace を使用して、[{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 機能拡張をインストールします。 詳しい情報については、{% data variables.product.prodname_vscode %} ドキュメントの「[Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery)」を参照してください。 {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. ![{% data variables.product.prodname_codespaces %} ヘッダ](/assets/images/help/codespaces/codespaces-header-vscode.png) +2. [REMOTE EXPLORER] ドロップダウンを使用して、[**{% data variables.product.prodname_github_codespaces %}**] をクリックします。 ![{% data variables.product.prodname_codespaces %} ヘッダ](/assets/images/help/codespaces/codespaces-header-vscode.png) 3. [**Sign in to view {% data variables.product.prodname_codespaces %}...**] をクリックします。 ![[Signing in to view {% data variables.product.prodname_codespaces %}]](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) 4. {% data variables.product.prodname_vscode %} からの {% data variables.product.product_name %} のアカウントへのアクセスを承認するには、[**Allow**] をクリックします。 5. 機能拡張を承認するには、{% data variables.product.product_name %} にサインインします。 -### Creating a codespace in {% data variables.product.prodname_vscode %} +### {% data variables.product.prodname_vscode %} で Codespaces を作成する -After you connect your {% data variables.product.product_name %} account to the {% data variables.product.prodname_vs_codespaces %} extension, you can develop in a codespace that you created on {% data variables.product.product_name %} or in {% data variables.product.prodname_vscode %}. +{% data variables.product.product_name %} アカウントを {% data variables.product.prodname_vs_codespaces %} 機能拡張に接続した後、{% data variables.product.product_name %} または {% data variables.product.prodname_vscode %} で作成した Codespaces で開発できます。 {% data reusables.codespaces.click-remote-explorer-icon-vscode %} -2. Click the Add icon, then click **Create New Codespace**. ![The Create new Codespace option in {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png) -3. Type, then click the repository's name you want to develop in. ![Searching for repository to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-repository-vscode.png) -4. Click the branch you want to develop on. ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-branch-vscode.png) -5. Click the instance type you want to develop in. ![Instance types for a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-sku-vscode.png) +2. [Add] アイコンをクリックしてから、[**Create New Codespace**] をクリックします。 ![{% data variables.product.prodname_codespaces %} の [Create New Codespace] オプション](/assets/images/help/codespaces/create-codespace-vscode.png) +3. 入力し、開発するリポジトリの名前をクリックします。 ![新しい {% data variables.product.prodname_codespaces %} を作成するためのリポジトリを検索する](/assets/images/help/codespaces/choose-repository-vscode.png) +4. 開発するブランチをクリックします。 ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/choose-branch-vscode.png) +5. 開発するインスタンスタイプをクリックします。 ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png) ### {% data variables.product.prodname_vscode %} で codespace を開く {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. [Codespaces] で、開発する codespace をクリックします。 3. [Connect to Codespace] アイコンをクリックします。 ![{% data variables.product.prodname_vscode %} の [Connect to Codespace] アイコン](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -### Deleting a codespace in {% data variables.product.prodname_vscode %} +### {% data variables.product.prodname_vscode %} で Codespaces を削除する -1. Under Codespaces, right-click the codespace you want to delete. -2. In the drop-down menu, click **Delete Codespace**. ![Deleting a codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png) +1. [Codespaces] で、削除する Codespaces を右クリックします。 +2. ドロップダウンメニューで、[**Delete Codespace**] をクリックします。 ![{% data variables.product.prodname_dotcom %} で Codespaces を削除する](/assets/images/help/codespaces/delete-codespace-vscode.png) 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 bb4fd7472e..17fb8e93ad 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: 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 %}.' +title: Visual Studio で Codespaces を使用する +intro: '{% data variables.product.product_name %} のアカウントに接続することにより、{% data variables.product.prodname_vs %} の Codespaces で直接開発できます。' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -8,50 +8,50 @@ versions: {% note %} -**注釈:** {% data variables.product.prodname_codespaces %} は現在限定パブリックベータであり、変更されることがあります。 ベータ期間中、{% data variables.product.prodname_dotcom %}は{% data variables.product.prodname_codespaces %}の可用性について保証しません。 [Sign up for the limited public beta](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 %}の可用性について保証しません。 [限定パブリックベータにサインアップする](https://github.com/features/codespaces/signup-vs) を参照してください。 ベータへの参加に関する詳しい情報については「[{% data variables.product.prodname_codespaces %}について](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)」を参照してください。 {% endnote %} -### About Codespaces in {% data variables.product.prodname_vs %} +### {% data variables.product.prodname_vs %} の Codespaces について -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. +{% data variables.product.prodname_vs %} で Codespaces を作成して、Windows 環境でアプリケーションを開発できます。 {% data variables.product.prodname_vs %} で Codespaces を使用すると、ソースコードの参照、ソリューションの構築、リポジトリへの変更をコミットできます。 -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 %}. +アプリケーションで使用するには、{% data variables.product.prodname_vs %} で Codespaces を作成する必要があります。 {% data variables.product.prodname_vs %} 外で作成された Codespaces は、現在 {% 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). +{% data variables.product.prodname_vs %} で Codespaces を設定する前に、最新バージョンの [{% 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 %} +#### {% data variables.product.prodname_vs %} と {% 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. +{% data variables.product.prodname_vs %} Preview を使用した {% data variables.product.prodname_github_codespaces %} への接続はデフォルトでは有効になっていないため、最初に [Preview Features] オプションを有効にする必要があります。 -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. +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 %} を再起動する必要があります。 -### Creating a codespace in {% data variables.product.prodname_vs %} +### {% data variables.product.prodname_vs %} で Codespaces を作成する -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) +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. 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) +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) -### Configuring a codespace for {% data variables.product.prodname_vs %} +### {% data variables.product.prodname_vs %} の Codespaces を設定する -A codespace, created with {% data variables.product.prodname_vs %}, can be customized through a new tool called devinit, a command line tool included with {% data variables.product.prodname_vs %}. +{% data variables.product.prodname_vs %} で作成された Codespaces は、{% data variables.product.prodname_vs %} に含まれているコマンドラインツールの devinit という新しいツールを使用してカスタマイズできます。 #### devinit -[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) lets you install additional frameworks and tools into your Windows development codespaces, modify environment variables, and more. +[devinit](https://docs.microsoft.com/visualstudio/devinit/getting-started-with-devinit) を使用すると、Windows の開発 Codespaces への追加のフレームワークとツールのインストールや環境変数の変更などができます。 -devinit supports a configuration file called [devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json). You can add this file to your project if you want to create a customized and repeatable development environment. When you use devinit with a [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) file, your codespaces will be automatically configured on creation. +devinit は、[devinit.json](https://docs.microsoft.com/visualstudio/devinit/devinit-json) という設定ファイルをサポートしています。 カスタマイズされた繰り返し可能な開発環境を作成する場合は、このファイルをプロジェクトに追加します。 [devcontainer.json](https://docs.microsoft.com/visualstudio/ide/codespaces/customize-codespaces#running-devinit-when-creating-a-codespace) ファイルで devinit を使用すると、Codespaces は作成時に自動的に設定されます。 -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). +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)」を参照してください。 diff --git a/translations/ja-JP/content/github/extending-github/getting-started-with-the-api.md b/translations/ja-JP/content/github/extending-github/getting-started-with-the-api.md index 127aee91ce..7b3b8675c8 100644 --- a/translations/ja-JP/content/github/extending-github/getting-started-with-the-api.md +++ b/translations/ja-JP/content/github/extending-github/getting-started-with-the-api.md @@ -14,5 +14,5 @@ API の詳細については、[GitHub REST API](/rest) および [GitHub GraphQ ### 参考リンク -- "[Backing up a repository](/articles/backing-up-a-repository)"{% if currentVersion == "free-pro-team@latest" %} +- 「[リポジトリをバックアップする](/articles/backing-up-a-repository)」{% if currentVersion == "free-pro-team@latest" %} - "[インテグレーションについて](/articles/about-integrations)"{% endif %} diff --git a/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md index 4606a49254..1f385a41ea 100644 --- a/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md +++ b/translations/ja-JP/content/github/extending-github/git-automation-with-oauth-tokens.md @@ -19,7 +19,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} **参考:** -- You must verify your email address before you can create a personal access token. 詳細は「[メールアドレスを検証する](/articles/verifying-your-email-address)」を参照してください。 +- 個人アクセストークンを作成する前に、メールアドレスを確認する必要があります。 詳細は「[メールアドレスを検証する](/articles/verifying-your-email-address)」を参照してください。 - {% data reusables.user_settings.review_oauth_tokens_tip %} {% else %} **ヒント:** {% data reusables.user_settings.review_oauth_tokens_tip %} @@ -33,7 +33,7 @@ versions: {% data reusables.command_line.providing-token-as-password %} -To avoid these prompts, you can use Git password caching. 詳しい情報については、「[Git に GitHub 認証情報をキャッシュする](/github/using-git/caching-your-github-credentials-in-git)」を参照してください。 +これらのプロンプトを回避するには、Git パスワードキャッシュを使用できます。 詳しい情報については、「[Git に GitHub 認証情報をキャッシュする](/github/using-git/caching-your-github-credentials-in-git)」を参照してください。 {% warning %} 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 878369e4a0..309effd0a6 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 @@ -44,11 +44,11 @@ Scanning code when someone pushes a change, and whenever a pull request is creat #### 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)." +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)." #### 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. 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 %} 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)." @@ -148,14 +148,14 @@ jobs: matrix: language: ['javascript', 'python'] ``` - + If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. ```yaml - uses: github/codeql-action/init@v1 with: languages: cpp, csharp, python -``` +``` {% if currentVersion == "free-pro-team@latest" %} ### Analyzing Python dependencies @@ -183,20 +183,20 @@ jobs: - name: Install dependencies run: | python -m pip install --upgrade pip - if [ -f requirements.txt ]; + if [ -f requirements.txt ]; then pip install -r requirements.txt; fi # Set the `CODEQL-PYTHON` environment variable to the Python executable # that includes the dependencies - echo "::set-env name=CODEQL_PYTHON::$(which python)" + echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV - name: Initialize CodeQL uses: github/codeql-action/init@v1 with: languages: python - # Override the default behavior so that the action doesn't attempt + # Override the default behavior so that the action doesn't attempt # to auto-install Python dependencies setup-python-dependencies: false -``` +``` {% endif %} ### Running additional queries @@ -239,7 +239,7 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp ``` The configuration file can be located within the local repository, or in a public, remote repository. For remote repositories, you can use the _owner/repository/file.yml@branch_ syntax. The settings in the file are written in YAML format. - + #### Specifying additional queries 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. @@ -265,15 +265,15 @@ For the interpreted languages that {% data variables.product.prodname_codeql %} ``` yaml paths: - - src -paths-ignore: + - src +paths-ignore: - src/node_modules - '**/*.test.js' ``` {% note %} -**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. @@ -298,7 +298,7 @@ You can quickly analyze small portions of a monorepo when you modify code in spe 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 `github/foo`, `github/bar`, and `github/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. +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 @@ -307,9 +307,9 @@ steps: env: TOKEN: ${{ secrets.ACCESS_TOKEN }} run: | - git config --global url."https://${TOKEN}@github.com/github/foo".insteadOf "https://github.com/github/foo" - git config --global url."https://${TOKEN}@github.com/github/bar".insteadOf "https://github.com/github/bar" - git config --global url."https://${TOKEN}@github.com/github/baz".insteadOf "https://github.com/github/baz" + 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 %} diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md index ec7563654b..c9b202f65e 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md @@ -21,7 +21,7 @@ You must run {% data variables.product.prodname_codeql %} in the same container You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations: * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* MacOS: https://github.com/actions/virtual-environments/tree/main/images/macos +* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos * Windows: https://github.com/actions/virtual-environments/tree/main/images/win ### Example workflow diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 78adfe31ce..3a60666faf 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -40,7 +40,7 @@ On Linux: chmod +x codeql-runner-linux ``` -macOSの場合: +macOS: ```shell chmod +x codeql-runner-macos diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 023a599822..c17ad6e046 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -107,13 +107,13 @@ You can check a SARIF file is compatible with {% data variables.product.prodname #### `physicalLocation` オブジェクト -| 名前 | 説明 | -| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `artifactLocation.uri` | **必須。**アーティファクトの場所を示す URI（通常はリポジトリ内のファイル、またはビルド中に生成されたファイル）。 URI が相対の場合、分析されている {% data variables.product.prodname_dotcom %} リポジトリのルートに相対である必要があります。 たとえば、main.js または src/script.js は、リポジトリのルートを基準にしています。 URI が絶対の場合、{% data variables.product.prodname_code_scanning %} は URI を使用してアーティファクトをチェックアウトし、リポジトリ内のファイルを照合できます。 例: `https://github.com/github/example/blob/00/src/promiseUtils.js` | -| `region.startLine` | **必須。**リージョンの最初の文字の行番号。 | -| `region.startColumn` | **必須。**リージョンの最初の文字の列番号。 | -| `region.endLine` | **必須。**リージョンの最後の文字の行番号。 | -| `region.endColumn` | **必須。**リージョンの末尾に続く文字の列番号。 | +| 名前 | 説明 | +| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `artifactLocation.uri` | **必須。**アーティファクトの場所を示す URI（通常はリポジトリ内のファイル、またはビルド中に生成されたファイル）。 URI が相対の場合、分析されている {% data variables.product.prodname_dotcom %} リポジトリのルートに相対である必要があります。 たとえば、main.js または src/script.js は、リポジトリのルートを基準にしています。 URI が絶対の場合、{% data variables.product.prodname_code_scanning %} は URI を使用してアーティファクトをチェックアウトし、リポジトリ内のファイルを照合できます。 For example, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. | +| `region.startLine` | **必須。**リージョンの最初の文字の行番号。 | +| `region.startColumn` | **必須。**リージョンの最初の文字の列番号。 | +| `region.endLine` | **必須。**リージョンの最後の文字の行番号。 | +| `region.endColumn` | **必須。**リージョンの末尾に続く文字の列番号。 | ### SARIF 出力ファイルの例 diff --git a/translations/ja-JP/content/github/getting-started-with-github/access-permissions-on-github.md b/translations/ja-JP/content/github/getting-started-with-github/access-permissions-on-github.md index 60f3e29aef..1fdc2f0e2d 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/access-permissions-on-github.md +++ b/translations/ja-JP/content/github/getting-started-with-github/access-permissions-on-github.md @@ -18,7 +18,7 @@ versions: ### 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{% if currentVersion == "free-pro-team@latest" %}, while billing managers can manage billing settings{% endif %}. メンバーは、その他の人のデフォルトのロールです。 Team を使って、複数のメンバーのアクセス権限を一度に管理できます。 詳しい情報については、以下を参照してください。 +Organization のメンバーは、*owner* (オーナー){% if currentVersion == "free-pro-team@latest" %}、*billing manager* (支払いマネージャー)、{% endif %}あるいは *member* (メンバー) ロールを保持することができます。 オーナーは、Organization に対する完全な管理者アクセスを持ち{% if currentVersion == "free-pro-team@latest" %}、支払いマネージャーは支払いの設定を管理できます{% endif %}。 メンバーは、その他の人のデフォルトのロールです。 Team を使って、複数のメンバーのアクセス権限を一度に管理できます。 詳しい情報については、以下を参照してください。 - 「[Organization の権限レベル](/articles/permission-levels-for-an-organization)」 - [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization) - [Organization のリポジトリ権限レベル](/articles/repository-permission-levels-for-an-organization) @@ -28,7 +28,7 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late ### Enterprise アカウント -*Enterprise のオーナー*は、Enterprise アカウントに対して最大の力を持ち、Enterprise アカウントであらゆるアクションを取ることができます。 *支払いマネージャー*は、Enterprise アカウントの支払い設定を管理できます。 Enterprise アカウントが所有する Organization のメンバーと外部コラボレーターは、自動的に Enterprise アカウントのメンバーになりますが、Enterprise アカウントそのものやその設定にはアクセスできません。 For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +*Enterprise のオーナー*は、Enterprise アカウントに対して最大の力を持ち、Enterprise アカウントであらゆるアクションを取ることができます。 *支払いマネージャー*は、Enterprise アカウントの支払い設定を管理できます。 Enterprise アカウントが所有する Organization のメンバーと外部コラボレーターは、自動的に Enterprise アカウントのメンバーになりますが、Enterprise アカウントそのものやその設定にはアクセスできません。 詳しい情報については、「[Enterprise アカウントのロール](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)」を参照してください。 {% data reusables.gated-features.enterprise-accounts %} diff --git a/translations/ja-JP/content/github/getting-started-with-github/be-social.md b/translations/ja-JP/content/github/getting-started-with-github/be-social.md index 64d2794a36..62c4a8095c 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/be-social.md +++ b/translations/ja-JP/content/github/getting-started-with-github/be-social.md @@ -22,7 +22,7 @@ versions: ### リポジトリを Watch する -リポジトリを Watch して、新しいプルリクエストと Issue に関する通知を受け取ることができます。 オーナーがリポジトリを更新すると、個人ダッシュボード上で変更を見ることができます。 For more information see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}." +リポジトリを Watch して、新しいプルリクエストと Issue に関する通知を受け取ることができます。 オーナーがリポジトリを更新すると、個人ダッシュボード上で変更を見ることができます。 詳しい情報については、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)」{% else %}「[リポジトリの Watch と Watch 解除](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)」を参照してください{% endif %}。 リポジトリを Watch するには、リポジトリの上部で [**Watch**] をクリックします。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/create-a-repo.md b/translations/ja-JP/content/github/getting-started-with-github/create-a-repo.md index 2b835092e7..00c80b6e59 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/create-a-repo.md +++ b/translations/ja-JP/content/github/getting-started-with-github/create-a-repo.md @@ -16,7 +16,7 @@ versions: {% elsif enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." +インナーソースプロジェクトを含め、さまざまなプロジェクトを {% data variables.product.product_name %} リポジトリに保存できます。 インナーソースを使用すると、コードを共有して、より優れた、より信頼性の高いソフトウェアを作成できます。 インナーソースの詳細については、{% data variables.product.company_short %} のホワイトペーパー「[インナーソース入門](https://resources.github.com/whitepapers/introduction-to-innersource/)」を参照してください。 {% endif %} @@ -32,8 +32,8 @@ You can store a variety of projects in {% data variables.product.product_name %} {% data reusables.repositories.create_new %} 2. リポジトリに、短くて覚えやすい名前を入力します。 たとえば、"hello-world" といった名前です。 ![リポジトリ名を入力するフィールド](/assets/images/help/repository/create-repository-name.png) -3. 必要な場合、リポジトリの説明を追加します。 For example, "My first repository on -{% data variables.product.product_name %}." +3. 必要な場合、リポジトリの説明を追加します。 たとえば、「 +{% data variables.product.product_name %} の最初のリポジトリ」などです。 ![リポジトリの説明を入力するフィールド](/assets/images/help/repository/create-repository-desc.png) {% data reusables.repositories.choose-repo-visibility %} {% data reusables.repositories.initialize-with-readme %} @@ -44,7 +44,7 @@ You can store a variety of projects in {% data variables.product.product_name %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% tip %} -**Tip**: You can also create repositories using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. +**ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリを作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo create`](https://cli.github.com/manual/gh_repo_create)」を参照してください。 {% endtip %} {% endif %} diff --git a/translations/ja-JP/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md b/translations/ja-JP/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md index 3d79395b9a..9407eb6ae8 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md +++ b/translations/ja-JP/content/github/getting-started-with-github/faq-about-changes-to-githubs-plans.md @@ -83,8 +83,8 @@ GitHub コミュニティサポートには、[コミュニティフォーラム 現在請求書をご利用の場合は、詳細について営業担当者にメールでお問い合わせください。 営業担当者が不明な場合は、支払いマネージャーまたはアカウント所有者にお問い合わせください。 -### 米国政府の制裁が適用される地域のユーザと Organization にどのように影響しますか？ government sanctions are applied? +### 米国政府の制裁が適用される地域のユーザと Organization にどのように影響しますか？ - -Due to U.S. 米国の貿易管理法の制限により、GitHub は米国の制裁対象地域のアカウントにプライベートリポジトリサービスと有料サービスを提供できません。 sanctioned regions. ただし、GitHub は無料の公開リポジトリサービスへのアクセスを保持しています。 詳細については、「[GitHub と貿易管理](/github/site-policy/github-and-trade-controls)」をご覧ください。 +- 米国の貿易管理法の制限により、GitHub は米国の制裁対象地域のアカウントにプライベートリポジトリサービスと有料サービスを提供できません。 - ただし、GitHub は無料の公開リポジトリサービスへのアクセスを保持しています。 詳細については、「[GitHub と貿易管理](/github/site-policy/github-and-trade-controls)」をご覧ください。 -GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. +GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 - 当社は、これらの無料サービスを提供することが、 各地域での情報の自由な流れと言論の自由を奨励するという米国の外交政策をサポートすることに繋がると信じています。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/ja-JP/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md index 7ba18b75ad..61ea0abb63 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/ja-JP/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -32,14 +32,14 @@ versions: {% data variables.product.prodname_dotcom_the_website %} にミラーされている有名なリポジトリを以下に挙げます: -- [Android Open Source Project](https://github.com/aosp-mirror) +- [Android オープンソースプロジェクト](https://github.com/aosp-mirror) - [The Apache Software Foundation](https://github.com/apache) - [The Chromium Project](https://github.com/chromium) - [Eclipse Foundation](https://github.com/eclipse) - [The FreeBSD Project](https://github.com/freebsd) - [Glasgow Haskell Compiler](https://github.com/ghc) - [GNOME](https://github.com/GNOME) -- [Linux kernel source tree](https://github.com/torvalds/linux) +- [Linux カーネルソースツリー](https://github.com/torvalds/linux) - [Qt](https://github.com/qt) 独自のミラーを設定するために、公式のプロジェクトリポジトリに [post-receive フック](https://git-scm.com/book/en/Customizing-Git-Git-Hooks)を設定して、コミットを {% data variables.product.product_name %} 上にミラーされたリポジトリに自動的にプッシュするようにできます。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/following-people.md b/translations/ja-JP/content/github/getting-started-with-github/following-people.md index c5befdb873..bc122e9f60 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/following-people.md +++ b/translations/ja-JP/content/github/getting-started-with-github/following-people.md @@ -1,6 +1,6 @@ --- title: 人をフォローする -intro: 'You can follow people on {% data variables.product.product_name %} to receive notifications about their activity{% if currentVersion == "free-pro-team@latest" %} and discover projects in their communities{% endif %}.' +intro: '{% data variables.product.product_name %} のユーザをフォローして、アクティビティに関する通知を受け取ることができます。{% if currentVersion == "free-pro-team@latest" %}また、それらのユーザのコミュニティ内でプロジェクトを見つけることもできます。{% endif %}' redirect_from: - /articles/following-people versions: @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -When you follow people, you'll see their public activity in the activity view of your news feed.{% if currentVersion == "free-pro-team@latest" %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you in the discovery view of your news feed.{% endif %} To follow someone, visit their profile page and click **Follow** under their profile image. +ユーザをフォローすると、ニュースフィードのアクティビティビューに、公開されたアクティビティが表示されます。{% if currentVersion == "free-pro-team@latest" %}フォローしているユーザがパブリックリポジトリに Star を付けると、ニュースフィードのディスカバリービューで {% data variables.product.product_name %} によっておすすめのリポジトリが紹介されます。{% endif %}ユーザをフォローするには、ユーザのプロフィールページにアクセスし、プロフィール画像の下にある [**Follow**] をクリックします。 ![ユーザのフォローボタン](/assets/images/help/profile/follow-user-button.png) diff --git a/translations/ja-JP/content/github/getting-started-with-github/fork-a-repo.md b/translations/ja-JP/content/github/getting-started-with-github/fork-a-repo.md index 20c6a8f76c..f9b7cf54a6 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/fork-a-repo.md +++ b/translations/ja-JP/content/github/getting-started-with-github/fork-a-repo.md @@ -19,13 +19,13 @@ versions: - リポジトリをフォークする。 - 修正する。 -- Submit a pull request to the project owner. +- プロジェクトのオーナーにプルリクエストを送信する。 #### 他のユーザのプロジェクトを自分のアイディアの出発点として活用する。 オープンソースソフトウェアは、コードを共有することで、より優れた、より信頼性の高いソフトウェアを作成可能にするという考えに基づいています。 詳しい情報については、Open Source Initiative の「[Open Source Initiative について](http://opensource.org/about)」を参照してください。 -For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." +{% data variables.product.product_location %} に関する Organization の開発作業にオープンソースの原則を適用する方法の詳細については、{% data variables.product.prodname_dotcom %} のホワイトペーパー「[インナーソース入門](https://resources.github.com/whitepapers/introduction-to-innersource/)」を参照してください。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} @@ -44,7 +44,7 @@ For more information about applying open source principles to your organization' {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} {% tip %} -**Tip**: You can also fork a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo fork`](https://cli.github.com/manual/gh_repo_fork)" in the {% data variables.product.prodname_cli %} documentation. +**ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリをフォークすることもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo fork`](https://cli.github.com/manual/gh_repo_fork)」を参照してください。 {% endtip %} {% endif %} @@ -66,11 +66,11 @@ For more information about applying open source principles to your organization' #### ステップ 2: フォークのローカルクローンを作成する -今、Spoon-Knife リポジトリのフォークがありますが、お使いのコンピュータにはそのリポジトリ内のファイルはありません。 Let's create a clone of your fork locally on your computer. +今、Spoon-Knife リポジトリのフォークがありますが、お使いのコンピュータにはそのリポジトリ内のファイルはありません。 コンピューター上でローカルにフォークのクローンを作成しましょう。 1. On -{% data variables.product.product_name %}, navigate to **your fork** of the Spoon-Knife repository. +{% data variables.product.product_name %} で、Spoon-Knife リポジトリの**自分のフォーク**に移動します。 {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} @@ -97,7 +97,7 @@ Spoon-Knife リポジトリのフォークのローカルのコピーができ 1. On -{% data variables.product.product_name %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. +{% data variables.product.product_name %} で、[octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) リポジトリに移動します。 {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} 4. ディレクトリを、「[ステップ 2: フォークのローカルクローンを作成する](#step-2-create-a-local-clone-of-your-fork)」でクローンしたフォークの場所に変更します。 @@ -139,7 +139,7 @@ Spoon-Knife リポジトリのフォークのローカルのコピーができ リポジトリをフォークしてプロジェクトへのコントリビューションを開始しましょう。 {% data reusables.repositories.you-can-fork %} -{% if currentVersion == "free-pro-team@latest" %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. 詳しい情報については、「[{% data variables.product.prodname_dotcom %} でオープンソースにコントリビュートする方法を見つける](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" %}[Explore](https://github.com/explore) でプロジェクトを探してオープンソースのリポジトリへのコントリビューションを開始できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} でオープンソースにコントリビュートする方法を見つける](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/ja-JP/content/github/getting-started-with-github/git-and-github-learning-resources.md index c9883267d3..f2773acb76 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/ja-JP/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +authors: + - GitHub --- ### Git を使用する @@ -55,6 +57,6 @@ versions: [Code School](http://codeschool.com) によるインタラクティブな[オンラインの Git コース](http://www.codeschool.com/courses/git-real)では、数十の楽しいゲーム形式のエクササイズを含む 7 段階のサービスを提供しています。 [.gitignore テンプレート](https://github.com/github/gitignore)では、お客様のニーズに合わせることができます。 -Extend your {% data variables.product.prodname_dotcom %} reach through {% if currentVersion == "free-pro-team@latest" %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [Atom](https://atom.io) text editor. +{% data variables.product.prodname_dotcom %} のリーチを、{% if currentVersion == "free-pro-team@latest" %}[インテグレーション](/articles/about-integrations){% else %}インテグレーション{% endif %}、または[{% data variables.product.prodname_desktop %}](https://desktop.github.com) と堅牢な [Atom](https://atom.io) テキストエディタで拡張しましょう。 [オープンソースのガイド](https://opensource.guide/)で、オープンソースのプロジェクトを立ち上げ成長させる方法をご確認ください。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-cli.md b/translations/ja-JP/content/github/getting-started-with-github/github-cli.md index 41a89fc4c4..60bb97957d 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/github-cli.md +++ b/translations/ja-JP/content/github/getting-started-with-github/github-cli.md @@ -1,6 +1,6 @@ --- title: GitHub CLI -intro: 'The {% data variables.product.prodname_cli %} is a command-line tool for using {% data variables.product.product_name %} features on your computer.' +intro: '{% data variables.product.prodname_cli %} は、コンピューターで {% data variables.product.product_name %} 機能を使用するためのコマンドラインツールです。' versions: free-pro-team: '*' enterprise-server: '>2.19' @@ -9,14 +9,14 @@ versions: ### {% data variables.product.prodname_cli %} について -{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.product_name %} from your computer's command line. When you're working from the command line, you can use the {% data variables.product.prodname_cli %} to save time and avoid switching context. +{% data variables.product.prodname_cli %} は、コンピューターのコマンドラインから {% data variables.product.product_name %} を使用するためのオープンソースツールです。 コマンドラインから作業しているときは、{% data variables.product.prodname_cli %} を使用して時間を節約し、コンテキストの切り替えを回避できます。 -You can use the following {% data variables.product.prodname_dotcom %} features with the {% data variables.product.prodname_cli %}. +次の {% data variables.product.prodname_dotcom %} 機能を {% data variables.product.prodname_cli %} で使用できます。 -- View, create, clone, and fork repositories -- Create, close, and list issues and pull requests -- Review, diff, and merge pull requests -- Create, edit, list, and view gists +- リポジトリの表示、作成、複製、フォーク +- Issue とプルリクエストの作成、クローズ、リスト表示 +- プルリクエストのレビュー、diff、マージ +- Gist の作成、編集、リスト表示、表示 {% data variables.product.prodname_cli %} でできることの詳細については、[{% data variables.product.prodname_cli %} マニュアル](https://cli.github.com/manual) を参照してください。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-desktop.md b/translations/ja-JP/content/github/getting-started-with-github/github-desktop.md index dc24cede50..fcd76328ea 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/github-desktop.md +++ b/translations/ja-JP/content/github/getting-started-with-github/github-desktop.md @@ -11,7 +11,7 @@ versions: {% data reusables.desktop.about-github-desktop %} -For more information about {% data variables.product.prodname_desktop %}, see "[Installing and configuring {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop)" in the {% data variables.product.prodname_desktop %} documentation. +{% data variables.product.prodname_desktop %} の詳細については、{% data variables.product.prodname_desktop %} ドキュメントの「[{% data variables.product.prodname_desktop %} のインストールと設定](/desktop/installing-and-configuring-github-desktop)」を参照してください。 ### フィードバックを送る diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md b/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md index b609e4f5f0..e028a76373 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/ja-JP/content/github/getting-started-with-github/github-for-mobile.md @@ -23,15 +23,15 @@ versions: Android または iOS に {% data variables.product.prodname_mobile %} をインストールするには、「[{% data variables.product.prodname_mobile %}](https://github.com/mobile)」を参照してください。 -### Supported languages for {% data variables.product.prodname_mobile %} +### {% data variables.product.prodname_mobile %} でサポートされている言語 -{% data variables.product.prodname_mobile %} is available in the following languages. +{% data variables.product.prodname_mobile %} は次の言語で利用できます。 - 日本語 -- Brazilian Portuguese +- ポルトガル語 (ブラジル) - スペイン語 -If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. +デバイスの言語をサポートされている言語に設定すると、{% data variables.product.prodname_mobile %} はデフォルトでその言語になります。 {% data variables.product.prodname_mobile %} の [**Settings**] メニューで {% data variables.product.prodname_mobile %} の言語を変更できます。 ### iOS で {% data variables.product.prodname_mobile %} のユニバーサルリンクを管理する @@ -43,9 +43,9 @@ If you configure the language on your device to a supported language, {% data va ### フィードバックを送る -If you find a bug in {% data variables.product.prodname_mobile %}, you can email us at mobilefeedback@github.com. +{% data variables.product.prodname_mobile %} でバグを見つけた場合は、mobilefeedback@github.com までメールでお知らせください。 -You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} [on GitHub Discussions](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). +[GitHub Discussions](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22) で {% data variables.product.prodname_mobile %} の機能リクエストやその他のフィードバックを送信できます。 ### iOS のベータリリースをオプトアウトする diff --git a/translations/ja-JP/content/github/getting-started-with-github/github-glossary.md b/translations/ja-JP/content/github/getting-started-with-github/github-glossary.md index 6e2e1238cf..a18e1dcb5b 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/github-glossary.md +++ b/translations/ja-JP/content/github/getting-started-with-github/github-glossary.md @@ -10,8 +10,8 @@ versions: --- {% for term in site.data.glossaries.external %} - ### {{term.term}} - {{term.description}} + ### {% data glossaries.external[forloop.index0].term %} + {% data glossaries.external[forloop.index0].description %} --- {% endfor %} 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 89333a770e..e3bca9f5cf 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 @@ -97,7 +97,7 @@ Organizationの{% data variables.product.prodname_free_team %}で利用できる - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" and "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning) (beta)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (beta)."{% endif %} +- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)」および「[{% data variables.product.prodname_secret_scanning %}について](/github/administering-a-repository/about-secret-scanning) (ベータ)」を参照してください。{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}。 詳しい情報については、「[{% data variables.product.prodname_code_scanning %} について](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (ベータ)」を参照してください。{% endif %} - [Organization の {% data variables.product.prodname_learning %}](https://lab.github.com/organizations) {% data variables.product.prodname_ghe_one %} へのサインアップの詳細については、[{% data variables.product.product_name %} の販売チーム](https://enterprise.github.com/contact)にお問い合わせください。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/index.md b/translations/ja-JP/content/github/getting-started-with-github/index.md index 8500013ff2..0ea87e1cc3 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/index.md +++ b/translations/ja-JP/content/github/getting-started-with-github/index.md @@ -27,37 +27,27 @@ versions: {% link_in_list /fork-a-repo %} {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} - {% link_in_list /githubs-products %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} - {% link_in_list /types-of-github-accounts %} - {% link_in_list /faq-about-changes-to-githubs-plans %} {% link_in_list /github-cli %} {% link_in_list /github-desktop %} {% link_in_list /github-for-mobile %} - {% link_in_list /access-permissions-on-github %} {% link_in_list /github-glossary %} {% link_in_list /git-cheatsheet %} {% link_in_list /git-and-github-learning-resources %} {% topic_link_in_list /signing-up-for-github %} - {% link_in_list /signing-up-for-a-new-github-account %} {% link_in_list /verifying-your-email-address %} - {% link_in_list /setting-up-a-trial-of-github-enterprise-cloud %} {% link_in_list /setting-up-a-trial-of-github-enterprise-server %} {% topic_link_in_list /exploring-projects-on-github %} - {% link_in_list /finding-ways-to-contribute-to-open-source-on-github %} - {% link_in_list /saving-repositories-with-stars %} {% link_in_list /following-people %} {% topic_link_in_list /using-github %} {% link_in_list /supported-browsers %} - {% link_in_list /troubleshooting-connectivity-problems %} - {% link_in_list /keyboard-shortcuts %} diff --git a/translations/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 c19aaf6ef0..18cc715585 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 @@ -21,22 +21,22 @@ versions: ### サイト全体のショートカット -| キーボードショートカット | 説明 | -| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s または / | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/articles/about-searching-on-github)」を参照してください。 | -| g n | 通知に移動します。 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 | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします | +| キーボードショートカット | 説明 | +| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| s または / | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/articles/about-searching-on-github)」を参照してください。 | +| g n | 通知に移動します。 詳しい情報については、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」{% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications)」を参照してください{% endif %}。 | +| esc | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします | ### リポジトリ -| キーボードショートカット | 説明 | -| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | [**Code**] タブに移動します | -| g i | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 | -| g p | [**Pull requests**] タブに移動します。 For more information, see "[About pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| 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 | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 | -| g w | [**Wiki**] タブに移動します。 詳細は「[ウィキについて](/articles/about-wikis)」を参照してください。 | +| キーボードショートカット | 説明 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| g c | [**Code**] タブに移動します | +| g i | [**Issues**] タブに移動します。 詳細は「[Issue について](/articles/about-issues)」を参照してください。 | +| g p | [**Pull requests**] タブに移動します。 詳しい情報については、「[プルリクエストについて](/articles/about-pull-requests)」を参照してください。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| g a | [**Actions**] タブに移動します。 詳しい情報については、「[アクションについて](/actions/getting-started-with-github-actions/about-github-actions)」を参照してください。{% endif %} +| g b | [**Projects**] タブに移動します。 詳細は「[プロジェクトボードについて](/articles/about-project-boards)」を参照してください。 | +| g w | [**Wiki**] タブに移動します。 詳細は「[ウィキについて](/articles/about-wikis)」を参照してください。 | ### ソースコード編集 @@ -68,16 +68,16 @@ versions: ### コメント -| キーボードショートカット | 説明 | -| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| control b または command b | 太字テキストの Markdown 書式を挿入します | -| control i または command i | イタリック体のテキストの Markdown 書式を挿入します | -| control k または command k | リンクを作成するための Markdown 書式を挿入します | -| control shift p または command shift p | **Write** と **Preview** のコメントタブを切り替えます。 | -| control enter | コメントをサブミットします | -| control .、次に control [返信テンプレート番号] | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} +| キーボードショートカット | 説明 | +| --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| control b または command b | 太字テキストの Markdown 書式を挿入します | +| control i または command i | イタリック体のテキストの Markdown 書式を挿入します | +| control k または command k | リンクを作成するための Markdown 書式を挿入します | +| control shift p または command shift p | **Write** と **Preview** のコメントタブを切り替えます。 | +| control enter | コメントをサブミットします | +| control .、次に control [返信テンプレート番号] | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳しい情報については「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% if currentVersion == "free-pro-team@latest" %} | control g または command g | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/articles/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 |{% endif %} -| r | 返信で選択したテキストを引用します。 詳細は「[基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)」を参照してください。 | +| r | 返信で選択したテキストを引用します。 詳細は「[基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)」を参照してください。 | ### Issue およびプルリクエストのリスト @@ -103,91 +103,91 @@ versions: ### プルリクエストの変更 -| キーボードショートカット | 説明 | -| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | プルリクエスト内のコミットのリストを開きます | -| t | プルリクエストで変更されたファイルのリストを開きます | -| j | リストで選択を下に移動します | -| k | リストで選択を上に移動します | -| cmd + shift + enter | プルリクエストの差分にコメントを 1 つ追加します | -| alt およびクリック | 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" %} +| キーボードショートカット | 説明 | +| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| c | プルリクエスト内のコミットのリストを開きます | +| t | プルリクエストで変更されたファイルのリストを開きます | +| j | リストで選択を下に移動します | +| k | リストで選択を上に移動します | +| cmd + shift + enter | プルリクエストの差分にコメントを 1 つ追加します | +| alt およびクリック | `alt` キーを押しながら [**Show outdated**] または [**Hide outdated**] をクリックして、プルリクエスト内のすべての古いレビューコメントの折りたたみと展開を切り替えます。|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | クリック後、shift およびクリック | プルリクエストの複数行にコメントするには、行番号をクリックし、shift を押したまま、別の行番号をクリックします。 詳しい情報については、「[プルリクエストへコメントする](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)」を参照してください。|{% endif %} ### プロジェクトボード #### 列を移動する -| キーボードショートカット | 説明 | -| ------------------------------------------------------------------------------------------------ | ----------------- | -| enter または space | フォーカスされた列を動かし始めます | -| escape | 進行中の移動をキャンセルします | -| enter | 進行中の移動を完了します | -| ← または h | 左に列を移動します | -| command ← または command h あるいは control ← または control h | 左端に列を移動します | -| → または l | 右に列を移動します | -| command → または command l あるいは control → または control l | 右端に列を移動します | +| キーボードショートカット | 説明 | +| ------------------------------------------------------------------------------------------------------- | ----------------- | +| enter または space | フォーカスされた列を動かし始めます | +| escape | 進行中の移動をキャンセルします | +| enter | 進行中の移動を完了します | +| ← または h | 左に列を移動します | +| command + ← または command + h または control + ← または control + h | 左端に列を移動します | +| → または l | 右に列を移動します | +| command + → または command + l または control + → または control + l | 右端に列を移動します | #### カードを移動する -| キーボードショートカット | 説明 | -| ------------------------------------------------------------------------------------------------------------------------ | ------------------- | -| enter または space | フォーカスされたカードを動かし始めます | -| escape | 進行中の移動をキャンセルします | -| enter | 進行中の移動を完了します | -| ↓ または j | カードを下に移動します | -| command ↓ または command j あるいは control ↓ または control j | カードを列の一番下に移動します | -| ↑ または k | カードを上に移動します | -| command ↑ または command k あるいは control ↑ または control k | カードを列の一番上に移動します | -| ← または h | カードを左側の列の一番下に移動します | -| shift ← または shift h | カードを左側の列の一番上に移動します | -| command ← または command h あるいは control ← または control h | カードを一番左の列の一番下に移動します | -| command shift ← または command shift h あるいは control shift ← または control shift h | カードを一番左の列の一番上に移動します | -| → | カードを右側の列の一番下に移動します | -| shift → または shift l | カードを右側の列の一番上に移動します | -| command → または command l あるいは control → または control l | カードを一番右の列の一番下に移動します | -| command shift → または command shift l あるいは control shift → または control shift l | カードを一番右の列の一番下に移動します | +| キーボードショートカット | 説明 | +| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | +| enter または space | フォーカスされたカードを動かし始めます | +| escape | 進行中の移動をキャンセルします | +| enter | 進行中の移動を完了します | +| ↓ または j | カードを下に移動します | +| command + ↓ または command + j または control + ↓ または control + j | カードを列の一番下に移動します | +| ↑ または k | カードを上に移動します | +| command + ↑ または command + k または control + ↑ または control + k | カードを列の一番上に移動します | +| ← または h | カードを左側の列の一番下に移動します | +| shift + ← または shift + h | カードを左側の列の一番上に移動します | +| command + ← または command + h または control + ← または control + h | カードを一番左の列の一番下に移動します | +| command + shift + ← または command + shift + h または control + shift + ← または control + shift + h | カードを一番左の列の一番上に移動します | +| → | カードを右側の列の一番下に移動します | +| shift + → または shift + l | カードを右側の列の一番上に移動します | +| command + → または command + l または control + → または control + l | カードを一番右の列の一番下に移動します | +| command + shift + → または command + shift + l または control + shift + → または control + shift + l | カードを一番右の列の一番下に移動します | -#### Previewing a card +#### カードをプレビューする -| キーボードショートカット | 説明 | -| -------------- | --------------------------- | -| esc | Close the card preview pane | +| キーボードショートカット | 説明 | +| -------------- | ---------------- | +| esc | カードのプレビューペインを閉じる | {% if currentVersion == "free-pro-team@latest" %} ### {% data variables.product.prodname_actions %} -| キーボードショートカット | 説明 | -| ------------------------------------------------------ | ------------------------------------ | -| command space または control space | ワークフローエディターで、ワークフローファイルに対する提案を取得します。 | +| キーボードショートカット | 説明 | +| ---------------------------------------------------------- | ------------------------------------ | +| command + space または control + space | ワークフローエディターで、ワークフローファイルに対する提案を取得します。 | {% endif %} ### 通知 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| キーボードショートカット | 説明 | -| ------------------ | ------------ | -| e | 完了済としてマークします | -| shift u | 未読としてマークします | -| shift i | 既読としてマークします | -| shift m | サブスクライブ解除します | +| キーボードショートカット | 説明 | +| -------------------- | ------------ | +| e | 完了済としてマークします | +| shift + u | 未読としてマークします | +| shift + i | 既読としてマークします | +| shift + m | サブスクライブ解除します | {% else %} | キーボードショートカット | 説明 | | ---------------------------------------------- | ------------ | | e または I または y | 既読としてマークします | -| shift m | スレッドをミュートします | +| shift + m | スレッドをミュートします | {% endif %} ### ネットワークグラフ -| キーボードショートカット | 説明 | -| ----------------------------------------- | ------------ | -| ← または h | 左にスクロールします | -| → または l | 右にスクロールします | -| ↑ または k | 上にスクロールします | -| ↓ または j | 下にスクロールします | -| shift ← または shift h | 左端までスクロールします | -| shift → または shift l | 右端までスクロールします | -| shift ↑ または shift k | 上端までスクロールします | -| shift ↓ または shift j | 下端までスクロールします | +| キーボードショートカット | 説明 | +| --------------------------------------------- | ------------ | +| ← または h | 左にスクロールします | +| → または l | 右にスクロールします | +| ↑ または k | 上にスクロールします | +| ↓ または j | 下にスクロールします | +| shift + ← または shift + h | 左端までスクロールします | +| shift + → または shift + l | 右端までスクロールします | +| shift + ↑ または shift + k | 上端までスクロールします | +| shift + ↓ または shift + j | 下端までスクロールします | diff --git a/translations/ja-JP/content/github/getting-started-with-github/saving-repositories-with-stars.md b/translations/ja-JP/content/github/getting-started-with-github/saving-repositories-with-stars.md index be840ba222..fa8e28f3b7 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/saving-repositories-with-stars.md +++ b/translations/ja-JP/content/github/getting-started-with-github/saving-repositories-with-stars.md @@ -1,6 +1,6 @@ --- title: Star を付けてリポジトリを保存する -intro: 'You can star repositories and topics to keep track of projects you find interesting{% if currentVersion == "free-pro-team@latest" %} and discover related content in your news feed{% endif %}.' +intro: 'リポジトリや Topics に Star を付けて、興味のあるプロジェクトを追跡し{% if currentVersion == "free-pro-team@latest" %}、ニュースフィードで関連コンテンツを見つけることができます{% endif %}。' redirect_from: - /articles/stars/ - /articles/about-stars/ @@ -20,7 +20,7 @@ versions: Star を付けることで、リポジトリやトピックが後で見つけやすくなります。 {% data variables.explore.your_stars_page %} にアクセスすると、Star 付きのリポジトリとトピックを確認することができます。 {% if currentVersion == "free-pro-team@latest" %} -You can star repositories and topics to discover similar projects on +リポジトリやトピックにスターを付けて、同様のプロジェクトを見つけることができます {% data variables.product.product_name %} の Enterprise 設定を使用してアナウンスバナーを設定することもできます。 リポジトリあるいはトピックに Star を付けると、{% data variables.product.product_name %} はニュースフィードの discovery ビューで関連するコンテンツを推薦することがあります。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} でオープンソースにコントリビュートする方法を見つける](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)」を参照してください。 {% endif %} @@ -44,7 +44,7 @@ Star ページの右上隅で、Star を付けたリポジトリおよびトピ ### 友人の Star を閲覧する - ページの右下隅では、友人の Star を参照することもできます。 You can use this to find new repositories and topics to star. + ページの右下隅では、友人の Star を参照することもできます。 これを使用して、Star を付ける新しいリポジトリや Topics を見つけることができます。 ![友人の Star を閲覧](/assets/images/help/stars/stars_jump_to_a_friend.png) diff --git a/translations/ja-JP/content/github/getting-started-with-github/set-up-git.md b/translations/ja-JP/content/github/getting-started-with-github/set-up-git.md index 26cb582214..b0a4cbab60 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/set-up-git.md +++ b/translations/ja-JP/content/github/getting-started-with-github/set-up-git.md @@ -17,9 +17,9 @@ versions: github-ae: '*' --- -コマンドラインで Git を使うには、あなたのコンピュータに Git をダウンロードし、インストールし、設定する必要があります。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. For more information on {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) documentation.{% endif %} +コマンドラインで Git を使うには、あなたのコンピュータに Git をダウンロードし、インストールし、設定する必要があります。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} コマンドラインから {% data variables.product.prodname_cli %} をインストールして {% data variables.product.product_name %} を使用することもできます。 {% data variables.product.prodname_cli %} の詳細については、[{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) ドキュメントを参照してください。{% endif %} -ローカルで Git を動かしたいけれどもコマンドラインを使いたくない場合、代わりに [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) クライアントをダウンロードしインストールしてください。 For more information, see "[Installing and configuring {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)." +ローカルで Git を動かしたいけれどもコマンドラインを使いたくない場合、代わりに [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) クライアントをダウンロードしインストールしてください。 詳しい情報については、「[{% data variables.product.prodname_desktop %} のインストールと設定](/desktop/installing-and-configuring-github-desktop/)」を参照してください。 ローカルでファイルを扱う作業をする必要がない場合、{% data variables.product.product_name %} により、以下を含む、多くの Git 関連のアクションをブラウザで直接実行できます: diff --git a/translations/ja-JP/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/ja-JP/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md index 480050dc00..be5895ed86 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/ja-JP/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md @@ -13,7 +13,7 @@ versions: {% data variables.product.prodname_ghe_server %} を評価するための 45 日間トライアルをリクエストできます。 トライアルは仮想アプライアンスとしてインストールされ、オンプレミスまたはクラウドでのデプロイメントのオプションがあります。 サポートされている仮想化プラットフォームの一覧については「[GitHub Enterprise Server インスタンスをセットアップする](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。 -{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. これらの機能のデモについては、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 これらの機能の詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」 および「[{% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_dotcom_the_website %} に接続する](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。 +{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}現在、セキュリティ{% endif %}アラートと {% data variables.product.prodname_github_connect %} は {% data variables.product.prodname_ghe_server %} のトライアルでは利用できません。 これらの機能のデモについては、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 これらの機能の詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」 および「[{% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_dotcom_the_website %} に接続する](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。 {% data variables.product.prodname_ghe_cloud %} のトライアルも利用できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_cloud %} のトライアルを設定する](/articles/setting-up-a-trial-of-github-enterprise-cloud)」を参照してください。 @@ -36,7 +36,7 @@ versions: - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) ウェブキャスト - {% data variables.product.prodname_dotcom %} ガイドの [Understanding the {% data variables.product.prodname_dotcom %}flow](https://guides.github.com/introduction/flow/) - {% data variables.product.prodname_dotcom %} ガイドの [Hello World](https://guides.github.com/activities/hello-world/) -3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise/admin/configuration/configuring-your-enterprise)." +3. 組織のニーズに合わせてインスタンスを設定するには、「[Enterprise を設定する](/enterprise/admin/configuration/configuring-your-enterprise)」を参照してください。 4. {% data variables.product.prodname_ghe_server %} とご使用のアイデンティティプロバイダとを統合するには、「[SAML を使用する](/enterprise/admin/user-management/using-saml)」および「[LDAP を使用する](/enterprise/admin/authentication/using-ldap)」を参照してください。 5. 個人をトライアルに招待します。人数制限はありません。 - ビルトイン認証または設定済みアイデンティティプロバイダを使用して、ユーザを {% data variables.product.prodname_ghe_server %} インスタンスに追加します。 詳細は「[ビルトイン認証を使用する](/enterprise/admin/user-management/using-built-in-authentication)」を参照してください。 diff --git a/translations/ja-JP/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md b/translations/ja-JP/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md index 1d360cc626..ed39ca2f35 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md +++ b/translations/ja-JP/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md @@ -1,5 +1,6 @@ --- title: 新しい GitHub アカウントへのサインアップ +shortTitle: Sign up for a new GitHub account intro: '{% data variables.product.product_name %} は、人々が協力して作業するチームのために個人および Organization のユーザアカウントを提供します。' redirect_from: - /articles/signing-up-for-a-new-github-account @@ -9,9 +10,8 @@ versions: アカウントの種類と製品の詳しい情報については、「[{% data variables.product.prodname_dotcom %}アカウントの種類](/articles/types-of-github-accounts)」および「[{% data variables.product.product_name %} の製品](/articles/github-s-products)」を参照してください。 -1. {% data variables.product.product_name %} の[価格]({% data variables.product.pricing_url %})ページに移動してください。 -2. {% data variables.product.product_name %} が提供するさまざまな製品およびサブスクリプションの情報をお読みいただき、選択したいプランの下にある [Upgrade] ボタンをクリックしてください。 -3. プロンプトに従って、個人アカウントまたは Organization を作成してください。 +{% data reusables.accounts.create-account %} +1. プロンプトに従って、個人アカウントまたは Organization を作成してください。 ### 次のステップ diff --git a/translations/ja-JP/content/github/getting-started-with-github/supported-browsers.md b/translations/ja-JP/content/github/getting-started-with-github/supported-browsers.md index 1fe118fff7..c3ca43e35d 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/supported-browsers.md +++ b/translations/ja-JP/content/github/getting-started-with-github/supported-browsers.md @@ -4,7 +4,7 @@ redirect_from: - /articles/why-doesn-t-graphs-work-with-ie-8/ - /articles/why-don-t-graphs-work-with-ie8/ - /articles/supported-browsers -intro: '{% data variables.product.product_name %} は、最新の Web ブラウザをサポートするよう設計されています。 We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).' +intro: '{% data variables.product.product_name %} は、最新の Web ブラウザをサポートするよう設計されています。 [Chrome](https://www.google.com/chrome/)、[Firefox](http://www.mozilla.org/firefox/)、[Safari](http://www.apple.com/safari/)、[Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge)の現在のバージョンがサポートされています。' versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/ja-JP/content/github/getting-started-with-github/types-of-github-accounts.md b/translations/ja-JP/content/github/getting-started-with-github/types-of-github-accounts.md index cf30e385e7..820a9561ea 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/types-of-github-accounts.md +++ b/translations/ja-JP/content/github/getting-started-with-github/types-of-github-accounts.md @@ -1,6 +1,6 @@ --- title: GitHub アカウントの種類 -intro: 'ユーザアカウントは {% data variables.product.product_location %} 上での身分証明となります。 Your user account can be a member of any number of organizations.{% if currentVersion == "free-pro-team@latest" %} Organizations can belong to enterprise accounts.{% endif %}' +intro: 'ユーザアカウントは {% data variables.product.product_location %} 上での身分証明となります。 ユーザーアカウントは、任意の数の Organization のメンバーになることができます。{% if currentVersion == "free-pro-team@latest" %} Organization は Enterprise アカウントに所属できます。{% endif %}' redirect_from: - /manage-multiple-clients/ - /managing-clients/ @@ -14,8 +14,8 @@ versions: --- {% if currentVersion == "free-pro-team@latest" %} -For a full list of features for each -{% data variables.product.product_name %} product, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)." +各 +{% data variables.product.product_name %} 製品の機能の完全なリストについては、「[{% data variables.product.prodname_dotcom %} の製品](/github/getting-started-with-github/githubs-products)」を参照してください。 {% endif %} ### 個人ユーザアカウント @@ -40,7 +40,7 @@ For a full list of features for each {% tip %} -**Tips**: +**ヒント**: - 個人での使用や仕事での使用など、1 つのアカウントを複数の目的で使用できます。 複数のアカウントを作成することはおすすめしません。 詳細は「[複数のユーザアカウントをマージする](/articles/merging-multiple-user-accounts)」を参照してください。 - ユーザアカウントは人間のためのものですが、必要に応じて継続的インテグレーションボットなどのロボットに付与することもできます。 @@ -73,6 +73,6 @@ Enterprise アカウントを使用すると、複数の {% data variables.produ ### 参考リンク -{% if currentVersion == "free-pro-team@latest" %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)" +{% if currentVersion == "free-pro-team@latest" %}- 「[新しい {% data variables.product.prodname_dotcom %} アカウントにサインアップする](/articles/signing-up-for-a-new-github-account)」 - 「[{% data variables.product.prodname_dotcom %} の製品](/articles/githubs-products)」{% endif %} - 「[新しい Organization アカウントを作成する](/articles/creating-a-new-organization-account)」 diff --git a/translations/ja-JP/content/github/getting-started-with-github/verifying-your-email-address.md b/translations/ja-JP/content/github/getting-started-with-github/verifying-your-email-address.md index 98cd463e9c..a7da5fde00 100644 --- a/translations/ja-JP/content/github/getting-started-with-github/verifying-your-email-address.md +++ b/translations/ja-JP/content/github/getting-started-with-github/verifying-your-email-address.md @@ -28,7 +28,7 @@ versions: {% warning %} -**Warnings**: +**警告**: - {% data reusables.user_settings.no-verification-disposable-emails %} - {% data reusables.user_settings.verify-org-approved-email-domain %} diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/ja-JP/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index 4717fabaef..de9b1acce7 100644 --- a/translations/ja-JP/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/ja-JP/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -22,7 +22,7 @@ versions: {% mac %} -1. [Create a new repository](/articles/creating-a-new-repository) on +1. {% data variables.product.product_location %} に[新しいリポジトリ](/articles/creating-a-new-repository)を作成します。 {% data variables.product.product_location %}. エラーを避けるため、新しいリポジトリは*README*、ライセンス、あるいは `gitignore` で初期化しないでください。 これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 ![[Create New Repository] ドロップダウン](/assets/images/help/repository/repo-create.png) @@ -53,14 +53,14 @@ versions: 9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/articles/pushing-commits-to-a-remote-repository/)します。 ```shell $ git push -u origin main - # Pushes the changes in your local repository up to the remote repository you specified as the origin + # ローカルリポジトリの変更を、origin として指定したリモートリポジトリにプッシュする ``` {% endmac %} {% windows %} -1. [Create a new repository](/articles/creating-a-new-repository) on +1. {% data variables.product.product_location %} に[新しいリポジトリ](/articles/creating-a-new-repository)を作成します。 {% data variables.product.product_location %}. エラーを避けるため、新しいリポジトリは*README*、ライセンス、あるいは `gitignore` で初期化しないでください。 これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 ![[Create New Repository] ドロップダウン](/assets/images/help/repository/repo-create.png) @@ -91,14 +91,14 @@ versions: 9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/articles/pushing-commits-to-a-remote-repository/)します。 ```shell $ git push origin main - # Pushes the changes in your local repository up to the remote repository you specified as the origin + # ローカルリポジトリの変更を、origin として指定したリモートリポジトリにプッシュする ``` {% endwindows %} {% linux %} -1. [Create a new repository](/articles/creating-a-new-repository) on +1. {% data variables.product.product_location %} に[新しいリポジトリ](/articles/creating-a-new-repository)を作成します。 {% data variables.product.product_location %}. エラーを避けるため、新しいリポジトリは*README*、ライセンス、あるいは `gitignore` で初期化しないでください。 これらのファイルは、プロジェクトを {% data variables.product.product_name %}にプッシュした後で追加できます。 ![[Create New Repository] ドロップダウン](/assets/images/help/repository/repo-create.png) @@ -129,7 +129,7 @@ versions: 9. {% data variables.product.product_location %} へ、ローカルリポジトリの[変更をプッシュ](/articles/pushing-commits-to-a-remote-repository/)します。 ```shell $ git push origin main - # Pushes the changes in your local repository up to the remote repository you specified as the origin + # ローカルリポジトリの変更を、origin として指定したリモートリポジトリにプッシュする ``` {% endlinux %} diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md index 6d8ed5cc6c..c1ed4c9bce 100644 --- a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md +++ b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md @@ -1,6 +1,6 @@ --- title: コマンドラインを使った Git リポジトリのインポート -intro: '{% if currentVersion == "free-pro-team@latest" %}If [GitHub Importer](/articles/importing-a-repository-with-github-importer) is not suitable for your purposes, such as if your existing code is hosted on a private network, then we recommend importing using the command line.{% else %}Importing Git projects using the command line is suitable when your existing code is hosted on a private network.{% endif %}' +intro: '{% if currentVersion == "free-pro-team@latest" %} 既存のコードがプライベートネットワークでホストされている場合など、[GitHub Importer](/articles/importing-a-repository-with-github-importer) が目的に適さない場合は、コマンドラインを使用してインポートすることをお勧めします。{% else %}コマンドラインを使用して Git プロジェクトをインポートすることは、既存のコードがプライベートネットワークでホストされている場合に適しています。{% endif %}' redirect_from: - /articles/importing-a-git-repository-using-the-command-line versions: diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github.md b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github.md index ca65b28fb7..d5cd9eaf10 100644 --- a/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github.md +++ b/translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github.md @@ -1,6 +1,6 @@ --- title: GitHub にソースコードをインポートする -intro: 'You can import repositories to GitHub using {% if currentVersion == "free-pro-team@latest" %}GitHub Importer, the command line,{% else %}the command line{% endif %} or external migration tools.' +intro: 'リポジトリは、{% if currentVersion == "free-pro-team@latest" %}GitHub Importer、コマンドライン、{% else %}コマンドライン{% endif %}、または外部移行ツールを使用して GitHub にインポートできます。' redirect_from: - /articles/importing-an-external-git-repository/ - /articles/importing-from-bitbucket/ diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/index.md b/translations/ja-JP/content/github/importing-your-projects-to-github/index.md index 907a8c3024..8db3deee39 100644 --- a/translations/ja-JP/content/github/importing-your-projects-to-github/index.md +++ b/translations/ja-JP/content/github/importing-your-projects-to-github/index.md @@ -15,11 +15,9 @@ versions: ### 目次 {% topic_link_in_list /importing-source-code-to-github %} - {% link_in_list /about-github-importer %} {% link_in_list /importing-a-repository-with-github-importer %} {% link_in_list /updating-commit-author-attribution-with-github-importer %} - {% link_in_list /importing-a-git-repository-using-the-command-line %} {% link_in_list /adding-an-existing-project-to-github-using-the-command-line %} {% link_in_list /source-code-migration-tools %} diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/support-for-subversion-clients.md b/translations/ja-JP/content/github/importing-your-projects-to-github/support-for-subversion-clients.md index 21dc477a91..1c488baf05 100644 --- a/translations/ja-JP/content/github/importing-your-projects-to-github/support-for-subversion-clients.md +++ b/translations/ja-JP/content/github/importing-your-projects-to-github/support-for-subversion-clients.md @@ -28,7 +28,7 @@ Subversion チェックアウトは違います。ワーキングディレクト $ cd repo ``` -4. `trunk` ブランチを取得します。 The Subversion bridge maps trunk to the Git HEAD branch. +4. `trunk` ブランチを取得します。 Subversion ブリッジは、トランクを Git の HEAD ブランチにマップします。 ```shell $ svn up trunk > A trunk @@ -47,7 +47,7 @@ Subversion チェックアウトは違います。ワーキングディレクト Subversion ブリッジを使って GitHub にブランチを作成することもできます。 -From your svn client, make sure the default branch is current by updating `trunk`: +svn クライアントで `trunk` を更新して、デフォルトブランチが最新であることを確認します。 ```shell $ svn up trunk > At revision 1. diff --git a/translations/ja-JP/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md b/translations/ja-JP/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md index 64239a6cdd..9b2bd8a8bf 100644 --- a/translations/ja-JP/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md +++ b/translations/ja-JP/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md @@ -35,9 +35,9 @@ Git プロジェクトも、単一のディレクトリに保管されます。 Git のワークフローは以下のようになります: * Git リポジトリは、ブランチおよびタグのすべての履歴を、*.git* ディレクトリ内に保管します。 -* The latest stable release is contained within the default branch. +* 最新の安定したリリースは、デフォルトブランチに含まれています。 * アクティブな feature は、別のブランチで開発されます。 -* When a feature is finished, the feature branch is merged into the default branch and deleted. +* feature が完了すると、フィーチャブランチはデフォルトブランチにマージされ、消去されます。 Git はディレクトリ構造は同じままですが、SVN とは違い、ファイルの変更内容はブランチベースです。 diff --git a/translations/ja-JP/content/github/index.md b/translations/ja-JP/content/github/index.md index b79bce08ae..95753b597d 100644 --- a/translations/ja-JP/content/github/index.md +++ b/translations/ja-JP/content/github/index.md @@ -20,24 +20,14 @@ versions: {% link_in_list /authenticating-to-github %} - {% link_in_list /managing-subscriptions-and-notifications-on-github %} - - {% link_in_list /receiving-notifications-about-activity-on-github %} - {% link_in_list /setting-up-and-managing-organizations-and-teams %} - - {% link_in_list /setting-up-and-managing-your-enterprise %} - - - {% link_in_list /setting-up-and-managing-billing-and-payments-on-github %} - {% link_in_list /writing-on-github %} @@ -50,10 +40,7 @@ versions: {% link_in_list /collaborating-with-issues-and-pull-requests %} {% link_in_list /managing-your-work-on-github %} - - {% link_in_list /developing-online-with-codespaces %} - {% link_in_list /building-a-strong-community %} @@ -64,45 +51,20 @@ versions: {% link_in_list /administering-a-repository %} {% link_in_list /visualizing-repository-data-with-graphs %} - - {% link_in_list /managing-security-vulnerabilities %} - {% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %} {% link_in_list /managing-files-in-a-repository %} {% link_in_list /managing-large-files %} - - {% link_in_list /customizing-your-github-workflow %} - {% link_in_list /extending-github %} {% link_in_list /working-with-github-pages %} - - {% link_in_list /supporting-the-open-source-community-with-github-sponsors %} - - - -{% link_in_list /teaching-and-learning-with-github-education %} - - - {% link_in_list /finding-talent-with-github-jobs %} - - - {% link_in_list /working-with-github-support %} - - - {% link_in_list /understanding-how-github-uses-and-protects-your-data %} - - - {% link_in_list /site-policy %} - diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/3d-file-viewer.md b/translations/ja-JP/content/github/managing-files-in-a-repository/3d-file-viewer.md index 4399ecc4b6..34f9a860a5 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/3d-file-viewer.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/3d-file-viewer.md @@ -58,6 +58,6 @@ STLファイルを含むコミットあるいは一連の変更を見る場合 {% tip %} -**Note**: `ref` can be a branch or the hash to an individual commit (like `2391ae`). +**注釈**: `ref` は、個々のコミットへのブランチまたはハッシュ (`2391ae` など) にすることができます。 {% endtip %} diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md b/translations/ja-JP/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md index 14d238864b..7226d74d0f 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md @@ -20,9 +20,9 @@ versions: {% data reusables.repositories.sensitive-info-warning %} -1. On your computer, move the file you'd like to upload to +1. お使いのコンピューターで、 -{% data variables.product.product_name %} into the local directory that was created when you cloned the repository. +{% data variables.product.product_name %} にアップロードするファイルを、リポジトリのクローン作成時に作成されたローカルディレクトリに移動します。 {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} {% data reusables.git.stage_for_commit %} diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/deleting-files.md b/translations/ja-JP/content/github/managing-files-in-a-repository/deleting-files.md index 1fc75da8cb..0579bdb9e4 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/deleting-files.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/deleting-files.md @@ -16,7 +16,7 @@ versions: {% endtip %} 1. リポジトリ内で削除対象のファイルを見つけます。 -2. At the top of the file, click +2. ページの上部で、次をクリックします。 {% octicon "trashcan" aria-label="The trashcan icon" %}. {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md b/translations/ja-JP/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md index e1d652abcd..2854b7a4c7 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md @@ -23,17 +23,17 @@ versions: * [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md) -refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file. +GitHub の `codeql` リポジトリを参照し、`main` ブランチの現在のバージョンの `README.md` ファイルを表示します。 ブランチのヘッドにあるファイルのバージョンは、新たなコミットが行われるたびに変更される場合があるため、通常の URL をコピーすると、後で他のユーザが見るときはファイルのコンテンツが同一ではない場合があります。 ### y を押して特定のコミット内のファイルへのパーマリンクを取得 -For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id. これにより、そのコミットの完全に同じバージョンに永続的にリンクされます。 例: +表示されるファイルの特定のバージョンへのパーマリンクについては、URL でブランチ名を使用する代わりに (つまり、上記の例の `main` 部分)、コミット ID を入力します。 これにより、そのコミットの完全に同じバージョンに永続的にリンクされます。 例: * [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) -replaces `main` with a specific commit id and the file content will not change. +`main` を特定のコミット ID に置き換え、ファイルの内容は変更されません。 コミット SHA を手作業で探すのは不便ですが、ショートカットとして y を押すと、URL がパーマリンクのバージョンに自動で更新されます。 その後、URL をコピーし、共有すると、自分が表示したのとまったく同じものが表示されます。 diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/index.md b/translations/ja-JP/content/github/managing-files-in-a-repository/index.md index b3f549a0e0..ae3336bd8c 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/index.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/index.md @@ -14,9 +14,7 @@ versions: ### 目次 {% topic_link_in_list /managing-files-on-github %} - {% link_in_list /navigating-code-on-github %} - {% link_in_list /creating-new-files %} {% link_in_list /adding-a-file-to-a-repository %} {% link_in_list /moving-a-file-to-a-new-location %} diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/mapping-geojson-files-on-github.md b/translations/ja-JP/content/github/managing-files-in-a-repository/mapping-geojson-files-on-github.md index f8536927c9..ce6ccafc7f 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/mapping-geojson-files-on-github.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/mapping-geojson-files-on-github.md @@ -51,7 +51,7 @@ GeoJSON マップを {% data variables.product.product_name %} 以外の場所 {% tip %} -**Note**: `ref` can be a branch or the hash to an individual commit (like `2391ae`). +**注釈**: `ref` は、個々のコミットへのブランチまたはハッシュ (`2391ae` など) にすることができます。 {% endtip %} diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md b/translations/ja-JP/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md index 69972a7501..71fd546554 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/moving-a-file-to-a-new-location.md @@ -14,7 +14,7 @@ versions: {% tip %} -**Tips**: +**ヒント**: - アクセス権のないリポジトリのファイルを移動しようとした場合は、プロジェクトがあなたのユーザー アカウントにフォークされ、変更のコミット後には元のリポジトリに[プル リクエスト](/articles/about-pull-requests)を送信できます。 - 画像など、ファイルによってはコマンドラインから移動しなければならない場合があります。 詳細は「[コマンドラインを使用してファイルを新しい場所へ移動する](/articles/moving-a-file-to-a-new-location-using-the-command-line)」を参照してください。 diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/renaming-a-file.md b/translations/ja-JP/content/github/managing-files-in-a-repository/renaming-a-file.md index bacdbb8133..ce80912837 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/renaming-a-file.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/renaming-a-file.md @@ -11,7 +11,7 @@ versions: {% tip %} -**Tips**: +**ヒント**: - アクセスのないリポジトリにあるファイルの名前を変更しようとした場合は、変更をコミットした後に、プロジェクトがユーザアカウントへフォークされ、[プルリクエスト](/articles/about-pull-requests)を元のリポジトリへ送信できるようになります。 - Web インターフェイスを介して作成されるファイル名では英数字とハイフン (`-`) しか使用できません。 それ以外の文字を使用するには、ファイルをローカルで作成してコミットしてから、リポジトリへプッシュします。 diff --git a/translations/ja-JP/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md b/translations/ja-JP/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md index 843b1485b3..4490d1d498 100644 --- a/translations/ja-JP/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md +++ b/translations/ja-JP/content/github/managing-files-in-a-repository/rendering-differences-in-prose-documents.md @@ -46,9 +46,9 @@ versions: ### 複雑な diff を表示する -プルリクエストの中には、大きくて複雑なドキュメントでの多数の変更を含むものがあります。 When the changes take too long to analyze, {% data variables.product.product_name %} can't always produce a rendered view of the changes. If this happens, you'll see an error message when you click the rendered button. +プルリクエストの中には、大きくて複雑なドキュメントでの多数の変更を含むものがあります。 変更の分析に時間がかかりすぎると、{% data variables.product.product_name %} が変更のレンダリングされたビューを常に生成できない場合があります。 これが発生した場合、レンダリングされたボタンをクリックするとエラーメッセージが表示されます。 -![Message when view can't be rendered](/assets/images/help/repository/prose_diff_rendering.png) +![ビューをレンダリングできない場合のメッセージ](/assets/images/help/repository/prose_diff_rendering.png) その場合でもソースビューは変更の分析やコメント入力に使用できます。 diff --git a/translations/ja-JP/content/github/managing-large-files/about-git-large-file-storage.md b/translations/ja-JP/content/github/managing-large-files/about-git-large-file-storage.md index 4c6b4cc0f2..0dd7134b65 100644 --- a/translations/ja-JP/content/github/managing-large-files/about-git-large-file-storage.md +++ b/translations/ja-JP/content/github/managing-large-files/about-git-large-file-storage.md @@ -14,7 +14,7 @@ versions: {% if currentVersion == "free-pro-team@latest" %} Using -{% data variables.large_files.product_name_short %}, you can store files up to: +{% data variables.large_files.product_name_short %} を使用すると、最大で次のファイルサイズまで保存できます。 | 製品 | 最大ファイルサイズ | | ------------------------------------------------- | ---------------- | @@ -23,7 +23,7 @@ Using | {% data variables.product.prodname_team %} | 4 GB | | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %} Using -{% data variables.large_files.product_name_short %}, you can store files up to {% if currentVersion ver_lt "enterprise-server@2.21" %}{% data variables.large_files.max_lfs_size %}{% else %}5 GB{% endif %} in your repository. +{% data variables.large_files.product_name_short %} を使用すると、最大 {% if currentVersion ver_lt "enterprise-server@2.21" %}{% data variables.large_files.max_lfs_size %}{% else %}5 GB{% endif %} のファイルをリポジトリに保存できます。 {% endif %} {% data variables.large_files.product_name_short %}を{% data variables.product.prodname_desktop %}と共に使うこともできます。 {% data variables.product.prodname_desktop %}でのGit FLSリポジトリのクローンに関する詳しい情報については、[GitHubからGitHub Desktopへのリポジトリのクローン](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)を参照してください。 @@ -45,8 +45,8 @@ size 84977953 {% note %} 設定ファイルでクエリスイートを指定すると、{% data variables.product.prodname_codeql %} 分析エンジンは、デフォルトのクエリセットに加えて、スイートに含まれるクエリを実行します。 -- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites. -- {% data variables.large_files.product_name_short %} cannot be used with template repositories. +- {% data variables.large_files.product_name_short %} は {% data variables.product.prodname_pages %} サイトでは使用できません。 +- {% data variables.large_files.product_name_short %} はテンプレートリポジトリでは使用できません。 {% endnote %} diff --git a/translations/ja-JP/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/ja-JP/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index eb69478b15..75af6d6ecc 100644 --- a/translations/ja-JP/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/ja-JP/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -21,12 +21,12 @@ versions: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} If -{% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. 詳しい情報については、「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。 +{% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) オブジェクトがリポジトリのソースコードアーカイブに含まれている場合、それらのアーカイブのダウンロードは、リポジトリの帯域幅使用量にカウントされます。 詳しい情報については、「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。 {% endif %} {% tip %} -**Tips**: +**ヒント**: - {% data reusables.large_files.owner_quota_only %} - {% data reusables.large_files.does_not_carry %} diff --git a/translations/ja-JP/content/github/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/ja-JP/content/github/managing-large-files/collaboration-with-git-large-file-storage.md index 3df5a039ea..bb23365a52 100644 --- a/translations/ja-JP/content/github/managing-large-files/collaboration-with-git-large-file-storage.md +++ b/translations/ja-JP/content/github/managing-large-files/collaboration-with-git-large-file-storage.md @@ -20,7 +20,7 @@ versions: ### プルリクエストの大容量ファイルを表示する -{% data variables.product.product_name %}は、プルリクエストの {% data variables.large_files.product_name_short %}オブジェクトを表示しません。 Only the pointer file is shown: +{% data variables.product.product_name %}は、プルリクエストの {% data variables.large_files.product_name_short %}オブジェクトを表示しません。 ポインタファイルのみが表示されます。 ![大容量ファイルのプルリクエスト例](/assets/images/help/large_files/large_files_pr.png) diff --git a/translations/ja-JP/content/github/managing-large-files/conditions-for-large-files.md b/translations/ja-JP/content/github/managing-large-files/conditions-for-large-files.md index b2493f86db..a27165185d 100644 --- a/translations/ja-JP/content/github/managing-large-files/conditions-for-large-files.md +++ b/translations/ja-JP/content/github/managing-large-files/conditions-for-large-files.md @@ -17,4 +17,4 @@ versions: ### 大きなファイルのブロックされたプッシュ -{% 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 %}. 詳しい情報については 、「[Git のプッシュ制限を設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)」を参照してください。{% endif %} +{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} デフォルトでは、{% endif %}{% data variables.product.product_name %}は {% data variables.large_files.max_github_size %} を超えるプッシュをブロックします。 {% if enterpriseServerVersions contains 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/ja-JP/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/ja-JP/content/github/managing-large-files/configuring-git-large-file-storage.md index af1045c12a..0cfe396906 100644 --- a/translations/ja-JP/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/ja-JP/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -18,7 +18,7 @@ versions: {% tip %} -**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. 詳しい情報については「[GitHub Enterprise Server で Git Large File Storage を設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)」を参照してください。 +**注釈:** 大容量ファイルを {% data variables.product.product_name %} にプッシュする前に、Enterprise で {% data variables.large_files.product_name_short %} を有効化していることを確認してください。 詳しい情報については「[GitHub Enterprise Server で Git Large File Storage を設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)」を参照してください。 {% endtip %} @@ -59,5 +59,5 @@ versions: ### 参考リンク -- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- 「[{% data variables.large_files.product_name_long %} とのコラボレーション](/articles/collaboration-with-git-large-file-storage/)」{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} - 「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」{% endif %} diff --git a/translations/ja-JP/content/github/managing-large-files/index.md b/translations/ja-JP/content/github/managing-large-files/index.md index abce0f3944..033029d166 100644 --- a/translations/ja-JP/content/github/managing-large-files/index.md +++ b/translations/ja-JP/content/github/managing-large-files/index.md @@ -15,16 +15,12 @@ versions: {% link_in_list /conditions-for-large-files %} {% link_in_list /removing-files-from-a-repositorys-history %} {% link_in_list /distributing-large-binaries %} - {% link_in_list /what-is-my-disk-quota %} - {% topic_link_in_list /versioning-large-files %} {% link_in_list /about-git-large-file-storage %} {% link_in_list /installing-git-large-file-storage %} {% link_in_list /configuring-git-large-file-storage %} - {% link_in_list /about-storage-and-bandwidth-usage %} - {% link_in_list /collaboration-with-git-large-file-storage %} {% link_in_list /moving-a-file-in-your-repository-to-git-large-file-storage %} {% link_in_list /removing-files-from-git-large-file-storage %} diff --git a/translations/ja-JP/content/github/managing-large-files/installing-git-large-file-storage.md b/translations/ja-JP/content/github/managing-large-files/installing-git-large-file-storage.md index 858a2192ea..efed5ecdb6 100644 --- a/translations/ja-JP/content/github/managing-large-files/installing-git-large-file-storage.md +++ b/translations/ja-JP/content/github/managing-large-files/installing-git-large-file-storage.md @@ -58,7 +58,7 @@ versions: {% endtip %} 2. コンピュータで、ダウンロードしたファイルを見つけます。 -3. *git-lfs-windows-1.X.X.exe* というファイルをダブルクリックします。1.X.X は、ダウンロードした Git LFS のバージョンに置き換えてください。 When you open this file Windows will run a setup wizard to install +3. *git-lfs-windows-1.X.X.exe* というファイルをダブルクリックします。1.X.X は、ダウンロードした Git LFS のバージョンに置き換えてください。 このファイルを開くと、Windows はセットアップウィザードを実行して {% data variables.large_files.product_name_short %} をインストールします。 {% data variables.large_files.product_name_short %}. {% data reusables.command_line.open_the_multi_os_terminal %} 5. インストールが成功したか検証します。 diff --git a/translations/ja-JP/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/ja-JP/content/github/managing-large-files/removing-files-from-git-large-file-storage.md index 42ea1d26b9..c6c5b9f8da 100644 --- a/translations/ja-JP/content/github/managing-large-files/removing-files-from-git-large-file-storage.md +++ b/translations/ja-JP/content/github/managing-large-files/removing-files-from-git-large-file-storage.md @@ -36,9 +36,9 @@ versions: ### リポジトリにある {% data variables.large_files.product_name_short %}オブジェクト -After you remove files from {% data variables.large_files.product_name_short %}, the {% data variables.large_files.product_name_short %} objects still exist on the remote storage{% if currentVersion == "free-pro-team@latest" %} and will continue to count toward your {% data variables.large_files.product_name_short %} storage quota{% endif %}. +{% data variables.large_files.product_name_short %} からファイルを削除した後でも、{% data variables.large_files.product_name_short %} オブジェクトはそのままリモートストレージに存在し{% if currentVersion == "free-pro-team@latest" %}、{% data variables.large_files.product_name_short %} のストレージ容量に対するカウントも継続します{% endif %}。 -To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. リポジトリを削除すると、関連する Issue、Star、フォークもすべて削除されます。 詳しい情報については、「[リポジトリを削除する](/github/administering-a-repository/deleting-a-repository)」を参照するか、{% else %}{% data variables.product.prodname_enterprise %} 管理者に連絡してオブジェクトをアーカイブします。 アーカイブ化されたオブジェクトは、3 か月後にパージされます。{% endif %} +リポジトリから {% data variables.large_files.product_name_short %} オブジェクトを削除するには、{% if currentVersion == "free-pro-team@latest" %}リポジトリを削除して再作成します。 リポジトリを削除すると、関連する Issue、Star、フォークもすべて削除されます。 詳しい情報については、「[リポジトリを削除する](/github/administering-a-repository/deleting-a-repository)」を参照するか、{% else %}{% data variables.product.prodname_enterprise %} 管理者に連絡してオブジェクトをアーカイブします。 アーカイブ化されたオブジェクトは、3 か月後にパージされます。{% endif %} {% note %} 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 a628b146fd..67f9613edb 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 @@ -25,6 +25,8 @@ When your code depends on a package that has a security vulnerability, this vuln - 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 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)." {% note %} diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md new file mode 100644 index 0000000000..26b9a33fd4 --- /dev/null +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -0,0 +1,24 @@ +--- +title: About managing vulnerable dependencies +intro: '{% data variables.product.prodname_dotcom %} helps you to avoid using third-party software that contains known vulnerabilities.' +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies. + +#### Dependency graph +The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 + +#### Dependency review +By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + +#### {% data variables.product.prodname_dependabot_alerts %} +{% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 + +#### {% data variables.product.prodname_dependabot_security_updates %} +When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." + + +#### {% data variables.product.prodname_dependabot_version_updates %} +Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 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 ee448d5896..d82367ea24 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 @@ -12,7 +12,7 @@ versions: {% 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-features-for-new-repositories)." +{% 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)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %} diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/index.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/index.md index 655eb0db33..57a731111a 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/index.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/index.md @@ -9,8 +9,6 @@ versions: ### 目次 - - {% topic_link_in_list /managing-security-vulnerabilities-in-your-project %} {% link_in_list /adding-a-security-policy-to-your-repository %} {% link_in_list /about-github-security-advisories %} @@ -22,17 +20,13 @@ versions: {% link_in_list /publishing-a-security-advisory %} {% link_in_list /editing-a-security-advisory %} {% link_in_list /withdrawing-a-security-advisory %} - {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %} - + {% link_in_list /about-managing-vulnerable-dependencies %} {% link_in_list /browsing-security-vulnerabilities-in-the-github-advisory-database %} - {% link_in_list /about-alerts-for-vulnerable-dependencies %} {% link_in_list /configuring-notifications-for-vulnerable-dependencies %} - {% link_in_list /about-dependabot-security-updates %} {% link_in_list /configuring-dependabot-security-updates %} {% link_in_list /viewing-and-updating-vulnerable-dependencies-in-your-repository %} {% link_in_list /troubleshooting-the-detection-of-vulnerable-dependencies %} {% link_in_list /troubleshooting-dependabot-errors %} - diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index 6bd20667d0..09eb6eef11 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -76,6 +76,12 @@ There are separate limits for security and version update pull requests, so that 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 %} can't resolve your dependency files + +**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". + +{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." + ### Triggering a {% data variables.product.prodname_dependabot %} pull request manually If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request. diff --git a/translations/ja-JP/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/ja-JP/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index a91201887f..633522ee1f 100644 --- a/translations/ja-JP/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/ja-JP/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -13,9 +13,11 @@ versions: {% data variables.product.prodname_dependabot_alerts %} と依存関係グラフを使用するリポジトリの自動セキュリティ更新を有効にすることができます。 For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +{% data reusables.repositories.dependency-review %} + ### リポジトリ内の脆弱性のある依存関係の更新について -{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository. {% data variables.product.prodname_dependabot_security_updates %} が有効になっているリポジトリで {% data variables.product.product_name %} が脆弱性のある依存関係を検出すると、{% data variables.product.prodname_dependabot %} はプルリクエストを作成して修正します。 プルリクエストは、脆弱性を回避するために必要最低限の安全なバージョンに依存関係をアップグレードします。 +{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. プルリクエストは、脆弱性を回避するために必要最低限の安全なバージョンに依存関係をアップグレードします。 ### 脆弱性のある依存関係を表示して更新する diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md index 7991804afa..f9fe7e5e55 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/about-notifications.md @@ -22,7 +22,7 @@ versions: - リポジトリまたは Team ディスカッション内のすべてのアクティビティ。 - {% data variables.product.prodname_actions %} で設定されたリポジトリ内のワークフローのステータスなどの CI アクティビティ。 {% if currentVersion == "free-pro-team@latest" %} -- Issues, pulls requests, releases and discussions (if enabled) in a repository. +- リポジトリ内の Issue、プルリクエスト、リリース、ディスカッション (有効な場合)。 {% endif %} {% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} - リポジトリ内のリリース。 @@ -50,7 +50,7 @@ versions: ### 通知とサブスクリプションをカスタマイズする -You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. +[https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} の通知インボックスと {% data variables.product.prodname_mobile %} アプリ{% endif %}、メール、またはこれらのオプションの組み合わせから通知を表示できます。 通知設定で、受信する更新の種類と更新の送信先をカスタマイズできます。 詳しい情報については「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)」を参照してください。 @@ -59,8 +59,8 @@ You can choose to view your notifications through the notifications inbox at [ht 特定のプルリクエストやプルリクエストの更新の受信方法をカスタマイズするには、Issue またはプルリクエスト内で設定できます。 詳しい情報については、「[単一の通知をトリアージする](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)」を参照してください。 {% if currentVersion == "free-pro-team@latest" %} -You can enable push notifications in the -{% data variables.product.prodname_mobile %} app. 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)」を参照してください。 +ー +{% data variables.product.prodname_mobile %} アプリケーションでプッシュ通知を有効にできます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)」を参照してください。 {% endif %} ### 通知の受信理由 @@ -89,7 +89,7 @@ You can enable push notifications in the ### 通知のインボックスをカスタマイズする -To focus on a group of notifications in your inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. たとえば、自分がコントリビュートしているオープンソースプロジェクトのカスタムフィルタを作成し、自分がメンションされているリポジトリの通知のみを表示することができます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)」を参照してください。 トリアージしているワークフローをカスタマイズする方法のその他の例については、「[通知をトリアージするためのワークフローをカスタマイズする](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。 +{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} または {% data variables.product.prodname_mobile %}{% endif %}のインボックスにある通知のグループにフォーカスするために、カスタムフィルタを作成できます。 たとえば、自分がコントリビュートしているオープンソースプロジェクトのカスタムフィルタを作成し、自分がメンションされているリポジトリの通知のみを表示することができます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)」を参照してください。 トリアージしているワークフローをカスタマイズする方法のその他の例については、「[通知をトリアージするためのワークフローをカスタマイズする](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。 ### 通知の保持ポリシー diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md index d7b3d460ca..720702b9ce 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications.md @@ -9,19 +9,19 @@ versions: ### インボックスのトリアージを開始する -Before you start triaging your inbox, consider whether you prefer to first find and respond to the most important updates or to clear your inbox of distracting updates that are easy to remove or triage. +インボックスのトリアージを開始する前に、最重要の更新を最初に見つけて対応するか、削除またはトリアージが簡単な煩わしい更新をインボックスからクリアするかを検討してください。 -You may decide to use a combination of both approaches at various times depending on the volume of notifications you have. +通知の量に応じて、さまざまな時点で両方のアプローチを組み合わせて使用することを決定できます。 -For an example workflow of finding and responding to the most important notifications, see "[Checking your highest notification priorities](#checking-your-highest-notification-priorities)." +最も重要な通知を見つけて対応するワークフローの例については、「[最優先の通知を確認する](#checking-your-highest-notification-priorities)」を参照してください。 -For an example workflow of removing notifications that are easy to remove or triage, see "[Clearing your least important notifications](#clearing-your-least-important-notifications)." +削除またはトリアージが簡単な通知を削除するワークフローの例については、「[最も重要度の低い通知を消去する](#clearing-your-least-important-notifications)」を参照してください。 ### 最も優先度の高い通知を確認する -Choose which type of notifications are most urgent to review and pick a time to review them that's best for you. You might consider the question "Who am I blocking?" +一番最初に確認する通知の種類を選択し、通知の確認時間を選択します。 「誰をブロックするか」ということを検討します。 -For example, you may decide to check your notifications in this order in the morning during your daily planning time: +たとえば、毎日の計画を行う午前中に、次の順序で通知を確認できます。 - レビューがリクエストされているプルリクエスト。 (`reason:review-requested` でフィルタ) - ユーザ名が@メンション（直接メンション）されているイベント。 (`reason:mention` でフィルタ) - メンバーになっている Team が@メンション（Team メンション）されているイベント。 (`reason:team-mention` でフィルタ) @@ -35,15 +35,15 @@ For example, you may decide to check your notifications in this order in the mor ### 進行中の通知の更新をフォローアップする -To follow-up on notifications, you might consider the question "What was I blocked on that I'm no longer blocked on?" Choose your follow-up notification priorities. +通知をフォローアップするには、「今はブロックされていないが、ブロックされていたもの」ということを検討します。 フォローアップ通知の優先順位を選択します。 -For example, you may decide to follow up in this order: +たとえば、次の順序でフォローアップすることを決定できます。 - 割り当てられた Issue およびプルリクエスト。 可能な Issue またはプルリクエストをすぐにクローズして、更新を追加します。 必要に応じて、後で確認するために通知を保存します。 - 保存済インボックスの通知、特に未読の更新を確認します。 スレッドが不要になった場合は、{% octicon "bookmark" aria-label="The bookmark icon" %} をオフにして、通知を保存済インボックスから削除し、保存を解除します。 ### 優先度の低い通知を管理する -After triaging the higher priority notifications, review the remaining notifications, such as participating notifications. Consider these questions: +優先度の高い通知をトリアージした後、参加通知などの残りの通知を確認します。 次の質問を検討してください。 - この通知をサブスクライブ解除できますか？ この通知は完了していて、**Done**としてマークしても大丈夫ですか？ {% tip %} @@ -55,12 +55,12 @@ After triaging the higher priority notifications, review the remaining notificat ### 最も重要度の低い通知を消去する -Choose which type of notifications are quickest and easiest for you to triage and remove from your inbox, ideally triaging multiple notifications at once. +トリアージしてインボックスから削除する際に最も速くて簡単な通知の種類を選択します。理想的としては、一度に複数の通知をトリアージします。 たとえば、次の順序で通知をクリアすることができます。 - サブスクライブ解除できる参加通知。 - 保持またはフォローアップに関連しないリポジトリの更新。 -For more information on managing multiple notifications in your inbox at the same time, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)." +インボックス内の複数の通知を同時に管理する方法の詳細については、「[インボックスからの通知を管理する](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)」を参照してください。 -You may also consider changing your notification settings or unsubscribing from these updates if possible. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" or "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)." +可能な場合、通知設定を変更するか、これらの更新のサブスクライブ解除することを検討することもできます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)」または「[GitHub におけるアクティビティのサブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)」を参照してください。 diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 95344d744c..4700a65188 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -124,7 +124,8 @@ To filter notifications by why you've received an update, you can use the `reaso - `is:repository-invitation`{% if currentVersion != "github-ae@latest" %} - `is:repository-vulnerability-alert` - `is:repository-advisory`{% endif %} -- `is:team-discussion` +- `is:team-discussion`{% if currentVersion == "free-pro-team@latest" %} +- `is:discussions`{% endif %} {% if currentVersion != "github-ae@latest" %} For information about reducing noise from notifications for diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md index 9bb6ca44db..574f5d9efe 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions.md @@ -7,39 +7,39 @@ versions: github-ae: '*' --- -To help you understand your subscriptions and decide whether to unsubscribe, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)." +サブスクリプションを理解し、サブスクライブ解除するかどうかを決めるため、「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)」を参照してください。 {% note %} -**Note:** Instead of unsubscribing, you have the option to ignore a repository. リポジトリを無視した場合、通知は届きません。 あなたが @メンションされても通知されなくなるため、リポジトリを無視することはおすすめしません。 {% if currentVersion == "free-pro-team@latest" %}If you're experiencing abuse and want to ignore a repository, please [contact support](/contact) so we can help. {% data reusables.policies.abuse %}{% endif %} +**注釈:** サブスクライブ解除する代わりに、リポジトリを無視するオプションがあります。 リポジトリを無視した場合、通知は届きません。 あなたが @メンションされても通知されなくなるため、リポジトリを無視することはおすすめしません。 {% if currentVersion == "free-pro-team@latest" %不正利用の発生によりリポジトリを無視する場合は、[サポートにお問い合わせ](/contact)ください。 {% data reusables.policies.abuse %}{% endif %} {% endnote %} ### サブスクライブ解除の方法を選択する -To unwatch (or unsubscribe from) repositories quickly, go to the "Watched repositories" page, where you can see all repositories you're watching. For more information, see "[Unwatch a repository](#unwatch-a-repository)." +リポジトリの Watch をすばやく Watch 解除 (またはサブスクライブ解除) するには、[Watched repositories] ページに移動します。このページでは、Watch しているすべてのリポジトリを確認できます。 詳しい情報については、「[リポジトリを Watch 解除する](#unwatch-a-repository)」を参照してください。 -To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page. +複数の通知のサブスクライブ解除を同時に行うには、インボックスまたはプランページを使用します。 これらのオプションはどちらも、[Watched repositories] ページよりもサブスクリプションに関するより多くのコンテキストを提供しています。 #### インボックスからサブスクライブ解除する利点 -When you unsubscribe from notifications in your inbox, you have several other triaging options and can filter your notifications by custom filters and discussion types. 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)」を参照してください。 +インボックスの通知をサブスクライブ解除する場合、他にも複数のトリアージオプションがあり、カスタムフィルタとディスカッションタイプで通知をフィルタ処理できます。 詳しい情報については「[インボックスからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)」を参照してください。 #### サブスクリプションページからサブスクライブ解除する利点 -When you unsubscribe from notifications on the subscriptions page, you can see more of the notifications you're subscribed to and sort them by "Most recently subscribed" or "Least recently subscribed". +プランページで通知のサブスクライブを解除すると、サブスクライブしている通知がさらに表示され、[Most recently subscribed] または [Least recently subscribed] で並べ替えることができます。 -The subscriptions page shows you all of the notifications that you're currently subscribed to, including notifications that you have marked as **Done** in your inbox. +プランページには、インボックスで [**Done**] としてマークした通知を含む、現在サブスクライブしているすべての通知が表示されます。 -You can only filter your subscriptions by repository and the reason you're receiving the notification. +サブスクリプションは、リポジトリと通知を受信する理由でのみフィルタできます。 ### インボックスの通知からサブスクライブ解除する -When you unsubscribe from notifications in your inbox, they will automatically disappear from your inbox. +インボックスの通知をサブスクライブ解除すると、通知は自動的にインボックスから削除されます。 {% data reusables.notifications.access_notifications %} 1. 通知インボックスから、サブスクライブ解除する通知を選択します。 -2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![メインインボックスからの [Unsubcribe] オプション](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. **選択した** {% octicon "triangle-down" aria-label="The down triangle icon" %} ドロップダウンを使用して、[**Unsubscribe**] をクリックします。 ![メインインボックスからの [Unsubcribe] オプション](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ### サブスクリプションページで通知をサブスクライブ解除する @@ -50,7 +50,7 @@ When you unsubscribe from notifications in your inbox, they will automatically d ### リポジトリの Watch 解除 -When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned. +リポジトリを Watch 解除すると、会話に参加したり@メンションされたりしない限り、そのリポジトリからの今後の更新をサブスクライブ解除します。 {% data reusables.notifications.access_notifications %} 1. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[**Watched repositories**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png) @@ -63,5 +63,5 @@ When you unwatch a repository, you unsubscribe from future updates from that rep {% if currentVersion == "free-pro-team@latest" %} - リポジトリの Watch 解除 - リポジトリのすべての通知を無視 - - customize the types of event you receive notifications for (issues, pull requests, releases or discussions, if enabled) + - 通知を受け取るイベントの種類をカスタマイズ (Issue、プルリクエスト、リリース、ディスカッションが有効の場合) {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md index 4c2fde38f8..8dcff434b3 100644 --- a/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md +++ b/translations/ja-JP/content/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification.md @@ -9,11 +9,11 @@ versions: ### 単一の通知を保存する -単一の通知を保存して後で確認するには、通知の右側にある {% octicon "bookmark" aria-label="The bookmark icon" %} をクリックします。 You can only save one notification at a time. +単一の通知を保存して後で確認するには、通知の右側にある {% octicon "bookmark" aria-label="The bookmark icon" %} をクリックします。 一度に保存できる通知は 1 つだけです。 -Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. 5か月以上前に保存した通知の保存を解除すると、通知は1日以内にインボックスから消えます。 +保存した通知は無期限に保持され、サイドバーの [**Saved**] をクリックするか、`is:saved` クエリで表示できます。 5か月以上前に保存した通知の保存を解除すると、通知は1日以内にインボックスから消えます。 - ![Save triaging option](/assets/images/help/notifications-v2/save-triaging-option.png) + ![トリアージの保存オプション](/assets/images/help/notifications-v2/save-triaging-option.png) ### 通知を調査する @@ -24,7 +24,7 @@ Saved notifications are kept indefinitely and can be viewed by clicking **Saved* - 後で確認するために通知を保存する - 通知インボックスに戻る -For more information about your triage options, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)." +トリアージオプションの詳細については、「[インボックスからの通知を管理する](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)」を参照してください。 ### Issue またはプルリクエストの今後の更新の受信タイミングをカスタマイズする @@ -32,10 +32,10 @@ For more information about your triage options, see "[Managing notifications fro 1. Issue またはプルリクエストの右側の列の [Notifications] の横にある [**Customize**] をクリックします。 - ![Customize option under "Notifications"](/assets/images/help/notifications-v2/customize-notifications-for-specific-thread.png) + ![[Notifications] の下のカスタマイズオプション](/assets/images/help/notifications-v2/customize-notifications-for-specific-thread.png) -2. Select **Custom** and choose when you'd like to receive a notification update for this thread. For example, you can choose to receive an update when the pull request has been merged, closed, or reopened. You will be subscribed again if you participate in the thread, your username is @mentioned, or a team you're a member of is @mentioned. +2. [**Custom**] を選択し、このスレッドの更新通知を受信するタイミングを選択します。 たとえば、プルリクエストがマージ、クローズ、または再オープンされたときに更新を受信するように選択できます。 スレッドに参加するか、ユーザー名が @メンションされているか、メンバーである Team が @メンションされている場合は、再度サブスクライブされます。 - ![Options for customizing notifications](/assets/images/help/notifications-v2/custom-options-for-customizing-notification-thread-updates.png) + ![通知をカスタマイズするオプション](/assets/images/help/notifications-v2/custom-options-for-customizing-notification-thread-updates.png) 3. [**Save**] をクリックします。 diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/about-issues.md b/translations/ja-JP/content/github/managing-your-work-on-github/about-issues.md index 3305849150..dea0a6b3f8 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/about-issues.md @@ -10,11 +10,17 @@ versions: github-ae: '*' --- +### Issueについて + リポジトリ中の Issue で、ユーザフィードバックの収集、ソフトウェアバグの報告、完了したいタスクの編成ができます。 Issueは、単なるソフトウェアのバグを報告する場所以上の働きをします。 +Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} + +{% data reusables.discussions.you-cannot-convert-a-discussion %} + {% data reusables.pull_requests.close-issues-using-keywords %} -Issue 内の最も最新のコメントの情報を得ておきたい場合には、Issue を Watch して最新のコメントについての通知を受けることができます。 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 %}." +Issue 内の最も最新のコメントの情報を得ておきたい場合には、Issue を Watch して最新のコメントについての通知を受けることができます。 詳しい情報については、{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」{% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications)」を参照してください{% endif %}。 サブスクライブした Issue の最新の更新へのリンクを素早く見つけるには、ダッシュボードにアクセスしてください。 詳しい情報については[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)を参照してください。 @@ -26,7 +32,7 @@ Issue を使うと、以下のことができます: - Issue テンプレートを作成して、コントリビューターが有意義な Issue をオープンしやすくする。 詳しい情報については[Issue およびプルリクエストのテンプレートについて](/articles/about-issue-and-pull-request-templates)を参照してください。 - オープン Issue を別のリポジトリへ移譲する。 詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照してください。 - 重要な Issue をピン止めして見つけやすくし、Issue の重複を避けてノイズを減らす。 詳細は「[Issue をリポジトリにピン止めする](/articles/pinning-an-issue-to-your-repository)」を参照してください。 -- 返信テンプレートを使って重複 Issue を追跡する。 For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} +- 返信テンプレートを使って重複 Issue を追跡する。 詳しい情報については「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% if currentVersion == "free-pro-team@latest" %} - {% data variables.product.prodname_dotcom %}の[コミュニティガイドライン](/articles/github-community-guidelines)に違反するコメントをレポートする。 詳細は「[乱用やスパムをレポートする](/articles/reporting-abuse-or-spam)」を参照してください。{% endif %} Issue は[他のユーザに割り当て](/articles/assigning-issues-and-pull-requests-to-other-github-users)たり、素早く検索できるように[ラベルでタグ付け](/articles/applying-labels-to-issues-and-pull-requests)したり、[マイルストーンでグループ化](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)したりすることもできます。 diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/index.md b/translations/ja-JP/content/github/managing-your-work-on-github/index.md index 5e60b99910..2d924314c5 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/index.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/index.md @@ -17,15 +17,11 @@ versions: {% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} - {% link_in_list /deleting-an-issue %} - {% link_in_list /opening-an-issue-from-a-comment %} {% link_in_list /opening-an-issue-from-code %} - {% link_in_list /transferring-an-issue-to-another-repository %} {% link_in_list /pinning-an-issue-to-your-repository %} - {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} @@ -43,9 +39,7 @@ versions: {% link_in_list /linking-a-repository-to-a-project-board %} {% link_in_list /about-automation-for-project-boards %} {% link_in_list /configuring-automation-for-project-boards %} - {% link_in_list /copying-a-project-board %} - {% link_in_list /closing-a-project-board %} {% link_in_list /reopening-a-closed-project-board %} {% link_in_list /deleting-a-project-board %} diff --git a/translations/ja-JP/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/ja-JP/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index 5d9fb1ac6b..d4f2acb7a9 100644 --- a/translations/ja-JP/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/ja-JP/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -25,6 +25,7 @@ Issue およびプルリクエストの検索用語により、次のことが - [特定の人に関連するが、必ずしも **@メンション**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)ではない Issue とプルリクエストのフィルタリング: `state:open type:issue involves:octocat` - アサインされた人による Issues とプルリクエストのフィルタリング: `state:open type:issue assignee:octocat` - ラベルにより Issue とプルエストをフィルタリング: `state:open type:issue label:"bug"` +- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} Issueについては、以下も検索に利用できます。 diff --git a/translations/ja-JP/content/github/receiving-notifications-about-activity-on-github/index.md b/translations/ja-JP/content/github/receiving-notifications-about-activity-on-github/index.md index 2e085383b4..486f984ff0 100644 --- a/translations/ja-JP/content/github/receiving-notifications-about-activity-on-github/index.md +++ b/translations/ja-JP/content/github/receiving-notifications-about-activity-on-github/index.md @@ -14,16 +14,10 @@ versions: {% link_in_list /choosing-the-delivery-method-for-your-notifications %} {% topic_link_in_list /managing-your-notifications %} {% link_in_list /marking-notifications-as-read %} - {% link_in_list /saving-notifications-for-later %} - {% link_in_list /subscribing-to-and-unsubscribing-from-notifications %} - {% link_in_list /listing-the-issues-and-pull-requests-youre-subscribed-to %} - {% link_in_list /watching-and-unwatching-repositories %} - {% link_in_list /watching-and-unwatching-releases-for-a-repository %} - {% link_in_list /watching-and-unwatching-team-discussions %} {% link_in_list /listing-the-repositories-youre-watching %} diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/ja-JP/content/github/searching-for-information-on-github/about-searching-on-github.md index bdf36a07f4..5c0c6613cf 100644 --- a/translations/ja-JP/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/ja-JP/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -41,7 +41,8 @@ versions: - [リポジトリ](/articles/searching-for-repositories) - [Topics](/articles/searching-topics) -- [Issue およびプルリクエスト](/articles/searching-issues-and-pull-requests) +- [Issues and pull requests](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} +- [Discussions](/github/searching-for-information-on-github/searching-discussions){% endif %} - [コード](/articles/searching-code) - [コミット](/articles/searching-commits) - [ユーザ](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/index.md b/translations/ja-JP/content/github/searching-for-information-on-github/index.md index e68269439d..f9b8326205 100644 --- a/translations/ja-JP/content/github/searching-for-information-on-github/index.md +++ b/translations/ja-JP/content/github/searching-for-information-on-github/index.md @@ -26,6 +26,7 @@ versions: {% link_in_list /searching-code %} {% link_in_list /searching-commits %} {% link_in_list /searching-issues-and-pull-requests %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /searching-discussions %} {% link_in_list /searching-github-marketplace %}{% endif %} {% link_in_list /searching-users %} {% link_in_list /searching-for-packages %} diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/searching-discussions.md b/translations/ja-JP/content/github/searching-for-information-on-github/searching-discussions.md new file mode 100644 index 0000000000..dd630093a8 --- /dev/null +++ b/translations/ja-JP/content/github/searching-for-information-on-github/searching-discussions.md @@ -0,0 +1,110 @@ +--- +title: Searching discussions +intro: You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/github/searching-for-information-on-github/about-searching-on-github)」を参照してください。 + +{% data reusables.search.syntax_tips %} + +### タイトル、本文、またはコメントで検索 + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| 修飾子 | サンプル | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +### ユーザまたは Organization のリポジトリ内の検索 + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| 修飾子 | サンプル | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +### リポジトリの可視性によるフィルタ + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. 詳細は「[リポジトリの可視性について](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)」を参照してください。 + +| Qualifier | Example | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +### 作者で検索 + +The `author` qualifier finds discussions created by a certain user. + +| 修飾子 | サンプル | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +### コメントした人で検索 + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| 修飾子 | サンプル | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +### Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| 修飾子 | サンプル | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +### コメントの数で検索 + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +### インタラクションの数で検索 + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +### リアクションの数で検索 + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +### Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +### 参考リンク + +- 「[検索結果をソートする](/articles/sorting-search-results/)」 diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 4829d23a26..6ca329b897 100644 --- a/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ja-JP/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -203,7 +203,7 @@ You can filter by the visibility of the repository containing the issues and pul | 修飾子 | サンプル | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3C100&type=Issues)は、コメント数が 100 を超えるクローズした Issue にマッチします。 | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues)は、コメント数が 100 を超えるクローズした Issue にマッチします。 | | | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues)は、500 から 1,000 までの範囲のコメント数の Issue にマッチします。 | ### インタラクションの数で検索 diff --git a/translations/ja-JP/content/github/searching-for-information-on-github/searching-topics.md b/translations/ja-JP/content/github/searching-for-information-on-github/searching-topics.md index cba7b34305..26b9be6503 100644 --- a/translations/ja-JP/content/github/searching-for-information-on-github/searching-topics.md +++ b/translations/ja-JP/content/github/searching-for-information-on-github/searching-topics.md @@ -27,7 +27,7 @@ versions: `is:featured` 検索修飾子は、{% data variables.product.product_name %} 上のほとんどのリポジトリのトピックの検索結果を絞り込みます。 また、これらのトピックは、https://github.com/topics/ に特集されています。 -`is:curated` 検索修飾子は、検索結果を、コミュニティのメンバーが特別な情報を追加したトピックに限定します。 詳しい情報については、https://github.com/github/explore の「リポジトリを調べる」を参照してください。 +`is:curated` 検索修飾子は、検索結果を、コミュニティのメンバーが特別な情報を追加したトピックに限定します。 For more information, see the [explore repository](https://github.com/github/explore). トピックは、日付パラメータと `created:` を使って、作成した日付に基づいてフィルタリングできます。また、`repositories:n` を使って、トピックに関連付けられているリポジトリの数でフィルタリングすることも可能です。 これら両方の修飾子では、[不等号や範囲の修飾子](/articles/understanding-the-search-syntax)を使うことができます。 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 ba9d067f18..120212ad6c 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 @@ -8,7 +8,9 @@ versions: ### {% data variables.product.prodname_actions %}の支払いについて -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} + +{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." 利用時間 (分) は毎月リセットされますが、ストレージはリセットされません。 @@ -69,8 +71,8 @@ versions: ### 利用上限について -デフォルトでは、アカウントで{% data variables.product.prodname_actions %}を使用する際の利用上限は$0です。 アカウントに含まれる金額を超えたプライベートリポジトリの分とストレージの利用を有効にしたい場合は、利用上限を増やすか、利用を無制限にすることができます。 詳しい情報については「[{% data variables.product.prodname_actions %}の利用上限の管理](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)」を参照してください。 +{% data reusables.github-actions.actions-spending-limit-detailed %} -{% data reusables.github-actions.spending-limit-enterprise-account %} +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 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 0b8643ec05..9d2feebf2d 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 @@ -10,6 +10,8 @@ versions: {% data reusables.package_registry.packages-billing %} +{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." + {% data reusables.package_registry.container-registry-beta-billing-note %} データ転送は毎月リセットされますが、ストレージはリセットされません。 @@ -50,8 +52,8 @@ versions: ### 利用上限について -デフォルトでは、アカウントで{% data variables.product.prodname_registry %}を使用する際の利用上限は$0です。 アカウントに含まれる金額を超えてプライベートパッケージのストレージとデータ転送を有効にしたい場合は、利用上限を増やすか、利用を無制限にすることができます。 詳しい情報については「[{% data variables.product.prodname_registry %}の利用上限の管理](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)」を参照してください。 +{% data reusables.package_registry.packages-spending-limit-detailed %} -{% data reusables.package_registry.spending-limit-enterprise-account %} +For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." {% data 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-sponsors.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md index f5763c4a78..9330d4b392 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md @@ -9,6 +9,8 @@ versions: {% data reusables.sponsors.sponsorship-details %} +{% data reusables.sponsors.no-fees %} + {% data reusables.dotcom_billing.view-all-subscriptions %} ### 参考リンク 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 c0fd833fae..4f3d5d5d23 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 @@ -18,11 +18,11 @@ versions: ### 個人アカウントへの割引 -{% data variables.product.prodname_free_user %} で学生と教員が無制限のパブリックリポジトリとプライベートリポジトリを使用できることに加えて、検証済みの学生は {% data variables.product.prodname_student_pack %} に申請し、{% data variables.product.prodname_dotcom %} パートナーからのさらなるメリットを受けていただけます。 詳しい情報については「[学生開発者パックに応募する](/articles/applying-for-a-student-developer-pack)」を参照してください。 +{% data variables.product.prodname_free_user %} で学生と教員が無制限のパブリックリポジトリとプライベートリポジトリを使用できることに加えて、検証済みの学生は {% data variables.product.prodname_student_pack %} に申請し、{% data variables.product.prodname_dotcom %} パートナーからのさらなるメリットを受けていただけます。 For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." ### 学校・大学向け割引 -検証済みの教職員は教育や学術研究の目的で {% data variables.product.prodname_team %} に申し込むことができます。 詳しい情報については「[教室や研究で {% 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 %} に申し込むことができます。 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)." また、学生のために教材をお求めいただくこともできます。 詳しい情報については [{% 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 b262840437..78d1d2963a 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 @@ -7,24 +7,24 @@ versions: free-pro-team: '*' --- +{% 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.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. ページの右側の、選択した層の隣にある [**Edit**] をクリックします。 ![層の編集ボタン](/assets/images/help/billing/edit-tier-button.png) +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### スポンサーシップをキャンセルする -スポンサーシップをキャンセルした場合、その変更は次回の請求日から有効になります。 {% data reusables.sponsors.no-refunds %} - {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.billing %} +{% 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-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 6a3d5ba722..56c92bc629 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 @@ -8,13 +8,15 @@ versions: ### {% data variables.product.prodname_actions %} の利用上限について -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} -設定する利用上限を引き上げたり、一部のアカウントについて無制限に設定することができます。 OrganizationまたはEnterprise アカウントの分を請求書で支払っている場合、超過分を前払いして、利用上限を引き上げることができます。 利用上限は、{% data variables.product.prodname_actions %} と {% data variables.product.prodname_registry %} を組み合わせた範囲に適用されます。 {% 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)」を参照してください。 +{% data reusables.github-actions.actions-spending-limit-brief %} -利用上限を$0より高く設定すると、過去に発生した超過分についても請求が生じます。 たとえば、Organizationで {% data variables.product.prodname_team %} を使用していて超過を許可しておらず、月あたりのストレージ使用量が1.9GBから2.1GBに増えるワークフローアーティファクトを作成した場合、ストレージは製品に含まれる2GBをわずかに超えることになります。 +{% 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)." -超過を有効にしていなかったため、次にパッケージのバージョンを発行しようとしても失敗します。 その月の0.1GBの超過分について請求書は発行されません。 ただし、次の月に超過を有効にすると、新しい請求サイクルの超過分に加えて、過去の0.1GB超過分が最初の請求書に含まれます。 +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をわずかに超えることになります。 + +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. ### ユーザアカウントの {% data variables.product.prodname_actions %} に対する利用上限を管理する @@ -30,8 +32,6 @@ versions: Organization の {% data variables.product.prodname_actions %} については、Organizationのオーナーと支払いマネージャーが利用上限を管理できます。 -Organizationアカウントに対して請求書での支払いをしている場合、{% data variables.product.product_name %}上のEnterpriseアカウントに対する料金の上限を管理できません。 Organizationが所有するリポジトリで、各リポジトリに含まれるストレージまたはデータ転送を超えて{% data variables.product.prodname_actions %}を使用を許可する場合は、超過分を前払いすることができます。 超過分は前払いする必要があるので、請求書で支払わうアカウントに対して無制限の使用を有効にすることはできません。 利用上限は、事前支払いした額の150%になります。 質問がある場合は[営業チームまでお問い合わせ](https://enterprise.github.com/contact)ください。 - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ Organizationアカウントに対して請求書での支払いをしている Enterprise アカウントの {% data variables.product.prodname_actions %} については、Enterprise オーナーと支払いマネージャーが利用上限を管理できます。 -{% data reusables.github-actions.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 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 8d107d7eaa..7de51df986 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 @@ -10,11 +10,13 @@ versions: {% data reusables.package_registry.packages-billing %} -設定する利用上限を引き上げたり、一部のアカウントについて無制限に設定することができます。 OrganizationまたはEnterprise アカウントの分を請求書で支払っている場合、超過分を前払いして、利用上限を引き上げることができます。 利用上限は、{% data variables.product.prodname_registry %} と {% data variables.product.prodname_actions %} を組み合わせた範囲に適用されます。 {% 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)」を参照してください。 +{% data reusables.package_registry.packages-spending-limit-brief %} -利用上限を$0より高く設定すると、過去に発生した超過分についても請求が生じます。 たとえば、Organizationで {% data variables.product.prodname_team %} を使用していて超過を許可しておらず、月あたりのストレージ使用量が1.9GBから2.1GBに増えるプライベートパッケージの新しいバージョンを発行した場合、ストレージは製品に含まれる2GBをわずかに超えることになります。 +{% 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)." -超過を有効にしていなかったため、次にパッケージのバージョンを発行しようとしても失敗します。 その月の0.1GBの超過分について請求書は発行されません。 ただし、次の月に超過を有効にすると、新しい請求サイクルの超過分に加えて、過去の0.1GB超過分が最初の請求書に含まれます。 +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.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. ### ユーザアカウントの {% data variables.product.prodname_registry %} に対する利用上限を管理する @@ -30,8 +32,6 @@ versions: Organization の {% data variables.product.prodname_registry %} については、Organizationのオーナーと支払いマネージャーが利用上限を管理できます。 -Organizationアカウントに対して請求書での支払いをしている場合、{% data variables.product.product_name %}上のEnterpriseアカウントに対する料金の上限を管理できません。 Organizationが所有するリポジトリで、各リポジトリに含まれるストレージまたはデータ転送を超えて{% data variables.product.prodname_registry %}を使用を許可する場合は、超過分を前払いすることができます。 超過分は前払いする必要があるので、請求書で支払わうアカウントに対して無制限の使用を有効にすることはできません。 利用上限は、事前支払いした額の150%になります。 質問がある場合は[営業チームまでお問い合わせ](https://enterprise.github.com/contact)ください。 - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ Organizationアカウントに対して請求書での支払いをしている Enterprise アカウントの {% data variables.product.prodname_registry %} については、Enterprise オーナーと支払いマネージャーが利用上限を管理できます。 -{% data reusables.package_registry.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 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 0044e1d5d4..c0f1b835fe 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 @@ -7,12 +7,15 @@ versions: free-pro-team: '*' --- +{% data reusables.sponsors.org-sponsors-release-phase %} + +### About sponsorship upgrades + スポンサーシップ層をアップグレードした場合、その変更は直ちに有効になります。 {% data reusables.sponsors.prorated-sponsorship %} -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. ページの右側の、選択した層の隣にある [**Edit**] をクリックします。 ![層の編集ボタン](/assets/images/help/billing/edit-tier-button.png) +### スポンサーシップをアップグレードする + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.update-sponsorship %} +{% data reusables.sponsors.update-sponsorship %} \ No newline at end of file diff --git a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md index 7cf5a2f757..6f6beefd96 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization.md @@ -12,7 +12,7 @@ versions: {% tip %} -**Tips**: +**ヒント**: - クライアントの Organization をアップグレードする前に、 [Organization のファイルで支払い方法を表示または更新](/articles/adding-or-editing-a-payment-method)することができます。 - これらの手順は、*シートごとのプラン*で Organization をアップグレードおよびダウングレードするためのものです。 クライアントが*レガシーのリポジトリ単位プラン*で {% data variables.product.product_name %} を支払っている場合は、レガシーのプランをアップグレードまたは[ダウングレード](/articles/downgrading-your-github-subscription)するか、[Organization をシート単位の価格に切り替える](/articles/upgrading-your-github-subscription)ことができます。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md index d3d0edebad..b5ada7978e 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md @@ -20,7 +20,7 @@ versions: ### 1. Organization コンテンツのバックアップ -Organization を削除すると、GitHub では**コンテンツを復元できません**。 そのため、Organization を削除する前に、必ずアカウントのリポジトリ、ウィキ、Issue をすべてコピーしておいてください。 +Organization を削除すると、GitHub では**コンテンツを復元できません**。 Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. ### 2. Organization の削除 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md index bb02a2d0b8..e9acc9631e 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -19,4 +19,4 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.oauth_app_access %} 5. [**Remove restrictions**] をクリックします。 ![[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) +6. サードパーティアプリケーション制限の無効化に関する情報を確認したら、[**Yes, remove application restrictions**] (はい、アプリケーション制限を削除します) をクリックします。 ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization.md index 7781959230..2d1e81d33d 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -12,7 +12,7 @@ versions: {% warning %} -**Warnings**: +**警告**: - {% 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 %} 取引に関する情報にアクセスできます。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md index d76dd3676c..4518bee2a5 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -20,42 +20,30 @@ versions: {% link_in_list /creating-a-new-organization-from-scratch %} {% link_in_list /accessing-your-organizations-settings %} {% link_in_list /about-your-organizations-news-feed %} - {% link_in_list /viewing-insights-for-your-organization %} - {% topic_link_in_list /managing-membership-in-your-organization %} - {% link_in_list /inviting-users-to-join-your-organization %} {% link_in_list /canceling-or-editing-an-invitation-to-join-your-organization %} {% link_in_list /adding-people-to-your-organization %} - {% link_in_list /removing-a-member-from-your-organization %} {% link_in_list /reinstating-a-former-member-of-your-organization %} - {% link_in_list /can-i-create-accounts-for-people-in-my-organization %} - {% topic_link_in_list /managing-peoples-access-to-your-organization-with-roles %} {% link_in_list /permission-levels-for-an-organization %} {% link_in_list /maintaining-ownership-continuity-for-your-organization %} {% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %} - {% link_in_list /adding-a-billing-manager-to-your-organization %} {% link_in_list /removing-a-billing-manager-from-your-organization %} - {% topic_link_in_list /organizing-members-into-teams %} {% link_in_list /about-teams %} {% link_in_list /creating-a-team %} {% link_in_list /setting-your-teams-profile-picture %} {% link_in_list /adding-organization-members-to-a-team %} - {% link_in_list /managing-code-review-assignment-for-your-team %} - {% link_in_list /renaming-a-team %} {% link_in_list /changing-team-visibility %} - {% link_in_list /synchronizing-a-team-with-an-identity-provider-group %} - {% link_in_list /moving-a-team-in-your-organizations-hierarchy %} {% link_in_list /requesting-to-add-a-child-team %} {% link_in_list /requesting-to-add-or-change-a-parent-team %} @@ -66,9 +54,7 @@ versions: {% topic_link_in_list /managing-access-to-your-organizations-repositories %} {% link_in_list /repository-permission-levels-for-an-organization %} {% link_in_list /setting-base-permissions-for-an-organization %} - {% link_in_list /viewing-people-with-access-to-your-repository %} - {% link_in_list /managing-an-individuals-access-to-an-organization-repository %} {% link_in_list /managing-team-access-to-an-organization-repository %} {% link_in_list /adding-outside-collaborators-to-repositories-in-your-organization %} @@ -84,83 +70,54 @@ versions: {% link_in_list /managing-an-individuals-access-to-an-organization-project-board %} {% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %} {% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %} - {% topic_link_in_list /managing-access-to-your-organizations-apps %} {% link_in_list /adding-github-app-managers-in-your-organization %} {% link_in_list /removing-github-app-managers-from-your-organization %} - {% topic_link_in_list /managing-organization-settings %} - {% link_in_list /verifying-your-organizations-domain %} - {% link_in_list /renaming-an-organization %} {% link_in_list /transferring-organization-ownership %} {% link_in_list /restricting-repository-creation-in-your-organization %} {% link_in_list /setting-permissions-for-deleting-or-transferring-repositories %} {% link_in_list /restricting-repository-visibility-changes-in-your-organization %} {% link_in_list /managing-the-forking-policy-for-your-organization %} - {% link_in_list /disabling-or-limiting-github-actions-for-your-organization %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization %} - - {% link_in_list /setting-permissions-for-adding-outside-collaborators %} - {% link_in_list /allowing-people-to-delete-issues-in-your-organization %} - - + {% link_in_list /allowing-people-to-delete-issues-in-your-organization %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /managing-discussion-creation-for-repositories-in-your-organization %}{% endif %} {% link_in_list /setting-team-creation-permissions-in-your-organization %} - - {% link_in_list /managing-scheduled-reminders-for-your-organization %} - - {% link_in_list /managing-the-default-branch-name-for-repositories-in-your-organization %} - - {% link_in_list /managing-default-labels-for-repositories-in-your-organization %} - - {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} - - {% link_in_list /managing-the-display-of-member-names-in-your-organization %} - + {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} - {% link_in_list /integrating-jira-with-your-organization-project-board %} - - {% link_in_list /upgrading-to-the-corporate-terms-of-service %} - {% topic_link_in_list /migrating-to-improved-organization-permissions %} {% link_in_list /converting-an-owners-team-to-improved-organization-permissions %} {% link_in_list /converting-an-admin-team-to-improved-organization-permissions %} {% link_in_list /migrating-admin-teams-to-improved-organization-permissions %} - {% topic_link_in_list /restricting-access-to-your-organizations-data %} {% link_in_list /about-oauth-app-access-restrictions %} {% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /approving-oauth-apps-for-your-organization %} {% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %} - {% topic_link_in_list /keeping-your-organization-secure %} {% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %} {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} - {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} {% link_in_list /managing-secret-scanning-for-your-organization %} - {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} - {% link_in_list /restricting-email-notifications-to-an-approved-domain %} - {% link_in_list /reviewing-the-audit-log-for-your-organization %} {% link_in_list /reviewing-your-organizations-installed-integrations %} - {% topic_link_in_list /managing-saml-single-sign-on-for-your-organization %} {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} {% link_in_list /about-scim %} @@ -170,17 +127,12 @@ versions: {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} {% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %} - {% link_in_list /managing-team-synchronization-for-your-organization %} - {% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %} {% topic_link_in_list /granting-access-to-your-organization-with-saml-single-sign-on %} {% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %} {% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %} - - {% topic_link_in_list /managing-git-access-to-your-organizations-repositories %} {% link_in_list /about-ssh-certificate-authorities %} {% link_in_list /managing-your-organizations-ssh-certificate-authorities %} - diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md index 25a6de5f2f..ad4aa2442f 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization.md @@ -11,7 +11,7 @@ versions: {% tip %} -**Tips**: +**ヒント**: - Organization がユーザ単位の有料プランである場合、新しいメンバーを招待して参加させる、または Organization の以前のメンバーを復帰させる前に、そのためのライセンスが用意されている必要があります。 詳細は「[ユーザごとの価格付けについて](/articles/about-per-user-pricing)」を参照してください。 {% data reusables.organizations.org-invite-expiration %} - Organization がメンバーに 2 要素認証を使うことを要求している場合、招待するユーザは招待を受ける前に 2 要素認証を有効化する必要があります。 詳細については、「[Organization で 2 要素認証を要求する](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)」と「[2要素認証 (2FA) でアカウントをセキュアにする](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)」を参照してください。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..33cc25ea47 --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Managing discussion creation for repositories in your organization +intro: You can choose the permission levels that members require to create discussions in repositories owned by your organization. +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Allowing or disallowing users with read access to create discussions + +By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. [**Save**] をクリックします。 !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png) + +### 参考リンク + +- "[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/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index ce254beaa8..37f5984aa9 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -9,29 +9,39 @@ versions: ### セキュリティおよび分析設定の管理について {% data variables.product.prodname_dotcom %} を使用して、Organization のリポジトリを保護できます。 Organization でメンバーが作成する既存または新規のリポジトリすべてについて、セキュリティおよび分析機能を管理できます。 - {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% endif %} - -### 既存のリポジトリに対して機能を有効または無効にする +### 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 %} -5. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -6. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。 ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -7. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。 ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) -### 既存のリポジトリに対して機能を有効または無効にする +The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. + +### Enabling or disabling a feature for all existing repositories + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) +1. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。 ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) +1. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。 ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + +### Enabling or disabling a feature for all new repositories when they are added + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. [Configure security and analysis features] にある機能の右側で、Organization の新規のリポジトリに対して機能をデフォルトで有効または無効にします。 ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + +### Allowing Dependabot to access private repositories + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) +1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. +1. Click **Select repositories**. -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. [Configure security and analysis features] にある機能の右側で、Organization の新規のリポジトリに対して機能をデフォルトで有効または無効にします。 ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..14a895aece --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,23 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +--- + +{% 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. 詳細は「[スポンサーシップを管理する](/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. [**Update profile**] をクリックします。 ![[Update profile] ボタン](/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)" \ No newline at end of file diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 3796766a48..8d3b92115e 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -55,6 +55,9 @@ Organization のメンバーは、*owner (オーナー)*{% if currentVersion == | Organization の Team ディスカッションを無効にする (詳細は「[Organization の Team ディスカッションを無効化する](/articles/disabling-team-discussions-for-your-organization)」を参照) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} | Organization dependency insights の可視性を管理する (詳細は「[Organization dependency insights の可視性を変更する](/articles/changing-the-visibility-of-your-organizations-dependency-insights)」を参照) | **X** | | |{% endif %} | **すべての Team** で Team プロフィール画像を設定する (詳細は「[Team のプロフィール画像を設定する](/articles/setting-your-team-s-profile-picture)」を参照) | **X** | | | +| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | Organization のリポジトリから {% data variables.product.prodname_pages %} サイトを公開するのを無効にする (詳細、「[Organization の {% data variables.product.prodname_pages %} サイトの公開を無効化する](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)」を参照) | **X** | | | | Organization のセキュリティおよび分析設定を管理する (詳細は「[Organization のセキュリティおよび分析設定を管理する](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)」を参照) | **X** | | | | [SAML シングルサインオン](/articles/about-identity-and-access-management-with-saml-single-sign-on)を有効にして強制する | **X** | | | diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md index a801c06981..0b3abb3c4b 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization.md @@ -25,7 +25,7 @@ When an outside collaborator's access to your organization's private repositorie {% tip %} -**Tips**: +**ヒント**: - 外部コラボレーターの 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 %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index afb5a4f33f..05b0e628ea 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -114,7 +114,19 @@ Organization レベルの設定を管理することに加え、Organization の | [リポジトリの削除または 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** | +| JIRA や Zendesk などの外部リソースに対する自動リンク参照を作成します (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| [セキュリティアドバイザリ](/github/managing-security-vulnerabilities/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} ### 参考リンク diff --git a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index d2be055386..eda6553151 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -82,7 +82,9 @@ Each category has a set of associated actions that you can filter on. 例: 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 %} 例: +{% data reusables.search.date_gt_lt %} + +例: * `created:2014-07-08` は、2014 年 7 月 8 日に発生したイベントをすべて検索します。 * `created:>=2014-07-08` は、2014 年 7 月 8 日かそれ以降に生じたすべてのイベントを検索します。 @@ -106,25 +108,53 @@ Using the qualifier `country`, you can filter events in the audit log based on t {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -### Audit log API を使用する +### 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 %} -**メモ**: Audit log API は、{% data variables.product.prodname_enterprise %} を使用している Organization が利用できます。 {% data reusables.gated-features.more-info-org-products %} +**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 %} -IP の安全性を保ち、Organization のコンプライアンスを守るため、Audit log API を使って、Audit log データのコピーを保存し、モニタリングできます。 -* Organization またはリポジトリの設定へのアクセス -* 権限の変更 -* Organization、リポジトリ、または Team におけるユーザの追加や削除 -* 管理者に昇格しているユーザ -* GitHub App の権限の変更 +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. +{% endif %} GraphQL のレスポンスには、90 日から 120 日までのデータを含めることができます。 たとえば、GraphQL にリクエストして、Organization に新しく追加された Organization メンバー全員を表示できます。 詳細は「[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 as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +{% 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)" in the REST API documentation. + +{% endif %} + ### Audit log actions An overview of some of the most common actions that are recorded as events in the audit log. @@ -149,7 +179,7 @@ An overview of some of the most common actions that are recorded as events in th | `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 +#### `billing` カテゴリアクション | アクション | 説明 | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | @@ -214,6 +244,28 @@ An overview of some of the most common actions that are recorded as events in th | `update` | [Team ディスカッションの投稿への返答が編集される](/articles/managing-disruptive-comments/#editing-a-comment)ときにトリガーされます。 | | `destroy` | [Team ディスカッションの投稿への返答が削除される](/articles/managing-disruptive-comments/#deleting-a-comment)ときにトリガーされます。 | +{% 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. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. + +{% 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 | アクション | 説明 | @@ -238,13 +290,13 @@ An overview of some of the most common actions that are recorded as events in th {% if currentVersion == "free-pro-team@latest" %} -#### `marketplace_agreement_signature` category actions +#### `marketplace_agreement_signature` カテゴリアクション | アクション | 説明 | | -------- | --------------------------------------------------------------------------------------- | | `create` | {% data variables.product.prodname_marketplace %} Developer Agreement に署名するときにトリガーされます。 | -#### `marketplace_listing` category actions +#### `marketplace_listing` カテゴリアクション | アクション | 説明 | | --------- | ----------------------------------------------------------------------------------- | @@ -345,7 +397,7 @@ An overview of some of the most common actions that are recorded as events in th {% if currentVersion == "free-pro-team@latest" %} -#### `payment_method` category actions +#### `payment_method` カテゴリアクション | アクション | 説明 | | -------- | -------------------------------------------------------------------- | @@ -355,12 +407,12 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} -#### `profile_picture` category actions +#### `profile_picture` カテゴリアクション | アクション | 説明 | | ------ | -------------------------------------------- | | update | Organization のプロファイル写真を設定または更新するときにトリガーされます。 | -#### `project` category actions +#### `project` カテゴリアクション | アクション | 説明 | | ------------------------ | -------------------------------------------------------------------------------------- | @@ -394,7 +446,7 @@ An overview of some of the most common actions that are recorded as events in th | `update_linear_history_requirement_enforcement_level` | 保護されたブランチについて、必須の直線状のコミット履歴が有効化または無効化されるときにトリガーされます。 | {% endif %} -#### `repo` category actions +#### `repo` カテゴリアクション | アクション | 説明 | | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -408,7 +460,7 @@ An overview of some of the most common actions that are recorded as events in th | `config.unlock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロック解除される](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。{% endif %} | `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} | `create_actions_secret` | Triggered when a repository admin [creates a {% data variables.product.prodname_actions %} secret](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).{% endif %} -| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} +| `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 repository admin removes a {% data variables.product.prodname_actions %} secret.{% endif %} @@ -497,16 +549,28 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} {% if currentVersion == "free-pro-team@latest" %} -#### `sponsors` category actions +#### `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)」を参照) | +| アクション | 説明 | +| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo_funding_link_button_toggle` | リポジトリでスポンサーボタンの表示を有効化または無効化したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | +| `repo_funding_links_file_action` | リポジトリで FUNDING ファイルを変更したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | +| `sponsor_sponsorship_cancel` | スポンサーシップをキャンセルしたときにトリガーされます (「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照) | +| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/articles/managing-your-sponsorship)") | +| `sponsor_sponsorship_tier_change` | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照) | +| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_tier_description_update` | スポンサーシップ層の説明を変更したときにトリガーされます (「[スポンサーシップ層を変更する](/articles/changing-your-sponsorship-tiers)」を参照) | +| 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 %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -#### `team` category actions +#### `team` カテゴリアクション | アクション | 説明 | | -------------------- | ---------------------------------------------------------------------------------------------------- | 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 66d16e2695..2732b6688d 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 @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and{% endif %}private repositories, with specific details of your activity in private repositories anonymized. 詳細は「[プライベートコントリビューションをプロフィールで公開または非公開にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)」を参照してください。 +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}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)」を参照してください。 {% note %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/index.md index 23477db558..8d293471c4 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/index.md @@ -14,41 +14,28 @@ versions: {% topic_link_in_list /managing-user-account-settings %} {% link_in_list /about-your-personal-dashboard %} + {% link_in_list /managing-your-theme-settings %} {% link_in_list /changing-your-github-username %} - {% link_in_list /merging-multiple-user-accounts %} {% link_in_list /converting-a-user-into-an-organization %} - {% link_in_list /deleting-your-user-account %} {% link_in_list /permission-levels-for-a-user-account-repository %} {% link_in_list /permission-levels-for-user-owned-project-boards %} {% link_in_list /managing-the-default-branch-name-for-your-repositories %} {% link_in_list /managing-security-and-analysis-settings-for-your-user-account %} - {% link_in_list /managing-access-to-your-user-accounts-project-boards %} - + {% link_in_list /managing-access-to-your-user-accounts-project-boards %} {% link_in_list /integrating-jira-with-your-personal-projects %} - - {% link_in_list /best-practices-for-leaving-your-company %} - - {% link_in_list /what-does-the-available-for-hire-checkbox-do %} - {% topic_link_in_list /managing-email-preferences %} {% link_in_list /adding-an-email-address-to-your-github-account %} {% link_in_list /changing-your-primary-email-address %} {% link_in_list /setting-a-backup-email-address %} {% link_in_list /setting-your-commit-email-address %} - {% link_in_list /blocking-command-line-pushes-that-expose-your-personal-email-address %} - {% link_in_list /remembering-your-github-username-or-email %} - {% link_in_list /types-of-emails-github-sends %} - - {% link_in_list /managing-marketing-emails-from-github %} - {% topic_link_in_list /managing-access-to-your-personal-repositories %} {% link_in_list /inviting-collaborators-to-a-personal-repository %} {% link_in_list /removing-a-collaborator-from-a-personal-repository %} @@ -58,9 +45,7 @@ versions: {% link_in_list /about-organization-membership %} {% link_in_list /accessing-an-organization %} {% link_in_list /viewing-peoples-roles-in-an-organization %} - {% link_in_list /requesting-organization-approval-for-oauth-apps %} - {% link_in_list /publicizing-or-hiding-organization-membership %} {% link_in_list /managing-your-scheduled-reminders %} {% link_in_list /removing-yourself-from-an-organization %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md new file mode 100644 index 0000000000..fc04420622 --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -0,0 +1,22 @@ +--- +title: Managing your theme settings +intro: You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode. +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Theme settings is currently in beta and subject to change. + +{% endnote %} + +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. + +{% data reusables.user_settings.access_settings %} +1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) + +### 参考リンク + +- "[{% data variables.product.prodname_desktop %}用のテーマの設定方法](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md b/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md index 573c1783dc..d3debb9365 100644 --- a/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ja-JP/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -このバージョンの発効日: 2020 年 11 月 13 日 +Version Effective Date: December 14, 2020 アカウントを作成すると利用できるようになる各種の機能と製品は、すべて本サービスの一部です。 このような機能と製品の多くは機能性が異なるため、その機能や製品に固有の利用規約が必要になる場合があります。 Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -46,13 +46,11 @@ GitHub Pagesは、特定の帯域幅および使用法の制限を受けるた ### 5. アクションとパッケージ #### a. アクションの使用量 -GitHubアクションでは、カスタムソフトウェア開発のライフサイクルにわたるワークフローをGitHubリポジトリに直接作成することができます。 Each Account comes with included compute and storage quantities for use with Actions, depending on your Account plan, which can be found in the [Actions documentation](/actions). Your Actions compute usage is displayed within [your account settings](https://github.com/settings/billing), and you will be notified by email in advance of reaching the limit of your included quantities. 付属の量を超えてアクションを使用したい場合は、[超過使用を有効にする](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)こともできます。 +GitHub Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. -付属の量と有料の量の計算使用量は、実行するアクションの種類 (Linux、Windows、macOSなど)に基づいて分単位で計算されます。 各アクションのジョブまたはタスクに使用された時間を、分単位で切り上げます。 付属の量の場合は、アクションの種類に応じ、各ジョブまたはタスクの実行に使われた時間に倍数をかけてから、最も近い分単位に切り上げます。 超過使用時間は、実行するアクションの種類に基づいて[申告された分単位の価格](https://github.com/features/actions)で請求されます。 アクションとパッケージはストレージを共有し、ストレージの使用量は、[アカウント設定](https://github.com/settings/billing)に表示されます。 For additional details about included quantity usage calculations, see the [Actions documentation](/actions). - -アクションとアクションサービスの要素は、本契約、[利用規定](/github/site-policy/github-acceptable-use-policies)、またはGitHubアクション[サービス制限](/actions/reference/usage-limits-billing-and-administration/#usage-limits)に違反して使用される場合があります。 また、アクションは次の用途には使用しないでください。 +Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions). また、アクションは次の用途には使用しないでください。 - クリプトマイニング; -- 当社サーバーを使用して、何らかのサービス、デバイス、データ、アカウントまたはネットワークを妨害すること、またはこれらに不正アクセスするかあるいはこれを試みること ([GitHub Bug Bounty program](https://bounty.github.com) により許可されている場合を除く)、 +- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); - the provision of a stand-alone or integrated application or service offering Actions or any elements of Actions for commercial purposes; - any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or - gitHubアクションが使用されるリポジトリに関連するソフトウェアプロジェクトの製造、テスト、デプロイ、公開に関連しないその他の行為。 @@ -60,16 +58,7 @@ GitHubアクションでは、カスタムソフトウェア開発のライフ このような使用制限違反や、GitHubアクションの悪用を防ぐために、GitHubはGitHubアクションの使用を監視する場合があります。 GitHubアクションを不正利用した場合には、ジョブが停止されたり、GitHubアクションの使用を制限されたりすることもあります。 #### b. パッケージの使用量 -GitHubパッケージを使用してコンテンツのパッケージをダウンロード、公開、管理することができます。 各アカウントプランには、パッケージで使用できる付属の帯域幅およびストレージ容量が付属しています。これについては、[パッケージのドキュメント](/github/managing-packages-with-github-package-registry/about-github-package-registry)を参照してください。 アクションとパッケージは、2つのサービス機能間でストレージを共有します。 ストレージと帯域幅の使用量は[アカウント設定](https://github.com/settings/billing)に表示され、付属の量の制限に達すると前もってメールで通知されます。 付属の帯域幅およびストレージを超えてパッケージを使用したい場合は、[超過使用を有効にする](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)こともできます。 - -帯域幅の使用量は、パッケージを通じてリポジトリの外部に委譲されたデータの量に基づいて計算されますが、アクションを通じてのパッケージ委譲は、付属の量にも有料の量にも含まれません。 Packages bandwidth usage is limited by the [Acceptable Use Policy](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use), and included bandwidth quantities are determined by your [account plan](https://github.com/pricing). - -アクションとパッケージのストリーム使用量は、2つのサービス機能間で共有します。 ストレージの使用量は1か月を通じた加重平均で計算され、毎月リセットはされません。 Public and private repositories have different included storage quantities, and the included quantities for private repositories depend on your [account plan](https://github.com/pricing). - -#### c. アカウントとパッケージに対する支払いと請求 -アクションとパッケージに対する請求は従量制です。 アクションまたはパッケージの追加の量を個別に購入することはできません。 月次請求のお客様が、これらのサービス機能の追加料の支払いを選択するには、支払い方法がファイルに指定されている必要があります。 請求書払いでない場合は、前月の使用量に基づいて毎月定期的に請求されます。 請求書払いのお客様の場合は、GitHubの請求日から30日以内にお支払いください。 サービス機能の制限超過分を前払いしたお客様の場合、未使用分数の前払い分は次の請求期間に繰り越されず、返金されません。 - -[アカウント設定](https://github.com/settings/billing/cost_management)で、毎月の使用制限を設定することができます。 付属の量の制限や、有料で追加した量に指定した使用制限に近づくと、前もってメールで通知されます。 +GitHub Packages is billed on a usage basis. The [Packages documentation](/packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies). ### 6. Learning Lab @@ -108,3 +97,13 @@ Your use of Spectrum is governed by the GitHub [Terms of Service](/github/site-p #### b. GitHub Advisory Databaseのライセンス GitHub Advisory Databaseは、[Creative Commons Attribution 4.0ライセンス](https://creativecommons.org/licenses/by/4.0/)の下でライセンスされています。 帰属条件は、のGitHub Advisory Databaseまたは使用される個々のGitHub Advisory Databaseレコード（で始まる）にリンクすることで満たすことができます。 + +### 13. GitHub Enterprise Server + +#### a. SQL Server Images + +You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time. + +#### b. Third-party components + +「ソフトウェア」には、第三者によって GitHub にライセンスを付与されたコンポーネントが含まれており、そうしたソフトウエアの中には、GitHub に対して、それらのコンポーネントのソースコードを入手可能にすることを要求するソフトウェアも含まれています。 これらのコンポーネントのソースコードは、要請に応じて提供いたします。 diff --git a/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md b/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md index 91f67c4ed2..8254f3970a 100644 --- a/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md +++ b/translations/ja-JP/content/github/site-policy/github-and-trade-controls.md @@ -13,7 +13,7 @@ GitHub.com、GitHub Enterprise Server、およびあなたがいずれかの製 GitHub のビジョンは、開発者たちがどこからでもコラボレーションに参加できるグローバルなプラットフォームを築くことです。 当社は、政府の命令を精査し、ユーザーおよびお客様が法律で要求される範囲を超えた影響を受けることがないようにする責任を真摯に受け止めています。 こうした取り組みには、オープンソースプロジェクトのサービスを含むパブリックリポジトリサービスを利用可能かつアクセス可能に保つことで、制裁対象地域の開発者が参加する個人的なコミュニケーションをサポートすることも含まれます。 -To comply with U.S. trade control laws, GitHub made some required changes to the way we conduct our services. As U.S. trade controls laws evolve, we will continue to work with U.S. regulators about the extent to which we can offer free code collaboration services to developers in sanctioned markets. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those markets. 当社のアプローチと制裁がグローバルなソフトウェアコラボレーションに与える影響について詳しくは、[制裁に関するブログ](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/)をご覧ください。 +To comply with U.S. trade control laws, GitHub made some required changes to the way we conduct our services. As U.S. trade controls laws evolve, we will continue to work with U.S. regulators about the extent to which we can offer free code collaboration services to developers in sanctioned markets. 当社は、これらの無料サービスを提供することが、 foreign policy of encouraging the free flow of information and free speech in those markets. 当社のアプローチと制裁がグローバルなソフトウェアコラボレーションに与える影響について詳しくは、[制裁に関するブログ](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/)をご覧ください。 Although we've provided the following information below for your convenience, it is ultimately your responsibility to ensure that your use of GitHub's products and services complies with all applicable laws and regulations, including U.S. export control laws. @@ -61,7 +61,7 @@ However, due to U.S. 米国の貿易管理法の制限により、GitHub は米 For paid organizational accounts in sanctioned regions, users may have limited access to their public repositories, which have been downgraded to archived read-only repositories. For free organizational accounts in sanctioned regions, however, users will continue to have full access to free public repositories for open source projects (and associated public Pages), public gists, and allotted free Action minutes. -GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. +GitHub は、無料のプライベートリポジトリを含め、認可された地域の開発者が無料のコードコラボレーションサービスに最大限にアクセスできるように、米国の規制当局に引き続き提唱していきます。 - 当社は、これらの無料サービスを提供することが、 各地域での情報の自由な流れと言論の自由を奨励するという米国の外交政策をサポートすることに繋がると信じています。 #### 対象のユーザをどのように定義しているのですか？ 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 a81d1c16a2..e1c939e0ed 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 @@ -191,7 +191,7 @@ GitHub will provide notice regarding our access to private repository content, u #### 1. 価格、料金 -**支払い条件** 料金については、[github.com/pricing](https://github.com/pricing) に掲載されているものが適用されます (ただし、関係者による協議を行い、「注文書」に記載されている場合を除きます)。 お客様は、減額や相殺などに類することを行わず、アメリカ合衆国ドルにより「料金」の全額を前払いで支払うことに同意します。 設定しなければなりません。 お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 本「契約」に基づいて支払われる金額は、本「契約」に別段の定めがある場合を除き、返金できません。 お客様が定められた期限に「料金」を支払わなかった場合、普通法または衡平法に基づく法的措置を取ることに加え、GitHub は次の権利を留保します。(i) 過去の未払い金に対して毎月 1.0% か、法律により許容される最高額の金利のうち、いずれか低い額の金利を課し、かつ回収に要するあらゆる費用を課すこと、および (ii) 該当する「注文書」または SOW を解約すること。 本契約に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 +**支払い条件** 料金については、[github.com/pricing](https://github.com/pricing) に掲載されているものが適用されます (ただし、関係者による協議を行い、「注文書」に記載されている場合を除きます)。 お客様は、減額や相殺などに類することを行わず、アメリカ合衆国ドルにより「料金」の全額を前払いで支払うことに同意します。 設定しなければなりません。 お客様は、GitHub による請求の日付から 30 日以内に「料金」を支払う必要があります。 本「契約」に基づいて支払われる金額は、本「契約」に別段の定めがある場合を除き、返金できません。 Amounts payable under this Agreement are non-refundable, except as provided in Sections 13 and 14.1. 本契約に関して課されたか、負うようになったあらゆる税金、料金、関税、および政府による査定 (GitHub の純利益に基づく税金を除く) について、お客様は全責任を負います。 **従量制支払い:** 「サービス」の一部の機能は、使用量に基づいて請求されます。 かかる「サービス」機能は、限られた使用量および期間であれば、追加料金なしでご利用のプランで使用できる場合があります。 ご利用のプランに含まれる数量を超えて有料の「サービス」機能を購入することを選択した場合、お客様は前月の実際の使用量に基づいてかかる「サービス」機能の料金を支払います。 かかる購入に対する毎月の支払いは、後払いで定期的に請求されます。ただし、請求書払いのお客様については、有料の「サービス」機能は前払いとなります。 詳しくは、[GitHub 追加製品の利用規約](/github/site-policy/github-additional-product-terms)を参照してください。 diff --git a/translations/ja-JP/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/ja-JP/content/github/site-policy/github-enterprise-service-level-agreement.md index f4ac26aacc..885ec39beb 100644 --- a/translations/ja-JP/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/ja-JP/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -8,22 +8,22 @@ versions: free-pro-team: '*' --- -**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the GitHub Enterprise Cloud service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). +**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the applicable GitHub service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). -For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. +For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. ## Uptime Guarantee -“**Uptime**” is the percentage of total possible minutes the Service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the Service. The Uptime calculation for each Service Feature is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. +“**Uptime**” is the percentage of total possible minutes the applicable GitHub service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service. The Uptime calculation for each Service Feature that may be included with the applicable GitHub service is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. -| **Service Feature** | **Uptime Calculation** | **定義** | **Service Credits Calculation** | -| --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -| The **Service** includes the following Service Features:
  • 問題
  • プルリクエスト
  • Git Operations
  • API Requests
  • webhook
  • ページ
  • アクション
  • Packages
| (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
  • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than or equal to 99.9%, but greater than 99.0%.

    OR

  • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
| | -| **アクション** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

“**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | -| **Packages** | Transfers Uptime = same as Actions

Storage Uptime = 100% - Average Error Rate*

*The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

“**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | +| **Service Feature** | **Uptime Calculation** | **定義** | **Service Credits Calculation** | +| -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | +| **Issues**,
**Pull Requests**,
**Git Operations**,
**API Requests**,
**Webhooks**,
**Pages** | (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
  • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than or equal to 99.9%, but greater than 99.0%.

    OR

  • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
| | +| **アクション** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

“**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | +| **Packages** | Transfers Uptime = same as Actions

Storage Uptime = 100% - Average Error Rate*

*The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

“**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | ## 除外 -Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. +Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the applicable GitHub service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Service Credits Redemption If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). diff --git a/translations/ja-JP/content/github/site-policy/github-registered-developer-agreement.md b/translations/ja-JP/content/github/site-policy/github-registered-developer-agreement.md index 874dbfe350..b016a9d9b6 100644 --- a/translations/ja-JP/content/github/site-policy/github-registered-developer-agreement.md +++ b/translations/ja-JP/content/github/site-policy/github-registered-developer-agreement.md @@ -86,7 +86,7 @@ GitHubは、多くの開発者に当社のプラットフォームをご愛用 13. **所有権** - お客様は、GitHubとそのライセンサーが、API、「プレリリース資料」、その他すべてのGitHubの製品とサービス、それらの構成と組み合わせに関連するすべての情報とデータ、およびそれらの変更と派生物のすべての権利、権原、および利益を所有していることに同意するものとします。 お客様は、当社がAPI、「プレリリース資料」やその他GitHub製品やサービスに掲載したり、埋め込んだりした著作権その他の所有権の表示を削除、変更、隠蔽、難読化しないことに同意するものとします。 + お客様は、GitHubとそのライセンサーが、API、「プレリリース資料」、その他すべてのGitHubの製品とサービス、それらの構成と組み合わせに関連するすべての情報とデータ、およびそれらの変更と派生物のすべての権利、権原、および利益を所有していることに同意するものとします。 You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services. 14. **ユーザとしての政府機関** 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 83567fea78..27797da134 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 @@ -9,7 +9,9 @@ versions: ### {% data variables.product.prodname_sponsors %} について -{% data reusables.sponsors.sponsorship-details %} {% data reusables.sponsors.no-fees %} 詳細は、「[{% data variables.product.prodname_sponsors %}の支払いについて](/articles/about-billing-for-github-sponsors)」を参照してください。 +{% data reusables.sponsors.sponsorship-details %} + +{% data reusables.sponsors.no-fees %}詳細は「[{% data variables.product.prodname_sponsors %} の支払いについて](/articles/about-billing-for-github-sponsors)」を参照してください。 {% data reusables.sponsors.you-can-be-a-sponsored-developer %} 詳細は、「[オープンソースコントリビューターに対する {% data variables.product.prodname_sponsors %}について](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)」と「[ユーザアカウントに {% data variables.product.prodname_sponsors %}を設定する](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照してください。 @@ -21,11 +23,11 @@ versions: {% note %} -**ノート：** {% data reusables.sponsors.matching-fund-eligible %} +**Note:** {% data reusables.sponsors.matching-fund-eligible %} {% endnote %} -{% data variables.product.prodname_matching_fund %} は、{% data variables.product.prodname_dotcom %} コミュニティのメンバーが[{% data variables.product.prodname_dotcom %} コミュニティガイドライン](/github/site-policy/github-community-guidelines)を推進するオープンソースソフトウェアを開発するのを支援することを目的としています。 スポンサード Organization は {% data variables.product.prodname_matching_fund %} を利用できません。 +{% data variables.product.prodname_matching_fund %} は、{% data variables.product.prodname_dotcom %} コミュニティのメンバーが[{% data variables.product.prodname_dotcom %} コミュニティガイドライン](/github/site-policy/github-community-guidelines)を推進するオープンソースソフトウェアを開発するのを支援することを目的としています。 Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}. {% data variables.product.prodname_matching_fund %} の資格を得るには、長期にわたって支えてくれるコミュニティを引き付けるようなプロフィールを作成する必要があります。 強力なプロフィールの作成については、「[{% data variables.product.prodname_sponsors %}のプロフィール詳細を編集する](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)」を参照してください。 @@ -35,8 +37,6 @@ versions: これは単なる始めに過ぎません。{% data variables.product.prodname_sponsors %} が将来皆さんのお役に立てるよう、ぜひともご意見をお寄せください。 フィードバックやご提案は、[{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors) からお送りください。 -現在のところ、スポンサード開発者および Organization になれるのは個人ユーザのみです。 Organization で開発者のスポンサーとなることに関心がある場合は、[{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors) までメールでお知らせください。 - ### 参考リンク - [オープンソースコントリビューターをスポンサーする](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors) - [{% data variables.product.prodname_sponsors %} を通じてスポンサーシップを獲得する](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors) diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md new file mode 100644 index 0000000000..57b1b5a4d6 --- /dev/null +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md @@ -0,0 +1,13 @@ +--- +title: Attributing sponsorships to your organization +intro: 'You can attribute the sponsorships paid by one of your organizations to another organization.' +versions: + free-pro-team: '*' +permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization. +--- + +1. Navigate to the organization whose sponsorships you want to attribute to another organization. +1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png) +1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png) +1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png) +1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md index 1aafab9387..2097f3d2e7 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -13,38 +13,20 @@ versions: {% data reusables.sponsors.maximum-tier %} -### スポンサード開発者プロフィールに層を追加する +### スポンサーシップ層を追加する -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} -### スポンサード Organization プロフィールに層を追加する +### Editing or retiring a tier -{% data reusables.sponsors.navigate-to-org-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-dev-sponsors-dashboard %} +{% 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 %} - -### スポンサード Organization プロフィールの層を編集または破棄する - -{% data reusables.sponsors.navigate-to-org-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 %} +{% data reusables.sponsors.retire-tier %} \ No newline at end of file diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md index 9481fdbf16..25f14b3d26 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md @@ -5,11 +5,13 @@ versions: free-pro-team: '*' --- -支払い期間の終了に伴うキャンセルなど、スポンサーシップに対する変更を監視するために、スポンサードユーザまたはスポンサード Organization のアカウントに webhook を作成できます。 スポンサードユーザまたはスポンサード Organization のアカウントに webhook を設定すると、スポンサーシップが作成、編集、削除されたときにアップデートを受け取れます。 詳細は、[`スポンサーシップ`webhook イベント](/webhooks/event-payloads/#sponsorship)を参照してください。 +### About webhooks for events in your sponsored account -### スポンサードユーザアカウントに対する webhook の管理 +支払い期間の終了に伴うキャンセルなど、スポンサーシップに対する変更を監視するために、スポンサードユーザまたはスポンサード Organization のアカウントに webhook を作成できます。 When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. 詳細は、[`スポンサーシップ`webhook イベント](/webhooks/event-payloads/#sponsorship)を参照してください。 -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +### Managing webhooks for events in your sponsored account + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-webhooks-tab %} {% data reusables.sponsors.add-webhook %} {% data reusables.sponsors.add-payload-url %} @@ -17,18 +19,4 @@ versions: {% data reusables.sponsors.webhook-secret-token %} {% data reusables.sponsors.add-active-triggers %} {% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} - -### スポンサード Organization に対する webhook の管理 - -Organizationのオーナーは、スポンサード Organization に webhook を設定できます。 - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-webhooks-tab %} -{% data reusables.sponsors.add-webhook %} -{% data reusables.sponsors.add-payload-url %} -{% data reusables.sponsors.webhook-content-formatting %} -{% data reusables.sponsors.webhook-secret-token %} -{% data reusables.sponsors.add-active-triggers %} -{% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} +{% data reusables.sponsors.manage-existing-webhooks %} \ No newline at end of file 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 11c8231a23..99e87ab13e 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 @@ -7,22 +7,15 @@ versions: free-pro-team: '*' --- +### About sponsorship updates + スポンサーは、メールで作業についての最新情報を受信するかどうかを選べます。 詳細は「[スポンサーシップを管理する](/articles/managing-your-sponsorship)」を参照してください。 -アップデートは、ユーザアカウントのプライマリメールアドレス、またはOrganization アカウントの `noreply@github.com` メールアドレスから送信されます。 ユーザアカウントでメールアドレスのプライバシーを有効化している場合は、`noreply@github.com` から送信されます。 詳細は「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address)」を参照してください。 +For sponsored developer accounts, the update will come from your user account's primary email address. ユーザアカウントでメールアドレスのプライバシーを有効化している場合は、`noreply@github.com` から送信されます。 For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. 詳細は「[コミットメールアドレスを設定する](/articles/setting-your-commit-email-address)」を参照してください。 -### ユーザアカウントのスポンサーに連絡する +### スポンサーに連絡する -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.sponsors-updates-tab %} -{% data reusables.sponsors.draft-new-update %} -{% data reusables.sponsors.send-update-to-sponsors %} -{% data reusables.sponsors.write-sponsor-update %} -{% data reusables.sponsors.publish-sponsor-update %} - -### Organization のスポンサーに連絡する - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.sponsors-updates-tab %} {% data reusables.sponsors.draft-new-update %} {% data reusables.sponsors.send-update-to-sponsors %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md index 23af693005..97b8bd9565 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md @@ -10,30 +10,17 @@ versions: ### スポンサープロフィールについて -{% data variables.product.prodname_sponsors %} プロフィールは、スポンサーとなる可能性がある人に、サポートが必要な理由を伝えます。 スポンサーとなる人は、あなたの個人または Organization プロフィールの [**Sponsor**] ボタンをクリックして、あなたのスポンサープロフィールを見ることができます。 次の情報を設定しておくことをお勧めします。 +{% data variables.product.prodname_sponsors %} プロフィールは、スポンサーとなる可能性がある人に、サポートが必要な理由を伝えます。 People see your sponsor profile when they click the **Sponsor** button on your profile. 次の情報を設定しておくことをお勧めします。 -- あなたが貢献しているオープンソースの作業 -- オープンソース開発に携わっている理由 +- Open source work that you contribute to +- Why you are committed to open source development -目標を設定して、スポンサーシップのレベルごとにコミュニティのためにできることを説明することもできます。 +### Editing your profile details -### スポンサード開発者プロフィールを編集する - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### スポンサードOrganizationプロフィールを編集する - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.meet-the-team %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} +{% data reusables.sponsors.save-profile %} \ No newline at end of file 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 3253970d2c..bb349f6d01 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 @@ -16,6 +16,7 @@ versions: {% topic_link_in_list /sponsoring-open-source-contributors %} {% link_in_list /sponsoring-an-open-source-contributor %} {% link_in_list /managing-your-sponsorship %} + {% link_in_list /attributing-sponsorships-to-your-organization %} {% topic_link_in_list /receiving-sponsorships-through-github-sponsors %} {% link_in_list /about-github-sponsors-for-open-source-contributors %} {% link_in_list /setting-up-github-sponsors-for-your-user-account %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md index c5ec3d75c7..2948d8dd1e 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md @@ -13,14 +13,8 @@ versions: {% data reusables.sponsors.payout-info %} -### スポンサードユーザアカウントに対する支払い情報の表示と編集 +### Viewing and editing payout information -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} - -### スポンサード Organization に対する支払い情報の表示と編集 - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} +{% data reusables.sponsors.edit-bank-information %} \ No newline at end of file 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 2fa8704b8e..b155c4c77d 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 @@ -1,27 +1,19 @@ --- title: スポンサーシップ目標を管理する -intro: コミュニティがあなたをスポンサーすることによる影響を把握できるように、スポンサード開発者またはスポンサード Organization プロフィールに対して目標を設定することができます。 +intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you. versions: free-pro-team: '*' --- ### スポンサーシップ目標について -スポンサード開発者または Organization プロフィールの資金獲得目標を設定し、その目標をコミュニティと共有することができます。 目標を設定すると、オープンソースコミュニティにおける自分の影響を把握し、{% data variables.product.prodname_sponsors %} プログラムで影響力を持てるようになります。 +You can set a funding goal for your sponsored account and share the goal with your community. 目標を設定すると、オープンソースコミュニティにおける自分の影響を把握し、{% data variables.product.prodname_sponsors %} プログラムで影響力を持てるようになります。 目標には、確保したいスポンサーの数、または毎月集めたい金額を設定できます。 一度に設定できる目標は 1 つだけです。 目標に達したら、次の目標を設定できます。 -### スポンサード Organization に対する目標の設定 +### Setting a goal -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.set-a-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### スポンサード開発者に対する目標の設定 - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.set-a-goal %} {% data reusables.sponsors.select-goal-type %} @@ -31,6 +23,7 @@ versions: 目標を編集するとき、すでに達成した目標を選択することはできません。 たとえば、5 スポンサーをすでに達成している場合、目標を設定して 4 スポンサーにすることはできません。 +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.select-goal-type %} @@ -40,6 +33,7 @@ versions: いったん破棄した目標を、再度アクティブ化することはできません。 かわりに、新しい目標を設定してください。 +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.retire-goal %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md index 50d8e7c37f..9dd20560af 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -1,42 +1,35 @@ --- title: スポンサーシップを管理する -intro: あなたのスポンサーシップを表示できる人や、スポンサードオープンソースコントリビューターからメールで最新情報を受け取るかどうかを管理できます。 +intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account. redirect_from: - /articles/managing-your-sponsorship versions: free-pro-team: '*' --- -スポンサーシップ層の変更に関する詳細は、「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照してください。 +{% data reusables.sponsors.org-sponsors-release-phase %} -### 開発者スポンサーシップのプライバシー設定を管理する +### スポンサーシップのプライバシー設定を管理する -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} {% data reusables.sponsors.who-can-see-your-sponsorship %} {% data reusables.sponsors.update-sponsorship %} -### Organization スポンサーシップのプライバシー設定を管理する +### Managing email updates for your sponsorship -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.who-can-see-your-sponsorship %} +You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address. + +{% data reusables.sponsors.manage-updates-for-orgs %} + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} +{% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.update-sponsorship %} -### スポンサード開発者からのメールによる最新情報を管理する +### 参考リンク -スポンサード開発者が、作業についての最新情報をメールであなたに送信できるかどうかを選択できます。 スポンサード開発者は、あなたのメールアドレスにアクセスできません。 - -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} -{% data reusables.sponsors.developer-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} - -### スポンサード Organization からのメールによる最新情報を管理する - -スポンサード Organization が、作業についての最新情報をメールであなたに送信できるかどうかを選択できます。 スポンサード Organization は、あなたのメールアドレスにアクセスできません。 - -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.org-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} +- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" +- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)" \ No newline at end of file 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 a1be975ee7..546a8e3286 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 @@ -25,7 +25,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu ### スポンサードOrganizationプロフィールを記入する -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% 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 %} @@ -54,7 +54,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} Open Collective を使用して Stripe Connect を設定する方法については、Open Collective のドキュメンテーションで「[{% data variables.product.prodname_sponsors %} の設定](https://docs.opencollective.com/help/collectives/github-sponsors)」を参照してください。 @@ -63,7 +63,7 @@ Open Collective を使用して Stripe Connect を設定する方法について {% data reusables.sponsors.tax-form-information-org %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -75,7 +75,7 @@ Organization がスポンサード Organization になるには、{% data variab ### {% data variables.product.prodname_dotcom %} に申請をサブミットして承認を求める -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %} {% data reusables.sponsors.github-review-app %} 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 d80618e9d8..d78788355a 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 @@ -26,7 +26,7 @@ To join {% data variables.product.prodname_sponsors %} as an organization, see " {% data variables.product.prodname_dotcom %} で申請がレビューされたら、ユーザがあなたのスポンサーになれるようにスポンサード開発者プロフィールを設定できます。 -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ To join {% data variables.product.prodname_sponsors %} as an organization, see " {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} @@ -54,14 +54,14 @@ To join {% data variables.product.prodname_sponsors %} as an organization, see " {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} ### 納税情報をサブミットする {% data reusables.sponsors.tax-form-information-dev %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -73,7 +73,7 @@ To join {% data variables.product.prodname_sponsors %} as an organization, see " ### {% data variables.product.prodname_dotcom %} に申請をサブミットして承認を求める -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 4. [**Request approval**] をクリックします。 ![[Request approval] ボタン](/assets/images/help/sponsors/request-approval-button.png) {% data reusables.sponsors.github-review-app %} 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 fe176cf7c5..a2a5c53396 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 @@ -7,17 +7,32 @@ redirect_from: - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer versions: free-pro-team: '*' +permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization. --- -### 開発者と Organization に対するスポンサーについて +{% data reusables.sponsors.org-sponsors-release-phase %} -{% data reusables.sponsors.sponsorship-details %} {% data reusables.sponsors.no-fees %} 詳細は、「[{% data variables.product.prodname_sponsors %}の支払いについて](/articles/about-billing-for-github-sponsors)」を参照してください。 +### About sponsorships -オープンソースコントリビューターをスポンサーすると、その変更は直ちに有効になります。 {% data reusables.sponsors.prorated-sponsorship %} +{% data reusables.sponsors.sponsorship-details %} -スポンサードオープンソースコントリビューターがあなたの層を廃止した場合、あなたが別の層を選択するか、プランをキャンセルするまで、あなたはその層にそのままとどまります。 詳細は「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照してください。 +You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons. +- Sustaining specific libraries that your organization's work depends on +- Investing in the ecosystem you rely on as a organization (such as blockchain) +- Developing brand awareness as an organization that values open source +- Thanking open source developers for building libraries that complement the product your organization offers -スポンサーしたいオープンソースコントリビューターに、スポンサード開発者または Organization のプロフィールがない場合は、スポンサード開発者または Organization のプロフィールを作成するようコントリビューターに促すことができます。 詳細については、「[ユーザアカウントに {% 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)」を参照してください。 +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). + +{% data reusables.sponsors.no-fees %}詳細は「[{% data variables.product.prodname_sponsors %} の支払いについて](/articles/about-billing-for-github-sponsors)」を参照してください。 + +When you sponsor an account using a credit card, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} + +{% data reusables.sponsors.manage-updates-for-orgs %} + +If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. 詳細は「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照してください。 + +If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. 詳細については、「[ユーザアカウントに {% 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)」を参照してください。 {% data reusables.sponsors.sponsorships-not-tax-deductible %} @@ -27,30 +42,20 @@ versions: {% endnote %} -### 開発者をスポンサーする +### Sponsoring an account -開発者をスポンサーするには、認証済みメールアドレスが必要です。 詳細は「[メールアドレスを検証する](/github/getting-started-with-github/verifying-your-email-address)」を参照してください。 +Before you can sponsor an account, you must have a verified email address. 詳細は「[メールアドレスを検証する](/github/getting-started-with-github/verifying-your-email-address)」を参照してください。 -1. {% data variables.product.product_name %} で、スポンサーしたい開発者のプロフィールに移動します -2. リポジトリ名の下で [**Sponsor**] をクリックします。 ![[Sponsor] ボタン](/assets/images/help/profile/sponsor-button.png) +1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor. +1. Navigate to your sponsorship dashboard for the account. + - To sponsor a developer, under the developer's name, click **Sponsor**. ![[Sponsor] ボタン](/assets/images/help/profile/sponsor-button.png) + - To sponsor an organization, to the right of the the organization's name, click **Sponsor**. ![[Sponsor] ボタン](/assets/images/help/sponsors/sponsor-org-button.png) +1. Optionally, on the right side of the page, to sponsor the account on behalf of your organization, use the **Sponsor as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you'll sponsor as](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) {% data reusables.sponsors.select-a-tier %} +{% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} ![[Edit payment] ボタン](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) {% data reusables.sponsors.who-can-see-your-sponsorship %} ![あなたのスポンサーシップを見ることができる人を選択するラジオボタン](/assets/images/help/sponsors/who-can-see-sponsorship.png) -{% data reusables.sponsors.developer-sponsored-choose-updates %} -7. [**Sponsor _DEVELOPER_**] をクリックします。 ![[Sponsor developer] ボタン](/assets/images/help/sponsors/sponsor-developer-button.png) - -### Organization をスポンサーする - -Organization をスポンサーするには、認証済みメールアドレスが必要です。 詳細は「[メールアドレスを検証する](/github/getting-started-with-github/verifying-your-email-address)」を参照してください。 - -1. {% data variables.product.product_name %} で、スポンサーする Organization のページに移動します。 -2. Organization 名の隣で、[**Sponsor**] をクリックします。 ![[Sponsor] ボタン](/assets/images/help/sponsors/sponsor-org-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.select-sponsorship-billing %} - ![[Edit payment] ボタン](/assets/images/help/sponsors/edit-org-sponsorship-payment-button.png) -{% data reusables.sponsors.who-can-see-your-sponsorship %} - ![あなたのスポンサーシップを見ることができる人を選択するラジオボタン](/assets/images/help/sponsors/who-can-see-org-sponsorship.png) -{% data reusables.sponsors.org-sponsored-choose-updates %} -7. [**Sponsor _ORGANIZATION_**] をクリックします。 ![[Sponsor organization] ボタン](/assets/images/help/sponsors/sponsor-org-confirm-button.png) +{% data reusables.sponsors.choose-updates %} +{% data reusables.sponsors.sponsor-account %} diff --git a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 23a4908009..b76532a603 100644 --- a/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/ja-JP/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -7,34 +7,25 @@ versions: free-pro-team: '*' --- +### About sponsors and sponsorships + 現在と過去のスポンサーシップについての分析、スポンサーから受領した支払い、キャンセルなどのイベント、スポンサーシップのスポンサー層の変更を表示できます。 新しいスポンサーシップ、スポンサーシップの変更、スポンサーシップのキャンセルといったアクティビティも確認できます。 アクティビティのリストは、日付でフィルタリングできます。 表示しているアカウントのスポンサーシップデータを CSV または JSON 形式でエクスポートすることもできます。 -この情報すべてには、スポンサーダッシュボードからアクセスします。 - -### スポンサーダッシュボードを表示する - -1. 任意のページの右上隅で、プロフィール画像をクリックし、続いて [**{% data variables.product.prodname_sponsors %}**] をクリックします。 ![{% data variables.product.prodname_sponsors %}ボタン](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. 表示されたリストで、スポンサーダッシュボードを表示したいアカウントまたは Organization の右にある [**Dashboard**] をクリックします。 ![開発者スポンサーダッシュボードボタン](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) - ### スポンサーとスポンサーシップを表示する -1. スポンサーダッシュボードにアクセスし、[[Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard)] を確認します。 -{% data reusables.sponsors.navigate-to-sponsors-tab %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. あるいは、スポンサーを層によってフィルタリングするには、**Filter（フィルター）**ドロップダウンメニューで、**Active tiers（アクティブな層）**または**Retired tiers（リタイアした層）**をクリックしてから、層を選択します。 ![層によってフィルタリングするドロップダウンメニュー](/assets/images/help/sponsors/filter-drop-down.png) ### 最近のスポンサーシップアクティビティを表示する -1. スポンサーダッシュボードにアクセスし、[[Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard)] を確認します。 +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. 左のサイドバーで**Activity（アクティビティ）**をクリックしてください。 ![アクティビティタブ](/assets/images/help/sponsors/activity-tab.png) ### スポンサーシップデータをエクスポートする -1. スポンサーダッシュボードにアクセスし、[[Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard)] を確認します。 +If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsors-tab %} 1. [**Export all**] をクリックします。 ![[Export all] ボタン](/assets/images/help/sponsors/export-all.png) - - スポンサーが存在しない場合、このボタンは表示されません。 - -1. エクスポートしたいデータの時間枠と形式を選択し、[**Start export**] をクリックします。 ![データエクスポートのオプション](/assets/images/help/sponsors/export-your-sponsors.png) - - {% data variables.product.prodname_dotcom %} で、選択した月のスポンサーすべてのデータがエクスポートされます。 すぐに、データの入ったファイルがファイルが添付されたメールが届きます。 エクスポートが完了したら、別の月のデータをエクスポートできます。 スポンサード Organization またはユーザアカウントごとに、1 時間に 10 セットまでのデータをエクスポートできます。 +1. エクスポートしたいデータの時間枠と形式を選択し、[**Start export**] をクリックします。 ![データエクスポートのオプション](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/ja-JP/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/ja-JP/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md index fa22605f4f..95a5ed531c 100644 --- a/translations/ja-JP/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/ja-JP/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -36,7 +36,7 @@ versions: {% endwindows %} - `BRANCH-NAME`: `master` や `gh-pages` などの、現在のプロジェクトのデフォルトブランチです。 ```shell - $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME + $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME # Filter the specified branch in your directory and remove empty commits > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) > Ref 'refs/heads/BRANCH-NAME' was rewritten diff --git a/translations/ja-JP/content/github/using-git/which-remote-url-should-i-use.md b/translations/ja-JP/content/github/using-git/which-remote-url-should-i-use.md index d4ab221511..79f5f5097f 100644 --- a/translations/ja-JP/content/github/using-git/which-remote-url-should-i-use.md +++ b/translations/ja-JP/content/github/using-git/which-remote-url-should-i-use.md @@ -24,7 +24,7 @@ The `https://` clone URLs are available on all repositories, regardless of visib {% tip %} -**Tips**: +**ヒント**: - 認証情報ヘルパーを使用すれば、{% data variables.product.prodname_dotcom %} と通信するたびに、{% data variables.product.prodname_dotcom %} の認証情報が Git で記憶されます。 詳細は「[Git に {% data variables.product.prodname_dotcom %} の認証情報をキャッシュする](/github/using-git/caching-your-github-credentials-in-git)」を参照してください。 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 ee6e10f5bc..1a66878f1a 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 @@ -21,6 +21,10 @@ 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)." +{% 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: @@ -41,7 +45,8 @@ 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. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +- 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 diff --git a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/index.md b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/index.md index 8063338026..bb4fa7c68b 100644 --- a/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/index.md +++ b/translations/ja-JP/content/github/visualizing-repository-data-with-graphs/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repository-graphs %} {% link_in_list /viewing-a-summary-of-repository-activity %} {% link_in_list /viewing-a-projects-contributors %} - {% link_in_list /viewing-traffic-to-a-repository %} - {% topic_link_in_list /analyzing-changes-to-a-repositorys-content %} {% link_in_list /visualizing-commits-in-a-repository %} {% link_in_list /visualizing-additions-and-deletions-to-content-in-a-repository %} {% topic_link_in_list /understanding-connections-between-repositories %} {% link_in_list /viewing-a-repositorys-network %} {% link_in_list /listing-the-forks-of-a-repository %} - {% link_in_list /about-the-dependency-graph %} {% link_in_list /exploring-the-dependencies-of-a-repository %} - diff --git a/translations/ja-JP/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index d0b84ba3dc..ca453d7cfb 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/ja-JP/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -51,7 +51,7 @@ Jekyll サイトのコンテンツとして 2 つの主なタイプは、ペー 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: page + layout: post title: "POST TITLE" date: YYYY-MM-DD hh:mm:ss -0000 categories: CATEGORY-1 CATEGORY-2 diff --git a/translations/ja-JP/content/github/working-with-github-pages/index.md b/translations/ja-JP/content/github/working-with-github-pages/index.md index 3d83352cf9..942952f0df 100644 --- a/translations/ja-JP/content/github/working-with-github-pages/index.md +++ b/translations/ja-JP/content/github/working-with-github-pages/index.md @@ -23,15 +23,11 @@ versions: {% topic_link_in_list /getting-started-with-github-pages %} {% link_in_list /about-github-pages %} {% link_in_list /creating-a-github-pages-site %} - {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} - {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} - {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} - {% link_in_list /unpublishing-a-github-pages-site %} {% topic_link_in_list /setting-up-a-github-pages-site-with-jekyll %} {% link_in_list /about-github-pages-and-jekyll %} @@ -42,9 +38,7 @@ versions: {% link_in_list /adding-a-theme-to-your-github-pages-site-using-jekyll %} {% link_in_list /about-jekyll-build-errors-for-github-pages-sites %} {% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %} - {% topic_link_in_list /configuring-a-custom-domain-for-your-github-pages-site %} {% link_in_list /about-custom-domains-and-github-pages %} {% link_in_list /managing-a-custom-domain-for-your-github-pages-site %} {% link_in_list /troubleshooting-custom-domains-and-github-pages %} - diff --git a/translations/ja-JP/content/github/working-with-github-support/index.md b/translations/ja-JP/content/github/working-with-github-support/index.md index 791eee0a24..452b7d0d52 100644 --- a/translations/ja-JP/content/github/working-with-github-support/index.md +++ b/translations/ja-JP/content/github/working-with-github-support/index.md @@ -2,6 +2,7 @@ title: GitHub Support への相談 redirect_from: - /categories/working-with-github-support + - /forum versions: free-pro-team: '*' --- diff --git a/translations/ja-JP/content/graphql/README.md b/translations/ja-JP/content/graphql/README.md new file mode 100644 index 0000000000..f29fbc5131 --- /dev/null +++ b/translations/ja-JP/content/graphql/README.md @@ -0,0 +1,10 @@ +# GraphQL + +The `/content/graphql` directory is where the GitHub GraphQL API docs live! + +* The `/content/graphql/guides` and `/content/graphql/overview` directories contain articles that are human-editable. +* The `/content/graphql/reference` directory contains an article for each GraphQL data type used in the GitHub GraphQL API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/graphql/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/graphql/README.md`](/lib/graphql/README.md). + + **As a result, we cannot accept contributions to GraphQL API reference content in this repository.** diff --git a/translations/ja-JP/content/graphql/overview/explorer.md b/translations/ja-JP/content/graphql/overview/explorer.md index 4f7f3872fc..74540b78a4 100644 --- a/translations/ja-JP/content/graphql/overview/explorer.md +++ b/translations/ja-JP/content/graphql/overview/explorer.md @@ -7,6 +7,6 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +layout: graphql-explorer --- -GitHubのGraphQL Explorerには、https://developer.github.com/v4/explorerからアクセスできます。 diff --git a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-organizations.md b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-organizations.md index 115be164d9..64712068b4 100644 --- a/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-organizations.md +++ b/translations/ja-JP/content/insights/installing-and-configuring-github-insights/managing-organizations.md @@ -36,4 +36,4 @@ versions: {% data reusables.github-insights.add-organizations %} 4. {% data variables.product.prodname_insights %}から削除したいOrganizationをクリックしてください。 4. "Uninstall {% data variables.product.prodname_insights %}（{% data variables.product.prodname_insights %}のアンインストール）"の下で、**Uninstall（アンインストール）**をクリックしてください。 ![アンインストールボタン](/assets/images/help/insights/uninstall-button.png) -5. Click **OK**. +5. [**OK**] をクリックします。 diff --git a/translations/ja-JP/content/packages/guides/about-github-container-registry.md b/translations/ja-JP/content/packages/guides/about-github-container-registry.md new file mode 100644 index 0000000000..d3e6ae2cfa --- /dev/null +++ b/translations/ja-JP/content/packages/guides/about-github-container-registry.md @@ -0,0 +1,94 @@ +--- +title: 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 %} を利用すれば、パッケージを管理できるユーザやパッケージにアクセスできるユーザを、きめ細かく設定できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/about-github-container-registry + - /packages/managing-container-images-with-github-container-registry +versions: + free-pro-team: '*' +--- + +{% note %} + +**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." + +{% endnote %} + +### {% data variables.product.prodname_github_container_registry %} について + +{% data reusables.package_registry.container-registry-feature-highlights %} + +パッケージの使用についてのコンテキストを共有するには、{% data variables.product.prodname_dotcom %} でコンテナイメージをリポジトリにリンクできます。 詳しい情報については、「[リポジトリをコンテナイメージに接続する](/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. + +| | パッケージレジストリ | {% data variables.product.prodname_github_container_registry %} +| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | +| ホスト場所 | 1 つのリポジトリに複数のパッケージをホストできます。 | 1 つの Organization またはユーザアカウントに複数のコンテナをホストできます。 | +| 権限 | {% data reusables.package_registry.public-or-private-packages %} パッケージはリポジトリの権限を継承するので、{% data variables.product.prodname_dotcom %}のロールとTeamを使い、各パッケージをインストールしたり公開したりできる人を制限できます。 リポジトリの読み取り権限を持っている人は、パッケージを依存関係としてプロジェクトにインストールでき、書き込み権限を持っている人は新しいパッケージのバージョンを公開できます。 | コンテナイメージごとに、他のユーザが持つアクセスレベルを選択できます。 コンテナイメージへのアクセス権限は、Organization およびリポジトリの権限とは別になります。 | + 可視性 | {% data reusables.package_registry.public-or-private-packages %} | それぞれのコンテナイメージに可視性を設定できます。 プライベートコンテナイメージは、Organization 内でアクセス権を付与されたユーザおよび Team のみに表示されます。 パブリックコンテナは誰でも表示できます。 | 匿名アクセス | 該当なし | パブリックコンテナイメージには匿名でアクセスできます。 + +For more information, see "[About scopes and permissions for {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)." + +### サポートされているフォーマット + +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: + +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) + +{% data variables.product.prodname_github_container_registry %} は、コンテナを `ghcr.io/OWNER/IMAGE-NAME` にホストします。 + +| パッケージクライアント | 言語 | パッケージフォーマット | 説明 | +| ----------- | -- | ------------ | ---------------- | +| docker | なし | `Dockerfile` | Nodeのパッケージマネージャー | + + +#### Manifest Lists/Image Indexes + +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. + +### コンテナイメージの可視性とアクセス権限 + +コンテナイメージへのアクセス権限がある場合、コンテナイメージをプライべートまたはパブリックに設定できます。 パブリックイメージは匿名でアクセスでき、認証や CLI 経由でサインインすることなくプルできます。 + +あなたが管理者であれば、Organization レベルおよびリポジトリレベルに設定した権限とは別に、コンテナイメージに対してアクセス権限を付与することもできます。 + +ユーザアカウントが所有し公開しているコンテナイメージには、任意のユーザにアクセスロールを付与できます。 Organization が所有し公開しているコンテナイメージには、Organization 内の任意の Team にアクセスロールを付与できます。 + +| 権限ロール | アクセス権の内容 | +| ----- | ---------------------------------------------------------------------------------------------------- | +| Read | パッケージをダウンロードできます。
メタデータの読み取りができます。 | +| Write | このパッケージをアップロードおよびダウンロードできます。
パッケージのメタデータの読み取りおよび書き込みができます。 | +| Admin | このパッケージのアップロード、ダウンロード、削除、管理ができます。
パッケージのメタデータの読み取りおよび書き込みができます。
パッケージに権限を付与できます。 | + +詳しい情報については、「[コンテナイメージにアクセス制御と可視性を設定する](/packages/guides/configuring-access-control-and-visibility-for-container-images)」を参照してください。 + +### トークンについて + +パッケージをインストールあるいは公開するには、適切なスコープを持つトークンを使い、ユーザアカウントがそのリポジトリに対する適切な権限を持っていなければなりません。 + +| スコープ | 説明 | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `read:packages` | {% data variables.product.prodname_github_container_registry %}からのコンテナイメージのダウンロードとインストール | +| `write:packages` | {% data variables.product.prodname_github_container_registry %}へのコンテナイメージのアップロードと公開 | +| `delete:packages` | {% data variables.product.prodname_github_container_registry %}からの特定バージョンのプライベートまたはパブリックコンテナイメージの削除。 詳細は「[コンテナイメージを削除する](/packages/guides/deleting-a-container-image)」を参照してください。 | + +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)." + +詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token/)」と「[利用可能なスコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)」を参照してください。 + +### {% data variables.product.prodname_github_container_registry %}の支払いについて + +{% data reusables.package_registry.billing-for-container-registry %} + +### サポートへの連絡 + +{% data variables.product.prodname_github_container_registry %} に関するフィードバックや機能のリクエストがある場合は、[フィードバックフォーム](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages)でご連絡ください。 + +[連絡フォーム](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages)を使い、{% data variables.product.prodname_github_container_registry %}について{% data variables.contact.github_support %}に連絡してください。 + +* ドキュメンテーションに反する何らかの体験をした時. +* 漠然とした、あるいは不明確なエラーを体験した時. +* GDPR 違反、API キー、個人を識別できる情報といったセンシティブなデータを含むパッケージを公開した時。 diff --git a/translations/ja-JP/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md b/translations/ja-JP/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md new file mode 100644 index 0000000000..bbae5dc615 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md @@ -0,0 +1,69 @@ +--- +title: コンテナイメージのアクセス制御と可視性を設定する +intro: 'コンテナイメージに読み取り、書き込み、管理アクセス権限があるユーザと、{% data variables.product.prodname_dotcom %} 上のコンテナイメージの可視性を選択します。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### 個人アカウントにコンテナイメージへのアクセス権限を設定する + +ユーザアカウントが所有するコンテナイメージに対する管理者権限がある場合には、他のユーザに読み取り、書き込み、管理者ロールを割り当てることができます。 これらの権限ロールに関する詳しい情報については、[コンテナイメージの可視性とアクセス権限](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)」を参照してください。 + +{% data reusables.package_registry.package-settings-from-user-level %} +1. パッケージ設定ページで [**Invite teams or people**] をクリックして、アクセス権を付与するユーザの名前、ユーザ名、またはメールアドレスを入力します。 Team には、ユーザアカウントが所持するコンテナイメージのアクセス権限を与えることができません。 ![コンテナアクセス権の招待ボタン](/assets/images/help/package-registry/container-access-invite.png) +1. ユーザ名または Team 名の隣にある [Role] のドロップダウンメニューで、付与する権限レベルを選択します。 ![コンテナアクセス権のオプション](/assets/images/help/package-registry/container-access-control-options.png) + +選択したユーザには自動的にアクセス権限が与えられ、招待を承諾する必要はありません。 + +### Organization にコンテナイメージへのアクセス権限を設定する + +Organization が所有するコンテナイメージに対する管理者権限がある場合には、他のユーザや Team に読み取り、書き込み、管理者ロールを割り当てることができます。 これらの権限ロールに関する詳しい情報については、[コンテナイメージの可視性とアクセス権限](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)」を参照してください。 + +パッケージが Organization の所有でかつプライベートである場合、他の Organization のメンバーまたは Team にのみアクセス権を付与できます。 + +Organization イメージコンテナに対しては、Organization の管理者がパッケージを有効にしないと、可視性をパブリックに設定できません。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% data reusables.package_registry.package-settings-from-org-level %} +1. パッケージ設定ページで [**Invite teams or people**] をクリックして、アクセス権を付与するユーザの名前、ユーザ名、またはメールアドレスを入力します。 また、Organization から Team 名を入力して、全 Team メンバーにアクセスを付与することもできます。 ![コンテナアクセス権の招待ボタン](/assets/images/help/package-registry/container-access-invite.png) +1. ユーザ名または Team 名の隣にある [Role] のドロップダウンメニューで、付与する権限レベルを選択します。 ![コンテナアクセス権のオプション](/assets/images/help/package-registry/container-access-control-options.png) + +選択したユーザや Team には自動的にアクセス権限が与えられ、招待を承諾する必要はありません。 + +### 個人アカウントにコンテナイメージの可視性を設定する + +パッケージを最初に公開する際のデフォルトの可視性はプライベートで、パッケージを表示できるのは公開したユーザだけです。 アクセス設定を変更することで、プライベートやパブリックなコンテナイメージのアクセス権限を変更できます。 + +パブリックパッケージは認証なしに匿名でアクセスできます。 いったんパッケージをパブリックに設定すると、そのパッケージをプライベートに戻すことはできません。 + +{% data reusables.package_registry.package-settings-from-user-level %} +5. [Danger Zone] の下で、可視性の設定を選択します。 + - あらゆる人がコンテナイメージを表示できるようにするには、[**Make public**] をクリックします。 + {% warning %} + + **警告:** いったんパッケージをパブリックにすると、プライベートに戻すことはできません。 + + {% endwarning %} + - 指定したユーザだけがコンテナイメージを表示できるようにするには、[**Make private**] をクリックします。 ![コンテナ可視性のオプション](/assets/images/help/package-registry/container-visibility-option.png) + +### Organization にコンテナイメージの可視性を設定する + +パッケージを最初に公開する際のデフォルトの可視性はプライベートで、パッケージを表示できるのは公開したユーザだけです。 アクセス設定を使用して、コンテナイメージに対するさまざまなアクセスロールをユーザや Team に付与できます。 + +パブリックパッケージは認証なしに匿名でアクセスできます。 いったんパッケージをパブリックに設定すると、そのパッケージをプライベートに戻すことはできません。 + +Organization イメージコンテナに対しては、Organization の管理者がパブリックパッケージを有効にしないと、可視性をパブリックに設定できません。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% data reusables.package_registry.package-settings-from-org-level %} +5. [Danger Zone] の下で、可視性の設定を選択します。 + - あらゆる人がコンテナイメージを表示できるようにするには、[**Make public**] をクリックします。 + {% warning %} + + **警告:** いったんパッケージをパブリックにすると、プライベートに戻すことはできません。 + + {% endwarning %} + - 指定したユーザだけがコンテナイメージを表示できるようにするには、[**Make private**] をクリックします。 ![コンテナ可視性のオプション](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/ja-JP/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md new file mode 100644 index 0000000000..2ac583d27e --- /dev/null +++ b/translations/ja-JP/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -0,0 +1,195 @@ +--- +title: GitHub Packagesで利用するために Apache Maven を設定する +intro: '{% data variables.product.prodname_registry %} にパッケージを公開するよう Apache Mavenを設定し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係としてJavaプロジェクトで利用できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。 + +### {% data variables.product.prodname_registry %} への認証を行う + +{% data reusables.package_registry.authenticate-packages %} + +#### 個人アクセストークンでの認証 + +{% data reusables.package_registry.required-scopes %} + +*~/.m2/settings.xml*ファイルを編集して個人アクセストークンを含めることで、Apache Mavenで{% data variables.product.prodname_registry %}の認証を受けられます。 *~/.m2/settings.xml*ファイルがないなら新しく作成してください。 + +`servers`タグの中に、子として`server`タグを`id`付きで追加し、*USERNAME*を{% data variables.product.prodname_dotcom %}のユーザ名で、*TOKEN*を個人アクセストークンで置き換えてください。 + +`repositories`の中で、リポジトリの`id`をクレデンシャルを含む`server`タグに追加した`id`にマッピングして、リポジトリを設定してください。 Replace {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}*REPOSITORY* with the name of the repository you'd like to publish a package to or install a package from, and *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. + +複数のリポジトリとやりとりをしたい場合には、それぞれのリポジトリを`repositories`タグの子の個別の`repository`に追加し、それぞれの`id`を`servers` タグのクレデンシャルにマッピングできます。 + +{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} + +{% if enterpriseServerVersions contains currentVersion %} +パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 +{% endif %} + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` +{% endif %} + +#### `GITHUB_TOKEN`での認証 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### パッケージを公開する + +{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。 + +同じリポジトリに複数のパッケージを公開したい場合には、そのリポジトリのURLを*pom.xml*ファイルの``要素に含めてください。 {% data variables.product.prodname_dotcom %} は、このこのフィールドを元にしてリポジトリを照合します。 リポジトリ名も`distributionManagement`要素の一部なので、複数のパッケージを同じリポジトリに公開するための追加手順はありません。 + +パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 + +1. パッケージディレクトリ内にある*pom.xml*ファイルの`distributionManagement`要素を編集し、`OWNER`をリポジトリを所有しているユーザもしくはOrganizationアカウントの名前で、`REPOSITORY`をプロジェクトを含むリポジトリの名前で置き換えてください。 + +{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. + {% if enterpriseServerVersions contains currentVersion %} + パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 + {% endif %} + ``` + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + ``` + {% if enterpriseServerVersions contains currentVersion %} + たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + ``` + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + ``` + {% endif %} +2. パッケージを公開します。 + + ```shell + $ mvn deploy + ``` + +{% data reusables.package_registry.viewing-packages %} + +### パッケージをインストールする + +{% data variables.product.prodname_registry %}からApache Mavenパッケージをインストールするには、*pom.xml*ファイルを編集してパッケージを依存関係として含めてください。 複数のリポジトリからパッケージをインストールしたい場合は、それぞれについて`repository`タグを追加してください。 プロジェクト内での*pom.xml*ファイルの利用に関する詳しい情報については、Apache Mavenドキュメンテーション中の「[ Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)」を参照してください。 + +{% data reusables.package_registry.authenticate-step %} +2. パッケージの依存関係をプロジェクトの*pom.xml*ファルの`dependencies`要素に追加し、`com.example:test`をパッケージで置き換えてください。 + + ``` + + + com.example + test + 1.0.0-SNAPSHOT + + + ``` +3. パッケージをインストールします。 + + ```shell + $ mvn install + ``` + +### 参考リンク + +- [{% data variables.product.prodname_registry %}で利用するためのGradleの設定](/packages/guides/configuring-gradle-for-use-with-github-packages) +- [パッケージの削除](/packages/manage-packages/deleting-a-package/) diff --git a/translations/ja-JP/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-docker-for-use-with-github-packages.md new file mode 100644 index 0000000000..4068888e07 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -0,0 +1,223 @@ +--- +title: GitHub Packagesで利用するために Docker を設定する +intro: 'Docker クライアントが、{% data variables.product.prodname_registry %} を利用して Docker イメージを公開および取得できるよう設定できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。 + +### {% data variables.product.prodname_registry %} への認証を行う + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +`docker` loginコマンドを使い、Dockerで{% data variables.product.prodname_registry %}の認証を受けることができます。 + +{% if enterpriseServerVersions contains currentVersion %} + +Docker レジストリを {% data variables.product.prodname_registry %} で使用する前に、{% data variables.product.product_location %} のサイト管理者がインスタンスに対し Docker のサポートとand Subdomain Isolation を有効化する必要があります。 詳しい情報については、「[Enterprise 向けの GitHub Packages を管理する](/enterprise/admin/packages)」を参照してください。 + +{% endif %} + +### {% data variables.product.prodname_registry %} への認証を行う + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% data reusables.package_registry.authenticate-packages %} + +#### 個人アクセストークンでの認証 + +{% data reusables.package_registry.required-scopes %} + +`docker` loginコマンドを使い、Dockerで{% data variables.product.prodname_registry %}の認証を受けることができます。 + +クレデンシャルをセキュアに保つ貯めに、個人アクセストークンは自分のコンピュータのローカルファイルに保存し、ローカルファイルからトークンを読み取るDockerの`--password-stdin`フラグを使うことをおすすめします。 + +{% if currentVersion == "free-pro-team@latest" %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + ``` +{% endraw %} +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +{% raw %} + ```shell + $ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# OWNER/REPO/IMAGE_NAMEでイメージにタグ付けする +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# {{ site.data.variables.product.prodname_registry }}にイメージをプッシュ +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` +{% endraw %} +{% endif %} + +To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. + +詳しい情報については「[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)」を参照してください。 + +#### `GITHUB_TOKEN`での認証 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publishing an image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% note %} + +**Note:** Image names must only use lowercase letters. + +{% endnote %} + +{% data variables.product.prodname_registry %} は、リポジトリごとに複数の最上位 Docker イメージをサポートしています。 リポジトリは任意の数のイメージタグを持つことができます。 10GB以上のDockerイメージの公開やインストールの際には、サービスのパフォーマンスが低下するかもしれず、各レイヤーは5GBが上限です。 詳しい情報については、Dockerのドキュメンテーションの「[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)」を参照してください。 + +{% data reusables.package_registry.viewing-packages %} + +1. `docker images`を使って、Dockerイメージのイメージ名とIDを確認してください。 + ```shell + $ docker images + > < > + > REPOSITORY TAG IMAGE ID CREATED SIZE + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + ``` +2. 新しいDockerイメージを初めて公開し、`monalisa`という名前にできます。 +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} +3. パッケージ用のDockerイメージをまだ構築していないなら、イメージを構築してください。 *OWNER*をリポジトリを所有しているユーザあるいはOrganizationのアカウント名で、*REPOSITORY*をプロジェクトを含むリポジトリ名で、*IMAGE_NAME*をパッケージもしくはイメージの名前で、*VERSION*をビルド時点のパッケージバージョンで置き換え、イメージが現在のワーキングディレクトリにないなら*PATH*をイメージへのパスで置き換えてください。 +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% else %} + ```shell + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} +4. イメージを +{% data variables.product.prodname_registry %}. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} + {% note %} + + **ノート:** イメージのプッシュは`IMAGE_NAME:SHA`を使うのではなく、`IMAGE_NAME:VERSION`を使って行ってください。 + + {% endnote %} + +#### Dockerイメージのプッシュの例 + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +`monalisa`イメージのバージョン1.0を、イメージIDを使って`octocat/octo-app`に公開できます。 + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# OWNER/REPO/IMAGE_NAMEでイメージにタグ付けする +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# {% data variables.product.prodname_registry %}にイメージをプッシュ +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} + +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` + +{% endif %} + +新しいDockerイメージを初めて公開し、`monalisa`という名前にできます。 + +{% if currentVersion == "free-pro-team@latest" %} +```shell +# docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION でイメージを構築 +# Dockerfileはカレントワーキングディレクトリ (.)にあるものとする +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} +```shell +# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` +{% endif %} + +### Downloading an image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %} and *TAG_NAME* with tag for the image you want to install. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% else %} +```shell +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} + +{% note %} + +**ノート:** イメージのプルは`IMAGE_NAME:SHA`を使うのではなく、`IMAGE_NAME:VERSION`を使って行ってください。 + +{% endnote %} + +### 参考リンク + +- [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package/) diff --git a/translations/ja-JP/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md new file mode 100644 index 0000000000..fabc683365 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -0,0 +1,197 @@ +--- +title: GitHub Packagesで利用するために`dotnet` CLIを設定する +intro: '{% data variables.product.prodname_registry %} にNuGetパッケージを公開し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係として .Net プロジェクトで利用するよう`dotnet`コマンドラインインターフェース（CLI）を設定できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages + - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。 + +### {% data variables.product.prodname_registry %} への認証を行う + +{% data reusables.package_registry.authenticate-packages %} + +#### 個人アクセストークンでの認証 + +{% data reusables.package_registry.required-scopes %} + +`dotnet`コマンドラインインターフェース（CLI）で{% data variables.product.prodname_registry %}に認証を受けるには、プロジェクトディレクトリに*nuget.config*ファイルを作成し、{% data variables.product.prodname_registry %}をソースとして`dotnet` CLIクライアントの`packageSources`の下に指定してください。 + +以下のように置き換えてください。 +- `USERNAME`を{% data variables.product.prodname_dotcom %}上のユーザアカウント名で。 +- `TOKEN`を個人アクセストークンで。 +- `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} +- `HOSTNAME`を、{% data variables.product.prodname_ghe_server %}インスタンスのホスト名で。 + +パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 +{% endif %} + +```xml + + + + + + + + + + + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + +```xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://github.com/octo-org/octo-cats-and-dogs + + + +``` +{% endif %} + +#### `GITHUB_TOKEN`での認証 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### パッケージを公開する + +*nuget.config*で認証を受けることによって、パッケージを{% data variables.product.prodname_registry %}に公開できます。 公開の際には、*nuget.config*認証ファイルで使用する*csproj*ファイル中で、`OWNER`に同じ値を使わなければなりません。 *.csproj*ファイル中でバージョン番号を指定もしくはインクリメントし、`dotnet pack`コマンドを使ってそのバージョンのための*.nuspec*ファイルを作成してください。 For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. 新しいプロジェクトを作成してください。 + ```shell + dotnet new console --name OctocatApp + ``` +3. プロジェクト固有の情報をプロジェクトファイルに追加してください。プロジェクトファイルは*.csproj*で終わります。 以下のように置き換えてください。 + - `OWNER`を、プロジェクトを含むリポジトリを所有しているユーザもしくはOrganizationアカウント名で。 + - `REPOSITORY`を、公開したいパッケージを含むリポジトリの名前で。 + - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion %} + - `HOSTNAME`を、{% data variables.product.prodname_ghe_server %}インスタンスのホスト名で。{% endif %} + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + ``` +4. プロジェクトをパッケージ化してください。 + ```shell + dotnet pack --configuration Release + ``` + +5. *nuget.config*ファイル中で指定した`key`を使ってパッケージを公開してください。 + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" + ``` + +### 同じリポジトリへの複数パッケージの公開 + +複数のパッケージを同じリポジトリに公開するには、同じ{% data variables.product.prodname_dotcom %}リポジトリURLをすべての*.csproj*プロジェクトファイル中の`RepositoryURL`フィールドに含めることができます。 {% data variables.product.prodname_dotcom %}は、そのフィールドに基づいてリポジトリをマッチします。 + +たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + +``` xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +### パッケージをインストールする + +プロジェクトで{% data variables.product.prodname_dotcom %}からパッケージを利用するのは、*nuget.org*からパッケージを使用するのに似ています。 パッケージの依存関係を*.csproj*ファイルに追加し、パッケージ名とバージョンを指定してください。 For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. + +{% data reusables.package_registry.authenticate-step %} + +2. パッケージを利用するには、*.csproj*プロジェクトファイルに`ItemGroup`を追加し、`PackageReference`フィールドを設定してください。`OctokittenApp`パッケージをパッケージの依存関係で、`1.0.0`を使いたいバージョンで置き換えてください。 + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + ``` + +3. `restore`コマンドでパッケージをインストールしてください。 + ```shell + dotnet restore + ``` + +### 参考リンク + +- [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package/) diff --git a/translations/ja-JP/content/packages/guides/configuring-gradle-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-gradle-for-use-with-github-packages.md new file mode 100644 index 0000000000..1c65996042 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/configuring-gradle-for-use-with-github-packages.md @@ -0,0 +1,215 @@ +--- +title: GitHub Packagesで利用するためにGradleを設定する +intro: '{% data variables.product.prodname_registry %} にパッケージを公開し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係としてJavaプロジェクトで利用するようGradleを設定できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。 + +### {% data variables.product.prodname_registry %} への認証を行う + +{% data reusables.package_registry.authenticate-packages %} + +#### 個人アクセストークンでの認証 + +{% data reusables.package_registry.required-scopes %} + +Gradle GroovyもしくはKotlin DSLを使って、Gradleで{% data variables.product.prodname_registry %}に認証を受けることができます。それには、*build.gradle*ファイル（Gradle Groovy）もしくは*build.gradle.kts*ファイル（Kotlin DSL）ファイルを編集して、個人アクセストークンを含めます。 リポジトリ中の単一のパッケージもしくは複数パッケージを認識するようにGradle Groovy及びKotlin DSLを設定することもできます。 + +{% if enterpriseServerVersions contains currentVersion %} +*REGISTRY-URL* をインスタンスの Maven レジストリの URL に置き換えます。 インスタンスで Subdomain Isolation が有効になっている場合は、`maven.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/maven` を使用します。 いずれの場合でも、*HOSTNAME* を +{% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。 +{% endif %} + +*USERNAME*を{% data variables.product.prodname_dotcom %}のユーザ名で、*TOKEN*を個人アクセストークンで、*REPOSITORY*を公開したいパッケージを含むリポジトリの名前で、*OWNER*をリポジトリを所有する{% data variables.product.prodname_dotcom %}のユーザもしくはOrganizationアカウント名で置き換えてください。 Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. + +{% note %} + +**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} 例として「[{% data variables.product.prodname_registry %}で使用するためのApache Mavenの設定](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)」を参照してください。 + +{% endnote %} + +##### リポジトリ中の単一のパッケージのためにGradle Groovyを使う例 + +```shell +plugins { + id("maven-publish") +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } +} +``` + +##### 同じリポジトリ中の複数のパッケージのためにGradle Groovyを使う例 + +```shell +plugins { + id("maven-publish") apply false +} + +subprojects { + apply plugin: "maven-publish" + publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } + } +} +``` + +##### 同じリポジトリ中の単一パッケージのためにKotlin DSLを使う例 + +```shell +plugins { + `maven-publish` +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } +} +``` + +##### 同じリポジトリ中の複数パッケージのためにKotlin DSLを使う例 + +```shell +plugins { + `maven-publish` apply false +} + +subprojects { + apply(plugin = "maven-publish") + configure { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } + } +} +``` + + #### `GITHUB_TOKEN`での認証 + + {% data reusables.package_registry.package-registry-with-github-tokens %} + + Mavenで `GITHUB_TOKEN` を使用する方法の詳細については、「[MavenでJavaパッケージを公開](/actions/language-and-framework-guides/publishing-java-packages-with-maven#publishing-packages-to-github-packages) 」を参照してください。 + + ### パッケージを公開する + + {% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test` {% data variables.product.prodname_registry %}リポジトリ内の`com.example.test`という名前のパッケージを公開します。 + + {% data reusables.package_registry.viewing-packages %} + + {% data reusables.package_registry.authenticate-step %} + 2. パッケージを作成した後、そのパッケージを公開できます。 + + ```shell + $ gradle publish + ``` + +### パッケージをインストールする + +プロジェクトの依存関係としてパッケージを追加することで、パッケージをインストールできます。 詳しい情報については、Gradleのドキュメンテーションの 「[ Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)」を参照してください。 + +{% data reusables.package_registry.authenticate-step %} +2. *build.gradle*ファイル（Gradle Groovy）もしくは*build.gradle.kts*ファイル（Kotlin DSL）にパッケージの依存関係を追加してください。 + + Example using Gradle Groovy: + ```shell + dependencies { + implementation 'com.example:package' + } + ``` + Kotlin DSLの例： + ```shell + dependencies { + implementation("com.example:package") + } + ``` + +3. *build.gradle*ファイル（Gradle Groovy）もしくは*build.gradle.kts*ファイル（Kotlin DSL）にmavenプラグインを追加してください。 + + Example using Gradle Groovy: + ```shell + plugins { + id 'maven' + } + ``` + Kotlin DSLの例： + ```shell + plugins { + `maven` + } + ``` + + 3. パッケージをインストールします。 + + ```shell + $ gradle install + ``` + +### 参考リンク + +- [{% data variables.product.prodname_registry %}で利用するためのApache Mavenの設定](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages) +- [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package/) diff --git a/translations/ja-JP/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-npm-for-use-with-github-packages.md new file mode 100644 index 0000000000..6f1973eb33 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -0,0 +1,203 @@ +--- +title: GitHub Packagesで利用するためにnpmを設定する +intro: '{% data variables.product.prodname_registry %} にパッケージを公開するよう npm を設定し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係として npm プロジェクトで利用できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。 + +### {% data variables.product.prodname_registry %} への認証を行う + +{% data reusables.package_registry.authenticate-packages %} + +#### 個人アクセストークンでの認証 + +{% data reusables.package_registry.required-scopes %} + +ユーザごとの*~/.npmrc*ファイルを編集して個人アクセストークンを含めるか、コマンドラインからユーザ名と個人アクセストークンを使ってnpmにログインすることによって、npmで{% data variables.product.prodname_registry %}の認証を受けられます。 + +To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*TOKEN* with your personal access token. *~/.npmrc*ファイルが存在しない場合は、新しく作成してください。 + +{% if enterpriseServerVersions contains currentVersion %} +パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 +{% endif %} + +```shell +//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN +``` + +{% if enterpriseServerVersions contains currentVersion %} +たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + +```shell +$ npm login --registry=https://npm.pkg.github.com +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +npmにログインすることで認証を受けるには、`npm login`コマンドを使ってください。*USERNAME*は{% data variables.product.prodname_dotcom %}のユーザ名で、*TOKEN*は個人アクセストークンで、*PUBLIC-EMAIL-ADDRESS*はメールアドレスで置き換えてください。 + +If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}. + +{% if enterpriseServerVersions contains currentVersion %} +パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 +{% endif %} + +```shell +$ npm login --scope=@OWNER --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} + +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` + +{% if enterpriseServerVersions contains currentVersion %} +たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + +```shell +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +#### `GITHUB_TOKEN`での認証 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### パッケージを公開する + +{% note %} + +**Note:** Package names and scopes must only use lowercase letters. + +{% endnote %} + +デフォルトでは、{% data variables.product.prodname_registry %}は*package.json*ファイルのnameフィールドで指定された{% data variables.product.prodname_dotcom %}のリポジトリにパッケージを公開します。 たとえば`@my-org/test`という名前のパッケージを{% data variables.product.prodname_dotcom %}リポジトリの`my-org/test`に公開します。 パッケージディレクトリに*README.md*ファイルを置くことで、パッケージリスティングページのためのまとめを追加できます。 詳しい情報については、npmのドキュメンテーション中の「[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)」及び「[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)」を参照してください。 + +`URL`フィールドを*package.json*ファイルに含めることで、同じ{% data variables.product.prodname_dotcom %}のリポジトリに複数のパッケージを公開できます。 詳しい情報については「[同じリポジトリへの複数パッケージの公開](#publishing-multiple-packages-to-the-same-repository)」を参照してください。 + +プロジェクト内にあるローカルの *.npmrc* ファイルか、*package.json* の `publishConfig` オプションを使って、スコープのマッピングを設定できます。 {% data variables.product.prodname_registry %}はスコープ付きのnpmパッケージのみをサポートしています。 スコープ付きパッケージには、`@owner/name` というフォーマットの名前が付いています。 スコープ付きパッケージの先頭には常に `@` 記号が付いています。 You may need to update the name in your *package.json* to use the scoped name. たとえば、`"name": "@codertocat/hello-world-npm"` のようになります。 + +{% data reusables.package_registry.viewing-packages %} + +#### ローカルの*.npmrc*ファイルを使ったパッケージの公開 + +*.npmrc*ファイルを使って、プロジェクトのスコープのマッピングを設定できます。 *.npmrc*ファイル中で{% data variables.product.prodname_registry %} URLとアカウントオーナーを使い、{% data variables.product.prodname_registry %}がどこへパッケージリクエストをまわせばいいか把握できるようにしてください。 *.npmrc*を使う事で、他の開発者が{% data variables.product.prodname_registry %}の代わりにうっかりパッケージをnpmjs.orgに公開してしまうのを避けることができます。 + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +1. プロジェクトの*package.json*中のパッケージ名を確認してください。 `name`フィールドは、スコープとパッケージの名前を含まなければなりません。 たとえば、パッケージの名前が "test" で、それを "My-org" という +{% data variables.product.prodname_dotcom %} Organizationに公開する場合、*package.json*の`name`フィールドは `@my-org/test`とする必要があります。 +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +#### *package.json*ファイル中の`publishConfig`を利用したパッケージの公開 + +*package.json*ファイル中の`publishConfig`要素を使い、パッケージを公開したいレジストリを指定できます。 詳しい情報についてはnpmドキュメンテーションの「[Configの公開](https://docs.npmjs.com/files/package.json#publishconfig)」を参照してください。 + +1. パッケージの*package.json*ファイルを編集して、`publishConfig`エントリを含めてください。 + {% if enterpriseServerVersions contains currentVersion %} + パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 + {% endif %} + ```shell + "publishConfig": { + "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + }, + ``` + {% if enterpriseServerVersions contains currentVersion %} + たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + ```shell + "publishConfig": { + "registry":"https://HOSTNAME/_registry/npm/" + }, + ``` + {% endif %} +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +### 同じリポジトリへの複数パッケージの公開 + +複数のパッケージを同じリポジトリに公開するには、{% data variables.product.prodname_dotcom %}リポジトリのURLを各パッケージの*package.json*ファイル中の`repository`フィールドに含めることができます。 + +リポジトリのURLが正しいことを確認するには、REPOSITORYを公開したいパッケージを含むリポジトリ名で、OWNERをリポジトリを所有している{% data variables.product.prodname_dotcom %}のユーザもしくはOrganizationアカウント名で置き換えてください。 + +{% data variables.product.prodname_registry %} は、パッケージ名の代わりに、このURLを元にしてリポジトリを照合します。 + +```shell +"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", +``` + +### パッケージをインストールする + +プロジェクトの*package.json*ファイルに依存関係としてパッケージを追加することで、{% data variables.product.prodname_registry %}からパッケージをインストールできます。 For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation. + +デフォルトでは、パッケージは1つのOrganizationから追加できます。 For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." + +また、*.npmrc*ファイルをプロジェクトに追加して、パッケージのインストールのすべてのリクエストが{% data variables.product.prodname_registry %}を経由するようにしなければなりません。 すべてのパッケージリクエストを{% data variables.product.prodname_registry %}を経由させると、*npmjs.com*からスコープ付き及びスコープ付きではないパッケージの両方を利用できます。 詳しい情報については npm ドキュメンテーションの「[npm-scope](https://docs.npmjs.com/misc/scope)」を参照してください。 + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +4. インストールしているパッケージを使うには、プロジェクトの*package.json*を設定してください。 {% data variables.product.prodname_registry %}のためにパッケージの依存関係を*package.json*ファイルに追加するには、`@my-org/server`というように完全なスコープ付きのパッケージ名を指定してください。 *npmjs.com*からのパッケージについては、`@babel/core`あるいは`@lodash`というような完全な名前を指定してください。 たとえば、以下の*package.json*は`@octo-org/octo-app`パッケージを依存関係として使っています。 + + ``` + { + "name": "@my-org/server", + "version": "1.0.0", + "description": "Server app that uses the @octo-org/octo-app package", + "main": "index.js", + "author": "", + "license": "MIT", + "dependencies": { + "@octo-org/octo-app": "1.0.0" + } + } + ``` +5. パッケージをインストールします。 + + ```shell + $ npm install + ``` + +#### 他のOrganizationからのパッケージのインストール + +デフォルトでは、1つのOrganizationからのみ{% data variables.product.prodname_registry %}パッケージを利用できます。 If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. + +{% if enterpriseServerVersions contains currentVersion %} +パッケージの作成に関する詳しい情報については[maven.apache.orgのドキュメンテーション](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)を参照してください。 +{% endif %} + +```shell +registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}/OWNER +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +``` + +{% if enterpriseServerVersions contains currentVersion %} +たとえば、以下の*OctodogApp*と*OctocatApp*は同じリポジトリに公開されます。 + +```shell +registry=https://HOSTNAME/_registry/npm/OWNER +@OWNER:registry=https://HOSTNAME/_registry/npm/ +@OWNER:registry=https://HOSTNAME/_registry/npm/ +``` +{% endif %} + +### 参考リンク + +- [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package/) diff --git a/translations/ja-JP/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/ja-JP/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md new file mode 100644 index 0000000000..dc4df376b5 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -0,0 +1,148 @@ +--- +title: GitHub Packagesで利用するために RubyGems を設定する +intro: '{% data variables.product.prodname_registry %} にパッケージを公開し、{% data variables.product.prodname_registry %} に保存されたパッケージを依存関係としてBundlerを使うRubyのプロジェクトで利用するよう、RubyGemsを設定できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.default-name %} たとえば、{% data variables.product.prodname_dotcom %}は`OWNER/test`というリポジトリ内の`com.example:test`という名前のパッケージを公開します。 + +### 必要な環境 + +- rubygems 2.4.1 以上. rubygemsのバージョンは以下のようにすればわかります。 + + ```shell + $ gem --version + ``` + + - Bundler 1.6.4 以上. Bundlerのバージョンは以下のようにすれば分かります。 + ```shell + $ bundle --version + Bundler version 1.13.7 + ``` + + - 複数の認証情報を扱うには、keycutter をインストールしてください. keycutterは以下のようにすればインストールできます。 + ```shell + $ gem install keycutter + ``` + +### {% data variables.product.prodname_registry %} への認証を行う + +{% data reusables.package_registry.authenticate-packages %} + +#### 個人アクセストークンでの認証 + +{% data reusables.package_registry.required-scopes %} + +gemの公開なら*~/.gem/credentials*ファイルを編集することで、単一のgemのインストールなら*~/.gemrc*ファイルを編集することで、Bundlerを使って1つ以上のgemを追跡してインストールするなら*~/.gemrc*ファイルを編集することで、RubyGemsで{% data variables.product.prodname_registry %}に認証を受けることができます。 + +新しいgemsを公開するには、*~/.gem/credentials*ファイルを編集して個人アクセストークンを含めることによって、RubyGemsで{% data variables.product.prodname_registry %}に認証を受けなければなりません。 *~/.gem/credentials*ファイルが存在しない場合、新しく作成してください。 + +たとえば、*~/.gem/credentials*を作成もしくは編集して、以下を含めてください。*TOKEN*は個人アクセストークンで置き換えてください。 + +```shell +gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" } +``` + +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` with the name of the user or organization account that owns the repository containing your project.{% if enterpriseServerVersions contains currentVersion %} + - `REGISTRY-URL` をインスタンスの Rubygems レジストリの URL で。 インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、 *HOSTNAME* を {% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。 +{% endif %} + +*~/.gemrc*ファイルがないなら、以下の例を使って新しい*~/.gemrc*ファイルを作成してください。 + +```shell +--- +:backtrace: false +:bulk_threshold: 1000 +:sources: +- https://rubygems.org/ +- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ +:update_sources: true +:verbose: true + +``` + +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. インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、 *HOSTNAME* を {% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。{% endif %} + +```shell +$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN +``` + +#### `GITHUB_TOKEN`での認証 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### パッケージを公開する + +{% data reusables.package_registry.default-name %} たとえば、`octo-gem`を`octo-org`というOrganizationに公開するなら、{% 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. *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. インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、 *HOSTNAME* を {% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。{% endif %} + + ```shell + $ gem push --key github \ + --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem + ``` + +### 同じリポジトリへの複数パッケージの公開 + +複数のgemを同じリポジトリに公開したい場合は、{% data variables.product.prodname_dotcom %}リポジトリの`gem.metadata`にある`github_repo`フィールドに、URL を記述できます。 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.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } +``` + +### パッケージをインストールする + +{% data variables.product.prodname_registry %}からのgemsは、*rubygems.org*からのgemsを使うのと同じように利用できます。 {% data variables.product.prodname_dotcom %}ユーザあるいはOrganizationをソースとして*~/.gemrc*ファイルに追加するか、Bundlerを使い、*Gemfile*を編集することで、{% data variables.product.prodname_registry %}の認証を受けなければなりません。 + +{% data reusables.package_registry.authenticate-step %} +2. Bundlerについては、{% data variables.product.prodname_dotcom %}ユーザもしくはOrganizationをソースとして*Gemfile*に追加して、この新しいソースからgemsをフェッチするようにしてください。 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. インスタンスで Subdomain Isolation が有効になっている場合は、`rubygems.HOSTNAME` を使用します。 インスタンスで Subdomain Isolation が無効になっている場合は、`HOSTNAME/_registry/rubygems` を使用します。 いずれの場合でも、 *HOSTNAME* を {% data variables.product.prodname_ghe_server %} インスタンスのホスト名に置き換えてください。{% endif %} + + ``` + source "https://rubygems.org" + + gem "rails" + + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do + gem "GEM NAME" + end + ``` + +3. 1.7.0以前のバージョンのBundlerの場合、新しいグローバルな`source`を追加する必要があります。 Bundlerの利用に関する詳しい情報については[bundler.ioのドキュメンテーション](http://bundler.io/v1.5/gemfile.html)を参照してください。 + + ``` + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" + source "https://rubygems.org" + + gem "rails" + gem "GEM NAME" + ``` + +4. パッケージをインストールしてください。 + ```shell + $ gem install octo-gem --version "0.1.1" + ``` + +### 参考リンク + +- [パッケージの削除](/packages/publishing-and-managing-packages/deleting-a-package/) diff --git a/translations/ja-JP/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/ja-JP/content/packages/guides/connecting-a-repository-to-a-container-image.md new file mode 100644 index 0000000000..207f85ba18 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -0,0 +1,83 @@ +--- +title: リポジトリをコンテナイメージに接続する +intro: 'ローカルおよび {% data variables.product.prodname_dotcom %} において、リポジトリをコンテナイメージにリンクできます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image +versions: + free-pro-team: '*' +--- + +コンテナイメージをリポジトリに接続すると、パッケージのランディングページには、README などリポジトリからの情報やリンクが表示されます。 + +リポジトリとコンテナイメージを {% data variables.product.prodname_dotcom %} 上で接続するには、それらが {% data variables.product.prodname_dotcom %} 上で同じオーナーを共有している必要があります。 たとえば、以下の例では `my_repo` と `hello_docker` が、同じ `monalisa` というユーザに所有されています。 +```shell +https://github.com/monalisa/my_repo +https://github.com/monalisa/hello_docker +``` + +### リポジトリをユーザが所有するコンテナに {% data variables.product.prodname_dotcom %} で接続する + +{% data reusables.package_registry.package-settings-from-user-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### リポジトリを Organization が所有するコンテナと {% data variables.product.prodname_dotcom %} で接続する + +{% data reusables.package_registry.package-settings-from-org-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### リポジトリをコンテナイメージにコマンドラインで接続する + +1. Dockerfile に以下の行を追加します。`OWNER` と `REPO` は、あなたの情報に置き換えてください。 + + ```shell + LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + ``` + たとえば、あなたのユーザ名が `monalisa` で、`my-repo` を所有している場合は、以下の行を Dockerfile に追加します。 + ```shell + LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + ``` + 詳しい情報については、公式の Docker ドキュメンテーションの「[LABEL](https://docs.docker.com/engine/reference/builder/#label)」、および `opencontainers/image-spec` リポジトリの「[事前定義されたアノテーションキー](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)」を参照してください。 + +2. あなたのコンテナイメージを構築します。 この連では、カレントディレクトリ内の Dockerfile からイメージを構築し、イメージ名を `hello_docker` とします。 + + ```shell + $ docker build -t hello_docker . + ``` +3. 必要に応じて、タグ付けする Docker イメージの情報を確認します。 + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +4. Docker イメージを任意のイメージ名とホスティング先でタグ付けします。 + ```shell + $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG + ``` + 例: + ```shell + $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest + ``` + +5. まだ {% data variables.product.prodname_github_container_registry %} への認証を行っていない場合には、 + +{% data variables.product.prodname_github_container_registry %}. 詳しい情報については 「[GitHub Container Registry への認証を行う](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-github-container-registry)」を参照してください。 + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + > Login Succeeded + ``` + {% endraw %} +6. コンテナイメージを {% data variables.product.prodname_github_container_registry %} にプッシュします。 + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG + ``` + 例: + ```shell + $ docker push ghcr.io/monalisa/hello_docker:latest + ``` diff --git a/translations/ja-JP/content/packages/guides/container-guides-for-github-packages.md b/translations/ja-JP/content/packages/guides/container-guides-for-github-packages.md new file mode 100644 index 0000000000..31b8f63889 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/container-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Container guides for GitHub Packages +shortTitle: Container guides for GitHub Packages +intro: 'You can publish and retrieve Docker images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/ja-JP/content/packages/guides/deleting-a-container-image.md b/translations/ja-JP/content/packages/guides/deleting-a-container-image.md new file mode 100644 index 0000000000..9d74cc5115 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/deleting-a-container-image.md @@ -0,0 +1,33 @@ +--- +title: コンテナイメージを削除する +intro: 'GraphQL を使って、あるいは {% data variables.product.prodname_dotcom %} 上でプライベートパッケージのバージョンを削除できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### パッケージの削除について + +{% data variables.product.prodname_dotcom %} 上のコンテナイメージ全体または特定のバージョンを削除できます。 コンテナイメージを削除するには、UI を使用する必要があります。 GraphQL を使用したコンテナイメージの削除は、現時点ではサポートされていません。 + +コンテナイメージを削除するには、そのコンテナイメージの管理権限が必要です。 + +パブリックパッケージを削除する場合、そのパッケージに依存するプロジェクトを破壊する可能性があることに注意してください。 + +### {% data variables.product.prodname_dotcom %} 上でユーザが所持するコンテナイメージのバージョンを削除する + +{% data reusables.package_registry.package-settings-from-user-level %} +5. 左にある [**Manage versions**] をクリックします。 +5. 削除したいバージョンの右で**Delete（削除）**をクリックしてください。 ![パッケージの削除ボタン](/assets/images/help/package-registry/delete-package-button.png) +6. 削除を確認するために、パッケージ名を入力して**I understand the consequences, delete this version（生じることを理解したので、このバージョンを削除してください）**をクリックしてください。 ![パッケージの削除の確認ボタン](/assets/images/help/package-registry/confirm-package-deletion.png) + +### {% data variables.product.prodname_dotcom %} 上で Organization が所持するコンテナイメージのバージョンを削除する + +{% data reusables.package_registry.package-settings-from-org-level %} +5. 左にある [**Manage versions**] をクリックします。 +5. 削除したいバージョンの右で**Delete（削除）**をクリックしてください。 ![パッケージの削除ボタン](/assets/images/help/package-registry/delete-package-button.png) +6. 削除を確認するために、パッケージ名を入力して**I understand the consequences, delete this version（生じることを理解したので、このバージョンを削除してください）**をクリックしてください。 ![パッケージの削除の確認ボタン](/assets/images/help/package-registry/confirm-package-deletion.png) diff --git a/translations/ja-JP/content/packages/guides/enabling-improved-container-support.md b/translations/ja-JP/content/packages/guides/enabling-improved-container-support.md new file mode 100644 index 0000000000..352dbaea56 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/enabling-improved-container-support.md @@ -0,0 +1,39 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/enabling-improved-container-support +versions: + free-pro-team: '*' +--- + +{% note %} + +**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 During the beta, storage and bandwidth are free. 詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/getting-started-with-github-container-registry/about-github-container-registry)」を参照してください。 + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. 詳しい情報については、「[コンテナイメージにアクセス制御と可視性を設定する](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)」を参照してください。 + + ![パブリックまたはプライベートパッケージを有効にするオプション ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/ja-JP/content/packages/guides/index.md b/translations/ja-JP/content/packages/guides/index.md new file mode 100644 index 0000000000..19708fa218 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/index.md @@ -0,0 +1,33 @@ +--- +title: ガイド +shortTitle: ガイド +intro: 'These guides help you configure {% data variables.product.prodname_actions %} or your package client to work with {% data variables.product.prodname_registry %}.' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem + - /packages/using-github-packages-with-your-projects-ecosystem +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### 目次 + +{% topic_link_in_list /package-client-guides-for-github-packages %} + {% link_in_list /using-github-packages-with-github-actions %} + {% link_in_list /configuring-apache-maven-for-use-with-github-packages %} + {% link_in_list /configuring-gradle-for-use-with-github-packages %} + {% link_in_list /configuring-npm-for-use-with-github-packages %} + {% link_in_list /configuring-dotnet-cli-for-use-with-github-packages %} + {% link_in_list /configuring-rubygems-for-use-with-github-packages %} +{% topic_link_in_list /container-guides-for-github-packages %} + {% link_in_list /configuring-docker-for-use-with-github-packages %} + {% link_in_list /about-github-container-registry %} + {% link_in_list /migrating-to-github-container-registry-for-docker-images %} + {% link_in_list /enabling-improved-container-support %} + {% link_in_list /configuring-access-control-and-visibility-for-container-images %} + {% link_in_list /connecting-a-repository-to-a-container-image %} + {% link_in_list /pushing-and-pulling-docker-images %} + {% link_in_list /deleting-a-container-image %} + diff --git a/translations/ja-JP/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md b/translations/ja-JP/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md new file mode 100644 index 0000000000..12b5da8a26 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md @@ -0,0 +1,115 @@ +--- +title: Docker イメージを GitHub Container Registry に移行する +intro: 'Docker イメージを保存するため GitHub パッケージ Docker レジストリを使っている場合には、新しい {% data variables.product.prodname_container_registry %} に移行できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images +versions: + free-pro-team: '*' +--- + +### {% data variables.product.prodname_github_container_registry %} と Docker パッケージレジストリとの主な違い + +{% data reusables.package_registry.container-registry-beta %} + +{% data variables.product.prodname_github_container_registry %} は既存の Packages Docker レジストリに取って代わるもので、コンテナ固有のニーズのいくつかをサポートできるよう最適化されています。 + +{% data reusables.package_registry.container-registry-feature-highlights %} + +詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/getting-started-with-github-container-registry/about-github-container-registry)」を参照してください。 + +### 支払いの変更 + +{% data reusables.package_registry.billing-for-container-registry %} + +### ドメインの変更 + +{% data variables.product.prodname_container_registry %} のドメインは `ghcr.io` です。 + +| レジストリ | URLの例 | +| ----------------------------------------------------------------- | --------------------------------------------------- | +| {% data variables.product.prodname_registry %} Docker レジストリ | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` | +| {% data variables.product.prodname_github_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME` | + +### コンテナレジストリで認証する + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +{% data variables.product.prodname_container_registry %} は、 ベース URL `ghcr.io` で認証する必要があります。 {% data variables.product.prodname_container_registry %} を使用するために、新しいアクセストークンの作成をお勧めします。 + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Docker CLI を使用して Docker イメージを移行する + +{% data variables.product.prodname_registry %} Docker レジストリでホストしている Docker イメージを移動するには、イメージを {% data variables.product.prodname_container_registry %} に再公開する必要があります。 既存の Docker イメージを再公開するには、ローカルマシンでコマンドラインを使うことをお勧めします。 + +1. 少なくとも `read:packages` スコープのある一時的な PAT (個人アクセストークン) を使用して、Docker レジストリにサインインします。 この PAT は、Docker レジストリにサインインしてイメージをプルダウンするためにのみ使用され、その後は削除して構いません。 + {% raw %} + ```shell + $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin + ``` + {% endraw %} +2. 移行したいイメージをプルダウンします。OWNER はリポジトリを所有しているユーザまたは Organization アカウントの名前に、REPOSITORY はプロジェクトを含むリポジトリの名前に、IMAGE_NAME はパッケージまたはイメージの名前に、VERSION はインストールするイメージのタグにそれぞれ置き換えてください。 たとえば、`docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` は octo-org という Organization の `octoshift/octoshift` イメージの、最新のタグをプルします。 + ```shell + $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + +3. 新しいドメインと新しいイメージ名でイメージにタグ付けし直します。 詳しい情報については、Dockerのドキュメンテーションの「[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)」を参照してください。 先ほどのステップで用いた URL と同じものを SOURCE URL とします。 TARGET_OWNER はコンテナイメージをの移行先であるユーザまたは Organization に、TARGET_IMAGE_NAME は新しい {% data variables.product.prodname_container_registry %} イメージ名に置き換えます。 + ```shell + $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION + ``` + +4. 新しい + +{% data variables.product.prodname_container_registry %}. `read:packages` スコープと `write:packages` スコープに限定した新しい PAT の作成をお勧めします。`repo` スコープはもはや不要であり、以前の PAT は `write:packages` スコープを持っていない場合があるからです。 + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + ``` + {% endraw %} +5. タグ付けし直したイメージを {% data variables.product.prodname_container_registry %} にプッシュします。 + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION + ``` + +### {% data variables.product.prodname_actions %} ワークフローを更新する + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +{% data variables.product.prodname_registry %} Docker レジストリから Docker イメージを使用する {% data variables.product.prodname_actions %} ワークフローがある場合、ワークフローを {% data variables.product.prodname_container_registry %} に更新するといいでしょう。そうすればパブリックコンテナのイメージへの匿名アクセスが可能になり、きめ細かいアクセス権限を設定でき、コンテナに対するストレージと帯域幅が向上します。 + +1. `ghcr.io` にある新しい {% data variables.product.prodname_container_registry %} に Docker イメージを移行します。 例については、「[Docker CLI を使用して Docker イメージを移行する](#migrating-a-docker-image-using-the-docker-cli)」を参照してください。 + +2. {% data variables.product.prodname_actions %} ワークフローファイルで、パッケージ URL を `https://docker.pkg.github.com` から `ghcr.io` に更新します。 + +3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. {% data variables.product.prodname_github_container_registry %} は PAT において `GITHUB_TOKEN` の使用をサポートしていないので、`CR_PAT` などの別のカスタム変数を使用する必要があります。 詳しい情報については「[暗号化されたシークレットの作成と保存](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)」を参照してください。 + +4. {% data variables.product.prodname_actions %} ワークフローファイルにおいて、Docker レジストリ PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} をコンテナレジストリ {% data variables.product.prodname_container_registry %} PAT の新しい変数 (たとえば {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}) に置き換えて、認証 PAT を更新します。 + +#### 更新したワークフローの例 + +ワークフローの一部が Docker レジストリにホストされた Docker イメージにアクセスした場合は、次のようになります。 + +{% raw %} +```yaml +echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin +docker pull docker.pkg.github.com/github/octoshift/octoshift:latest +docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest +docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA +``` +{% endraw %} + +そして、ワークフローを新しい {% data variables.product.prodname_container_registry %} URL と PAT で次のように更新する必要があります。 + +{% raw %} +```yaml +# new login with new container registry url and PAT +echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin +# new container registry urls added +docker pull ghcr.io/github/octoshift:latest +docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest +docker push ghcr.io/github/octoshift:$GITHUB_SHA +``` +{% endraw %} diff --git a/translations/ja-JP/content/packages/guides/package-client-guides-for-github-packages.md b/translations/ja-JP/content/packages/guides/package-client-guides-for-github-packages.md new file mode 100644 index 0000000000..6f77e8b9bd --- /dev/null +++ b/translations/ja-JP/content/packages/guides/package-client-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Package client guides for GitHub Packages +shortTitle: Package client guides for GitHub Packages +intro: 'You can publish and retrieve package client images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/ja-JP/content/packages/guides/pushing-and-pulling-docker-images.md b/translations/ja-JP/content/packages/guides/pushing-and-pulling-docker-images.md new file mode 100644 index 0000000000..2a2c13b3e0 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/pushing-and-pulling-docker-images.md @@ -0,0 +1,106 @@ +--- +title: Docker イメージをプッシュ、プルする +intro: 'Docker イメージは {% data variables.product.prodname_github_container_registry %} で保存して管理できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +Organization が所有するコンテナイメージをプッシュまたはプルするには、{% data variables.product.prodname_github_container_registry %} を Organization に対して有効化する必要があります。 For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +### {% data variables.product.prodname_github_container_registry %} への認証を行う + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### コンテナイメージをプッシュする + +以下の例では、`IMAGE-NAME` の最新バージョンをプッシュします。 + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +以下の例では、イメージのバージョン `2.5` をプッシュします。 + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 + ``` + +パッケージを最初に公開する際のデフォルトの可視性はプライベートです。 可視性の変更やアクセス権限の設定については、「[コンテナイメージにアクセス制御と可視性を設定する](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)」を参照してください。 + +### コンテナイメージをプルする + +#### ダイジェストによるプル + +常に同一のイメージを使用するため、`digest` SHA 値でプルするコンテナイメージのバージョンを指定できます。 + +1. `docker inspect` または `docker pull` を使用してダイジェスト SHA 値を調べ、その SHA 値を `Digest:` の後にコピーします。 + ```shell + $ docker inspect ghcr.io/OWNER/IMAGE_NAME + ``` +2. 必要に応じてローカルでイメージを削除します。 + ```shell + $ docker rmi ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +3. イメージ名の後に `@YOUR_SHA_VALUE` を付けてコンテナイメージをプルします。 + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs + ``` + +#### 名前によるプル + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME + ``` + +#### 名前とバージョンによるプル + +名前と `1.14.1` バージョンタグにより Docker CLI でイメージをプルする例を以下に示します。 + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1 + > 5e35bd43cf78: Pull complete + > 0c48c2209aab: Pull complete + > fd45dd1aad5a: Pull complete + > db6eb50c2d36: Pull complete + > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e + > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 + > ghcr.io/orgname/image-name/release:1.14.1 + ``` + +#### 名前と最新バージョンによるプル + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest + > latest: Pulling from user/image-name + > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 + > Status: Downloaded newer image for ghcr.io/user/image-name:latest + > ghcr.io/user/image-name:latest + ``` + +### コンテナイメージを構築する + +以下の例では `hello_docker` イメージを構築します。 + ```shell + $ docker build -t hello_docker . + ``` + +### コンテナイメージにタグ付けする + +1. タグ付けする Docker イメージの ID を調べます。 + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +2. イメージ ID を使用して、Docker イメージを任意のイメージ名とホスティング先でタグ付けします。 + ```shell + $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest + ``` 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 new file mode 100644 index 0000000000..bb4ed48ec6 --- /dev/null +++ b/translations/ja-JP/content/packages/guides/using-github-packages-with-github-actions.md @@ -0,0 +1,54 @@ +--- +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 %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions + - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About {% data variables.product.prodname_registry %} with {% 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)." + +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 %} + +{% 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)." + +{% endif %} + +#### Authenticating to package registries on {% 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. + +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)." + +### Publishing a package using an action + +You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. + +{% data reusables.package_registry.actions-configuration %} + +### 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 %} + +{% 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 %} diff --git a/translations/ja-JP/content/packages/index.md b/translations/ja-JP/content/packages/index.md index 035960447b..e76d269f8d 100644 --- a/translations/ja-JP/content/packages/index.md +++ b/translations/ja-JP/content/packages/index.md @@ -2,31 +2,46 @@ title: GitHub Packagesのドキュメント shortTitle: GitHub Packages intro: '安全にパッケージを公開及び利用し、コードと共にパッケージを保存し、パッケージをTeamとプライベートに、あるいはオープンソースコミュニティとパブリックに共有してください。 また、{% data variables.product.prodname_actions %}とパッケージを自動化することもできます。' +introLinks: + quickstart: /packages/quickstart + reference: /packages/manage-packages featuredLinks: - gettingStarted: - - /packages/publishing-and-managing-packages/about-github-packages - - /packages/getting-started-with-github-container-registry/about-github-container-registry - - /packages/getting-started-with-github-container-registry - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/publishing-and-managing-packages/publishing-a-package - - /packages/publishing-and-managing-packages/installing-a-package + guides: + - /packages/learn-github-packages + - /packages/guides/using-github-packages-with-github-actions + - /packages/manage-packages/installing-a-package popular: - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-apache-maven-for-use-with-github-packages + guideCards: + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/guides/enabling-improved-container-support + - /packages/guides/configuring-rubygems-for-use-with-github-packages +changelog: + - + title: Packages container support is an opt-in beta + date: '2020-11-17' + href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support + - + title: Organization admins access to containers + date: '2020-11-16' + href: https://github.blog/changelog/2020-11-16-packages-organization-admins-access-to-containers/ + - + title: Packages now respects IP allow list settings + date: '2020-11-12' + href: https://github.blog/changelog/2020-11-12-packages-now-respects-ip-allow-list-settings/ redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry - /github/managing-packages-with-github-package-registry +layout: product-landing versions: free-pro-team: '*' enterprise-server: '>=2.22' --- -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% link_with_intro /getting-started-with-github-container-registry %} -{% link_with_intro /managing-container-images-with-github-container-registry %} -{% link_with_intro /publishing-and-managing-packages %} -{% link_with_intro /using-github-packages-with-your-projects-ecosystem %} + + + + 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 new file mode 100644 index 0000000000..94a4586b20 --- /dev/null +++ b/translations/ja-JP/content/packages/learn-github-packages/about-github-packages.md @@ -0,0 +1,166 @@ +--- +title: GitHub Packagesについて +intro: '{% data variables.product.prodname_registry %}はソフトウェアパッケージのホスティングサービスであり、ソフトウェアパッケージをプライベートもしくはパブリックでホストでき、パッケージをプロジェクト中で依存関係として使えるようになります。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/about-github-package-registry + - /github/managing-packages-with-github-package-registry/about-github-package-registry + - /github/managing-packages-with-github-packages/about-github-packages + - /packages/publishing-and-managing-packages/about-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### {% 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.product_name %} API、{% data variables.product.prodname_actions %}、webhookと統合して、コード、CI、デプロイメントのソリューションを含むエンドツーエンドのDevOpsワークフローを作成できます。 + +1つのリポジトリで複数のパッケージをホストし、各パッケージのREADMEを見たり、統計をダウンロードしたり、バージョン履歴を見たりすることで、各パッケージに関する詳しい情報を見ることができます。 + +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.prodname_actions %}ワークフローを作成する際には、`GITHUB_TOKEN`を使って{% data variables.product.prodname_registry %}にパッケージを公開してインストールでき、個人アクセストークンを保存して管理する必要はありません。 詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/guides/about-github-container-registry)」を参照してください。 + +{% data reusables.package_registry.container-registry-beta %} + +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + +{% endif %} + +#### パッケージの表示 + +パッケージの README や、ライセンス、ダウンロード統計、バージョン履歴などのメタデータを {% data variables.product.product_name %} 上で確認できます。 詳しい情報については「[パッケージの表示](/packages/manage-packages/viewing-packages)」を参照してください。 + +#### パッケージの権限と可視性について + +| | パッケージレジストリ | +| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| ホスト場所 | 1 つのリポジトリに複数のパッケージをホストできます。 | +| 権限 | {% data reusables.package_registry.public-or-private-packages %} パッケージはリポジトリの権限を継承するので、{% data variables.product.prodname_dotcom %}のロールとTeamを使い、各パッケージをインストールしたり公開したりできる人を制限できます。 リポジトリの読み取り権限を持っている人は、パッケージを依存関係としてプロジェクトにインストールでき、書き込み権限を持っている人は新しいパッケージのバージョンを公開できます。 | +| 可視性 | {% data reusables.package_registry.public-or-private-packages %} + +{% 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.container-registry-beta-billing-note %} +{% endif %} + +### サポートされているクライアントとフォーマット + +{% 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` | + +{% note %} + +**注釈:** Subdomain Isolation が無効化されている場合、Docker はサポートされません。 + +{% endnote %} + +Subdomain Isolation の詳しい情報については、「[Subdomain Isolation を有効化する](/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)." + +{% 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)." +{% endif %} +### {% data variables.product.prodname_registry %} への認証を行う + +{% data reusables.package_registry.authenticate-packages %} + +### パッケージの管理 + +パッケージをインストールあるいは公開するには、適切なスコープを持つトークンを使い、ユーザアカウントがそのリポジトリに対する適切な権限を持っていなければなりません。 + +例: +- リポジトリからパッケージをダウンロードしてインストールするには、トークンは`read:packages`スコープを持っていなければならず、ユーザアカウントはそのリポジトリの読み取り権限を持っていなければなりません。 +- {% data variables.product.product_name %}上の特定バージョンのプライベートパッケージを削除するには、トークンは`delete:packages`及び`repo`スコープを持っていなければなりません。 パブリックなパッケージは削除できません。 詳しい情報については「[パッケージの削除](/packages/manage-packages/deleting-a-package)」を参照してください。 + +| スコープ | 説明 | リポジトリの権限 | +| ----------------- | ------------------------------------------------------------------------------ | --------------- | +| `read:packages` | {% data variables.product.prodname_registry %}からのパッケージのダウンロードとインストール | 読み取り | +| `write:packages` | {% data variables.product.prodname_registry %}へのパッケージのアップロードと公開 | 書き込み | +| `delete:packages` | {% data variables.product.prodname_registry %}からの特定バージョンのプライベートパッケージの削除 | 管理 | +| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write, or admin | + +{% data variables.product.prodname_actions %}ワークフローを作成する際には、`GITHUB_TOKEN`を使って{% data variables.product.prodname_registry %}にパッケージを公開してインストールでき、個人アクセストークンを保存して管理する必要はありません。 + +詳しい情報については、以下を参照してください。 +- ドキュメンテーションに反する何らかの体験をした時 +- [個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token/) +- GDPR違反、APIキー、個人を識別する情報といったセンシティブなデータを含むパッケージを公開した時 + +### パッケージの管理 + +You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. GraphQL APIを使ってプライベートパッケージに対するクエリや削除を行う場合、{% data variables.product.prodname_registry %}の認証に使うのと同じトークンを使わなければなりません。 詳しい情報については、「[パッケージの削除](/packages/manage-packages/deleting-a-package)」と「[GraphQLでの呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」を参照してください。 + +webhookを設定して、パッケージの公開や更新といったパッケージ関連のイベントにサブスクライブできます。 詳しい情報については、「[`package` webhookイベント](/webhooks/event-payloads/#package)」を参照してください。 + +### サポートへの連絡 + +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.prodname_registry %} についてのフィードバックあるいは機能リクエストがある場合は、 +[{% data variables.product.prodname_registry %} のフィードバックフォーム](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages)を利用してください。 + +[連絡フォーム](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages)を使い、{% data variables.product.prodname_registry %}について{% data variables.contact.github_support %}に連絡してください。 + +* ドキュメンテーションに反する何らかの体験をした時 +* 漠然とした、あるいは不明確なエラーを体験した時 +* GDPR違反、APIキー、個人を識別する情報といったセンシティブなデータを含むパッケージを公開した時 + +{% else %} +{% data variables.product.prodname_registry %} についてサポートが必要な場合は、 +サイト管理者に連絡してください。 + +{% endif %} diff --git a/translations/ja-JP/content/packages/learn-github-packages/core-concepts-for-github-packages.md b/translations/ja-JP/content/packages/learn-github-packages/core-concepts-for-github-packages.md new file mode 100644 index 0000000000..e70161cf99 --- /dev/null +++ b/translations/ja-JP/content/packages/learn-github-packages/core-concepts-for-github-packages.md @@ -0,0 +1,28 @@ +--- +title: Core concepts for GitHub Packages +intro: '弊社のサイトおよびドキュメンテーションで使用する、一般的な {% data variables.product.prodname_registry %} 用語を以下に挙げます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Package + +パッケージは自己完結している再利用可能なソフトウェアで、開発者がコードやメタデータといったものを共通の場所にまとめて、他の人が利用できるようにしたものです。 パッケージのメタデータには、バージョン番号、名前、コードの依存関係を含めることができます。 パッケージは、プロジェクトの開発やテストに必要なフレームワーク、コードの品質を高めるための文法チェッカー、アプリケーションを強化するための業界標準の機械学習ツールといった、一般的な問題に対するソリューションの利用および配布を容易にします。 パッケージは多くのエコシステムで存在します。 たとえば、Node.js と Java のコードやコンテナイメージをパッケージ化できます。 + +### コンテナ + +コンテナとは、あらゆるプラットフォームに標準化された方法でソフトウェアを確実にデプロイするために設計されたソフトウェアのユニットです。 コンテナは、お使いのオペレーティングシステムで、同じホストカーネル上のさまざまなソフトウェアパッケージとコンポーネントを実行できる独立した仮想環境またはインスタンスとして動作します。 コンテナは、実行するために独自の仮想ハードウェアを含める必要がないため、仮想マシンよりも使用するリソースか少なくなります。 コンテナは、Dockerfile などのコンテナイメージと、コンテナクライアントまたはランタイムプログラムを使用して作成されます。 + +### コンテナイメージ + +コンテナイメージとは、コンテナからアプリケーションを実行するためのソフトウェア要件を指定するパッケージアーカイブの一種です。 コンテナイメージには通常、アプリケーションのコード、ライブラリ、およびランタイム命令が含まれます。 どこでイメージがデプロイ、実行されても詳細にわたるまで確実に同じイメージが使用されるようにするため、コンテナイメージは自動的にバージョン管理され、コンテナ内にいったんコンテナイメージが構築されると変更できません。 + +### Dockerコンテナ + +Docker コンテナは、Docker プラットフォーム上に構築されたオープンソースコンテナの一種です。 Docker のオリジナルイメージフォーマットは OCI (Open Container Initiative) イメージ仕様となっています。 詳しい情報については、「[Docker のドキュメンテーション](https://docs.docker.com/get-started/overview/)」を参照してください。 diff --git a/translations/ja-JP/content/packages/learn-github-packages/index.md b/translations/ja-JP/content/packages/learn-github-packages/index.md new file mode 100644 index 0000000000..a21e10fe4c --- /dev/null +++ b/translations/ja-JP/content/packages/learn-github-packages/index.md @@ -0,0 +1,16 @@ +--- +title: Learn GitHub Packages +shortTitle: Learn GitHub Packages +intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.' +redirect_from: + - /packages/getting-started-with-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /about-github-packages %} +{% link_in_list /core-concepts-for-github-packages %} +{% link_in_list /publishing-a-package %} diff --git a/translations/ja-JP/content/packages/learn-github-packages/publishing-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/publishing-a-package.md new file mode 100644 index 0000000000..e63ea80a30 --- /dev/null +++ b/translations/ja-JP/content/packages/learn-github-packages/publishing-a-package.md @@ -0,0 +1,37 @@ +--- +title: パッケージを公開する +intro: '{% data variables.product.prodname_registry %}にパッケージを公開し、そのパッケージを他者がダウンロードして再利用できるようにすることができます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-a-package + - /packages/publishing-and-managing-packages/publishing-a-package +permissions: リポジトリの書き込み権限を持つ人は、そのリポジトリにパッケージを公開できます。 +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### 公開されたパッケージについて + +パッケージページ上のインストール及び利用方法の説明といった、説明やその他の詳細を提供することによって、パッケージを理解して利用しやすくできます。 {% data variables.product.product_name %} は各バージョンについて、公開日、ダウンロードのアクティビティ、最近のバージョンなどのメタデータを提供します。 パッケージページの例としては、[@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1)を参照してください。 + +{% data reusables.package_registry.public-or-private-packages %} リポジトリには複数のパッケージを含めることができます。 混乱を避けるため、READMEと説明で各パッケージに関する情報を明確に提供してください。 + +{% if currentVersion == "free-pro-team@latest" %} +新しいバージョンのパッケージでセキュリティの脆弱性が解決される場合は、リポジトリでセキュリティアドバイザリを公開する必要があります。 +{% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. 詳しい情報については、「[GitHub セキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」 を参照してください。 +{% endif %} + +### パッケージを公開する + +以下の同じ一般的なガイドラインに従って、{% if currentVersion == "free-pro-team@latest" %}サポートされているいずれかのパッケージのクライアント{% else %}インスタンスで有効化しているパッケージのタイプ{% endif %}を使い、{% data variables.product.prodname_registry %} にパッケージを公開できます。 + +1. 実行したいタスクに対して適切なスコープを持つ既存のアクセストークンを作成もしくは利用してください。 詳しい情報については「[{% data variables.product.prodname_registry %}について](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)」を参照してください。 +2. 使用するパッケージクライアントについての指示に従って、アクセストークンを使って{% data variables.product.prodname_registry %}の認証をしてください。 +3. 使用するパッケージクライアントに関する指示に従って、パッケージを公開してください。 + +使用するパッケージクライアントに特有の指示については、「[プロジェクトのエコシステムでの{% data variables.product.prodname_registry %}の利用](/packages/using-github-packages-with-your-projects-ecosystem)」を参照してください。 + +パッケージを公開した後は、{% data variables.product.prodname_dotcom %}上でそのパッケージを見ることができます。 詳しい情報については「[パッケージの表示](/packages/publishing-and-managing-packages/viewing-packages)」を参照してください。 diff --git a/translations/ja-JP/content/packages/manage-packages/deleting-a-package.md b/translations/ja-JP/content/packages/manage-packages/deleting-a-package.md new file mode 100644 index 0000000000..fea973038b --- /dev/null +++ b/translations/ja-JP/content/packages/manage-packages/deleting-a-package.md @@ -0,0 +1,81 @@ +--- +title: パッケージを削除する +intro: 'GraphQLを使って、あるいは{% data variables.product.product_name %}上でプライベートパッケージのバージョンを削除できます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/deleting-a-package + - /packages/publishing-and-managing-packages/deleting-a-package +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% if currentVersion == "free-pro-team@latest" %} +### プライベートパッケージの削除について + +To delete a container image package on {% data variables.product.product_name %}, see "[Deleting a container image](/packages/guides/deleting-a-container-image)." + +{% endif %} + +### プライベートパッケージの削除について + +{% data variables.product.product_name %}上で、あるいはGraphQL APIで、プライベートパッケージの指定したバージョンだけが削除できます。 {% data variables.product.product_name %}上でプラベートパッケージが完全に表示されないよう削除するには、まずそのパッケージのすべてのバージョンを削除しなければなりません。 + +{% if currentVersion == "free-pro-team@latest" %} +### パブリックパッケージの削除について + +パッケージに依存しているかもしれないプロジェクトが壊れることを避けるために、パブリックなパッケージ全体、あるいはパブリックなパッケージの特定バージョンを削除する事はできません。 + +法的な理由、あるいはGDPR標準への準拠のような特別な状況下では、{% data variables.contact.github_support %}に対してパブリックパッケージを削除してもらうよう、[連絡フォーム](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry)を使って頼むことができます。 + +{% else %} + +At this time, {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} does not support deleting public packages. + +{% endif %} + +### {% data variables.product.product_name %}上でのプライベートパッケージのバージョンの削除 + +プライベートパッケージのバージョンを削除するには、そのリポジトリの管理権限が必要です。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +3. 削除したいパッケージの名前をクリックしてください。 ![パッケージ名](/assets/images/help/package-registry/select-pkg-cloud.png) +4. 右側で**Edit package（パッケージの編集）**ドロップダウンを使い、"Manage versions（バージョンの管理）"を選択してください。 ![パッケージ名](/assets/images/help/package-registry/manage-versions.png) +5. 削除したいバージョンの右で**Delete（削除）**をクリックしてください。 ![パッケージの削除ボタン](/assets/images/help/package-registry/delete-package-button.png) +6. 削除を確認するために、パッケージ名を入力して**I understand the consequences, delete this version（生じることを理解したので、このバージョンを削除してください）**をクリックしてください。 ![パッケージの削除の確認ボタン](/assets/images/help/package-registry/confirm-package-deletion.png) + +### GraphQLでのプライベートパッケージのバージョンの削除 + +GraphQL APIの`deletePackageVersion`ミューテーションを使ってください。 `read:packages`、`delete:packages`、`repo`スコープを持つトークンを使わなければなりません。 トークンに関する詳しい情報については「[{% data variables.product.prodname_registry %}について](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)」を参照してください。 + +以下は、個人アクセストークンを使って`MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`というパッケージバージョンIDを持つパッケージのバージョンを削除するcURLコマンドの例です。 + +{% if currentVersion == "free-pro-team@latest" %} +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +https://api.github.com/graphql +``` + +{% else %} + +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +HOSTNAME/graphql +``` + +{% endif %} + +パッケージのバージョンIDと併せて{% data variables.product.prodname_registry %}に公開したすべてプライベートパッケージを見つけるには、`registryPackagesForQuery`コネクションが利用できます。 `read:packages`及び`repo`のスコープを持つトークンが必要です。 For more information, see "[`registryPackagesForQuery`](/v4/object/registrypackageconnection/)." + +`deletePackageVersion`ミューテーションの詳しい情報については、「[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)」を参照してください。 + +削除したいパッケージの名前をクリックしてください。 diff --git a/translations/ja-JP/content/packages/manage-packages/index.md b/translations/ja-JP/content/packages/manage-packages/index.md new file mode 100644 index 0000000000..c4f3e73ee1 --- /dev/null +++ b/translations/ja-JP/content/packages/manage-packages/index.md @@ -0,0 +1,18 @@ +--- +title: Managing GitHub packages +shortTitle: Managing GitHub packages +intro: '新しいパッケージを{% data variables.product.prodname_registry %}に公開し、既存のパッケージを見てインストールし、特殊な環境では既存のパッケージを削除できます。' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-and-managing-packages + - /github/packages/publishing-and-managing-packages + - /packages/publishing-and-managing-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /viewing-packages %} +{% link_in_list /installing-a-package %} +{% link_in_list /deleting-a-package %} diff --git a/translations/ja-JP/content/packages/manage-packages/installing-a-package.md b/translations/ja-JP/content/packages/manage-packages/installing-a-package.md new file mode 100644 index 0000000000..9956482d23 --- /dev/null +++ b/translations/ja-JP/content/packages/manage-packages/installing-a-package.md @@ -0,0 +1,29 @@ +--- +title: パッケージをインストールする +intro: '{% data variables.product.prodname_registry %}からパッケージをインストールし、そのパッケージを自分のプロジェクトの依存関係として使うことができます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/installing-a-package + - /packages/publishing-and-managing-packages/installing-a-package +permissions: リポジトリの読み取り権限を持っている人は、そのリポジトリからパッケージをインストールできます。 +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### パッケージのインストールについて + +{% data variables.product.product_name %}を検索して、自分のプロジェクトにインストールできるパッケージを{% data variables.product.prodname_registry %}で見つけることができます。 詳しい情報については「[パッケージを{% data variables.product.prodname_registry %}で検索する](/github/searching-for-information-on-github/searching-for-packages)」を参照してください。 + +パッケージを見つけたなら、そのパッケージの説明と、パッケージのページにあるインストールと利用方法の指示を読むことができます。 + +### パッケージをインストールする + +以下の同じ一般的なガイドラインに従って、{% if currentVersion == "free-pro-team@latest" %}サポートされているいずれかのパッケージのクライアント{% else %}インスタンスで有効化しているパッケージのタイプ{% endif %}を使い、{% data variables.product.prodname_registry %} からパッケージをインストールできます。 + +1. 使用するパッケージクライアントについての指示に従って、{% data variables.product.prodname_registry %}の認証をしてください。 詳しい情報については「[トークンについて](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)」を参照してください。 +2. 使用するパッケージクライアントに関する指示に従って、パッケージをインストールしてください。 + +使用するパッケージクライアントに特有の指示については、「[プロジェクトのエコシステムでの{% data variables.product.prodname_registry %}の利用](/packages/using-github-packages-with-your-projects-ecosystem)」を参照してください。 diff --git a/translations/ja-JP/content/packages/manage-packages/viewing-packages.md b/translations/ja-JP/content/packages/manage-packages/viewing-packages.md new file mode 100644 index 0000000000..61f74be2d3 --- /dev/null +++ b/translations/ja-JP/content/packages/manage-packages/viewing-packages.md @@ -0,0 +1,50 @@ +--- +title: パッケージの表示 +intro: 'リポジトリに公開されたパッケージの詳細を表示し、Organization またはユーザごとに結果を絞り込むことができます。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/viewing-packages + - /packages/publishing-and-managing-packages/viewing-packages +permissions: リポジトリへの読み取り権限を持つユーザは、リポジトリのパッケージを表示できます。 +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### リポジトリのパッケージを表示する + +パッケージはリポジトリレベルでインストールする必要がありますが、Organization 内のすべてのパッケージと公開したすべてのパッケージを表示できます。 {% data reusables.package_registry.package-page-info %} + +### リポジトリのパッケージを表示する + +リポジトリ内のすべてのパッケージを表示し、リポジトリ内の特定のパッケージを検索できます。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + +### Organization のパッケージを表示する + +Organization にインストールされているすべてのパッケージを表示し、Organization のリポジトリにインストールされている特定のパッケージを検索できます。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Organization 名の下で、クリックします +Organization 名の下で、{% octicon "package" aria-label="The package icon" %} [**Packages**] をクリックします。 +{% data reusables.package_registry.navigate-to-packages %} + +### パッケージを表示する + +インストールしたすべてのパッケージを表示し、インストールした特定のパッケージをすべての Organization とリポジトリに渡って検索できます。 + +{% data reusables.profile.access_profile %} +2. プロフィールページの一番上のメインナビゲーションにある [**Packages（パッケージ）**] をクリックします。 ![プロジェクトタブ](/assets/images/help/package-registry/user-packages-tab.png) +{% data reusables.package_registry.navigate-to-packages %} + +### 参考リンク + +- [パッケージの検索](/github/searching-for-information-on-github/searching-for-packages) diff --git a/translations/ja-JP/content/packages/quickstart.md b/translations/ja-JP/content/packages/quickstart.md new file mode 100644 index 0000000000..15ccc422e6 --- /dev/null +++ b/translations/ja-JP/content/packages/quickstart.md @@ -0,0 +1,110 @@ +--- +title: Quickstart for GitHub Packages +intro: 'Publish to {% data variables.product.prodname_registry %} in 5 minutes or less with {% data variables.product.prodname_actions %}.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### はじめに + +You only need an existing {% data variables.product.prodname_dotcom %} repository to publish a package to {% data variables.product.prodname_registry %}. In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}. Feel free to create a new repository for this Quickstart. You can use it to test this and future {% data variables.product.prodname_actions %} workflows. + +### Publishing your package + +1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. Create a private repository if you’d like to delete this package later, public packages cannot be deleted. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clone the repository to your local machine. + {% raw %} + ```shell + $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git + $ cd YOUR-REPOSITORY + ``` + {% endraw %} +3. Create an `index.js` file and add a basic alert to say "Hello world!" + {% raw %} + ```javascript{:copy} + alert("Hello, World!"); + ``` + {% endraw %} +4. Initialize an npm package. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0` if you do not have any tests. Commit your changes and push them to +{% data variables.product.prodname_dotcom %}. + {% raw %} + ```shell + $ npm init + ... + package name: @YOUR-USERNAME/YOUR-REPOSITORY + ... + test command: exit 0 + ... + + $ npm install + $ git add index.js package.json package-lock.json + $ git commit -m "initialize npm package" + $ git push + ``` + {% endraw %} +5. {% data variables.product.prodname_dotcom %} のリポジトリから、`release-package.yml` という名前の新しいファイルを `.github/workflows` ディレクトリに作成します。 詳細は「[新しいファイルを作成する](/github/managing-files-in-a-repository/creating-new-files)」を参照してください。 +6. Copy the following YAML content into the `release-package.yml` file. + {% raw %} + ```yaml{:copy} + name: Node.js Package + + on: + release: + types: [created] + + jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm ci + - run: npm test + + publish-gpr: + needs: build + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + registry-url: https://npm.pkg.github.com/ + - run: npm ci + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + ``` + {% endraw %} +7. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. 次に、[**Propose new file**] をクリックしてプルリクエストを作成します。 +8. **Merge** the pull request. +9. Navigate to the **Code** tab and create a new release to test the workflow. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." + +Creating a new release in your repository triggers the workflow to build and test your code. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. + +### Viewing your published package + +Packages are published at the repository level. You can see all the packages in a repository and search for a specific package. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + + +### Installing a published package + +Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)." + +### 次のステップ + +The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more. + +Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. 開始する場合、 Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}: + +- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions +- "[Guides](/packages/guides)" for specific uses cases and examples diff --git a/translations/ja-JP/content/rest/README.md b/translations/ja-JP/content/rest/README.md new file mode 100644 index 0000000000..55aaa5edda --- /dev/null +++ b/translations/ja-JP/content/rest/README.md @@ -0,0 +1,10 @@ +# REST + +The `/content/rest` directory is where the GitHub REST API docs live! + +* The `/content/rest/guides` and `/content/rest/overview` directories contain regular articles. These are human-editable. +* The `/content/rest/reference` directory contains an article for each group of endpoints in the GitHub REST API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/rest/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/rest/README.md`](/lib/rest/README.md). + + **As a result, we cannot accept contributions to REST API reference content in this repository.** 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 d58d660cae..725f4a7ee7 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 @@ -373,7 +373,7 @@ $ {% data variables.product.api_url_pre %}/users/defunkt [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore [issues-api]: /rest/reference/issues -[link-header]: http://www.w3.org/wiki/LinkHeader/ +[link-header]: https://www.w3.org/wiki/LinkHeader [conditional-requests]: /rest#conditional-requests [rate-limiting]: /rest#rate-limiting [rate-limiting]: /rest#rate-limiting diff --git a/translations/ja-JP/content/rest/overview/api-previews.md b/translations/ja-JP/content/rest/overview/api-previews.md index 3b221ce743..e97891ce2e 100644 --- a/translations/ja-JP/content/rest/overview/api-previews.md +++ b/translations/ja-JP/content/rest/overview/api-previews.md @@ -53,7 +53,7 @@ pre-receive フックの環境を作成、一覧表示、更新、削除しま {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### インテグレーション -API を介して[インテグレーション](/early-access/integrations/)を管理します。 +API を介して[インテグレーション](/v3/integrations)を管理します。 **カスタムメディアタイプ:** `machine-man-preview` **発表日:** [2016-09-14](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/) {% endif %} diff --git a/translations/ja-JP/content/rest/overview/libraries.md b/translations/ja-JP/content/rest/overview/libraries.md index fbdaca7569..7e9c454fcc 100644 --- a/translations/ja-JP/content/rest/overview/libraries.md +++ b/translations/ja-JP/content/rest/overview/libraries.md @@ -72,7 +72,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md index 7081b7c8c1..5c6a55d84a 100644 --- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md @@ -261,13 +261,15 @@ API v3 は、可能な限り各アクションに適切な HTTPメソッドを ### ページネーション -複数のアイテムを返すリクエストは、デフォルトで 30 件ごとにページ分けされます。 `?page` パラメータを使用すると、さらにページを指定できます。 一部のリソースでは、`?per_page` パラメータを使用してカスタムページサイズを最大 100 に設定することもできます。 技術的な理由により、すべてのエンドポイントが `?per_page` パラメータを尊重するわけではないことに注意してください。例については、[イベント](/rest/reference/activity#events)を参照してください。 +複数のアイテムを返すリクエストは、デフォルトで 30 件ごとにページ分けされます。 You can specify further pages with the `page` parameter. For some resources, you can also set a custom page size up to 100 with the `per_page` parameter. Note that for technical reasons not all endpoints respect the `per_page` parameter, see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -ページ番号は 1 から始まり、`?page` パラメータを省略すると最初のページが返されることに注意してください。 +Note that page numbering is 1-based and that omitting the `page` parameter will return the first page. + +Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set. With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page. Instead, you can traverse the results by using the `before` or `after` parameters. ページネーションの詳細については、[ページネーションでトラバースする][pagination-guide]のガイドをご覧ください。 @@ -279,14 +281,18 @@ $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' {% endnote %} -[Link ヘッダ](http://tools.ietf.org/html/rfc5988)には、ページネーション情報が含まれています。 +The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information. 例: Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" _この例は、読みやすいように改行されています。_ -この `Link` レスポンスヘッダには、1 つ以上の[ハイパーメディア](/rest#hypermedia)リンク関係が含まれています。その一部には、[URI テンプレート](http://tools.ietf.org/html/rfc6570)としての拡張が必要な場合があります。 +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). 使用可能な `rel` の値は以下のとおりです。 @@ -311,7 +317,7 @@ Basic 認証または OAuth を使用する API リクエストの場合、1 時 {% data reusables.enterprise.rate_limit %} -[Search API にはカスタムのレート制限ルール](/rest/reference/search#rate-limit)があることに注意してください。 +Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). API リクエストの返された HTTP ヘッダは、現在のレート制限ステータスを示しています。 @@ -354,7 +360,7 @@ new Date(1372700873 * 1000) > } ``` -API ヒットを発生させることなく、[レート制限ステータスを確認](/rest/reference/rate-limit)できます。 +You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. #### OAuth アプリケーションの認証されていないレート制限を増やす @@ -585,9 +591,9 @@ JavaScript ハンドラを記述して、コールバックを処理できます #### ISO 8601 タイムスタンプにタイムゾーン情報を明示的に提供する -タイムスタンプを指定できる API 呼び出しの場合、その正確なタイムスタンプを使用します。 これは[コミット API](/rest/reference/git#commits) の例です。 +タイムスタンプを指定できる API 呼び出しの場合、その正確なタイムスタンプを使用します。 An example of this is the [Commits API](/rest/reference/git#commits). -これらのタイムスタンプは、`2014-02-27T15:05:06+01:00` のようになります。 これらのタイムスタンプを指定する方法については、[こちらの例](/rest/reference/git#example-input)も参照してください。 +これらのタイムスタンプは、`2014-02-27T15:05:06+01:00` のようになります。 Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified. #### `Time-Zone` ヘッダを使用する @@ -597,7 +603,7 @@ JavaScript ハンドラを記述して、コールバックを処理できます $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -つまり、このヘッダが定義するタイムゾーンで API 呼び出しが行われた時のタイムスタンプが生成されます。 たとえば、[コンテンツ API](/rest/reference/repos#contents) は追加または変更ごとに git コミットを生成し、タイムスタンプとして現在の時刻を使用します。 このヘッダは、現在のタイムスタンプの生成に使用されたタイムゾーンを決定します。 +つまり、このヘッダが定義するタイムゾーンで API 呼び出しが行われた時のタイムスタンプが生成されます。 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. このヘッダは、現在のタイムスタンプの生成に使用されたタイムゾーンを決定します。 #### ユーザが最後に認識されたタイムゾーンを使用する diff --git a/translations/ja-JP/content/rest/overview/troubleshooting.md b/translations/ja-JP/content/rest/overview/troubleshooting.md index 63a188ab00..9db07dcdd9 100644 --- a/translations/ja-JP/content/rest/overview/troubleshooting.md +++ b/translations/ja-JP/content/rest/overview/troubleshooting.md @@ -52,7 +52,7 @@ curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos #### Calls to OAuth Authorizations API -If you're making [OAuth Authorization API](/enterprise-server@2.22/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: +If you're making [OAuth Authorization API](/enterprise-server/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: ```bash curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}' diff --git a/translations/ja-JP/content/rest/reference/enterprise-admin.md b/translations/ja-JP/content/rest/reference/enterprise-admin.md index a448ae41b2..8667f6ea31 100644 --- a/translations/ja-JP/content/rest/reference/enterprise-admin.md +++ b/translations/ja-JP/content/rest/reference/enterprise-admin.md @@ -57,6 +57,16 @@ The current version of your enterprise is returned in the response header of eve {% endif %} +{% if currentVersion == "free-pro-team@latest" %} + +## Audit log + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ## 支払い diff --git a/translations/ja-JP/content/rest/reference/index.md b/translations/ja-JP/content/rest/reference/index.md index 91a394406b..ba931ec352 100644 --- a/translations/ja-JP/content/rest/reference/index.md +++ b/translations/ja-JP/content/rest/reference/index.md @@ -15,8 +15,6 @@ versions: {% link_in_list /apps %} {% link_in_list /billing %} {% link_in_list /checks %} - - {% link_in_list /codes-of-conduct %} {% link_in_list /code-scanning %} {% link_in_list /emojis %} @@ -39,6 +37,7 @@ versions: {% link_in_list /repos %} {% link_in_list /scim %} {% link_in_list /search %} +{% link_in_list /secret-scanning %} {% link_in_list /teams %} {% link_in_list /users %} {% link_in_list /permissions-required-for-github-apps %} diff --git a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md index 1e6eecdbe9..e181fd677f 100644 --- a/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ja-JP/content/rest/reference/permissions-required-for-github-apps.md @@ -819,10 +819,19 @@ _Team_ * [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) - {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Permission on "secret scanning alerts" + +- [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) + +- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read) + +- [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### "security events"に対する権限 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) diff --git a/translations/ja-JP/content/rest/reference/secret-scanning.md b/translations/ja-JP/content/rest/reference/secret-scanning.md new file mode 100644 index 0000000000..6c266b8488 --- /dev/null +++ b/translations/ja-JP/content/rest/reference/secret-scanning.md @@ -0,0 +1,12 @@ +--- +title: Secret scanning +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.secret-scanning.api-beta %} + +The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a private repository. For more information on secret scanning for private repositories, see "[Securing your repository](/github/administering-a-repository/securing-your-repository)." + +{% include rest_operations_at_current_path %} diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml index f7d2d1791e..d17ae73ea1 100644 --- a/translations/ja-JP/data/glossaries/external.yml +++ b/translations/ja-JP/data/glossaries/external.yml @@ -390,7 +390,7 @@ - term: main description: >- - The default development branch. Whenever you create a Git repository, a branch named "main" is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. + The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. - term: master description: >- @@ -449,7 +449,7 @@ description: >- Organization の 1 つ以上のリポジトリに対するアクセス権が付与されているが、その Organization に対する他のアクセス権がなく、その Organization のメンバーでもないユーザ。 - - term: Открытое программное обеспечение, sometimes used untranslated + term: オープンソース description: >- オープンソースソフトウェアとは、誰でも自由に使用、修正、および（修正済みと未修正のいずれの形式でも）共有できるソフトウェアです。今日では、「オープンソース」の概念はソフトウェアの枠を超えてコラボレーションの哲学をいうことが多く、そのコラボレーションの素材について誰でもオンラインでフォーク、修正、ディスカッション、コントリビューションができます。 - diff --git a/translations/ja-JP/data/products.yml b/translations/ja-JP/data/products.yml index 9068fbfa82..8d13a67096 100644 --- a/translations/ja-JP/data/products.yml +++ b/translations/ja-JP/data/products.yml @@ -5,10 +5,12 @@ productsInOrder: - github - 管理 + - ディスカッション - actions - パッケージ - developers - rest - graphql - insights - - desktop、 + - education + - desktop diff --git a/translations/ja-JP/data/release-notes/2-20/0.yml b/translations/ja-JP/data/release-notes/2-20/0.yml new file mode 100644 index 0000000000..5623123354 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/0.yml @@ -0,0 +1,44 @@ +--- +date: '2020-02-11' +sections: + features: + - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" + - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" + - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + changes: + - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/1.yml b/translations/ja-JP/data/release-notes/2-20/1.yml new file mode 100644 index 0000000000..e303f5525e --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/1.yml @@ -0,0 +1,21 @@ +--- +date: '2020-02-27' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + bugs: + - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/10.yml b/translations/ja-JP/data/release-notes/2-20/10.yml new file mode 100644 index 0000000000..58a38245c0 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/10.yml @@ -0,0 +1,21 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" + - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/11.yml b/translations/ja-JP/data/release-notes/2-20/11.yml new file mode 100644 index 0000000000..0bdd30cf96 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/11.yml @@ -0,0 +1,19 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/12.yml b/translations/ja-JP/data/release-notes/2-20/12.yml new file mode 100644 index 0000000000..5b286392f5 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/12.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + bugs: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + changes: + - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/13.yml b/translations/ja-JP/data/release-notes/2-20/13.yml new file mode 100644 index 0000000000..7388ff5103 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/13.yml @@ -0,0 +1,22 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/14.yml b/translations/ja-JP/data/release-notes/2-20/14.yml new file mode 100644 index 0000000000..d33fe2b58d --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/14.yml @@ -0,0 +1,13 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/15.yml b/translations/ja-JP/data/release-notes/2-20/15.yml new file mode 100644 index 0000000000..aa3c664487 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/15.yml @@ -0,0 +1,24 @@ +date: '2020-08-26' +sections: + security_fixes: + - >- + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, + https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} + - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + bugs: + - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' + changes: + - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/16.yml b/translations/ja-JP/data/release-notes/2-20/16.yml new file mode 100644 index 0000000000..4ca63bc213 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/16.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/17.yml b/translations/ja-JP/data/release-notes/2-20/17.yml new file mode 100644 index 0000000000..5f3bf87a25 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/17.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/18.yml b/translations/ja-JP/data/release-notes/2-20/18.yml new file mode 100644 index 0000000000..3aab7ba337 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/18.yml @@ -0,0 +1,26 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/19.yml b/translations/ja-JP/data/release-notes/2-20/19.yml new file mode 100644 index 0000000000..b686131852 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/19.yml @@ -0,0 +1,14 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/2.yml b/translations/ja-JP/data/release-notes/2-20/2.yml new file mode 100644 index 0000000000..78e2faa7e1 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/2.yml @@ -0,0 +1,28 @@ +--- +date: '2020-03-10' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + bugs: + - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + changes: + - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/20.yml b/translations/ja-JP/data/release-notes/2-20/20.yml new file mode 100644 index 0000000000..0cf4def9e0 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/20.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/21.yml b/translations/ja-JP/data/release-notes/2-20/21.yml new file mode 100644 index 0000000000..4b970a92ee --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/21.yml @@ -0,0 +1,15 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/22.yml b/translations/ja-JP/data/release-notes/2-20/22.yml new file mode 100644 index 0000000000..099ce93b0d --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/22.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/3.yml b/translations/ja-JP/data/release-notes/2-20/3.yml new file mode 100644 index 0000000000..23c25312e5 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/3.yml @@ -0,0 +1,15 @@ +--- +date: '2020-03-12' +sections: + bugs: + - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/4.yml b/translations/ja-JP/data/release-notes/2-20/4.yml new file mode 100644 index 0000000000..0f06a203cd --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/4.yml @@ -0,0 +1,18 @@ +--- +date: '2020-03-25' +sections: + bugs: + - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/5.yml b/translations/ja-JP/data/release-notes/2-20/5.yml new file mode 100644 index 0000000000..44115fdc71 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/5.yml @@ -0,0 +1,20 @@ +--- +date: '2020-04-07' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + bugs: + - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/6.yml b/translations/ja-JP/data/release-notes/2-20/6.yml new file mode 100644 index 0000000000..568f19954f --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/6.yml @@ -0,0 +1,27 @@ +--- +date: '2020-04-23' +sections: + security_fixes: + - '**HIGH**: OpenSSL has been updated to address [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 %}' + - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + bugs: + - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" + - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + changes: + - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% 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: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/7.yml b/translations/ja-JP/data/release-notes/2-20/7.yml new file mode 100644 index 0000000000..b377d90b66 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/7.yml @@ -0,0 +1,21 @@ +--- +date: '2020-05-05' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + bugs: + - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' + - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/8.yml b/translations/ja-JP/data/release-notes/2-20/8.yml new file mode 100644 index 0000000000..510bf779fb --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/8.yml @@ -0,0 +1,20 @@ +--- +date: '2020-05-19' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + bugs: + - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-20/9.yml b/translations/ja-JP/data/release-notes/2-20/9.yml new file mode 100644 index 0000000000..326818d711 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-20/9.yml @@ -0,0 +1,17 @@ +--- +date: '2020-06-02' +sections: + security_fixes: + - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + bugs: + - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/0.yml b/translations/ja-JP/data/release-notes/2-21/0.yml new file mode 100644 index 0000000000..cfd8a069f8 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/0.yml @@ -0,0 +1,72 @@ +--- +date: '2020-06-09' +sections: + features: + - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + security_fixes: + - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + bugs: + - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' + changes: + - 'The web notifications interface, including new [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - 'Admins can [enable security alerts](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' + - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/1.yml b/translations/ja-JP/data/release-notes/2-21/1.yml new file mode 100644 index 0000000000..9b802bd1f3 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/1.yml @@ -0,0 +1,20 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/10.yml b/translations/ja-JP/data/release-notes/2-21/10.yml new file mode 100644 index 0000000000..65b5d9c64c --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/10.yml @@ -0,0 +1,15 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/11.yml b/translations/ja-JP/data/release-notes/2-21/11.yml new file mode 100644 index 0000000000..ce20fbe36a --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/11.yml @@ -0,0 +1,18 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/12.yml b/translations/ja-JP/data/release-notes/2-21/12.yml new file mode 100644 index 0000000000..c347bb7aca --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/12.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/13.yml b/translations/ja-JP/data/release-notes/2-21/13.yml new file mode 100644 index 0000000000..06e910bb50 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/13.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/2.yml b/translations/ja-JP/data/release-notes/2-21/2.yml new file mode 100644 index 0000000000..bdac746dbc --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/2.yml @@ -0,0 +1,20 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/3.yml b/translations/ja-JP/data/release-notes/2-21/3.yml new file mode 100644 index 0000000000..dd4ccbbb5e --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/3.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% 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: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/4.yml b/translations/ja-JP/data/release-notes/2-21/4.yml new file mode 100644 index 0000000000..e90460c88e --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/4.yml @@ -0,0 +1,27 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" + - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/5.yml b/translations/ja-JP/data/release-notes/2-21/5.yml new file mode 100644 index 0000000000..444cf28527 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/5.yml @@ -0,0 +1,15 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/6.yml b/translations/ja-JP/data/release-notes/2-21/6.yml new file mode 100644 index 0000000000..8638d1d9cd --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/6.yml @@ -0,0 +1,26 @@ +date: '2020-08-26' +sections: + security_fixes: + - >- + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, + https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} + - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + bugs: + - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' + - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' + changes: + - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/7.yml b/translations/ja-JP/data/release-notes/2-21/7.yml new file mode 100644 index 0000000000..69134720e7 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/7.yml @@ -0,0 +1,14 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/8.yml b/translations/ja-JP/data/release-notes/2-21/8.yml new file mode 100644 index 0000000000..b7bf410b13 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/8.yml @@ -0,0 +1,16 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + bugs: + - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-21/9.yml b/translations/ja-JP/data/release-notes/2-21/9.yml new file mode 100644 index 0000000000..46656c9e6b --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-21/9.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ja-JP/data/release-notes/2-22/0.yml b/translations/ja-JP/data/release-notes/2-22/0.yml new file mode 100644 index 0000000000..49d4808c59 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-22/0.yml @@ -0,0 +1,130 @@ +--- +intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. +date: '2020-09-23' +sections: + features: + - + heading: GitHub Actions Beta + notes: + - | + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + + You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + - + heading: GitHub Packages Beta + notes: + - | + [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + - + heading: Advanced Security Code Scanning Beta + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. + + Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + - + heading: Pull Request Retargeting + notes: + - | + When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + - + heading: Suspend and Unsuspend an App Installation + notes: + - | + Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + - + heading: Improved Large Scale Performance + notes: + - | + We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% 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 %}'' + + Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + - + heading: View All of Your Users + notes: + - | + For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](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: Administration Changes + notes: + - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} + - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](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 %}' + - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% 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 %} + - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% 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: Security Changes + notes: + - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](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 %} + - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - + heading: Developer Changes + notes: + - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' + - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' + - + heading: Users and organizations can add Twitter usernames to their GitHub profiles + notes: + - '[Developers and organizations can now add their Twitter username to their profile](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: API の変更 + notes: + - | + #### Graduated Previews + + The following previews are now an official part of the API: + * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} + * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} + - | + #### GraphQL Schema Changes + + * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + bugs: + - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + deprecations: + - + heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020** That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + #- type: Backup and Disaster recovery + #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} + - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} + - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a 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 %}' + - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/1.yml b/translations/ja-JP/data/release-notes/2-22/1.yml new file mode 100644 index 0000000000..fbd3988c3d --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-22/1.yml @@ -0,0 +1,71 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - | + The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - | + Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + - | + Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + - | + System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + - | + The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + - | + `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + - | + Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + - | + Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + - | + Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + - | + When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + - | + The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + - | + OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + - | + Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + - | + On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + - | + When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + - | + When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + - | + Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + - | + Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + - | + The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + - | + Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + - | + A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + - | + When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + - | + [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + - | + GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management 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: + - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} + - GitHub App Manifests now include the `request_oauth_on_install` field. {% 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: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/2.yml b/translations/ja-JP/data/release-notes/2-22/2.yml new file mode 100644 index 0000000000..dc36b39e12 --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-22/2.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + bugs: + - | + If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + - | + A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} + - | + On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + - | + When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + - | + Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} + - | + The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + - | + On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/3.yml b/translations/ja-JP/data/release-notes/2-22/3.yml new file mode 100644 index 0000000000..45442a5d4b --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-22/3.yml @@ -0,0 +1,23 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - | + **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + - | + **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + - | + Packages have been updated to the latest security versions. {% 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: + - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/4.yml b/translations/ja-JP/data/release-notes/2-22/4.yml new file mode 100644 index 0000000000..e97737ee0b --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-22/4.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + bugs: + - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} diff --git a/translations/ja-JP/data/release-notes/2-22/5.yml b/translations/ja-JP/data/release-notes/2-22/5.yml new file mode 100644 index 0000000000..0520df862f --- /dev/null +++ b/translations/ja-JP/data/release-notes/2-22/5.yml @@ -0,0 +1,22 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' + - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/ja-JP/data/reusables/accounts/create-account.md b/translations/ja-JP/data/reusables/accounts/create-account.md new file mode 100644 index 0000000000..351caf9129 --- /dev/null +++ b/translations/ja-JP/data/reusables/accounts/create-account.md @@ -0,0 +1,2 @@ +1. {% data variables.product.product_name %} の[価格]({% data variables.product.pricing_url %})ページに移動してください。 +2. {% data variables.product.product_name %} が提供するさまざまな製品およびサブスクリプションの情報をお読みいただき、選択したいプランの下にある [Upgrade] ボタンをクリックしてください。 diff --git a/translations/ja-JP/data/reusables/actions/actions-not-verified.md b/translations/ja-JP/data/reusables/actions/actions-not-verified.md index 2ab85ce6c1..3107e5a79f 100644 --- a/translations/ja-JP/data/reusables/actions/actions-not-verified.md +++ b/translations/ja-JP/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations, but unlike verified apps, {% data variables.product.prodname_dotcom %} does not review or verify individual actions listed in {% data variables.product.prodname_marketplace %}. +Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/ja-JP/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/ja-JP/data/reusables/actions/actions-packages-set-spending-limit.md new file mode 100644 index 0000000000..f07aa61371 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/actions-packages-set-spending-limit.md @@ -0,0 +1 @@ +You can set a specific spending limit or, for some accounts, allow unlimited spending. 利用上限は、{% data variables.product.prodname_registry %} と {% data variables.product.prodname_actions %} を組み合わせた範囲に適用されます。 diff --git a/translations/ja-JP/data/reusables/actions/visualization-beta.md b/translations/ja-JP/data/reusables/actions/visualization-beta.md new file mode 100644 index 0000000000..ee3ad11ef4 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/visualization-beta.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** The workflow visualization graph for {% data variables.product.prodname_actions %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ja-JP/data/reusables/apps/beta_feature_activation.md b/translations/ja-JP/data/reusables/apps/beta_feature_activation.md index 0dda3037db..d8038da90d 100644 --- a/translations/ja-JP/data/reusables/apps/beta_feature_activation.md +++ b/translations/ja-JP/data/reusables/apps/beta_feature_activation.md @@ -1,2 +1,2 @@ -4. In the left sidebar, click **Beta Features**. ![GitHub Apps or OAuth Apps section](/assets/images/github-apps/beta-features-option.png) +4. 左のサイドバーで、**Beta Features（ベータの機能）**をクリックしてください。 ![GitHub Apps or OAuth Apps section](/assets/images/github-apps/beta-features-option.png) 5. Next to the beta feature you want to enable for your app, click **Opt-in**. ![Opt-in button to enable a beta feature](/assets/images/github-apps/enable-beta-features.png) diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-api-info.md b/translations/ja-JP/data/reusables/audit_log/audit-log-api-info.md new file mode 100644 index 0000000000..55728a1692 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-api-info.md @@ -0,0 +1,5 @@ +* Access to your organization or repository settings +* Changes in permissions +* Added or removed users in an organization, repository, or team +* Users being promoted to admin +* Changes to permissions of a {% data variables.product.prodname_github_app %} diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/ja-JP/data/reusables/audit_log/audit-log-git-events-retention.md new file mode 100644 index 0000000000..3f1584bf91 --- /dev/null +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-git-events-retention.md @@ -0,0 +1 @@ +The audit log retains Git events for 7 days. This is shorter than other audit log events, which can be retained for 90 days. diff --git a/translations/ja-JP/data/reusables/classroom/about-assignments.md b/translations/ja-JP/data/reusables/classroom/about-assignments.md new file mode 100644 index 0000000000..65a3506229 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/about-assignments.md @@ -0,0 +1 @@ +Each assignment has a title and an optional deadline. You can choose the visibility of repositories that {% data variables.product.prodname_classroom %} creates and choose access permissions. You can also automatically grade assignments and create a dedicated space to discuss the assignment with the student. diff --git a/translations/ja-JP/data/reusables/classroom/about-autograding.md b/translations/ja-JP/data/reusables/classroom/about-autograding.md new file mode 100644 index 0000000000..04ed2b067c --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/about-autograding.md @@ -0,0 +1 @@ +You can use autograding to automatically check a student's work for an assignment on {% data variables.product.prodname_classroom %}. You configure tests for an assignment, and the tests run immediately every time a student pushes to an assignment repository on {% data variables.product.product_location %}. The student can view the test results, make changes, and push to see new results. diff --git a/translations/ja-JP/data/reusables/classroom/about-classrooms.md b/translations/ja-JP/data/reusables/classroom/about-classrooms.md new file mode 100644 index 0000000000..5d19bbb44a --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/about-classrooms.md @@ -0,0 +1 @@ +A classroom in {% data variables.product.prodname_classroom %} is where teachers and students interact during a course. Teachers can create a student roster for the classroom, then create, assign, review, and grade assignments within the classroom. diff --git a/translations/ja-JP/data/reusables/classroom/about-online-ides.md b/translations/ja-JP/data/reusables/classroom/about-online-ides.md new file mode 100644 index 0000000000..43818e691f --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/about-online-ides.md @@ -0,0 +1 @@ +You can optionally configure an assignment to use an online integrated development environment (IDE). Online IDEs allow your students to write code, run programs, and collaborate in a browser, without installing Git and a full development toolchain on the student's computer. If you choose an online IDE for an assignment, students can still check out and run code locally on a computer with the necessary software. diff --git a/translations/ja-JP/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/ja-JP/data/reusables/classroom/assignments-classroom-prerequisite.md new file mode 100644 index 0000000000..06284dad51 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-classroom-prerequisite.md @@ -0,0 +1 @@ +You must create a classroom before you can create an assignment. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." diff --git a/translations/ja-JP/data/reusables/classroom/assignments-click-pencil.md b/translations/ja-JP/data/reusables/classroom/assignments-click-pencil.md new file mode 100644 index 0000000000..820afd5260 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-click-pencil.md @@ -0,0 +1 @@ +1. To the right of the assignment you want to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing assignment in list of assignments](/assets/images/help/classroom/assignments-click-pencil.png) diff --git a/translations/ja-JP/data/reusables/classroom/assignments-group-definition.md b/translations/ja-JP/data/reusables/classroom/assignments-group-definition.md new file mode 100644 index 0000000000..3143cddc70 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-group-definition.md @@ -0,0 +1 @@ +A group assignment is collaborative coursework for groups of students on {% data variables.product.prodname_classroom %}. diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-assign-a-deadline.md new file mode 100644 index 0000000000..6e8e29cc11 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-assign-a-deadline.md @@ -0,0 +1,5 @@ +Optionally, you can assign a deadline to the assignment. Under "Deadline (optional)", click in the text field, then use the date picker to assign a deadline. + +
+ Date picker for assignment deadline +
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-an-online-ide.md new file mode 100644 index 0000000000..54858178a5 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -0,0 +1,5 @@ +To choose an online IDE for the assignment, select the **Select an online IDE** drop-down menu, then click the IDE you'd like your students to use. + +
+ Using the 'Select an online IDE' drop-down menu to click an online IDE for the assignment +
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-template-repository.md new file mode 100644 index 0000000000..15bcb66cb5 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-template-repository.md @@ -0,0 +1,5 @@ +Under "Add a template repository to give students starter code", select the **Select a repository** drop-down, then type a search query. In the list of results, click the template repository you'd like to use for starter code. + +
+ Using the 'Select a repository' drop-down menu to find a template repository to use as starter code for an assignment +
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 new file mode 100644 index 0000000000..3f4f17e1b2 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -0,0 +1,9 @@ +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)." + +Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. + +
+ Visibility options for assignment repositories +
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-click-continue-after-basics.md new file mode 100644 index 0000000000..b82d19fe8e --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-click-continue-after-basics.md @@ -0,0 +1,7 @@ +
+ +When you're done, click **Continue** to configure starter code and a development environment for the assignment. + +
+ 'Continue' button +
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md new file mode 100644 index 0000000000..4607b61065 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md @@ -0,0 +1,7 @@ +
+ +When you're done, click **Continue** to configure automatic grading and feedback for the project. + +
+ 'Continue' button +
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-click-create-assignment-button.md new file mode 100644 index 0000000000..935d73f5df --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-click-create-assignment-button.md @@ -0,0 +1,5 @@ +To create the assignment, click **Create assignment**. + +
+ 'Create assignment' button +
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-create-review-pull-request.md new file mode 100644 index 0000000000..5cc14ee9ff --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-create-review-pull-request.md @@ -0,0 +1,5 @@ +To create pull requests for the discussion of feedback, select **Enable feedback pull requests**. + +
+ Checkbox for 'Enable feedback pull requests' +
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-create-the-assignment.md new file mode 100644 index 0000000000..051e169c57 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -0,0 +1,5 @@ +To create an assignment, sign into {% data variables.product.prodname_classroom_with_url %} and navigate to a classroom. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click **New assignment**. + +
+ The 'New assignment' button +
diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-intro-for-environment.md new file mode 100644 index 0000000000..bda2c39723 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-intro-for-environment.md @@ -0,0 +1 @@ +Optionally, decide whether to provide empty repositories or starter code, and preconfigure a development environment for your students. diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md new file mode 100644 index 0000000000..6290d808ad --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md @@ -0,0 +1,3 @@ +{% data reusables.classroom.classroom-enables-invitation-urls %} + +{% data reusables.classroom.invitation-url-warning %} diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-prevent-changes.md new file mode 100644 index 0000000000..9ef39a18b9 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-prevent-changes.md @@ -0,0 +1,7 @@ +You can prevent students from changing files that contain tests for autograding, or other important files in the assignment repository. + +Under "Protected file paths", type relative paths within the repository to protect. + +
+ Text field for typing protected file paths +
\ No newline at end of file diff --git a/translations/ja-JP/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/ja-JP/data/reusables/classroom/assignments-guide-using-autograding.md new file mode 100644 index 0000000000..5f50beec64 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-guide-using-autograding.md @@ -0,0 +1,23 @@ +{% data reusables.classroom.about-autograding %} For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." + +{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} For more information, see "[Grading methods](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)." + +
+ Using the 'Add test' drop-down menu to click a grading method +
+ +
+ +Define the parameters of your test case, like the name, commands, inputs, outputs, timeout, and points. When you're done, click **Save test case**. + +
+ 'Save test case' button for an autograding test +
+ +
+ +You can add more tests with the **Add test** drop-down menu, and you can edit or delete existing tests with {% octicon "pencil" aria-label="The pencil icon" %} or {% octicon "trash" aria-label="The trash icon" %}. + +
+ Pencil and trash icons to edit or delete an autograding test +
\ No newline at end of file diff --git a/translations/ja-JP/data/reusables/classroom/assignments-individual-definition.md b/translations/ja-JP/data/reusables/classroom/assignments-individual-definition.md new file mode 100644 index 0000000000..33425ae2c3 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-individual-definition.md @@ -0,0 +1 @@ +An individual assignment is coursework for each student who participates in a course on {% data variables.product.prodname_classroom %}. The student is intended to complete an individual assignment without help from other students. diff --git a/translations/ja-JP/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/ja-JP/data/reusables/classroom/assignments-to-prevent-submission.md new file mode 100644 index 0000000000..62bd9cc2da --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-to-prevent-submission.md @@ -0,0 +1 @@ +To prevent acceptance or submission of an assignment by students, deselect **Enable assignment invitation URL**. To edit the assignment, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment**. diff --git a/translations/ja-JP/data/reusables/classroom/assignments-type-a-title.md b/translations/ja-JP/data/reusables/classroom/assignments-type-a-title.md new file mode 100644 index 0000000000..20d32397ac --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/assignments-type-a-title.md @@ -0,0 +1,5 @@ +Type a title for the assignment. Optionally, click {% octicon "pencil" aria-label="The pencil icon" %} to edit the prefix. + +
+ Assignment title and prefix +
diff --git a/translations/ja-JP/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/ja-JP/data/reusables/classroom/classroom-creates-group-repositories.md new file mode 100644 index 0000000000..10cdc5924a --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/classroom-creates-group-repositories.md @@ -0,0 +1 @@ +For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.product_name %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. diff --git a/translations/ja-JP/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/ja-JP/data/reusables/classroom/classroom-creates-individual-repositories.md new file mode 100644 index 0000000000..4108abf9ad --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -0,0 +1 @@ +When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.product_name %}. diff --git a/translations/ja-JP/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/ja-JP/data/reusables/classroom/classroom-enables-invitation-urls.md new file mode 100644 index 0000000000..1b357c3a2d --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/classroom-enables-invitation-urls.md @@ -0,0 +1 @@ +By default, {% data variables.product.prodname_classroom %} enables an invitation URL for each assignment you create. Students can accept and submit the assignment while the invitation URL is enabled. You can share the URL with your students on your LMS, course homepage, or wherever you post assignments. Students can also navigate to the assignment on {% data variables.product.prodname_classroom %} if the student has already accepted an assignment for the classroom. diff --git a/translations/ja-JP/data/reusables/classroom/click-assignment-in-list.md b/translations/ja-JP/data/reusables/classroom/click-assignment-in-list.md new file mode 100644 index 0000000000..347d0bc108 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/click-assignment-in-list.md @@ -0,0 +1 @@ +1. In the list of assignments, click the assignment you want to view. ![Assignment in list of assignments for an classroom](/assets/images/help/classroom/click-assignment-in-list.png) diff --git a/translations/ja-JP/data/reusables/classroom/click-classroom-in-list.md b/translations/ja-JP/data/reusables/classroom/click-classroom-in-list.md new file mode 100644 index 0000000000..fe7d091cdc --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/click-classroom-in-list.md @@ -0,0 +1 @@ +1. In the list of classrooms, click the classroom you want to view. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) diff --git a/translations/ja-JP/data/reusables/classroom/click-settings.md b/translations/ja-JP/data/reusables/classroom/click-settings.md new file mode 100644 index 0000000000..9fe6b33d6b --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/click-settings.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" tab for classroom](/assets/images/help/classroom/click-settings.png) diff --git a/translations/ja-JP/data/reusables/classroom/click-students.md b/translations/ja-JP/data/reusables/classroom/click-students.md new file mode 100644 index 0000000000..13df0b1e40 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/click-students.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**. !["Students" tab for classroom](/assets/images/help/classroom/click-students.png) diff --git a/translations/ja-JP/data/reusables/classroom/for-more-information-about-assignment-creation.md b/translations/ja-JP/data/reusables/classroom/for-more-information-about-assignment-creation.md new file mode 100644 index 0000000000..8fd113d763 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/for-more-information-about-assignment-creation.md @@ -0,0 +1 @@ +For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." 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 new file mode 100644 index 0000000000..e554d4b605 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/guide-create-new-classroom.md @@ -0,0 +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. 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/ja-JP/data/reusables/classroom/invitation-url-warning.md b/translations/ja-JP/data/reusables/classroom/invitation-url-warning.md new file mode 100644 index 0000000000..f85e808ddc --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/invitation-url-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning**: Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a user account on {% data variables.product.product_name %} with an identifier in your roster. + +{% endwarning %} diff --git a/translations/ja-JP/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/ja-JP/data/reusables/classroom/readme-contains-button-for-online-ide.md new file mode 100644 index 0000000000..fac85f79f1 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -0,0 +1 @@ +When a student accepts an assignment with an online IDE, the assignment repository will include a _README.md_ file with a special button at the top of the file. The button links the student directly to the workspace in the online IDE. diff --git a/translations/ja-JP/data/reusables/classroom/sign-into-github-classroom.md b/translations/ja-JP/data/reusables/classroom/sign-into-github-classroom.md new file mode 100644 index 0000000000..578bf7213e --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/sign-into-github-classroom.md @@ -0,0 +1 @@ +1. Sign into {% data variables.product.prodname_classroom_with_url %}. diff --git a/translations/ja-JP/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/ja-JP/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md new file mode 100644 index 0000000000..2486daf0a4 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md @@ -0,0 +1 @@ +Under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. diff --git a/translations/ja-JP/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/ja-JP/data/reusables/classroom/you-can-choose-a-template-repository.md new file mode 100644 index 0000000000..40eb9d273b --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -0,0 +1 @@ +You can optionally choose a template repository as starter code for the assignment. The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}. diff --git a/translations/ja-JP/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/ja-JP/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md new file mode 100644 index 0000000000..e9592fb832 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md @@ -0,0 +1 @@ +You can automatically create a pull request where you can provide feedback and answer a student's questions about an assignment. For more information about the review of changes in a pull request, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)." diff --git a/translations/ja-JP/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md b/translations/ja-JP/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md new file mode 100644 index 0000000000..af5be0c098 --- /dev/null +++ b/translations/ja-JP/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md @@ -0,0 +1 @@ +You may want to predefine the default settings for the assignment repositories that {% data variables.product.prodname_classroom %} creates from a template repository. For example, you may want to disable issues, define labels for pull requests, or protect a branch in some or all of the repositories. diff --git a/translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md b/translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md index 8a1128db5e..41cdb74888 100644 --- a/translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md +++ b/translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md @@ -1 +1 @@ -{% data variables.product.prodname_codespaces %} is free to use during the beta. When {% data variables.product.prodname_codespaces %} becomes generally available, you will be billed for storage and compute usage. +{% data variables.product.prodname_codespaces %} is free to use during the beta. {% data variables.product.prodname_codespaces %} が一般提供されると、ストレージとコンピューティングの使用量に対して課金されます。 diff --git a/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md b/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md new file mode 100644 index 0000000000..b8d2b78cbc --- /dev/null +++ b/translations/ja-JP/data/reusables/dependabot/private-dependencies-note.md @@ -0,0 +1,3 @@ +When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)." + +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file 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 3bb2a8366f..84342d6571 100644 --- a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md @@ -1,20 +1,23 @@ -| パッケージマネージャー | Supports vendoring | -| -------------------------------- |:------------------:| -| Bundler: `bundler` | **X** | -| Cargo: `cargo` | | -| Composer: `composer` | | -| Docker: `docker` | | -| Elm: `elm` | | -| gitサブモジュール:`gitsubmodule` | | -| GitHub Actions: `github-actions` | | -| Goモジュール:`gomod` | **X** | -| Gradle: `gradle` | | -| Maven: `maven` | | -| Mix: `mix` | | -| npm: `npm` | | -| NuGet: `nuget` | | -| pip: `pip` | | -| Terraform: `terraform` | | +The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. + +| パッケージマネージャー | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | +| -------------------------------- |:-----------------------------------------------------------------:|:---------:| +| Bundler: `bundler` | | **✓** | +| Cargo: `cargo` | **✓** | | +| Composer: `composer` | **✓** | | +| Docker: `docker` | **✓** | | +| Elixir: `hex` | | | +| Elm: `elm` | **✓** | | +| gitサブモジュール:`gitsubmodule` | **✓** | | +| GitHub Actions: `github-actions` | **✓** | | +| Goモジュール:`gomod` | **✓** | **✓** | +| Gradle: `gradle` | **✓** | | +| Maven: `maven` | **✓** | | +| Mix: `mix` | **✓** | | +| npm: `npm` | **✓** | | +| NuGet: `nuget` | **✓** | | +| pip: `pip` | | | +| Terraform: `terraform` | **✓** | | {% note %} diff --git a/translations/ja-JP/data/reusables/discussions/about-categories-and-formats.md b/translations/ja-JP/data/reusables/discussions/about-categories-and-formats.md new file mode 100644 index 0000000000..a17ca2ca53 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/about-categories-and-formats.md @@ -0,0 +1 @@ +All discussions must be created in a category, and repository administrators and maintainers define the categories for a repository. Categories can contain open-ended conversations, or conversations with a question/answer format. diff --git a/translations/ja-JP/data/reusables/discussions/about-discussions.md b/translations/ja-JP/data/reusables/discussions/about-discussions.md new file mode 100644 index 0000000000..c61b8b0f0a --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/about-discussions.md @@ -0,0 +1 @@ +Discussions are an open forum for conversation among maintainers and the community for a project on {% data variables.product.product_name %}. diff --git a/translations/ja-JP/data/reusables/discussions/beta.md b/translations/ja-JP/data/reusables/discussions/beta.md new file mode 100644 index 0000000000..bceda98fd2 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/beta.md @@ -0,0 +1,5 @@ +{% note %} + +**ノート:** {% data variables.product.prodname_discussions %}は現在ベータで、変更されることがあります。 + +{% endnote %} diff --git a/translations/ja-JP/data/reusables/discussions/click-discussion-in-list.md b/translations/ja-JP/data/reusables/discussions/click-discussion-in-list.md new file mode 100644 index 0000000000..8156c86331 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/click-discussion-in-list.md @@ -0,0 +1 @@ +1. In the list of discussions, click the discussion you want to view. ![Discussion in list of discussions for a repository](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/ja-JP/data/reusables/discussions/discussions-tab.md b/translations/ja-JP/data/reusables/discussions/discussions-tab.md new file mode 100644 index 0000000000..67795aa5ae --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/discussions-tab.md @@ -0,0 +1 @@ +1. Under your repository name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. !["Discussions" tab for a repository](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/translations/ja-JP/data/reusables/discussions/edit-categories.md b/translations/ja-JP/data/reusables/discussions/edit-categories.md new file mode 100644 index 0000000000..6f4f6af574 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/edit-categories.md @@ -0,0 +1 @@ +1. To the right of "Categories", click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing categories](/assets/images/help/discussions/click-edit-categories.png) diff --git a/translations/ja-JP/data/reusables/discussions/edit-category-details.md b/translations/ja-JP/data/reusables/discussions/edit-category-details.md new file mode 100644 index 0000000000..8004b70314 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/edit-category-details.md @@ -0,0 +1 @@ +Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." diff --git a/translations/ja-JP/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/ja-JP/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md new file mode 100644 index 0000000000..95ff0e10f0 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -0,0 +1,5 @@ +You can enable or disable discussions for a repository. + +{% data reusables.repositories.navigate-to-repo %} +1. リポジトリ名の下で{% octicon "gear" aria-label="The gear icon" %} **Settings（設定）**をクリックしてください。 ![リポジトリの設定ボタン](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", select **Discussions**. ![Checkbox under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/ja-JP/data/reusables/discussions/github-recognizes-members.md b/translations/ja-JP/data/reusables/discussions/github-recognizes-members.md new file mode 100644 index 0000000000..b6874b910d --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/github-recognizes-members.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. diff --git a/translations/ja-JP/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/ja-JP/data/reusables/discussions/marking-a-comment-as-an-answer.md new file mode 100644 index 0000000000..bdefffdea0 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -0,0 +1,14 @@ +You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +When you mark a question as an answer, {% data variables.product.product_name %} will highlight the comment and replies to the comment to help visitors quickly find the answer. + +![Comment marked as answer to a discussion](/assets/images/help/discussions/comment-marked-as-answer.png) + +You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the unanswered discussion you want to mark as answered. ![Unanswered discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the discussion, find the comment you want to mark as the answer. +1. In the upper-right corner of the comment, click {% octicon "check-circle" aria-label="The circular check icon" %}. !["Mark as answer" circular check icon for marking comment as answer in a discussion](/assets/images/help/discussions/comment-mark-as-answer-button.png) +1. Optionally, to unmark a comment as the answer, click {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. diff --git a/translations/ja-JP/data/reusables/discussions/repository-category-limit.md b/translations/ja-JP/data/reusables/discussions/repository-category-limit.md new file mode 100644 index 0000000000..293d3632b5 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/repository-category-limit.md @@ -0,0 +1 @@ +Each repository can have up to 10 categories. diff --git a/translations/ja-JP/data/reusables/discussions/starting-a-discussion.md b/translations/ja-JP/data/reusables/discussions/starting-a-discussion.md new file mode 100644 index 0000000000..242e3abf9b --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/starting-a-discussion.md @@ -0,0 +1,6 @@ +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Click **New discussion**. !["New discussion" button within the "Discussions" tab for a repository](/assets/images/help/discussions/new-discussion-button.png) +1. Select the **Select Category** drop-down menu, and click a category for your discussion. !["Select Category" drop-down menu and list of available categories in a repository](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) +1. Type a title and body for your discussion. ![Text fields for new discussion's title and body](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) diff --git a/translations/ja-JP/data/reusables/discussions/you-can-categorize-discussions.md b/translations/ja-JP/data/reusables/discussions/you-can-categorize-discussions.md new file mode 100644 index 0000000000..bb05316d77 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/you-can-categorize-discussions.md @@ -0,0 +1 @@ +You can categorize discussions to help community members begin conversations in the right place, and to help community members find related discussions. diff --git a/translations/ja-JP/data/reusables/discussions/you-can-convert-an-issue.md b/translations/ja-JP/data/reusables/discussions/you-can-convert-an-issue.md new file mode 100644 index 0000000000..1421256e1f --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/you-can-convert-an-issue.md @@ -0,0 +1 @@ +If an issue turns out to be a question or open-ended conversation instead of a work item to track and prioritize, you can convert the issue to a discussion. diff --git a/translations/ja-JP/data/reusables/discussions/you-can-use-discussions.md b/translations/ja-JP/data/reusables/discussions/you-can-use-discussions.md new file mode 100644 index 0000000000..27c1ba7cb2 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/you-can-use-discussions.md @@ -0,0 +1 @@ +You can use discussions to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/discussions/you-cannot-convert-a-discussion.md b/translations/ja-JP/data/reusables/discussions/you-cannot-convert-a-discussion.md new file mode 100644 index 0000000000..9e9b687b67 --- /dev/null +++ b/translations/ja-JP/data/reusables/discussions/you-cannot-convert-a-discussion.md @@ -0,0 +1 @@ +You cannot convert a discussion to an issue. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/ja-JP/data/reusables/dotcom_billing/actions-packages-unpaid-account.md index c4524745c4..92071d66e4 100644 --- a/translations/ja-JP/data/reusables/dotcom_billing/actions-packages-unpaid-account.md +++ b/translations/ja-JP/data/reusables/dotcom_billing/actions-packages-unpaid-account.md @@ -2,4 +2,4 @@ * {% data variables.product.prodname_actions %}と{% data variables.product.prodname_registry %}のアカウントに含まれるストレージや分は、支払いの処理が成功するまでリセットされません。 * 現在の支払い期間に対して残っているストレージや分をもつアカウントに対して、{% data variables.product.prodname_actions %}及び{% data variables.product.prodname_registry %}は、含まれる利用に到達するまでは引き続き利用できます。 -* {% data variables.product.prodname_actions %}あるいは{% data variables.product.prodname_registry %}に対する現在の支払い期間に含まれる利用に達したアカウントについては、{% data variables.product.prodname_actions %}と{% data variables.product.prodname_registry %}はどちらもそれ以上の超過を避けるため、無効化されます。 アカウントの支払いを請求書で行う場合には、[営業チームに連絡](https://enterprise.github.com/contact)し、支払いを処理して利用状況をリセットしなければなりません。 +* {% data variables.product.prodname_actions %}あるいは{% data variables.product.prodname_registry %}に対する現在の支払い期間に含まれる利用に達したアカウントについては、{% data variables.product.prodname_actions %}と{% data variables.product.prodname_registry %}はどちらもそれ以上の超過を避けるため、無効化されます。 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 7d3008b84c..db36f0cbec 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 %} について](https://education.github.com/partners/schools)」を参照してください。 +個人の割引を適用する前に、あなたの学習コミュニティがすでに弊社と{% data variables.product.prodname_education %}学校としてパートナーになっているかを確認してください。 詳しい情報については、「[{% data variables.product.prodname_education %} について](/education/teach-and-learn-with-github-education/about-github-education)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/education/apply-for-team.md b/translations/ja-JP/data/reusables/education/apply-for-team.md index f8af616e90..3fa2344166 100644 --- a/translations/ja-JP/data/reusables/education/apply-for-team.md +++ b/translations/ja-JP/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- 無料の[{% data variables.product.prodname_team %}](/articles/github-s-products)に応募してください。{% data variables.product.prodname_team %}では、無制限のユーザとプライベートリポジトリが利用できます。 詳細は「[教育者割引または研究者割引に応募する](/articles/applying-for-an-educator-or-researcher-discount)」を参照してください。 +- 無料の[{% data variables.product.prodname_team %}](/articles/github-s-products)に応募してください。{% data variables.product.prodname_team %}では、無制限のユーザとプライベートリポジトリが利用できます。 For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." diff --git a/translations/ja-JP/data/reusables/education/click-get-teacher-benefits.md b/translations/ja-JP/data/reusables/education/click-get-teacher-benefits.md new file mode 100644 index 0000000000..25bbacd747 --- /dev/null +++ b/translations/ja-JP/data/reusables/education/click-get-teacher-benefits.md @@ -0,0 +1 @@ +1. Under "Individuals", click **Get teacher benefits**. !["Get teacher benefits" on {% data variables.product.prodname_education %} homepage](/assets/images/help/education/click-get-teacher-benefits.png) diff --git a/translations/ja-JP/data/reusables/education/educator-requirements.md b/translations/ja-JP/data/reusables/education/educator-requirements.md new file mode 100644 index 0000000000..38a8db61bc --- /dev/null +++ b/translations/ja-JP/data/reusables/education/educator-requirements.md @@ -0,0 +1,6 @@ +To apply for an educator or researcher discount, you must meet the following requirements. + +- 教育者、教職員、または研究者であること. +- Have a verifiable school-issued email address. +- Upload documents that prove your school affiliation. +- Have a user account on {% data variables.product.product_name %}. diff --git a/translations/ja-JP/data/reusables/gated-features/discussions.md b/translations/ja-JP/data/reusables/gated-features/discussions.md new file mode 100644 index 0000000000..5ada0a25ee --- /dev/null +++ b/translations/ja-JP/data/reusables/gated-features/discussions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_discussions %} is available in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/ja-JP/data/reusables/github-actions/actions-billing.md b/translations/ja-JP/data/reusables/github-actions/actions-billing.md index 4fe173f909..283a221a48 100644 --- a/translations/ja-JP/data/reusables/github-actions/actions-billing.md +++ b/translations/ja-JP/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. プライベートリポジトリでは、それぞれの{% data variables.product.prodname_dotcom %}アカウントは使用している製品に応じて一定量の無料の分とストレージを受け取ります。 +{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. プライベートリポジトリでは、それぞれの{% data variables.product.prodname_dotcom %}アカウントは使用している製品に応じて一定量の無料の分とストレージを受け取ります。 Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md b/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md index 81c2310549..a2e6f4f909 100644 --- a/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md +++ b/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -##### **1つのイベントを使用する例** +##### 1つのイベントを使用する例 ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -##### **イベントのリストを使用する例** +##### イベントのリストを使用する例 ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -##### **アクティビティの種類もしくは設定を伴う複数のイベントを使用する例** +##### アクティビティの種類もしくは設定を伴う複数のイベントを使用する例 イベントに対してアクティビティの種類もしくは設定を指定する必要がある場合、それぞれのイベントを個別に設定しなければなりません。 設定を持たないイベントも含め、すべてのイベントにはコロン (`:`)を追加しなければなりません。 diff --git a/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-brief.md new file mode 100644 index 0000000000..20d912fb21 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-detailed.md new file mode 100644 index 0000000000..b5695b9925 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/actions-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.github-actions.actions-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where a workflow is run. アカウントのクーポンは、{% data variables.product.prodname_actions %}の過剰分には適用されません。 diff --git a/translations/ja-JP/data/reusables/github-actions/contacting-support.md b/translations/ja-JP/data/reusables/github-actions/contacting-support.md index a91aaa37e2..c563d37da6 100644 --- a/translations/ja-JP/data/reusables/github-actions/contacting-support.md +++ b/translations/ja-JP/data/reusables/github-actions/contacting-support.md @@ -1,4 +1,4 @@ -たとえば構文、{% data variables.product.prodname_dotcom %}ホストランナー、アクションの構築など、ワークフローの設定に関して何か支援が必要な場合は、[{% data variables.product.prodname_gcf %}の{% data variables.product.prodname_actions %}ボード](https://github.community/c/github-actions)で既存のトピックを探してみるか、新しいトピックを開始してください。 +If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). {% data variables.product.prodname_actions %}についてのフィードバックもしくは機能リクエストがあるなら、それらを{% data variables.contact.contact_feedback_actions %}で共有してください。 diff --git a/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md b/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md index 88a2d482c4..e6db4f8803 100644 --- a/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/ja-JP/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The MacOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the MacOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/ja-JP/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/ja-JP/data/reusables/github-actions/publish-to-maven-workflow-step.md index c2d86e88ed..ab87d8d36c 100644 --- a/translations/ja-JP/data/reusables/github-actions/publish-to-maven-workflow-step.md +++ b/translations/ja-JP/data/reusables/github-actions/publish-to-maven-workflow-step.md @@ -1 +1 @@ -`ossrh`リポジトリへ公開するために`mvn -B deploy`コマンドを実行してください。 環境変数の`MAVEN_USERNAME`は`OSSRH_USERNAME`シークレットの内容で、環境変数の`MAVEN_PASSWORD`は`OSSRH_TOKEN`シークレットの内容で設定されます。 +Runs the `mvn --batch-mode deploy` command to publish to the `ossrh` repository. 環境変数の`MAVEN_USERNAME`は`OSSRH_USERNAME`シークレットの内容で、環境変数の`MAVEN_PASSWORD`は`OSSRH_TOKEN`シークレットの内容で設定されます。 diff --git a/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md index 5a3db3270a..7d47b1f0bc 100644 --- a/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ b/translations/ja-JP/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -{% data variables.product.prodname_registry %}に公開するために`mvn -B deploy`コマンドを実行してください。 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 +Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. 環境変数`GITHUB_TOKEN`には、`GITHUB_TOKEN`シークレットの内容が設定されます。 diff --git a/translations/ja-JP/data/reusables/github-insights/download-latest-release.md b/translations/ja-JP/data/reusables/github-insights/download-latest-release.md index 5d918cecc2..0470ab34cf 100644 --- a/translations/ja-JP/data/reusables/github-insights/download-latest-release.md +++ b/translations/ja-JP/data/reusables/github-insights/download-latest-release.md @@ -1,3 +1,3 @@ -1. アプリケーションサーバーから、`github/insights-releases`の[リリースページ](https://github.com/github/insights-releases/releases/latest)上の最新の{% data variables.product.prodname_insights %}リリースにアクセスしてください。 +1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the Releases page for `github/insights-releases`. 2. 最新のリリースをダウンロードするために、"Assets（アセット）"の下の`insights-VERSION.tar.gz`をクリックしてください。 ![アセットのインストール](/assets/images/help/insights/installation-tgz.png) 3. ディレクトリをUnzipしてください。 diff --git a/translations/ja-JP/data/reusables/issue-events/issue-event-common-properties.md b/translations/ja-JP/data/reusables/issue-events/issue-event-common-properties.md index 0fd49cd43d..2d82946ae0 100644 --- a/translations/ja-JP/data/reusables/issue-events/issue-event-common-properties.md +++ b/translations/ja-JP/data/reusables/issue-events/issue-event-common-properties.md @@ -1,10 +1,10 @@ -| 名前 | 種類 | 説明 | -| ------------ | --------- | ------------------------------------------------------------------------- | -| `id` | `integer` | The unique identifier of the event. | -| `node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event. | -| `url` | `string` | The REST API URL for fetching the event. | -| `actor` | `オブジェクト` | The person who generated the event. | -| `event` | `string` | Identifies the actual type of event that occurred. | -| `commit_id` | `string` | The SHA of the commit that referenced this issue. | -| `commit_url` | `string` | The GitHub REST API link to the commit that referenced this issue. | -| `created_at` | `string` | The timestamp indicating when the event occurred. | +| 名前 | 種類 | 説明 | +| ------------ | --------- | ------------------------------------------------------------------ | +| `id` | `integer` | イベントの一意の識別子。 | +| `node_id` | `string` | イベントの[グローバルノード ID](/graphql/guides/using-global-node-ids)。 | +| `url` | `string` | The REST API URL for fetching the event. | +| `actor` | `オブジェクト` | イベントを生成したユーザ。 | +| `event` | `string` | Identifies the actual type of event that occurred. | +| `commit_id` | `string` | The SHA of the commit that referenced this issue. | +| `commit_url` | `string` | The GitHub REST API link to the commit that referenced this issue. | +| `created_at` | `string` | The timestamp indicating when the event occurred. | diff --git a/translations/ja-JP/data/reusables/marketplace/app-transfer-to-org-for-verification.md b/translations/ja-JP/data/reusables/marketplace/app-transfer-to-org-for-verification.md new file mode 100644 index 0000000000..0621a9e6e9 --- /dev/null +++ b/translations/ja-JP/data/reusables/marketplace/app-transfer-to-org-for-verification.md @@ -0,0 +1 @@ +If you want to sell an app that's owned by your user account, first you'll need to transfer the app to an organization, and then request verification for a listing created by the organization. diff --git a/translations/ja-JP/data/reusables/marketplace/free-plan-note.md b/translations/ja-JP/data/reusables/marketplace/free-plan-note.md new file mode 100644 index 0000000000..9db67ca394 --- /dev/null +++ b/translations/ja-JP/data/reusables/marketplace/free-plan-note.md @@ -0,0 +1,5 @@ +{% note %} + +**ノート:**{% data variables.product.prodname_marketplace %}上でアプリケーションをリストする場合、{% data variables.product.prodname_marketplace %}の外部で有料サービスを提供しているなら無料プランでアプリケーションをリストすることはできません。 + +{% endnote %} diff --git a/translations/ja-JP/data/reusables/marketplace/launch-with-free.md b/translations/ja-JP/data/reusables/marketplace/launch-with-free.md index 15230e218b..2151c241cc 100644 --- a/translations/ja-JP/data/reusables/marketplace/launch-with-free.md +++ b/translations/ja-JP/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can submit both an unverified and verified app. This will allow you to launch with a free version of your app. Once GitHub verifies your app, your listing will change from unverified to verified in {% data variables.product.prodname_marketplace %} and GitHub will publish your new pricing plans. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/ja-JP/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/ja-JP/data/reusables/marketplace/marketplace-billing-ui-requirements.md index 9c02badeae..5aa91ca839 100644 --- a/translations/ja-JP/data/reusables/marketplace/marketplace-billing-ui-requirements.md +++ b/translations/ja-JP/data/reusables/marketplace/marketplace-billing-ui-requirements.md @@ -1,7 +1,7 @@ -- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} must be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} It's highly recommended to allow customers to re-enable their previous plan. -- Customers must be able to upgrade from your app's UI if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` -- Customers must be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. -- Customers must be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: +- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} should be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} It's highly recommended to allow customers to re-enable their previous plan. +- Customers should be able to upgrade from your app's user interface if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` +- Customers should be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. +- Customers should be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: - Current plan and price. - New plans purchased. - Upgrades, downgrades, cancellations, and the number of remaining days in a free trial. diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate-packages.md b/translations/ja-JP/data/reusables/package_registry/authenticate-packages.md index 4c2a168f02..075ac8d549 100644 --- a/translations/ja-JP/data/reusables/package_registry/authenticate-packages.md +++ b/translations/ja-JP/data/reusables/package_registry/authenticate-packages.md @@ -3,7 +3,7 @@ {% if currentVersion == "free-pro-team@latest" %} To authenticate using a {% data variables.product.prodname_actions %}のワークフロー: -- For package registries (`PACKAGE-REGISTRY.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`), you can use a `GITHUB_TOKEN`. +- 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. {% else %} To authenticate to diff --git a/translations/ja-JP/data/reusables/package_registry/billing-for-container-registry.md b/translations/ja-JP/data/reusables/package_registry/billing-for-container-registry.md index 7cf8e2459f..479e2d5b55 100644 --- a/translations/ja-JP/data/reusables/package_registry/billing-for-container-registry.md +++ b/translations/ja-JP/data/reusables/package_registry/billing-for-container-registry.md @@ -1,3 +1,3 @@ -During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." +During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-docker-for-use-with-github-packages)." After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the container registry. 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)." diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-beta-billing-note.md b/translations/ja-JP/data/reusables/package_registry/container-registry-beta-billing-note.md index 8a290f9344..95e543e0a5 100644 --- a/translations/ja-JP/data/reusables/package_registry/container-registry-beta-billing-note.md +++ b/translations/ja-JP/data/reusables/package_registry/container-registry-beta-billing-note.md @@ -1,5 +1,5 @@ {% note %} -**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. 詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/getting-started-with-github-container-registry/about-github-container-registry)」を参照してください。 +**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. 詳しい情報については「[{% data variables.product.prodname_github_container_registry %}について](/packages/guides/about-github-container-registry)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md b/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md index 77cc289fce..27ba66e317 100644 --- a/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md +++ b/translations/ja-JP/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" and "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**注釈:** {% data variables.product.prodname_github_container_registry %} は現在パブリックベータであり、変更されることがあります。 During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} diff --git a/translations/ja-JP/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/ja-JP/data/reusables/package_registry/docker_registry_deprecation_status.md index 2df9364c31..a23fdc598b 100644 --- a/translations/ja-JP/data/reusables/package_registry/docker_registry_deprecation_status.md +++ b/translations/ja-JP/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -1,5 +1,5 @@ {% warning %} -**Note:** The {% data variables.product.prodname_registry %} Docker registry will be superseded by {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} in a future {% data variables.product.product_name %} release{% endif %}.{% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" and "[Getting started with {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry)."{% endif %} +**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 %} {% endwarning %} diff --git a/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md index b0cddc8bcb..3b74dd6c78 100644 --- a/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md +++ b/translations/ja-JP/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/package_registry/packages-billing.md b/translations/ja-JP/data/reusables/package_registry/packages-billing.md index 33fff043bf..73e4087efb 100644 --- a/translations/ja-JP/data/reusables/package_registry/packages-billing.md +++ b/translations/ja-JP/data/reusables/package_registry/packages-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_registry %}の利用は、パブリックパッケージについては無料です。 プライベートパッケージについては、それぞれの{% data variables.product.product_name %}アカウントは一定量の無料のストレージとデータ転送を、そのアカウントで使っている製品に応じて受け取ります。 デフォルトではアカウントの料金の上限は$0になっており、含まれている量に達した後に追加でストレージやデータ転送が利用されないようになっています。 デフォルトの$0を超えて利用上限を増やしたなら、追加のストレージやデータ転送に対しては利用上限を最大として課金されます。これは過剰分とも呼ばれます。 アカウントのクーポンは、{% data variables.product.prodname_registry %}の過剰分には適用されません。 +{% data variables.product.prodname_registry %}の利用は、パブリックパッケージについては無料です。 プライベートパッケージについては、それぞれの{% data variables.product.product_name %}アカウントは一定量の無料のストレージとデータ転送を、そのアカウントで使っている製品に応じて受け取ります。 Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ja-JP/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/ja-JP/data/reusables/package_registry/packages-spending-limit-brief.md new file mode 100644 index 0000000000..ea07621d29 --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/packages-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/ja-JP/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/ja-JP/data/reusables/package_registry/packages-spending-limit-detailed.md new file mode 100644 index 0000000000..dd5845d6d1 --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/packages-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.package_registry.packages-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. アカウントのクーポンは、{% data variables.product.prodname_registry %}の過剰分には適用されません。 diff --git a/translations/ja-JP/data/reusables/package_registry/required-scopes.md b/translations/ja-JP/data/reusables/package_registry/required-scopes.md index a59ba109a8..706be80670 100644 --- a/translations/ja-JP/data/reusables/package_registry/required-scopes.md +++ b/translations/ja-JP/data/reusables/package_registry/required-scopes.md @@ -1 +1 @@ -{% data variables.product.prodname_registry %}内でパッケージを公開及びインストールするためには、適切なスコープで個人アクセストークンを使わなければなりません。 詳しい情報については「[{% data variables.product.prodname_registry %}について](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)」を参照してください。 +{% data variables.product.prodname_registry %}内でパッケージを公開及びインストールするためには、適切なスコープで個人アクセストークンを使わなければなりません。 詳しい情報については「[{% data variables.product.prodname_registry %}について](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/package_registry/viewing-packages.md b/translations/ja-JP/data/reusables/package_registry/viewing-packages.md index a91c34b0fe..0eb1c09651 100644 --- a/translations/ja-JP/data/reusables/package_registry/viewing-packages.md +++ b/translations/ja-JP/data/reusables/package_registry/viewing-packages.md @@ -1 +1 @@ -パッケージを公開した後は、{% data variables.product.prodname_dotcom %}上でそのパッケージを見ることができます。 詳しい情報については「[パッケージの表示](/packages/publishing-and-managing-packages/viewing-packages)」を参照してください。 +パッケージを公開した後は、{% data variables.product.prodname_dotcom %}上でそのパッケージを見ることができます。 詳しい情報については「[パッケージの表示](/packages/manage-packages/viewing-packages)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/dependency-review.md b/translations/ja-JP/data/reusables/repositories/dependency-review.md new file mode 100644 index 0000000000..e780074c3c --- /dev/null +++ b/translations/ja-JP/data/reusables/repositories/dependency-review.md @@ -0,0 +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)." +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/repositories/navigate-to-job-superlinter.md b/translations/ja-JP/data/reusables/repositories/navigate-to-job-superlinter.md index a389d235a1..0fac301855 100644 --- a/translations/ja-JP/data/reusables/repositories/navigate-to-job-superlinter.md +++ b/translations/ja-JP/data/reusables/repositories/navigate-to-job-superlinter.md @@ -1,5 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. 左のサイドバーで、表示させたいジョブをクリックしてください。 ![Lint コードベースジョブ](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% else %} 1. 左のサイドバーで、表示させたいジョブをクリックしてください。 ![ワークフロージョブを選択](/assets/images/help/repository/workflow-job.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/request-changes-tips.md b/translations/ja-JP/data/reusables/repositories/request-changes-tips.md index 2fcc3e8c36..377bbc0b0d 100644 --- a/translations/ja-JP/data/reusables/repositories/request-changes-tips.md +++ b/translations/ja-JP/data/reusables/repositories/request-changes-tips.md @@ -1,6 +1,6 @@ {% tip %} -**Tips**: +**ヒント**: - 必須レビューが有効化されており、リポジトリへの_書き込み_、_管理_、_オーナー_のいずれかの権限を持つコラボレータがレビューを要求する変更をサブミットすると、そのプルリクエストは同じコラボレータがプルリクエスト中の変更を承認する他のレビューをサブミットするまではマージできません。 - リポジトリのオーナーと管理者は、プルリクエストが承認レビューを受けていなかったり、あるいは変更をリクエストしたレビュー担当者がOrganizationを離れていたりアクセスできなくなっている場合でも、プルリクエストをマージできます。 - 必須レビューと古いレビューの棄却がどちらも有効化されており、承認済みのプルリクエストのブランチにコードを変更するコミットがプッシュされた場合、その承認は却下されます。 そのプルリクエストは、再度レビューされ承認されるまではマージできません。 diff --git a/translations/ja-JP/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/ja-JP/data/reusables/repositories/two-dot-diff-comparison-example-urls.md index 1b882a3b38..1a25944892 100644 --- a/translations/ja-JP/data/reusables/repositories/two-dot-diff-comparison-example-urls.md +++ b/translations/ja-JP/data/reusables/repositories/two-dot-diff-comparison-example-urls.md @@ -1 +1 @@ -たとえば、以下のURLは短縮された7文字のSHAコードを使って`c3a414e`と`faf7c6f`のコミットを比較しています。 `https://github.com/github/linguist/compare/c3a414e..faf7c6f.` +For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`. diff --git a/translations/ja-JP/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/ja-JP/data/reusables/repositories/view-failed-job-results-superlinter.md index 434994a169..39cc5396f0 100644 --- a/translations/ja-JP/data/reusables/repositories/view-failed-job-results-superlinter.md +++ b/translations/ja-JP/data/reusables/repositories/view-failed-job-results-superlinter.md @@ -1,5 +1,9 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Any failed steps are automatically expanded to display the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png) +1. Any failed steps are automatically expanded to display the results. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %} +![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png) +{% endif %} {% else %} 1. Expand the **Run Super-Linter** step to view the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results.png) {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/repositories/view-specific-line-superlinter.md b/translations/ja-JP/data/reusables/repositories/view-specific-line-superlinter.md index 88413fba19..51721e7a7e 100644 --- a/translations/ja-JP/data/reusables/repositories/view-specific-line-superlinter.md +++ b/translations/ja-JP/data/reusables/repositories/view-specific-line-superlinter.md @@ -1,5 +1,10 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. あるいはログの中の特定の行へのリンクを取得するには、そのステップの行番号をクリックします。 You can then copy the link from the address bar of your web browser. ![リンクをコピーするボタン](/assets/images/help/repository/copy-link-button-updated.png) +1. あるいはログの中の特定の行へのリンクを取得するには、そのステップの行番号をクリックします。 You can then copy the link from the address bar of your web browser. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![リンクをコピーするボタン](/assets/images/help/repository/copy-link-button-updated-2.png) + {% else %} + ![リンクをコピーするボタン](/assets/images/help/repository/copy-link-button-updated.png) + {% endif %} {% else %} 1. あるいはログの中の特定の行へのリンクを取得するには、そのステップの行番号をクリックします。 You can then copy the link from the address bar of your web browser. ![リンクをコピーするボタン](/assets/images/help/repository/copy-link-button.png) {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/search/date_gt_lt.md b/translations/ja-JP/data/reusables/search/date_gt_lt.md index 4fcb54438c..213cd754e1 100644 --- a/translations/ja-JP/data/reusables/search/date_gt_lt.md +++ b/translations/ja-JP/data/reusables/search/date_gt_lt.md @@ -1 +1 @@ -日付では[大なり、小なりおよび範囲指定](/articles/understanding-the-search-syntax)を使用できます。 +When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/secret-scanning/api-beta.md b/translations/ja-JP/data/reusables/secret-scanning/api-beta.md new file mode 100644 index 0000000000..510473ea8d --- /dev/null +++ b/translations/ja-JP/data/reusables/secret-scanning/api-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The {% data variables.product.prodname_secret_scanning %} API is currently in beta and subject to change. + +{% endnote %} diff --git a/translations/ja-JP/data/reusables/sponsors/billing-switcher.md b/translations/ja-JP/data/reusables/sponsors/billing-switcher.md new file mode 100644 index 0000000000..4831c34a3b --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/billing-switcher.md @@ -0,0 +1 @@ +1. Optionally, to manage your sponsorship on behalf of an organization, in the upper-left corner, use the **Personal settings** drop-down menu, and click the organization. ![Drop-down menu to switch accounts for settings](/assets/images/help/sponsors/billing-account-switcher.png) diff --git a/translations/ja-JP/data/reusables/sponsors/change-tier.md b/translations/ja-JP/data/reusables/sponsors/change-tier.md index 7e6a270b71..07f7c9cafa 100644 --- a/translations/ja-JP/data/reusables/sponsors/change-tier.md +++ b/translations/ja-JP/data/reusables/sponsors/change-tier.md @@ -1 +1 @@ -1. "{% data variables.product.prodname_sponsors %}"の下で、スポンサードオープンソースコントリビューターの右のあなたがスポンサーした額の隣にある{% octicon "triangle-down" aria-label="The down triangle octicon" %}をクリックし、**Change tier（層の変更）**をクリックしてください。 ![層の変更ボタン](/assets/images/help/billing/edit-sponsor-billing.png) +1. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored account, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your tier amount, then click **Change tier**. ![層の変更ボタン](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/ja-JP/data/reusables/sponsors/choose-updates.md b/translations/ja-JP/data/reusables/sponsors/choose-updates.md new file mode 100644 index 0000000000..ade59cf05b --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/choose-updates.md @@ -0,0 +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) diff --git a/translations/ja-JP/data/reusables/sponsors/manage-sponsorship.md b/translations/ja-JP/data/reusables/sponsors/manage-sponsorship.md new file mode 100644 index 0000000000..125d4020ad --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/manage-sponsorship.md @@ -0,0 +1 @@ +1. To the right of your current tier, click **Manage**. ![スポンサーシップの管理ボタン](/assets/images/help/sponsors/manage-your-sponsorship-button.png) \ No newline at end of file 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 new file mode 100644 index 0000000000..0cd08d5382 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/manage-updates-for-orgs.md @@ -0,0 +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)." diff --git a/translations/ja-JP/data/reusables/sponsors/maximum-tier.md b/translations/ja-JP/data/reusables/sponsors/maximum-tier.md index c90f7a86fb..71f2918dff 100644 --- a/translations/ja-JP/data/reusables/sponsors/maximum-tier.md +++ b/translations/ja-JP/data/reusables/sponsors/maximum-tier.md @@ -1 +1 @@ -最高価格は月あたり6000米ドルです。 +最高価格は月あたり12,000米ドルです。 diff --git a/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsored-account.md new file mode 100644 index 0000000000..def70f43f1 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsored-account.md @@ -0,0 +1 @@ +1. On {% data variables.product.product_name %}, navigate to the sponsored account's profile. diff --git a/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsors-dashboard.md new file mode 100644 index 0000000000..7a4eaac3c6 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/navigate-to-sponsors-dashboard.md @@ -0,0 +1,2 @@ +1. 任意のページの右上隅で、プロフィール画像をクリックし、続いて [**{% data variables.product.prodname_sponsors %}**] をクリックします。 ![{% data variables.product.prodname_sponsors %}ボタン](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) +2. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**. ![開発者スポンサーダッシュボードボタン](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) diff --git a/translations/ja-JP/data/reusables/sponsors/no-fees.md b/translations/ja-JP/data/reusables/sponsors/no-fees.md index f31dc99fe8..ea983ae36d 100644 --- a/translations/ja-JP/data/reusables/sponsors/no-fees.md +++ b/translations/ja-JP/data/reusables/sponsors/no-fees.md @@ -1 +1 @@ -{% data variables.product.prodname_sponsors %}はユーザアカウントからスポンサーシップの費用を請求しないので、これらのスポンサーシップの100%がスポンサー付きの開発者あるいはOrganizationに渡ります。 +{% data variables.product.prodname_sponsors %}はユーザアカウントからスポンサーシップの費用を請求しないので、これらのスポンサーシップの100%がスポンサー付きの開発者あるいはOrganizationに渡ります。 The 10% fee for sponsorships from organizations is waived during the beta. diff --git a/translations/ja-JP/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/ja-JP/data/reusables/sponsors/org-sponsors-release-phase.md new file mode 100644 index 0000000000..75983073a4 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/org-sponsors-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Sponsoring on behalf of an organization is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md b/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md new file mode 100644 index 0000000000..f201de957c --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/pay-prorated-amount.md @@ -0,0 +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 diff --git a/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md b/translations/ja-JP/data/reusables/sponsors/prorated-sponsorship.md index b3c479b33c..56a047d867 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. diff --git a/translations/ja-JP/data/reusables/sponsors/sponsor-account.md b/translations/ja-JP/data/reusables/sponsors/sponsor-account.md new file mode 100644 index 0000000000..28ea6f4fa5 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/sponsor-account.md @@ -0,0 +1 @@ +1. Click **Sponsor _ACCOUNT_**. ![[Sponsor] ボタン](/assets/images/help/sponsors/sponsor-developer-button.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/sponsors/sponsorship-dashboard.md b/translations/ja-JP/data/reusables/sponsors/sponsorship-dashboard.md new file mode 100644 index 0000000000..14263e3677 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/sponsorship-dashboard.md @@ -0,0 +1,4 @@ +1. Navigate to your sponsorship dashboard for the account. + - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![スポンサーをするボタン](/assets/images/help/profile/sponsoring-button.png) + - If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![スポンサーをするボタン](/assets/images/help/sponsors/org-sponsoring-button.png) +1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md b/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md index 0497dbbb59..06efbfc160 100644 --- a/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md +++ b/translations/ja-JP/data/reusables/sponsors/sponsorship-details.md @@ -1 +1 @@ -{% data variables.product.product_name %}アカウントを持つ人は、スポンサード開発者プロフィールあるいはスポンサードOrganizationプロフィールを持つ人を、繰り返しの月次支払いを通じてスポンサーできます。 スポンサード開発者もしくはOrganizationが設定した月次の支払い額やメリットを持つ複数のスポンサーシップ層から選択することができます。 スポンサーシップは、既存の支払日、支払い方法、領収書を共有します。 +You can sponsor anyone with a sponsored developer profile or sponsored organization profile on behalf of your user account or an organization. You can choose from multiple sponsorship tiers, with monthly payment amounts and benefits that are set by the sponsored account. スポンサーシップは、既存の支払日、支払い方法、領収書を共有します。 diff --git a/translations/ja-JP/data/reusables/webhooks/app_always_desc.md b/translations/ja-JP/data/reusables/webhooks/app_always_desc.md new file mode 100644 index 0000000000..d52aaebe58 --- /dev/null +++ b/translations/ja-JP/data/reusables/webhooks/app_always_desc.md @@ -0,0 +1 @@ +`installation` | `object` | The {% data variables.product.prodname_github_app %} installation. diff --git a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md index cd08b87360..df16a97c7b 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md @@ -1,6 +1,6 @@ | キー | 種類 | 説明 | | --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
| +| `action` | `string` | 実行されたアクション。 次のいずれかになります。
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
| | `check_run` | `オブジェクト` | The [check_run](/rest/reference/checks#get-a-check-run). | | `check_run[status]` | `string` | The current status of the check run. Can be `queued`, `in_progress`, or `completed`. | | `check_run[conclusion]` | `string` | The result of the completed check run. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`. | diff --git a/translations/ja-JP/data/reusables/webhooks/installation_properties.md b/translations/ja-JP/data/reusables/webhooks/installation_properties.md index eecb054088..b8d658fcfc 100644 --- a/translations/ja-JP/data/reusables/webhooks/installation_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ | キー | 種類 | 説明 | | -------------- | -------- | ---------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be one of:
  • `created` - Someone installs a {% data variables.product.prodname_github_app %}.
  • `deleted` - Someone uninstalls a {% data variables.product.prodname_github_app %}
    • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
  • `suspend` - Someone suspends a {% data variables.product.prodname_github_app %} installation.
  • `unsuspend` - Someone unsuspends a {% data variables.product.prodname_github_app %} installation.
    • {% endif %}
  • `new_permissions_accepted` - Someone accepts new permissions for a {% data variables.product.prodname_github_app %} installation. When a {% data variables.product.prodname_github_app %} owner requests new permissions, the person who installed the {% data variables.product.prodname_github_app %} must accept the new permissions request.
| +| `action` | `string` | 実行されたアクション. 次のいずれかになります。
  • `created` - Someone installs a {% data variables.product.prodname_github_app %}.
  • `deleted` - Someone uninstalls a {% data variables.product.prodname_github_app %}
    • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
  • `suspend` - Someone suspends a {% data variables.product.prodname_github_app %} installation.
  • `unsuspend` - Someone unsuspends a {% data variables.product.prodname_github_app %} installation.
    • {% endif %}
  • `new_permissions_accepted` - Someone accepts new permissions for a {% data variables.product.prodname_github_app %} installation. When a {% data variables.product.prodname_github_app %} owner requests new permissions, the person who installed the {% data variables.product.prodname_github_app %} must accept the new permissions request.
| | `repositories` | `array` | An array of repository objects that the installation can access. | diff --git a/translations/ja-JP/data/reusables/webhooks/member_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/member_webhook_properties.md index bf2681e0c1..1f8317a1c0 100644 --- a/translations/ja-JP/data/reusables/webhooks/member_webhook_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/member_webhook_properties.md @@ -1,3 +1,3 @@ -| キー | 種類 | 説明 | -| -------- | -------- | --------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be one of:
  • `added` - A user accepts an invitation to a repository.
  • `removed` - A user is removed as a collaborator in a repository.
  • `edited` - A user's collaborator permissions have changed.
| +| キー | 種類 | 説明 | +| -------- | -------- | ------------------------------------------------- | +| `action` | `string` | 実行されたアクション. 次のいずれかになります。
  • `added` - A user accepts an invitation to a repository.
  • `removed` - A user is removed as a collaborator in a repository.
  • `edited` - A user's collaborator permissions have changed.
| diff --git a/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md b/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md index f75660fcdb..ec89e9f647 100644 --- a/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md +++ b/translations/ja-JP/data/reusables/webhooks/org_block_short_desc.md @@ -1 +1 @@ -Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. +Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} 詳しい情報については、「[Organization ユーザをブロックする](/rest/reference/orgs#blocking)」REST API を参照してください。 diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md index a056cfc763..cb0f3b9e46 100644 --- a/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/pull_request_review_properties.md @@ -1,6 +1,6 @@ | キー | 種類 | 説明 | | --------------------- | -------- | ----------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be one of:
  • `submitted` - A pull request review is submitted into a non-pending state.
  • `edited` - The body of a review has been edited.
  • `dismissed` - A review has been dismissed.
| +| `action` | `string` | 実行されたアクション. 次のいずれかになります。
  • `submitted` - A pull request review is submitted into a non-pending state.
  • `edited` - The body of a review has been edited.
  • `dismissed` - A review has been dismissed.
| | `pull_request` | `オブジェクト` | The [pull request](/rest/reference/pulls) the review pertains to. | | `レビュー` | `オブジェクト` | The review that was affected. | | `changes[body][from]` | `string` | The previous version of the body if the action was `edited`. | diff --git a/translations/ja-JP/data/reusables/webhooks/release_webhook_properties.md b/translations/ja-JP/data/reusables/webhooks/release_webhook_properties.md index ffd7a5802a..45743ee342 100644 --- a/translations/ja-JP/data/reusables/webhooks/release_webhook_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/release_webhook_properties.md @@ -1,3 +1,3 @@ -| キー | 種類 | 説明 | -| -------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション. Can be one of:
  • `published`: a release, pre-release, or draft of a release is published
  • `unpublished`: a release or pre-release is deleted
  • `created`: a draft is saved, or a release or pre-release is published without previously being saved as a draft
  • `edited`: a release, pre-release, or draft release is edited
  • `deleted`: a release, pre-release, or draft release is deleted
  • `prereleased`: a pre-release is created
  • `released`: a release or draft of a release is published, or a pre-release is changed to a release
    • | +| キー | 種類 | 説明 | +| -------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション. 次のいずれかになります。
    • `published`: a release, pre-release, or draft of a release is published
    • `unpublished`: a release or pre-release is deleted
    • `created`: a draft is saved, or a release or pre-release is published without previously being saved as a draft
    • `edited`: a release, pre-release, or draft release is edited
    • `deleted`: a release, pre-release, or draft release is deleted
    • `prereleased`: a pre-release is created
    • `released`: a release or draft of a release is published, or a pre-release is changed to a release
      • | diff --git a/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_properties.md new file mode 100644 index 0000000000..4afbdd9682 --- /dev/null +++ b/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -0,0 +1,4 @@ +| キー | 種類 | 説明 | +| -------- | -------- | -------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション. This can be either `created`, `resolved`, or `reopened`. | +| `アラート` | `オブジェクト` | The secret scanning alert involved in the event. | diff --git a/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md new file mode 100644 index 0000000000..5da7e75271 --- /dev/null +++ b/translations/ja-JP/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -0,0 +1 @@ +Activity related to secret scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see “[About secret scanning](/github/administering-a-repository/about-secret-scanning).” diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml index 43750c86fe..f0aa25b75b 100644 --- a/translations/ja-JP/data/ui.yml +++ b/translations/ja-JP/data/ui.yml @@ -7,7 +7,7 @@ header: release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。 localization_in_progress: こんにちは！このページは開発中か、まだ翻訳中です。最新の正しい情報を得るには、英語のドキュメンテーションにアクセスしてください。 - early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' + early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' search: need_help: お困りですか？ placeholder: トピックや製品などの検索 @@ -56,6 +56,14 @@ contribution_cta: button: Make a contribution or: OR, to_guidelines: learn how to contribute. +enterprise_releases_list: + title: Enterprise Server Releases + currently_supported: Currently supported + currently_supported_message: See GitHub Enterprise for information about the latest release. + deprecated: Deprecated + deprecated_message: 'These docs remain available but are no longer maintained:' + deprecated_developer: Deprecated on developer.github.com + deprecated_developer_message: 'These docs remain available on the legacy developer site but are no longer maintained:' products: graphql: reference: @@ -123,3 +131,4 @@ footer: product_landing: quick_start: クイックスタート reference_guides: Reference guides + overview: 概要 diff --git a/translations/ja-JP/data/variables/action_code_examples.yml b/translations/ja-JP/data/variables/action_code_examples.yml index fcbcb9c899..b816b4df25 100644 --- a/translations/ja-JP/data/variables/action_code_examples.yml +++ b/translations/ja-JP/data/variables/action_code_examples.yml @@ -1,12 +1,4 @@ --- -- - title: Starter workflows - description: Workflow files for helping people get started with GitHub Actions - languages: TypeScript - href: actions/starter-workflows - tags: - - official - - ワークフロー - title: Example services description: Example workflows using service containers @@ -334,3 +326,10 @@ - monorepo - copybara - ワークフロー +- + title: Deploy static files to GitHub Pages + description: GitHub Action to publish website to GitHub Pages automatically + languages: 'TypeScript, JavaScript' + href: peaceiris/actions-gh-pages + tags: + - publishing diff --git a/translations/ja-JP/data/variables/command_line.yml b/translations/ja-JP/data/variables/command_line.yml index 805c67903e..5d1f568716 100644 --- a/translations/ja-JP/data/variables/command_line.yml +++ b/translations/ja-JP/data/variables/command_line.yml @@ -1,5 +1,5 @@ --- -#Use this variable wherever backticks are necessary: https://github.com/github/docs-internal/pull/1176#discussion-diff-19853931 +#Use this variable wherever backticks are necessary backticks: >- {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} #Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!) diff --git a/translations/ja-JP/data/variables/discussions_community_examples.yml b/translations/ja-JP/data/variables/discussions_community_examples.yml new file mode 100644 index 0000000000..8b3594f2ec --- /dev/null +++ b/translations/ja-JP/data/variables/discussions_community_examples.yml @@ -0,0 +1,38 @@ +--- +- + #Images and descriptions are pulled directly from the repo + repo: vercel/next.js + description: The React Framework +- + repo: gatsbyjs/gatsby + description: Build blazing fast, modern apps and websites with React +- + repo: nodejs/node + description: Node.js JavaScript runtime ✨🐢🚀✨ +- + repo: tailwindlabs/tailwindcss + description: A utility-first CSS framework for rapid UI development. +- + repo: laravel/framework + description: Laravel is a web application framework with expressive, elegant syntax. +- + repo: prisma/prisma + description: Modern database access (ORM alternative) for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite +- + repo: dotnet/csharplang + description: 'The official repo for the design of the C# programming language' +- + repo: home-assistant/frontend + description: '🍭 Frontend for Home Assistant' +- + repo: jspsych/jsPsych + description: A JavaScript library for creating and running behavioral experiments in a web browser +- + repo: adonisjs/core + description: '🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence' +- + repo: ImageMagick/ImageMagick + description: '🧙‍♂️ ImageMagick 7' +- + repo: react-hook-form/react-hook-form + description: '📋 React Hooks for forms validation (Web + React Native)' diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index 726cad186c..cddfec0f16 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -37,7 +37,10 @@ prodname_unified_search: 'Unified Search' #GitHub Education prodname_education: 'GitHub Education' prodname_education_community: 'Education Community' +prodname_education_community_with_url: 'the [GitHub Education Community](https://education.github.community)' prodname_classroom: 'GitHub Classroom' +prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)' +prodname_campus_program: 'GitHub Campus Program' prodname_student_pack: 'GitHub 学生開発者パック' #GitHub CLI prodname_cli: 'GitHub CLI' @@ -69,6 +72,8 @@ ae_azure_ad_app_link: 'the [GitHub AE application](https://azuremarketplace.micr prodname_actions: 'GitHub Actions' #GitHub Debug prodname_debug: 'GitHub デバッグ' +#GitHub Discussions +prodname_discussions: 'GitHub Discussions' #GitHub Packages prodname_registry: 'GitHub Packages' prodname_github_container_registry: 'GitHub Container Registry' 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 fb3cd025b4..9640844ccb 100644 --- a/translations/ko-KR/content/actions/creating-actions/about-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/about-actions.md @@ -33,8 +33,8 @@ You can build Docker container and JavaScript actions. Actions require a metadat | 유형 | Operating system | | ------------------- | --------------------- | | Docker container | Linux | -| JavaScript | Linux, MacOS, Windows | -| Composite run steps | Linux, MacOS, Windows | +| JavaScript | Linux, macOS, Windows | +| Composite run steps | Linux, macOS, Windows | #### Docker container actions 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 f9d1f55a67..9b1416053e 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 @@ -226,6 +226,10 @@ jobs: ``` {% endraw %} -From your repository, click the **Actions** tab, and select the latest workflow run. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +From your repository, click the **Actions** tab, and select the latest workflow run. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png) +{% else %} ![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run.png) +{% endif %} 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 8bcad07573..76711c4bba 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 @@ -176,7 +176,7 @@ git tag -a -m "My first action release" v1 git push --follow-tags ``` -As an alternative to checking in your `node_modules` directory you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. +Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. 1. Install `vercel/ncc` by running this command in your terminal. `npm i -g @vercel/ncc` @@ -256,9 +256,11 @@ jobs: ``` {% endraw %} -From your repository, click the **Actions** tab, and select the latest workflow run. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +From your repository, click the **Actions** tab, and select the latest workflow run. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} ![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png) {% else %} ![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run.png) 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 fb6d34e119..3a5f57be33 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 @@ -22,19 +22,19 @@ Docker and JavaScript actions require a metadata file. The metadata filename mus Action metadata files use YAML syntax. If you're new to YAML, you can read "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." -### **`name`** +### `name` **Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job. -### **`저자`** +### `저자` **Optional** The name of the action's author. -### **`설명`** +### `설명` **Required** A short description of the action. -### **`inputs`** +### `inputs` **Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids. @@ -57,23 +57,23 @@ When you specify an input to an action in a workflow file or use a default input 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.`** +#### `inputs.` **Required** A `string` identifier to associate with the input. The value of `` is a map of the input's metadata. The `` must be a unique identifier within the `inputs` object. The `` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`. -#### **`inputs..description`** +#### `inputs..description` **Required** A `string` description of the input parameter. -#### **`inputs..required`** +#### `inputs..required` **Required** A `boolean` to indicate whether the action requires the input parameter. Set to `true` when the parameter is required. -#### **`inputs..default`** +#### `inputs..default` **Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file. -### **`outputs`** +### `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. @@ -87,15 +87,15 @@ outputs: description: 'The sum of the inputs' ``` -#### **`outputs.`** +#### `outputs.` **Required** A `string` identifier to associate with the output. The value of `` is a map of the output's metadata. The `` must be a unique identifier within the `outputs` object. The `` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`. -#### **`outputs..description`** +#### `outputs..description` **Required** A `string` description of the output parameter. -### **`outputs`** for composite run steps actions +### `outputs` for composite run steps actions **Optional** `outputs` use the same parameters as `outputs.` and `outputs..description` (see "[`outputs` for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), but also includes the `value` token. @@ -116,12 +116,12 @@ runs: ``` {% endraw %} -#### **`outputs.`** +#### `outputs..value` **Required** The value that the output parameter will be mapped to. You can set this to a `string` or an expression with context. For example, you can use the `steps` context to set the `value` of an output to the output value of a step. For more information on how to use context and expression syntax, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -### **`runs`** for JavaScript actions +### `runs` for JavaScript actions **Required** Configures the path to the action's code and the application used to execute the code. @@ -133,15 +133,15 @@ runs: main: 'main.js' ``` -#### **`runs.using`** +#### `runs.using` **Required** The application used to execute the code specified in [`main`](#runsmain). -#### **`runs.main`** +#### `runs.main` **Required** The file that contains your action code. The application specified in [`using`](#runsusing) executes this file. -#### **`pre`** +#### `pre` **Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The application specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if). @@ -155,7 +155,7 @@ runs: post: 'cleanup.js' ``` -#### **`pre-if`** +#### `pre-if` **Optional** Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`. Note that the `step` context is unavailable, as no steps have run yet. @@ -166,7 +166,7 @@ In this example, `cleanup.js` only runs on Linux-based runners: pre-if: 'runner.os == linux' ``` -#### **`게시`** +#### `게시` **Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The application specified with the [`using`](#runsusing) syntax will execute this file. @@ -181,7 +181,7 @@ runs: The `post:` action always runs by default but you can override this using `post-if`. -#### **`post-if`** +#### `post-if` **Optional** Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`. @@ -192,19 +192,19 @@ For example, this `cleanup.js` will only run on Linux-based runners: post-if: 'runner.os == linux' ``` -### **`runs`** for composite run steps actions +### `runs` for composite run steps actions **Required** Configures the path to the composite action, and the application used to execute the code. -#### **`runs.using`** +#### `runs.using` **Required** To use a composite run steps action, set this to `"composite"`. -#### **`runs.steps`** +#### `runs.steps` **Required** The run steps that you plan to run in this action. -##### **`runs.steps.run`** +##### `runs.steps.run` **Required** The command you want to run. This can be inline or a script in your action repository: ```yaml @@ -227,27 +227,27 @@ runs: For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". -##### **`runs.steps.shell`** +##### `runs.steps.shell` **Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell). -##### **`runs.steps.name`** +##### `runs.steps.name` **Optional** The name of the composite run step. -##### **`runs.steps.id`** +##### `runs.steps.id` **Optional** 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)". -##### **`runs.steps.env`** +##### `runs.steps.env` **Optional** Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} in a composite run step. -##### **`runs.steps.working-directory`** +##### `runs.steps.working-directory` **Optional** Specifies the working directory where the command is run. -### **`runs`** for Docker actions +### `runs` for Docker actions **Required** Configures the image used for the Docker action. @@ -267,11 +267,11 @@ runs: image: 'docker://debian:stretch-slim' ``` -#### **`runs.using`** +#### `runs.using` **Required** You must set this value to `'docker'`. -#### **`pre-entrypoint`** +#### `pre-entrypoint` **Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if). @@ -289,21 +289,21 @@ runs: entrypoint: 'main.sh' ``` -#### **`runs.image`** +#### `runs.image` **Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. To reference a `Dockerfile` local to your repository, use a path relative to your action metadata file. The `docker` application will execute this file. -#### **`runs.env`** +#### `runs.env` **Optional** Specifies a key/value map of environment variables to set in the container environment. -#### **`runs.entrypoint`** +#### `runs.entrypoint` **Optional** Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Use `entrypoint` when the `Dockerfile` does not specify an `ENTRYPOINT` or you want to override the `ENTRYPOINT` instruction. If you omit `entrypoint`, the commands you specify in the Docker `ENTRYPOINT` instruction will execute. The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction. For more information about how the `entrypoint` executes, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)." -#### **`post-entrypoint`** +#### `post-entrypoint` **Optional** Allows you to run a cleanup script once the `runs.entrypoint` action has completed. {% data variables.product.prodname_actions %} uses `docker run` to launch this action. Because {% data variables.product.prodname_actions %} runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using [`post-if`](#post-if). @@ -317,7 +317,7 @@ runs: post-entrypoint: 'cleanup.sh' ``` -#### **`runs.args`** +#### `runs.args` **Optional** An array of strings that define the inputs for a Docker container. Inputs can include hardcoded strings. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. @@ -343,7 +343,7 @@ runs: ``` {% endraw %} -### **`branding`** +### `branding` You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. Badges are shown next to your action name in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). @@ -355,11 +355,11 @@ branding: color: 'green' ``` -#### **`branding.color`** +#### `branding.color` The background color of the badge. Can be one of: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, or `gray-dark`. -#### **`branding.icon`** +#### `branding.icon` The name of the [Feather](https://feathericons.com/) icon to use. 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 4f6a16ade5..81c4419e79 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 @@ -25,7 +25,11 @@ Creating a package at the end of a continuous integration workflow can help duri Now, when reviewing a pull request, you'll be able to look at the workflow run and download the artifact that was produced. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png) +{% else %} ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png) +{% endif %} This will let you run the code in the pull request on your machine, which can help with debugging or testing the pull request. 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 81e5ae5945..f56207004e 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 @@ -53,7 +53,7 @@ jobs: with: java-version: 1.8 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -85,7 +85,7 @@ steps: with: java-version: 1.8 - name: Run the Maven verify phase - run: mvn -B verify --file pom-ci.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -108,7 +108,7 @@ steps: key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} restore-keys: ${{ runner.os }}-m2 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -125,7 +125,7 @@ Maven will usually create output files like JARs, EARs, or WARs in the `target` steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 - - run: mvn -B package --file pom.xml + - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 with: 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 14717c687d..4b2ff9372f 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 @@ -60,7 +60,11 @@ jobs: * `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory. * `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. 예시: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png) + {% else %} ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png) + {% endif %} * `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following: ``` 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 e482de7f30..5e415b926f 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 @@ -84,7 +84,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -143,7 +143,7 @@ jobs: with: java-version: 1.8 - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` @@ -182,7 +182,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish to the Maven Central Repository - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -191,7 +191,7 @@ jobs: with: java-version: 1.8 - name: Publish to GitHub Packages - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` 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 89cb5d334d..3a402d35a1 100644 --- a/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ko-KR/content/actions/guides/publishing-nodejs-packages.md @@ -8,8 +8,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 75f673d979..deaf7f498a 100644 --- a/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ko-KR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,8 +11,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ko-KR/content/actions/guides/storing-workflow-data-as-artifacts.md index 633050ef6c..3d929426f3 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 @@ -108,8 +108,6 @@ jobs: path: output/test/code-coverage.html ``` -![Image of workflow upload artifact workflow run](/assets/images/help/repository/upload-build-test-artifact.png) - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Configuring a custom artifact retention period @@ -238,7 +236,12 @@ jobs: echo The result is $value ``` +The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% else %} ![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +{% endif %} {% if currentVersion == "free-pro-team@latest" %} 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 022c544673..28591c40bf 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 @@ -87,7 +87,7 @@ The following operating systems are supported for the self-hosted runner applica - Windows Server 2016 64-bit - Windows Server 2019 64-bit -#### MacOS +#### macOS - macOS 10.13 (High Sierra) or later diff --git a/translations/ko-KR/content/actions/index.md b/translations/ko-KR/content/actions/index.md index a52b17016f..4365c6f495 100644 --- a/translations/ko-KR/content/actions/index.md +++ b/translations/ko-KR/content/actions/index.md @@ -41,6 +41,7 @@ changelog: title: Self-Hosted Runner Group Access Changes date: '2020-10-16' href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ +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/ @@ -69,18 +70,18 @@ versions:

      Code examples

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

      Sorry, there is no result for

      +

      Sorry, there is no result for

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

      Learn how to add a code example {% octicon "arrow-right" %}
      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 6131f65296..2740523926 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 @@ -204,13 +204,18 @@ In this diagram, you can see the workflow file you just created and how the {% d ### Viewing the job's activity -Once your job has started running, you can view each step's activity on {% data variables.product.prodname_dotcom %}. +Once your job has started running, you can {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}. {% data reusables.repositories.navigate-to-repo %} 1. Under your repository name, click **Actions**. ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png) 1. In the left sidebar, click the workflow you want to see. ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png) 1. Under "Workflow runs", click the name of the run you want to see. ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Select job](/assets/images/help/images/overview-actions-result-navigate.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. View the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. Click on the job name to see the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated.png) {% else %} 1. Click on the job name to see the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result.png) 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 96ca6b2b21..b22d715c60 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 @@ -54,6 +54,8 @@ This means that a compromise of a single action within a workflow can be very si **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail. {% endwarning %} + + * **Audit the source code of the action** Ensure that the action is handling the content of your repository and secrets as expected. For example, check that secrets are not sent to unintended hosts, or are not inadvertently logged. @@ -92,10 +94,14 @@ This list describes the recommended approaches for accessing repository data wit As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be cautious when using self-hosted runners on private repositories, as anyone who can fork the repository and open a PR (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the more privileged `GITHUB_TOKEN` which grants write-access permissions on the repository. +When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)." + You should also consider the environment of the self-hosted runner machines: - What sensitive information resides on the machine configured as a self-hosted runner? For example, private SSH keys, API access tokens, among others. - Does the machine have network access to sensitive services? For example, Azure or AWS metadata services. The amount of sensitive information in this environment should be kept to a minimum, and you should always be mindful that any user capable of invoking workflows has access to this environment. +Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. + ### Auditing {% data variables.product.prodname_actions %} events 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. @@ -130,5 +136,3 @@ The following tables describe the {% data variables.product.prodname_actions %} | `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. | - - diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/canceling-a-workflow.md index 031f4cb53f..80174965ed 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -17,8 +17,13 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} -{% data reusables.repositories.view-run %} -1. In the upper-right corner of the workflow, click **Cancel workflow**. ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite.png) +1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel. ![Name of workflow run](/assets/images/help/repository/in-progress-run.png) +1. In the upper-right corner of the workflow, click **Cancel workflow**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite-updated.png) +{% else %} + ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite.png) +{% endif %} ### Steps {% data variables.product.prodname_dotcom %} takes to cancel a workflow run diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 591f969666..64daea7ddb 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -19,4 +19,9 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under **Artifacts**, click the artifact you want to download. ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png) +1. Under **Artifacts**, click the artifact you want to download. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png) + {% else %} + ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png) + {% endif %} diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/index.md b/translations/ko-KR/content/actions/managing-workflow-runs/index.md index 5096b761c7..8905d8b087 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/index.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/index.md @@ -18,6 +18,7 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% link_in_list /using-the-visualization-graph %}{% endif %} {% link_in_list /viewing-workflow-run-history %} {% link_in_list /using-workflow-run-logs %} {% link_in_list /manually-running-a-workflow %} diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md index 5c46ed4da5..323ebab2d3 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -16,4 +16,4 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**. ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png) +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index a7eb83e1c6..ae9e20f6f5 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -26,7 +26,13 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under **Artifacts**, click {% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove. ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact.png) +1. Under **Artifacts**, click +{% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact-updated.png) + {% else %} + ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact.png) + {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Setting the retention period for an artifact diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/ko-KR/content/actions/managing-workflow-runs/using-the-visualization-graph.md new file mode 100644 index 0000000000..f1ef803e42 --- /dev/null +++ b/translations/ko-KR/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -0,0 +1,21 @@ +--- +title: Using the visualization graph +intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.visualization-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} + +1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies. ![Workflow graph](/assets/images/help/images/workflow-graph.png) + +2. Click on a job to view the job log. ![Workflow graph](/assets/images/help/images/workflow-graph-job.png) diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md index a6150cf4bf..bc67775e57 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -44,7 +44,12 @@ You can search the build logs for a particular step. When you search logs, only {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query. ![Search box to search logs](/assets/images/help/repository/search-log-box-updated.png) +1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Search box to search logs](/assets/images/help/repository/search-log-box-updated-2.png) +{% else %} + ![Search box to search logs](/assets/images/help/repository/search-log-box-updated.png) +{% endif %} {% else %} 1. To expand each step you want to include in your search, click the step. ![Step name](/assets/images/help/repository/failed-check-step.png) 1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query. ![Search box to search logs](/assets/images/help/repository/search-log-box.png) @@ -61,8 +66,12 @@ You can download the log files from your workflow run. You can also download a w {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 1. In the upper right corner, click -{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Download log archive**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated-2.png) + {% else %} ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated.png) + {% endif %} {% else %} 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Download log archive**. @@ -78,8 +87,20 @@ You can delete the log files from your workflow run. {% data reusables.repositor {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) -2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. +1. In the upper right corner, click +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) + {% else %} + ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) + {% endif %} +2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png) + {% else %} + ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) + {% endif %} +After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. {% else %} 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png) 2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) After the logs have been deleted, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/ko-KR/content/actions/managing-workflow-runs/viewing-job-execution-time.md index 709a7343a9..402220c3c0 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/viewing-job-execution-time.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -15,7 +15,7 @@ Billable job execution minutes are only shown for jobs run on private repositori {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under the job summary, you can view the job's execution time. To view the billable job execution time, click **Run and billable time details**. ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png) +1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, click the time under **Billable time**. ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png) {% note %} diff --git a/translations/ko-KR/content/actions/quickstart.md b/translations/ko-KR/content/actions/quickstart.md index 45613e5427..586344c270 100644 --- a/translations/ko-KR/content/actions/quickstart.md +++ b/translations/ko-KR/content/actions/quickstart.md @@ -59,7 +59,11 @@ Committing the workflow file in your repository triggers the `push` event and ru {% 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 %} ### More starter workflows @@ -101,7 +105,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o # When the event is triggered, GitHub Actions will run the jobs indicated jobs: say_hello: - # Uses a ubuntu-lates runner to complete the requested steps + # Uses a ubuntu-latest runner to complete the requested steps runs-on: ubuntu-latest steps: - run: | diff --git a/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 1f6b29d987..3740b49057 100644 --- a/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,7 +75,7 @@ In order to use property dereference syntax, the property name must: - start with `a-Z` or `_`. - be followed by `a-Z` `0-9` `-` or `_`. -#### **`github` context** +#### `github` context The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." @@ -103,7 +103,7 @@ The `github` context contains information about the workflow run and the event t | `github.workflow` | `문자열` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. | | `github.workspace` | `문자열` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | -#### **`env` context** +#### `env` context The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)." @@ -117,7 +117,7 @@ You can only use the `env` context in the value of the `with` and `name` keys, o | `env.` | `문자열` | The value of a specific environment variable. | -#### **`job` context** +#### `job` context The `job` context contains information about the currently running job. @@ -133,7 +133,7 @@ The `job` context contains information about the currently running job. | `job.services..ports` | `개체` | The exposed ports of the service container. | | `job.status` | `문자열` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. | -#### **`steps` context** +#### `steps` context The `steps` context contains information about the steps in the current job that have already run. @@ -145,7 +145,7 @@ The `steps` context contains information about the steps in the current job that | `steps..outcome` | `문자열` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. | | `steps..outputs.` | `문자열` | The value of a specific output. | -#### **`runner` context** +#### `runner` context The `runner` context contains information about the runner that is executing the current job. @@ -155,7 +155,7 @@ The `runner` context contains information about the runner that is executing the | `runner.temp` | `문자열` | The path of the temporary directory for the runner. This directory is guaranteed to be empty at the start of each job, even on self-hosted runners. | | `runner.tool_cache` | `문자열` | The path of the directory containing some of the preinstalled tools for {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". | -#### **`needs` context** +#### `needs` context The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)." diff --git a/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md b/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md index 353d02f366..5fda97dde6 100644 --- a/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/ko-KR/content/actions/reference/events-that-trigger-workflows.md @@ -137,9 +137,9 @@ jobs: #### `repository_dispatch` -| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------- | -------------- | -------------------------------------- | ----------------------------- | -| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Last commit on the `GITHUB_REF` branch | Branch that received dispatch | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------------------- | -------------- | ----------------------------- | -------------- | +| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Last commit on default branch | Default branch | {% data reusables.github-actions.branch-requirement %} @@ -699,6 +699,8 @@ on: {% data reusables.webhooks.workflow_run_desc %} +{% data reusables.github-actions.branch-requirement %} + | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------- | -------------- | ----------------------------- | -------------- | | [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - n/a | Last commit on default branch | Default branch | diff --git a/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md index f220d10e25..ee818e09cf 100644 --- a/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ko-KR/content/actions/reference/specifications-for-github-hosted-runners.md @@ -63,8 +63,8 @@ The software tools included in {% data variables.product.prodname_dotcom %}-host * [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md) * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md) -* [MacOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) -* [MacOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) +* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) {% data reusables.github-actions.ubuntu-runner-preview %} {% data reusables.github-actions.macos-runner-preview %} diff --git a/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md index 4f7c77e3ed..7a269bf6c4 100644 --- a/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/reference/workflow-syntax-for-github-actions.md @@ -21,17 +21,17 @@ Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file ex You must store workflow files in the `.github/workflows` directory of your repository. -### **`name`** +### `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. -### **`on`** +### `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)." {% data reusables.github-actions.actions-on-examples %} -### **`on..types`** +### `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. @@ -45,7 +45,7 @@ on: types: [published, created, edited] ``` -### **`on..`** +### `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. @@ -112,7 +112,7 @@ on: - '!releases/**-alpha' ``` -### **`on..paths`** +### `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. @@ -179,13 +179,13 @@ The filter determines if a workflow should run by evaluating the changed files a For more information, see "[About comparing branches in pull requests](/articles/about-comparing-branches-in-pull-requests)." -### **`on.schedule`** +### `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)." -### **`env`** +### `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). @@ -198,13 +198,13 @@ env: SERVER: production ``` -### **`defaults`** +### `defaults` 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). {% data reusables.github-actions.defaults-override %} -### **`defaults.run`** +### `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. @@ -219,7 +219,7 @@ defaults: working-directory: scripts ``` -### **`jobs`** +### `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. @@ -229,7 +229,7 @@ You can run an unlimited number of jobs as long as you are within the workflow u If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." -### **`jobs.`** +### `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 `_`. @@ -243,15 +243,15 @@ jobs: name: My second job ``` -### **`jobs..name`** +### `jobs..name` The name of the job displayed on {% data variables.product.prodname_dotcom %}. -### **`jobs..needs`** +### `jobs..needs` -Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional statement that causes the job to continue. +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. -#### 예시 +#### Example requiring dependent jobs to be successful ```yaml jobs: @@ -270,7 +270,21 @@ The jobs in this example run sequentially: 2. `job2` 3. `job3` -### **`jobs..runs-on`** +#### Example not requiring dependent jobs to be successful + +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + if: always() + 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)." + +### `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. @@ -286,7 +300,7 @@ Available {% data variables.product.prodname_dotcom %}-hosted runner types are: {% data reusables.github-actions.ubuntu-runner-preview %} -##### **예시** +##### 예시 ```yaml runs-on: ubuntu-latest @@ -298,7 +312,7 @@ For more information, see "[Virtual environments for {% data variables.product.p {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -##### **예시** +##### 예시 ```yaml runs-on: [self-hosted, linux] @@ -306,7 +320,7 @@ 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)." -### **`jobs..outputs`** +### `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). @@ -314,7 +328,7 @@ Job outputs are strings, and job outputs containing expressions are evaluated on 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)." -#### **예시** +#### 예시 {% raw %} ```yaml @@ -338,13 +352,13 @@ jobs: ``` {% endraw %} -### **`jobs..env`** +### `jobs..env` A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs..steps.env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -#### **예시** +#### 예시 ```yaml jobs: @@ -353,13 +367,13 @@ jobs: FIRST_NAME: Mona ``` -### **`jobs..defaults`** +### `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). {% data reusables.github-actions.defaults-override %} -### **`jobs..defaults.run`** +### `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. @@ -379,13 +393,13 @@ jobs: working-directory: scripts ``` -### **`jobs..if`** +### `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. {% 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)." -### **`jobs..steps`** +### `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. @@ -415,17 +429,17 @@ jobs: ``` {% endraw %} -#### **`jobs..steps.id`** +### `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)." -#### **`jobs..steps.if`** +### `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. {% 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)." -##### Example using contexts +#### Example using contexts This step only runs when the event type is a `pull_request` and the event action is `unassigned`. @@ -436,7 +450,7 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -##### Example using status check functions +#### Example using status check functions 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)." @@ -449,11 +463,11 @@ steps: uses: actions/heroku@1.0.0 ``` -#### **`jobs..steps.name`** +### `jobs..steps.name` A name for your step to display on {% data variables.product.prodname_dotcom %}. -#### **`jobs..steps.uses`** +### `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/). @@ -466,7 +480,7 @@ Some actions require inputs that you must set using the [`with`](#jobsjob_idstep 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). -##### Example using versioned actions +#### Example using versioned actions ```yaml steps: @@ -480,7 +494,7 @@ steps: - uses: actions/setup-node@main ``` -##### Example using a public action +#### Example using a public action `{owner}/{repo}@{ref}` @@ -498,7 +512,7 @@ jobs: uses: actions/aws@v2.0.1 ``` -##### Example using a public action in a subdirectory +#### Example using a public action in a subdirectory `{owner}/{repo}/{path}@{ref}` @@ -512,7 +526,7 @@ jobs: uses: actions/aws/ec2@main ``` -##### Example using action in the same repository as the workflow +#### Example using action in the same repository as the workflow `./path/to/dir` @@ -528,7 +542,7 @@ jobs: uses: ./.github/actions/my-action ``` -##### Example using a Docker Hub action +#### Example using a Docker Hub action `docker://{image}:{tag}` @@ -542,7 +556,7 @@ jobs: uses: docker://alpine:3.8 ``` -##### Example using a Docker public registry action +#### Example using a Docker public registry action `docker://{host}/{image}:{tag}` @@ -556,7 +570,7 @@ jobs: uses: docker://gcr.io/cloud-builders/gradle ``` -#### **`jobs..steps.run`** +### `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. @@ -588,7 +602,7 @@ Using the `working-directory` keyword, you can specify the working directory of working-directory: ./temp ``` -##### Using a specific shell +#### Using a specific shell You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. @@ -601,7 +615,7 @@ You can override the default shell settings in the runner's operating system usi | 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}'"`. | -##### Example running a script using bash +#### Example running a script using bash ```yaml steps: @@ -610,7 +624,7 @@ steps: shell: bash ``` -##### Example running a script using Windows `cmd` +#### Example running a script using Windows `cmd` ```yaml steps: @@ -619,7 +633,7 @@ steps: shell: cmd ``` -##### Example running a script using PowerShell Core +#### Example running a script using PowerShell Core ```yaml steps: @@ -628,7 +642,7 @@ steps: shell: pwsh ``` -##### Example running a python script +#### Example running a python script ```yaml steps: @@ -639,11 +653,11 @@ steps: shell: python ``` -##### Custom shell +#### Custom shell You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`. -##### Exit codes and error action preference +#### Exit codes and error action preference 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. @@ -661,11 +675,11 @@ For built-in shell keywords, we provide the following defaults that are executed - 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. -#### **`jobs..steps.with`** +### `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. -##### 예시 +#### 예시 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. @@ -681,11 +695,11 @@ jobs: last_name: Octocat ``` -#### **`jobs..steps.with.args`** +### `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. -##### 예시 +#### 예시 {% raw %} ```yaml @@ -704,11 +718,11 @@ The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you 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. -#### **`jobs..steps.with.entrypoint`** +### `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. -##### 예시 +#### 예시 ```yaml steps: @@ -720,7 +734,7 @@ steps: The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. -#### **`jobs..steps.env`** +### `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). @@ -728,7 +742,7 @@ Sets environment variables for steps to use in the runner environment. You can a 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)." -##### 예시 +#### 예시 {% raw %} ```yaml @@ -741,23 +755,23 @@ steps: ``` {% endraw %} -#### **`jobs..steps.continue-on-error`** +### `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. -#### **`jobs..steps.timeout-minutes`** +### `jobs..steps.timeout-minutes` The maximum number of minutes to run the step before killing the process. -### **`jobs..timeout-minutes`** +### `jobs..timeout-minutes` The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360 -### **`jobs..strategy`** +### `jobs..strategy` A strategy creates a build matrix for your jobs. You can define different variations of an environment to run each job in. -#### **`jobs..strategy.matrix`** +### `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. @@ -767,7 +781,7 @@ Each option you define in the `matrix` has a key and value. The keys you define The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow. -##### Example running with more than one version of Node.js +#### Example running with more than one version of 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`. @@ -789,7 +803,7 @@ steps: 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. -##### Example running with more than one operating system +#### Example running with more than one operating system 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: @@ -814,7 +828,7 @@ steps: 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)." -##### Example including additional values into combinations +#### Example including additional values into combinations 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. @@ -834,7 +848,7 @@ strategy: ``` {% endraw %} -##### Example including new combinations +#### Example including new combinations 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. @@ -852,7 +866,7 @@ strategy: ``` {% endraw %} -##### Example excluding configurations from a matrix +#### Example excluding configurations from a matrix 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`). @@ -882,11 +896,11 @@ You can add custom environment variables for each test combination by using the {% data reusables.github-actions.matrix-variable-example %} -### **`jobs..strategy.fail-fast`** +### `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` -### **`jobs..strategy.max-parallel`** +### `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. @@ -895,7 +909,7 @@ strategy: max-parallel: 2 ``` -### **`jobs..continue-on-error`** +### `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. @@ -920,7 +934,7 @@ strategy: ``` {% endraw %} -### **`jobs..container`** +### `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. @@ -950,16 +964,17 @@ jobs: container: node:10.16-jessie ``` -#### **`jobs..container.image`** +### `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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..container.credentials`** + +### `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -##### 예시 +#### 예시 {% raw %} ```yaml @@ -972,15 +987,15 @@ container: {% endraw %} {% endif %} -#### **`jobs..container.env`** +### `jobs..container.env` Sets a `map` of environment variables in the container. -#### **`jobs..container.ports`** +### `jobs..container.ports` Sets an `array` of ports to expose on the container. -#### **`jobs..container.volumes`** +### `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. @@ -990,7 +1005,7 @@ To specify a volume, you specify the source and destination path: The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -##### 예시 +#### 예시 ```yaml volumes: @@ -999,11 +1014,11 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..container.options`** +### `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)." -### **`jobs..services`** +### `jobs..services` {% data reusables.github-actions.docker-container-os-support %} @@ -1033,16 +1048,17 @@ services: - 6379/tcp ``` -#### **`jobs..services..image`** +### `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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..services..credentials`** + +### `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -##### 예시 +#### 예시 {% raw %} ```yaml @@ -1061,15 +1077,15 @@ services: {% endraw %} {% endif %} -#### **`jobs..services..env`** +### `jobs..services..env` Sets a `map` of environment variables in the service container. -#### **`jobs..services..ports`** +### `jobs..services..ports` Sets an `array` of ports to expose on the service container. -#### **`jobs..services..volumes`** +### `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. @@ -1079,7 +1095,7 @@ To specify a volume, you specify the source and destination path: The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -##### 예시 +#### 예시 ```yaml volumes: @@ -1088,7 +1104,7 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..services..options`** +### `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)." diff --git a/translations/ko-KR/content/admin/configuration/index.md b/translations/ko-KR/content/admin/configuration/index.md index 736ec887b6..4efeb57618 100644 --- a/translations/ko-KR/content/admin/configuration/index.md +++ b/translations/ko-KR/content/admin/configuration/index.md @@ -31,9 +31,7 @@ versions: {% link_in_list /enabling-private-mode %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} - {% link_in_list /configuring-applications %} - {% link_in_list /troubleshooting-ssl-errors %} {% link_in_list /configuring-time-synchronization %} {% link_in_list /command-line-utilities %} @@ -54,11 +52,7 @@ versions: {% link_in_list /connecting-github-enterprise-server-to-github-enterprise-cloud %} {% link_in_list /enabling-unified-search-between-github-enterprise-server-and-githubcom %} {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %} - {% link_in_list /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server %} {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} - - {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} - diff --git a/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md index 4353629ea2..79944278a7 100644 --- a/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/ko-KR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -37,7 +37,7 @@ The time required to failover depends on how long it takes to manually promote t ``` - On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace *`UUID`* with a UUID you retrieved in the previous step. ```shell - $ ghe-repl-teardown -u UUNID + $ ghe-repl-teardown -u UUID ``` ### 더 읽을거리 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 f088e0c9e4..7419d7f562 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 @@ -24,7 +24,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ### 빌드전 요구 사양 -* Before using the 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](/github/setting-up-and-managing-organizations-and-teams/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)." ### Example: Using the `actions-sync` tool diff --git a/translations/ko-KR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ko-KR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 9e060a0a5b..9aae505b8a 100644 --- a/translations/ko-KR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ko-KR/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -1,6 +1,6 @@ --- title: Setting up the tool cache on self-hosted runners without internet access -intro: 'To use the the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' +intro: 'To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' redirect_from: - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access versions: diff --git a/translations/ko-KR/content/admin/index.md b/translations/ko-KR/content/admin/index.md index 14c3aca964..6928e31fc4 100644 --- a/translations/ko-KR/content/admin/index.md +++ b/translations/ko-KR/content/admin/index.md @@ -28,3 +28,5 @@ versions: {% link_with_intro /packages %} {% link_with_intro /enterprise-support %} + +{% link_with_intro /release-notes %} diff --git a/translations/ko-KR/content/admin/overview/about-enterprise-accounts.md b/translations/ko-KR/content/admin/overview/about-enterprise-accounts.md index 02c92ad31d..26731d2fac 100644 --- a/translations/ko-KR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/ko-KR/content/admin/overview/about-enterprise-accounts.md @@ -15,7 +15,7 @@ An enterprise account allows you to manage multiple organizations{% if enterpris - 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) +- 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 reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." diff --git a/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md b/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md index ec679b8d8c..8305fed871 100644 --- a/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/ko-KR/content/developers/apps/authenticating-with-github-apps.md @@ -28,7 +28,7 @@ To generate a private key: {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. In "Private keys," click **Generate a private key**. ![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png) +5. In "Private keys", click **Generate a private key**. ![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png) 6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key. {% note %} 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 45ee46145e..aa11e4c59a 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 @@ -73,7 +73,9 @@ You can select permissions in a query string using the permission name in the fo | `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. | | [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | | [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %} | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. | | [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. | | [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. | diff --git a/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md b/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md index eea880cf33..5e7984982f 100644 --- a/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/scopes-for-oauth-apps.md @@ -46,7 +46,8 @@ X-Accepted-OAuth-Scopes: user |  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | |  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | |  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | -|  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +|  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +|  `security_events` | Grants:
      read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).
      read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} |  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} | **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | |  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | diff --git a/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index a83272428a..f99a24dffb 100644 --- a/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/ko-KR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -422,7 +422,7 @@ Here are a few common problems and some suggested solutions. If you run into any **A:** You may not be running the Smee client, or you may not have the correct Smee domain in your GitHub App settings. First check to make sure the Smee client is running in a Terminal tab. If that's not the problem, visit your [app settings page](https://github.com/settings/apps) and check the fields shown in "[Step 2. Register a new GitHub App](#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u ` command in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." -* **Q:** I'm getting seeing an `Octokit::NotFound` 404 error in my debug output: +* **Q:** I'm getting an `Octokit::NotFound` 404 error in my debug output: ``` 2018-12-06 15:00:56 - Octokit::NotFound - POST https://api.github.com/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token: ``` diff --git a/translations/ko-KR/content/developers/github-marketplace/about-github-marketplace.md b/translations/ko-KR/content/developers/github-marketplace/about-github-marketplace.md index 0ea91b55cb..697d461954 100644 --- a/translations/ko-KR/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/ko-KR/content/developers/github-marketplace/about-github-marketplace.md @@ -1,6 +1,6 @@ --- title: About GitHub Marketplace -intro: 'Learn the basics to prepare your app for review before joining {% data variables.product.prodname_marketplace %}.' +intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.' redirect_from: - /apps/marketplace/getting-started/ - /marketplace/getting-started @@ -14,52 +14,41 @@ versions: {% data reusables.actions.actions-not-verified %} -To learn about publishing {% data variables.product.prodname_actions %} in the {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." +To learn about publishing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." ### 앱 -You can list verified and unverified apps in {% data variables.product.prodname_marketplace %}. Unverified apps do not go through the security, testing, and verification cycle {% data variables.product.prodname_dotcom %} requires for verified apps. +Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only listings that are verified by {% data variables.product.company_short %} can include paid plans. For more information, see "[About verified creators](/developers/github-marketplace/about-verified-creators)." -Verified apps have a green badge in {% data variables.product.prodname_marketplace %}. Unverified apps have a grey badge next to their listing and are only available as free apps. +If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)." -![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) - -If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s, see "[Building apps](/apps/)." - -{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. See "[Differences between GitHub and OAuth apps](/apps/differences-between-apps/)" for more details. To learn more about switching from OAuth to {% data variables.product.prodname_github_apps %}, see [Migrating OAuth Apps to {% data variables.product.prodname_github_app %}s](/apps/migrating-oauth-apps-to-github-apps/). +{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_app %}s to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. -#### Unverified Apps +### Publishing an app to {% data variables.product.prodname_marketplace %} -Unverified apps do not need to meet the "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)" or go through the "[Security review process](/marketplace/getting-started/security-review-process/)". +When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: -{% data reusables.marketplace.unverified-apps %} Having a published paid plan will prevent you from being able to submit an unverified app. You must remove paid plans or keep them in draft mode before publishing an unverified app. +1. Review your app carefully to ensure that it will behave as expected in other repositories and that it follows best practice guidelines. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)." -To list your unverified app in {% data variables.product.prodname_marketplace %}, you only need to create a "[Listing on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)" and submit it as an unverified listing. +1. Add webhook events to the app to track user billing requests. For more information about the {% data variables.product.prodname_marketplace %} API, webhook events, and billing requests, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.launch-with-free %} +1. Create a draft {% data variables.product.prodname_marketplace %} listing. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -#### Verified Apps +1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -If you've already built an app and you're interested in submitting a verified listing in {% data variables.product.prodname_marketplace %}, start here: +1. Check whether your app meets the requirements for listing on {% data variables.product.prodname_marketplace %} as a free or a paid app. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." -1. [Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)
      Learn about requirements, guidelines, and the app submission process. +1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -1. [Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)
      Before you can list your app on {% data variables.product.prodname_marketplace %}, you'll need to integrate billing flows using the {% data variables.product.prodname_marketplace %} API and webhook events. +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}, requesting verification if you want to sell the app. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." -1. [Listing on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)
      Create a draft {% data variables.product.prodname_marketplace %} listing, configure webhook settings, and set up pricing plans. +An onboarding expert will contact you with any questions or further steps. For example, if you have added a paid plan, you will need to complete the verification process and complete financial onboarding. As soon as your listing is approved the app is published to {% data variables.product.prodname_marketplace %}. -1. [Selling your app](/marketplace/selling-your-app/)
      Learn about pricing plans, billing cycles, and how to receive payment from {% data variables.product.prodname_dotcom %} for your app. +### Seeing how your app is performing -1. [{% data variables.product.prodname_marketplace %} Insights](/marketplace/github-marketplace-insights/)
      See how your app is performing in {% data variables.product.prodname_marketplace %}. You can use metrics collected by {% data variables.product.prodname_dotcom %} to guide your marketing campaign and be successful in {% data variables.product.prodname_marketplace %}. +You can access metrics and transactions for your listing. For more information, see: -1. [{% data variables.product.prodname_marketplace %} transactions](/marketplace/github-marketplace-transactions/)
      Download and view transaction data for your {% data variables.product.prodname_marketplace %} listing. - -### Reviewing your app - -We want to make sure that the apps offered on {% data variables.product.prodname_marketplace %} are safe, secure, and well tested. The {% data variables.product.prodname_marketplace %} onboarding specialists will review your app to ensure that it meets all requirements. Follow the guidelines in these articles before submitting your app: - - -* [Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) -* [Security review process](/marketplace/getting-started/security-review-process/) +- "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" +- "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" diff --git a/translations/ko-KR/content/developers/github-marketplace/about-verified-creators.md b/translations/ko-KR/content/developers/github-marketplace/about-verified-creators.md new file mode 100644 index 0000000000..915c221b27 --- /dev/null +++ b/translations/ko-KR/content/developers/github-marketplace/about-verified-creators.md @@ -0,0 +1,43 @@ +--- +title: About verified creators +intro: 'Each organization that wants to sell apps on {% data variables.product.prodname_marketplace %} must follow a verification process. Their identity is checked and their billing process reviewed.' +versions: + free-pro-team: '*' +--- + +### About verified creators + +A verified creator is an organization that {% data variables.product.company_short %} has checked. Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only organizations that are verified by {% data variables.product.company_short %} can sell apps. For more information about organizations, see "[About organizations](/github/setting-up-and-managing-organizations-and-teams/about-organizations)." + +The verification process aims to protect users. For example, it verifies the seller's identity, checks that their {% data variables.product.product_name %} organization is set up securely, and that they can be contacted for support. + +After passing the verification checks, any apps that the organization lists on {% data variables.product.prodname_marketplace %} are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. The organization can now add paid plans to any of their apps. Each app with a paid plan also goes through a financial onboarding process to check that it's set up to handle billing correctly. + +![verified creator badges](/assets/images/marketplace/marketplace_verified_creator_badges_apps.png) + +In addition to the verified creator badge, you'll also see badges for unverified and verified apps. These apps were published using the old method for verifying individual apps. + +![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) + +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." + +### About the verification process + +The first time you request verification for a listing of one of your apps, you will enter the verification process. An onboarding expert will guide you through the process. This includes checking: + +- Profile information - The basic profile information is populated accurately and appropriately. +- Security - The organization has enabled two-factor authentication. +- Verified domain - The organization has verified the domain of the site URL. +- Purchase webhook event - The event is handled correctly by the app. + +When your organization is verified, all your apps are shown with a verified creator badge. You are now able to offer paid plans for any of your apps. + +For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% note %} + +**Note:** This verification process for apps replaces the previous process where individual apps were verified. The current process is similar to the verification process for actions. If you have apps that were verified under the old process, these will not be affected by the changes. The {% data variables.product.prodname_marketplace %} team will contact you with details of how to migrate to organization-based verification. + +{% endnote %} diff --git a/translations/ko-KR/content/developers/github-marketplace/billing-customers.md b/translations/ko-KR/content/developers/github-marketplace/billing-customers.md index ddc8e0716d..ae302e3a11 100644 --- a/translations/ko-KR/content/developers/github-marketplace/billing-customers.md +++ b/translations/ko-KR/content/developers/github-marketplace/billing-customers.md @@ -13,17 +13,17 @@ versions: ### Understanding the billing cycle -Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[Webhook events for the {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)." ### Providing billing services in your app's UI -Customers must be able to perform the following actions from your app's website: -- Customers must be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. +Customers should be able to perform the following actions from your app's website: +- Customers should be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. {% data reusables.marketplace.marketplace-billing-ui-requirements %} ### Billing services for upgrades, downgrades, and cancellations -Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)." +Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). @@ -33,7 +33,7 @@ When a customer upgrades their pricing plan or changes their billing cycle from {% data reusables.marketplace.marketplace-failed-purchase-event %} -For information about building upgrade and downgrade workflows into your app, see "[Upgrading and downgrading plans](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)." +For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)." #### Downgrades and cancellations @@ -45,4 +45,4 @@ When a customer cancels a plan, you must: {% data reusables.marketplace.cancellation-clarification %} - Enable them to upgrade the plan through GitHub if they would like to continue the plan at a later time. -For information about building cancellation workflows into your app, see "[Cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)." +For information about building cancellation workflows into your app, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." diff --git a/translations/ko-KR/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md b/translations/ko-KR/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md new file mode 100644 index 0000000000..4107fa4427 --- /dev/null +++ b/translations/ko-KR/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md @@ -0,0 +1,20 @@ +--- +title: Customer experience best practices for apps +intro: 'Guidelines for creating an app that will be easy to use and understand.' +shortTitle: Customer experience best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a good customer experience. + +### Customer communication + +- Marketing materials for the app should accurately represent the app's behavior. +- Apps should include links to user-facing documentation that describe how to set up and use the app. +- Customers should be able to see what type of plan they have in the billing, profile, or account settings section of the app. +- Customers should be able to install and use your app on both a personal account and an organization account. They should be able to view and manage the app on those accounts separately. + +### Plan management + +{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/ko-KR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/ko-KR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 7bc6b6e542..52c2c64dc9 100644 --- a/translations/ko-KR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/ko-KR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,8 +60,8 @@ Once you've created a {% data variables.product.prodname_marketplace %} draft li ### Submitting your app -Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, the {% data variables.product.prodname_marketplace %} onboarding team will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." +Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." ### Removing a {% data variables.product.prodname_marketplace %} listing -If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact [marketplace@github.com](mailto:marketplace@github.com) to remove your listing. +If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing. diff --git a/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index a30f26b72e..ff81fb5871 100644 --- a/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ko-KR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -28,7 +28,7 @@ GitHub then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketp Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins. -If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)." See "[Upgrading and downgrading plans](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)" to find out how to transition a free trial to a paid plan when a free trial expires. +If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." See "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)" to find out how to transition a free trial to a paid plan when a free trial expires. See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload. diff --git a/translations/ko-KR/content/developers/github-marketplace/index.md b/translations/ko-KR/content/developers/github-marketplace/index.md index 8758c8b3e4..e0fdf26b6e 100644 --- a/translations/ko-KR/content/developers/github-marketplace/index.md +++ b/translations/ko-KR/content/developers/github-marketplace/index.md @@ -11,8 +11,10 @@ versions: {% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /about-github-marketplace %} + {% link_in_list /about-verified-creators %} {% link_in_list /requirements-for-listing-an-app %} - {% link_in_list /security-review-process-for-submitted-apps %} + {% link_in_list /security-best-practices-for-apps %} + {% link_in_list /customer-experience-best-practices-for-apps %} {% link_in_list /viewing-metrics-for-your-listing %} {% link_in_list /viewing-transactions-for-your-listing %} {% topic_link_in_list /using-the-github-marketplace-api-in-your-app %} @@ -27,7 +29,7 @@ versions: {% link_in_list /writing-a-listing-description-for-your-app %} {% link_in_list /setting-pricing-plans-for-your-listing %} {% link_in_list /configuring-a-webhook-to-notify-you-of-plan-changes %} - {% link_in_list /submitting-your-listing-for-review %} + {% link_in_list /submitting-your-listing-for-publication %} {% topic_link_in_list /selling-your-app-on-github-marketplace %} {% link_in_list /pricing-plans-for-github-marketplace-apps %} {% link_in_list /billing-customers %} diff --git a/translations/ko-KR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/ko-KR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md index bb33fe004f..aa9d924b49 100644 --- a/translations/ko-KR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/ko-KR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -10,35 +10,45 @@ versions: -{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit, and GitHub lists the price in US dollars. Customers purchase your app using a payment method attached to their {% data variables.product.product_name %} account, without having to leave GitHub.com. You don't have to write code to perform billing transactions, but you will have to handle [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) for purchase events. +{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to verified listings. + +Customers purchase your app using a payment method attached to their {% data variables.product.product_name %} account, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed. For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." -{% note %} - -**Note:** If you're listing an app on {% data variables.product.prodname_marketplace %}, you can't list your app with a free pricing plan if you offer a paid service outside of {% data variables.product.prodname_marketplace %}. - -{% endnote %} +{% data reusables.marketplace.free-plan-note %} ### Types of pricing plans -**Free pricing plans** are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. Unverified free apps do not need to implement any billing flows. Free apps that are verified by Github need to implement billing flows for new purchases and cancellations, but do not need to implement billing flows for free trials, upgrades, and downgrades. If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to resubmit the app for review. +#### Free pricing plans -**Flat rate pricing plans** charge a set fee on a monthly and yearly basis. +{% data reusables.marketplace.free-apps-encouraged %} -**Per-unit pricing plans** charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). +Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. -**Marketplace free trials** provide 14-day free trials of OAuth or GitHub Apps to customers. When you [set up a Marketplace pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/), you can select the option to provide a free trial for flat-rate or per-unit pricing plans. +All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding. + +#### Paid pricing plans + +There are two types of paid pricing plan: + +- Flat rate pricing plans charge a set fee on a monthly and yearly basis. + +- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). + +You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans. ### Free trials -Customers can start a free trial for any available paid plan on a Marketplace listing, but will not be able to create more than one free trial for a Marketplace product. +Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product. Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel. -See "[New purchases and free trials](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for details on how to handle free trials in your app. +For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)." {% note %} diff --git a/translations/ko-KR/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/ko-KR/content/developers/github-marketplace/requirements-for-listing-an-app.md index 8161beddc6..2ae24c334e 100644 --- a/translations/ko-KR/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/ko-KR/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- title: Requirements for listing an app -intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before our {% data variables.product.prodname_marketplace %} onboarding specialists will approve the listing.' +intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ @@ -12,49 +12,62 @@ versions: free-pro-team: '*' --- + +The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app. -Before you submit your app for review, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." You'll accept the terms within your [draft listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) on {% data variables.product.product_name %}. Once you've submitted your app, one of the {% data variables.product.prodname_marketplace %} onboarding specialists will reach out to you with more information about the onboarding process, and review your app to ensure it meets these requirements: +### Requirements for all {% data variables.product.prodname_marketplace %} listings -### User experience +All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -- {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. -- {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. +#### User experience requirements for all apps + +All listings should meet the following requirements, regardless of whether they are for a free or paid app. + +- Listings must not actively persuade users away from {% data variables.product.product_name %}. +- Listings must include valid contact information for the publisher. +- Listings must have a relevant description of the application. +- Listings must specify a pricing plan. - Apps must provide value to customers and integrate with the platform in some way beyond authentication. - Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only. -- Apps cannot actively persuade users away from {% data variables.product.product_name %}. -- Marketing materials for the app must accurately represent the app's behavior. -- Apps must include links to user-facing documentation that describe how to set up and use the app. -- When a customer purchases an app and GitHub redirects them to the app's installation URL, the app must begin the OAuth flow immediately. For details, see "[Handling new purchases and free trials](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/#step-3-authorization)." +- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -- Customers must be able to install your app and select repositories on both a personal and organization account. They should be able to view and manage those accounts separately. +For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)." -### Brand and listing +#### Brand and listing requirements for all apps -- Apps that use GitHub logos must follow the "[{% data variables.product.product_name %} Logos and Usage](https://github.com/logos)" guidelines. +- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)." - Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." - Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." -### 보안 +To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)." -Apps will go through a security review before being listed on {% data variables.product.prodname_marketplace %}. A successful review will meet the requirements and follow the security best practices listed in "[Security review process](/marketplace/getting-started/security-review-process/)." For information on the review process, contact [marketplace@github.com](mailto:marketplace@github.com). +### Considerations for free apps -### Billing flows +{% data reusables.marketplace.free-apps-encouraged %} -Your app must integrate [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) using the [{% data variables.product.prodname_marketplace %} webhook event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). +### Requirements for paid apps -#### Free apps +In addition to the requirements for all apps above, each app that you offer as a paid service on {% data variables.product.prodname_marketplace %} must also meet the following requirements: -{% data reusables.marketplace.free-apps-encouraged %} If you are listing a free app, you'll need to meet these requirements: +- {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. +- {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. +- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. +- Publishing organizations must have a verified domain and must enable two-factor authentication. 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.") -- Customers must be able to see that they have a free plan in the billing, profile, or account settings section of the app. -- When a customer cancels your app, you must follow the flow for [cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/). +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the listing. -#### Paid apps +{% note %} -To offer your app as a paid service, you'll need to meet these requirements to list your app on {% data variables.product.prodname_marketplace %}: +The verification process is open to organizations. {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% endnote %} + +### Billing requirements for paid apps + +Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their {% data variables.product.product_name %} account. -- To sell your app in {% data variables.product.prodname_marketplace %}, it must use GitHub's billing system. Your app does not need to handle payments but does need to use "[{% data variables.product.prodname_marketplace %} purchase events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" to manage new purchases, upgrades, downgrades, cancellations, and free trials. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" to learn about how to integrate these events into your app. Using GitHub's billing system allows customers to purchase an app without leaving GitHub and pay for the service with the payment method already attached to their {% data variables.product.product_name %} account. - Apps must support both monthly and annual billing for paid subscriptions purchases. - Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." -{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/ko-KR/content/developers/github-marketplace/security-best-practices-for-apps.md b/translations/ko-KR/content/developers/github-marketplace/security-best-practices-for-apps.md new file mode 100644 index 0000000000..eaec8c6874 --- /dev/null +++ b/translations/ko-KR/content/developers/github-marketplace/security-best-practices-for-apps.md @@ -0,0 +1,59 @@ +--- +title: Security best practices for apps +intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/marketplace/getting-started/security-review-process/ + - /marketplace/getting-started/security-review-process + - /developers/github-marketplace/security-review-process-for-submitted-apps +shortTitle: Security best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a secure user experience. + +### Authorization, authentication, and access control + +We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details. +- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia. +- Apps should provide customers with a way to delete their account, without having to email or call a support person. +- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately. +- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code. +- Apps should not share service accounts such as email or database services to manage your SaaS service. +- All services used in your app should have unique login and password credentials. +- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties. +- Apps should not use personal access tokens to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps): + - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/). + - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). + +### Data protection + +- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git. +- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). +- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub. +- Apps should not require the user to provide their GitHub password. +- Apps should encrypt tokens, client IDs, and client secrets. + +### Logging and monitoring + +Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year. A security log should include: + +- Authentication and authorization events +- Service configuration changes +- Object reads and writes +- All user and group permission changes +- Elevation of role to admin +- Consistent timestamping for each event +- Source users, IP addresses, and/or hostnames for all logged actions + +### Incident response workflow + +To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident. + +For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template. + +### Vulnerability management and patching workflow + +You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. + +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)." diff --git a/translations/ko-KR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/ko-KR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 205978a5f6..9ab919817d 100644 --- a/translations/ko-KR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/ko-KR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Setting pricing plans for your listing -intro: 'When [listing your app on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/), you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' +intro: 'When you list your app on {% data variables.product.prodname_marketplace %}, you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' redirect_from: - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ @@ -17,57 +17,52 @@ versions: free-pro-team: '*' --- +### About setting pricing plans +If you want to sell an app on {% data variables.product.prodname_marketplace %}, you need to request verification when you publish the listing for your app. During the verification process, an onboarding expert checks the organization's identity and security settings. The onboarding expert will also take the organization through financial onboarding. For more information, see: "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% data variables.product.prodname_marketplace %} offers several different types of pricing plan. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." + +### About saving pricing plans + +You can save pricing plans in a draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish a pricing plan on a published listing, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. + +For guidelines on billing customers, see "[Billing customers](/developers/github-marketplace/billing-customers)." ### Creating pricing plans -To learn about the types of pricing plans that {% data variables.product.prodname_marketplace %} offers, see "[{% data variables.product.prodname_marketplace %} Pricing Plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." You'll also find helpful billing guidelines in "[Selling your app](/marketplace/selling-your-app/)." - -Pricing plans can be in the draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published listing will function the same way as draft listings until your app is approved and listed on {% data variables.product.prodname_marketplace %}. Draft listings allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish the pricing plan, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. - -To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). If you haven't created a {% data variables.product.prodname_marketplace %} listing yet, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how. +To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). For more information, see "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)." When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan: -#### Plan name +- **Plan name** - Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align with the plan's resources, the size of the company that will use the plan, or anything you'd like. -Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align to the plan's resources, the size of the company that will use the plan, or anything you'd like. +- **Pricing models** - There are three types of pricing plan: free, flat-rate, and per-unit. All plans require you to process new purchase and cancellation events from the marketplace API. In addition, for paid plans: -#### Pricing models + - You must set a price for both monthly and yearly subscriptions in US dollars. + - Your app must process plan change events. + - You must request verification to publish a listing with a paid plan. + - {% data reusables.marketplace.marketplace-pricing-free-trials %} -##### Free plans + For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.free-apps-encouraged %} A free plan still requires you to handle [new purchase](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/) and [cancellation](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/) billing flows. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" for more details. +- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. -##### Flat-rate plans +- **Short description** - Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. -Flat-rate pricing plans allow you to offer your service to customers for a flat-rate fee. {% data reusables.marketplace.marketplace-pricing-free-trials %} +- **Bullets** - You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. -You must set a price for both monthly and yearly subscriptions in U.S. Dollars for flat-rate plans. - -##### Per-unit plans - -Per-unit pricing allows you to offer your app in units. For example, a unit can be a person, seat, or user. You'll need to provide a name for the unit and set a price for both monthly and yearly subscriptions, in U.S. Dollars. - -#### Available for - -{% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. - -#### Short description - -Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. - -#### Bullets - -You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. +{% data reusables.marketplace.free-plan-note %} ### Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan -If a pricing plan for your {% data variables.product.prodname_marketplace %} plan is no longer needed or if you need to adjust pricing details, you can remove it. +If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it. ![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png) -Once you publish a pricing plan for an app already listed in the {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." +Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan and create a new plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription. diff --git a/translations/ko-KR/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/ko-KR/content/developers/github-marketplace/submitting-your-listing-for-publication.md new file mode 100644 index 0000000000..b25c4580ae --- /dev/null +++ b/translations/ko-KR/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -0,0 +1,37 @@ +--- +title: Submitting your listing for publication +intro: 'You can submit your listing for the {% data variables.product.prodname_dotcom %} community to use.' +redirect_from: + - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review + - /developers/github-marketplace/submitting-your-listing-for-review +versions: + free-pro-team: '*' +--- + + + +Once you've completed the listing for your app, you'll see two buttons that allow you to request publication of the listing with or without verification. The **Request** button for "Publish without verification" is disabled if you have published any paid pricing plans in the listing. + +![Unverified and verified request button](/assets/images/marketplace/marketplace-request-button.png) + +{% data reusables.marketplace.launch-with-free %} + +After you submit your listing for review, an onboarding expert will reach out to you with additional information. + +For an overview of the process for creating and submitting a listing, see "[About {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)." + +### Prerequisites for publishing with verification + +Before you request verification of your listing, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your app. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +If you've met the requirements for listing and you've integrated with the {% data variables.product.prodname_marketplace %} API, go ahead and submit your listing. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Transferring an app to an organization before you submit](#transferring-an-app-to-an-organization-before-you-submit)" below. + +### Transferring an app to an organization before you submit + +You cannot sell an app that's owned by a user account. You need to transfer the app to an organization that is already a verified creator, or that can request verification for a listing for the app. For details, see: + +1. "[Creating an organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" + +1. "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" diff --git a/translations/ko-KR/content/developers/github-marketplace/testing-your-app.md b/translations/ko-KR/content/developers/github-marketplace/testing-your-app.md index 09e79b1a7a..577b6d624a 100644 --- a/translations/ko-KR/content/developers/github-marketplace/testing-your-app.md +++ b/translations/ko-KR/content/developers/github-marketplace/testing-your-app.md @@ -1,6 +1,6 @@ --- title: Testing your app -intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before the {% data variables.product.prodname_marketplace %} onboarding team approves your app, it must adequately handle the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows).' +intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.' redirect_from: - /apps/marketplace/testing-apps-apis-and-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ @@ -13,7 +13,7 @@ versions: ### Testing apps -You can use a [draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) to simulate each of the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows). A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. +You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." #### Using a development app with a draft listing to test changes diff --git a/translations/ko-KR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/ko-KR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index 60d0556bb3..e0dcbc1739 100644 --- a/translations/ko-KR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/ko-KR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -1,6 +1,6 @@ --- title: Webhook events for the GitHub Marketplace API -intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan. For details on how to respond to each of these types of events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)."' +intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.' redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ diff --git a/translations/ko-KR/content/developers/overview/about-githubs-apis.md b/translations/ko-KR/content/developers/overview/about-githubs-apis.md index 0d647b78cb..e60baa72e3 100644 --- a/translations/ko-KR/content/developers/overview/about-githubs-apis.md +++ b/translations/ko-KR/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,7 @@ versions: github-ae: '*' --- -There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). - -When using the REST API, we encourage you to [request v3 via the `Accept` header](/rest/overview/media-types#request-specific-version). - -For information on using the GraphQL API, see the [v4 docs](/graphql). +There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). For information on using the GraphQL API, see the [v4 docs](/graphql). ## Deprecated versions diff --git a/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md index 7c93e78582..83942fe2e3 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -145,7 +145,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {{ webhookPayloadsForCurrentVersion.check_suite.completed }} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### code_scanning_alert {% data reusables.webhooks.code_scanning_alert_event_short_desc %} @@ -445,7 +445,7 @@ When someone revokes their authorization of a {% data variables.product.prodname #### Webhook payload object {% data reusables.webhooks.installation_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Webhook payload example @@ -469,7 +469,7 @@ When someone revokes their authorization of a {% data variables.product.prodname #### Webhook payload object {% data reusables.webhooks.installation_repositories_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Webhook payload example @@ -1047,7 +1047,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends | 키 | 유형 | 설명 | | ---- | ----- | --------------------------------------------------------------------------- | -| `동작` | `문자열` | The action that was performed. This can be one of:
      • `created` - A repository is created.
      • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
      • `archived` - A repository is archived.
      • `unarchived` - A repository is unarchived.
        • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
      • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/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.
      | +| `동작` | `문자열` | 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.
      | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1100,6 +1100,31 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### secret_scanning_alert + +{% data reusables.webhooks.secret_scanning_alert_event_short_desc %} + +#### Availability + +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `secret_scanning_alerts:read` permission + +#### Webhook payload object + +{% 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. + +#### Webhook payload example + +{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} +{% endif %} + ### 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/)." 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 new file mode 100644 index 0000000000..05cfcd1b6b --- /dev/null +++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -0,0 +1,54 @@ +--- +title: About discussions +intro: Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About discussions + +With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools. + +- Share announcements and information, gather feedback, plan, and make decisions +- Ask questions, discuss and answer the questions, and mark the discussions as answered +- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows + +![Discussions tab for a repository](/assets/images/help/discussions/hero.png) + +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)." + +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)." + +### About categories and formats for discussions + +{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %} + +For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %} + +For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +### Best practices for discussions + +As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)." + +Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." + +### Sharing feedback + +You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). + +### 더 읽을거리 + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" +- "[Moderating comments and conversations](/github/building-a-strong-community/moderating-comments-and-conversations)" +- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md new file mode 100644 index 0000000000..451c539854 --- /dev/null +++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -0,0 +1,48 @@ +--- +title: Collaborating with maintainers using discussions +shortTitle: Collaborating with maintainers +intro: You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion. +permissions: People with read permissions to a repository can start and participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About collaboration with maintainers using discussions + +{% data reusables.discussions.about-discussions %} If you use or contribute to a project, you can start a discussion to make suggestions and engage with maintainers and community members about your plans, questions, ideas, and feedback. For more information, see "[‎About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +{% data reusables.discussions.about-categories-and-formats %} Repository administrators and project maintainers can delete a discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)." + +{% data reusables.discussions.github-recognizes-members %} These members appear in a list of the most helpful contributors to the project's discussions. As your project grows, you can grant higher access permissions to active members of your community. For more information, see "[Granting higher permissions to top contributors](/discussions/guides/granting-higher-permissions-to-top-contributors)" + +![Most helpful contributors to discussions for a project](/assets/images/help/discussions/most-helpful.png) + +For more information about participation in discussions, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +### 빌드전 요구 사양 + +To collaborate with maintainers using discussions, a repository administrator or project maintainer must enable discussions for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Starting a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Filtering the list of discussions + +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the **Search all discussions** field, type a search query. Optionally, to the right of the search field, click a button to further filter the results. ![Search bar and buttons for filtering discussions](/assets/images/help/discussions/search-and-filter-controls.png) +1. In the list of discussions, click the discussion you want to view. ![Discussion search results](/assets/images/help/discussions/search-result.png) + +### Converting an issue to a discussion + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)." + +### 더 읽을거리 + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/index.md new file mode 100644 index 0000000000..44aed03c8b --- /dev/null +++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/index.md @@ -0,0 +1,14 @@ +--- +title: Collaborating with your community using discussions +shortTitle: Collaborating using discussions +intro: Gather and discuss your project with community members and other maintainers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /about-discussions %} +{% link_in_list /participating-in-a-discussion %} +{% link_in_list /collaborating-with-maintainers-using-discussions %} + diff --git a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md new file mode 100644 index 0000000000..6b83789ee7 --- /dev/null +++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -0,0 +1,31 @@ +--- +title: Participating in a discussion +intro: You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}. +permissions: People with read permissions to a repository can participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About participation in a discussion + +{% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)." + +You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)." + +### 빌드전 요구 사양 + +Discussions must be enabled for the repository for you to participate in a discussion in the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Creating a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Marking a comment as an answer + +Discussion authors and users with the triage role or greater for a repository can mark a comment as the answer to a discussion in the repository. + +{% data reusables.discussions.marking-a-comment-as-an-answer %} 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 new file mode 100644 index 0000000000..52f05d1759 --- /dev/null +++ b/translations/ko-KR/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -0,0 +1,49 @@ +--- +title: Best practices for community conversations on GitHub +shortTitle: Best practices for community conversations +intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to a discussion when you are ready to scope out the work.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Community conversations in {% data variables.product.prodname_discussions %} + +Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository and gather diverse feedback and ideas more quickly. You can help drive a productive conversation by: + +- Asking pointed questions and follow-up questions to garner specific feedback +- Capture a diverse experience and distill it down to main points +- Open an issue to take action based on the conversation, where applicable + +For more information about opening an issue and cross-referencing a discussion, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." + +### Learning about conversations on GitHub + +You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have. + +You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and spike out a project's specific details before committing it to an issue, which can then be scoped. Discussions are useful for teams if: +- You are in the discovery phase of a project and are still learning which director your team wants to go in +- You want to collect feedback from a wider community about a project +- You want to keep bug fixes, feature requests, and general conversations separate + +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](/articles/about-team-discussions)." + +### Following contributing guidelines + +Before you open a discussion, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project. + +For more information, see "[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### 다음 단계 + +To continue learning about {% data variables.product.prodname_discussions %} and quickly create a discussion for your community, see "[Quickstart for {% data variables.product.prodname_discussions %}](/discussions/quickstart)." + +### 더 읽을거리 + +- "[Setting up your project for healthy contributions](/articles/setting-up-your-project-for-healthy-contributions)" +- "[Using templates to encourage useful issues and pull requests](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Moderating comments and conversations](/articles/moderating-comments-and-conversations)" +- "[Writing on {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)" diff --git a/translations/ko-KR/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/ko-KR/content/discussions/guides/finding-discussions-across-multiple-repositories.md new file mode 100644 index 0000000000..b39a876fc3 --- /dev/null +++ b/translations/ko-KR/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -0,0 +1,20 @@ +--- +title: Finding discussions across multiple repositories +intro: 'You can easily access every discussion you''ve created or participated in across multiple repositories.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Finding discussions + +1. Navigate to {% data variables.product.prodname_dotcom_the_website %}. +1. In the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your discussions**. !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. + +### 더 읽을거리 + +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" 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 new file mode 100644 index 0000000000..8ded0aaa3a --- /dev/null +++ b/translations/ko-KR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -0,0 +1,32 @@ +--- +title: Granting higher permissions to top contributors +intro: 'Repository administrators can promote any community member to a moderator and maintainer.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Introduction + +The most helpful contributors for the past 30 days are highlighted on the {% data variables.product.prodname_discussions %} dashboard, based on how many comments were marked as answers by other community members. Helpful contributors can help drive a healthy community and moderate and guide the community space in addition to maintainers. + +### Step 1: Audit your discussions top contributors + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Compare the list of contributors with their access permissions to see who qualifies to moderate the discussion. + +### Step 2: Review permission levels for discussions + +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)." + +### Step 3: Change permissions levels for top contributors + +You can change a contributor's permission levels to give them more access to the tooling they need to moderate GitHub Discussions. To change a person's or team's permission levels, see "[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)." + +### Step 4: Notify community members of elevated access + +When you change a collaborators permission level, they will receive a notification for the change. diff --git a/translations/ko-KR/content/discussions/guides/index.md b/translations/ko-KR/content/discussions/guides/index.md new file mode 100644 index 0000000000..b5019ecee5 --- /dev/null +++ b/translations/ko-KR/content/discussions/guides/index.md @@ -0,0 +1,31 @@ +--- +title: Discussions guides +shortTitle: 안내서 +intro: 'Discover pathways to get started or learn best practices for participating or monitoring your community''s discussions.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Getting started with discussions + +{% link_in_list /about-discussions %} +{% link_in_list /best-practices-for-community-conversations-on-github %} +{% link_in_list /finding-discussions-across-multiple-repositories %} + +### Administering discussions + +{% link_in_list /granting-higher-permissions-to-top-contributors %} + + + + + diff --git a/translations/ko-KR/content/discussions/index.md b/translations/ko-KR/content/discussions/index.md new file mode 100644 index 0000000000..66dca4f270 --- /dev/null +++ b/translations/ko-KR/content/discussions/index.md @@ -0,0 +1,55 @@ +--- +title: GitHub Discussions Documentation +beta_product: true +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.' +introLinks: + quickstart: /discussions/quickstart +featuredLinks: + guides: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + gettingStarted: + - /discussions/quickstart + guideCards: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + popular: + - /discussions/guides/granting-higher-permissions-to-top-contributors + - /discussions/guides/best-practices-for-community-conversations-on-github + - /discussions/guides/finding-discussions-across-multiple-repositories + - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions + - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository +product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +layout: product-landing +versions: + free-pro-team: '*' +--- + + + + + + + +{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} +{% if discussionsCommunityExamples %} +
      +

      Communities using discussions

      + +
      + {% 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" %} +
      +
      +{% endif %} diff --git a/translations/ko-KR/content/discussions/managing-discussions-for-your-community/index.md b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/index.md new file mode 100644 index 0000000000..8ccb2875b2 --- /dev/null +++ b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/index.md @@ -0,0 +1,13 @@ +--- +title: Managing discussions for your community +shortTitle: Managing discussions +intro: 'You can enable and configure discussions for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /managing-discussions-in-your-repository %} +{% link_in_list /managing-categories-for-discussions-in-your-repository %} +{% link_in_list /moderating-discussions %} diff --git a/translations/ko-KR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md new file mode 100644 index 0000000000..010ec989cd --- /dev/null +++ b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md @@ -0,0 +1,56 @@ +--- +title: Managing categories for discussions in your repository +intro: You can categorize the discussions in your repository to organize conversations for your community members, and you can choose a format for each category. +permissions: Repository administrators and people with write or greater access to a repository can enable discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About categories for discussions + +{% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} + +Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations.{% data reusables.discussions.repository-category-limit %} + +For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +### Default categories + +| 카테고리 | Purpose | 유형 | +|:--------------- |:-------------------------------------------------------------------- |:--------------------- | +| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion | +| 💡Ideas | Ideas to change or improve the project | Open-ended discussion | +| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer | +| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion | + +### Creating a category + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.edit-categories %} +1. Click **New category**. !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png) +1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png) +1. Click **Create**. !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png) + +### Editing a category + +You can edit a category to change the category's emoji, title, description, and discussion format. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} +![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png) +1. Click **Save changes**. !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +### Deleting a category + +When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png) +1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png) +1. Click **Delete & Move**. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png) 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 new file mode 100644 index 0000000000..9becfa8d0a --- /dev/null +++ b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -0,0 +1,94 @@ +--- +title: Managing discussions in your repository +intro: You can categorize, spotlight, transfer, or delete the discussions in a repository. +permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About management of discussions + +{% 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)." + +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](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)." + +For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/github/building-a-strong-community/moderating-comments-and-conversations)." + +### 빌드전 요구 사양 + +To manage discussions in a repository, discussions must be enabled for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Changing the category for a discussion + +You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" article. + +You can also move a discussion to a different category. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) + +### Pinning a discussion + +You can pin up to four important discussions above the list of discussions for the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png) +1. Optionally, customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Editing a pinned discussion + +Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Unpinning a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) +1. Read the warning, then click **Unpin discussion**. !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png) + +### Transferring a discussion + +To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png) +1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Click **Transfer discussion**. !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png) + +### Deleting a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png) +1. Read the warning, then click **Delete this discussion**. !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) + +### Converting issues based on labels + +You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Next to the label you want to convert to issues, click **Convert issues**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/ko-KR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md new file mode 100644 index 0000000000..2c91d32d89 --- /dev/null +++ b/translations/ko-KR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -0,0 +1,39 @@ +--- +title: Moderating discussions +intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, and converting issues to discussions. and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct to discussions.' +permissions: People with triage access to a repository can moderate discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About moderating discussions + +{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you 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. + +### Marking a comment as an answer + +{% data reusables.discussions.marking-a-comment-as-an-answer %} + +### Locking discussions + +It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository will still be able to comment on the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the discussion you want to lock. ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the right margin of a discussion, click **Lock conversation**. +1. Read the information about locking conversations and click **Lock conversation on this discussion**. +1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**. + +### Converting an issue to a discussion + +When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository can bulk convert issues based on labels. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to convert. +1. In the right margin of an issue, click **Convert to discussion**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/ko-KR/content/discussions/quickstart.md b/translations/ko-KR/content/discussions/quickstart.md new file mode 100644 index 0000000000..d9fcf987de --- /dev/null +++ b/translations/ko-KR/content/discussions/quickstart.md @@ -0,0 +1,58 @@ +--- +title: Quickstart for GitHub Discussions +intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository and start conversations with your community.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Introduction + +{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike issues. Discussions enable fluid, open conversation in a public forum. + +Discussions give a space for more collaborative conversations by connecting and giving a more centralized area to connect and find information. + +### Enabling {% data variables.product.prodname_discussions %} on your repository + +Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public repositories. + +When you first enable a {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. + +{% data reusables.repositories.navigate-to-repo %} +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. ![Public settings button](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", click **Set up discussions**. ![Set up a discussion button under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png) +1. Under "Start a new discussion," edit the template to align with the resources and tone you want to set for your community. +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) + +### Welcoming contributions to your discussions + +You can welcome your community and introduce a new way to communicate in a repository by creating a welcome post and pin the post to your {% data variables.product.prodname_discussions %} page. Pinning and locking discussions helps people know that a post is meant as an announcement. You can use announcements as a way to link people to more resources and offer guidance for opening discussions in your community. For more information about pinning a discussion, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + + +### Setting up community guidelines for contributors + +You can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. You can also update the repository's README to communicate expectations on when collaborators should open an issue or discussion. + +For more information about providing guidelines for your project, see "[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and "[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Creating a new discussion + +Anyone with access to a repository can create a discussion. + +{% data reusables.discussions.starting-a-discussion %} + +### Organizing discussions into relevant categories + +Repository owners and people with write access can create new categories to keep discussions organized. Collaborators participating and creating new discussions can group discussions into the most relevant existing categories. Discussions can also be recategorized after they are created. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" + +### Promoting healthy conversations + +People with write permissions for a repository can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +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)." + +### 다음 단계 + +Once there is a clear path to scope work out and move an idea from concept to reality, you can create an issue and start tracking your progress. For more information on creating an issue from a discussion, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." diff --git a/translations/ko-KR/content/education/guides.md b/translations/ko-KR/content/education/guides.md new file mode 100644 index 0000000000..0265b53633 --- /dev/null +++ b/translations/ko-KR/content/education/guides.md @@ -0,0 +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 +versions: + free-pro-team: '*' +--- + +### Get started with {% 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. + +- [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/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) + +### Run a software development course with {% 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 %}. + +- [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) + +### Learn to develop software + +Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. + +- [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/teach-and-learn-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) + +### Contribute to the community + +Participate in the community, get training from {% data variables.product.company_short %}, and learn or teach new skills. + +- [{% data variables.product.prodname_education_community %}](https://education.github.community) +- [About Campus Experts](/education/teach-and-learn-with-github-education/about-campus-experts) +- [About Campus Advisors](/education/teach-and-learn-with-github-education/about-campus-advisors) diff --git a/translations/ko-KR/content/education/index.md b/translations/ko-KR/content/education/index.md new file mode 100644 index 0000000000..c3827df288 --- /dev/null +++ b/translations/ko-KR/content/education/index.md @@ -0,0 +1,45 @@ +--- +title: GitHub Education Documentation +shortTitle: Education +intro: "{% data variables.product.prodname_education %} helps you teach or learn software development with the tools and support of {% data variables.product.company_short %}'s platform and community." +introLinks: + quickstart: /education/quickstart +featuredLinks: + guides: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + guideCards: + - /github/getting-started-with-github/signing-up-for-a-new-github-account + - /github/getting-started-with-github/git-and-github-learning-resources + - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom + popular: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /desktop + - /github/getting-started-with-github/github-cli + - /education/manage-coursework-with-github-classroom/teach-with-github-classroom +changelog: + - + title: 'Try something new at Local Hack Day: Learn' + date: '2020-10-15' + href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ + - + title: 'Remote Education: Creating community through shared experiences' + date: '2020-09-24' + href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ + - + title: 'Remote Education: A series of best practices for online campus communities' + date: '2020-09-10' + href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ + - + title: Welcome to the inaugural class of MLH Fellows + date: '2020-06-24' + href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ +layout: product-landing +versions: + free-pro-team: '*' +--- + + + diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md new file mode 100644 index 0000000000..2f9997821d --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -0,0 +1,31 @@ +--- +title: About using MakeCode Arcade with GitHub Classroom +shortTitle: About using MakeCode Arcade +intro: You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-makecode +--- + +### About MakeCode Arcade + +MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade. + +For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. + +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. + +### About submission of assignments with MakeCode Arcade + +By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.product.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen. + +![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) + +### 더 읽을거리 + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md new file mode 100644 index 0000000000..19b032ae1d --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: About using Repl.it with GitHub Classroom +shortTitle: About using Repl.it +intro: You can configure Repl.it as the online integrated development environment (IDE) for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-replit +--- + +### About Repl.it + +Repl.it is an online integrated development environment (IDE) that supports multiple programming languages. Students can write, edit, run, test, and debug code in a browser with Repl.it. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. + +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). + +For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. + +### About submission of assignments with Repl.it + +By default, Repl.it is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with Repl.it, students should push changes to {% data variables.product.product_location %} using the version control functionality in the left sidebar. + +![Repl.it version control functionality](/assets/images/help/classroom/ide-replit-version-control-button.png) + +For more information about using Git on Repl.it, see the [Repl.it + Git Tutorial](https://repl.it/talk/learn/Replit-Git-Tutorial/23331) on the Repl.it website. + +### 더 읽을거리 + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md new file mode 100644 index 0000000000..26a082d449 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: Basics of setting up GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %} basics' +intro: Learn how to set up your classroom, manage assignments, and configure time-saving automation. +versions: + free-pro-team: '*' +--- + +### Videos about {% data variables.product.prodname_classroom %} + +You can watch a series of short video tutorials about the configuration and use of {% data variables.product.prodname_classroom %}. To watch all videos as part of a continuous playlist, see the [{% data variables.product.prodname_classroom %} Getting Started Guide](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) on YouTube. + +For more information about terminology for {% data variables.product.prodname_classroom %}, see "[Glossary](/education/manage-coursework-with-github-classroom/glossary)". + +1. Getting started {% octicon "link-external" aria-label="The external link icon" %} +2. Adding your student roster {% octicon "link-external" aria-label="The external link icon" %} +3. Creating assignments + - Creating an assignment using a {% data variables.product.prodname_dotcom %} repository {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Microsoft MakeCode as your online IDE {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Repl.it as your online IDE {% octicon "link-external" aria-label="The external link icon" %} +4. How students complete assignments {% octicon "link-external" aria-label="The external link icon" %} +5. How teachers review assignments {% octicon "link-external" aria-label="The external link icon" %} +6. Creating group assignments {% octicon "link-external" aria-label="The external link icon" %} +7. Next steps to get started {% octicon "link-external" aria-label="The external link icon" %} +8. {% data variables.product.prodname_dotcom %} Teacher Toolbox {% octicon "link-external" aria-label="The external link icon" %} + +### 다음 단계 + +For more information about teaching with {% data variables.product.prodname_classroom %}, see "[Teach with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom)." + +### 더 읽을거리 + +- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md new file mode 100644 index 0000000000..72957e48b8 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md @@ -0,0 +1,50 @@ +--- +title: Configure default settings for assignment repositories +shortTitle: Configure defaults for assignment repositories +intro: You can use the Probot Settings app to configure the default settings for repositories that {% data variables.product.prodname_classroom %} creates for an assignment. +permissions: Organization owners can configure default settings for assignment repositories by installing a {% data variables.product.prodname_github_app %} for the organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/probot-settings +--- + +### About configuration of defaults for assignment repositories + +{% data variables.product.prodname_classroom %} creates a repository that belongs for each student or team that accepts an assignment. The repository belongs to the organization that you use for {% data variables.product.prodname_classroom %}. Assignment repositories can be empty, or you can use a template repository. For more information, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} + +With the Probot Settings app, you can create a file named _.github/settings.yml_ in a repository that contains a list of settings for the repository, and then install a {% data variables.product.prodname_github_app %} for your organization that automatically applies the settings to the repository. + +You can include _.github/settings.yml_ in a template repository that you use for an assignment in {% data variables.product.prodname_classroom %}. When an individual or team accepts the assignment, {% data variables.product.prodname_classroom %} creates the assignment repository, and the Settings app automatically applies the settings from _.github/settings.yml_. + +Probot is a a project, framework, and collection of free apps to automate {% data variables.product.product_name %}. A Probot app can listen to repository events, like the creation of new commits, comments, and issues, and automatically respond to the event. + +For more information, see the [Probot website](https://probot.github.io) and the [Settings app website](https://probot.github.io/apps/settings/). For more information about {% data variables.product.prodname_github_apps %}, see "[About apps](/developers/apps/about-apps)." + +### Adding the Settings app to your organization + +After you install the Probot Settings app for your organization, the app will apply the settings that you define in _.github/settings.yml_ for any repository in your organization, including new assignment repositories that {% data variables.product.prodname_classroom %} creates. + +1. Navigate to the [Settings app page](https://github.com/apps/settings). +1. Click **Install**, then click the organization that you use for {% data variables.product.prodname_classroom %}. Provide the app full access to all repositories owned by the organization. ![Installing the Probot Settings app](/assets/images/help/classroom/probot-settings.gif) + +### Configuring default settings for an assignment repository + +1. Create a template repository that contains a _.github/settings.yml_ file. For a complete list of settings, see the [README](https://github.com/probot/settings#github-settings) for the `probot/settings` repository. For more information about using a template repository for starter code in {% data variables.product.prodname_classroom %}, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + + {% warning %} + + **Warning:** Do not define `collaborators` in the _.github/settings.yml_ file for your template repository. {% data variables.product.prodname_classroom %} automatically grants teachers and teaching assistants access to assignment repositories. + + {% endwarning %} + +1. Create an assignment using the template repository containing _.github/settings.yml_ as the starter code. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +The Probot Settings app for your organization will now apply the settings you define in _.github/settings.yml_ within the template repository to every assignment repository that {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} creates for a student or team. + +### 더 읽을거리 + +- [Probot apps](https://probot.github.io/apps/) +- [Probot documentation](https://probot.github.io/docs/) diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md new file mode 100644 index 0000000000..55c31e532e --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -0,0 +1,138 @@ +--- +title: Connect a learning management system to GitHub Classroom +intro: You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom + - /education/manage-coursework-with-github-classroom/connect-to-lms + - /education/manage-coursework-with-github-classroom/generate-lms-credentials + - /education/manage-coursework-with-github-classroom/setup-canvas + - /education/manage-coursework-with-github-classroom/setup-generic-lms + - /education/manage-coursework-with-github-classroom/setup-moodle +--- + +### About configuration of your LMS + +You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS. + +### 빌드전 요구 사양 + +To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)." + +### Supported LMSes + +{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards. + +- LTI version 1.0 and/or 1.1 +- LTI Names and Roles Provisioning 1.X + +Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website. + +{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. + +- Canvas +- Google Classroom +- Moodle +- Sakai + +Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace + +### Generating configuration credentials for your classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster. + - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)." +1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**. ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. Read about connecting your LMS, then click **Connect to _LMS_**. +1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom. ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png) + +### Configuring a generic LMS + +You must configure the privacy settings for your LMS to allow external tools to receive roster information. + +1. Navigate to your LMS. +1. Configure an external tool. +1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}. + - Consumer key + - Shared secret + - Launch URL (sometimes called "tool URL" or similar) + +### Configuring Canvas + +You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). + +1. Sign into [Canvas](https://www.instructure.com/canvas/#login). +1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}. +1. In the left sidebar, click **Settings**. +1. Click the **Apps** tab. +1. Click **View app configurations**. +1. Click **+App**. +1. Select the **Configuration Type** drop-down menu, and click **By URL**. +1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Canvas app configuration | Value or setting | + |:------------------------------------------------------------------------- |:------------------------------------------------------------------ | + | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} + | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled | + | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} + + {% note %} + + **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website. + + {% endnote %} + +1. Click **Submit**. +1. In the left sidebar, click **Home**. +1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}. + +### Configuring Moodle + +You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org). + +You must be using Moodle version 3.0 or greater. + +1. Sign into [Moodle](https://moodle.org/login/index.php). +1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}. +1. Click **Turn editing on**. +1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**. +1. Choose **External tool** and click **Add**. +1. In the "Activity name" field, type "GitHub Classroom". +1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**. +1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Moodle app configuration | Value or setting | + |:--------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_

      **Note**: You can use any name, but we suggest this value for clarity. | + | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} + | **LTI version** | LTI 1.0/1.1 | + | **Default launch container** | New window | + | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} + +1. Scroll to and click **Services**. +1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**. +1. Scroll to and click **Privacy**. +1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**. +1. At the bottom of the page, click **Save changes**. +1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**. +1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**. +1. At the bottom of the page, click **Save and return to course**. +1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity. + +### Importing a roster from your LMS + +For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + +### Disconnecting your LMS + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Connect to a learning management system (LMS)", click **Connection Settings**. !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**. !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) 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 new file mode 100644 index 0000000000..50361dd2e8 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -0,0 +1,145 @@ +--- +title: Create a group assignment +intro: 'You can create a collaborative assignment for teams of students who participate in your course.' +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/create-group-assignments +--- + +### About group assignments + +{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers. + +When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment. + +{% data reusables.classroom.classroom-creates-group-repositories %} + +{% data reusables.classroom.about-assignments %} + +You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/github/setting-up-and-managing-organizations-and-teams/about-teams)." + +For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### 빌드전 요구 사양 + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Defining teams for an assignment](#defining-teams-for-an-assignment) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +#### Defining teams for an assignment + +If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams. + +{% tip %} + +**Tips**: + +- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course. + +- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members. + +{% endtip %} + +![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png) + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +### Providing feedback + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the team. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
      + Group assignment +
      + +### 다음 단계 + +- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. + +- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### 더 읽을거리 + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md new file mode 100644 index 0000000000..65a51556da --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -0,0 +1,19 @@ +--- +title: Create an assignment from a template repository +intro: You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments +--- + +You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. For more information, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." + +### 더 읽을거리 + +- "[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)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md new file mode 100644 index 0000000000..0dc4885527 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -0,0 +1,124 @@ +--- +title: Create an individual assignment +intro: You can create an assignment for students in your course to complete individually. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment + - /education/manage-coursework-with-github-classroom/create-an-individual-assignment +--- + +### About individual assignments + +{% data reusables.classroom.assignments-individual-definition %} + +{% data reusables.classroom.classroom-creates-individual-repositories %} + +{% data reusables.classroom.about-assignments %} + +For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### 빌드전 요구 사양 + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +### Providing feedback for an assignment + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the student. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
      + Individual assignment +
      + +### 다음 단계 + +- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." + +- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### 더 읽을거리 + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md new file mode 100644 index 0000000000..dc4171e7a0 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md @@ -0,0 +1,9 @@ +--- +title: Get started with GitHub Classroom +shortTitle: 시작하기 +intro: Learn how to configure and use {% data variables.product.prodname_classroom %} to administer your course. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/glossary.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/glossary.md new file mode 100644 index 0000000000..65c2f88995 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/glossary.md @@ -0,0 +1,52 @@ +--- +title: 용어 사전 +intro: You can review explanations of terminology for {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +--- + +### assignment + +An assignment is coursework in {% data variables.product.prodname_classroom %}. A teacher can assign an assignment to an individual student or a group of students. Teachers can import starter code for the assignment, assign students, and create a deadline for each assignment. For more information, see the definitions for "[individual assignment](#individual-assignment)" and "[group assignment](#group-assignment)." + +--- + +### classroom + +A classroom is the basic unit of {% data variables.product.prodname_classroom %}. Teachers can use a classroom to organize and manage students, teaching assistants, and assignments for a single course. A classroom belongs to an organization on {% data variables.product.prodname_dotcom_the_website %}. To administer a classroom, you must be an organization owner for the organization on {% data variables.product.prodname_dotcom %}. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." + +--- + +### {% data variables.product.prodname_classroom %} + +{% data variables.product.prodname_classroom %} is a web application for educators that provides course administration tools integrated with {% data variables.product.prodname_dotcom %}. For more information, see the [{% data variables.product.prodname_classroom %}](https://classroom.github.com/) website. + +--- + +### group assignment + +{% data reusables.classroom.assignments-group-definition %} For more information, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +--- + +### identifier + +An identifier in {% data variables.product.prodname_classroom %} is a unique ID for a student participating in a course. For example, an identifier can be a student name, alphanumeric ID, or email address. + +--- + +### individual assignment + +{% data reusables.classroom.assignments-individual-definition %} For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +--- + +### roster + +A roster allows a teacher to manage students and assignment submissions in a classroom on {% data variables.product.prodname_classroom %}. Teachers can create a roster by entering a list of student identifiers, or by connecting {% data variables.product.prodname_classroom %} to a learning management system (LMS). For more information about identifiers, see the definition of "[identifier](#identifier)." For more information about connecting {% data variables.product.prodname_classroom %} to an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + +--- + +### 더 읽을거리 + +- "[{% data variables.product.prodname_dotcom %} glossary](/github/getting-started-with-github/github-glossary)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/index.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/index.md new file mode 100644 index 0000000000..f5a8689fa7 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/index.md @@ -0,0 +1,32 @@ +--- +title: Manage coursework with GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %}' +intro: With {% data variables.product.prodname_classroom %}, you can use {% data variables.product.product_name %} to administer or participate in a course about software development. +versions: + free-pro-team: '*' +--- + +### Table of Contents + +{% topic_link_in_list /get-started-with-github-classroom %} + {% link_in_list /basics-of-setting-up-github-classroom %} + {% link_in_list /glossary %} + +{% topic_link_in_list /teach-with-github-classroom %} + {% link_in_list /manage-classrooms %} + {% link_in_list /create-an-individual-assignment %} + {% link_in_list /create-a-group-assignment %} + {% link_in_list /create-an-assignment-from-a-template-repository %} + {% link_in_list /leave-feedback-with-pull-requests %} + {% link_in_list /use-autograding %} + {% link_in_list /configure-default-settings-for-assignment-repositories %} + {% link_in_list /connect-a-learning-management-system-to-github-classroom %} + +{% topic_link_in_list /integrate-github-classroom-with-an-ide %} + {% link_in_list /integrate-github-classroom-with-an-online-ide %} + {% link_in_list /about-using-makecode-arcade-with-github-classroom %} + {% link_in_list /about-using-replit-with-github-classroom %} + {% link_in_list /run-student-code-in-an-online-ide %} + +{% topic_link_in_list /learn-with-github-classroom %} + {% link_in_list /view-autograding-results %} diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md new file mode 100644 index 0000000000..f4245ea672 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md @@ -0,0 +1,9 @@ +--- +title: Integrate GitHub Classroom with an IDE +shortTitle: Integrate with an IDE +intro: You can help your students write, test, and debug code by preconfiguring a development environment for assignment repositories on {% data variables.product.prodname_classroom %}. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md new file mode 100644 index 0000000000..bb4ad199ff --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md @@ -0,0 +1,42 @@ +--- +title: Integrate GitHub Classroom with an online IDE +shortTitle: Integrate with an online IDE +intro: You can preconfigure a supported online integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/online-ide-integrations +--- + +### About integration with an online IDE + +{% data reusables.classroom.about-online-ides %} + +After a student accepts an assignment with an online IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary. + +![Button for online IDE in README.md for assignment repository](/assets/images/help/classroom/assignment-repository-ide-button-in-readme.png) + +### Supported online IDEs + +{% data variables.product.prodname_classroom %} supports the following online IDEs. You can learn more about the student experience for each IDE. + +| IDE | More information | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | +| Repl.it | "[About using Repl.it with GitHub Classroom](/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom)" | + +### Configuring an online IDE for an assignment + +You can choose the online IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an online IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Authorizing the OAuth app for an online IDE + +The first time you configure an assignment with an online IDE, you must authorize the OAuth app for the online IDE for your organization. + +!["Go grant access" button in popover for authorizing OAuth app for online IDE](/assets/images/help/classroom/assignment-ide-go-grant-access-button.png) + +For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." + +### 더 읽을거리 + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md new file mode 100644 index 0000000000..bca1150346 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Learn with GitHub Classroom +intro: You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md new file mode 100644 index 0000000000..723b65c9b1 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md @@ -0,0 +1,31 @@ +--- +title: Leave feedback with pull requests +intro: You can leave feedback for your students in a special pull request within the repository for each assignment. +permissions: People with read permissions to a repository can leave feedback in a pull request for the repository. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github +--- + +### About feedback pull requests for assignments + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +When you enable the pull request for feedback for an assignment, {% data variables.product.prodname_classroom %} will create a special pull request titled **Feedback** in the assignment repository for each student or team. The pull request automatically shows every commit that a student pushed to the assignment repository's default branch. + +### 빌드전 요구 사양 + +To create and access the feedback pull request, you must enable the feedback pull request when you create the assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +### Leaving feedback in a pull request for an assignment + +{% data reusables.classroom.sign-into-github-classroom %} +1. In the list of classrooms, click the classroom with the assignment you want to review. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **Review**. ![Review button for assignment in list of submissions for an assignment](/assets/images/help/classroom/assignments-click-review-button.png) +1. Review the pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)." + +### 더 읽을거리 + +- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](http://localhost:4000/en/free-pro-team@latest/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" 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 new file mode 100644 index 0000000000..f9a64fc411 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -0,0 +1,106 @@ +--- +title: Manage classrooms +intro: You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}. +permissions: Organization owners can manage a classroom for an organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/archive-a-classroom +--- + +### About classrooms + +{% data reusables.classroom.about-classrooms %} + +![Classroom](/assets/images/help/classroom/classroom-hero.png) + +### About management of classrooms + +{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. + +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 classrom. 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)." + +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. + +### About classroom rosters + +Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course. + +When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment. + +![Classroom roster](/assets/images/help/classroom/roster-hero.png) + +### 빌드전 요구 사양 + +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 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)." + +### Creating a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **New classroom**. !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png) +{% data reusables.classroom.guide-create-new-classroom %} + +After you create a classroom, you can begin creating assignments for students. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Creating a roster for your classroom + +You can create a roster of the students who participate in your course. + +If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) +1. To create a roster manually, type your student identifiers. Optionally, click **Upload a CSV or text file** to upload a file containing the identifiers. ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png) +1. Click **Create roster**. !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png) + +### Adding students to the roster for your classroom + +Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classrom](#creating-a-roster-for-your-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To the right of "Classroom roster", click **Update students**. !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png) +1. Follow the instructions to add students to the roster. + - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**. ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) + +### Renaming a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Classroom name", type a new name for the classroom. ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png) +1. Click **Rename classroom**. !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png) + +### Archiving or unarchiving a classroom + +You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**. ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png) +1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**. ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) + +### Deleting a roster for a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Under "Delete this roster", click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png) +1. Read the warnings, then click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) + +### Deleting a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) +1. **Read the warnings**. +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md new file mode 100644 index 0000000000..57e3f1e824 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md @@ -0,0 +1,21 @@ +--- +title: Run student code in an online IDE +intro: You can run the code from a student assignment within the online integrated development environment (IDE) that you configured for the assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/running-student-code +--- + +### About student code and online IDEs + +If you configure an online integrated development environment (IDE) for an assignment, you can run the code within the online IDE. You don't need to clone the assignment repository to your computer. + +For more information about online IDEs, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +### Running student code in the online IDE + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **View IDE**. !["View IDE" button for submission using an online IDE](/assets/images/help/classroom/assignments-click-view-ide.png) diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md new file mode 100644 index 0000000000..6e051e9d2d --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Teach with GitHub Classroom +intro: Learn how to set up your classroom and assignments. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/use-autograding.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/use-autograding.md new file mode 100644 index 0000000000..2bcb0a8425 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/use-autograding.md @@ -0,0 +1,83 @@ +--- +title: Use autograding +intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers +--- + +### About autograding + +{% data reusables.classroom.about-autograding %} + +After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding. + +You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." + +You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment. + +![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png) + +### Grading methods + +There are two grading methods: input/output tests and run command tests. + +#### Input/output test + +An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result. + +| Setting | 설명 | +|:------------------- |:------------------------------------------------------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate standard output for evaluation | +| **Inputs** | Standard input for run command | +| **Expected output** | The output that you want to see as standard output from the run command | +| **Comparison** | The type of comparison between the run command's output and the expected output

      • **Included**: Passes when the expected output appears
        anywhere in the standard output from the run command
      • **Exact**: Passes when the expected output is completely identical
        to the standard output from the run command
      • **Regex**: Passes if the regular expression in expected
        output matches against the standard output from the run command
      | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +#### Run command test + +A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure. + +{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`. + +| Setting | 설명 | +|:----------------- |:------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate an exit code for evaluation | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +### Configuring autograding tests for an assignment + +You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests. + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.assignments-click-pencil %} +1. In the left sidebar, click **Grading and feedback**. !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) +1. Add, edit, or delete an autograding test. + - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png) +1. At the bottom of the page, click **Update assignment**. !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png) + +### Viewing logs from autograding tests + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of a submission, click **View test**. !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png) +1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)." + +### 더 읽을거리 + +- [{% data variables.product.prodname_actions %} documentation](/actions) diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/view-autograding-results.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/view-autograding-results.md new file mode 100644 index 0000000000..64a446c0a4 --- /dev/null +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/view-autograding-results.md @@ -0,0 +1,30 @@ +--- +title: View autograding results +intro: You can see results from autograding within the repository for your assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students +--- + +### About autograding + +Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.product.product_location %}. + +If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X. + +### Viewing autograding results for an assignment repository + +{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." + +The **Actions** tab shows the full history of test runs. + +!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png) + +You can click a specific test run to review log output, like compilation errors and test failures. + +![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) + +### 더 읽을거리 + +- "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/ko-KR/content/education/quickstart.md b/translations/ko-KR/content/education/quickstart.md new file mode 100644 index 0000000000..f7adf64233 --- /dev/null +++ b/translations/ko-KR/content/education/quickstart.md @@ -0,0 +1,87 @@ +--- +title: Quickstart for GitHub Educators +intro: In about 15 minutes, teachers can get started with discounts, training, and tools for {% data variables.product.company_short %}, then create a classroom for the students in a software development course using {% data variables.product.prodname_classroom %}. +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +### Introduction + +Educators who teach a course on software development can use discounts, partnerships, training, and tools from {% data variables.product.prodname_education %} to effectively teach relevant skills to students. + +In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}. + +{% tip %} + +**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Applying for a student developer pack](/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack)." + +{% endtip %} + +### Creating accounts on {% data variables.product.product_name %} + +First, you'll need to create a free user account on {% data variables.product.product_name %}. + +{% data reusables.accounts.create-account %} +1. Follow the prompts to create your free user account. + +After you create your user account, create a free organization account. You'll use this organization account to create and manage classrooms {% data variables.product.prodname_classroom %}. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Follow the prompts to create a free organization. + +For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." + +### Applying for an educator discount + +Next, you'll sign up for discounts on services from {% data variables.product.company_short %}. {% data reusables.education.educator-requirements %} + +{% tip %} + +**Tip** In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website. + +{% endtip %} + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Set up {% data variables.product.prodname_classroom %} + +With your user account and organization account, you're ready to get started with {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %} is free to use. You can track and manage assignments, grade work automatically, and provide feedback to your students. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To authorize {% data variables.product.prodname_classroom %} to access your user account on {% data variables.product.prodname_dotcom %}, review the information, then click **Authorize {% data variables.product.prodname_classroom %}**. !["Authorize {% data variables.product.prodname_classroom %}" button for user account](/assets/images/help/classroom/setup-click-authorize-github-classroom.png) +1. Review the information. To authorize {% data variables.product.prodname_classroom %} to access your organization account on {% data variables.product.prodname_dotcom %}, click **Grant**. !["Grant" button for organization](/assets/images/help/classroom/setup-click-grant.png) + + {% tip %} + + **Tip**: If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps#oauth-apps-and-organizations)." + + {% endtip %} + +1. Click **Authorize github**. ![Click "Authorize" button for organization](/assets/images/help/classroom/setup-click-authorize-github.png) + +### Create your classroom + +{% data reusables.classroom.about-classrooms %} + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **Create your first classroom** or **New classroom**. +{% data reusables.classroom.guide-create-new-classroom %} + +### 다음 단계 + +You've created a classroom, and you're ready to enrich your course with {% data variables.product.product_name %} and {% data variables.product.prodname_classroom %}! 🎉 + +- Watch some videos about {% data variables.product.prodname_classroom %}. For more information, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." +- Manage your classrooms and classroom admins, and create a roster of students for your classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." +- Create an assignment for individual students or teams. {% data reusables.classroom.for-more-information-about-assignment-creation %} +- Write and implement automated tests to provide immediate feedback to students directly in assignment repositories. For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." +- Participate in {% data variables.product.prodname_education_community_with_url %}. diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-campus-advisors.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..4bc9c6fd0c --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-campus-advisors.md @@ -0,0 +1,17 @@ +--- +title: About Campus Advisors +intro: 'As an instructor or mentor, learn to use {% data variables.product.prodname_dotcom %} at your school with Campus Advisors training and support.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +Professors, teachers and mentors can use the Campus Advisors online training to master Git and {% data variables.product.prodname_dotcom %} and learn best practices for teaching students with {% data variables.product.prodname_dotcom %}. For more information, see "[Campus Advisors](https://education.github.com/teachers/advisors)." + +{% note %} + +**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 %} diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-campus-experts.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..9bda70a042 --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-campus-experts.md @@ -0,0 +1,11 @@ +--- +title: About Campus Experts +intro: 'As a student, learn the skills you need to build your school''s technology community and a real-world portfolio, with {% data variables.product.prodname_dotcom %} Campus Experts training.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +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)." diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..2bfba742c6 --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,31 @@ +--- +title: About GitHub Education for educators and researchers +intro: '{% data variables.product.prodname_education %} offers a variety of tools to help educators and researchers work more effectively inside and outside of the classroom.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} for educators + +With {% data variables.product.prodname_education %}'s tools and services for educators of all levels, you can: + - Use [{% data variables.product.prodname_classroom %}](https://classroom.github.com) to distribute code, give students feedback, and collect assignments on {% data variables.product.prodname_dotcom %}. + - Join our [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) to discuss current trends in technology education with your peers from around the world. + - Access and adapt our [open source lesson plans](https://education.github.community/t/open-source-lesson-plans/1591) for teaching Git and {% data variables.product.prodname_dotcom %}. + - [Request a {% data variables.product.prodname_dotcom %} swag bag](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) with educational materials and goodies for your students. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} for researchers + +With {% data variables.product.prodname_education %}'s tools and services for researchers, you can: + - Collaborate with others on your research work around the world on {% data variables.product.prodname_dotcom %}. + - [Learn](https://education.github.com/stories) how academic institutions around the world are using {% data variables.product.prodname_dotcom %} for their research. + {% data reusables.education.apply-for-team %} + +### 더 읽을거리 + +- "[About {% data variables.product.prodname_education %} for students](/articles/about-github-education-for-students)" diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..c237913434 --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md @@ -0,0 +1,21 @@ +--- +title: About GitHub Education for students +intro: '{% data variables.product.prodname_education %} offers students real-world experience with free access to various developer tools from {% data variables.product.prodname_dotcom %}''s partners.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Using {% data variables.product.prodname_dotcom %} for your school projects is a practical way to collaborate with others and build a portfolio that showcases real-world experience. + +{% data reusables.education.about-github-education-link %} + +Everyone with a {% data variables.product.prodname_dotcom %} account can collaborate in unlimited public and private repositories with {% data variables.product.prodname_free_user %}. As a student, you can also apply for the {% data variables.product.prodname_student_pack %}, which offers free access to tools and services used by professional developers. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +If you're a member of a FIRST robotics club, your mentor can apply for an educator discount so your team can collaborate using {% data variables.product.prodname_team %}, which allows unlimited users and private repositories, for free. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." + +### 더 읽을거리 + +- "[About {% data variables.product.prodname_education %} for educators and researchers](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education.md new file mode 100644 index 0000000000..e02c546320 --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/about-github-education.md @@ -0,0 +1,23 @@ +--- +title: About GitHub Education +intro: '{% data variables.product.prodname_education %} offers a special free product for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community and agree to specific program requirements.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +If your school agrees to meet certain requirements, your secondary school, university, or bootcamp can get {% data variables.product.prodname_education %}, which offers the best of {% data variables.product.prodname_dotcom %} for free, including: +- {% data variables.product.prodname_ghe_cloud %} and/or {% data variables.product.prodname_ghe_server %} +- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our Campus Advisor program +- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %} +- Leadership development and technical training for students with the Campus Experts program + +For more information, see the [official {% data variables.product.prodname_education %}](https://education.github.com/partners/schools) page. + +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)." + +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)." + +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_education %} 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/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..be796f414d --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,53 @@ +--- +title: Apply for a student developer pack +intro: 'As a student, you can apply for the {% data variables.product.prodname_student_pack %}, which includes offers and benefits from {% data variables.product.prodname_dotcom %} partners.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 요구 사항 + +To be eligible for the {% data variables.product.prodname_student_pack %}, you must: +- Be currently enrolled in a degree or diploma granting course of study such as a high school, secondary school, college, university, homeschool, or similar educational institution +- Have a verifiable school-issued email address or upload documents that prove your current student status +- Have a [{% data variables.product.prodname_dotcom %} user account](/articles/signing-up-for-a-new-github-account) +- Be at least 13 years old + +Documents that prove your current student status include a picture of your school ID, class schedule, transcript, and affiliation or enrollment verification letter. + +During your tenure as a student, you may be prompted to periodically re-verify your current academic status. + +{% note %} + +**Note:** You cannot transfer academic discounts from one account to another. If you have more than one account you want to apply the discount to, consider [merging](/articles/merging-multiple-user-accounts) your user accounts and [renaming](/articles/changing-your-github-username) the retained account if desired. + +{% endnote %} + +For information about renewing your {% data variables.product.prodname_student_pack %}, see "[Expiration and renewals](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)." + +### Applying for a {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. Under "Which best describes your academic status?", select **Student**. ![Select academic status](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Expiration and renewals + +Once your {% data variables.product.prodname_student_pack %} access expires, you may reapply if you're still eligible, although some of our partner offers cannot renew. Most of the timed offers from our partners start once you set them up. For more information, see the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) page. + +To see when your free access to the {% data variables.product.prodname_student_pack %} expires, visit your account's [billing settings](https://github.com/settings/billing). + +### 더 읽을거리 + +- "[Why wasn't my application for a {% data variables.product.prodname_student_pack %} approved?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..367d1dbb0a --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,57 @@ +--- +title: Apply for an educator or researcher discount +intro: 'If you''re an educator or a researcher, you can apply to receive {% data variables.product.prodname_team %} for your organization account for free.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### About educator and researcher discounts + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### Applying for an educator or researcher discount + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Upgrading your organization + +After your request for an educator or researcher discount has been approved, you can upgrade the organizations you use with your learning community to {% data variables.product.prodname_team %}, which allows unlimited users and private repositories with full features, for free. You can upgrade an existing organization or create a new organization to upgrade. + +#### Upgrading an existing organization + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Upgrading a new organization + +{% data reusables.education.upgrade-page %} +1. Click {% octicon "plus" aria-label="The plus symbol" %} **Create an organization**. ![Create an organization button](/assets/images/help/education/create-org-button.png) +3. Read the information, then click **Create organization**. ![Create organization button](/assets/images/help/education/create-organization-button.png) +4. Under "Choose your plan", click **Choose {% data variables.product.prodname_free_team %}**. +5. Follow the prompts to create your organization. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### 더 읽을거리 + +- "[Why wasn't my application for an educator or researcher discount approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %} Videos](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/index.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/index.md new file mode 100644 index 0000000000..fa8223b8ed --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Teach and learn +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Table of Contents + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..6fc2cf9659 --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,11 @@ +--- +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 +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..9419a99fef --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,11 @@ +--- +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 +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..fb952f6a09 --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,11 @@ +--- +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 +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..8cc02628d8 --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,67 @@ +--- +title: Why wasn't my application for a student developer pack approved? +intro: 'Review common reasons that applications for the {% data variables.product.prodname_student_pack %} are not approved and learn tips for reapplying successfully.' +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved + - /articles/why-was-my-application-for-a-student-developer-pack-denied/ + - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved + - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tip:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unclear academic affiliation documents + +If the image you uploaded doesn't clearly identify your current academic status, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Using an academic email with an unverified domain + +If your academic email address has an unverified domain, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Using an academic email from a school with lax email policies + +If your school issues email addresses prior to paid student enrollment, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +If you have other questions or concerns about the school domain please ask your school IT staff to contact us. + +### Academic email address already used + +If your academic email address was already used to request a {% data variables.product.prodname_student_pack %} for a different {% data variables.product.prodname_dotcom %} account, you cannot reuse the academic email address to successfully apply for another {% data variables.product.prodname_student_pack %} until that discount expires. + +{% note %} + +**Note:** It is against the {% data variables.product.prodname_dotcom %} [Terms of Service](/articles/github-terms-of-service/#3-account-requirements) to maintain more than one individual account. + +{% endnote %} + +If you have more than one personal user account, you must merge your accounts. To retain the discount, keep the account that was granted the discount. You can rename the retained account and keep your contribution history by adding all your email addresses to the retained account. + +For more information, see: +- "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)" +- "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)" +- "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account)" + +### 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 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). + +### 더 읽을거리 + +- "[How to get the GitHub Student Developer Pack without a student ID](https://github.blog/2019-07-30-how-to-get-the-github-student-developer-pack-without-a-student-id/)" on {% data variables.product.prodname_blog %} +- "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/ko-KR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/ko-KR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..6ec7d5bfec --- /dev/null +++ b/translations/ko-KR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,45 @@ +--- +title: Why wasn't my application for an educator or researcher discount approved? +intro: Review common reasons that applications for an educator or researcher discount are not approved and learn tips for reapplying successfully. +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tip:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unclear proof of affiliation documents + +If the image you uploaded doesn't clearly identify your current employment with a school or university, you must reapply and upload another image of your faculty ID or employment verification letter with clear information. + +{% data reusables.education.pdf-support %} + +### Using an academic email with an unverified domain + +If your academic email address has an unverified domain, we may require further proof of your academic status. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Using an academic email from a school with lax email policies + +If alumni and retired faculty of your school have lifetime access to school-issued email addresses, we may require further proof of your academic status. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +If you have other questions or concerns about the school domain, please ask your school IT staff to contact us. + +### Non-student applying for Student Developer Pack + +Educators and researchers are not eligible for the partner offers that come with the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). When you reapply, make sure that you choose **Faculty** to describe your academic status. + +### 더 읽을거리 + +- "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md index a49e5c06ec..b792b6c4a3 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -32,14 +32,14 @@ If you've enabled security updates, you'll sometimes see extra pull requests for ### Supported repositories and ecosystems +You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)." + {% note %} -{% data reusables.dependabot.private-dependencies %} +{% 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. See the details in the table below. {% endnote %} -You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)." - {% data reusables.dependabot.supported-package-managers %} If your repository already uses an integration for dependency management, you will need to disable this before enabling {% data variables.product.prodname_dependabot %}. For more information, see "[About integrations](/github/customizing-your-github-workflow/about-integrations)." diff --git a/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md b/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md index 32380d4d97..013bb9b8bf 100644 --- a/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/ko-KR/content/github/administering-a-repository/about-secret-scanning.md @@ -36,6 +36,7 @@ When {% data variables.product.prodname_secret_scanning %} detects a set of cred - Databricks - Datadog - Discord +- Doppler - Dropbox - Dynatrace - Finicity @@ -79,6 +80,8 @@ When {% data variables.product.prodname_secret_scanning %} detects a secret in a Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." + {% data variables.product.product_name %} currently scans private repositories for secrets issued by the following service providers. - Adafruit @@ -90,6 +93,7 @@ Repository administrators and organization owners can grant users and team acces - CloudBees CodeShip - Databricks - Discord +- Doppler - Dropbox - Dynatrace - Finicity diff --git a/translations/ko-KR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/ko-KR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index 7b3ccfce08..9fe65cea78 100644 --- a/translations/ko-KR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/ko-KR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -302,13 +302,14 @@ updates: - dependency-name: "express" # For Express, ignore all updates for version 4 and 5 versions: ["4.x", "5.x"] - # For Loadash, ignore all updates - - dependency-name: "loadash" + # For Lodash, ignore all updates + - dependency-name: "lodash" ``` {% note %} -**Note**: {% data variables.product.prodname_dependabot_version_updates %} can't run version updates for any dependencies in manifests containing private git dependencies or private git registries, even if you add the private dependencies to the `ignore` option of your configuration file. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot#supported-repositories-and-ecosystems)." +**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-repositories)" 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/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/ko-KR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md index 5604b5f003..a2732f9641 100644 --- a/translations/ko-KR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md +++ b/translations/ko-KR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -14,14 +14,10 @@ You enable {% data variables.product.prodname_dependabot_version_updates %} by c {% data reusables.dependabot.initial-updates %} For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)." +{% 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)." + ### Enabling {% data variables.product.prodname_dependabot_version_updates %} -{% note %} - -{% data reusables.dependabot.private-dependencies %} - -{% endnote %} - {% data reusables.dependabot.create-dependabot-yml %} 1. Use `package-ecosystem` to specify the package managers to monitor. 1. For each package manager, use: diff --git a/translations/ko-KR/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/ko-KR/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md new file mode 100644 index 0000000000..a5fc92c5be --- /dev/null +++ b/translations/ko-KR/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -0,0 +1,20 @@ +--- +title: Enabling or disabling GitHub Discussions for a repository +intro: 'You can use discussions in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.' +product: '{% data reusables.gated-features.discussions %}' +permissions: People with admin permissions to a repository can enable discussions for the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Enabling or disabling discussions for your repository + +{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} +1. To disable discussions, under "Features", unselect **Discussions**. + +### 더 읽을거리 + +- "[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/github/administering-a-repository/index.md b/translations/ko-KR/content/github/administering-a-repository/index.md index 4d9e27630d..e3831cad21 100644 --- a/translations/ko-KR/content/github/administering-a-repository/index.md +++ b/translations/ko-KR/content/github/administering-a-repository/index.md @@ -12,36 +12,25 @@ versions: ### Table of Contents {% topic_link_in_list /managing-repository-settings %} - {% link_in_list /setting-repository-visibility %}{% if currentVersion == "free-pro-team@latest" %} - {% link_in_list /managing-teams-and-people-with-access-to-your-repository %}{% endif %} + {% link_in_list /setting-repository-visibility %} + {% link_in_list /managing-teams-and-people-with-access-to-your-repository %} {% link_in_list /classifying-your-repository-with-topics %} {% link_in_list /customizing-how-changed-files-appear-on-github %} {% link_in_list /about-email-notifications-for-pushes-to-your-repository %} - {% link_in_list /displaying-a-sponsor-button-in-your-repository %} - - {% link_in_list /customizing-your-repositorys-social-media-preview %} - - {% link_in_list /viewing-deployment-activity-for-your-repository %} - {% link_in_list /managing-the-forking-policy-for-your-repository %} - {% link_in_list /setting-the-default-branch %} - {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %} + {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /enabling-or-disabling-github-discussions-for-a-repository %}{% endif %} {% link_in_list /managing-git-lfs-objects-in-archives-of-your-repository %} {% link_in_list /enabling-anonymous-git-read-access-for-a-repository %} - - {% link_in_list /configuring-autolinks-to-reference-external-resources %} - {% link_in_list /renaming-a-repository %} {% link_in_list /transferring-a-repository %} {% link_in_list /deleting-a-repository %} - {% link_in_list /restoring-a-deleted-repository %} - {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} {% link_in_list /changing-the-default-branch %} @@ -50,9 +39,7 @@ versions: {% link_in_list /about-merge-methods-on-github %} {% link_in_list /configuring-commit-squashing-for-pull-requests %} {% link_in_list /configuring-commit-rebasing-for-pull-requests %} - {% link_in_list /managing-the-automatic-deletion-of-branches %} - {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} {% link_in_list /configuring-protected-branches %} @@ -65,31 +52,22 @@ versions: {% link_in_list /enabling-required-reviews-for-pull-requests %} {% link_in_list /about-required-commit-signing %} {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} {% link_in_list /enabling-force-pushes-to-a-protected-branch %} {% link_in_list /enabling-deletion-of-a-protected-branch %} - {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} {% link_in_list /viewing-your-repositorys-releases-and-tags %} {% link_in_list /linking-to-releases %} - {% link_in_list /comparing-releases %} - - {% link_in_list /automation-for-release-forms-with-query-parameters %} - - {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} {% link_in_list /configuring-secret-scanning-for-private-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} - - {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} {% link_in_list /about-dependabot-version-updates %} {% link_in_list /enabling-and-disabling-version-updates %} @@ -98,4 +76,3 @@ versions: {% link_in_list /customizing-dependency-updates %} {% link_in_list /configuration-options-for-dependency-updates %} {% link_in_list /keeping-your-actions-up-to-date-with-dependabot %} - diff --git a/translations/ko-KR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/ko-KR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md index bb6a205408..9d5a08987c 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/ko-KR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -19,9 +19,9 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc {% mac %} -1. Copy the SSH key to your clipboard. +1. Copy the SSH public key to your clipboard. - If your SSH key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ pbcopy < ~/.ssh/id_ed25519.pub @@ -46,9 +46,9 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc {% windows %} -1. Copy the SSH key to your clipboard. +1. Copy the SSH public key to your clipboard. - If your SSH key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ clip < ~/.ssh/id_ed25519.pub @@ -73,9 +73,9 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc {% linux %} -1. Copy the SSH key to your clipboard. +1. Copy the SSH public key to your clipboard. - If your SSH key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ sudo apt-get install xclip 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 d1cded972a..c13e5b2385 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 @@ -9,7 +9,7 @@ versions: enterprise-server: '*' --- -You must choose or generate a password for your {% data variables.product.product_name %} account that is: +You must choose or generate a password for your {% data variables.product.product_name %} account that is at least: - Eight characters long, if it includes a number and a lowercase letter, or - 16 characters long with any combination of characters diff --git a/translations/ko-KR/content/github/authenticating-to-github/index.md b/translations/ko-KR/content/github/authenticating-to-github/index.md index 1ea2f31cb2..30e51c7087 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/index.md +++ b/translations/ko-KR/content/github/authenticating-to-github/index.md @@ -35,11 +35,9 @@ versions: {% link_in_list /reviewing-your-authorized-applications-oauth %} {% link_in_list /reviewing-your-security-log %} {% link_in_list /removing-sensitive-data-from-a-repository %} - {% link_in_list /about-anonymized-image-urls %} {% link_in_list /about-githubs-ip-addresses %} {% link_in_list /githubs-ssh-key-fingerprints %} - {% link_in_list /sudo-mode %} {% link_in_list /preventing-unauthorized-access %} {% topic_link_in_list /securing-your-account-with-two-factor-authentication-2fa %} @@ -48,18 +46,14 @@ versions: {% link_in_list /configuring-two-factor-authentication-recovery-methods %} {% link_in_list /accessing-github-using-two-factor-authentication %} {% link_in_list /recovering-your-account-if-you-lose-your-2fa-credentials %} - {% link_in_list /changing-two-factor-authentication-delivery-methods-for-your-mobile-device %} {% link_in_list /countries-where-sms-authentication-is-supported %} - {% link_in_list /disabling-two-factor-authentication-for-your-personal-account %} - {% topic_link_in_list /authenticating-with-saml-single-sign-on %} {% link_in_list /about-authentication-with-saml-single-sign-on %} {% link_in_list /authorizing-an-ssh-key-for-use-with-saml-single-sign-on %} {% link_in_list /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-your-active-saml-sessions %} - {% topic_link_in_list /connecting-to-github-with-ssh %} {% link_in_list /about-ssh %} {% link_in_list /checking-for-existing-ssh-keys %} @@ -68,13 +62,9 @@ versions: {% link_in_list /testing-your-ssh-connection %} {% link_in_list /working-with-ssh-key-passphrases %} {% topic_link_in_list /troubleshooting-ssh %} - {% link_in_list /using-ssh-over-the-https-port %} - {% link_in_list /recovering-your-ssh-key-passphrase %} - {% link_in_list /deleted-or-missing-ssh-keys %} - {% link_in_list /error-permission-denied-publickey %} {% link_in_list /error-bad-file-number %} {% link_in_list /error-key-already-in-use %} @@ -82,9 +72,7 @@ versions: {% link_in_list /error-permission-to-userrepo-denied-to-userother-repo %} {% link_in_list /error-agent-admitted-failure-to-sign %} {% link_in_list /error-ssh-add-illegal-option----k %} - {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %} - {% link_in_list /error-were-doing-an-ssh-key-audit %} {% topic_link_in_list /managing-commit-signature-verification %} {% link_in_list /about-commit-signature-verification %} diff --git a/translations/ko-KR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/ko-KR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index b1066affe4..2e1120963c 100644 --- a/translations/ko-KR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/ko-KR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -40,6 +40,12 @@ To replace all text listed in `passwords.txt` wherever it can be found in your r $ bfg --replace-text passwords.txt ``` +After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. + +```shell +$ git push --force +``` + See the [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. #### Using filter-branch 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 aa13e68ecd..ec31f9eaff 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 @@ -176,7 +176,7 @@ An overview of some of the most common actions that are recorded as events in th | `repo_funding_link_button_toggle` | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") | -| `sponsor_sponsorship_create` | Triggered when you sponsor a developer (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor#sponsoring-a-developer)") | +| `sponsor_sponsorship_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)") | diff --git a/translations/ko-KR/content/github/building-a-strong-community/index.md b/translations/ko-KR/content/github/building-a-strong-community/index.md index 854d6d0950..70d3a13506 100644 --- a/translations/ko-KR/content/github/building-a-strong-community/index.md +++ b/translations/ko-KR/content/github/building-a-strong-community/index.md @@ -13,21 +13,15 @@ versions: ### Table of Contents {% topic_link_in_list /setting-up-your-project-for-healthy-contributions %} - {% link_in_list /about-community-management-and-moderation %} {% link_in_list /about-community-profiles-for-public-repositories %} {% link_in_list /accessing-a-projects-community-profile %} {% link_in_list /adding-a-code-of-conduct-to-your-project %} - {% link_in_list /setting-guidelines-for-repository-contributors %} {% link_in_list /adding-a-license-to-a-repository %} {% link_in_list /adding-support-resources-to-your-project %} - {% link_in_list /creating-a-default-community-health-file %} - - {% link_in_list /encouraging-helpful-contributions-to-your-project-with-labels %} - {% topic_link_in_list /using-templates-to-encourage-useful-issues-and-pull-requests %} {% link_in_list /about-issue-and-pull-request-templates %} {% link_in_list /configuring-issue-templates-for-your-repository %} @@ -42,7 +36,6 @@ versions: {% link_in_list /tracking-changes-in-a-comment %} {% link_in_list /managing-how-contributors-report-abuse-in-your-organizations-repository %} {% link_in_list /managing-reported-content-in-your-organizations-repository %} - {% topic_link_in_list /maintaining-your-safety-on-github %} {% link_in_list /blocking-a-user-from-your-personal-account %} {% link_in_list /viewing-users-youve-blocked-from-your-personal-account %} @@ -51,7 +44,6 @@ versions: {% link_in_list /viewing-users-who-are-blocked-from-your-organization %} {% link_in_list /unblocking-a-user-from-your-organization %} {% link_in_list /reporting-abuse-or-spam %} - {% topic_link_in_list /documenting-your-project-with-wikis %} {% link_in_list /about-wikis %} {% link_in_list /adding-or-editing-wiki-pages %} @@ -60,10 +52,8 @@ versions: {% link_in_list /viewing-a-wikis-history-of-changes %} {% link_in_list /changing-access-permissions-for-wikis %} {% link_in_list /disabling-wikis %} - {% topic_link_in_list /collaborating-with-your-team %} {% link_in_list /about-team-discussions %} {% link_in_list /creating-a-team-discussion %} {% link_in_list /editing-or-deleting-a-team-discussion %} {% link_in_list /pinning-a-team-discussion %} - diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md index 9114a58b66..30fb120449 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -22,7 +22,11 @@ versions: {% data reusables.pull_requests.automatically-delete-branches %} -If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." +{% note %} + +**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." + +{% endnote %} If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)" or "[Closing a pull request](/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request)." diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/index.md index fe2b997f77..ae4915c002 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/index.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/index.md @@ -29,9 +29,7 @@ versions: {% link_in_list /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility %} {% topic_link_in_list /collaborating-on-repositories-with-code-quality-features %} {% link_in_list /about-status-checks %} - {% link_in_list /working-with-pre-receive-hooks %} - {% topic_link_in_list /proposing-changes-to-your-work-with-pull-requests %} {% link_in_list /about-branches %} {% link_in_list /creating-and-deleting-branches-within-your-repository %} @@ -39,9 +37,7 @@ versions: {% link_in_list /about-comparing-branches-in-pull-requests %} {% link_in_list /creating-a-pull-request %} {% link_in_list /creating-a-pull-request-from-a-fork %} - {% link_in_list /changing-the-stage-of-a-pull-request %} - {% link_in_list /requesting-a-pull-request-review %} {% link_in_list /changing-the-base-branch-of-a-pull-request %} {% link_in_list /committing-changes-to-a-pull-request-branch-created-from-a-fork %} @@ -52,15 +48,12 @@ versions: {% topic_link_in_list /reviewing-changes-in-pull-requests %} {% link_in_list /about-pull-request-reviews %} {% link_in_list /reviewing-proposed-changes-in-a-pull-request %} - {% link_in_list /filtering-files-in-a-pull-request %} - {% link_in_list /finding-changed-methods-and-functions-in-a-pull-request %} {% link_in_list /commenting-on-a-pull-request %} {% link_in_list /viewing-a-pull-request-review %} - + {% link_in_list /reviewing-dependency-changes-in-a-pull-request %} {% link_in_list /incorporating-feedback-in-your-pull-request %} - {% link_in_list /approving-a-pull-request-with-required-reviews %} {% link_in_list /dismissing-a-pull-request-review %} {% link_in_list /checking-out-pull-requests-locally %} diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md new file mode 100644 index 0000000000..308d7f0f33 --- /dev/null +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -0,0 +1,74 @@ +--- +title: Reviewing dependency changes in a pull request +intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Dependency review is currently in beta and subject to change. + +{% endnote %} + +### About dependency review + +If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. + +Dependency review is available in: + +* All public repositories. +* Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[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)." + +Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. + +By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. {% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix them at some later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)." + +Dependency review supports the same languages and package management ecosystems as the dependency graph. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." + +### Reviewing dependencies in a pull request + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} + +1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. + + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + + {% note %} + + **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% endnote %} + +1. Check the dependencies listed in the dependency review. + + ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) + + Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name. + + The icon beside each dependency indicates whether the dependency has been added ({% octicon "diff-added" aria-label="Dependency added icon" %}), updated ({% octicon "diff-modified" aria-label="Dependency modified icon" %}), or removed ({% octicon "diff-removed" aria-label="Dependency removed icon" %}) in this pull request. + + Other information includes: + + * The version, or version range, of the new, updated, or deleted dependency. + * For a specific version of a dependency: + * The age of that release of the dependency. + * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency. + * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project. + + Where a dependency has a known vulnerability, the warning message includes: + + * A brief description of the vulnerability. + * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability. + * The severity of the vulnerability. + * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. + +1. You can return to the original view of the file by clicking the source diff button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 0ba9a59060..ed9d6ec646 100644 --- a/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -29,6 +29,18 @@ Before you submit your review, your line comments are _pending_ and only visible ![Cancel review button](/assets/images/help/pull_requests/cancel-review-button.png) +{% if currentVersion == "free-pro-team@latest" %} +### Reviewing dependency changes + +If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. 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 reusables.repositories.changed-files %} + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) +{% endif %} + ### Marking a file as viewed After you finish reviewing a file, you can mark the file as viewed, and the file will collapse. If the file changes after you view the file, it will be unmarked as viewed. @@ -53,8 +65,5 @@ After you've finished reviewing all the files you want in the pull request, subm ### 더 읽을거리 -- "[About pull request reviews](/articles/about-pull-request-reviews)" -- "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" -- "[Approving a pull request with required reviews](/articles/approving-a-pull-request-with-required-reviews)" -- "[Commenting on a pull request](/articles/commenting-on-a-pull-request)" -- "[Filtering pull requests by review status](/articles/filtering-pull-requests-by-review-status)" +- "[About required reviews for pull requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[Filtering pull requests by review status](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/ko-KR/content/github/committing-changes-to-your-project/index.md b/translations/ko-KR/content/github/committing-changes-to-your-project/index.md index 6a0d69b0c6..d08959632a 100644 --- a/translations/ko-KR/content/github/committing-changes-to-your-project/index.md +++ b/translations/ko-KR/content/github/committing-changes-to-your-project/index.md @@ -16,9 +16,7 @@ versions: {% topic_link_in_list /creating-and-editing-commits %} {% link_in_list /about-commits %} {% link_in_list /creating-a-commit-with-multiple-authors %} - {% link_in_list /creating-a-commit-on-behalf-of-an-organization %} - {% link_in_list /changing-a-commit-message %} {% topic_link_in_list /viewing-and-comparing-commits %} {% link_in_list /commit-branch-and-tag-labels %} 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 e3e1dd5f8a..2879205076 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 @@ -40,9 +40,9 @@ For code owners to receive review requests, the CODEOWNERS file must be on the b ### CODEOWNERS syntax -A CODEOWNERS file uses a pattern that follows the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files. The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. You can also refer to a user by an email address that has been added to their {% data variables.product.product_name %} account, for example `user@example.com`. +A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. You can also refer to a user by an email address that has been added to their {% data variables.product.product_name %} account, for example `user@example.com`. -If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. Invalid syntax includes inline comments and user or team names that do not exist on {% data variables.product.product_name %}. +If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. #### Example of a CODEOWNERS file ``` # This is a comment. @@ -84,6 +84,13 @@ apps/ @octocat # subdirectories. /docs/ @doctocat ``` +#### Syntax exceptions +There are some syntax rules for gitignore files that do not work in CODEOWNERS files: +- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment +- Using `!` to negate a pattern +- Using `[ ]` to define a character range + + ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index c2f5ec223e..00fb2c63f3 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -1,6 +1,6 @@ --- title: About repositories -intro: A repository is like a folder for your project. Your project's repository contains all of your project's files and stores each file's revision history. You can also discuss and manage your project's work within the repository. +intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository. redirect_from: - /articles/about-repositories versions: @@ -22,9 +22,11 @@ With Each person and organization can own unlimited repositories and invite an unlimited number of collaborators to all repositories. {% endif %} -You can collaborate on your project with others using your repository's issues, pull requests, and project boards. - -![Main page of the octocat/Hello-World repository](/assets/images/help/repository/repo-main-page.png) +You can use repositories to manage your work and collaborate with others. +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)." +- {% data reusables.discussions.you-can-use-discussions %} +- You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." +- You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)." {% data reusables.repositories.repo-size-limit %} diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md index 3dfc5d732a..9848b72fff 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md @@ -45,16 +45,16 @@ You can find the URL of the local repository by opening the command line and typ ```shell $ git remote -v # View existing remotes -> origin https://github.com/github/reactivecocoa.git (fetch) -> origin https://github.com/github/reactivecocoa.git (push) +> origin https://github.com/ghost/reactivecocoa.git (fetch) +> origin https://github.com/ghost/reactivecocoa.git (push) -$ git remote set-url origin https://github.com/github/ReactiveCocoa.git +$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git # Change the 'origin' remote's URL $ git remote -v # Verify new remote URL -> origin https://github.com/github/ReactiveCocoa.git (fetch) -> origin https://github.com/github/ReactiveCocoa.git (push) +> origin https://github.com/ghost/ReactiveCocoa.git (fetch) +> origin https://github.com/ghost/ReactiveCocoa.git (push) ``` Alternatively, you can change the URL through our [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) application. diff --git a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/index.md index c3f6d3e54d..d590e22a92 100644 --- a/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/index.md +++ b/translations/ko-KR/content/github/creating-cloning-and-archiving-repositories/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repositories %} {% link_in_list /about-repository-visibility %} {% link_in_list /creating-a-new-repository %} - {% link_in_list /creating-a-repository-from-a-template %} - {% link_in_list /about-readmes %} {% link_in_list /about-code-owners %} {% link_in_list /about-repository-languages %} {% link_in_list /licensing-a-repository %} - {% link_in_list /creating-a-template-repository %} - {% link_in_list /creating-an-issues-only-repository %} {% link_in_list /limits-for-viewing-content-and-diffs-in-a-repository %} {% link_in_list /duplicating-a-repository %} @@ -39,8 +35,6 @@ versions: {% topic_link_in_list /archiving-a-github-repository %} {% link_in_list /about-archiving-repositories %} {% link_in_list /archiving-repositories %} - {% link_in_list /about-archiving-content-and-data-on-github %} {% link_in_list /referencing-and-citing-content %} - {% link_in_list /backing-up-a-repository %} diff --git a/translations/ko-KR/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/ko-KR/content/github/customizing-your-github-workflow/about-github-marketplace.md index f1b78903b0..0a907f0579 100644 --- a/translations/ko-KR/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/ko-KR/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -7,26 +7,27 @@ versions: free-pro-team: '*' --- -You can discover, browse, and install free and paid tools, including [{% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/), and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). +You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). If you purchase a paid tool, you'll pay for your tool subscription with the same billing information you use to pay for your {% data variables.product.product_name %} subscription, and receive one bill on your regular billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)." -You may also have the option to select a free 14-day trial on select tools. You can cancel at any time during your trial and you won't be charged, but you will automatically lose access to the tool. Your paid subscription will start at the end of the 14-day trial. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)." +You may also have the option to select a free 14-day trial on some tools. You can cancel at any time during your trial and you won't be charged, but you will automatically lose access to the tool. Your paid subscription will start at the end of the 14-day trial. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)." -{% data variables.product.prodname_github_app %}s and {% data variables.product.prodname_oauth_app %}s can be verified or unverified. Verified apps meet specific requirements set by {% data variables.product.prodname_dotcom %} and go through a security review before they are listed on {% data variables.product.prodname_marketplace %}. For more information, see "[Requirements for listing an app on GitHub Marketplace](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." +### Finding tools on {% data variables.product.prodname_marketplace %} -### {% data variables.product.prodname_actions %} on {% data variables.product.prodname_marketplace %} +You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." -You can discover, browse, and install {% data variables.product.prodname_actions %} created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +{% data reusables.actions.actions-not-verified %} -Anyone can list an action on {% data variables.product.prodname_marketplace %}. Unlike some apps, {% data variables.product.prodname_actions %} listed on {% data variables.product.prodname_marketplace %} are never verified by {% data variables.product.prodname_dotcom %}. +Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About verified creators](/developers/github-marketplace/about-verified-creators)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### Building and listing a tool on {% data variables.product.prodname_marketplace %} -For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/apps)" and "[{% data variables.product.prodname_actions %}](/actions)." +For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/developers/apps)" and "[{% data variables.product.prodname_actions %}](/actions)." ### 더 읽을거리 - "[Purchasing and installing apps in {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" - "[Managing billing for {% data variables.product.prodname_marketplace %} apps](/articles/managing-billing-for-github-marketplace-apps)" - "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)" +- "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)" diff --git a/translations/ko-KR/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/ko-KR/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md index bae90e2db4..07781dde1b 100644 --- a/translations/ko-KR/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/ko-KR/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -15,7 +15,7 @@ versions: {% data reusables.codespaces.about-configuration %} -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes tools for Node.js, JavaScript, TypeScript, Python, C++, Java, C#, .NET Core, PHP, and PowerShell. For more information about the base Linux image, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) repository. +If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes tools for Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, PowerShell, Go, Ruby, and Rust. For more information about the base Linux image, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) repository. {% data reusables.codespaces.about-personalization %} {% data reusables.codespaces.codespace-config-order %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 9e693aff0b..877edcc652 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -181,17 +181,17 @@ jobs: - name: Install dependencies run: | python -m pip install --upgrade pip - if [ -f requirements.txt ]; + if [ -f requirements.txt ]; then pip install -r requirements.txt; fi # Set the `CODEQL-PYTHON` environment variable to the Python executable # that includes the dependencies - echo "::set-env name=CODEQL_PYTHON::$(which python)" + echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV - name: Initialize CodeQL uses: github/codeql-action/init@v1 with: languages: python - # Override the default behavior so that the action doesn't attempt + # Override the default behavior so that the action doesn't attempt # to auto-install Python dependencies setup-python-dependencies: false ``` @@ -263,8 +263,8 @@ For the interpreted languages that {% data variables.product.prodname_codeql %} ``` yaml paths: - - src -paths-ignore: + - src +paths-ignore: - src/node_modules - '**/*.test.js' ``` @@ -296,7 +296,7 @@ You can quickly analyze small portions of a monorepo when you modify code in spe 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 `github/foo`, `github/bar`, and `github/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. +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 @@ -305,9 +305,9 @@ steps: env: TOKEN: ${{ secrets.ACCESS_TOKEN }} run: | - git config --global url."https://${TOKEN}@github.com/github/foo".insteadOf "https://github.com/github/foo" - git config --global url."https://${TOKEN}@github.com/github/bar".insteadOf "https://github.com/github/bar" - git config --global url."https://${TOKEN}@github.com/github/baz".insteadOf "https://github.com/github/baz" + 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 %} diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md index d32e59c2c2..8b0021e943 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md @@ -21,7 +21,7 @@ You must run {% data variables.product.prodname_codeql %} in the same container You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations: * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* MacOS: https://github.com/actions/virtual-environments/tree/main/images/macos +* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos * Windows: https://github.com/actions/virtual-environments/tree/main/images/win ### Example workflow diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index c1f4131223..c7e1cf8ad2 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -40,7 +40,7 @@ On Linux: chmod +x codeql-runner-linux ``` -On MacOS: +macOS 의 경우 : ```shell chmod +x codeql-runner-macos diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 8e382ca4b8..3a91315ff7 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -107,13 +107,13 @@ A location within a programming artifact, such as a file in the repository or a #### `physicalLocation` object -| 이름 | 설명 | -| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `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/github/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. | +| 이름 | 설명 | +| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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. | ### SARIF output file examples diff --git a/translations/ko-KR/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/ko-KR/content/github/getting-started-with-github/git-and-github-learning-resources.md index 88204a2b3d..656411ec03 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/ko-KR/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +authors: + - GitHub --- ### Using Git diff --git a/translations/ko-KR/content/github/getting-started-with-github/github-glossary.md b/translations/ko-KR/content/github/getting-started-with-github/github-glossary.md index a2d0143dfd..fbc057510f 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/github-glossary.md +++ b/translations/ko-KR/content/github/getting-started-with-github/github-glossary.md @@ -10,8 +10,8 @@ versions: --- {% for term in site.data.glossaries.external %} - ### {{term.term}} - {{term.description}} + ### {% data glossaries.external[forloop.index0].term %} + {% data glossaries.external[forloop.index0].description %} --- {% endfor %} diff --git a/translations/ko-KR/content/github/getting-started-with-github/index.md b/translations/ko-KR/content/github/getting-started-with-github/index.md index b333ae0ca8..7616a6b80d 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/index.md +++ b/translations/ko-KR/content/github/getting-started-with-github/index.md @@ -27,37 +27,27 @@ versions: {% link_in_list /fork-a-repo %} {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} - {% link_in_list /githubs-products %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} - {% link_in_list /types-of-github-accounts %} - {% link_in_list /faq-about-changes-to-githubs-plans %} {% link_in_list /github-cli %} {% link_in_list /github-desktop %} {% link_in_list /github-for-mobile %} - {% link_in_list /access-permissions-on-github %} {% link_in_list /github-glossary %} {% link_in_list /git-cheatsheet %} {% link_in_list /git-and-github-learning-resources %} {% topic_link_in_list /signing-up-for-github %} - {% link_in_list /signing-up-for-a-new-github-account %} {% link_in_list /verifying-your-email-address %} - {% link_in_list /setting-up-a-trial-of-github-enterprise-cloud %} {% link_in_list /setting-up-a-trial-of-github-enterprise-server %} {% topic_link_in_list /exploring-projects-on-github %} - {% link_in_list /finding-ways-to-contribute-to-open-source-on-github %} - {% link_in_list /saving-repositories-with-stars %} {% link_in_list /following-people %} {% topic_link_in_list /using-github %} {% link_in_list /supported-browsers %} - {% link_in_list /troubleshooting-connectivity-problems %} - {% link_in_list /keyboard-shortcuts %} diff --git a/translations/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 893e8f37dc..b775002844 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 @@ -117,35 +117,35 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr #### Moving a column -| Keyboard shortcut | 설명 | -| -------------------------------------------------------------------------------------------- | ------------------------------------- | -| 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 | +| Keyboard shortcut | 설명 | +| ---------------------------------------------------------------------------------------------------- | ------------------------------------- | +| 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 | #### Moving a card -| Keyboard shortcut | 설명 | -| -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | -| 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 | +| Keyboard shortcut | 설명 | +| ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------- | +| 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 | #### Previewing a card @@ -156,38 +156,38 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr {% if currentVersion == "free-pro-team@latest" %} ### {% data variables.product.prodname_actions %} -| Keyboard shortcut | 설명 | -| ----------------------------------------------------- | --------------------------------------------------------------- | -| command space or control space | In the workflow editor, get suggestions for your workflow file. | +| Keyboard shortcut | 설명 | +| --------------------------------------------------------- | --------------------------------------------------------------- | +| command + space or control + space | In the workflow editor, get suggestions for your workflow file. | {% endif %} ### 알림(Notifications) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| Keyboard shortcut | 설명 | -| ------------------ | -------------- | -| e | Mark as done | -| shift u | Mark as unread | -| shift i | Mark as read | -| shift m | Unsubscribe | +| Keyboard shortcut | 설명 | +| -------------------- | -------------- | +| e | Mark as done | +| shift + u | Mark as unread | +| shift + i | Mark as read | +| shift + m | Unsubscribe | {% else %} | Keyboard shortcut | 설명 | | -------------------------------------------- | ------------ | | e or I or y | Mark as read | -| shift m | Mute thread | +| shift + m | Mute thread | {% endif %} ### 네트워크 그래프 -| Keyboard shortcut | 설명 | -| ---------------------------------------- | ------------------------ | -| ← 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 | +| Keyboard shortcut | 설명 | +| -------------------------------------------- | ------------------------ | +| ← 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 | diff --git a/translations/ko-KR/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md b/translations/ko-KR/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md index a3e314f496..3b91529770 100644 --- a/translations/ko-KR/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md +++ b/translations/ko-KR/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md @@ -1,5 +1,6 @@ --- title: Signing up for a new GitHub account +shortTitle: Sign up for a new GitHub account intro: '{% data variables.product.product_name %} offers user accounts for individuals and organizations for teams of people working together.' redirect_from: - /articles/signing-up-for-a-new-github-account @@ -9,9 +10,8 @@ versions: For more information about account types and products, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)" and "[{% data variables.product.product_name %}'s products](/articles/github-s-products)." -1. Go to {% data variables.product.product_name %}'s [Pricing]({% data variables.product.pricing_url %}) page. -2. Read the information about the different products and subscriptions that {% data variables.product.product_name %} offers, then click the upgrade button under the subscription you'd like to choose. -3. Follow the prompts to create your personal account or organization. +{% data reusables.accounts.create-account %} +1. Follow the prompts to create your personal account or organization. ### 다음 단계 diff --git a/translations/ko-KR/content/github/importing-your-projects-to-github/index.md b/translations/ko-KR/content/github/importing-your-projects-to-github/index.md index 1ebc5ad0d3..7882a47ea4 100644 --- a/translations/ko-KR/content/github/importing-your-projects-to-github/index.md +++ b/translations/ko-KR/content/github/importing-your-projects-to-github/index.md @@ -15,11 +15,9 @@ versions: ### Table of Contents {% topic_link_in_list /importing-source-code-to-github %} - {% link_in_list /about-github-importer %} {% link_in_list /importing-a-repository-with-github-importer %} {% link_in_list /updating-commit-author-attribution-with-github-importer %} - {% link_in_list /importing-a-git-repository-using-the-command-line %} {% link_in_list /adding-an-existing-project-to-github-using-the-command-line %} {% link_in_list /source-code-migration-tools %} diff --git a/translations/ko-KR/content/github/index.md b/translations/ko-KR/content/github/index.md index 768349e16a..ea86322b6d 100644 --- a/translations/ko-KR/content/github/index.md +++ b/translations/ko-KR/content/github/index.md @@ -20,24 +20,14 @@ versions: {% link_in_list /authenticating-to-github %} - {% link_in_list /managing-subscriptions-and-notifications-on-github %} - - {% link_in_list /receiving-notifications-about-activity-on-github %} - {% link_in_list /setting-up-and-managing-organizations-and-teams %} - - {% link_in_list /setting-up-and-managing-your-enterprise %} - - - {% link_in_list /setting-up-and-managing-billing-and-payments-on-github %} - {% link_in_list /writing-on-github %} @@ -50,10 +40,7 @@ versions: {% link_in_list /collaborating-with-issues-and-pull-requests %} {% link_in_list /managing-your-work-on-github %} - - {% link_in_list /developing-online-with-codespaces %} - {% link_in_list /building-a-strong-community %} @@ -64,45 +51,20 @@ versions: {% link_in_list /administering-a-repository %} {% link_in_list /visualizing-repository-data-with-graphs %} - - {% link_in_list /managing-security-vulnerabilities %} - {% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %} {% link_in_list /managing-files-in-a-repository %} {% link_in_list /managing-large-files %} - - {% link_in_list /customizing-your-github-workflow %} - {% link_in_list /extending-github %} {% link_in_list /working-with-github-pages %} - - {% link_in_list /supporting-the-open-source-community-with-github-sponsors %} - - - -{% link_in_list /teaching-and-learning-with-github-education %} - - - {% link_in_list /finding-talent-with-github-jobs %} - - - {% link_in_list /working-with-github-support %} - - - {% link_in_list /understanding-how-github-uses-and-protects-your-data %} - - - {% link_in_list /site-policy %} - diff --git a/translations/ko-KR/content/github/managing-files-in-a-repository/index.md b/translations/ko-KR/content/github/managing-files-in-a-repository/index.md index ebc35dd973..d1765daf5e 100644 --- a/translations/ko-KR/content/github/managing-files-in-a-repository/index.md +++ b/translations/ko-KR/content/github/managing-files-in-a-repository/index.md @@ -14,9 +14,7 @@ versions: ### Table of Contents {% topic_link_in_list /managing-files-on-github %} - {% link_in_list /navigating-code-on-github %} - {% link_in_list /creating-new-files %} {% link_in_list /adding-a-file-to-a-repository %} {% link_in_list /moving-a-file-to-a-new-location %} diff --git a/translations/ko-KR/content/github/managing-large-files/index.md b/translations/ko-KR/content/github/managing-large-files/index.md index bc1db5f762..576ce0e49f 100644 --- a/translations/ko-KR/content/github/managing-large-files/index.md +++ b/translations/ko-KR/content/github/managing-large-files/index.md @@ -15,16 +15,12 @@ versions: {% link_in_list /conditions-for-large-files %} {% link_in_list /removing-files-from-a-repositorys-history %} {% link_in_list /distributing-large-binaries %} - {% link_in_list /what-is-my-disk-quota %} - {% topic_link_in_list /versioning-large-files %} {% link_in_list /about-git-large-file-storage %} {% link_in_list /installing-git-large-file-storage %} {% link_in_list /configuring-git-large-file-storage %} - {% link_in_list /about-storage-and-bandwidth-usage %} - {% link_in_list /collaboration-with-git-large-file-storage %} {% link_in_list /moving-a-file-in-your-repository-to-git-large-file-storage %} {% link_in_list /removing-files-from-git-large-file-storage %} 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 a17fe4c6a1..0c7b5fd960 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 @@ -25,6 +25,8 @@ When your code depends on a package that has a security vulnerability, this vuln - 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 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)." {% note %} diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md new file mode 100644 index 0000000000..c03292e26f --- /dev/null +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -0,0 +1,24 @@ +--- +title: About managing vulnerable dependencies +intro: '{% data variables.product.prodname_dotcom %} helps you to avoid using third-party software that contains known vulnerabilities.' +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies. + +#### Dependency graph +The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." + +#### Dependency review +By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + +#### {% data variables.product.prodname_dependabot_alerts %} +{% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + +#### {% data variables.product.prodname_dependabot_security_updates %} +When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." + + +#### {% data variables.product.prodname_dependabot_version_updates %} +Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 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 2dc007d65a..266167b804 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 @@ -12,7 +12,7 @@ versions: {% 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-features-for-new-repositories)." +{% 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)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %} diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/index.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/index.md index 819e4c4e24..9afde0213a 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/index.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/index.md @@ -9,8 +9,6 @@ versions: ### Table of Contents - - {% topic_link_in_list /managing-security-vulnerabilities-in-your-project %} {% link_in_list /adding-a-security-policy-to-your-repository %} {% link_in_list /about-github-security-advisories %} @@ -22,17 +20,13 @@ versions: {% link_in_list /publishing-a-security-advisory %} {% link_in_list /editing-a-security-advisory %} {% link_in_list /withdrawing-a-security-advisory %} - {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %} - + {% link_in_list /about-managing-vulnerable-dependencies %} {% link_in_list /browsing-security-vulnerabilities-in-the-github-advisory-database %} - {% link_in_list /about-alerts-for-vulnerable-dependencies %} {% link_in_list /configuring-notifications-for-vulnerable-dependencies %} - {% link_in_list /about-dependabot-security-updates %} {% link_in_list /configuring-dependabot-security-updates %} {% link_in_list /viewing-and-updating-vulnerable-dependencies-in-your-repository %} {% link_in_list /troubleshooting-the-detection-of-vulnerable-dependencies %} {% link_in_list /troubleshooting-dependabot-errors %} - diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index c33aa46aba..dd179ef0df 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -76,6 +76,12 @@ There are separate limits for security and version update pull requests, so that 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 %} can't resolve your dependency files + +**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". + +{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." + ### Triggering a {% data variables.product.prodname_dependabot %} pull request manually If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request. diff --git a/translations/ko-KR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/ko-KR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 78e10421af..aeabaf053d 100644 --- a/translations/ko-KR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/ko-KR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -13,9 +13,11 @@ Your repository's {% data variables.product.prodname_dependabot %} alerts tab li You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +{% data reusables.repositories.dependency-review %} + ### About updates for vulnerable dependencies in your repository -{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. +{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. ### Viewing and updating vulnerable dependencies diff --git a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 313b384904..2540bee0af 100644 --- a/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/ko-KR/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -124,7 +124,8 @@ To filter notifications for specific activity on {% data variables.product.produ - `is:repository-invitation`{% if currentVersion != "github-ae@latest" %} - `is:repository-vulnerability-alert` - `is:repository-advisory`{% endif %} -- `is:team-discussion` +- `is:team-discussion`{% if currentVersion == "free-pro-team@latest" %} +- `is:discussions`{% endif %} {% if currentVersion != "github-ae@latest" %} For information about reducing noise from notifications for diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/about-issues.md b/translations/ko-KR/content/github/managing-your-work-on-github/about-issues.md index 43422e7898..9897fe9bb5 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/about-issues.md @@ -10,8 +10,14 @@ versions: github-ae: '*' --- +### About issues + 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. +Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} + +{% data reusables.discussions.you-cannot-convert-a-discussion %} + {% 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 %}." diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/index.md b/translations/ko-KR/content/github/managing-your-work-on-github/index.md index d882a90b1d..eb501619b0 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/index.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/index.md @@ -17,15 +17,11 @@ versions: {% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} - {% link_in_list /deleting-an-issue %} - {% link_in_list /opening-an-issue-from-a-comment %} {% link_in_list /opening-an-issue-from-code %} - {% link_in_list /transferring-an-issue-to-another-repository %} {% link_in_list /pinning-an-issue-to-your-repository %} - {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} @@ -43,9 +39,7 @@ versions: {% link_in_list /linking-a-repository-to-a-project-board %} {% link_in_list /about-automation-for-project-boards %} {% link_in_list /configuring-automation-for-project-boards %} - {% link_in_list /copying-a-project-board %} - {% link_in_list /closing-a-project-board %} {% link_in_list /reopening-a-closed-project-board %} {% link_in_list /deleting-a-project-board %} diff --git a/translations/ko-KR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/ko-KR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index 1099a977f0..e8f62a0662 100644 --- a/translations/ko-KR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/ko-KR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -25,6 +25,7 @@ With issue and pull request search terms, you can: - Filter issues and pull requests that involve, but don't necessarily [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), certain people: `state:open type:issue involves:octocat` - Filter issues and pull requests by assignee: `state:open type:issue assignee:octocat` - Filter issues and pull requests by label: `state:open type:issue label:"bug"` +- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} For issues, you can also use search to: diff --git a/translations/ko-KR/content/github/receiving-notifications-about-activity-on-github/index.md b/translations/ko-KR/content/github/receiving-notifications-about-activity-on-github/index.md index 31ad8c870e..cbb97cfc98 100644 --- a/translations/ko-KR/content/github/receiving-notifications-about-activity-on-github/index.md +++ b/translations/ko-KR/content/github/receiving-notifications-about-activity-on-github/index.md @@ -14,16 +14,10 @@ versions: {% link_in_list /choosing-the-delivery-method-for-your-notifications %} {% topic_link_in_list /managing-your-notifications %} {% link_in_list /marking-notifications-as-read %} - {% link_in_list /saving-notifications-for-later %} - {% link_in_list /subscribing-to-and-unsubscribing-from-notifications %} - {% link_in_list /listing-the-issues-and-pull-requests-youre-subscribed-to %} - {% link_in_list /watching-and-unwatching-repositories %} - {% link_in_list /watching-and-unwatching-releases-for-a-repository %} - {% link_in_list /watching-and-unwatching-team-discussions %} {% link_in_list /listing-the-repositories-youre-watching %} diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/ko-KR/content/github/searching-for-information-on-github/about-searching-on-github.md index 2f84601561..dbd26f1946 100644 --- a/translations/ko-KR/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/ko-KR/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -41,7 +41,8 @@ You can search for the following information across all repositories you can acc - [Repositories](/articles/searching-for-repositories) - [Topics](/articles/searching-topics) -- [Issues and pull requests](/articles/searching-issues-and-pull-requests) +- [Issues and pull requests](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} +- [Discussions](/github/searching-for-information-on-github/searching-discussions){% endif %} - [Code](/articles/searching-code) - [Commits](/articles/searching-commits) - [Users](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/index.md b/translations/ko-KR/content/github/searching-for-information-on-github/index.md index 1c417eade8..e95408d576 100644 --- a/translations/ko-KR/content/github/searching-for-information-on-github/index.md +++ b/translations/ko-KR/content/github/searching-for-information-on-github/index.md @@ -26,6 +26,7 @@ versions: {% link_in_list /searching-code %} {% link_in_list /searching-commits %} {% link_in_list /searching-issues-and-pull-requests %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /searching-discussions %} {% link_in_list /searching-github-marketplace %}{% endif %} {% link_in_list /searching-users %} {% link_in_list /searching-for-packages %} diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/searching-discussions.md b/translations/ko-KR/content/github/searching-for-information-on-github/searching-discussions.md new file mode 100644 index 0000000000..9f2df82760 --- /dev/null +++ b/translations/ko-KR/content/github/searching-for-information-on-github/searching-discussions.md @@ -0,0 +1,110 @@ +--- +title: Searching discussions +intro: You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)." + +{% data reusables.search.syntax_tips %} + +### Search by the title, body, or comments + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| Qualifier | 예시 | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +### Search within a user's or organization's repositories + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| Qualifier | 예시 | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +### Filter by repository visibility + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +| Qualifier | Example | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +### Search by author + +The `author` qualifier finds discussions created by a certain user. + +| Qualifier | 예시 | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +### Search by commenter + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| Qualifier | 예시 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +### Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| Qualifier | 예시 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +### Search by number of comments + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +### Search by number of interactions + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +### Search by number of reactions + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +### Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +### 더 읽을거리 + +- "[Sorting search results](/articles/sorting-search-results/)" diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 1f2f3910b8..058d316875 100644 --- a/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ko-KR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -203,7 +203,7 @@ You can use the `comments` qualifier along with [greater than, less than, and ra | Qualifier | 예시 | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3C100&type=Issues) matches closed issues with more than 100 comments. | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. | | | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. | ### Search by number of interactions diff --git a/translations/ko-KR/content/github/searching-for-information-on-github/searching-topics.md b/translations/ko-KR/content/github/searching-for-information-on-github/searching-topics.md index 961212159a..5f6b669048 100644 --- a/translations/ko-KR/content/github/searching-for-information-on-github/searching-topics.md +++ b/translations/ko-KR/content/github/searching-for-information-on-github/searching-topics.md @@ -26,7 +26,7 @@ If you want to explore repositories about a certain topic, find projects to cont The `is:featured` search qualifier will narrow search results to the topics with the most repositories on {% data variables.product.product_name %}. These topics are also featured at https://github.com/topics/. -The `is:curated` search qualifier will narrow search results to topics that community members have added extra information to. For more information, see the explore repository at https://github.com/github/explore. +The `is:curated` search qualifier will narrow search results to topics that community members have added extra information to. For more information, see the [explore repository](https://github.com/github/explore). You can filter topics based when they were created using the date parameter and `created:` or based on how many repositories are associated with this topic using `repositories:n`. Both of these qualifiers can use the [greater than and less than range qualifiers](/articles/understanding-the-search-syntax). diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 582f7db2aa..5c4f268ece 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -8,7 +8,9 @@ versions: ### About billing for {% data variables.product.prodname_actions %} -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} + +{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." Minutes reset every month, while storage usage does not. @@ -69,8 +71,8 @@ Your {% data variables.product.prodname_actions %} usage shares your account's e ### About spending limits -By default, your account will have a spending limit of $0 for {% data variables.product.prodname_actions %} usage. To enable using minutes and storage for private repositories beyond the amounts included with your account, you can increase the spending limit or allow unlimited spending. For more information, 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 reusables.github-actions.actions-spending-limit-detailed %} -{% data reusables.github-actions.spending-limit-enterprise-account %} +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 reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 29ac4bbc5e..838a947290 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -10,6 +10,8 @@ versions: {% data reusables.package_registry.packages-billing %} +{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." + {% data reusables.package_registry.container-registry-beta-billing-note %} Data transfer resets every month, while storage usage does not. @@ -50,8 +52,8 @@ Your {% data variables.product.prodname_registry %} usage shares your account's ### About spending limits -By default, your account will have a spending limit of $0 for {% data variables.product.prodname_registry %} usage. To enable storage and data transfer for private packages beyond the amounts included with your account, you can increase the spending limit or allow unlimited spending. For more information, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." +{% data reusables.package_registry.packages-spending-limit-detailed %} -{% data reusables.package_registry.spending-limit-enterprise-account %} +For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md index 307d033403..b48f64bd19 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md @@ -9,6 +9,8 @@ versions: {% data reusables.sponsors.sponsorship-details %} +{% data reusables.sponsors.no-fees %} + {% data reusables.dotcom_billing.view-all-subscriptions %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index 0494e1b907..c79f7a32a3 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### Discounts for personal accounts -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 "[Applying for a student developer pack](/articles/applying-for-a-student-developer-pack)." +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/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." ### Discounts for schools and universities -Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[Using {% data variables.product.prodname_dotcom %} in your classroom and research](/articles/using-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/). +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/teach-and-learn-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/). ### Discounts for nonprofits and libraries 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 68a7d36c58..340d65b9b2 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 @@ -7,24 +7,24 @@ versions: free-pro-team: '*' --- +{% 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 %} + ### Downgrading a sponsorship -When you downgrade a sponsorship, the change will become effective on your next billing date. {% data reusables.sponsors.no-refunds %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. On the right side of the page, next to your selected tier, click **Edit**. ![Edit tier button](/assets/images/help/billing/edit-tier-button.png) +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### Canceling a sponsorship -When you cancel a sponsorship, the change will become effective on your next billing date. {% data reusables.sponsors.no-refunds %} - {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.billing %} +{% 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/managing-your-spending-limit-for-github-actions.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index bc99201f6a..8ae1262da6 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -8,13 +8,15 @@ versions: ### About spending limits for {% data variables.product.prodname_actions %} -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} -You can set a higher spending limit or, for some accounts, allow unlimited spending. If you pay for your organization or enterprise account by invoice, you can prepay for overages to set a higher spending limit. The spending limit applies to your combined overages for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. 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.github-actions.actions-spending-limit-brief %} -As soon as you set a spending limit above $0, you will be responsible for any overages that occurred in the past. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and creates workflow artifacts that increase your storage usage for the month from 1.9GB to 2.1GB, you will use slightly more storage than the 2GB your product includes. +{% 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)." -Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages in a future month, your first bill will include the 0.1GB of overage from the past in addition to any overages for the current billing cycle. +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and creates workflow artifacts that increase your storage usage for the month from 1.9GB to 2.1GB, you will use slightly more storage than the 2GB your product includes. + +Because you have not enabled overages, your next attempt to create a workflow artifact will fail. You will not receive a bill for the 0.1GB overage that month. 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. ### Managing the spending limit for {% data variables.product.prodname_actions %} for your user account @@ -30,8 +32,6 @@ Anyone can manage the spending limit for {% data variables.product.prodname_acti Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an organization. -If you pay for your organization account by invoice, you cannot manage the spending limit for your enterprise account on {% data variables.product.product_name %}. If you want to allow repositories owned by your organization to use {% data variables.product.prodname_actions %} beyond the storage or data transfer included for each repository, you can prepay for overages. Because overages must prepaid, you cannot enable unlimited spending on accounts paid by invoice. Your spending limit will be 150% of the amount you prepaid. If you have any questions, [contact our account management team](https://enterprise.github.com/contact). - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ If you pay for your organization account by invoice, you cannot manage the spend Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an enterprise account. -{% data reusables.github-actions.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 4fd980b821..a89aca74c9 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -10,11 +10,13 @@ versions: {% data reusables.package_registry.packages-billing %} -You can set a higher spending limit or, for some accounts, allow unlimited spending. If you pay for your organization or enterprise account by invoice, you can prepay for overages to set a higher spending limit. The spending limit applies to your combined overages for {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}. 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.package_registry.packages-spending-limit-brief %} -As soon as you set a spending limit above $0, you will be responsible for any overages that occurred in the past. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and publishes a new version of a private package that increases your storage usage for the month from 1.9GB to 2.1GB, publishing the version will use slightly more than the 2GB your product includes. +{% 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)." -Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages in a future month, your first bill will include the 0.1GB of overage from the past in addition to any overages for the current billing cycle. +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and publishes a new version of a private package that increases your storage usage for the month from 1.9GB to 2.1GB, publishing the version will use slightly more than the 2GB your product includes. + +Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. 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. ### Managing the spending limit for {% data variables.product.prodname_registry %} for your user account @@ -30,8 +32,6 @@ Anyone can manage the spending limit for {% data variables.product.prodname_regi Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an organization. -If you pay for your organization account by invoice, you cannot manage the spending limit for your enterprise account on {% data variables.product.product_name %}. If you want to allow repositories owned by your organization to use {% data variables.product.prodname_registry %} beyond the storage or data transfer included for each repository, you can prepay for overages. Because overages must prepaid, you cannot enable unlimited spending on accounts paid by invoice. Your spending limit will be 150% of the amount you prepaid. If you have any questions, [contact our account management team](https://enterprise.github.com/contact). - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ If you pay for your organization account by invoice, you cannot manage the spend Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an enterprise account. -{% data reusables.package_registry.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 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 43f0ab53e7..f1ff761223 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 @@ -7,12 +7,15 @@ versions: free-pro-team: '*' --- +{% data reusables.sponsors.org-sponsors-release-phase %} + +### About sponsorship upgrades + When you upgrade your sponsorship tier, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. On the right side of the page, next to your selected tier, click **Edit**. ![Edit tier button](/assets/images/help/billing/edit-tier-button.png) +### Upgrading a sponsorship + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.update-sponsorship %} +{% data reusables.sponsors.update-sponsorship %} \ No newline at end of file diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md index 65902675cb..6cc19fc18b 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md @@ -20,7 +20,7 @@ versions: ### 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, and issues from the account. +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 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md index a60e0307b4..858bd85d4a 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -19,4 +19,4 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.oauth_app_access %} 5. 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 button](/assets/images/help/settings/settings-third-party-confirm-disable.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/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md index 51d361dd56..d1c440e8c5 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -20,42 +20,30 @@ versions: {% link_in_list /creating-a-new-organization-from-scratch %} {% link_in_list /accessing-your-organizations-settings %} {% link_in_list /about-your-organizations-news-feed %} - {% link_in_list /viewing-insights-for-your-organization %} - {% topic_link_in_list /managing-membership-in-your-organization %} - {% link_in_list /inviting-users-to-join-your-organization %} {% link_in_list /canceling-or-editing-an-invitation-to-join-your-organization %} {% link_in_list /adding-people-to-your-organization %} - {% link_in_list /removing-a-member-from-your-organization %} {% link_in_list /reinstating-a-former-member-of-your-organization %} - {% link_in_list /can-i-create-accounts-for-people-in-my-organization %} - {% topic_link_in_list /managing-peoples-access-to-your-organization-with-roles %} {% link_in_list /permission-levels-for-an-organization %} {% link_in_list /maintaining-ownership-continuity-for-your-organization %} {% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %} - {% link_in_list /adding-a-billing-manager-to-your-organization %} {% link_in_list /removing-a-billing-manager-from-your-organization %} - {% topic_link_in_list /organizing-members-into-teams %} {% link_in_list /about-teams %} {% link_in_list /creating-a-team %} {% link_in_list /setting-your-teams-profile-picture %} {% link_in_list /adding-organization-members-to-a-team %} - {% link_in_list /managing-code-review-assignment-for-your-team %} - {% link_in_list /renaming-a-team %} {% link_in_list /changing-team-visibility %} - {% link_in_list /synchronizing-a-team-with-an-identity-provider-group %} - {% link_in_list /moving-a-team-in-your-organizations-hierarchy %} {% link_in_list /requesting-to-add-a-child-team %} {% link_in_list /requesting-to-add-or-change-a-parent-team %} @@ -66,9 +54,7 @@ versions: {% topic_link_in_list /managing-access-to-your-organizations-repositories %} {% link_in_list /repository-permission-levels-for-an-organization %} {% link_in_list /setting-base-permissions-for-an-organization %} - {% link_in_list /viewing-people-with-access-to-your-repository %} - {% link_in_list /managing-an-individuals-access-to-an-organization-repository %} {% link_in_list /managing-team-access-to-an-organization-repository %} {% link_in_list /adding-outside-collaborators-to-repositories-in-your-organization %} @@ -84,83 +70,54 @@ versions: {% link_in_list /managing-an-individuals-access-to-an-organization-project-board %} {% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %} {% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %} - {% topic_link_in_list /managing-access-to-your-organizations-apps %} {% link_in_list /adding-github-app-managers-in-your-organization %} {% link_in_list /removing-github-app-managers-from-your-organization %} - {% topic_link_in_list /managing-organization-settings %} - {% link_in_list /verifying-your-organizations-domain %} - {% link_in_list /renaming-an-organization %} {% link_in_list /transferring-organization-ownership %} {% link_in_list /restricting-repository-creation-in-your-organization %} {% link_in_list /setting-permissions-for-deleting-or-transferring-repositories %} {% link_in_list /restricting-repository-visibility-changes-in-your-organization %} {% link_in_list /managing-the-forking-policy-for-your-organization %} - {% link_in_list /disabling-or-limiting-github-actions-for-your-organization %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization %} - - {% link_in_list /setting-permissions-for-adding-outside-collaborators %} - {% link_in_list /allowing-people-to-delete-issues-in-your-organization %} - - + {% link_in_list /allowing-people-to-delete-issues-in-your-organization %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /managing-discussion-creation-for-repositories-in-your-organization %}{% endif %} {% link_in_list /setting-team-creation-permissions-in-your-organization %} - - {% link_in_list /managing-scheduled-reminders-for-your-organization %} - - {% link_in_list /managing-the-default-branch-name-for-repositories-in-your-organization %} - - {% link_in_list /managing-default-labels-for-repositories-in-your-organization %} - - {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} - - {% link_in_list /managing-the-display-of-member-names-in-your-organization %} - + {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} - {% link_in_list /integrating-jira-with-your-organization-project-board %} - - {% link_in_list /upgrading-to-the-corporate-terms-of-service %} - {% topic_link_in_list /migrating-to-improved-organization-permissions %} {% link_in_list /converting-an-owners-team-to-improved-organization-permissions %} {% link_in_list /converting-an-admin-team-to-improved-organization-permissions %} {% link_in_list /migrating-admin-teams-to-improved-organization-permissions %} - {% topic_link_in_list /restricting-access-to-your-organizations-data %} {% link_in_list /about-oauth-app-access-restrictions %} {% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /approving-oauth-apps-for-your-organization %} {% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %} - {% topic_link_in_list /keeping-your-organization-secure %} {% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %} {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} - {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} {% link_in_list /managing-secret-scanning-for-your-organization %} - {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} - {% link_in_list /restricting-email-notifications-to-an-approved-domain %} - {% link_in_list /reviewing-the-audit-log-for-your-organization %} {% link_in_list /reviewing-your-organizations-installed-integrations %} - {% topic_link_in_list /managing-saml-single-sign-on-for-your-organization %} {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} {% link_in_list /about-scim %} @@ -170,17 +127,12 @@ versions: {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} {% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %} - {% link_in_list /managing-team-synchronization-for-your-organization %} - {% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %} {% topic_link_in_list /granting-access-to-your-organization-with-saml-single-sign-on %} {% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %} {% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %} - - {% topic_link_in_list /managing-git-access-to-your-organizations-repositories %} {% link_in_list /about-ssh-certificate-authorities %} {% link_in_list /managing-your-organizations-ssh-certificate-authorities %} - diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..7e73c05fd2 --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Managing discussion creation for repositories in your organization +intro: You can choose the permission levels that members require to create discussions in repositories owned by your organization. +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Allowing or disallowing users with read access to create discussions + +By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. 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/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 4b6e5321ba..cdd76927c4 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -9,29 +9,39 @@ versions: ### About management of security and analysis settings {% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. - {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% endif %} - -### Enabling or disabling features for existing repositories +### 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 %} -5. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -6. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) -### Enabling or disabling features for new repositories +The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. + +### Enabling or disabling a feature for all existing repositories + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) +1. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) +1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + +### Enabling or disabling a feature for all new repositories when they are added + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + +### Allowing Dependabot to access private repositories + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) +1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. +1. Click **Select repositories**. -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..116f22dbe9 --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,23 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +--- + +{% 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)" \ No newline at end of file diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index ca9d809a86..642309de49 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -55,6 +55,9 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late | Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} | 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** | | |{% endif %} | 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](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | | Manage security and analysis settings (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)" for details) | **X** | | | | Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 3ffd62c502..a4c4374335 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -114,7 +114,19 @@ In addition to managing organization-level settings, organization owners have ad | [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** | +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} ### 더 읽을거리 diff --git a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index f14dbeb656..1fe1d8b293 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -82,7 +82,9 @@ Each category has a set of associated actions that you can filter on. 예시: Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} -{% data reusables.search.date_gt_lt %} For example: +{% 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. @@ -106,25 +108,53 @@ Using the qualifier `country`, you can filter events in the audit log based on t {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -### Using the Audit log API +### 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 API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} +**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 API to keep copies of your audit log data and monitor: -* Access to your organization or repository settings. -* Changes in permissions. -* Added or removed users in an organization, repository, or team. -* Users being promoted to admin. -* Changes to permissions of a GitHub App. +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. +{% 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 as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +{% 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)" in the REST API documentation. + +{% endif %} + ### Audit log actions An overview of some of the most common actions that are recorded as events in the audit log. @@ -214,6 +244,28 @@ An overview of some of the most common actions that are recorded as events in th | `업데이트` | 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" %} + +#### `git` category actions + +{% note %} + +**Note:** To access Git events in the audit log, you must use the audit log REST API. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. + +{% 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 | 동작 | 설명 | @@ -499,10 +551,22 @@ For more information, see "[Restricting publication of {% data variables.product {% 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)") | +| 동작 | 설명 | +| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `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 organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") | +| 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 %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index 747c37af9d..32bdc84b38 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and{% endif %}private repositories, with specific details of your activity in private repositories anonymized. 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 %}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)." {% note %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/index.md index 19615ecffa..aff371dd59 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/index.md @@ -14,41 +14,28 @@ versions: {% topic_link_in_list /managing-user-account-settings %} {% link_in_list /about-your-personal-dashboard %} + {% link_in_list /managing-your-theme-settings %} {% link_in_list /changing-your-github-username %} - {% link_in_list /merging-multiple-user-accounts %} {% link_in_list /converting-a-user-into-an-organization %} - {% link_in_list /deleting-your-user-account %} {% link_in_list /permission-levels-for-a-user-account-repository %} {% link_in_list /permission-levels-for-user-owned-project-boards %} {% link_in_list /managing-the-default-branch-name-for-your-repositories %} {% link_in_list /managing-security-and-analysis-settings-for-your-user-account %} - {% link_in_list /managing-access-to-your-user-accounts-project-boards %} - + {% link_in_list /managing-access-to-your-user-accounts-project-boards %} {% link_in_list /integrating-jira-with-your-personal-projects %} - - {% link_in_list /best-practices-for-leaving-your-company %} - - {% link_in_list /what-does-the-available-for-hire-checkbox-do %} - {% topic_link_in_list /managing-email-preferences %} {% link_in_list /adding-an-email-address-to-your-github-account %} {% link_in_list /changing-your-primary-email-address %} {% link_in_list /setting-a-backup-email-address %} {% link_in_list /setting-your-commit-email-address %} - {% link_in_list /blocking-command-line-pushes-that-expose-your-personal-email-address %} - {% link_in_list /remembering-your-github-username-or-email %} - {% link_in_list /types-of-emails-github-sends %} - - {% link_in_list /managing-marketing-emails-from-github %} - {% topic_link_in_list /managing-access-to-your-personal-repositories %} {% link_in_list /inviting-collaborators-to-a-personal-repository %} {% link_in_list /removing-a-collaborator-from-a-personal-repository %} @@ -58,9 +45,7 @@ versions: {% link_in_list /about-organization-membership %} {% link_in_list /accessing-an-organization %} {% link_in_list /viewing-peoples-roles-in-an-organization %} - {% link_in_list /requesting-organization-approval-for-oauth-apps %} - {% link_in_list /publicizing-or-hiding-organization-membership %} {% link_in_list /managing-your-scheduled-reminders %} {% link_in_list /removing-yourself-from-an-organization %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md new file mode 100644 index 0000000000..3a12936ae6 --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -0,0 +1,22 @@ +--- +title: Managing your theme settings +intro: You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode. +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Theme settings is currently in beta and subject to change. + +{% endnote %} + +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. + +{% data reusables.user_settings.access_settings %} +1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) + +### 더 읽을거리 + +- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md b/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md index 34d99f176a..91acf9fde2 100644 --- a/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ko-KR/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: November 13, 2020 +Version Effective Date: December 14, 2020 When you create an Account, you're given access to lots of different features and products that are all a part of the Service. Because many of these features and products offer different functionality, they may require additional terms and conditions specific to that feature or product. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -46,13 +46,11 @@ GitHub Pages are subject to some specific bandwidth and usage limits, and may no ### 5. Actions and Packages #### a. Actions Usage -GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Each Account comes with included compute and storage quantities for use with Actions, depending on your Account plan, which can be found in the [Actions documentation](/actions). Your Actions compute usage is displayed within [your account settings](https://github.com/settings/billing), and you will be notified by email in advance of reaching the limit of your included quantities. If you want to use Actions beyond your included quantities, then you may [enable overages](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions). +GitHub Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. -Compute usage for included and paid quantities is calculated in minutes based on the type of Actions you execute (e.g. Linux, Windows, macOS). The minutes used for each Action's job or task will be rounded up to the nearest minute. For included quantities and depending on the type of Action, a multiplier may be applied to the amount of time used to execute each job or task, prior to being rounded up to the nearest minute. Overage minutes are charged at the [stated per minute price](https://github.com/features/actions) based on the type of Actions you execute. Actions and Packages share storage, and your storage usage is displayed within your [account settings](https://github.com/settings/billing). For additional details about included quantity usage calculations, see the [Actions documentation](/actions). - -Actions and any elements of the Action service may not be used in violation of the Agreement, the [Acceptable Use Policy](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions [service limitations](/actions/reference/usage-limits-billing-and-administration/#usage-limits). Additionally, Actions should not be used for: +Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions). Additionally, Actions should not be used for: - cryptomining; -- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)) +- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); - the provision of a stand-alone or integrated application or service offering Actions or any elements of Actions for commercial purposes; - any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or - any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used. @@ -60,16 +58,7 @@ Actions and any elements of the Action service may not be used in violation of t In order to prevent violations of these limitations and abuse of GitHub Actions, GitHub may monitor your use of GitHub Actions. Misuse of GitHub Actions may result in termination of jobs, or restrictions in your ability to use GitHub Actions. #### b. Packages Usage -GitHub Packages may be used to download, publish, and manage packages of Content. Each Account plan comes with included bandwidth and storage quantities for use with Packages, which can be found in the [Packages documentation](/github/managing-packages-with-github-package-registry/about-github-package-registry). Actions and Packages share storage between the two Service features. Storage and bandwidth usage are displayed within your [account settings](https://github.com/settings/billing), and you will be notified by email in advance of reaching the limit of your included quantities. If you want to use Packages beyond your included bandwidth and storage quantities, then you may [enable overages](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages). - -Bandwidth usage is calculated based on the amount of data transferred out of your repositories through Packages, but package transfers through Actions will not count toward your included or paid quantities. Packages bandwidth usage is limited by the [Acceptable Use Policy](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use), and included bandwidth quantities are determined by your [account plan](https://github.com/pricing). - -Actions and Packages storage usage is shared between the two Service features. Storage usage is calculated as a weighted average over the course of the month and does not reset each month. Public and private repositories have different included storage quantities, and the included quantities for private repositories depend on your [account plan](https://github.com/pricing). - -#### c. Payment and Billing for Actions and Packages -Billing for Actions and Packages is usage-based. Additional quantities of Actions or Packages cannot be purchased separately. For monthly-billed customers, you must have a payment method on file to choose to pay for additional quantities of these Service features. You will be charged on a monthly, recurring basis based on your usage in the preceding month, unless you are billed by invoice. For invoiced customers, you must pay the fees within thirty (30) days of the GitHub invoice date. For customers paying for Service feature overages in advance, unused prepaid minutes will not roll over to the next billing period and will not be refunded. - -You can set a monthly spending limit in your [account settings](https://github.com/settings/billing/cost_management). You will be notified by email in advance of reaching the limit of your included quantities and the designated spending limit of your paid additional quantities. +GitHub Packages is billed on a usage basis. The [Packages documentation](/packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies). ### 6. Learning Lab @@ -108,3 +97,13 @@ We need the legal right to submit your contributions to the GitHub Advisory Data #### b. License to the GitHub Advisory Database The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by . + +### 13. GitHub Enterprise Server + +#### a. SQL Server Images + +You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time. + +#### b. Third-party components + +The Software includes components licensed to GitHub by third parties, including software whose licenses require GitHub to make the source code for those components available. The source code for such components will be provided upon request. 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 0e378a5dff..6bed997ba6 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 @@ -191,7 +191,7 @@ Customer’s Affiliates are authorized to use the Products in accordance with th #### 1. Pricing; Fees -**Payment Terms** Our pricing is available at [github.com/pricing](https://github.com/pricing) (unless otherwise negotiated by the parties and stated in an Order Form). Customer agrees to pay the Fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. Customer must pay the Fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If Customer fails to pay any Fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable Order Form or SOW. Customer is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. +**Payment Terms** Our pricing is available at [github.com/pricing](https://github.com/pricing) (unless otherwise negotiated by the parties and stated in an Order Form). Customer agrees to pay the Fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. Customer must pay the Fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If Customer fails to pay any Fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable Order Form or SOW. Customer is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. **Usage-Based Billing** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to purchase paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears, provided that for invoiced customers, paid Service features are billed in advance. See [GitHub Additional Product Terms for details](/github/site-policy/github-additional-product-terms). diff --git a/translations/ko-KR/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/ko-KR/content/github/site-policy/github-enterprise-service-level-agreement.md index eeeeaad115..1a422a96fe 100644 --- a/translations/ko-KR/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/ko-KR/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -8,22 +8,22 @@ versions: free-pro-team: '*' --- -**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the GitHub Enterprise Cloud service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). +**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the applicable GitHub service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). -For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. +For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. ## Uptime Guarantee -“**Uptime**” is the percentage of total possible minutes the Service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the Service. The Uptime calculation for each Service Feature is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. +“**Uptime**” is the percentage of total possible minutes the applicable GitHub service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service. The Uptime calculation for each Service Feature that may be included with the applicable GitHub service is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. -| **Service Feature** | **Uptime Calculation** | **정의** | **Service Credits Calculation** | -| --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -| The **Service** includes the following Service Features:
      • 문제
      • 풀 리퀘스트
      • Git Operations
      • API Requests
      • Webhooks
      • Pages
      • Actions
      • Packages
      | (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
      • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than or equal to 99.9%, but greater than 99.0%.

        OR

      • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
      | | -| **Actions** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

      “**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | -| **Packages** | Transfers Uptime = same as Actions

      Storage Uptime = 100% - Average Error Rate*

      *The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

      “**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | +| **Service Feature** | **Uptime Calculation** | **정의** | **Service Credits Calculation** | +| -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | +| **Issues**,
      **Pull Requests**,
      **Git Operations**,
      **API Requests**,
      **Webhooks**,
      **Pages** | (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
      • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than or equal to 99.9%, but greater than 99.0%.

        OR

      • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
      | | +| **Actions** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

      “**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | +| **Packages** | Transfers Uptime = same as Actions

      Storage Uptime = 100% - Average Error Rate*

      *The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

      “**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | ## Exclusions -Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. +Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the applicable GitHub service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Service Credits Redemption If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). diff --git a/translations/ko-KR/content/github/site-policy/github-registered-developer-agreement.md b/translations/ko-KR/content/github/site-policy/github-registered-developer-agreement.md index 98c90d694d..234ef5d9f0 100644 --- a/translations/ko-KR/content/github/site-policy/github-registered-developer-agreement.md +++ b/translations/ko-KR/content/github/site-policy/github-registered-developer-agreement.md @@ -86,7 +86,7 @@ This Agreement is a legal agreement between you (“you”) and GitHub, Inc. ( 13. **Proprietary Rights** - You agree that GitHub and its licensors own all right, title and interest in and to the API, the Pre-release Materials, and all other GitHub products and services; all information and data relating to their configurations and combinations; and all modifications to and derivative works of any of the foregoing. You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other other GitHub products and services. + You agree that GitHub and its licensors own all right, title and interest in and to the API, the Pre-release Materials, and all other GitHub products and services; all information and data relating to their configurations and combinations; and all modifications to and derivative works of any of the foregoing. You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services. 14. **Government Users** 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 5af62e7229..63c538e230 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 @@ -9,7 +9,9 @@ versions: ### About {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.sponsorship-details %} {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." +{% data reusables.sponsors.sponsorship-details %} + +{% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." {% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[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)." @@ -25,7 +27,7 @@ When you become a sponsored developer or sponsored organization, additional term {% endnote %} -The {% data variables.product.prodname_matching_fund %} aims to benefit members of the {% data variables.product.prodname_dotcom %} community who develop open source software that promotes the [{% data variables.product.prodname_dotcom %} Community Guidelines](/github/site-policy/github-community-guidelines). Sponsored organizations are not eligible for {% data variables.product.prodname_matching_fund %}. +The {% data variables.product.prodname_matching_fund %} aims to benefit members of the {% data variables.product.prodname_dotcom %} community who develop open source software that promotes the [{% data variables.product.prodname_dotcom %} Community Guidelines](/github/site-policy/github-community-guidelines). Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}. To be eligible for the {% data variables.product.prodname_matching_fund %}, you must create a profile that will attract a community that will sustain you for the long term. For more information about creating a strong 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)." @@ -35,8 +37,6 @@ To be eligible for the {% data variables.product.prodname_matching_fund %}, you 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). -Currently, only individual users can sponsor developers and organizations. If your organization is interested in sponsoring developers, please let us know by contacting [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). - ### 더 읽을거리 - "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" - "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)" diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md new file mode 100644 index 0000000000..57b1b5a4d6 --- /dev/null +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md @@ -0,0 +1,13 @@ +--- +title: Attributing sponsorships to your organization +intro: 'You can attribute the sponsorships paid by one of your organizations to another organization.' +versions: + free-pro-team: '*' +permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization. +--- + +1. Navigate to the organization whose sponsorships you want to attribute to another organization. +1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png) +1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png) +1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png) +1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md index 4bed524e3c..f9b176f55d 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -13,38 +13,20 @@ versions: {% data reusables.sponsors.maximum-tier %} -### Adding a tier for your sponsored developer profile +### Adding a tier -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} -### Adding a tier for your sponsored organization profile +### Editing or retiring a tier -{% data reusables.sponsors.navigate-to-org-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 for your sponsored developer profile - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} - -### Editing or retiring a tier for your sponsored organization profile - -{% data reusables.sponsors.navigate-to-org-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 %} +{% data reusables.sponsors.retire-tier %} \ No newline at end of file diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md index ba6e771ba3..0cae836a8f 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md @@ -5,11 +5,13 @@ versions: free-pro-team: '*' --- -To monitor changes to your sponsorships, such as cancellations at the end of a pay period, you can create webhooks for your sponsored user or organization account. When you set up a webhook for your sponsored user or organization account, you'll receive updates when sponsorships are created, edited, or deleted. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship). +### About webhooks for events in your sponsored account -### Managing webhooks for your sponsored user account +To monitor changes to your sponsorships, such as cancellations at the end of a pay period, you can create webhooks for your sponsored user or organization account. When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship). -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +### Managing webhooks for events in your sponsored account + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-webhooks-tab %} {% data reusables.sponsors.add-webhook %} {% data reusables.sponsors.add-payload-url %} @@ -17,18 +19,4 @@ To monitor changes to your sponsorships, such as cancellations at the end of a p {% data reusables.sponsors.webhook-secret-token %} {% data reusables.sponsors.add-active-triggers %} {% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} - -### Managing webhooks for your sponsored organization - -Organization owners can configure webhooks for a sponsored organization. - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-webhooks-tab %} -{% data reusables.sponsors.add-webhook %} -{% data reusables.sponsors.add-payload-url %} -{% data reusables.sponsors.webhook-content-formatting %} -{% data reusables.sponsors.webhook-secret-token %} -{% data reusables.sponsors.add-active-triggers %} -{% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} +{% data reusables.sponsors.manage-existing-webhooks %} \ No newline at end of file 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 80e23f3cf5..640d965448 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 @@ -7,22 +7,15 @@ versions: free-pro-team: '*' --- +### About sponsorship updates + Your sponsors can choose whether they receive email updates about your work. For more information, see "[Managing your sponsorship](/articles/managing-your-sponsorship)." -The update will come from your user account's primary email address or organization account's `noreply@github.com` email address. If you've enabled email address privacy on your user account, the update will come from `noreply@github.com` instead. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +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)." -### Contacting your user account's sponsors +### Contacting your sponsors -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.sponsors-updates-tab %} -{% data reusables.sponsors.draft-new-update %} -{% data reusables.sponsors.send-update-to-sponsors %} -{% data reusables.sponsors.write-sponsor-update %} -{% data reusables.sponsors.publish-sponsor-update %} - -### Contacting your organization's sponsors - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.sponsors-updates-tab %} {% data reusables.sponsors.draft-new-update %} {% data reusables.sponsors.send-update-to-sponsors %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md index e841276f04..53004b7463 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md @@ -10,30 +10,17 @@ versions: ### About sponsor profiles -Your {% data variables.product.prodname_sponsors %} profile tells potential sponsors why they should support you. People see your sponsor profile when they click the **Sponsor** button on your personal or organization profile. We recommend including the following information. +Your {% data variables.product.prodname_sponsors %} profile tells potential sponsors why they should support you. People see your sponsor profile when they click the **Sponsor** button on your profile. We recommend including the following information. -- Open source work that you contribute to. -- Why you are committed to open source development. +- Open source work that you contribute to +- Why you are committed to open source development -You can also set goals to explain what different of levels of sponsorship will allow you to do for the community. +### Editing your profile details -### Editing your sponsored developer profile - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### Editing your sponsored organization profile - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.meet-the-team %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} +{% data reusables.sponsors.save-profile %} \ No newline at end of file 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 def51bcb47..48892ef8f2 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 @@ -16,6 +16,7 @@ versions: {% topic_link_in_list /sponsoring-open-source-contributors %} {% link_in_list /sponsoring-an-open-source-contributor %} {% link_in_list /managing-your-sponsorship %} + {% link_in_list /attributing-sponsorships-to-your-organization %} {% topic_link_in_list /receiving-sponsorships-through-github-sponsors %} {% link_in_list /about-github-sponsors-for-open-source-contributors %} {% link_in_list /setting-up-github-sponsors-for-your-user-account %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md index 295daca888..abfed9bd2c 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md @@ -13,14 +13,8 @@ You can only manage your payouts from {% data variables.product.prodname_sponsor {% data reusables.sponsors.payout-info %} -### Viewing and editing payout information for your sponsored user account +### Viewing and editing payout information -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} - -### Viewing and editing payout information for your sponsored organization - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} +{% data reusables.sponsors.edit-bank-information %} \ No newline at end of file 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 07a67e1a88..a4d3bdc206 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 @@ -1,27 +1,19 @@ --- title: Managing your sponsorship goal -intro: You can set a goal for your sponsored developer or sponsored organization profile to help the community understand the impact of sponsoring you. +intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you. versions: free-pro-team: '*' --- ### About sponsorship goals -You can set a funding goal for your sponsored developer or organization profile and share the goal with your community. Goals help you understand the impact you have in the open source community and build up your presence in the {% data variables.product.prodname_sponsors %} program. +You can set a funding goal for your sponsored account and share the goal with your community. Goals help you understand the impact you have in the open source community and build up your presence in the {% data variables.product.prodname_sponsors %} program. 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. -### Setting a goal for a sponsored organization +### Setting a goal -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.set-a-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### Setting a goal for a sponsored developer - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.set-a-goal %} {% data reusables.sponsors.select-goal-type %} @@ -31,6 +23,7 @@ Your goal can set a target for the number of sponsors you want to have or the am When you edit a goal, you can't choose a goal you've already achieved. For example, if you already have 5 sponsors, you can't edit your goal so that you're aiming for 4 sponsors. +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.select-goal-type %} @@ -40,6 +33,7 @@ When you edit a goal, you can't choose a goal you've already achieved. For examp After you retire a goal, you won't be able to reactivate the goal. You must create a new goal instead. +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.retire-goal %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md index 17c1100ced..06c74171b2 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -1,42 +1,35 @@ --- title: Managing your sponsorship -intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored open source contributor. +intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account. redirect_from: - /articles/managing-your-sponsorship versions: free-pro-team: '*' --- -For information about changing your sponsorship tier, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)." +{% data reusables.sponsors.org-sponsors-release-phase %} -### Managing the privacy setting for your developer sponsorship +### Managing the privacy setting for your sponsorship -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} {% data reusables.sponsors.who-can-see-your-sponsorship %} {% data reusables.sponsors.update-sponsorship %} -### Managing the privacy setting for your organization sponsorship +### Managing email updates for your sponsorship -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.who-can-see-your-sponsorship %} +You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address. + +{% data reusables.sponsors.manage-updates-for-orgs %} + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} +{% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.update-sponsorship %} -### Managing email updates from a sponsored developer +### 더 읽을거리 -You can choose whether a sponsored developer can send you email updates about their work. The sponsored developer will not have access to your email address. - -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} -{% data reusables.sponsors.developer-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} - -### Managing email updates from a sponsored organization - -You can choose whether a sponsored organization can send you email updates about their work. The sponsored organization will not have access to your email address. - -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.org-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} +- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" +- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)" \ No newline at end of file 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 08af58419c..261a4245bc 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 @@ -25,7 +25,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu ### Completing your sponsored organization profile -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% 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 %} @@ -54,7 +54,7 @@ As a sponsored organization, you must receive payouts to a dedicated bank accoun {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} For more information about setting up Stripe Connect using Open Collective, see [Setting up {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) in the Open Collective Docs. @@ -63,7 +63,7 @@ For more information about setting up Stripe Connect using Open Collective, see {% data reusables.sponsors.tax-form-information-org %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -75,7 +75,7 @@ Before your organization can become a sponsored organization, you must enable 2F ### Submitting your application to {% data variables.product.prodname_dotcom %} for approval -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %} {% data reusables.sponsors.github-review-app %} 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 f11ff74a9a..e47f54497f 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 @@ -26,7 +26,7 @@ If you have a bank account in a supported region, {% data variables.product.prod After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you. -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ After {% data variables.product.prodname_dotcom %} reviews your application, you {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} @@ -54,14 +54,14 @@ If you live in a supported region, you can follow these instructions to submit y {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} ### Submitting your tax information {% data reusables.sponsors.tax-form-information-dev %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -73,7 +73,7 @@ Before you can become a sponsored developer, you must enable 2FA on your {% data ### Submitting your application to {% data variables.product.prodname_dotcom %} for approval -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 4. Click **Request approval**. ![Request approval button](/assets/images/help/sponsors/request-approval-button.png) {% data reusables.sponsors.github-review-app %} 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 8fb3e7686c..69bff67d4a 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 @@ -7,17 +7,32 @@ redirect_from: - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer versions: free-pro-team: '*' +permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization. --- -### About sponsoring developers and organizations +{% data reusables.sponsors.org-sponsors-release-phase %} -{% data reusables.sponsors.sponsorship-details %} {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." +### About sponsorships -When you sponsor an open source contributor, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} +{% data reusables.sponsors.sponsorship-details %} -If the sponsored open source contributor retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. For more information, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)." +You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons. +- Sustaining specific libraries that your organization's work depends on +- Investing in the ecosystem you rely on as a organization (such as blockchain) +- Developing brand awareness as an organization that values open source +- Thanking open source developers for building libraries that complement the product your organization offers -If the open source contributor you want to sponsor does not have a sponsored developer or organization profile, you can encourage the contributor to create a sponsored developer or organization profile. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). + +{% data 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 %} + +{% data reusables.sponsors.manage-updates-for-orgs %} + +If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. For more information, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)." + +If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data reusables.sponsors.sponsorships-not-tax-deductible %} @@ -27,30 +42,20 @@ If the open source contributor you want to sponsor does not have a sponsored dev {% endnote %} -### Sponsoring a developer +### Sponsoring an account -Before you can sponsor a developer, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)." +Before you can sponsor an account, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)." -1. On {% data variables.product.product_name %}, navigate to the profile of the person you want to sponsor. -2. Under the developer's name, click **Sponsor**. ![Sponsor button](/assets/images/help/profile/sponsor-button.png) +1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor. +1. Navigate to your sponsorship dashboard for the account. + - To sponsor a developer, under the developer's name, click **Sponsor**. ![Sponsor button](/assets/images/help/profile/sponsor-button.png) + - To sponsor an organization, to the right of the 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.select-a-tier %} +{% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} ![Edit payment button](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) {% data reusables.sponsors.who-can-see-your-sponsorship %} ![Radio buttons to choose who can see your sponsorship](/assets/images/help/sponsors/who-can-see-sponsorship.png) -{% data reusables.sponsors.developer-sponsored-choose-updates %} -7. Click **Sponsor _DEVELOPER_**. ![Sponsor developer button](/assets/images/help/sponsors/sponsor-developer-button.png) - -### Sponsoring an organization - -Before you can sponsor an organization, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)." - -1. On {% data variables.product.product_name %}, navigate to the page of the organization you want to sponsor. -2. Next to the the organization's name, click **Sponsor**. ![Sponsor button](/assets/images/help/sponsors/sponsor-org-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.select-sponsorship-billing %} - ![Edit payment button](/assets/images/help/sponsors/edit-org-sponsorship-payment-button.png) -{% data reusables.sponsors.who-can-see-your-sponsorship %} - ![Radio buttons to choose who can see your sponsorship](/assets/images/help/sponsors/who-can-see-org-sponsorship.png) -{% data reusables.sponsors.org-sponsored-choose-updates %} -7. Click **Sponsor _ORGANIZATION_**. ![Sponsor organization button](/assets/images/help/sponsors/sponsor-org-confirm-button.png) +{% data reusables.sponsors.choose-updates %} +{% data reusables.sponsors.sponsor-account %} diff --git a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 8504c6fad5..62daa89c40 100644 --- a/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/ko-KR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -7,34 +7,25 @@ versions: free-pro-team: '*' --- +### About sponsors and sponsorships + You can view analytics on your current and past sponsorships, the payments you've received from sponsors, and events, such as cancellations and sponsor tier changes for your sponsorships. You can also view activity such as new sponsorships, changes to sponsorships, and canceled sponsorships. You can filter the list of activities by date. You can also export sponsorship data for the account you're viewing in CSV or JSON format. -You access all of this information from your Sponsors dashboard. - -### Viewing your Sponsors dashboard - -1. In the upper-right corner of any page, click your profile photo, then click **{% data variables.product.prodname_sponsors %}**. ![{% data variables.product.prodname_sponsors %} button](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. In the list that's displayed, to the right of the account or organization whose Sponsors dashboard you want to view, click **Dashboard**. ![Developer sponsors dashboard button](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) - ### Viewing your sponsors and sponsorships -1. Go to your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard). -{% data reusables.sponsors.navigate-to-sponsors-tab %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. Optionally, to filter your sponsors by tier, use the **Filter** drop-down menu, click **Active tiers** or **Retired tiers**, and select a tier. ![Drop-down menu to filter by tier](/assets/images/help/sponsors/filter-drop-down.png) ### Viewing recent sponsorship activity -1. Go to your your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard). +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. In the left sidebar, click **Activity**. ![Activity tab](/assets/images/help/sponsors/activity-tab.png) ### Exporting your sponsorship data -1. Go to your your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard). +If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsors-tab %} 1. Click **Export all**. ![Export all button](/assets/images/help/sponsors/export-all.png) - - This button is not displayed if you don't have any sponsors. - -1. Choose a timeframe and a format for the data you'd like to export, then click **Start export**. ![Options for data export](/assets/images/help/sponsors/export-your-sponsors.png) - - {% data variables.product.prodname_dotcom %} starts exporting data for all of your sponsors for the month you selected. You'll be emailed shortly with an attachment containing the data. After the export is complete you can export another month of data. You can export up to 10 sets of data an hour for any of your sponsored organizations or user accounts. +1. Choose a timeframe and a format for the data you'd like to export, then click **Start export**. ![Options for data export](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/ko-KR/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/ko-KR/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 092b539416..767490b515 100644 --- a/translations/ko-KR/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/ko-KR/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -36,7 +36,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist {% endwindows %} - `BRANCH-NAME`: The default branch for your current project, for example, `main` or `gh-pages`. ```shell - $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME + $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME # Filter the specified branch in your directory and remove empty commits > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) > Ref 'refs/heads/BRANCH-NAME' was rewritten 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 a77f8603ba..0569432f90 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 @@ -21,6 +21,11 @@ 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)." +{% 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. 여기에는 다음이 포함됩니다. @@ -41,7 +46,8 @@ 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. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +- 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 diff --git a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/index.md b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/index.md index fb095cfc5f..bbe4472b6b 100644 --- a/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/index.md +++ b/translations/ko-KR/content/github/visualizing-repository-data-with-graphs/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repository-graphs %} {% link_in_list /viewing-a-summary-of-repository-activity %} {% link_in_list /viewing-a-projects-contributors %} - {% link_in_list /viewing-traffic-to-a-repository %} - {% topic_link_in_list /analyzing-changes-to-a-repositorys-content %} {% link_in_list /visualizing-commits-in-a-repository %} {% link_in_list /visualizing-additions-and-deletions-to-content-in-a-repository %} {% topic_link_in_list /understanding-connections-between-repositories %} {% link_in_list /viewing-a-repositorys-network %} {% link_in_list /listing-the-forks-of-a-repository %} - {% link_in_list /about-the-dependency-graph %} {% link_in_list /exploring-the-dependencies-of-a-repository %} - diff --git a/translations/ko-KR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ko-KR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index e60ecfd486..873337f03e 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/ko-KR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -51,7 +51,7 @@ Your theme includes default layouts, includes, and stylesheets that will automat 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: page + layout: post title: "POST TITLE" date: YYYY-MM-DD hh:mm:ss -0000 categories: CATEGORY-1 CATEGORY-2 diff --git a/translations/ko-KR/content/github/working-with-github-pages/index.md b/translations/ko-KR/content/github/working-with-github-pages/index.md index bd6f2fc27e..d9cf723b62 100644 --- a/translations/ko-KR/content/github/working-with-github-pages/index.md +++ b/translations/ko-KR/content/github/working-with-github-pages/index.md @@ -23,15 +23,11 @@ versions: {% topic_link_in_list /getting-started-with-github-pages %} {% link_in_list /about-github-pages %} {% link_in_list /creating-a-github-pages-site %} - {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} - {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} - {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} - {% link_in_list /unpublishing-a-github-pages-site %} {% topic_link_in_list /setting-up-a-github-pages-site-with-jekyll %} {% link_in_list /about-github-pages-and-jekyll %} @@ -42,9 +38,7 @@ versions: {% link_in_list /adding-a-theme-to-your-github-pages-site-using-jekyll %} {% link_in_list /about-jekyll-build-errors-for-github-pages-sites %} {% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %} - {% topic_link_in_list /configuring-a-custom-domain-for-your-github-pages-site %} {% link_in_list /about-custom-domains-and-github-pages %} {% link_in_list /managing-a-custom-domain-for-your-github-pages-site %} {% link_in_list /troubleshooting-custom-domains-and-github-pages %} - diff --git a/translations/ko-KR/content/github/working-with-github-support/index.md b/translations/ko-KR/content/github/working-with-github-support/index.md index 176ea10515..1ea83fac6b 100644 --- a/translations/ko-KR/content/github/working-with-github-support/index.md +++ b/translations/ko-KR/content/github/working-with-github-support/index.md @@ -2,6 +2,7 @@ title: Working with GitHub Support redirect_from: - /categories/working-with-github-support + - /forum versions: free-pro-team: '*' --- diff --git a/translations/ko-KR/content/graphql/README.md b/translations/ko-KR/content/graphql/README.md new file mode 100644 index 0000000000..f29fbc5131 --- /dev/null +++ b/translations/ko-KR/content/graphql/README.md @@ -0,0 +1,10 @@ +# GraphQL + +The `/content/graphql` directory is where the GitHub GraphQL API docs live! + +* The `/content/graphql/guides` and `/content/graphql/overview` directories contain articles that are human-editable. +* The `/content/graphql/reference` directory contains an article for each GraphQL data type used in the GitHub GraphQL API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/graphql/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/graphql/README.md`](/lib/graphql/README.md). + + **As a result, we cannot accept contributions to GraphQL API reference content in this repository.** diff --git a/translations/ko-KR/content/graphql/overview/explorer.md b/translations/ko-KR/content/graphql/overview/explorer.md index f87b12b44e..74540b78a4 100644 --- a/translations/ko-KR/content/graphql/overview/explorer.md +++ b/translations/ko-KR/content/graphql/overview/explorer.md @@ -7,6 +7,6 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +layout: graphql-explorer --- -You can access GitHub's GraphQL Explorer at https://developer.github.com/v4/explorer. diff --git a/translations/ko-KR/content/packages/guides/about-github-container-registry.md b/translations/ko-KR/content/packages/guides/about-github-container-registry.md new file mode 100644 index 0000000000..981bc862a0 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/about-github-container-registry.md @@ -0,0 +1,94 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/about-github-container-registry + - /packages/managing-container-images-with-github-container-registry +versions: + free-pro-team: '*' +--- + +{% note %} + +**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)." + +{% endnote %} + +### About {% 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)." + +{% data variables.product.prodname_github_container_registry %} has different hosting locations, permission, and visibility than other package registries. + +| | 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. + +For more information, see "[About scopes and permissions for {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)." + +### Supported formats + +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: + +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) + +The {% data variables.product.prodname_github_container_registry %} hosts containers at `ghcr.io/OWNER/IMAGE-NAME`. + +| Package client | Language | Package format | 설명 | +| -------------- | -------- | -------------- | ------------------------- | +| Docker CLI | N/A | `Dockerfile` | Docker container support. | + + +#### Manifest Lists/Image Indexes + +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. + +### Visibility and access permissions for container images + +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. + +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. + +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. + +| 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. | + +For more information, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." + +### About scopes and permissions for {% data variables.product.prodname_github_container_registry %} + +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. + +| 범위 | 설명 | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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)." | + +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)." + +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)." + +### About billing for {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.billing-for-container-registry %} + +### Contacting support + +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). + +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: + +* 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. diff --git a/translations/ko-KR/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md b/translations/ko-KR/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md new file mode 100644 index 0000000000..1d66526320 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md @@ -0,0 +1,69 @@ +--- +title: Configuring access control and visibility for container images +intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### Configuring access to container images for your personal account + +If you have admin permissions to a user-account owned container image, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)." + +{% data reusables.package_registry.package-settings-from-user-level %} +1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a user account. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) +1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) + +The selected users will automatically be given access and don't need to accept an invitation first. + +### Configuring access to container images for an organization + +If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)." + +If your package is owned by an organization and private, then you can only give access to other organization members or teams. + +For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% data reusables.package_registry.package-settings-from-org-level %} +1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) +1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) + +The selected users or teams will automatically be given access and don't need to accept an invitation first. + +### Configuring visibility of container images for your personal account + +When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings. + +A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. + +{% data reusables.package_registry.package-settings-from-user-level %} +5. Under "Danger Zone", choose a visibility setting: + - To make the container image visible to anyone, click **Make public**. + {% warning %} + + **Warning:** Once you make a package public, you cannot make it private again. + + {% endwarning %} + - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) + +### Configuring visibility of container images for an organization + +When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings. + +A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. + +For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% data reusables.package_registry.package-settings-from-org-level %} +5. Under "Danger Zone", choose a visibility setting: + - To make the container image visible to anyone, click **Make public**. + {% warning %} + + **Warning:** Once you make a package public, you cannot make it private again. + + {% endwarning %} + - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/ko-KR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md new file mode 100644 index 0000000000..5a827f2186 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -0,0 +1,195 @@ +--- +title: Configuring Apache Maven for use with GitHub Packages +intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Authenticating to {% 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 Apache Maven by editing your *~/.m2/settings.xml* file to include your personal access token. Create a new *~/.m2/settings.xml* file if one doesn't exist. + +In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your personal access token. + +In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}*REPOSITORY* with the name of the repository you'd like to publish a package to or install a package from, and *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. + +If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag. + +{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` +{% endif %} + +#### 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, {% data variables.product.prodname_dotcom %} will publish a package named `com.example:test` in a repository called `OWNER/test`. + +If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository. + +For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + +1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing + +{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation enabled: + {% endif %} + ``` + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + ``` + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation disabled: + ``` + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + ``` + {% endif %} +2. Publish the package. + + ```shell + $ mvn deploy + ``` + +{% data reusables.package_registry.viewing-packages %} + +### Installing a package + +To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation. + +{% data reusables.package_registry.authenticate-step %} +2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package. + + ``` + + + com.example + test + 1.0.0-SNAPSHOT + + + ``` +3. Install the package. + + ```shell + $ mvn install + ``` + +### 더 읽을거리 + +- "[Configuring Gradle for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-gradle-for-use-with-github-packages)" +- "[Deleting a package](/packages/manage-packages/deleting-a-package/)" diff --git a/translations/ko-KR/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-docker-for-use-with-github-packages.md new file mode 100644 index 0000000000..61833f3204 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -0,0 +1,213 @@ +--- +title: Configuring Docker for use with GitHub Packages +intro: 'You can configure the Docker client to use {% data variables.product.prodname_registry %} to publish and retrieve docker images.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### About Docker and {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +{% if enterpriseServerVersions contains currentVersion %} + +Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." + +{% endif %} + +### Authenticating to {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Authenticating with a personal access token + +{% data reusables.package_registry.required-scopes %} + +You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command. + +To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file. + +{% if currentVersion == "free-pro-team@latest" %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + ``` +{% endraw %} +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + +To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. + +For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)." + +#### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publishing an image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% note %} + +**Note:** Image names must only use lowercase letters. + +{% endnote %} + +{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. + +{% data reusables.package_registry.viewing-packages %} + +1. Determine the image name and ID for your docker image using `docker images`. + ```shell + $ docker images + > < > + > REPOSITORY TAG IMAGE ID CREATED SIZE + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + ``` +2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} +3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time, +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% else %} + ```shell + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} +4. Publish the image to +{% data variables.product.prodname_registry %}. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} + {% note %} + + **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. + + {% endnote %} + +#### Example publishing a Docker image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} + +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` + +{% endif %} + +You can publish a new Docker image for the first time and name it `monalisa`. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +# Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} +```shell +# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` +{% endif %} + +### Downloading an image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %} and *TAG_NAME* with tag for the image you want to install. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% else %} +```shell +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} + +{% note %} + +**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. + +{% endnote %} + +### 더 읽을거리 + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ko-KR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md new file mode 100644 index 0000000000..5a16a9b1c8 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -0,0 +1,196 @@ +--- +title: Configuring `dotnet` CLI for use with GitHub Packages +intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages + - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Authenticating to {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Authenticating with a personal access token + +{% data reusables.package_registry.required-scopes %} + +To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client. + +You must replace: +- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}. +- `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 %} +- `HOSTNAME` with the host name for your {% data variables.product.prodname_ghe_server %} instance. + +If your instance has subdomain isolation enabled: +{% endif %} + +```xml + + + + + + + + + + + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```xml + + + + + + + + + + + + + +``` +{% endif %} + +#### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publishing a package + +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file. When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Create a new project. + ```shell + dotnet new console --name OctocatApp + ``` +3. Add your project's specific information to your project's file, which ends in *.csproj*. You must replace: + - `OWNER` with the name of the user or organization account that owns the repository containing your project. + - `REPOSITORY` with the name of the repository containing the package you want to publish. + - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion %} + - `HOSTNAME` with the host name for your {% data variables.product.prodname_ghe_server %} instance.{% endif %} + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + ``` +4. Package the project. + ```shell + dotnet pack --configuration Release + ``` + +5. Publish the package using the `key` you specified in the *nuget.config* file. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" + ``` + +### Publishing multiple packages to the same repository + +To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. + +For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository: + +``` xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +### Installing a package + +Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. + +{% data reusables.package_registry.authenticate-step %} + +2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use: + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + ``` + +3. Install the packages with the `restore` command. + ```shell + dotnet restore + ``` + +### 더 읽을거리 + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ko-KR/content/packages/guides/configuring-gradle-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-gradle-for-use-with-github-packages.md new file mode 100644 index 0000000000..f0518315b9 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/configuring-gradle-for-use-with-github-packages.md @@ -0,0 +1,215 @@ +--- +title: Configuring Gradle for use with GitHub Packages +intro: 'You can configure Gradle to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Authenticating to {% 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 Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your personal access token. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository. + +{% if enterpriseServerVersions contains currentVersion %} +Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your +{% data variables.product.prodname_ghe_server %} instance. +{% endif %} + +Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. + +{% note %} + +**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)." + +{% endnote %} + +##### Example using Gradle Groovy for a single package in a repository + +```shell +plugins { + id("maven-publish") +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } +} +``` + +##### Example using Gradle Groovy for multiple packages in the same repository + +```shell +plugins { + id("maven-publish") apply false +} + +subprojects { + apply plugin: "maven-publish" + publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } + } +} +``` + +##### Example using Kotlin DSL for a single package in the same repository + +```shell +plugins { + `maven-publish` +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } +} +``` + +##### Example using Kotlin DSL for multiple packages in the same repository + +```shell +plugins { + `maven-publish` apply false +} + +subprojects { + apply(plugin = "maven-publish") + configure { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } + } +} +``` + + #### Authenticating with the `GITHUB_TOKEN` + + {% data reusables.package_registry.package-registry-with-github-tokens %} + + For more information about using `GITHUB_TOKEN` with Maven, see "[Publishing Java packages with Maven](/actions/language-and-framework-guides/publishing-java-packages-with-maven#publishing-packages-to-github-packages)." + + ### Publishing a package + + {% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository. + + {% data reusables.package_registry.viewing-packages %} + + {% data reusables.package_registry.authenticate-step %} + 2. After creating your package, you can publish the package. + + ```shell + $ gradle publish + ``` + +### Installing a package + +You can install a package by adding the package as a dependency to your project. For more information, see "[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" in the Gradle documentation. + +{% data reusables.package_registry.authenticate-step %} +2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. + + Example using Gradle Groovy: + ```shell + dependencies { + implementation 'com.example:package' + } + ``` + Example using Kotlin DSL: + ```shell + dependencies { + implementation("com.example:package") + } + ``` + +3. Add the maven plugin to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. + + Example using Gradle Groovy: + ```shell + plugins { + id 'maven' + } + ``` + Example using Kotlin DSL: + ```shell + plugins { + `maven` + } + ``` + + 3. Install the package. + + ```shell + $ gradle install + ``` + +### 더 읽을거리 + +- "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)" +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ko-KR/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-npm-for-use-with-github-packages.md new file mode 100644 index 0000000000..a7b7163cfe --- /dev/null +++ b/translations/ko-KR/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -0,0 +1,200 @@ +--- +title: Configuring npm for use with GitHub Packages +intro: 'You can configure npm to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in an npm project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Authenticating to {% 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 npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token. + +To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +//HOSTNAME/_registry/npm/:_authToken=TOKEN +``` +{% endif %} + +To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address. + +If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +$ npm login --scope=@OWNER --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} + +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +#### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publishing a package + +{% note %} + +**Note:** Package names and scopes must only use lowercase letters. + +{% endnote %} + +By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. You can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation. + +You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)." + +You can set up the scope mapping for your project using either a local *.npmrc* file in the project or using the `publishConfig` option in the *package.json*. {% data variables.product.prodname_registry %} only supports scoped npm packages. Scoped packages have names with the format of `@owner/name`. Scoped packages always begin with an `@` symbol. You may need to update the name in your *package.json* to use the scoped name. For example, `"name": "@codertocat/hello-world-npm"`. + +{% data reusables.package_registry.viewing-packages %} + +#### Publishing a package using a local *.npmrc* file + +You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +1. Verify the name of your package in your project's *package.json*. The `name` field must contain the scope and the name of the package. For example, if your package is called "test", and you are publishing to the "My-org" +{% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`. +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +#### Publishing a package using `publishConfig` in the *package.json* file + +You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation. + +1. Edit the *package.json* file for your package and include a `publishConfig` entry. + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation enabled: + {% endif %} + ```shell + "publishConfig": { + "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + }, + ``` + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation disabled: + ```shell + "publishConfig": { + "registry":"https://HOSTNAME/_registry/npm/" + }, + ``` + {% endif %} +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +### Publishing multiple packages to the same repository + +To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package. + +To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. + +{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name. + +```shell +"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", +``` + +### Installing a package + +You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation. + +By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." + +You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency. + + ``` + { + "name": "@my-org/server", + "version": "1.0.0", + "description": "Server app that uses the @octo-org/octo-app package", + "main": "index.js", + "author": "", + "license": "MIT", + "dependencies": { + "@octo-org/octo-app": "1.0.0" + } + } + ``` +5. Install the package. + + ```shell + $ npm install + ``` + +#### Installing packages from other organizations + +By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}/OWNER +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +registry=https://HOSTNAME/_registry/npm/OWNER +@OWNER:registry=https://HOSTNAME/_registry/npm/ +@OWNER:registry=https://HOSTNAME/_registry/npm/ +``` +{% endif %} + +### 더 읽을거리 + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ko-KR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/ko-KR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md new file mode 100644 index 0000000000..5f7756b91e --- /dev/null +++ b/translations/ko-KR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -0,0 +1,149 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### 빌드전 요구 사양 + +- You must have rubygems 2.4.1 or higher. To find your rubygems version: + + ```shell + $ gem --version + ``` + + - You must have bundler 1.6.4 or higher. To find your Bundler version: + ```shell + $ bundle --version + Bundler version 1.13.7 + ``` + + - Install keycutter to manage multiple credentials. To install keycutter: + ```shell + $ gem install keycutter + ``` + +### Authenticating to {% 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. + +```shell +--- +:github: Bearer TOKEN +``` + +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. + +```shell +--- +:backtrace: false +:bulk_threshold: 1000 +:sources: +- https://rubygems.org/ +- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ +:update_sources: true +:verbose: true + +``` + +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 %} + +```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. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Build the package from the *gemspec* to create the *.gem* package. + ```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 %} + + ```shell + $ gem push --key github \ + --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem + ``` + +### 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.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 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 %} + + ``` + source "https://rubygems.org" + + gem "rails" + + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do + gem "GEM NAME" + end + ``` + +3. 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). + + ``` + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" + source "https://rubygems.org" + + gem "rails" + gem "GEM NAME" + ``` + +4. Install the package: + ```shell + $ gem install octo-gem --version "0.1.1" + ``` + +### 더 읽을거리 + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ko-KR/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/ko-KR/content/packages/guides/connecting-a-repository-to-a-container-image.md new file mode 100644 index 0000000000..545d19db19 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -0,0 +1,83 @@ +--- +title: Connecting a repository to a container image +intro: 'You can link a repository with a container image locally and on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image +versions: + free-pro-team: '*' +--- + +When you link a container image with a repository, the package landing page will show information and links from the repository, such as the README. + +To connect a repository and a container image on {% data variables.product.prodname_dotcom %}, they must share the same owner on {% data variables.product.prodname_dotcom %}. For example, both `my_repo` and `hello_docker` are owned by the user `monalisa`: +```shell +https://github.com/monalisa/my_repo +https://github.com/monalisa/hello_docker +``` + +### Connecting a repository to a user-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Connecting a repository to an organization-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Connecting a repository to a container image on the command line + +1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details: + + ```shell + LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + ``` + For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile: + ```shell + LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + ``` + For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. + +2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`. + + ```shell + $ docker build -t hello_docker . + ``` +3. Optionally, review details for the Docker image you want to tag. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +4. Tag your Docker image with your desired image name and hosting destination. + ```shell + $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG + ``` + 예시: + ```shell + $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest + ``` + +5. If you haven't already, authenticate to + +{% data variables.product.prodname_github_container_registry %}. For more information, see "[Authenticating to GitHub Container Registry](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-github-container-registry)." + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + > Login Succeeded + ``` + {% endraw %} +6. Push your container image to {% data variables.product.prodname_github_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG + ``` + 예시: + ```shell + $ docker push ghcr.io/monalisa/hello_docker:latest + ``` diff --git a/translations/ko-KR/content/packages/guides/container-guides-for-github-packages.md b/translations/ko-KR/content/packages/guides/container-guides-for-github-packages.md new file mode 100644 index 0000000000..31b8f63889 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/container-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Container guides for GitHub Packages +shortTitle: Container guides for GitHub Packages +intro: 'You can publish and retrieve Docker images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/ko-KR/content/packages/guides/deleting-a-container-image.md b/translations/ko-KR/content/packages/guides/deleting-a-container-image.md new file mode 100644 index 0000000000..33451deeaa --- /dev/null +++ b/translations/ko-KR/content/packages/guides/deleting-a-container-image.md @@ -0,0 +1,33 @@ +--- +title: Deleting a container image +intro: 'You can delete a version of a private container image using GraphQL or on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### About package deletion + +You can remove an entire container image or a specific version on {% data variables.product.prodname_dotcom %}. To delete a container image, you must use the UI. Using GraphQL to delete a container image is not supported at this time. + +To delete a container image, you must have admin permissions to the container image. + +When deleting public packages, be aware that you may break projects that depend on your package. + +### Deleting a version of a user-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Deleting a version of an organization-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) diff --git a/translations/ko-KR/content/packages/guides/enabling-improved-container-support.md b/translations/ko-KR/content/packages/guides/enabling-improved-container-support.md new file mode 100644 index 0000000000..d0b4d98741 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/enabling-improved-container-support.md @@ -0,0 +1,39 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/enabling-improved-container-support +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + + ![Options to enable public or private packages ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/ko-KR/content/packages/guides/index.md b/translations/ko-KR/content/packages/guides/index.md new file mode 100644 index 0000000000..fb2875e7ec --- /dev/null +++ b/translations/ko-KR/content/packages/guides/index.md @@ -0,0 +1,33 @@ +--- +title: 안내서 +shortTitle: 안내서 +intro: 'These guides help you configure {% data variables.product.prodname_actions %} or your package client to work with {% data variables.product.prodname_registry %}.' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem + - /packages/using-github-packages-with-your-projects-ecosystem +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Table of Contents + +{% topic_link_in_list /package-client-guides-for-github-packages %} + {% link_in_list /using-github-packages-with-github-actions %} + {% link_in_list /configuring-apache-maven-for-use-with-github-packages %} + {% link_in_list /configuring-gradle-for-use-with-github-packages %} + {% link_in_list /configuring-npm-for-use-with-github-packages %} + {% link_in_list /configuring-dotnet-cli-for-use-with-github-packages %} + {% link_in_list /configuring-rubygems-for-use-with-github-packages %} +{% topic_link_in_list /container-guides-for-github-packages %} + {% link_in_list /configuring-docker-for-use-with-github-packages %} + {% link_in_list /about-github-container-registry %} + {% link_in_list /migrating-to-github-container-registry-for-docker-images %} + {% link_in_list /enabling-improved-container-support %} + {% link_in_list /configuring-access-control-and-visibility-for-container-images %} + {% link_in_list /connecting-a-repository-to-a-container-image %} + {% link_in_list /pushing-and-pulling-docker-images %} + {% link_in_list /deleting-a-container-image %} + diff --git a/translations/ko-KR/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md b/translations/ko-KR/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md new file mode 100644 index 0000000000..0a37abf195 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md @@ -0,0 +1,115 @@ +--- +title: Migrating to GitHub Container Registry for Docker images +intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate to the new {% data variables.product.prodname_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images +versions: + free-pro-team: '*' +--- + +### Key differences between {% data variables.product.prodname_github_container_registry %} and the Docker package registry + +{% data reusables.package_registry.container-registry-beta %} + +The {% data variables.product.prodname_github_container_registry %} supersedes the existing Packages Docker registry and is optimized to support some of the unique needs of containers. + +{% data reusables.package_registry.container-registry-feature-highlights %} + +For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." + +### Billing changes + +{% data reusables.package_registry.billing-for-container-registry %} + +### Domain changes + +The domain for the {% data variables.product.prodname_container_registry %} is `ghcr.io`. + +| Registry | Example URL | +| ----------------------------------------------------------------- | --------------------------------------------------- | +| {% data variables.product.prodname_registry %} Docker registry | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` | +| {% data variables.product.prodname_github_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME` | + +### Authenticating with the container registry + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}. + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Migrating a Docker image using the Docker CLI + +To move Docker images that you host on {% data variables.product.prodname_registry %} Docker registry, you must republish the images to {% data variables.product.prodname_container_registry %}. We recommend republishing your existing Docker images using the command line on your local machine. + +1. Sign in to the Docker registry using a temporary PAT with at least the `read:packages` scope. This PAT will only be used to sign in to the Docker registry to pull down images and can be deleted afterward. + {% raw %} + ```shell + $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin + ``` + {% endraw %} +2. Pull down the image you'd like to migrate, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with tag for the image you want to install. For example, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` pulls the latest tag of the `octoshift/octoshift` image in the octo-org organization. + ```shell + $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + +3. Re-tag the image with the new domain and a new image name. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. Use the same URL that you used in the previous step for the SOURCE URL. Replace the TARGET_OWNER with the user or organization that you are migrating the container image to and replace the TARGET_IMAGE_NAME with the new {% data variables.product.prodname_container_registry %} image name. + ```shell + $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION + ``` + +4. Sign in to the new + +{% data variables.product.prodname_container_registry %}. We recommend creating a new PAT limited to the `read:packages` and `write:packages` scopes since you no longer need the `repo` scope and your previous PAT may not have the `write:packages` scope. + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + ``` + {% endraw %} +5. Push your re-tagged image to the {% data variables.product.prodname_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION + ``` + +### Updating your {% data variables.product.prodname_actions %} workflow + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers. + +1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)." + +2. In your {% data variables.product.prodname_actions %} workflow file, update the package url from `https://docker.pkg.github.com` to `ghcr.io`. + +3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. {% data variables.product.prodname_github_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." + +4. In your {% data variables.product.prodname_actions %} workflow file, update the authentication PAT by replacing your Docker registry PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) with a new variable for your {% data variables.product.prodname_container_registry %} PAT, such as {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}. + +#### Example of updated workflow + +If part of your workflow accessed a Docker image hosted by the Docker registry like this: + +{% raw %} +```yaml +echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin +docker pull docker.pkg.github.com/github/octoshift/octoshift:latest +docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest +docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA +``` +{% endraw %} + +Then you'll need to update your workflow with the new {% data variables.product.prodname_container_registry %} URL and PAT like this: + +{% raw %} +```yaml +# new login with new container registry url and PAT +echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin +# new container registry urls added +docker pull ghcr.io/github/octoshift:latest +docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest +docker push ghcr.io/github/octoshift:$GITHUB_SHA +``` +{% endraw %} diff --git a/translations/ko-KR/content/packages/guides/package-client-guides-for-github-packages.md b/translations/ko-KR/content/packages/guides/package-client-guides-for-github-packages.md new file mode 100644 index 0000000000..6f77e8b9bd --- /dev/null +++ b/translations/ko-KR/content/packages/guides/package-client-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Package client guides for GitHub Packages +shortTitle: Package client guides for GitHub Packages +intro: 'You can publish and retrieve package client images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/ko-KR/content/packages/guides/pushing-and-pulling-docker-images.md b/translations/ko-KR/content/packages/guides/pushing-and-pulling-docker-images.md new file mode 100644 index 0000000000..de286a6be1 --- /dev/null +++ b/translations/ko-KR/content/packages/guides/pushing-and-pulling-docker-images.md @@ -0,0 +1,106 @@ +--- +title: Pushing and pulling Docker images +intro: 'You can store and manage Docker images in {% data variables.product.prodname_github_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +### Authenticating to {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Pushing container images + +This example pushes the latest version of `IMAGE-NAME`. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +This example pushes the `2.5` version of the image. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 + ``` + +When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + +### Pulling container images + +#### Pull by digest + +To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value. + +1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:` + ```shell + $ docker inspect ghcr.io/OWNER/IMAGE_NAME + ``` +2. Remove image locally as needed. + ```shell + $ docker rmi ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +3. Pull the container image with `@YOUR_SHA_VALUE` after the image name. + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs + ``` + +#### Pull by name + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME + ``` + +#### Pull by name and version + +Docker CLI example showing an image pulled by its name and the `1.14.1` version tag: + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1 + > 5e35bd43cf78: Pull complete + > 0c48c2209aab: Pull complete + > fd45dd1aad5a: Pull complete + > db6eb50c2d36: Pull complete + > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e + > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 + > ghcr.io/orgname/image-name/release:1.14.1 + ``` + +#### Pull by name and latest version + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest + > latest: Pulling from user/image-name + > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 + > Status: Downloaded newer image for ghcr.io/user/image-name:latest + > ghcr.io/user/image-name:latest + ``` + +### Building container images + +This example builds the `hello_docker` image: + ```shell + $ docker build -t hello_docker . + ``` + +### Tagging container images + +1. Find the ID for the Docker image you want to tag. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +2. Tag your Docker image using the image ID and your desired image name and hosting destination. + ```shell + $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest + ``` diff --git a/translations/ko-KR/content/packages/guides/using-github-packages-with-github-actions.md b/translations/ko-KR/content/packages/guides/using-github-packages-with-github-actions.md new file mode 100644 index 0000000000..b66eb8628a --- /dev/null +++ b/translations/ko-KR/content/packages/guides/using-github-packages-with-github-actions.md @@ -0,0 +1,55 @@ +--- +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 %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions + - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About {% data variables.product.prodname_registry %} with {% 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)." + +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 %} + +{% 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)." + +{% endif %} + +#### Authenticating to package registries on {% 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. + +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)." + +### Publishing a package using an action + +You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. + +{% data reusables.package_registry.actions-configuration %} + +### 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 %} + +{% 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 %} diff --git a/translations/ko-KR/content/packages/index.md b/translations/ko-KR/content/packages/index.md index e00d89f22a..c40765a9dc 100644 --- a/translations/ko-KR/content/packages/index.md +++ b/translations/ko-KR/content/packages/index.md @@ -2,31 +2,46 @@ title: GitHub Packages Documentation shortTitle: GitHub Packages intro: 'Learn to safely publish and consume packages, store your packages alongside your code, and share your packages privately with your team or publicly with the open source community. You can also automate your packages with {% data variables.product.prodname_actions %}.' +introLinks: + quickstart: /packages/quickstart + reference: /packages/manage-packages featuredLinks: - gettingStarted: - - /packages/publishing-and-managing-packages/about-github-packages - - /packages/getting-started-with-github-container-registry/about-github-container-registry - - /packages/getting-started-with-github-container-registry - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/publishing-and-managing-packages/publishing-a-package - - /packages/publishing-and-managing-packages/installing-a-package + guides: + - /packages/learn-github-packages + - /packages/guides/using-github-packages-with-github-actions + - /packages/manage-packages/installing-a-package popular: - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-apache-maven-for-use-with-github-packages + guideCards: + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/guides/enabling-improved-container-support + - /packages/guides/configuring-rubygems-for-use-with-github-packages +changelog: + - + title: Packages container support is an opt-in beta + date: '2020-11-17' + href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support + - + title: Organization admins access to containers + date: '2020-11-16' + href: https://github.blog/changelog/2020-11-16-packages-organization-admins-access-to-containers/ + - + title: Packages now respects IP allow list settings + date: '2020-11-12' + href: https://github.blog/changelog/2020-11-12-packages-now-respects-ip-allow-list-settings/ redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry - /github/managing-packages-with-github-package-registry +layout: product-landing versions: free-pro-team: '*' enterprise-server: '>=2.22' --- -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% link_with_intro /getting-started-with-github-container-registry %} -{% link_with_intro /managing-container-images-with-github-container-registry %} -{% link_with_intro /publishing-and-managing-packages %} -{% link_with_intro /using-github-packages-with-your-projects-ecosystem %} + + + + diff --git a/translations/ko-KR/content/packages/learn-github-packages/about-github-packages.md b/translations/ko-KR/content/packages/learn-github-packages/about-github-packages.md new file mode 100644 index 0000000000..e95c3765a2 --- /dev/null +++ b/translations/ko-KR/content/packages/learn-github-packages/about-github-packages.md @@ -0,0 +1,166 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/about-github-package-registry + - /github/managing-packages-with-github-package-registry/about-github-package-registry + - /github/managing-packages-with-github-packages/about-github-packages + - /packages/publishing-and-managing-packages/about-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About {% 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 %}. + +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. + +{% data variables.product.prodname_registry %} offers different package registries for commonly used packages, such as for Node, RubyGems, Apache Maven, Gradle, and Nuget. + +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.prodname_registry %} also offers a {% data variables.product.prodname_container_registry %} designed to support the unique needs of container images. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." + +{% data reusables.package_registry.container-registry-beta %} + +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + +{% endif %} + +#### Viewing packages + +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)." + +#### About package permissions and visibility + +| | 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 %} + +{% if currentVersion == "free-pro-team@latest" %} +### About billing for {% 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.container-registry-beta-billing-note %} +{% endif %} + +### Supported clients and formats + +{% 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 + +{% 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 | 설명 | 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 | 설명 | 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 | 설명 | 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` | + +{% note %} + +**Note:** Docker is not supported when subdomain isolation is disabled. + +{% endnote %} + +For more information about subdomain isolation, see "[Enabling subdomain isolation](/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)." + +{% 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)." +{% endif %} +### Authenticating to {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +### About scopes and permissions for package registries + +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. + +예시: +- 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)." + +| 범위 | 설명 | 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 | + +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. + +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)" + +### Managing packages + +You can a delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." + +You can 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 + +{% 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). + +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: + +* 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 + +{% else %} +If you need support for +{% data variables.product.prodname_registry %}, please contact your site administrators. + +{% endif %} diff --git a/translations/ko-KR/content/packages/learn-github-packages/core-concepts-for-github-packages.md b/translations/ko-KR/content/packages/learn-github-packages/core-concepts-for-github-packages.md new file mode 100644 index 0000000000..07b7774cd7 --- /dev/null +++ b/translations/ko-KR/content/packages/learn-github-packages/core-concepts-for-github-packages.md @@ -0,0 +1,28 @@ +--- +title: Core concepts for GitHub Packages +intro: 'Below is a list of common {% data variables.product.prodname_registry %} terms we use across our sites and documentation.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Package + +A package is a self-contained and reusable piece of software that includes code and metadata that a developer bundles together in a common place for others to use. A package's metadata may include the version number, name, and the code's dependencies. Packages simplify using and distributing solutions to common problems such as needing frameworks for developing or testing a project, linters to improve code quality, or industry-standard machine learning tools to power your application. Packages exist in many ecosystems. For example, you can package Node.js and Java code or container images. + +### Container + +A container is a unit of software designed to reliably deploy software in a standardized way on any platform. A container operates as an isolated virtual environment or instance that can run various software packages and components on the same host kernel as your operating system. Containers use fewer resources than virtual machines because they don't need to include their own virtual hardware to run. Containers are created using a container image file, such as a Dockerfile, and a container client or runtime program. + +### Container image + +A container image is a type of package archive that specifies the software requirements to run an app from a container. A container image typically includes the app's code, libraries, and runtime instructions. To ensure that the same image details are used wherever an image is deployed and run, a container image is automatically versioned and cannot be changed once a container image is built in a container. + +### Docker container + +A Docker container is a type of open source container built on the Docker platform. Docker's original image format has become the OCI (Open Container Initiative) Image Specification. For more information, see the "[Docker documentation](https://docs.docker.com/get-started/overview/)." diff --git a/translations/ko-KR/content/packages/learn-github-packages/index.md b/translations/ko-KR/content/packages/learn-github-packages/index.md new file mode 100644 index 0000000000..a21e10fe4c --- /dev/null +++ b/translations/ko-KR/content/packages/learn-github-packages/index.md @@ -0,0 +1,16 @@ +--- +title: Learn GitHub Packages +shortTitle: Learn GitHub Packages +intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.' +redirect_from: + - /packages/getting-started-with-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /about-github-packages %} +{% link_in_list /core-concepts-for-github-packages %} +{% link_in_list /publishing-a-package %} diff --git a/translations/ko-KR/content/packages/learn-github-packages/publishing-a-package.md b/translations/ko-KR/content/packages/learn-github-packages/publishing-a-package.md new file mode 100644 index 0000000000..41d764d306 --- /dev/null +++ b/translations/ko-KR/content/packages/learn-github-packages/publishing-a-package.md @@ -0,0 +1,37 @@ +--- +title: Publishing a package +intro: 'You can publish a package to {% data variables.product.prodname_registry %} to make the package available for others to download and re-use.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-a-package + - /packages/publishing-and-managing-packages/publishing-a-package +permissions: Anyone with write permissions for a repository can publish a package to that repository. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About published packages + +You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. {% data variables.product.product_name %} provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). + +{% data reusables.package_registry.public-or-private-packages %} A repository can contain more than one package. To prevent confusion, make sure the README and description clearly provide information about each package. + +{% if currentVersion == "free-pro-team@latest" %} +If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. +{% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +{% endif %} + +### Publishing a package + +You can publish a package to {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. + +1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +2. Authenticate to {% data variables.product.prodname_registry %} using your access token and the instructions for your package client. +3. Publish the package using the instructions for your package client. + +For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)." + +After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see “[Viewing packages](/packages/publishing-and-managing-packages/viewing-packages).” diff --git a/translations/ko-KR/content/packages/manage-packages/deleting-a-package.md b/translations/ko-KR/content/packages/manage-packages/deleting-a-package.md new file mode 100644 index 0000000000..dec649cf0b --- /dev/null +++ b/translations/ko-KR/content/packages/manage-packages/deleting-a-package.md @@ -0,0 +1,81 @@ +--- +title: Deleting a package +intro: 'You can delete a version of a private package using GraphQL or on {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/deleting-a-package + - /packages/publishing-and-managing-packages/deleting-a-package +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% if currentVersion == "free-pro-team@latest" %} +### About container image deletion + +To delete a container image package on {% data variables.product.product_name %}, see "[Deleting a container image](/packages/guides/deleting-a-container-image)." + +{% endif %} + +### About private package deletion + +You can only delete a specified version of a private package on {% data variables.product.product_name %} or with the GraphQL API. To remove an entire private package from appearing on {% data variables.product.product_name %}, you must delete every version of the package first. + +{% if currentVersion == "free-pro-team@latest" %} +### About public package deletion + +To avoid breaking projects that may depend on your packages, you cannot delete an entire public package or specific versions of a public package. + +Under special circumstances, such as for legal reasons or to conform with GDPR standards, you can ask {% data variables.contact.github_support %} to delete a public package for you, using [our contact form](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry). + +{% else %} + +At this time, {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} does not support deleting public packages. + +{% endif %} + +### Deleting a version of a private package on {% data variables.product.product_name %} + +To delete a private package version, you must have admin permissions in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +3. Click the name of the package that you want to delete. ![Package name](/assets/images/help/package-registry/select-pkg-cloud.png) +4. On the right, use the **Edit package** drop-down and select "Manage versions". ![Package name](/assets/images/help/package-registry/manage-versions.png) +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Deleting a version of a private package with GraphQL + +Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." + +Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token. + +{% if currentVersion == "free-pro-team@latest" %} +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +https://api.github.com/graphql +``` + +{% else %} + +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +HOSTNAME/graphql +``` + +{% endif %} + +To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface. + +For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)." + +You cannot delete an entire package, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %} diff --git a/translations/ko-KR/content/packages/manage-packages/index.md b/translations/ko-KR/content/packages/manage-packages/index.md new file mode 100644 index 0000000000..7f313028a1 --- /dev/null +++ b/translations/ko-KR/content/packages/manage-packages/index.md @@ -0,0 +1,18 @@ +--- +title: Managing GitHub packages +shortTitle: Managing GitHub packages +intro: 'You can publish new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-and-managing-packages + - /github/packages/publishing-and-managing-packages + - /packages/publishing-and-managing-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /viewing-packages %} +{% link_in_list /installing-a-package %} +{% link_in_list /deleting-a-package %} diff --git a/translations/ko-KR/content/packages/manage-packages/installing-a-package.md b/translations/ko-KR/content/packages/manage-packages/installing-a-package.md new file mode 100644 index 0000000000..007e344089 --- /dev/null +++ b/translations/ko-KR/content/packages/manage-packages/installing-a-package.md @@ -0,0 +1,29 @@ +--- +title: Installing a package +intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/installing-a-package + - /packages/publishing-and-managing-packages/installing-a-package +permissions: Anyone with read permissions for a repository can install a package from that repository. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About package installation + +You can search {% data variables.product.product_name %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)." + +After you find a package, you can read the package's description and installation and usage instructions on the package page. + +### Installing a package + +You can install a package from {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. + +1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[About tokens](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +2. Install the package using the instructions for your package client. + +For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)." diff --git a/translations/ko-KR/content/packages/manage-packages/viewing-packages.md b/translations/ko-KR/content/packages/manage-packages/viewing-packages.md new file mode 100644 index 0000000000..60395d2c8b --- /dev/null +++ b/translations/ko-KR/content/packages/manage-packages/viewing-packages.md @@ -0,0 +1,50 @@ +--- +title: Viewing packages +intro: 'You can see details about packages published to a repository, and narrow results by organization or user.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/viewing-packages + - /packages/publishing-and-managing-packages/viewing-packages +permissions: Anyone with read permissions to a repository can view the repository's packages. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About package views + +Packages must be installed at the repository level, but you can view all packages in an organization and all packages you've published. {% data reusables.package_registry.package-page-info %} + +### Viewing a repository's packages + +You can see all the packages in a repository and search for a specific package in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + +### Viewing an organization's packages + +You can see all the packages installed in an organization and search for a specific package installed in an organization's repositories. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. 조직 이름에서 클릭하십시오. +{% octicon "package" aria-label="The package icon" %} **Packages**. +{% data reusables.package_registry.navigate-to-packages %} + +### Viewing your packages + +You can see all the packages you've installed and search for a specific package you've installed across all organizations and repositories. + +{% data reusables.profile.access_profile %} +2. On the top of the profile page, in the main navigation, click **Packages**. ![Project tab](/assets/images/help/package-registry/user-packages-tab.png) +{% data reusables.package_registry.navigate-to-packages %} + +### 더 읽을거리 + +- "[Searching for packages](/github/searching-for-information-on-github/searching-for-packages)" diff --git a/translations/ko-KR/content/packages/quickstart.md b/translations/ko-KR/content/packages/quickstart.md new file mode 100644 index 0000000000..73639e8dd8 --- /dev/null +++ b/translations/ko-KR/content/packages/quickstart.md @@ -0,0 +1,110 @@ +--- +title: Quickstart for GitHub Packages +intro: 'Publish to {% data variables.product.prodname_registry %} in 5 minutes or less with {% data variables.product.prodname_actions %}.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Introduction + +You only need an existing {% data variables.product.prodname_dotcom %} repository to publish a package to {% data variables.product.prodname_registry %}. In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}. Feel free to create a new repository for this Quickstart. You can use it to test this and future {% data variables.product.prodname_actions %} workflows. + +### Publishing your package + +1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. Create a private repository if you’d like to delete this package later, public packages cannot be deleted. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clone the repository to your local machine. + {% raw %} + ```shell + $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git + $ cd YOUR-REPOSITORY + ``` + {% endraw %} +3. Create an `index.js` file and add a basic alert to say "Hello world!" + {% raw %} + ```javascript{:copy} + alert("Hello, World!"); + ``` + {% endraw %} +4. Initialize an npm package. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0` if you do not have any tests. Commit your changes and push them to +{% data variables.product.prodname_dotcom %}. + {% raw %} + ```shell + $ npm init + ... + package name: @YOUR-USERNAME/YOUR-REPOSITORY + ... + test command: exit 0 + ... + + $ npm install + $ git add index.js package.json package-lock.json + $ git commit -m "initialize npm package" + $ git push + ``` + {% endraw %} +5. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `release-package.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." +6. Copy the following YAML content into the `release-package.yml` file. + {% raw %} + ```yaml{:copy} + name: Node.js Package + + on: + release: + types: [created] + + jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm ci + - run: npm test + + publish-gpr: + needs: build + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + registry-url: https://npm.pkg.github.com/ + - run: npm ci + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + ``` + {% endraw %} +7. 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**. +8. **Merge** the pull request. +9. Navigate to the **Code** tab and create a new release to test the workflow. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." + +Creating a new release in your repository triggers the workflow to build and test your code. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. + +### Viewing your published package + +Packages are published at the repository level. You can see all the packages in a repository and search for a specific package. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + + +### Installing a published package + +Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)." + +### 다음 단계 + +The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more. + +Combining {% data variables.product.prodname_registry %} and {% 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_registry %} and {% data variables.product.prodname_actions %}: + +- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions +- "[Guides](/packages/guides)" for specific uses cases and examples diff --git a/translations/ko-KR/content/rest/README.md b/translations/ko-KR/content/rest/README.md new file mode 100644 index 0000000000..55aaa5edda --- /dev/null +++ b/translations/ko-KR/content/rest/README.md @@ -0,0 +1,10 @@ +# REST + +The `/content/rest` directory is where the GitHub REST API docs live! + +* The `/content/rest/guides` and `/content/rest/overview` directories contain regular articles. These are human-editable. +* The `/content/rest/reference` directory contains an article for each group of endpoints in the GitHub REST API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/rest/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/rest/README.md`](/lib/rest/README.md). + + **As a result, we cannot accept contributions to REST API reference content in this repository.** 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 9498083852..c0906ae0dd 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 @@ -373,7 +373,7 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]! [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore [issues-api]: /rest/reference/issues -[link-header]: http://www.w3.org/wiki/LinkHeader/ +[link-header]: https://www.w3.org/wiki/LinkHeader [conditional-requests]: /rest#conditional-requests [rate-limiting]: /rest#rate-limiting [rate-limiting]: /rest#rate-limiting diff --git a/translations/ko-KR/content/rest/overview/api-previews.md b/translations/ko-KR/content/rest/overview/api-previews.md index 3cdc9b7033..3fbdab9ba2 100644 --- a/translations/ko-KR/content/rest/overview/api-previews.md +++ b/translations/ko-KR/content/rest/overview/api-previews.md @@ -53,7 +53,7 @@ Create, list, update, and delete environments for pre-receive hooks. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### Integrations -Manage [integrations](/early-access/integrations/) through the API. +Manage [integrations](/v3/integrations) through the API. **Custom media type:** `machine-man-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/) {% endif %} diff --git a/translations/ko-KR/content/rest/overview/libraries.md b/translations/ko-KR/content/rest/overview/libraries.md index 169441d839..c44db06aa8 100644 --- a/translations/ko-KR/content/rest/overview/libraries.md +++ b/translations/ko-KR/content/rest/overview/libraries.md @@ -72,7 +72,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby diff --git a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md index 598d668d10..76a15da763 100644 --- a/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ko-KR/content/rest/overview/resources-in-the-rest-api.md @@ -262,13 +262,15 @@ You can then expand these templates using something like the [uri_template][uri] ### Pagination -Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/rest/reference/activity#events) for example. +Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `page` parameter. For some resources, you can also set a custom page size up to 100 with the `per_page` parameter. Note that for technical reasons not all endpoints respect the `per_page` parameter, see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -Note that page numbering is 1-based and that omitting the `?page` parameter will return the first page. +Note that page numbering is 1-based and that omitting the `page` parameter will return the first 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. For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. @@ -280,13 +282,17 @@ For more information on pagination, check out our guide on [Traversing with Pagi {% endnote %} -The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information: +The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information. 예시: Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" _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). The possible `rel` values are: diff --git a/translations/ko-KR/content/rest/overview/troubleshooting.md b/translations/ko-KR/content/rest/overview/troubleshooting.md index 719805a046..5865ff59ca 100644 --- a/translations/ko-KR/content/rest/overview/troubleshooting.md +++ b/translations/ko-KR/content/rest/overview/troubleshooting.md @@ -52,7 +52,7 @@ curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos #### Calls to OAuth Authorizations API -If you're making [OAuth Authorization API](/enterprise-server@2.22/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: +If you're making [OAuth Authorization API](/enterprise-server/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: ```bash curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}' diff --git a/translations/ko-KR/content/rest/reference/enterprise-admin.md b/translations/ko-KR/content/rest/reference/enterprise-admin.md index 209d878aff..8db2a549e6 100644 --- a/translations/ko-KR/content/rest/reference/enterprise-admin.md +++ b/translations/ko-KR/content/rest/reference/enterprise-admin.md @@ -57,6 +57,16 @@ The current version of your enterprise is returned in the response header of eve {% endif %} +{% if currentVersion == "free-pro-team@latest" %} + +## Audit log + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ## Billing diff --git a/translations/ko-KR/content/rest/reference/index.md b/translations/ko-KR/content/rest/reference/index.md index dfeb1f0648..d235a3280e 100644 --- a/translations/ko-KR/content/rest/reference/index.md +++ b/translations/ko-KR/content/rest/reference/index.md @@ -15,8 +15,6 @@ versions: {% link_in_list /apps %} {% link_in_list /billing %} {% link_in_list /checks %} - - {% link_in_list /codes-of-conduct %} {% link_in_list /code-scanning %} {% link_in_list /emojis %} @@ -39,6 +37,7 @@ versions: {% link_in_list /repos %} {% link_in_list /scim %} {% link_in_list /search %} +{% link_in_list /secret-scanning %} {% link_in_list /teams %} {% link_in_list /users %} {% link_in_list /permissions-required-for-github-apps %} diff --git a/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md b/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md index ded6db8934..3ce558cad2 100644 --- a/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ko-KR/content/rest/reference/permissions-required-for-github-apps.md @@ -819,10 +819,19 @@ _Teams_ * [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) - {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Permission on "secret scanning alerts" + +- [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) + +- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read) + +- [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permission on "security events" - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) diff --git a/translations/ko-KR/content/rest/reference/secret-scanning.md b/translations/ko-KR/content/rest/reference/secret-scanning.md new file mode 100644 index 0000000000..6c266b8488 --- /dev/null +++ b/translations/ko-KR/content/rest/reference/secret-scanning.md @@ -0,0 +1,12 @@ +--- +title: Secret scanning +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.secret-scanning.api-beta %} + +The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a private repository. For more information on secret scanning for private repositories, see "[Securing your repository](/github/administering-a-repository/securing-your-repository)." + +{% include rest_operations_at_current_path %} diff --git a/translations/ko-KR/data/glossaries/external.yml b/translations/ko-KR/data/glossaries/external.yml index acba35cda9..6ebca09a60 100644 --- a/translations/ko-KR/data/glossaries/external.yml +++ b/translations/ko-KR/data/glossaries/external.yml @@ -390,7 +390,7 @@ - term: main description: >- - The default development branch. Whenever you create a Git repository, a branch named "main" is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. + The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. - term: master description: >- diff --git a/translations/ko-KR/data/products.yml b/translations/ko-KR/data/products.yml index 413a59b62c..bb3e433dff 100644 --- a/translations/ko-KR/data/products.yml +++ b/translations/ko-KR/data/products.yml @@ -5,10 +5,12 @@ productsInOrder: - github - admin + - discussions - actions - 패키지 - developers - rest - graphql - insights + - education - desktop diff --git a/translations/ko-KR/data/release-notes/2-20/0.yml b/translations/ko-KR/data/release-notes/2-20/0.yml new file mode 100644 index 0000000000..5623123354 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/0.yml @@ -0,0 +1,44 @@ +--- +date: '2020-02-11' +sections: + features: + - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" + - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" + - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + changes: + - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/1.yml b/translations/ko-KR/data/release-notes/2-20/1.yml new file mode 100644 index 0000000000..e303f5525e --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/1.yml @@ -0,0 +1,21 @@ +--- +date: '2020-02-27' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + bugs: + - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/10.yml b/translations/ko-KR/data/release-notes/2-20/10.yml new file mode 100644 index 0000000000..58a38245c0 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/10.yml @@ -0,0 +1,21 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" + - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/11.yml b/translations/ko-KR/data/release-notes/2-20/11.yml new file mode 100644 index 0000000000..0bdd30cf96 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/11.yml @@ -0,0 +1,19 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/12.yml b/translations/ko-KR/data/release-notes/2-20/12.yml new file mode 100644 index 0000000000..5b286392f5 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/12.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + bugs: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + changes: + - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/13.yml b/translations/ko-KR/data/release-notes/2-20/13.yml new file mode 100644 index 0000000000..7388ff5103 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/13.yml @@ -0,0 +1,22 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/14.yml b/translations/ko-KR/data/release-notes/2-20/14.yml new file mode 100644 index 0000000000..d33fe2b58d --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/14.yml @@ -0,0 +1,13 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/15.yml b/translations/ko-KR/data/release-notes/2-20/15.yml new file mode 100644 index 0000000000..651811695b Binary files /dev/null and b/translations/ko-KR/data/release-notes/2-20/15.yml differ diff --git a/translations/ko-KR/data/release-notes/2-20/16.yml b/translations/ko-KR/data/release-notes/2-20/16.yml new file mode 100644 index 0000000000..4ca63bc213 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/16.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/17.yml b/translations/ko-KR/data/release-notes/2-20/17.yml new file mode 100644 index 0000000000..5f3bf87a25 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/17.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/18.yml b/translations/ko-KR/data/release-notes/2-20/18.yml new file mode 100644 index 0000000000..3aab7ba337 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/18.yml @@ -0,0 +1,26 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/19.yml b/translations/ko-KR/data/release-notes/2-20/19.yml new file mode 100644 index 0000000000..b686131852 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/19.yml @@ -0,0 +1,14 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/2.yml b/translations/ko-KR/data/release-notes/2-20/2.yml new file mode 100644 index 0000000000..78e2faa7e1 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/2.yml @@ -0,0 +1,28 @@ +--- +date: '2020-03-10' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + bugs: + - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + changes: + - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/20.yml b/translations/ko-KR/data/release-notes/2-20/20.yml new file mode 100644 index 0000000000..0cf4def9e0 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/20.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/21.yml b/translations/ko-KR/data/release-notes/2-20/21.yml new file mode 100644 index 0000000000..4b970a92ee --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/21.yml @@ -0,0 +1,15 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/22.yml b/translations/ko-KR/data/release-notes/2-20/22.yml new file mode 100644 index 0000000000..099ce93b0d --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/22.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/3.yml b/translations/ko-KR/data/release-notes/2-20/3.yml new file mode 100644 index 0000000000..23c25312e5 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/3.yml @@ -0,0 +1,15 @@ +--- +date: '2020-03-12' +sections: + bugs: + - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/4.yml b/translations/ko-KR/data/release-notes/2-20/4.yml new file mode 100644 index 0000000000..0f06a203cd --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/4.yml @@ -0,0 +1,18 @@ +--- +date: '2020-03-25' +sections: + bugs: + - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/5.yml b/translations/ko-KR/data/release-notes/2-20/5.yml new file mode 100644 index 0000000000..44115fdc71 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/5.yml @@ -0,0 +1,20 @@ +--- +date: '2020-04-07' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + bugs: + - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/6.yml b/translations/ko-KR/data/release-notes/2-20/6.yml new file mode 100644 index 0000000000..568f19954f --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/6.yml @@ -0,0 +1,27 @@ +--- +date: '2020-04-23' +sections: + security_fixes: + - '**HIGH**: OpenSSL has been updated to address [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 %}' + - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + bugs: + - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" + - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + changes: + - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% 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: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/7.yml b/translations/ko-KR/data/release-notes/2-20/7.yml new file mode 100644 index 0000000000..b377d90b66 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/7.yml @@ -0,0 +1,21 @@ +--- +date: '2020-05-05' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + bugs: + - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' + - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/8.yml b/translations/ko-KR/data/release-notes/2-20/8.yml new file mode 100644 index 0000000000..510bf779fb --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/8.yml @@ -0,0 +1,20 @@ +--- +date: '2020-05-19' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + bugs: + - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-20/9.yml b/translations/ko-KR/data/release-notes/2-20/9.yml new file mode 100644 index 0000000000..326818d711 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-20/9.yml @@ -0,0 +1,17 @@ +--- +date: '2020-06-02' +sections: + security_fixes: + - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + bugs: + - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/0.yml b/translations/ko-KR/data/release-notes/2-21/0.yml new file mode 100644 index 0000000000..cfd8a069f8 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/0.yml @@ -0,0 +1,72 @@ +--- +date: '2020-06-09' +sections: + features: + - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + security_fixes: + - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + bugs: + - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' + changes: + - 'The web notifications interface, including new [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - 'Admins can [enable security alerts](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' + - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/1.yml b/translations/ko-KR/data/release-notes/2-21/1.yml new file mode 100644 index 0000000000..9b802bd1f3 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/1.yml @@ -0,0 +1,20 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/10.yml b/translations/ko-KR/data/release-notes/2-21/10.yml new file mode 100644 index 0000000000..65b5d9c64c --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/10.yml @@ -0,0 +1,15 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/11.yml b/translations/ko-KR/data/release-notes/2-21/11.yml new file mode 100644 index 0000000000..ce20fbe36a --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/11.yml @@ -0,0 +1,18 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/12.yml b/translations/ko-KR/data/release-notes/2-21/12.yml new file mode 100644 index 0000000000..c347bb7aca --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/12.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/13.yml b/translations/ko-KR/data/release-notes/2-21/13.yml new file mode 100644 index 0000000000..06e910bb50 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/13.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/2.yml b/translations/ko-KR/data/release-notes/2-21/2.yml new file mode 100644 index 0000000000..bdac746dbc --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/2.yml @@ -0,0 +1,20 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/3.yml b/translations/ko-KR/data/release-notes/2-21/3.yml new file mode 100644 index 0000000000..dd4ccbbb5e --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/3.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% 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: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/4.yml b/translations/ko-KR/data/release-notes/2-21/4.yml new file mode 100644 index 0000000000..e90460c88e --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/4.yml @@ -0,0 +1,27 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" + - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/5.yml b/translations/ko-KR/data/release-notes/2-21/5.yml new file mode 100644 index 0000000000..444cf28527 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/5.yml @@ -0,0 +1,15 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/6.yml b/translations/ko-KR/data/release-notes/2-21/6.yml new file mode 100644 index 0000000000..d85f716f13 Binary files /dev/null and b/translations/ko-KR/data/release-notes/2-21/6.yml differ diff --git a/translations/ko-KR/data/release-notes/2-21/7.yml b/translations/ko-KR/data/release-notes/2-21/7.yml new file mode 100644 index 0000000000..69134720e7 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/7.yml @@ -0,0 +1,14 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/8.yml b/translations/ko-KR/data/release-notes/2-21/8.yml new file mode 100644 index 0000000000..b7bf410b13 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/8.yml @@ -0,0 +1,16 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + bugs: + - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-21/9.yml b/translations/ko-KR/data/release-notes/2-21/9.yml new file mode 100644 index 0000000000..46656c9e6b --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-21/9.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ko-KR/data/release-notes/2-22/0.yml b/translations/ko-KR/data/release-notes/2-22/0.yml new file mode 100644 index 0000000000..cb67278fca --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-22/0.yml @@ -0,0 +1,130 @@ +--- +intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. +date: '2020-09-23' +sections: + features: + - + heading: GitHub Actions Beta + notes: + - | + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + + You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + - + heading: GitHub Packages Beta + notes: + - | + [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + - + heading: Advanced Security Code Scanning Beta + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. + + Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + - + heading: Pull Request Retargeting + notes: + - | + When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + - + heading: Suspend and Unsuspend an App Installation + notes: + - | + Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + - + heading: Improved Large Scale Performance + notes: + - | + We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% 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 %}'' + + Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + - + heading: View All of Your Users + notes: + - | + For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](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: Administration Changes + notes: + - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} + - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](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 %}' + - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% 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 %} + - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% 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: Security Changes + notes: + - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](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 %} + - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - + heading: Developer Changes + notes: + - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' + - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' + - + heading: Users and organizations can add Twitter usernames to their GitHub profiles + notes: + - '[Developers and organizations can now add their Twitter username to their profile](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: API Changes + notes: + - | + #### Graduated Previews + + The following previews are now an official part of the API: + * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} + * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} + - | + #### GraphQL Schema Changes + + * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + bugs: + - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + deprecations: + - + heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020** That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + #- type: Backup and Disaster recovery + #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} + - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} + - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a 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 %}' + - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ko-KR/data/release-notes/2-22/1.yml b/translations/ko-KR/data/release-notes/2-22/1.yml new file mode 100644 index 0000000000..fbd3988c3d --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-22/1.yml @@ -0,0 +1,71 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - | + The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - | + Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + - | + Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + - | + System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + - | + The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + - | + `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + - | + Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + - | + Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + - | + Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + - | + When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + - | + The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + - | + OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + - | + Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + - | + On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + - | + When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + - | + When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + - | + Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + - | + Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + - | + The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + - | + Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + - | + A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + - | + When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + - | + [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + - | + GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management 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: + - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} + - GitHub App Manifests now include the `request_oauth_on_install` field. {% 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: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ko-KR/data/release-notes/2-22/2.yml b/translations/ko-KR/data/release-notes/2-22/2.yml new file mode 100644 index 0000000000..dc36b39e12 --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-22/2.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + bugs: + - | + If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + - | + A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} + - | + On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + - | + When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + - | + Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} + - | + The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + - | + On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ko-KR/data/release-notes/2-22/3.yml b/translations/ko-KR/data/release-notes/2-22/3.yml new file mode 100644 index 0000000000..45442a5d4b --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-22/3.yml @@ -0,0 +1,23 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - | + **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + - | + **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + - | + Packages have been updated to the latest security versions. {% 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: + - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ko-KR/data/release-notes/2-22/4.yml b/translations/ko-KR/data/release-notes/2-22/4.yml new file mode 100644 index 0000000000..e97737ee0b --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-22/4.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + bugs: + - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} diff --git a/translations/ko-KR/data/release-notes/2-22/5.yml b/translations/ko-KR/data/release-notes/2-22/5.yml new file mode 100644 index 0000000000..0520df862f --- /dev/null +++ b/translations/ko-KR/data/release-notes/2-22/5.yml @@ -0,0 +1,22 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' + - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/ko-KR/data/reusables/accounts/create-account.md b/translations/ko-KR/data/reusables/accounts/create-account.md new file mode 100644 index 0000000000..dc817b083d --- /dev/null +++ b/translations/ko-KR/data/reusables/accounts/create-account.md @@ -0,0 +1,2 @@ +1. Go to {% data variables.product.product_name %}'s [Pricing]({% data variables.product.pricing_url %}) page. +2. Read the information about the different products and subscriptions that {% data variables.product.product_name %} offers, then click the upgrade button under the subscription you'd like to choose. diff --git a/translations/ko-KR/data/reusables/actions/actions-not-verified.md b/translations/ko-KR/data/reusables/actions/actions-not-verified.md index 2ab85ce6c1..3107e5a79f 100644 --- a/translations/ko-KR/data/reusables/actions/actions-not-verified.md +++ b/translations/ko-KR/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations, but unlike verified apps, {% data variables.product.prodname_dotcom %} does not review or verify individual actions listed in {% data variables.product.prodname_marketplace %}. +Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/ko-KR/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/ko-KR/data/reusables/actions/actions-packages-set-spending-limit.md new file mode 100644 index 0000000000..e315a34bc8 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/actions-packages-set-spending-limit.md @@ -0,0 +1 @@ +You can set a specific spending limit or, for some accounts, allow unlimited spending. The spending limit applies to your combined overages for {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}. diff --git a/translations/ko-KR/data/reusables/actions/visualization-beta.md b/translations/ko-KR/data/reusables/actions/visualization-beta.md new file mode 100644 index 0000000000..ee3ad11ef4 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/visualization-beta.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** The workflow visualization graph for {% data variables.product.prodname_actions %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ko-KR/data/reusables/audit_log/audit-log-api-info.md b/translations/ko-KR/data/reusables/audit_log/audit-log-api-info.md new file mode 100644 index 0000000000..55728a1692 --- /dev/null +++ b/translations/ko-KR/data/reusables/audit_log/audit-log-api-info.md @@ -0,0 +1,5 @@ +* Access to your organization or repository settings +* Changes in permissions +* Added or removed users in an organization, repository, or team +* Users being promoted to admin +* Changes to permissions of a {% data variables.product.prodname_github_app %} diff --git a/translations/ko-KR/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/ko-KR/data/reusables/audit_log/audit-log-git-events-retention.md new file mode 100644 index 0000000000..3f1584bf91 --- /dev/null +++ b/translations/ko-KR/data/reusables/audit_log/audit-log-git-events-retention.md @@ -0,0 +1 @@ +The audit log retains Git events for 7 days. This is shorter than other audit log events, which can be retained for 90 days. diff --git a/translations/ko-KR/data/reusables/classroom/about-assignments.md b/translations/ko-KR/data/reusables/classroom/about-assignments.md new file mode 100644 index 0000000000..65a3506229 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/about-assignments.md @@ -0,0 +1 @@ +Each assignment has a title and an optional deadline. You can choose the visibility of repositories that {% data variables.product.prodname_classroom %} creates and choose access permissions. You can also automatically grade assignments and create a dedicated space to discuss the assignment with the student. diff --git a/translations/ko-KR/data/reusables/classroom/about-autograding.md b/translations/ko-KR/data/reusables/classroom/about-autograding.md new file mode 100644 index 0000000000..04ed2b067c --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/about-autograding.md @@ -0,0 +1 @@ +You can use autograding to automatically check a student's work for an assignment on {% data variables.product.prodname_classroom %}. You configure tests for an assignment, and the tests run immediately every time a student pushes to an assignment repository on {% data variables.product.product_location %}. The student can view the test results, make changes, and push to see new results. diff --git a/translations/ko-KR/data/reusables/classroom/about-classrooms.md b/translations/ko-KR/data/reusables/classroom/about-classrooms.md new file mode 100644 index 0000000000..5d19bbb44a --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/about-classrooms.md @@ -0,0 +1 @@ +A classroom in {% data variables.product.prodname_classroom %} is where teachers and students interact during a course. Teachers can create a student roster for the classroom, then create, assign, review, and grade assignments within the classroom. diff --git a/translations/ko-KR/data/reusables/classroom/about-online-ides.md b/translations/ko-KR/data/reusables/classroom/about-online-ides.md new file mode 100644 index 0000000000..43818e691f --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/about-online-ides.md @@ -0,0 +1 @@ +You can optionally configure an assignment to use an online integrated development environment (IDE). Online IDEs allow your students to write code, run programs, and collaborate in a browser, without installing Git and a full development toolchain on the student's computer. If you choose an online IDE for an assignment, students can still check out and run code locally on a computer with the necessary software. diff --git a/translations/ko-KR/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/ko-KR/data/reusables/classroom/assignments-classroom-prerequisite.md new file mode 100644 index 0000000000..06284dad51 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-classroom-prerequisite.md @@ -0,0 +1 @@ +You must create a classroom before you can create an assignment. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." diff --git a/translations/ko-KR/data/reusables/classroom/assignments-click-pencil.md b/translations/ko-KR/data/reusables/classroom/assignments-click-pencil.md new file mode 100644 index 0000000000..820afd5260 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-click-pencil.md @@ -0,0 +1 @@ +1. To the right of the assignment you want to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing assignment in list of assignments](/assets/images/help/classroom/assignments-click-pencil.png) diff --git a/translations/ko-KR/data/reusables/classroom/assignments-group-definition.md b/translations/ko-KR/data/reusables/classroom/assignments-group-definition.md new file mode 100644 index 0000000000..3143cddc70 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-group-definition.md @@ -0,0 +1 @@ +A group assignment is collaborative coursework for groups of students on {% data variables.product.prodname_classroom %}. diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-assign-a-deadline.md new file mode 100644 index 0000000000..6e8e29cc11 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-assign-a-deadline.md @@ -0,0 +1,5 @@ +Optionally, you can assign a deadline to the assignment. Under "Deadline (optional)", click in the text field, then use the date picker to assign a deadline. + +
      + Date picker for assignment deadline +
      diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md new file mode 100644 index 0000000000..54858178a5 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -0,0 +1,5 @@ +To choose an online IDE for the assignment, select the **Select an online IDE** drop-down menu, then click the IDE you'd like your students to use. + +
      + Using the 'Select an online IDE' drop-down menu to click an online IDE for the assignment +
      diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-template-repository.md new file mode 100644 index 0000000000..15bcb66cb5 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-template-repository.md @@ -0,0 +1,5 @@ +Under "Add a template repository to give students starter code", select the **Select a repository** drop-down, then type a search query. In the list of results, click the template repository you'd like to use for starter code. + +
      + Using the 'Select a repository' drop-down menu to find a template repository to use as starter code for an assignment +
      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 new file mode 100644 index 0000000000..3f4f17e1b2 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -0,0 +1,9 @@ +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)." + +Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. + +
      + Visibility options for assignment repositories +
      diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md new file mode 100644 index 0000000000..b82d19fe8e --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md @@ -0,0 +1,7 @@ +
      + +When you're done, click **Continue** to configure starter code and a development environment for the assignment. + +
      + 'Continue' button +
      diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md new file mode 100644 index 0000000000..4607b61065 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md @@ -0,0 +1,7 @@ +
      + +When you're done, click **Continue** to configure automatic grading and feedback for the project. + +
      + 'Continue' button +
      diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md new file mode 100644 index 0000000000..935d73f5df --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md @@ -0,0 +1,5 @@ +To create the assignment, click **Create assignment**. + +
      + 'Create assignment' button +
      diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-create-review-pull-request.md new file mode 100644 index 0000000000..5cc14ee9ff --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-create-review-pull-request.md @@ -0,0 +1,5 @@ +To create pull requests for the discussion of feedback, select **Enable feedback pull requests**. + +
      + Checkbox for 'Enable feedback pull requests' +
      diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-create-the-assignment.md new file mode 100644 index 0000000000..051e169c57 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -0,0 +1,5 @@ +To create an assignment, sign into {% data variables.product.prodname_classroom_with_url %} and navigate to a classroom. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click **New assignment**. + +
      + The 'New assignment' button +
      diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-intro-for-environment.md new file mode 100644 index 0000000000..bda2c39723 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-intro-for-environment.md @@ -0,0 +1 @@ +Optionally, decide whether to provide empty repositories or starter code, and preconfigure a development environment for your students. diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md new file mode 100644 index 0000000000..6290d808ad --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md @@ -0,0 +1,3 @@ +{% data reusables.classroom.classroom-enables-invitation-urls %} + +{% data reusables.classroom.invitation-url-warning %} diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-prevent-changes.md new file mode 100644 index 0000000000..9ef39a18b9 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-prevent-changes.md @@ -0,0 +1,7 @@ +You can prevent students from changing files that contain tests for autograding, or other important files in the assignment repository. + +Under "Protected file paths", type relative paths within the repository to protect. + +
      + Text field for typing protected file paths +
      \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/ko-KR/data/reusables/classroom/assignments-guide-using-autograding.md new file mode 100644 index 0000000000..5f50beec64 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-guide-using-autograding.md @@ -0,0 +1,23 @@ +{% data reusables.classroom.about-autograding %} For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." + +{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} For more information, see "[Grading methods](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)." + +
      + Using the 'Add test' drop-down menu to click a grading method +
      + +
      + +Define the parameters of your test case, like the name, commands, inputs, outputs, timeout, and points. When you're done, click **Save test case**. + +
      + 'Save test case' button for an autograding test +
      + +
      + +You can add more tests with the **Add test** drop-down menu, and you can edit or delete existing tests with {% octicon "pencil" aria-label="The pencil icon" %} or {% octicon "trash" aria-label="The trash icon" %}. + +
      + Pencil and trash icons to edit or delete an autograding test +
      \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/classroom/assignments-individual-definition.md b/translations/ko-KR/data/reusables/classroom/assignments-individual-definition.md new file mode 100644 index 0000000000..33425ae2c3 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-individual-definition.md @@ -0,0 +1 @@ +An individual assignment is coursework for each student who participates in a course on {% data variables.product.prodname_classroom %}. The student is intended to complete an individual assignment without help from other students. diff --git a/translations/ko-KR/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/ko-KR/data/reusables/classroom/assignments-to-prevent-submission.md new file mode 100644 index 0000000000..62bd9cc2da --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-to-prevent-submission.md @@ -0,0 +1 @@ +To prevent acceptance or submission of an assignment by students, deselect **Enable assignment invitation URL**. To edit the assignment, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment**. diff --git a/translations/ko-KR/data/reusables/classroom/assignments-type-a-title.md b/translations/ko-KR/data/reusables/classroom/assignments-type-a-title.md new file mode 100644 index 0000000000..20d32397ac --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/assignments-type-a-title.md @@ -0,0 +1,5 @@ +Type a title for the assignment. Optionally, click {% octicon "pencil" aria-label="The pencil icon" %} to edit the prefix. + +
      + Assignment title and prefix +
      diff --git a/translations/ko-KR/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/ko-KR/data/reusables/classroom/classroom-creates-group-repositories.md new file mode 100644 index 0000000000..10cdc5924a --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/classroom-creates-group-repositories.md @@ -0,0 +1 @@ +For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.product_name %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. diff --git a/translations/ko-KR/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/ko-KR/data/reusables/classroom/classroom-creates-individual-repositories.md new file mode 100644 index 0000000000..4108abf9ad --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -0,0 +1 @@ +When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.product_name %}. diff --git a/translations/ko-KR/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/ko-KR/data/reusables/classroom/classroom-enables-invitation-urls.md new file mode 100644 index 0000000000..1b357c3a2d --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/classroom-enables-invitation-urls.md @@ -0,0 +1 @@ +By default, {% data variables.product.prodname_classroom %} enables an invitation URL for each assignment you create. Students can accept and submit the assignment while the invitation URL is enabled. You can share the URL with your students on your LMS, course homepage, or wherever you post assignments. Students can also navigate to the assignment on {% data variables.product.prodname_classroom %} if the student has already accepted an assignment for the classroom. diff --git a/translations/ko-KR/data/reusables/classroom/click-assignment-in-list.md b/translations/ko-KR/data/reusables/classroom/click-assignment-in-list.md new file mode 100644 index 0000000000..347d0bc108 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/click-assignment-in-list.md @@ -0,0 +1 @@ +1. In the list of assignments, click the assignment you want to view. ![Assignment in list of assignments for an classroom](/assets/images/help/classroom/click-assignment-in-list.png) diff --git a/translations/ko-KR/data/reusables/classroom/click-classroom-in-list.md b/translations/ko-KR/data/reusables/classroom/click-classroom-in-list.md new file mode 100644 index 0000000000..fe7d091cdc --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/click-classroom-in-list.md @@ -0,0 +1 @@ +1. In the list of classrooms, click the classroom you want to view. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) diff --git a/translations/ko-KR/data/reusables/classroom/click-settings.md b/translations/ko-KR/data/reusables/classroom/click-settings.md new file mode 100644 index 0000000000..9fe6b33d6b --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/click-settings.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" tab for classroom](/assets/images/help/classroom/click-settings.png) diff --git a/translations/ko-KR/data/reusables/classroom/click-students.md b/translations/ko-KR/data/reusables/classroom/click-students.md new file mode 100644 index 0000000000..13df0b1e40 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/click-students.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**. !["Students" tab for classroom](/assets/images/help/classroom/click-students.png) diff --git a/translations/ko-KR/data/reusables/classroom/for-more-information-about-assignment-creation.md b/translations/ko-KR/data/reusables/classroom/for-more-information-about-assignment-creation.md new file mode 100644 index 0000000000..8fd113d763 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/for-more-information-about-assignment-creation.md @@ -0,0 +1 @@ +For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." 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 new file mode 100644 index 0000000000..e554d4b605 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/guide-create-new-classroom.md @@ -0,0 +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. 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/classroom/invitation-url-warning.md b/translations/ko-KR/data/reusables/classroom/invitation-url-warning.md new file mode 100644 index 0000000000..f85e808ddc --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/invitation-url-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning**: Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a user account on {% data variables.product.product_name %} with an identifier in your roster. + +{% endwarning %} diff --git a/translations/ko-KR/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/ko-KR/data/reusables/classroom/readme-contains-button-for-online-ide.md new file mode 100644 index 0000000000..fac85f79f1 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -0,0 +1 @@ +When a student accepts an assignment with an online IDE, the assignment repository will include a _README.md_ file with a special button at the top of the file. The button links the student directly to the workspace in the online IDE. diff --git a/translations/ko-KR/data/reusables/classroom/sign-into-github-classroom.md b/translations/ko-KR/data/reusables/classroom/sign-into-github-classroom.md new file mode 100644 index 0000000000..578bf7213e --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/sign-into-github-classroom.md @@ -0,0 +1 @@ +1. Sign into {% data variables.product.prodname_classroom_with_url %}. diff --git a/translations/ko-KR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/ko-KR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md new file mode 100644 index 0000000000..2486daf0a4 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md @@ -0,0 +1 @@ +Under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. diff --git a/translations/ko-KR/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/ko-KR/data/reusables/classroom/you-can-choose-a-template-repository.md new file mode 100644 index 0000000000..40eb9d273b --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -0,0 +1 @@ +You can optionally choose a template repository as starter code for the assignment. The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}. diff --git a/translations/ko-KR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/ko-KR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md new file mode 100644 index 0000000000..e9592fb832 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md @@ -0,0 +1 @@ +You can automatically create a pull request where you can provide feedback and answer a student's questions about an assignment. For more information about the review of changes in a pull request, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)." diff --git a/translations/ko-KR/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md b/translations/ko-KR/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md new file mode 100644 index 0000000000..af5be0c098 --- /dev/null +++ b/translations/ko-KR/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md @@ -0,0 +1 @@ +You may want to predefine the default settings for the assignment repositories that {% data variables.product.prodname_classroom %} creates from a template repository. For example, you may want to disable issues, define labels for pull requests, or protect a branch in some or all of the repositories. diff --git a/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md b/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md new file mode 100644 index 0000000000..b8d2b78cbc --- /dev/null +++ b/translations/ko-KR/data/reusables/dependabot/private-dependencies-note.md @@ -0,0 +1,3 @@ +When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)." + +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file 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 fc99299bc2..b36b0b6cb7 100644 --- a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md @@ -1,20 +1,23 @@ -| Package manager | Supports vendoring | -| -------------------------------- |:------------------:| -| Bundler: `bundler` | **X** | -| Cargo: `cargo` | | -| Composer: `composer` | | -| Docker: `docker` | | -| Elm: `elm` | | -| git submodule: `gitsubmodule` | | -| GitHub Actions: `github-actions` | | -| Go modules: `gomod` | **X** | -| Gradle: `gradle` | | -| Maven: `maven` | | -| Mix: `mix` | | -| npm: `npm` | | -| NuGet: `nuget` | | -| pip: `pip` | | -| Terraform: `terraform` | | +The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. + +| Package manager | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | +| -------------------------------- |:-----------------------------------------------------------------:|:---------:| +| Bundler: `bundler` | | **✓** | +| Cargo: `cargo` | **✓** | | +| Composer: `composer` | **✓** | | +| Docker: `docker` | **✓** | | +| Elixir: `hex` | | | +| Elm: `elm` | **✓** | | +| git submodule: `gitsubmodule` | **✓** | | +| GitHub Actions: `github-actions` | **✓** | | +| Go modules: `gomod` | **✓** | **✓** | +| Gradle: `gradle` | **✓** | | +| Maven: `maven` | **✓** | | +| Mix: `mix` | **✓** | | +| npm: `npm` | **✓** | | +| NuGet: `nuget` | **✓** | | +| pip: `pip` | | | +| Terraform: `terraform` | **✓** | | {% note %} diff --git a/translations/ko-KR/data/reusables/discussions/about-categories-and-formats.md b/translations/ko-KR/data/reusables/discussions/about-categories-and-formats.md new file mode 100644 index 0000000000..a17ca2ca53 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/about-categories-and-formats.md @@ -0,0 +1 @@ +All discussions must be created in a category, and repository administrators and maintainers define the categories for a repository. Categories can contain open-ended conversations, or conversations with a question/answer format. diff --git a/translations/ko-KR/data/reusables/discussions/about-discussions.md b/translations/ko-KR/data/reusables/discussions/about-discussions.md new file mode 100644 index 0000000000..c61b8b0f0a --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/about-discussions.md @@ -0,0 +1 @@ +Discussions are an open forum for conversation among maintainers and the community for a project on {% data variables.product.product_name %}. diff --git a/translations/ko-KR/data/reusables/discussions/beta.md b/translations/ko-KR/data/reusables/discussions/beta.md new file mode 100644 index 0000000000..8562a9025f --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_discussions %} is currently in beta and subject to change. + +{% endnote %} diff --git a/translations/ko-KR/data/reusables/discussions/click-discussion-in-list.md b/translations/ko-KR/data/reusables/discussions/click-discussion-in-list.md new file mode 100644 index 0000000000..8156c86331 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/click-discussion-in-list.md @@ -0,0 +1 @@ +1. In the list of discussions, click the discussion you want to view. ![Discussion in list of discussions for a repository](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/ko-KR/data/reusables/discussions/discussions-tab.md b/translations/ko-KR/data/reusables/discussions/discussions-tab.md new file mode 100644 index 0000000000..67795aa5ae --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/discussions-tab.md @@ -0,0 +1 @@ +1. Under your repository name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. !["Discussions" tab for a repository](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/translations/ko-KR/data/reusables/discussions/edit-categories.md b/translations/ko-KR/data/reusables/discussions/edit-categories.md new file mode 100644 index 0000000000..6f4f6af574 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/edit-categories.md @@ -0,0 +1 @@ +1. To the right of "Categories", click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing categories](/assets/images/help/discussions/click-edit-categories.png) diff --git a/translations/ko-KR/data/reusables/discussions/edit-category-details.md b/translations/ko-KR/data/reusables/discussions/edit-category-details.md new file mode 100644 index 0000000000..8004b70314 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/edit-category-details.md @@ -0,0 +1 @@ +Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." diff --git a/translations/ko-KR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/ko-KR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md new file mode 100644 index 0000000000..a43c0686b0 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -0,0 +1,5 @@ +You can enable or disable discussions for a repository. + +{% data reusables.repositories.navigate-to-repo %} +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. ![Repository settings button](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", select **Discussions**. ![Checkbox under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/ko-KR/data/reusables/discussions/github-recognizes-members.md b/translations/ko-KR/data/reusables/discussions/github-recognizes-members.md new file mode 100644 index 0000000000..b6874b910d --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/github-recognizes-members.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. diff --git a/translations/ko-KR/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/ko-KR/data/reusables/discussions/marking-a-comment-as-an-answer.md new file mode 100644 index 0000000000..bdefffdea0 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -0,0 +1,14 @@ +You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +When you mark a question as an answer, {% data variables.product.product_name %} will highlight the comment and replies to the comment to help visitors quickly find the answer. + +![Comment marked as answer to a discussion](/assets/images/help/discussions/comment-marked-as-answer.png) + +You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the unanswered discussion you want to mark as answered. ![Unanswered discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the discussion, find the comment you want to mark as the answer. +1. In the upper-right corner of the comment, click {% octicon "check-circle" aria-label="The circular check icon" %}. !["Mark as answer" circular check icon for marking comment as answer in a discussion](/assets/images/help/discussions/comment-mark-as-answer-button.png) +1. Optionally, to unmark a comment as the answer, click {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. diff --git a/translations/ko-KR/data/reusables/discussions/repository-category-limit.md b/translations/ko-KR/data/reusables/discussions/repository-category-limit.md new file mode 100644 index 0000000000..293d3632b5 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/repository-category-limit.md @@ -0,0 +1 @@ +Each repository can have up to 10 categories. diff --git a/translations/ko-KR/data/reusables/discussions/starting-a-discussion.md b/translations/ko-KR/data/reusables/discussions/starting-a-discussion.md new file mode 100644 index 0000000000..242e3abf9b --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/starting-a-discussion.md @@ -0,0 +1,6 @@ +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Click **New discussion**. !["New discussion" button within the "Discussions" tab for a repository](/assets/images/help/discussions/new-discussion-button.png) +1. Select the **Select Category** drop-down menu, and click a category for your discussion. !["Select Category" drop-down menu and list of available categories in a repository](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) +1. Type a title and body for your discussion. ![Text fields for new discussion's title and body](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) diff --git a/translations/ko-KR/data/reusables/discussions/you-can-categorize-discussions.md b/translations/ko-KR/data/reusables/discussions/you-can-categorize-discussions.md new file mode 100644 index 0000000000..bb05316d77 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/you-can-categorize-discussions.md @@ -0,0 +1 @@ +You can categorize discussions to help community members begin conversations in the right place, and to help community members find related discussions. diff --git a/translations/ko-KR/data/reusables/discussions/you-can-convert-an-issue.md b/translations/ko-KR/data/reusables/discussions/you-can-convert-an-issue.md new file mode 100644 index 0000000000..1421256e1f --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/you-can-convert-an-issue.md @@ -0,0 +1 @@ +If an issue turns out to be a question or open-ended conversation instead of a work item to track and prioritize, you can convert the issue to a discussion. diff --git a/translations/ko-KR/data/reusables/discussions/you-can-use-discussions.md b/translations/ko-KR/data/reusables/discussions/you-can-use-discussions.md new file mode 100644 index 0000000000..27c1ba7cb2 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/you-can-use-discussions.md @@ -0,0 +1 @@ +You can use discussions to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/discussions/you-cannot-convert-a-discussion.md b/translations/ko-KR/data/reusables/discussions/you-cannot-convert-a-discussion.md new file mode 100644 index 0000000000..9e9b687b67 --- /dev/null +++ b/translations/ko-KR/data/reusables/discussions/you-cannot-convert-a-discussion.md @@ -0,0 +1 @@ +You cannot convert a discussion to an issue. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/ko-KR/data/reusables/dotcom_billing/actions-packages-unpaid-account.md index cb9dac9ca3..dc87bcb5ee 100644 --- a/translations/ko-KR/data/reusables/dotcom_billing/actions-packages-unpaid-account.md +++ b/translations/ko-KR/data/reusables/dotcom_billing/actions-packages-unpaid-account.md @@ -2,4 +2,4 @@ If your account has outstanding unpaid charges: * The storage or minutes included in your account for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} will not be reset until the payment has been successfully processed. * For accounts with storage or minutes remaining for the current billing period, {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} will continue to be available until any included usage has been reached. -* For accounts that have reached the included usage for the current billing period for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} will be disabled to prevent any further overages. If you pay your account by invoice, you must [contact our account management team](https://enterprise.github.com/contact) to process payment and reset your usage. +* For accounts that have reached the included usage for the current billing period for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} will be disabled to prevent any further overages. 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 1d0ef762d6..67fa09ec6a 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 %}](https://education.github.com/partners/schools)." +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/teach-and-learn-with-github-education/about-github-education)." diff --git a/translations/ko-KR/data/reusables/education/apply-for-team.md b/translations/ko-KR/data/reusables/education/apply-for-team.md index afc1ef555d..88fdff7f90 100644 --- a/translations/ko-KR/data/reusables/education/apply-for-team.md +++ b/translations/ko-KR/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Apply for free [{% data variables.product.prodname_team %}](/articles/github-s-products), which allows unlimited users and private repositories. For more information, see "[Applying for an educator or researcher discount](/articles/applying-for-an-educator-or-researcher-discount)." +- Apply for free [{% data variables.product.prodname_team %}](/articles/github-s-products), which allows unlimited users and private repositories. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." diff --git a/translations/ko-KR/data/reusables/education/click-get-teacher-benefits.md b/translations/ko-KR/data/reusables/education/click-get-teacher-benefits.md new file mode 100644 index 0000000000..25bbacd747 --- /dev/null +++ b/translations/ko-KR/data/reusables/education/click-get-teacher-benefits.md @@ -0,0 +1 @@ +1. Under "Individuals", click **Get teacher benefits**. !["Get teacher benefits" on {% data variables.product.prodname_education %} homepage](/assets/images/help/education/click-get-teacher-benefits.png) diff --git a/translations/ko-KR/data/reusables/education/educator-requirements.md b/translations/ko-KR/data/reusables/education/educator-requirements.md new file mode 100644 index 0000000000..b7a004744d --- /dev/null +++ b/translations/ko-KR/data/reusables/education/educator-requirements.md @@ -0,0 +1,6 @@ +To apply for an educator or researcher discount, you must meet the following requirements. + +- Be an educator, faculty member, or researcher. +- Have a verifiable school-issued email address. +- Upload documents that prove your school affiliation. +- Have a user account on {% data variables.product.product_name %}. diff --git a/translations/ko-KR/data/reusables/gated-features/discussions.md b/translations/ko-KR/data/reusables/gated-features/discussions.md new file mode 100644 index 0000000000..5ada0a25ee --- /dev/null +++ b/translations/ko-KR/data/reusables/gated-features/discussions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_discussions %} is available in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/ko-KR/data/reusables/github-actions/actions-billing.md b/translations/ko-KR/data/reusables/github-actions/actions-billing.md index 947b31a56d..4e12946e9b 100644 --- a/translations/ko-KR/data/reusables/github-actions/actions-billing.md +++ b/translations/ko-KR/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account. +{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ko-KR/data/reusables/github-actions/actions-on-examples.md b/translations/ko-KR/data/reusables/github-actions/actions-on-examples.md index beea3062f5..06efe2e4ea 100644 --- a/translations/ko-KR/data/reusables/github-actions/actions-on-examples.md +++ b/translations/ko-KR/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -##### **Example using a single event** +##### Example using a single event ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -##### **Example using a list of events** +##### Example using a list of events ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -##### **Example using multiple events with activity types or configuration** +##### Example using multiple events with activity types or configuration If you need to specify activity types or configuration for an event, you must configure each event separately. You must append a colon (`:`) to all events, including events without configuration. diff --git a/translations/ko-KR/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/ko-KR/data/reusables/github-actions/actions-spending-limit-brief.md new file mode 100644 index 0000000000..20d912fb21 --- /dev/null +++ b/translations/ko-KR/data/reusables/github-actions/actions-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/ko-KR/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/ko-KR/data/reusables/github-actions/actions-spending-limit-detailed.md new file mode 100644 index 0000000000..062eef3c3f --- /dev/null +++ b/translations/ko-KR/data/reusables/github-actions/actions-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.github-actions.actions-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where a workflow is run. Any coupons on your account do not apply to {% data variables.product.prodname_actions %} overages. diff --git a/translations/ko-KR/data/reusables/github-actions/contacting-support.md b/translations/ko-KR/data/reusables/github-actions/contacting-support.md index c3d307a405..d4bcb7c776 100644 --- a/translations/ko-KR/data/reusables/github-actions/contacting-support.md +++ b/translations/ko-KR/data/reusables/github-actions/contacting-support.md @@ -1,4 +1,4 @@ -If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} board](https://github.community/c/github-actions). +If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). If you have feedback or feature requests for {% data variables.product.prodname_actions %}, share those in the {% data variables.contact.contact_feedback_actions %}. diff --git a/translations/ko-KR/data/reusables/github-actions/macos-runner-preview.md b/translations/ko-KR/data/reusables/github-actions/macos-runner-preview.md index 88a2d482c4..e6db4f8803 100644 --- a/translations/ko-KR/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/ko-KR/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The MacOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the MacOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/ko-KR/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/ko-KR/data/reusables/github-actions/publish-to-maven-workflow-step.md index 24292b0b12..fec15a1815 100644 --- a/translations/ko-KR/data/reusables/github-actions/publish-to-maven-workflow-step.md +++ b/translations/ko-KR/data/reusables/github-actions/publish-to-maven-workflow-step.md @@ -1 +1 @@ -Runs the `mvn -B deploy` command to publish to the `ossrh` repository. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. +Runs the `mvn --batch-mode deploy` command to publish to the `ossrh` repository. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. diff --git a/translations/ko-KR/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/ko-KR/data/reusables/github-actions/publish-to-packages-workflow-step.md index aa0c63eeea..743020588d 100644 --- a/translations/ko-KR/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ b/translations/ko-KR/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -Runs the `mvn -B deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret. +Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret. diff --git a/translations/ko-KR/data/reusables/github-insights/download-latest-release.md b/translations/ko-KR/data/reusables/github-insights/download-latest-release.md index 207d17df7f..9f144cfd30 100644 --- a/translations/ko-KR/data/reusables/github-insights/download-latest-release.md +++ b/translations/ko-KR/data/reusables/github-insights/download-latest-release.md @@ -1,3 +1,3 @@ -1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the [Releases page](https://github.com/github/insights-releases/releases/latest) for `github/insights-releases`. +1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the Releases page for `github/insights-releases`. 2. To download the latest release, under "Assets", click `insights-VERSION.tar.gz`. ![Installation assset](/assets/images/help/insights/installation-tgz.png) 3. Unzip the directory. diff --git a/translations/ko-KR/data/reusables/marketplace/app-transfer-to-org-for-verification.md b/translations/ko-KR/data/reusables/marketplace/app-transfer-to-org-for-verification.md new file mode 100644 index 0000000000..0621a9e6e9 --- /dev/null +++ b/translations/ko-KR/data/reusables/marketplace/app-transfer-to-org-for-verification.md @@ -0,0 +1 @@ +If you want to sell an app that's owned by your user account, first you'll need to transfer the app to an organization, and then request verification for a listing created by the organization. diff --git a/translations/ko-KR/data/reusables/marketplace/free-plan-note.md b/translations/ko-KR/data/reusables/marketplace/free-plan-note.md new file mode 100644 index 0000000000..bf63caa53d --- /dev/null +++ b/translations/ko-KR/data/reusables/marketplace/free-plan-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** If you're listing an app on {% data variables.product.prodname_marketplace %}, you can't list your app with a free pricing plan if you offer a paid service outside of {% data variables.product.prodname_marketplace %}. + +{% endnote %} diff --git a/translations/ko-KR/data/reusables/marketplace/launch-with-free.md b/translations/ko-KR/data/reusables/marketplace/launch-with-free.md index 15230e218b..2151c241cc 100644 --- a/translations/ko-KR/data/reusables/marketplace/launch-with-free.md +++ b/translations/ko-KR/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can submit both an unverified and verified app. This will allow you to launch with a free version of your app. Once GitHub verifies your app, your listing will change from unverified to verified in {% data variables.product.prodname_marketplace %} and GitHub will publish your new pricing plans. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/ko-KR/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/ko-KR/data/reusables/marketplace/marketplace-billing-ui-requirements.md index 9c02badeae..5aa91ca839 100644 --- a/translations/ko-KR/data/reusables/marketplace/marketplace-billing-ui-requirements.md +++ b/translations/ko-KR/data/reusables/marketplace/marketplace-billing-ui-requirements.md @@ -1,7 +1,7 @@ -- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} must be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} It's highly recommended to allow customers to re-enable their previous plan. -- Customers must be able to upgrade from your app's UI if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` -- Customers must be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. -- Customers must be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: +- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} should be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} It's highly recommended to allow customers to re-enable their previous plan. +- Customers should be able to upgrade from your app's user interface if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` +- Customers should be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. +- Customers should be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: - Current plan and price. - New plans purchased. - Upgrades, downgrades, cancellations, and the number of remaining days in a free trial. diff --git a/translations/ko-KR/data/reusables/package_registry/authenticate-packages.md b/translations/ko-KR/data/reusables/package_registry/authenticate-packages.md index 89915a62e8..aee972b1ba 100644 --- a/translations/ko-KR/data/reusables/package_registry/authenticate-packages.md +++ b/translations/ko-KR/data/reusables/package_registry/authenticate-packages.md @@ -3,7 +3,7 @@ You need an access token to publish, install, and delete packages. You can use a {% if currentVersion == "free-pro-team@latest" %} To authenticate using a {% data variables.product.prodname_actions %} workflow: -- For package registries (`PACKAGE-REGISTRY.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`), you can use a `GITHUB_TOKEN`. +- 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. {% else %} To authenticate to diff --git a/translations/ko-KR/data/reusables/package_registry/billing-for-container-registry.md b/translations/ko-KR/data/reusables/package_registry/billing-for-container-registry.md index 7cf8e2459f..479e2d5b55 100644 --- a/translations/ko-KR/data/reusables/package_registry/billing-for-container-registry.md +++ b/translations/ko-KR/data/reusables/package_registry/billing-for-container-registry.md @@ -1,3 +1,3 @@ -During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." +During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-docker-for-use-with-github-packages)." After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the container registry. 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)." diff --git a/translations/ko-KR/data/reusables/package_registry/container-registry-beta-billing-note.md b/translations/ko-KR/data/reusables/package_registry/container-registry-beta-billing-note.md index ccc4fc14f8..f588ab6f9b 100644 --- a/translations/ko-KR/data/reusables/package_registry/container-registry-beta-billing-note.md +++ b/translations/ko-KR/data/reusables/package_registry/container-registry-beta-billing-note.md @@ -1,5 +1,5 @@ {% note %} -**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." +**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." {% endnote %} diff --git a/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md b/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md index 24313880ba..6bd738198e 100644 --- a/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md +++ b/translations/ko-KR/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" and "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} diff --git a/translations/ko-KR/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/ko-KR/data/reusables/package_registry/docker_registry_deprecation_status.md index 2df9364c31..a23fdc598b 100644 --- a/translations/ko-KR/data/reusables/package_registry/docker_registry_deprecation_status.md +++ b/translations/ko-KR/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -1,5 +1,5 @@ {% warning %} -**Note:** The {% data variables.product.prodname_registry %} Docker registry will be superseded by {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} in a future {% data variables.product.product_name %} release{% endif %}.{% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" and "[Getting started with {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry)."{% endif %} +**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 %} {% endwarning %} diff --git a/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md index b0cddc8bcb..3b74dd6c78 100644 --- a/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md +++ b/translations/ko-KR/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/package_registry/packages-billing.md b/translations/ko-KR/data/reusables/package_registry/packages-billing.md index 7a93df94ba..adc9c87bed 100644 --- a/translations/ko-KR/data/reusables/package_registry/packages-billing.md +++ b/translations/ko-KR/data/reusables/package_registry/packages-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_registry %} usage is free for public packages. For private packages, each {% data variables.product.product_name %} account receives a certain amount of free storage and data transfer, depending on the product used with the account. By default, your account will have a spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you increase your spending limit above the default of $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. Any coupons on your account do not apply to {% data variables.product.prodname_registry %} overages. +{% data variables.product.prodname_registry %} usage is free for public packages. For private packages, each {% data variables.product.product_name %} account receives a certain amount of free storage and data transfer, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ko-KR/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/ko-KR/data/reusables/package_registry/packages-spending-limit-brief.md new file mode 100644 index 0000000000..ea07621d29 --- /dev/null +++ b/translations/ko-KR/data/reusables/package_registry/packages-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/ko-KR/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/ko-KR/data/reusables/package_registry/packages-spending-limit-detailed.md new file mode 100644 index 0000000000..2719322745 --- /dev/null +++ b/translations/ko-KR/data/reusables/package_registry/packages-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.package_registry.packages-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. Any coupons on your account do not apply to {% data variables.product.prodname_registry %} overages. diff --git a/translations/ko-KR/data/reusables/package_registry/required-scopes.md b/translations/ko-KR/data/reusables/package_registry/required-scopes.md index ec9748d65a..364cdccaef 100644 --- a/translations/ko-KR/data/reusables/package_registry/required-scopes.md +++ b/translations/ko-KR/data/reusables/package_registry/required-scopes.md @@ -1 +1 @@ -You must use a personal access token with the appropriate scopes to publish and install packages in {% data variables.product.prodname_registry %}. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +You must use a personal access token with the appropriate scopes to publish and install packages in {% data variables.product.prodname_registry %}. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)." diff --git a/translations/ko-KR/data/reusables/package_registry/viewing-packages.md b/translations/ko-KR/data/reusables/package_registry/viewing-packages.md index 7a16420a97..131b04989a 100644 --- a/translations/ko-KR/data/reusables/package_registry/viewing-packages.md +++ b/translations/ko-KR/data/reusables/package_registry/viewing-packages.md @@ -1 +1 @@ -After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/publishing-and-managing-packages/viewing-packages)." +After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)." diff --git a/translations/ko-KR/data/reusables/repositories/dependency-review.md b/translations/ko-KR/data/reusables/repositories/dependency-review.md new file mode 100644 index 0000000000..e780074c3c --- /dev/null +++ b/translations/ko-KR/data/reusables/repositories/dependency-review.md @@ -0,0 +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)." +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/repositories/navigate-to-job-superlinter.md b/translations/ko-KR/data/reusables/repositories/navigate-to-job-superlinter.md index 3c79e1a1a6..afa0402d6b 100644 --- a/translations/ko-KR/data/reusables/repositories/navigate-to-job-superlinter.md +++ b/translations/ko-KR/data/reusables/repositories/navigate-to-job-superlinter.md @@ -1,5 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. In the left sidebar, click the job you want to see. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% else %} 1. In the left sidebar, click the job you want to see. ![Select a workflow job](/assets/images/help/repository/workflow-job.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ko-KR/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/ko-KR/data/reusables/repositories/two-dot-diff-comparison-example-urls.md index 5dbca8831b..1a25944892 100644 --- a/translations/ko-KR/data/reusables/repositories/two-dot-diff-comparison-example-urls.md +++ b/translations/ko-KR/data/reusables/repositories/two-dot-diff-comparison-example-urls.md @@ -1 +1 @@ -For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f.` +For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`. diff --git a/translations/ko-KR/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/ko-KR/data/reusables/repositories/view-failed-job-results-superlinter.md index 434994a169..d436c99e66 100644 --- a/translations/ko-KR/data/reusables/repositories/view-failed-job-results-superlinter.md +++ b/translations/ko-KR/data/reusables/repositories/view-failed-job-results-superlinter.md @@ -1,5 +1,8 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Any failed steps are automatically expanded to display the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png) +1. Any failed steps are automatically expanded to display the results. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %} +![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png){% endif %} {% else %} 1. Expand the **Run Super-Linter** step to view the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results.png) {% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/repositories/view-specific-line-superlinter.md b/translations/ko-KR/data/reusables/repositories/view-specific-line-superlinter.md index ae70f1762f..5695e5746a 100644 --- a/translations/ko-KR/data/reusables/repositories/view-specific-line-superlinter.md +++ b/translations/ko-KR/data/reusables/repositories/view-specific-line-superlinter.md @@ -1,5 +1,10 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Optionally, to get a link to a specific line in the logs, click on the step's line number. You can then copy the link from the address bar of your web browser. ![Button to copy link](/assets/images/help/repository/copy-link-button-updated.png) +1. Optionally, to get a link to a specific line in the logs, click on the step's line number. You can then copy the link from the address bar of your web browser. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Button to copy link](/assets/images/help/repository/copy-link-button-updated-2.png) + {% else %} + ![Button to copy link](/assets/images/help/repository/copy-link-button-updated.png) + {% endif %} {% else %} 1. Optionally, to get a link to a specific line in the logs, click on the step's line number. You can then copy the link from the address bar of your web browser. ![Button to copy link](/assets/images/help/repository/copy-link-button.png) {% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/search/date_gt_lt.md b/translations/ko-KR/data/reusables/search/date_gt_lt.md index 960f02127d..57a206f28c 100644 --- a/translations/ko-KR/data/reusables/search/date_gt_lt.md +++ b/translations/ko-KR/data/reusables/search/date_gt_lt.md @@ -1 +1 @@ -Dates support [greater than, less than, and range qualifiers](/articles/understanding-the-search-syntax). +When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." diff --git a/translations/ko-KR/data/reusables/secret-scanning/api-beta.md b/translations/ko-KR/data/reusables/secret-scanning/api-beta.md new file mode 100644 index 0000000000..510473ea8d --- /dev/null +++ b/translations/ko-KR/data/reusables/secret-scanning/api-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The {% data variables.product.prodname_secret_scanning %} API is currently in beta and subject to change. + +{% endnote %} diff --git a/translations/ko-KR/data/reusables/sponsors/billing-switcher.md b/translations/ko-KR/data/reusables/sponsors/billing-switcher.md new file mode 100644 index 0000000000..4831c34a3b --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/billing-switcher.md @@ -0,0 +1 @@ +1. Optionally, to manage your sponsorship on behalf of an organization, in the upper-left corner, use the **Personal settings** drop-down menu, and click the organization. ![Drop-down menu to switch accounts for settings](/assets/images/help/sponsors/billing-account-switcher.png) diff --git a/translations/ko-KR/data/reusables/sponsors/change-tier.md b/translations/ko-KR/data/reusables/sponsors/change-tier.md index 9770dfebd1..e805d6d08a 100644 --- a/translations/ko-KR/data/reusables/sponsors/change-tier.md +++ b/translations/ko-KR/data/reusables/sponsors/change-tier.md @@ -1 +1 @@ -1. 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 **Change tier**. ![Change tier button](/assets/images/help/billing/edit-sponsor-billing.png) +1. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored account, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your tier amount, then click **Change tier**. ![Change tier button](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/ko-KR/data/reusables/sponsors/choose-updates.md b/translations/ko-KR/data/reusables/sponsors/choose-updates.md new file mode 100644 index 0000000000..ade59cf05b --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/choose-updates.md @@ -0,0 +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) diff --git a/translations/ko-KR/data/reusables/sponsors/manage-sponsorship.md b/translations/ko-KR/data/reusables/sponsors/manage-sponsorship.md new file mode 100644 index 0000000000..fb0b480922 --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/manage-sponsorship.md @@ -0,0 +1 @@ +1. To the right of your current tier, click **Manage**. ![Manage your sponsorship button](/assets/images/help/sponsors/manage-your-sponsorship-button.png) \ No newline at end of file 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 new file mode 100644 index 0000000000..0cd08d5382 --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/manage-updates-for-orgs.md @@ -0,0 +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)." diff --git a/translations/ko-KR/data/reusables/sponsors/maximum-tier.md b/translations/ko-KR/data/reusables/sponsors/maximum-tier.md index a787f1dd0a..803658fba4 100644 --- a/translations/ko-KR/data/reusables/sponsors/maximum-tier.md +++ b/translations/ko-KR/data/reusables/sponsors/maximum-tier.md @@ -1 +1 @@ -The maximum price is US$6000 per month. +The maximum price is US$12,000 per month. diff --git a/translations/ko-KR/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/ko-KR/data/reusables/sponsors/navigate-to-sponsored-account.md new file mode 100644 index 0000000000..def70f43f1 --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/navigate-to-sponsored-account.md @@ -0,0 +1 @@ +1. On {% data variables.product.product_name %}, navigate to the sponsored account's profile. diff --git a/translations/ko-KR/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/ko-KR/data/reusables/sponsors/navigate-to-sponsors-dashboard.md new file mode 100644 index 0000000000..0185cfdeed --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/navigate-to-sponsors-dashboard.md @@ -0,0 +1,2 @@ +1. In the upper-right corner of any page, click your profile photo, then click **{% data variables.product.prodname_sponsors %}**. ![{% data variables.product.prodname_sponsors %} button](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) +2. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**. ![Developer sponsors dashboard button](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) diff --git a/translations/ko-KR/data/reusables/sponsors/no-fees.md b/translations/ko-KR/data/reusables/sponsors/no-fees.md index a122d94bbb..dd829bafdc 100644 --- a/translations/ko-KR/data/reusables/sponsors/no-fees.md +++ b/translations/ko-KR/data/reusables/sponsors/no-fees.md @@ -1 +1 @@ -{% data variables.product.prodname_sponsors %} does not charge any fees for sponsorships from user accounts, so 100% of these sponsorships go to the sponsored developer or organization. +{% data variables.product.prodname_sponsors %} does not charge any fees for sponsorships from user accounts, so 100% of these sponsorships go to the sponsored developer or organization. The 10% fee for sponsorships from organizations is waived during the beta. diff --git a/translations/ko-KR/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/ko-KR/data/reusables/sponsors/org-sponsors-release-phase.md new file mode 100644 index 0000000000..75983073a4 --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/org-sponsors-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Sponsoring on behalf of an organization is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/sponsors/pay-prorated-amount.md b/translations/ko-KR/data/reusables/sponsors/pay-prorated-amount.md new file mode 100644 index 0000000000..f201de957c --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/pay-prorated-amount.md @@ -0,0 +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 diff --git a/translations/ko-KR/data/reusables/sponsors/prorated-sponsorship.md b/translations/ko-KR/data/reusables/sponsors/prorated-sponsorship.md index f63d25e339..56a047d867 100644 --- a/translations/ko-KR/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/ko-KR/data/reusables/sponsors/prorated-sponsorship.md @@ -1 +1 @@ -You will immediately be charged a prorated amount for the time until your next regular billing date. +If you're sponsoring on behalf of your user account, you will immediately be charged a prorated amount for the time until your next regular billing date. If you're sponsoring on behalf of an organization, you can choose to pay the prorated amount or make the full monthly payment. diff --git a/translations/ko-KR/data/reusables/sponsors/sponsor-account.md b/translations/ko-KR/data/reusables/sponsors/sponsor-account.md new file mode 100644 index 0000000000..d2f8a2e73d --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/sponsor-account.md @@ -0,0 +1 @@ +1. Click **Sponsor _ACCOUNT_**. ![Sponsor button](/assets/images/help/sponsors/sponsor-developer-button.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/sponsors/sponsorship-dashboard.md b/translations/ko-KR/data/reusables/sponsors/sponsorship-dashboard.md new file mode 100644 index 0000000000..e76cb9b70c --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/sponsorship-dashboard.md @@ -0,0 +1,4 @@ +1. Navigate to your sponsorship dashboard for the account. + - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![Sponsoring button](/assets/images/help/profile/sponsoring-button.png) + - If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![Sponsoring button](/assets/images/help/sponsors/org-sponsoring-button.png) +1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/ko-KR/data/reusables/sponsors/sponsorship-details.md b/translations/ko-KR/data/reusables/sponsors/sponsorship-details.md index 55425b5c0a..6542580736 100644 --- a/translations/ko-KR/data/reusables/sponsors/sponsorship-details.md +++ b/translations/ko-KR/data/reusables/sponsors/sponsorship-details.md @@ -1 +1 @@ -Anyone with a {% data variables.product.product_name %} account can sponsor anyone with a sponsored developer profile or sponsored organization profile through a recurring monthly payment. You can choose from multiple sponsorship tiers, with monthly payment amounts and benefits that are set by the sponsored developer or organization. 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 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/webhooks/app_always_desc.md b/translations/ko-KR/data/reusables/webhooks/app_always_desc.md new file mode 100644 index 0000000000..d52aaebe58 --- /dev/null +++ b/translations/ko-KR/data/reusables/webhooks/app_always_desc.md @@ -0,0 +1 @@ +`installation` | `object` | The {% data variables.product.prodname_github_app %} installation. diff --git a/translations/ko-KR/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/ko-KR/data/reusables/webhooks/secret_scanning_alert_event_properties.md new file mode 100644 index 0000000000..239534e652 --- /dev/null +++ b/translations/ko-KR/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -0,0 +1,4 @@ +| 키 | 유형 | 설명 | +| ---- | ----- | --------------------------------------------------------------------------------------- | +| `동작` | `문자열` | The action that was performed. This can be either `created`, `resolved`, or `reopened`. | +| `경고` | `개체` | The secret scanning alert involved in the event. | diff --git a/translations/ko-KR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/ko-KR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md new file mode 100644 index 0000000000..5da7e75271 --- /dev/null +++ b/translations/ko-KR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -0,0 +1 @@ +Activity related to secret scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see “[About secret scanning](/github/administering-a-repository/about-secret-scanning).” diff --git a/translations/ko-KR/data/ui.yml b/translations/ko-KR/data/ui.yml index 0780738a45..52909bb40b 100644 --- a/translations/ko-KR/data/ui.yml +++ b/translations/ko-KR/data/ui.yml @@ -7,7 +7,7 @@ header: release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: 문서에 대한 업데이트가 자주 게시되며, 이 페이지의 번역이 아직 진행 중일 수 있습니다. 최신 정보는영어 설명서를 방문하십시오. 이 페이지에서 번역에 문제가 있는 경우 알려주십시오. localization_in_progress: 안녕하세요! 이 페이지는 현재 개발 중이거나 아직 번역 중입니다. 정확한 최신 정보를 확인하려면 영어 설명서를 방문하십시오. - early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' + early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' search: need_help: 도움이 필요하십니까? placeholder: 검색 주제, 제품... @@ -56,6 +56,14 @@ contribution_cta: button: Make a contribution or: Or, to_guidelines: learn how to contribute. +enterprise_releases_list: + title: Enterprise Server Releases + currently_supported: Currently supported + currently_supported_message: See GitHub Enterprise for information about the latest release. + deprecated: Deprecated + deprecated_message: 'These docs remain available but are no longer maintained:' + deprecated_developer: Deprecated on developer.github.com + deprecated_developer_message: 'These docs remain available on the legacy developer site but are no longer maintained:' products: graphql: reference: @@ -123,3 +131,4 @@ footer: product_landing: quick_start: Quickstart reference_guides: Reference guides + overview: 개요 diff --git a/translations/ko-KR/data/variables/action_code_examples.yml b/translations/ko-KR/data/variables/action_code_examples.yml index d68a26f48a..6eee910142 100644 --- a/translations/ko-KR/data/variables/action_code_examples.yml +++ b/translations/ko-KR/data/variables/action_code_examples.yml @@ -1,12 +1,4 @@ --- -- - title: Starter workflows - description: Workflow files for helping people get started with GitHub Actions - languages: TypeScript - href: actions/starter-workflows - tags: - - official - - 워크플로 - title: Example services description: Example workflows using service containers @@ -334,3 +326,10 @@ - monorepo - copybara - 워크플로 +- + title: Deploy static files to GitHub Pages + description: GitHub Action to publish website to GitHub Pages automatically + languages: 'TypeScript, JavaScript' + href: peaceiris/actions-gh-pages + tags: + - publishing diff --git a/translations/ko-KR/data/variables/command_line.yml b/translations/ko-KR/data/variables/command_line.yml index 805c67903e..5d1f568716 100644 --- a/translations/ko-KR/data/variables/command_line.yml +++ b/translations/ko-KR/data/variables/command_line.yml @@ -1,5 +1,5 @@ --- -#Use this variable wherever backticks are necessary: https://github.com/github/docs-internal/pull/1176#discussion-diff-19853931 +#Use this variable wherever backticks are necessary backticks: >- {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} #Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!) diff --git a/translations/ko-KR/data/variables/discussions_community_examples.yml b/translations/ko-KR/data/variables/discussions_community_examples.yml new file mode 100644 index 0000000000..8b3594f2ec --- /dev/null +++ b/translations/ko-KR/data/variables/discussions_community_examples.yml @@ -0,0 +1,38 @@ +--- +- + #Images and descriptions are pulled directly from the repo + repo: vercel/next.js + description: The React Framework +- + repo: gatsbyjs/gatsby + description: Build blazing fast, modern apps and websites with React +- + repo: nodejs/node + description: Node.js JavaScript runtime ✨🐢🚀✨ +- + repo: tailwindlabs/tailwindcss + description: A utility-first CSS framework for rapid UI development. +- + repo: laravel/framework + description: Laravel is a web application framework with expressive, elegant syntax. +- + repo: prisma/prisma + description: Modern database access (ORM alternative) for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite +- + repo: dotnet/csharplang + description: 'The official repo for the design of the C# programming language' +- + repo: home-assistant/frontend + description: '🍭 Frontend for Home Assistant' +- + repo: jspsych/jsPsych + description: A JavaScript library for creating and running behavioral experiments in a web browser +- + repo: adonisjs/core + description: '🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence' +- + repo: ImageMagick/ImageMagick + description: '🧙‍♂️ ImageMagick 7' +- + repo: react-hook-form/react-hook-form + description: '📋 React Hooks for forms validation (Web + React Native)' diff --git a/translations/ko-KR/data/variables/product.yml b/translations/ko-KR/data/variables/product.yml index 987063a361..80107ee7b5 100644 --- a/translations/ko-KR/data/variables/product.yml +++ b/translations/ko-KR/data/variables/product.yml @@ -37,7 +37,10 @@ prodname_unified_search: '통합 검색' #GitHub Education prodname_education: 'GitHub Education' prodname_education_community: 'Education Community' +prodname_education_community_with_url: 'the [GitHub Education Community](https://education.github.community)' prodname_classroom: 'GitHub Classroom' +prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)' +prodname_campus_program: 'GitHub Campus Program' prodname_student_pack: 'GitHub Student Developer Pack' #GitHub CLI prodname_cli: 'GitHub CLI' @@ -69,6 +72,8 @@ ae_azure_ad_app_link: 'the [GitHub AE application](https://azuremarketplace.micr prodname_actions: 'GitHub Actions' #GitHub Debug prodname_debug: 'GitHub Debug' +#GitHub Discussions +prodname_discussions: 'GitHub Discussions' #GitHub Packages prodname_registry: 'GitHub Packages' prodname_github_container_registry: 'GitHub Container Registry' 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 fa3cc49a71..356198c401 100644 --- a/translations/pt-BR/content/actions/creating-actions/about-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/about-actions.md @@ -33,8 +33,8 @@ Você pode compilar ações do contêiner Docker e JavaScript. As ações exigem | Tipo | Sistema operacional | | ---------------------------- | --------------------- | | Contêiner Docker | Linux | -| JavaScript | Linux, MacOS, Windows | -| Etapas de execução compostas | Linux, MacOS, Windows | +| JavaScript | Linux, macOS, Windows | +| Etapas de execução compostas | Linux, macOS, Windows | #### Ações de contêiner docker diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md index 10f5eb902b..cb4e7011e4 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md @@ -226,6 +226,10 @@ trabalhos: ``` {% endraw %} -No seu repositório, clique na aba **Ações** e selecione a última execução do fluxo de trabalho. Você deverá ver "Hello Mona the Octocat" ou o nome que você usou como entrada em `who-to-greet` e o horário impresso no log. +No seu repositório, clique na aba **Ações** e selecione a última execução do fluxo de trabalho. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Em **Trabalhos** ou no gráfico de visualização, clique em **A job to say hello**. {% endif %}Você deverá ver "Hello Mona the Octocat" ou o nome que você usou como entrada em `who-to-greet` e o horário impresso no log. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/docker-action-workflow-run-updated.png) +{% else %} ![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/docker-action-workflow-run.png) +{% endif %} diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md index 2626805293..494debeaac 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md @@ -176,7 +176,7 @@ git tag -a -m "Versão da minha primeira ação" v1 git push --follow-tags ``` -Como alternativa à verificação no seu diretório de `node_modules` você pode usar uma ferramenta denominada [`@vercel/ncc`](https://github.com/vercel/ncc) para compilar o seu código e os módulos em um arquivo usado para distribuição. +Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. 1. Instale o `vercel/ncc` executando este comando no seu terminal. `npm i -g @vercel/ncc` @@ -256,9 +256,11 @@ trabalhos: ``` {% endraw %} -No seu repositório, clique na aba **Ações** e selecione a última execução do fluxo de trabalho. Você deverá ver "Hello Mona the Octocat" ou o nome que você usou como entrada em `who-to-greet` e o horário impresso no log. +No seu repositório, clique na aba **Ações** e selecione a última execução do fluxo de trabalho. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Em **Trabalhos** ou no gráfico de visualização, clique em **A job to say hello**. {% endif %}Você deverá ver "Hello Mona the Octocat" ou o nome que você usou como entrada em `who-to-greet` e o horário impresso no log. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} ![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run-updated.png) {% else %} ![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/javascript-action-workflow-run.png) 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 9e74be3d96..c0c90c4d34 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 @@ -22,19 +22,19 @@ Ações Docker e JavaScript requerem um arquivo de metadados. O nome do arquivo Arquivos de metadados de ação usam a sintaxe YAML. Se você não souber o que é YAML, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". -### **`name`** +### `name` **Necessário**: nome de sua ação. O {% data variables.product.prodname_dotcom %} exibe o `name` (nome) na aba **Actions** (Ações) para facilitar a identificação visual das ações em cada trabalho. -### **`autor`** +### `autor` **Opcional**: nome do autor da ação. -### **`descrição`** +### `descrição` **Necessário**: uma descrição curta da ação. -### **`inputs`** +### `inputs` **Opcional**: parâmetros de entrada permitem que você especifique os dados que a ação espera usar no momento da execução. O {% data variables.product.prodname_dotcom %} armazena parâmetros como variáveis de ambiente. Identificações de entrada com letras maiúsculas são alteradas para letras minúsculas no momento da execução. Recomenda-se usar identificações de entrada com letras minúsculas. @@ -57,23 +57,23 @@ Quando você especifica uma entrada para uma ação em um arquivo de fluxo de tr 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`. -#### **`inputs.`** +#### `inputs.` **Necessário**: um identificador `string` para associar à entrada. O valor de `` é um mapa dos metadados da entrada. `` deve ser um identificador único dentro do objeto `inputs` (entradas). `` deve iniciar com uma letra ou `_` e conter somente caracteres alfanuméricos, `-` ou `_`. -#### **`inputs..description`** +#### `inputs..description` **Necessário**: descrição de `string` do parâmetro de entrada. -#### **`inputs..required`** +#### `inputs..required` **Necessário**: um `boolean` (booleano) para indicar se a ação requer o parâmetro de entrada. Defina para `true` quando o parâmetro for necessário. -#### **`inputs..default`** +#### `inputs..default` **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. -### **`outputs (saídas)`** +### `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. @@ -87,15 +87,15 @@ saídas: descrição: 'Soma das entradas' ``` -#### **`outputs.`** +#### `outputs.` **Necessário**: um identificador `string` para associar à saída. O valor de `` é um mapa dos metadados de saída. `` deve ser um identificador único dentro do objeto `outputs` (saídas). `` deve iniciar com uma letra ou `_` e conter somente caracteres alfanuméricos, `-` ou `_`. -#### **`outputs..description`** +#### `outputs..description` **Necessário**: descrição de `string` do parâmetro de saída. -### **`saídas`** para ações de etapas de execução compostas +### `outputs` para ações em etapas de execução compostas As **saídas** `opcionais` usam os mesmos parâmetros que `outputs.` e `outputs..description` (veja "[`saídas` para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), mas também inclui o token do `valor`. @@ -116,12 +116,12 @@ runs: ``` {% endraw %} -#### **`outputs.`** +#### `outputs..value` **Obrigatório** O valor com o qual o parâmetro de saída será mapeado. Você pode defini-lo como uma `string` ou uma expressão com contexto. Por exemplo, você pode usar o contexto das `etapas` para definir o `valor` de uma saída como o valor de saída de uma etapa. Para obter mais informações sobre como usar a sintaxe de contexto e expressão, consulte "[Sintaxe de contexto e expressão para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -### **`executa`** para ações JavaScript +### `runs` para ações de JavaScript **Obrigatório** Configura o caminho para o código da ação e o aplicativo usado para executar o código. @@ -133,15 +133,15 @@ executa: main: 'main.js' ``` -#### **`runs.using`** +#### `runs.using` **Obrigatório** O aplicativo usado para executar o código especificado em [`principal`](#runsmain). -#### **`runs.main`** +#### `runs.main` **Obrigatório** O arquivo que contém o código da ação. O aplicativo especificado em [`usando`](#runsusing) executa este arquivo. -#### **`pre`** +#### `pre` **Opcional** Permite que você execute um script no início de um trabalho antes de a ação `main:` começar. Por exemplo, você pode usar `pre:` para executar um pré-requisito da configuração do script. O aplicativo especificado com a sintaxe [`using`](#runsusing) executará esse arquivo. A ação `pre:` é sempre executada como padrão, mas você pode substituí-la usando [`pre-if`](#pre-if). @@ -155,7 +155,7 @@ executa: post: 'cleanup.js' ``` -#### **`pre-if`** +#### `pre-if` **Opcional** Permite que você defina condições para a execução da ação `pre:`. A ação `pre:` será executada apenas se as condições em `pre-if` forem atendidas. Se não forem definidas, o padrão de `pre-if` será `sempre()`. Observe que o contexto da `etapa` está indisponível, uma vez que nenhuma etapa foi executada ainda. @@ -166,7 +166,7 @@ Neste exemplo, o `cleanup.js` é executado apenas nos executores baseados no Lin pre-if: 'runner.os == linux' ``` -#### **`post`** +#### `post` **Opcional** Permite que você execute um script no final do trabalho, uma vez que a ação `main:` foi finalizada. Por exemplo, você pode usar `post:` para encerrar uns processos ou remover arquivos desnecessários. O aplicativo especificado com a sintaxe [`using`](#runsusing) executará esse arquivo. @@ -181,7 +181,7 @@ executa: A ação `post:` é executada sempre por padrão, mas você pode substituí-la usando `post-if`. -#### **`post-if`** +#### `post-if` **Opcional** Permite que você defina condições para a execução da ação `post:`. A ação `post:` só será executada se as condições em `post-if` forem atendidas. Se não forem definidas, o padrão de `post-if` será `sempre()`. @@ -192,19 +192,19 @@ Por exemplo, este `cleanup.js` só será executado em executores baseados no Lin post-if: 'runner.os == linux' ``` -### **`executa`** para ações de etapas de execução compostas +### `runs` para ações em etapas de execução compostas **Obrigatório** Configura o caminho para a ação composta, e o aplicativo usado para executar o código. -#### **`runs.using`** +#### `runs.using` **Obrigatório** Para usar uma ação de etapas de execução compostas, defina como `"composite"`. -#### **`runs.steps`** +#### `runs.steps` **Obrigatório** As etapas de execução que você planeja executar nesta ação. -##### **`runs.steps.run`** +##### `runs.steps.run` **Obrigatório** O comando que você deseja executar. Isso pode ser inline ou um script no seu repositório de ação: ```yaml @@ -227,27 +227,27 @@ runs: Para obter mais informações, consulte "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". -##### **`runs.steps.shell`** +##### `runs.steps.shell` **Obrigatório** O shell onde você quer executar o comando. Você pode usar qualquer um dos shells listados [aqui](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell). -##### **`runs.steps.name`** +##### `runs.steps.name` **Opcional** O nome da etapa de execução composta. -##### **`runs.steps.id`** +##### `runs.steps.id` **Opcional** Um identificador único para a 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)". -##### **`runs.steps.env`** +##### `runs.steps.env` **Opcional** Define um `mapa` de variáveis de ambiente apenas para essa etapa. Se você quiser modificar a variável de ambiente armazenada no fluxo de trabalho, use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} em uma etapa de execução composta. -##### **`runs.steps.working-directory`** +##### `runs.steps.working-directory` **Opcional** Especifica o diretório de trabalho onde o comando é executado. -### **`é executado`** para ações do Docker +### `runs` para ações do Docker **Obrigatório** Configura a imagem usada para a ação Docker. @@ -267,11 +267,11 @@ runs: image: 'docker://debian:stretch-slim' ``` -#### **`runs.using`** +#### `runs.using` **Obrigatório** Você deve definir este valor como `'docker'`. -#### **`pre-entrypoint`** +#### `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). @@ -289,21 +289,21 @@ executa: entrypoint: 'main.sh' ``` -#### **`runs.image`** +#### `runs.image` **Obrigatório ** A imagem do Docker a ser usada como contêiner para executar a ação. O valor pode ser o nome da imagem de base do Docker, um `arquivo Docker` local no seu repositório u uma imagem pública no Docker Hub ou outro registro. Para fazer referência a um `arquivo Docker` no seu repositório, use um caminho relativo ao seu arquivo de metadados da ação. O aplicativo do `docker` executará este arquivo. -#### **`runs.env`** +#### `runs.env` **Opcional** Especifica um mapa da chave/valor das variáveis do ambiente a serem definidas no ambiente do contêiner. -#### **`runs.entrypoint`** +#### `runs.entrypoint` **Opcional** Substitui o `ENTRYPOINT` do Docker no `arquivo Docker` ou o define, caso nenhum já tenha sido especificado. Use o `entrypoint` quando o `arquivo Docker` não especificar um `ENTRYPOINT` ou você desejar substituir a instrução do`ENTRYPOINT`. Se você omitir o `entrypoint`, serão executados os comandos que você especificar na instrução do `ENTRYPOINT` do Docker. A instrução do `ENTRYPOINT` do Docker tem forma de _shell_ e forma de _exec_. A documentação do `ENTRYPOINT` do docker recomenda o uso da forma _exec_ da instrução do `ENTRYPOINT`. Para obter mais informações sobre como o `entrypoint` é executado, consulte "[Suporte do arquivo Docker para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)". -#### **`post-entrypoint`** +#### `post-entrypoint` **Opcional**Permite que você execute um script de cleanup, uma vez finalizada a ação`runs.entrypoint`. {% data variables.product.prodname_actions %} usa a `execução do docker` para lançar esta ação. Porque {% data variables.product.prodname_actions %} executa o script dentro de um novo contêiner usando a mesma imagem-base, o estado do momento da execução é diferente do contêiner principal do `entrypoint`. Você pode acessar qualquer estado que precisar na área de trabalho, em `HOME` ou como variável `STATE_`. A ação `post-entrypoint:` é sempre executada por padrão, mas você pode substituí-la usando [`post-if`](#post-if). @@ -317,7 +317,7 @@ executa: post-entrypoint: 'cleanup.sh' ``` -#### **`runs.args`** +#### `runs.args` **Opcional** Um array de strings que define as entradas para um contêiner Docker. As entradas podem incluir strings com codificação rígida. O {% data variables.product.prodname_dotcom %} entrega os `args` ao `ENTRYPOINT` do contêiner quando o contêiner inicia. @@ -343,7 +343,7 @@ runs: ``` {% endraw %} -### **`branding`** +### `branding` Você pode usar uma cor e o ícone da [Pena](https://feathericons.com/) para criar um selo para personalizar e distinguir a sua ação. Os selos são exibidos ao lado do nome da sua ação em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). @@ -355,11 +355,11 @@ branding: color: 'green' ``` -#### **`branding.color`** +#### `branding.color` Cor de fundo do selo. Pode ser: `branco`, `amarelo`, `azul`, `verde`, `laranja`, `vermelho`, `roxo` ou `cinza-escuro`. -#### **`branding.icon`** +#### `branding.icon` Nome do ícone [Feather](https://feathericons.com/) (pena) para usar. 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 9ff581a456..3919a65e7c 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 @@ -25,7 +25,11 @@ Criar um pacote ao fim de um fluxo de trabalho de integração contínua pode aj Agora, ao revisar um pull request, você poderá ver a execução do fluxo de trabalho e fazer o download do artefato produzido. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down-updated.png) +{% else %} ![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down.png) +{% endif %} Isso permitirá que você execute o código no pull request em sua máquina, o que pode ajudar a depurar ou testar o pull request. 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 f4ab8f735b..373f4ef785 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 @@ -91,7 +91,7 @@ steps: ### Memorizar dependências -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. Após a conclusão bem-sucedida, a sua cache do pacote do Gradle local será armazenada na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios de pacotes remotos. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, a sua cache do pacote do Gradle local será armazenada na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios de pacotes remotos. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml 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 61693099b8..83ccbade3e 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 @@ -53,7 +53,7 @@ jobs: with: java-version: 1.8 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -85,13 +85,13 @@ steps: with: java-version: 1.8 - name: Run the Maven verify phase - run: mvn -B verify --file pom-ci.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} ### Memorizar dependências -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. Após a conclusão bem-sucedida, o seu repositório local do Maven será armazenado na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, o seu repositório local do Maven será armazenado na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml @@ -108,7 +108,7 @@ steps: key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} restore-keys: ${{ runner.os }}-m2 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -125,7 +125,7 @@ De modo geral, o Maven criará arquivos de saída como JARs, EARs ou WARs no dir steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 - - run: mvn -B package --file pom.xml + - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 with: diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md index 0ad489ba42..868fb76eff 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-nodejs.md @@ -129,7 +129,7 @@ Se você não especificar uma versão do Node.js, o {% data variables.product.pr Executores hospedados em {% data variables.product.prodname_dotcom %} têm gerenciadores de dependências npm e Yarn instalados. Você pode usar o npm e o Yarn para instalar dependências no seu fluxo de trabalho antes de criar e testar seu código. Os executores do Windows e Linux hospedados em {% data variables.product.prodname_dotcom %} também têm o Grunt, Gulp, e Bower instalado. -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você também poderá armazenar em cache dependências para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". #### Exemplo de uso do npm @@ -227,7 +227,7 @@ always-auth=true #### Exemplo de memorização de dependências -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar dependências usando uma chave única e restaurar as dependências ao executar futuros fluxos de trabalho usando a ação `cache`. Para obter mais informações, consulte "Memorizando dependências para acelerar os fluxos de trabalho" e a ação [`cache`](https://github.com/marketplace/actions/cache). {% raw %} ```yaml diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md b/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md index 642f2ada38..298386cec8 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-powershell.md @@ -60,7 +60,11 @@ jobs: * `run: Test-Path resultsfile.log` - Verifica se um arquivo denominado `resultsfile.log` está presente no diretório raiz do repositório. * `Should -Be $true` - Usa o Pester para definir um resultado esperado. Se o resultado for inesperado, {% data variables.product.prodname_actions %} irá sinalizar isso como um teste falho. Por exemplo: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Falha no teste de Pester](/assets/images/help/repository/actions-failed-pester-test-updated.png) + {% else %} ![Falha no teste de Pester](/assets/images/help/repository/actions-failed-pester-test.png) + {% endif %} * `Invoke-Pester Unit.Tests.ps1 -Passthru` - Usa o Pester para executar testes definidos em um arquivo denominado `Unit.Tests.ps1`. Por exemplo, para realizar o mesmo teste descrito acima, o `Unit.Tests.ps1` conterá o seguinte: ``` @@ -91,7 +95,7 @@ Executores hospedados em {% data variables.product.prodname_dotcom %} têm Power {% endnote %} -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você também poderá armazenar em cache dependências para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". Por exemplo, o trabalho a seguir instala os módulos `SqlServer` e `PSScriptAnalyzer`: @@ -119,7 +123,7 @@ jobs: #### Memorizar dependências -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache dependências do PowerShell usando uma chave única, o que permite que você restaure as dependências para futuros fluxos de trabalho com a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". O PowerShell armazena suas dependências em diferentes locais, dependendo do sistema operacional do executor. Por exemplo, o `caminho` local usado no exemplo do Ubuntu a seguir será diferente para um sistema operacional Windows. diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-python.md b/translations/pt-BR/content/actions/guides/building-and-testing-python.md index 66003ff6b1..4ae797f177 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-python.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-python.md @@ -192,7 +192,7 @@ Recomendamos usar `setup-python` para configurar a versão do Python usada nos s Os executores hospedados em {% data variables.product.prodname_dotcom %} têm instalado o gerenciador do pacote pip. Você pode usar o pip para instalar dependências do registro de pacotes do PyPI antes de criar e testar o seu código. Por exemplo, o YAML abaixo instala ou atualiza o instalador de pacotes `pip` e as os pacotes `setuptools` e `wheel`. -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você também poderá armazenar em cache dependências para acelerar seu fluxo de trabalho. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". {% raw %} ```yaml @@ -228,7 +228,7 @@ etapas: #### Memorizar dependências -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache dependências usando uma chave única e restaurar as dependências quando você executar fluxos de trabalho futuros usando a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". O Pip armazena dependências em diferentes locais, dependendo do sistema operacional do executor. O caminho que você precisa efetuar o armazenamento em cache pode ser diferente do exemplo do Ubuntu abaixo, dependendo do sistema operacional que você usa. Para obter mais informações, consulte [Exemplos de armazenamento em cache do Python](https://github.com/actions/cache/blob/main/examples.md#python---pip). diff --git a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md index 8b7cec1f07..6c5e5d7146 100644 --- a/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md +++ b/translations/pt-BR/content/actions/guides/building-and-testing-ruby.md @@ -148,7 +148,7 @@ steps: #### Memorizar dependências -If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +Se você estiver usando executores hospedados em {% data variables.product.prodname_dotcom %}, as ações do `setup-ruby` fornecem um método para lidar automaticamente com o cache dos seus gems entre as execuções. Para habilitar o cache, defina o seguinte. @@ -165,7 +165,7 @@ Isso irá configurar o bundler para instalar seus gems em `vendor/cache`. Para c **Fazer armazenamento em cache sem o setup-ruby** -For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +Para maior controle sobre o cache, se você estiver usando executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá usar a ação `actions/cache` diretamente. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". {% raw %} ```yaml 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 0fbe0a2545..4802e76abc 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 @@ -67,24 +67,24 @@ Na etapa de implementação, você deverá definir as variáveis de ambiente par {% raw %} ```yaml -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 no Repositório Central do Maven - usa: actions/setup-java@v1 - com: + steps: + - uses: actions/checkout@v2 + - name: Set up Maven Central Repository + uses: actions/setup-java@v1 + with: java-version: 1.8 server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - - nome: Publicar pacote - executar: mvn -B deploy + - name: Publish package + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -130,20 +130,20 @@ Com esta configuração, você pode criar um fluxo de trabalho que publica seu p {% raw %} ```yaml -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: + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-java@v1 + with: java-version: 1.8 - - nome: Publicar pacote - executar: mvn -B deploy + - name: Publish package + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` @@ -165,33 +165,33 @@ Certifique-se de que seu arquivo _pom.xml_ inclui um repositório de gerenciamen {% raw %} ```yaml -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: - - usar: actions/checkout@v2 - - nome: Configurar o Java para publicação no Repositório Central do Maven + steps: + - uses: actions/checkout@v2 + - name: Set up Java for publishing to Maven Central Repository uses: actions/setup-java@v1 with: java-version: 1.8 server-id: ossrh server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - - nome: Publicar no Repositório Central do Maven - run: mvn -B deploy + - name: Publish to the Maven Central Repository + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} - name: Set up Java for publishing to GitHub Packages - usa: actions/setup-java@v1 - com: + uses: actions/setup-java@v1 + with: java-version: 1.8 - - nome: Publicar nos pacotes do GitHub - executar: mvn -B deploy + - name: Publish to GitHub Packages + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` diff --git a/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md b/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md index 055a0ebeec..2883119128 100644 --- a/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/pt-BR/content/actions/guides/publishing-nodejs-packages.md @@ -8,8 +8,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index f0cf61a99c..631a3792dd 100644 --- a/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/pt-BR/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,8 +11,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md index de100c86f4..d9c5358029 100644 --- a/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md +++ b/translations/pt-BR/content/actions/guides/storing-workflow-data-as-artifacts.md @@ -108,8 +108,6 @@ jobs: path: output/test/code-coverage.html ``` -![Imagem de execução de fluxo de trabalho de artefato carregado em fluxo de trabalho](/assets/images/help/repository/upload-build-test-artifact.png) - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Configurar um período de retenção do artefato personalizado @@ -238,7 +236,12 @@ jobs: echo The result is $value ``` +A execução do fluxo de trabalho arquivará quaisquer artefatos gerados por ele. Para obter mais informações sobre o download de artefatos arquivados, consulte "[Fazer download dos artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts)". +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Fluxo de trabalho que transmite dados entre trabalhos para executar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% else %} ![Fluxo de trabalho que transmite dados entre trabalhos para executar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +{% endif %} {% if currentVersion == "free-pro-team@latest" %} 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 b150d1d2b1..859a4af749 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 @@ -87,7 +87,7 @@ Os sistemas operacionais a seguir são compatíveis com o aplicativo de execuç - Windows Server 2016 64-bit - Windows Server 2019 64-bit -#### MacOS +#### macOS - macOS 10.13 (High Sierra) or versão posterior diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 36c3292cfe..b0906aa35e 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -42,9 +42,9 @@ Ao criar um grupo, você deverá escolher uma política que defina quais reposit ![Adicionar grupo de executor](/assets/images/help/settings/actions-org-add-runner-group.png) 1 -Enter a name for your runner group, and assign a policy for repository access. +Insira um nome para o seu grupo de executor e atribua uma política para acesso ao repositório. - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to a specific list of repositories, all private repositories, or all repositories in the organization.{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} Você pode configurar um grupo de executores para poder ser acessado por uma lista específica de repositórios ou por todos os repositórios na organização. Por padrão, os repositórios públicos não podem acessar executores em um grupo de executor, mas você pode usar a opção **Permitir repositórios públicos** para substituir isso.{% else if currentVersion == "enterprise-server@2.22"%}Você pode configurar um grupo de executores para ser acessível por uma lista específica de repositórios, todos os repositórios privados ou todos os repositórios na organização.{% endif %} {% warning %} @@ -66,7 +66,7 @@ As empresas podem adicionar seus executores auto-hospedados a grupos para gerenc Os executores auto-hospedados são automaticamente atribuídos ao grupo-padrão quando criados e só podem ser membros de um grupo por vez. Você pode atribuir o executor a um grupo específico durante o processo de registro, ou você pode mover o executor do grupo-padrão para um grupo personalizado. -When creating a group, you must choose a policy that defines which organizations have access to the runner group. +Ao criar um grupo, você deve escolher uma política que defina quais organizações têm acesso ao grupo de executores. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -75,9 +75,9 @@ When creating a group, you must choose a policy that defines which organizations 1. Clique em **Adicionar novo** e, em seguida, **Novo grupo**. ![Adicionar grupo de executor](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) -1. Enter a name for your runner group, and assign a policy for organization access. +1. Insira um nome para o seu grupo de executor e atribua uma política para acesso à organização. - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise. By default, public repositories can't access runners in a runner group, but you can use the **Allow public repositories** option to override this.{% else if currentVersion == "enterprise-server@2.22"%}You can configure a runner group to be accessible to all organizations in the enterprise or choose specific organizations.{% endif %} + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" %} Você pode configurar um grupo para ser acessível para uma lista específica de organizações ou todas as organizações da empresa. Por padrão, os repositórios públicos não podem acessar executores em um grupo de executores, mas você pode usar a opção **Permitir repositórios públicos** para substituir isso.{% else if currentVersion == "enterprise-server@2.22"%}Você pode configurar um grupo de executores para ser acessível por todas as organizações da empresa ou escolher organizações específicas.{% endif %} {% warning %} diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md index 7d23c9b917..7de361318f 100644 --- a/translations/pt-BR/content/actions/index.md +++ b/translations/pt-BR/content/actions/index.md @@ -1,7 +1,7 @@ --- -title: Documentação do GitHub Actions +title: GitHub Actions Documentation shortTitle: GitHub Actions -intro: 'Automatize, personalize e execute seus fluxos de trabalho de desenvolvimento do software diretamente no seu repositório com o {% data variables.product.prodname_actions %}. Você pode descobrir, criar e compartilhar ações para realizar qualquer trabalho que desejar, incluindo CI/CD, bem como combinar ações em um fluxo de trabalho completamente personalizado.' +intro: 'Automate, customize, and execute your software development workflows right in your repository with {% data variables.product.prodname_actions %}. You can discover, create, and share actions to perform any job you''d like, including CI/CD, and combine actions in a completely customized workflow.' introLinks: quickstart: /actions/quickstart reference: /actions/reference @@ -25,22 +25,21 @@ featuredLinks: - /actions/reference/workflow-commands-for-github-actions - /actions/reference/environment-variables changelog: - - - title: Remover comandos set-env e add-path em 16 de novembro + - title: Removing set-env and add-path commands on November 16 date: '2020-11-09' href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ - - - title: Os últimos fluxos de trabalho do Ubuntu-20.04 + - title: Ubuntu-latest workflows will use Ubuntu-20.04 date: '2020-10-29' href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04 - - - title: Pré-visualização para MacOS Big Sur + - title: MacOS Big Sur Preview date: '2020-10-29' href: https://github.blog/changelog/2020-10-29-github-actions-macos-big-sur-preview - - - title: Alterações de acesso ao grupo de executores auto-hospedados + - title: Self-Hosted Runner Group Access Changes date: '2020-10-16' href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ + +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/ @@ -66,23 +65,23 @@ versions: {% assign actionsCodeExamples = site.data.variables.action_code_examples %} {% if actionsCodeExamples %}
      -

      Exemplos de códigos

      +

      Code examples

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

      Desculpe, não há resultados para

      -

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

      - Saiba como adicionar um exemplo de código {% octicon "arrow-right" %} +

      Sorry, there is no result for

      +

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

      + Learn how to add a code example {% octicon "arrow-right" %}
      {% endif %} diff --git a/translations/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 99b803b1ab..c9305bee90 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 @@ -204,13 +204,18 @@ Neste diagrama, você pode ver o arquivo de fluxo de trabalho que acabou de cria ### Visualizar a atividade do trabalho -Assim que seu trabalho começar a funcionar, você pode ver as atividades de cada etapa em {% data variables.product.prodname_dotcom %}. +Assim que o seu trabalho começar a ser executado, você poderá {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}ver um gráfico de visualização do progresso da execução e {% endif %}visualizar a atividade de cada etapa em {% data variables.product.prodname_dotcom %}. {% data reusables.repositories.navigate-to-repo %} 1. No nome do seu repositório, clique em **Ações**. ![Acesse o repositório](/assets/images/help/images/learn-github-actions-repository.png) 1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja ver. ![Captura de tela dos resultados do fluxo de trabalho](/assets/images/help/images/learn-github-actions-workflow.png) 1. Em "Execuções do fluxo de trabalho", clique no nome da execução que você deseja ver. ![Captura de tela das execuções do fluxo de trabalho](/assets/images/help/images/learn-github-actions-run.png) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Em **Trabalhos** ou no gráfico de visualização, clique no trabalho que você deseja ver. ![Selecionar trabalho](/assets/images/help/images/overview-actions-result-navigate.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Visualizar os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. Clique no nome do trabalho para ver os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result-updated.png) {% else %} 1. Clique no nome do trabalho para ver os resultados de cada etapa. ![Captura de tela dos detalhes de execução do fluxo de trabalho](/assets/images/help/images/overview-actions-result.png) diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md index a7bdcbea7d..2c935c122f 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -101,7 +101,7 @@ GitHub Actions -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +O armazenamento em cache de {% data variables.product.prodname_actions %} só é aplicável a executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". {% data variables.product.prodname_actions %} não tem o equivalente ao Docker Layer Caching (DLC) do CircleCI. diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 71c29a33c7..e608f5123c 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -346,7 +346,7 @@ jobs: -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +O armazenamento em cache de {% data variables.product.prodname_actions %} só é aplicável a executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". ### Artefatos diff --git a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md index ec1ff5e102..c63dd16fe9 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -165,9 +165,9 @@ git: #### Usando variáveis de ambiente em uma matriz -Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. +O Travis CI e {% data variables.product.prodname_actions %} podem adicionar variáveis de ambiente personalizadas a uma matriz de teste, que permite que você faça referência à variável em uma etapa posterior. -In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} +Em {% data variables.product.prodname_actions %}, você pode usar a chave `incluir` para adicionar variáveis de ambiente personalizadas a uma matriz. {% data reusables.github-actions.matrix-variable-example %} ### Principais recursos em {% data variables.product.prodname_actions %} @@ -322,7 +322,7 @@ cache: npm -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". +O armazenamento em cache de {% data variables.product.prodname_actions %} só é aplicável a executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "Memorizar dependências para acelerar fluxos de trabalho". ### Exemplos de tarefas comuns 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 0dd84827a9..8d55d5d083 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 @@ -54,6 +54,8 @@ Isso significa que comprometer uma única ação dentro de um fluxo de trabalho **Aviso:** A versão curta do commit SHA é insegura e nunca deve ser usada para especificar a referência do Git de uma ação. Devido ao modo como funcionam as redes de repositório, qualquer usuário pode bifurcar o repositório e fazer push de um commit criado que colida com o SHA curto. Isso faz com que os clones subsequentes falhem nesse SHA, pois se converte em um commit ambíguo. Como resultado, todos os fluxos de trabalho que usam o SHA encurtado falharão imediatamente. {% endwarning %} + + * **Audite o código-fonte da ação** Certifique-se de que a ação está tratando o conteúdo do seu repositório e os segredos, como esperado. Por exemplo, verifique se os segredos não são enviados para os hosts não intencionais, ou se não são registrados inadvertidamente. @@ -92,10 +94,14 @@ Executores **auto-hospedados** em {% data variables.product.product_name %} não Como resultado, os executores auto-hospedados quase [nunca devem ser usados para repositórios públicos](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) em {% data variables.product.product_name %}, porque qualquer usuário pode abrir pull requests contra o repositório e comprometer o ambiente. Da mesma forma, tenha cuidado ao usar executores auto-hospedados em repositórios privados, uma vez que qualquer pessoa que possa bifurcar o repositório e abrir um PR (geralmente aqueles com acesso de leitura ao repositório) são capazes de comprometer o ambiente de executores auto-hospedados, incluindo a obtenção de acesso a segredos e `GITHUB_TOKEN` mais privilegiado, que concede permissões de gravação no repositório. +Quando um executor auto-hospedado é definido no nível da organização ou empresa, {% data variables.product.product_name %} pode programar fluxos de trabalho de vários repositórios para o mesmo executor. Consequentemente, um compromisso de segurança destes ambientes pode ter um grande impacto. Para ajudar a reduzir o escopo de um compromisso, você pode criar limites organizando seus executores auto-hospedados em grupos separados. Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)". + Você também deve considerar o ambiente das máquinas de executores auto-hospedadas: - Que informação sensível reside na máquina configurada como um executor auto-hospedado? Por exemplo, chaves SSH privadas, tokens de acesso à API, entre outros. - A máquina tem acesso à rede a serviços sensíveis? Por exemplo, serviços de metadados do Azure ou AWS. A quantidade de informações confidenciais neste ambiente deve ser limitada ao mínimo, e você deve estar sempre ciente de que qualquer usuário capaz de invocar fluxos de trabalho terá acesso a esse ambiente. +Alguns clientes podem tentar mitigar parcialmente esses riscos implementando sistemas que destroem automaticamente o executor auto-hospedado após cada execução do trabalho. No entanto, esta abordagem poderá não ser tão eficaz como pretendido, uma vez que não há forma de garantir que um executor auto-hospedado execute apenas um trabalho. + ### Auditar eventos de {% data variables.product.prodname_actions %} 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. @@ -130,5 +136,3 @@ As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_a | `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. | - - diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md index 014e40c95d..04520e1ff2 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -17,8 +17,13 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} -{% data reusables.repositories.view-run %} -1. No canto superior direito do fluxo de trabalho, clique em **Cancelar fluxo de trabalho**. ![Botão Cancel check suite (Cancelar conjunto de verificações)](/assets/images/help/repository/cancel-check-suite.png) +1. Na lista de execuções do fluxo de trabalho, clique no nome da execução em estado `queued` ou `em progresso` que você deseja cancelar. ![Nome da execução do fluxo de trabalho](/assets/images/help/repository/in-progress-run.png) +1. No canto superior direito do fluxo de trabalho, clique em **Cancelar fluxo de trabalho**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Botão Cancel check suite (Cancelar conjunto de verificações)](/assets/images/help/repository/cancel-check-suite-updated.png) +{% else %} + ![Botão Cancel check suite (Cancelar conjunto de verificações)](/assets/images/help/repository/cancel-check-suite.png) +{% endif %} ### Etapas que o {% data variables.product.prodname_dotcom %} realiza para cancelar uma execução de fluxo de trabalho diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 1d72a57b16..b64fe15226 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -19,4 +19,9 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Em **Artefatos**, clique no artefato que deseja baixar. ![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down.png) +1. Em **Artefatos**, clique no artefato que deseja baixar. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down-updated.png) + {% else %} + ![Menu suspenso do para fazer download do artefato](/assets/images/help/repository/artifact-drop-down.png) + {% endif %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/index.md b/translations/pt-BR/content/actions/managing-workflow-runs/index.md index d0199b7c06..d7a79763ae 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/index.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/index.md @@ -18,6 +18,7 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% link_in_list /using-the-visualization-graph %}{% endif %} {% link_in_list /viewing-workflow-run-history %} {% link_in_list /using-workflow-run-logs %} {% link_in_list /manually-running-a-workflow %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md index 8374c0bc65..b4dda727e6 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -16,4 +16,4 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. No canto superior direito do fluxo de trabalho, use o menu suspenso **Reexecutar trabalhos** e selecione **Reexecutar todos os trabalhos**. ![Menu suspenso Re-run checks (Executar verificações novamente)](/assets/images/help/repository/rerun-checks-drop-down.png) +1. No canto superior direito do fluxo de trabalho, use o menu suspenso **Reexecutar trabalhos** e selecione **Reexecutar todos os trabalhos**{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 227e551f7c..eb9273cabd 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -26,7 +26,13 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Em **Artefatos**, clique em {% octicon "trashcan" aria-label="The trashcan icon" %} ao lado do artefato que você deseja remover. ![Menu suspenso para excluir o artefato](/assets/images/help/repository/actions-delete-artifact.png) +1. Em **Artefatos**, clique em +{% octicon "trashcan" aria-label="The trashcan icon" %} ao lado do artefato que você deseja remover. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Menu suspenso para excluir o artefato](/assets/images/help/repository/actions-delete-artifact-updated.png) + {% else %} + ![Menu suspenso para excluir o artefato](/assets/images/help/repository/actions-delete-artifact.png) + {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Definir o período de retenção para um artefato diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/pt-BR/content/actions/managing-workflow-runs/using-the-visualization-graph.md new file mode 100644 index 0000000000..19cdd64408 --- /dev/null +++ b/translations/pt-BR/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -0,0 +1,21 @@ +--- +title: Usar o gráfico de visualização +intro: Cada execução de fluxo de trabalho gera um gráfico em tempo real que ilustra o progresso da execução. Você pode usar este gráfico para monitorar e depurar fluxos de trabalho. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.visualization-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} + +1. O gráfico exibe cada trabalho no fluxo de trabalho. Um ícone à esquerda do nome do trabalho indica o status do trabalho. As linhas entre as trabalhos indicam dependências. ![Gráfico de fluxo de trabalho](/assets/images/help/images/workflow-graph.png) + +2. Clique em um trabalho para visualizar o registro da tarefa. ![Gráfico de fluxo de trabalho](/assets/images/help/images/workflow-graph-job.png) diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md index eac8188e84..fa20d9daa8 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -44,7 +44,12 @@ Para trabalhos executados em executores hospedados no {% data variables.product. {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. No canto superior direito da saída do log, na caixa **Search logs** (Pesquisar logs), digite um termo de consulta. ![Caixa de pesquisa de logs](/assets/images/help/repository/search-log-box-updated.png) +1. No canto superior direito da saída do log, na caixa **Search logs** (Pesquisar logs), digite um termo de consulta. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Caixa de pesquisa de logs](/assets/images/help/repository/search-log-box-updated-2.png) +{% else %} + ![Caixa de pesquisa de logs](/assets/images/help/repository/search-log-box-updated.png) +{% endif %} {% else %} 1. Para expandir cada etapa que você pretende incluir na pesquisa, clique na etapa.![Nome da etapa](/assets/images/help/repository/failed-check-step.png) 1. No canto superior direito da saída do log, na caixa **Search logs** (Pesquisar logs), digite um termo de consulta. ![Caixa de pesquisa de logs](/assets/images/help/repository/search-log-box.png) @@ -61,8 +66,12 @@ Você pode fazer o download dos arquivos de registro da execução do seu fluxo {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 1. No canto superior direito, clique em -{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e selecione **Fazer o download o arquivo de registro**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} e selecione **Fazer download do arquivo do registro**. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Menu suspenso Download logs (Baixar logs)](/assets/images/help/repository/download-logs-drop-down-updated-2.png) + {% else %} ![Menu suspenso Download logs (Baixar logs)](/assets/images/help/repository/download-logs-drop-down-updated.png) + {% endif %} {% else %} 1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e selecione **Fazer o download o arquivo de registro**. @@ -78,8 +87,20 @@ Você pode excluir arquivos de registro da execução do seu fluxo de trabalho. {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ícone horizontal do kebab](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) -2. Para excluir os arquivos de registro, clique no botão **Excluir todos os registros** e revise a instrução de confirmação. ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png)Após excluir os registros, o botão **Excluir todos os registros** será removido para indicar que não restaram arquivos de registro na execução do fluxo de trabalho. +1. No canto superior direito, clique em +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Ícone horizontal do kebab](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) + {% else %} + ![Ícone horizontal do kebab](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) + {% endif %} +2. Para excluir os arquivos de registro, clique no botão **Excluir todos os registros** e revise a instrução de confirmação. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Excluir todos os registros](/assets/images/help/repository/delete-all-logs-updated-2.png) + {% else %} + ![Excluir todos os registros](/assets/images/help/repository/delete-all-logs-updated.png) + {% endif %} +Após excluir os registros, o botão **Excluir todos os registros** será removido para indicar que nenhum arquivo de registro permaneça na execução do fluxo de trabalho. {% else %} 1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ícone horizontal do kebab](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png) 2. Para excluir os arquivos de registro, clique no botão **Excluir todos os registros** e revise a instrução de confirmação. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) Depois que os registros forem excluídos, o botão **Excluir todos os registros** é removido para indicar que nenhum arquivo de registro permanece na execução do fluxo de trabalho. diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/pt-BR/content/actions/managing-workflow-runs/viewing-job-execution-time.md index de546bd8cc..9f0b77f2a0 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/viewing-job-execution-time.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -15,7 +15,7 @@ Os minutos de execução de um trabalho faturável são exibidos para trabalhos {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. No resumo do trabalho, você pode ver o tempo de execução do trabalho. Para visualizar o tempo faturável de execução do trabalho, clique em **Informações de tempo de execução e de tempo faturável**. ![Link com informações sobre o tempo faturável e execução](/assets/images/help/repository/view-run-billable-time.png) +1. No resumo do trabalho, você pode ver o tempo de execução do trabalho. Para visualizar os detalhes sobre o tempo de execução do trabalho faturável, clique no tempo abaixo do **Tempo faturável**. ![Link com informações sobre o tempo faturável e execução](/assets/images/help/repository/view-run-billable-time.png) {% note %} diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md index 9da0b4a78c..d762304a99 100644 --- a/translations/pt-BR/content/actions/quickstart.md +++ b/translations/pt-BR/content/actions/quickstart.md @@ -59,7 +59,11 @@ Fazer commit do arquivo de fluxo de trabalho no repositório aciona o evento `pu {% 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. 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 %} ### Mais fluxos de trabalho iniciais @@ -101,7 +105,7 @@ Imprimir "Olá, mundo!" é uma ótima maneira de explorar a configuração e a s # When the event is triggered, GitHub Actions will run the jobs indicated jobs: say_hello: - # Uses a ubuntu-lates runner to complete the requested steps + # Uses a ubuntu-latest runner to complete the requested steps runs-on: ubuntu-latest steps: - run: | diff --git a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 79537ed880..654b6591e2 100644 --- a/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,7 +75,7 @@ Para usar a sintaxe de propriedade de desreferência, o nome da propriedade deve - começar com `a-Z` ou `_`; - ser seguido por `a-Z` `0-9` `-` ou `_`. -#### **Contexto `github`** +#### Contexto `github` O contexto `github` context contém informações sobre a execução do fluxo de trabalho e sobre o evento que a acionou. Você pode ler a maioria dos dados de contexto `github` em variáveis de ambiente. Para obter mais informações sobre as variáveis de ambiente, consulte "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)". @@ -103,7 +103,7 @@ O contexto `github` context contém informações sobre a execução do fluxo de | `github.workflow` | `string` | Nome do fluxo de trabalho. Se o fluxo de trabalho não determina um `name` (nome), o valor desta propriedade é o caminho completo do arquivo do fluxo de trabalho no repositório. | | `github.workspace` | `string` | O diretório-padrão de trabalho para etapas e a localização-padrão do repositório ao usar a ação [`checkout-`](https://github.com/actions/checkout). | -#### **Contexto `env`** +#### Contexto `env` O contexto `env` contém variáveis de ambiente que foram definidas em um fluxo de trabalho, trabalho ou etapa. Para obter mais informações sobre como configurar variáveis de ambiente em seu fluxo de trabalho, consulte "[Sintaxe do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)". @@ -117,7 +117,7 @@ Você só pode usar o contexto `env` no valor de `com` e as chaves do `nome` ou | `env.` | `string` | O valor de uma variável de ambiente específica. | -#### **Contexto `trabalho`** +#### Contexto `trabalho` O contexto `job` (trabalho) contém informações sobre o trabalho atualmente em execução. @@ -133,7 +133,7 @@ O contexto `job` (trabalho) contém informações sobre o trabalho atualmente em | `job.services..ports` | `objeto` | As portas expostas do contêiner de serviço. | | `job.status` | `string` | Status atual do trabalho. Possíveis valores são `success`, `failure` ou `cancelled`. | -#### **Contexto `etapas`** +#### Contexto `etapas` O contexto `steps` (etapas) contém informações sobre as etapas já executadas do trabalho atual. @@ -145,7 +145,7 @@ O contexto `steps` (etapas) contém informações sobre as etapas já executadas | `steps..outcome` | `string` | O resultado de uma etapa concluída antes de [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) ser aplicado. Os valores possíveis são: `sucesso`, `falha`, `cancelado`ou `ignorado`. Quando ocorre uma falha na etapa de `continue-on-error`, o `resultado` será `falha`, mas a conclusão `final` será `sucesso`. | | `steps..outputs.` | `string` | Valor de uma saída específica. | -#### **Contexto do `executor`** +#### Contexto do `executor` O contexto do `executor` contém informações sobre o executor que está executando o trabalho atual. @@ -155,7 +155,7 @@ O contexto do `executor` contém informações sobre o executor que está execut | `runner.temp` | `string` | O caminho do diretório temporário para o executor. É certo que este diretório estará vazio no início de cada trabalho, mesmo em executores auto-hospedados. | | `runner.tool_cache` | `string` | O caminho do diretório que contém algumas das ferramentas pré-instaladas para executores hospedados no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Especificações para executores hospedados no {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". | -#### **Contexto `needs`** +#### Contexto `needs` O contexto `needs` contém saídas de todos os trabalhos definidos como uma dependência do trabalho atual. Para obter mais informações sobre a definição de dependências de tarefas, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)". 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 29e172067e..d35c6d5779 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 @@ -137,9 +137,9 @@ jobs: #### `repository_dispatch` -| Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------- | ------------------ | --------------------------------------------- | ------------------------ | -| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Último commit de merge no branch `GITHUB_REF` | Branch que recebeu envio | +| Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------------------- | ------------------ | ------------------------------ | ------------- | +| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Último commit no branch padrão | Branch padrão | {% data reusables.github-actions.branch-requirement %} @@ -699,6 +699,8 @@ on: {% data reusables.webhooks.workflow_run_desc %} +{% data reusables.github-actions.branch-requirement %} + | Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------- | ------------------ | ------------------------------ | ------------- | | [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - n/a | Último commit no branch padrão | Branch padrão | diff --git a/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md index 84ee8a1a71..c20ede373b 100644 --- a/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/pt-BR/content/actions/reference/specifications-for-github-hosted-runners.md @@ -63,8 +63,8 @@ As ferramentas do software incluídas em executores hospedados em {% data variab * [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md) * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md) -* [MacOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) -* [MacOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) +* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) {% data reusables.github-actions.ubuntu-runner-preview %} {% data reusables.github-actions.macos-runner-preview %} 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 5ba82777f1..863f1adada 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 @@ -21,17 +21,17 @@ Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file ex You must store workflow files in the `.github/workflows` directory of your repository. -### **`name`** +### `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. -### **`on`** +### `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)." {% data reusables.github-actions.actions-on-examples %} -### **`on..types`** +### `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. @@ -45,7 +45,7 @@ on: types: [published, created, edited] ``` -### **`on..`** +### `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. @@ -112,7 +112,7 @@ on: - '!releases/**-alpha' ``` -### **`on..paths`** +### `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. @@ -179,13 +179,13 @@ The filter determines if a workflow should run by evaluating the changed files a For more information, see "[About comparing branches in pull requests](/articles/about-comparing-branches-in-pull-requests)." -### **`on.schedule`** +### `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)." -### **`env`** +### `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). @@ -198,13 +198,13 @@ env: SERVER: production ``` -### **`defaults`** +### `defaults` 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). {% data reusables.github-actions.defaults-override %} -### **`defaults.run`** +### `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. @@ -219,7 +219,7 @@ defaults: working-directory: scripts ``` -### **`jobs`** +### `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. @@ -229,7 +229,7 @@ You can run an unlimited number of jobs as long as you are within the workflow u If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." -### **`jobs.`** +### `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 `_`. @@ -243,15 +243,15 @@ jobs: name: My second job ``` -### **`jobs..name`** +### `jobs..name` The name of the job displayed on {% data variables.product.prodname_dotcom %}. -### **`jobs..needs`** +### `jobs..needs` -Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional statement that causes the job to continue. +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. -#### Example +#### Example requiring dependent jobs to be successful ```yaml jobs: @@ -270,7 +270,21 @@ The jobs in this example run sequentially: 2. `job2` 3. `job3` -### **`jobs..runs-on`** +#### Example not requiring dependent jobs to be successful + +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + if: always() + 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)." + +### `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. @@ -286,7 +300,7 @@ Available {% data variables.product.prodname_dotcom %}-hosted runner types are: {% data reusables.github-actions.ubuntu-runner-preview %} -##### **Example** +##### Example ```yaml runs-on: ubuntu-latest @@ -298,7 +312,7 @@ For more information, see "[Virtual environments for {% data variables.product.p {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -##### **Example** +##### Example ```yaml runs-on: [self-hosted, linux] @@ -306,7 +320,7 @@ 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)." -### **`jobs..outputs`** +### `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). @@ -314,7 +328,7 @@ Job outputs are strings, and job outputs containing expressions are evaluated on 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)." -#### **Example** +#### Example {% raw %} ```yaml @@ -338,13 +352,13 @@ jobs: ``` {% endraw %} -### **`jobs..env`** +### `jobs..env` A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs..steps.env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -#### **Example** +#### Example ```yaml jobs: @@ -353,13 +367,13 @@ jobs: FIRST_NAME: Mona ``` -### **`jobs..defaults`** +### `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). {% data reusables.github-actions.defaults-override %} -### **`jobs..defaults.run`** +### `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. @@ -379,13 +393,13 @@ jobs: working-directory: scripts ``` -### **`jobs..if`** +### `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. {% 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)." -### **`jobs..steps`** +### `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. @@ -415,17 +429,17 @@ jobs: ``` {% endraw %} -#### **`jobs..steps.id`** +### `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)." -#### **`jobs..steps.if`** +### `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. {% 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)." -##### Example using contexts +#### Example using contexts This step only runs when the event type is a `pull_request` and the event action is `unassigned`. @@ -436,7 +450,7 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -##### Example using status check functions +#### Example using status check functions 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)." @@ -449,11 +463,11 @@ steps: uses: actions/heroku@1.0.0 ``` -#### **`jobs..steps.name`** +### `jobs..steps.name` A name for your step to display on {% data variables.product.prodname_dotcom %}. -#### **`jobs..steps.uses`** +### `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/). @@ -466,7 +480,7 @@ Some actions require inputs that you must set using the [`with`](#jobsjob_idstep 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). -##### Example using versioned actions +#### Example using versioned actions ```yaml steps: @@ -480,7 +494,7 @@ steps: - uses: actions/setup-node@main ``` -##### Example using a public action +#### Example using a public action `{owner}/{repo}@{ref}` @@ -498,7 +512,7 @@ jobs: uses: actions/aws@v2.0.1 ``` -##### Example using a public action in a subdirectory +#### Example using a public action in a subdirectory `{owner}/{repo}/{path}@{ref}` @@ -512,7 +526,7 @@ jobs: uses: actions/aws/ec2@main ``` -##### Example using action in the same repository as the workflow +#### Example using action in the same repository as the workflow `./path/to/dir` @@ -528,7 +542,7 @@ jobs: uses: ./.github/actions/my-action ``` -##### Example using a Docker Hub action +#### Example using a Docker Hub action `docker://{image}:{tag}` @@ -542,7 +556,7 @@ jobs: uses: docker://alpine:3.8 ``` -##### Example using a Docker public registry action +#### Example using a Docker public registry action `docker://{host}/{image}:{tag}` @@ -556,7 +570,7 @@ jobs: uses: docker://gcr.io/cloud-builders/gradle ``` -#### **`jobs..steps.run`** +### `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. @@ -588,7 +602,7 @@ Using the `working-directory` keyword, you can specify the working directory of working-directory: ./temp ``` -##### Using a specific shell +#### Using a specific shell You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. @@ -601,7 +615,7 @@ You can override the default shell settings in the runner's operating system usi | 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}'"`. | -##### Example running a script using bash +#### Example running a script using bash ```yaml steps: @@ -610,7 +624,7 @@ steps: shell: bash ``` -##### Example running a script using Windows `cmd` +#### Example running a script using Windows `cmd` ```yaml steps: @@ -619,7 +633,7 @@ steps: shell: cmd ``` -##### Example running a script using PowerShell Core +#### Example running a script using PowerShell Core ```yaml steps: @@ -628,7 +642,7 @@ steps: shell: pwsh ``` -##### Example running a python script +#### Example running a python script ```yaml steps: @@ -639,11 +653,11 @@ steps: shell: python ``` -##### Custom shell +#### Custom shell You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`. -##### Exit codes and error action preference +#### Exit codes and error action preference 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. @@ -661,11 +675,11 @@ For built-in shell keywords, we provide the following defaults that are executed - 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. -#### **`jobs..steps.with`** +### `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. -##### Example +#### Example 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. @@ -681,11 +695,11 @@ jobs: last_name: Octocat ``` -#### **`jobs..steps.with.args`** +### `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. -##### Example +#### Example {% raw %} ```yaml @@ -704,11 +718,11 @@ The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you 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. -#### **`jobs..steps.with.entrypoint`** +### `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. -##### Example +#### Example ```yaml steps: @@ -720,7 +734,7 @@ steps: The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. -#### **`jobs..steps.env`** +### `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). @@ -728,7 +742,7 @@ Sets environment variables for steps to use in the runner environment. You can a 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)." -##### Example +#### Example {% raw %} ```yaml @@ -741,23 +755,23 @@ steps: ``` {% endraw %} -#### **`jobs..steps.continue-on-error`** +### `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. -#### **`jobs..steps.timeout-minutes`** +### `jobs..steps.timeout-minutes` The maximum number of minutes to run the step before killing the process. -### **`jobs..timeout-minutes`** +### `jobs..timeout-minutes` The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360 -### **`jobs..strategy`** +### `jobs..strategy` A strategy creates a build matrix for your jobs. You can define different variations of an environment to run each job in. -#### **`jobs..strategy.matrix`** +### `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. @@ -767,7 +781,7 @@ Each option you define in the `matrix` has a key and value. The keys you define The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow. -##### Example running with more than one version of Node.js +#### Example running with more than one version of 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`. @@ -789,7 +803,7 @@ steps: 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. -##### Example running with more than one operating system +#### Example running with more than one operating system 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: @@ -814,7 +828,7 @@ steps: 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)." -##### Example including additional values into combinations +#### Example including additional values into combinations 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. @@ -834,7 +848,7 @@ strategy: ``` {% endraw %} -##### Example including new combinations +#### Example including new combinations 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. @@ -852,7 +866,7 @@ strategy: ``` {% endraw %} -##### Example excluding configurations from a matrix +#### Example excluding configurations from a matrix 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`). @@ -882,11 +896,11 @@ You can add custom environment variables for each test combination by using the {% data reusables.github-actions.matrix-variable-example %} -### **`jobs..strategy.fail-fast`** +### `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` -### **`jobs..strategy.max-parallel`** +### `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. @@ -895,7 +909,7 @@ strategy: max-parallel: 2 ``` -### **`jobs..continue-on-error`** +### `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. @@ -920,7 +934,7 @@ strategy: ``` {% endraw %} -### **`jobs..container`** +### `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. @@ -950,16 +964,17 @@ jobs: container: node:10.16-jessie ``` -#### **`jobs..container.image`** +### `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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..container.credentials`** + +### `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -##### Example +#### Example {% raw %} ```yaml @@ -972,15 +987,15 @@ container: {% endraw %} {% endif %} -#### **`jobs..container.env`** +### `jobs..container.env` Sets a `map` of environment variables in the container. -#### **`jobs..container.ports`** +### `jobs..container.ports` Sets an `array` of ports to expose on the container. -#### **`jobs..container.volumes`** +### `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. @@ -990,7 +1005,7 @@ To specify a volume, you specify the source and destination path: The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -##### Example +#### Example ```yaml volumes: @@ -999,11 +1014,11 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..container.options`** +### `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)." -### **`jobs..services`** +### `jobs..services` {% data reusables.github-actions.docker-container-os-support %} @@ -1033,16 +1048,17 @@ services: - 6379/tcp ``` -#### **`jobs..services..image`** +### `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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..services..credentials`** + +### `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -##### Example +#### Example {% raw %} ```yaml @@ -1061,15 +1077,15 @@ services: {% endraw %} {% endif %} -#### **`jobs..services..env`** +### `jobs..services..env` Sets a `map` of environment variables in the service container. -#### **`jobs..services..ports`** +### `jobs..services..ports` Sets an `array` of ports to expose on the service container. -#### **`jobs..services..volumes`** +### `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. @@ -1079,7 +1095,7 @@ To specify a volume, you specify the source and destination path: The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -##### Example +#### Example ```yaml volumes: @@ -1088,7 +1104,7 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..services..options`** +### `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)." diff --git a/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md b/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md index 6a43289ead..8b15bdb071 100644 --- a/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md +++ b/translations/pt-BR/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: As contas de usuário no {% data variables.product.product_location %} são preservadas quando você altera o método de autenticação, e os usuários continuarão fazendo login na mesma conta (desde que não haja alteração nos nomes de usuário). -Se o novo método de autenticação alterar nomes de usuários, serão criadas novas contas. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). +Se o novo método de autenticação alterar nomes de usuários, serão criadas novas contas. Como administrador, você pode renomear os usuários por meio das configurações de administrador do site ou usando [a API de Administração de Usuário](/rest/reference/enterprise-admin#update-the-username-for-a-user). Veja outras questões que você deve manter em mente: diff --git a/translations/pt-BR/content/admin/configuration/index.md b/translations/pt-BR/content/admin/configuration/index.md index 1968eda320..fb4e38d0a3 100644 --- a/translations/pt-BR/content/admin/configuration/index.md +++ b/translations/pt-BR/content/admin/configuration/index.md @@ -31,9 +31,7 @@ versions: {% link_in_list /enabling-private-mode %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} - {% link_in_list /configuring-applications %} - {% link_in_list /troubleshooting-ssl-errors %} {% link_in_list /configuring-time-synchronization %} {% link_in_list /command-line-utilities %} @@ -54,11 +52,7 @@ versions: {% link_in_list /connecting-github-enterprise-server-to-github-enterprise-cloud %} {% link_in_list /enabling-unified-search-between-github-enterprise-server-and-githubcom %} {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %} - {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %} {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} - - {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} - diff --git a/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md index acaa155a21..e0c1be5124 100644 --- a/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/pt-BR/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -37,7 +37,7 @@ O tempo do failover dependerá do tempo necessário para promover manualmente a ``` - No novo primário, remova os UUIDs usando `ghe-repl-teardown`. Substitua *`UUID`* por um UUID que você recuperou na etapa anterior. ```shell - $ ghe-repl-teardown -u UUNID + $ ghe-repl-teardown -u UUID ``` ### Leia mais 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 e2b743fada..51abb54c9c 100644 --- a/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ b/translations/pt-BR/content/admin/github-actions/manually-syncing-actions-from-githubcom.md @@ -24,7 +24,7 @@ A ferramenta `actions-sync` só pode fazer download de ações de {% data variab ### Pré-requisitos -* Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino existam na instância corporativa. O exemplo a seguir demonstra como sincronizar ações com uma organização denominada `synced-actions` em uma instância corporativa. 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](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)". * Você deve criar um token de acesso pessoal (PAT) na instância corporativa que pode criar e gravar em repositórios nas organizações de destino. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." ### Exemplo: Usando a ferramenta de `actions-sync` diff --git a/translations/pt-BR/content/admin/index.md b/translations/pt-BR/content/admin/index.md index bf33586b9d..f4fa39f5e0 100644 --- a/translations/pt-BR/content/admin/index.md +++ b/translations/pt-BR/content/admin/index.md @@ -28,3 +28,5 @@ versions: {% link_with_intro /packages %} {% link_with_intro /enterprise-support %} + +{% link_with_intro /release-notes %} diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md index 7b3202222a..9d0fb4fc2e 100644 --- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md @@ -1,6 +1,6 @@ --- title: Sobre contas corporativas -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 %}.' +intro: 'Com {% data variables.product.product_name %}, você pode usar uma conta corporativa para dar aos administradores um único ponto de visibilidade e gestão{% if enterpriseServerVersions contains currentVersion %} para cobrança e uso da licença{% endif %}.' redirect_from: - /enterprise/admin/installation/about-enterprise-accounts - /enterprise/admin/overview/about-enterprise-accounts @@ -11,14 +11,14 @@ versions: ### Sobre as contas corporativas do {% 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 %}. Sua conta corporativa deve ter um manipulador, como uma conta pessoal ou organizacional no {% data variables.product.prodname_dotcom %}. Os administradores corporativos podem gerenciar configurações e preferências, como: +Uma conta corporativa permite gerenciar várias organizações{% if enterpriseServerVersions contains currentVersion %} e instâncias de {% data variables.product.prodname_ghe_server %} {% else %} em {% data variables.product.product_name %}{% endif %}. Sua conta corporativa deve ter um manipulador, como uma conta pessoal ou organizacional no {% data variables.product.prodname_dotcom %}. Os administradores corporativos podem gerenciar configurações e preferências, como: -- 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 %} +- Acesso de integrante e gerenciamento (integrantes da organização, colaboradores externos){% if enterpriseServerVersions contains currentVersion %} +- Cobrança e uso (instâncias de {% data variables.product.prodname_ghe_server %}, licenças de usuário, pacotes de {% data variables.large_files.product_name_short %}){% endif %} +- Segurança {% if enterpriseServerVersions contains currentVersion %}(logon único, autenticação de dois fatores) +- Compartilhamento de pacotes de solicitação e {% if enterpriseServerVersions contains currentVersion %}suporte {% endif %} com {% data variables.contact.enterprise_support %}{% endif %} -{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} Para ver mais informações sobre como gerenciar sua assinatura de {% data variables.product.prodname_ghe_cloud %}, consulte "[Visualizar a assinatura e o uso para sua conta corporativa](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}Para obter mais informações sobre como gerenciar suas configurações de cobrança de {% data variables.product.product_name %}, consulte "[Gerenciar cobrança para sua empresa](/admin/overview/managing-billing-for-your-enterprise)". {% if enterpriseServerVersions contains currentVersion %} diff --git a/translations/pt-BR/content/admin/release-notes.md b/translations/pt-BR/content/admin/release-notes.md index fecb63f3f2..420c4f4b64 100644 --- a/translations/pt-BR/content/admin/release-notes.md +++ b/translations/pt-BR/content/admin/release-notes.md @@ -1,6 +1,6 @@ --- title: Notas de lançamento -intro: The release notes for {{ allVersions[currentVersion].versionTitle }}. +intro: As observações de versão para {{ allVersions[currentVersion].versionTitle }}. layout: release-notes versions: enterprise-server: '*' 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 fb75a36cfc..a0e8616d25 100644 --- a/translations/pt-BR/content/admin/user-management/audited-actions.md +++ b/translations/pt-BR/content/admin/user-management/audited-actions.md @@ -39,9 +39,9 @@ versions: | Nome | Descrição | | -------------------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `business.update_member_repository_creation_permission` | Um administrador do site restringe a criação de repositórios em organizações da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)". | -| `business.clear_members_can_create_repos` | Um administrador do site elimina uma restrição de criação de repositórios em organizações da empresa. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."{% if enterpriseServerVersions contains currentVersion %} +| `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)".{% if enterpriseServerVersions contains currentVersion %} | `enterprise.config.lock_anonymous_git_access` | Um administrador do site bloqueia acessos de leitura anônimos do Git para impedir que os administradores do repositório alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | -| `enterprise.config.unlock_anonymous_git_access` | Um administrador do site desbloqueia acessos de leitura anônimos do Git para permitir que administradores alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."{% endif %} +| `enterprise.config.unlock_anonymous_git_access` | Um administrador do site desbloqueia acessos de leitura anônimos do Git para permitir que administradores alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)".{% endif %} #### Problemas e pull requests @@ -77,23 +77,23 @@ versions: #### Repositórios -| Nome | Descrição | -| ------------------------------------------:| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `repo.access` | The visibility of a repository changed to private{% if enterpriseServerVersions contains currentVersion %}, public,{% endif %} or internal. | -| `repo.archive` | Um repositório foi arquivado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | -| `repo.add_member` | Um colaborador foi adicionado ao repositório. | -| `repo.config` | Um administrador do site bloqueou a opção de forçar pushes. Para obter mais informações, consulte [Bloquear pushes forçados em um repositório](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/). | -| `repo.create` | Um repositório foi criado. | -| `repo.destroy` | Um repositório foi excluído. | -| `repo.remove_member` | Um colaborador foi removido do repositório. | -| `repo.rename` | Um repositório foi renomeado. | -| `repo.transfer` | Um usuário aceitou uma solicitação para receber um repositório transferido. | -| `repo.transfer_start` | Um usuário enviou uma solicitação para transferir um repositório a outro usuário ou organização. | -| `repo.unarchive` | Um repositório teve o arquivamento cancelado. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."{% if enterpriseServerVersions contains currentVersion %} -| `repo.config.disable_anonymous_git_access` | Anonymous Git read access is disabled for a repository. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | -| `repo.config.enable_anonymous_git_access` | Anonymous Git read access is enabled for a repository. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | -| `repo.config.lock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está bloqueado, impedindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | -| `repo.config.unlock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está desbloqueado, permitindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. For more information, see "[Preventing users from changing anonymous Git read access](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %} +| Nome | Descrição | +| ------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `repo.access` | A visibilidade de um repositório alterado para privado{% if enterpriseServerVersions contains currentVersion %}, público,{% endif %} ou interno. | +| `repo.archive` | Um repositório foi arquivado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | +| `repo.add_member` | Um colaborador foi adicionado ao repositório. | +| `repo.config` | Um administrador do site bloqueou a opção de forçar pushes. Para obter mais informações, consulte [Bloquear pushes forçados em um repositório](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/). | +| `repo.create` | Um repositório foi criado. | +| `repo.destroy` | Um repositório foi excluído. | +| `repo.remove_member` | Um colaborador foi removido do repositório. | +| `repo.rename` | Um repositório foi renomeado. | +| `repo.transfer` | Um usuário aceitou uma solicitação para receber um repositório transferido. | +| `repo.transfer_start` | Um usuário enviou uma solicitação para transferir um repositório a outro usuário ou organização. | +| `repo.unarchive` | Um repositório teve o arquivamento cancelado. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)".{% if enterpriseServerVersions contains currentVersion %} +| `repo.config.disable_anonymous_git_access` | O acesso de leitura anônimo do Git está desabilitado em um repositório. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | +| `repo.config.enable_anonymous_git_access` | O acesso de leitura anônimo do Git está abilitado em um repositório. Para obter mais informações, consulte "[Habilitar acesso de leitura anônimo do Git para um repositório](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)". | +| `repo.config.lock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está bloqueado, impedindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterarem o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)". | +| `repo.config.unlock_anonymous_git_access` | O acesso de leitura anônimo de um repositório do Git está desbloqueado, permitindo que os administradores de repositório alterem (habilitem ou desabilitem) essa configuração. Para obter mais informações, consulte "[Impedir os usuários de alterar o acesso de leitura anônimo do Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."{% endif %} #### Ferramentas de administração do site diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md index 3422dbd951..d2ac938cb1 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### Excluir repositórios de uma organização no {% data variables.product.prodname_dotcom_the_website %} -After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). Você precisará do token de acesso para autenticação: +Após desbloquear os repositórios da organização de {% data variables.product.prodname_dotcom_the_website %}, você deverá excluir todos os repositórios previamente migrados usando [o ponto de extremidade de exclusão do repositório](/rest/reference/repos/#delete-a-repository). Você precisará do token de acesso para autenticação: ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md index c0848bd3cb..4ae1903ebb 100644 --- a/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/pt-BR/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ Assim como na suspensão, o cancelamento da suspensão de um usuário ocorre na ``` ### Leia mais -- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file +- "[Suspender um usuário](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/pt-BR/content/developers/apps/about-apps.md b/translations/pt-BR/content/developers/apps/about-apps.md index 97855febdd..a14d520e9b 100644 --- a/translations/pt-BR/content/developers/apps/about-apps.md +++ b/translations/pt-BR/content/developers/apps/about-apps.md @@ -67,13 +67,13 @@ Tenha isso em mente ao criar {% data variables.product.prodname_oauth_app %}s: * Não crie um {% data variables.product.prodname_oauth_app %} para atuar como um aplicativo para sua equipe ou empresa. {% data variables.product.prodname_oauth_app %}s efetuam a autenticação como um único usuário. Portanto, se uma pessoa criar um {% data variables.product.prodname_oauth_app %} para a empresa usar e depois sair da empresa, ninguém mais terá acesso a ele.{% if currentVersion == "free-pro-team@latest" %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -For more on {% data variables.product.prodname_oauth_app %}s, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." +Para obter mais informações sobre {% data variables.product.prodname_oauth_app %}, consulte "[Criar um {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" e "[Registrando seu aplicativo](/rest/guides/basics-of-authentication#registering-your-app)". ### Tokens de acesso pessoal Um [token de acesso pessoal](/articles/creating-a-personal-access-token-for-the-command-line/) é uma string de caracteres que funciona da mesma forma que um [token do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/), cujas permissões você pode especificar por meio de [escopos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Um token de acesso pessoal também é semelhante a uma senha, mas você pode ter muitos delas e você pode revogar o acesso a cada uma a qualquer momento. -Como exemplo, você pode habilitar um token de acesso pessoal para escrever em seus repositórios. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the personal access token to authenticate. Você pode armazenar o token de acesso pessoal como uma variável de ambiente para evitar ter de digitá-lo toda vez que você usá-lo. +Como exemplo, você pode habilitar um token de acesso pessoal para escrever em seus repositórios. Em seguida, se você executar um comando cURL ou escrever um script que [cria um problema](/rest/reference/issues#create-an-issue) no seu repositório, você informaria o token de acesso pessoal para efetuar a autenticação. Você pode armazenar o token de acesso pessoal como uma variável de ambiente para evitar ter de digitá-lo toda vez que você usá-lo. Tenha em mente essas ideias ao usar os tokens de acesso pessoais: 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 655d7d41b8..0cfcdc820e 100644 --- a/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/authorizing-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Authorizing OAuth Apps +title: Autorizar aplicativos OAuth intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps/ @@ -14,84 +14,83 @@ versions: github-ae: '*' --- -{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser{% endif %}. +A implementação do OAuth de {% data variables.product.product_name %}oferece suporte ao [tipo de concessão do código padrão](https://tools.ietf.org/html/rfc6749#section-4.1) {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} e o OAuth 2.0 [Concessão de Autorização do Dispositivo](https://tools.ietf.org/html/rfc8628) para aplicativos que não têm acesso a um navegador web{% endif %}. -If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow). +Se você desejar ignorar a autorização do seu aplicativo da forma-padrão, como no teste do seu aplicativo, você poderá usar o fluxo do aplicativo [que não é web](#non-web-application-flow). {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -To authorize your OAuth app, consider which authorization flow best fits your app. +Para autorizar o seu aplicativo OAuth, considere qual fluxo de autorização melhor se adequa ao seu aplicativo. -- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.) -- [device flow](#device-flow): Used for headless apps, such as CLI tools. +- [Fluxo de aplicativos web](#web-application-flow): Usado para autorizar usuários para aplicativos OAuth padrão executados no navegador. (O [tipo implícito de concessão](https://tools.ietf.org/html/rfc6749#section-4.2) não é compatível) +- [fluxo de dispositivo](#device-flow): Usado para aplicativos sem cabeçalho, como ferramentas de CLI. {% else %} -For standard apps that run in the browser, use the [web application flow](#web-application-flow) to obtain an authorization code and exchange it for a token. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.) +Para os aplicativos-padrão que são executados no navegador, use o [fluxo do aplicativo web](#web-application-flow) para obter um código de autorização e trocá-lo por um token. (O [tipo implícito de concessão](https://tools.ietf.org/html/rfc6749#section-4.2) não é compatível) {% endif %} -### Web application flow +### Fluxo do aplicativo web {% note %} -**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. +**Observação:** Se você está criando um aplicativo GitHub, você ainda pode usar o fluxo do aplicativo web OAuth, mas a configuração tem algumas diferenças importantes. Consulte "[Identificando e autorizando usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obter mais informações. {% endnote %} -The web application flow to authorize users for your app is: +O fluxo do aplicativo web para autorizar os usuários para seu aplicativo é: -1. Users are redirected to request their GitHub identity -2. Users are redirected back to your site by GitHub -3. Your app accesses the API with the user's access token +1. Os usuários são redirecionados para solicitar sua identidade do GitHub +2. Os usuários são redirecionados de volta para o seu site pelo GitHub +3. Seu aplicativo acessa a API com o token de acesso do usuário -#### 1. Request a user's GitHub identity +#### 1. Solicitar identidade do GitHub de um usuário GET {% data variables.product.oauth_host_code %}/login/oauth/authorize -When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. +Quando seu aplicativo GitHub especifica um parâmetro do `login`, ele solicita aos usuários com uma conta específica que podem usar para iniciar sessão e autorizar seu aplicativo. -##### Parameters +##### Parâmetros -Name | Type | Description ------|------|-------------- -`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% if currentVersion == "free-pro-team@latest" %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}. -`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls). -`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. -`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope. -`state` | `string` | {% data reusables.apps.state_description %} -`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups. +| Nome | Tipo | Descrição | +| -------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `string` | **Obrigatório**. O ID do cliente que você recebeu do GitHub quando {% if currentVersion == "free-pro-team@latest" %}[registrado](https://github.com/settings/applications/new){% else %}registrado{% endif %}. | +| `redirect_uri` | `string` | A URL no seu aplicativo para o qual os usuários serão enviados após a autorização. Veja os detalhes abaixo sobre [redirecionamento das urls](#redirect-urls). | +| `login` | `string` | Sugere uma conta específica para iniciar a sessão e autorizar o aplicativo. | +| `escopo` | `string` | Uma lista de [escopos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) delimitada por espaço. Caso não seja fornecido, o `escopo`-padrão será uma lista vazia para usuários que não autorizaram nenhum escopo para o aplicativo. Para usuários que têm escopos autorizados para o aplicativo, a página de autorização OAuth com a lista de escopos não será exibida para o usuário. Em vez disso, esta etapa do fluxo será concluída automaticamente com o conjunto de escopos que o usuário autorizou para o aplicativo. Por exemplo, se um usuário já executou o fluxo web duas vezes e autorizou um token com escopo do `usuário` e outro token com o escopo do `repositório`, um terceiro fluxo web que não fornece um escopo `` receberá um token com os escopos do `usuário` e do `repositório`. | +| `estado` | `string` | {% data reusables.apps.state_description %} +| `allow_signup` | `string` | Independentemente de os usuários serem autenticados, eles receberão uma opção para inscrever-se no GitHub durante o fluxo do OAuth. O padrão é `verdadeiro`. Use `falso` quando uma política proibir inscrições. | -#### 2. Users are redirected back to your site by GitHub +#### 2. Os usuários são redirecionados de volta para o seu site pelo GitHub -If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process. +Se o usuário aceitar a sua solicitação, o {% data variables.product.product_name %} redireciona de volta para seu site com `código` temporário em um parâmetro de código, bem como o estado que você forneceu na etapa anterior em um `parâmetro de estado`. O código temporário irá expirar após 10 minutos. Se os estados não corresponderem, significa que uma terceira criou a solicitação, e você deverá abortar o processo. -Exchange this `code` for an access token: +Troque este `código` por um token de acesso: POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -##### Parameters +##### Parâmetros -Name | Type | Description ------|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. -`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. -`code` | `string` | **Required.** The code you received as a response to Step 1. -`redirect_uri` | `string` | The URL in your application where users are sent after authorization. -`state` | `string` | The unguessable random string you provided in Step 1. +| Nome | Tipo | Descrição | +| --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_github_app %}. | +| `client_secret` | `string` | **Obrigatório.** O segredo do cliente que recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_github_app %}. | +| `código` | `string` | **Obrigatório.** O código que você recebeu como resposta ao Passo 1. | +| `redirect_uri` | `string` | A URL do seu aplicativo para onde os usuários são enviados após a autorização. | +| `estado` | `string` | A string aleatória inexplicável que você forneceu na etapa 1. | -##### Response +##### Resposta -By default, the response takes the following form: +Por padrão, a resposta assume o seguinte formato: access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer -You can also receive the content in different formats depending on the Accept -header: +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"} - + Accept: application/xml bearer @@ -99,52 +98,52 @@ header: e72e16c7e42f292c6912e7710c838347ae178b4a -#### 3. Use the access token to access the API +#### 3. Use o token de acesso para acessar a API -The access token allows you to make requests to the API on a behalf of a user. +O token de acesso permite que você faça solicitações para a API em nome de um usuário. - Authorization: token OAUTH-TOKEN + Autorização: token OUTH-TOKEN GET {% data variables.product.api_url_code %}/user -For example, in curl you can set the Authorization header like this: +Por exemplo, no cURL você pode definir o cabeçalho de autorização da seguinte forma: ```shell curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user ``` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -### Device flow +### Fluxo de dispositivo {% if currentVersion ver_lt "enterprise-server@3.1" %} {% note %} -**Note:** The device flow is in public beta and subject to change. +**Nota:** O fluxo do dispositivo está na versão beta pública e sujeito a alterações. {% endnote %} {% endif %} -The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. +O fluxo de dispositivos permite que você autorize usuários para um aplicativo sem cabeçalho, como uma ferramenta de CLI ou um gerenciador de credenciais do Git. -#### Overview of the device flow +#### Visão geral do fluxo do dispositivo -1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code. -2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}. -3. The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token. +1. O seu aplicativo solicita o dispositivo e o código de verificação do usuário e obtém a URL de autorização em que o usuário digitará o código de verificação do usuário. +2. O aplicativo solicita que o usuário insira um código de verificação em {% data variables.product.device_authorization_url %}. +3. O aplicativo pesquisa status de autenticação do usuário. Uma vez que o usuário tenha autorizado o dispositivo, o aplicativo poderá fazer chamadas de API com um novo token de acesso. -#### Step 1: App requests the device and user verification codes from GitHub +#### Passo 1: O aplicativo solicita o dispositivo e os códigos de verificação de usuário do GitHub POST {% data variables.product.oauth_host_code %}/login/device/code -Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication. +O seu aplicativo deve solicitar um código de verificação e uma URL de verificação que o aplicativo usará para solicitar que o usuário seja autenticado na próxima etapa. Essa solicitação também retorna um código de verificação de dispositivo que o aplicativo deve usar para receber um token de acesso e verificar o status da autenticação do usuário. -##### Input Parameters +##### Parâmetros de entrada -Name | Type | Description ------|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app. -`scope` | `string` | The scope that your app is requesting access to. +| Nome | Tipo | Descrição | +| ----------- | -------- | --------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu aplicativo. | +| `escopo` | `string` | O escopo ao qual o seu aplicativo está solicitando acesso. | -##### Response +##### Resposta {% if currentVersion == "free-pro-team@latest" %} ```JSON @@ -168,41 +167,41 @@ Name | Type | Description ``` {% endif %} -##### Response parameters +##### Parâmetros de resposta -Name | Type | Description ------|------|-------------- -`device_code` | `string` | The device verification code is 40 characters and used to verify the device. -`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle. -`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}. -`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes. -`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error. +| Nome | Tipo | Descrição | +| ------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `device_code` | `string` | O código de verificação do dispositivo tem 40 caracteres e é usado para verificar o dispositivo. | +| `user_code` | `string` | O código de verificação do usuário é exibido no dispositivo para que o usuário possa inserir o código no navegador. Este código tem 8 caracteres com um hífen no meio. | +| `verification_uri` | `string` | A URL de verificação em que os usuários devem digitar o código do usuário ``: {% data variables.product.device_authorization_url %}. | +| `expires_in` | `inteiro` | O número de segundos antes dos códigos `device_code` e `user_code` expirarem. O padrão é 900 segundos ou 15 minutos. | +| `interval` | `inteiro` | O número mínimo de segundos que decorridos antes de você poder fazer uma nova solicitação de token de acesso (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) para concluir a autorização do dispositivo. Por exemplo, se o intervalo for 5, você não poderá fazer uma nova solicitação a partir de 5 segundos. Se você fizer mais de uma solicitação em 5 segundos, você atingirá o limite de taxa e receberá uma mensagem de erro `slow_down`. | -#### Step 2: Prompt the user to enter the user code in a browser +#### Passo 2: Solicite ao usuário que insira o código do usuário em um navegador -Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}. +O seu dispositivo mostrará o código de verificação do usuário e solicitará que o usuário insira o código em {% data variables.product.device_authorization_url %}. - ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png) + ![Campo para digitar o código de verificação do usuário exibido no seu dispositivo](/assets/images/github-apps/device_authorization_page_for_user_code.png) -#### Step 3: App polls GitHub to check if the user authorized the device +#### Passo 3: O aplicativo solicita que o GitHub verifique se o usuário autorizou o dispositivo POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)." +O seu aplicativo fará solicitações de autorização do dispositivo que pesquisem `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, até que o dispositivo e códigos de usuário expirem ou o usuário autorizem com sucesso o aplicativo com um código de usuário válido. O aplicativo deve usar o `intervalo` mínimo de sondagem recuperado na etapa 1 para evitar erros de limite de taxa. Para obter mais informações, consulte "[Limites de taxa para o fluxo do dispositivo](#rate-limits-for-the-device-flow)". -The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`. +O usuário deve inserir um código válido em de 15 minutos (ou 900 segundos). Após 15 minutos, você deverá solicitar um novo código de autorização do dispositivo com `POST {% data variables.product.oauth_host_code %}/login/dispositivo/código`. -Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user. +Uma vez que o usuário tenha autorizado, o aplicativo receberá um token de acesso que poderá ser usado para fazer solicitações para a API em nome de um usuário. -##### Input parameters +##### Parâmetros de entrada -Name | Type | Description ------|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. -`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request. -`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`. +| Nome | Tipo | Descrição | +| ------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `client_id` | `string` | **Obrigatório.** O ID do cliente que você recebeu do {% data variables.product.product_name %} para o seu {% data variables.product.prodname_oauth_app %}. | +| `device_code` | `string` | **Obrigatório.** O código de verificação do dispositivo que você recebeu da solicitação `POST {% data variables.product.oauth_host_code %}/login/dispositivo/código`. | +| `grant_type` | `string` | **Obrigatório.** O tipo de concessão deve ser `urn:ietf:params:oauth:grant-type:device_code`. | -##### Response +##### Resposta ```json { @@ -212,52 +211,46 @@ Name | Type | Description } ``` -#### Rate limits for the device flow +#### Limites de taxa para o fluxo do dispositivo -When a user submits the verification code on the browser, there is a there is a rate limit of 50 submissions in an hour per application. +Quando um usuário envia o código de verificação no navegador, existe um limite de taxa máximo de 50 submissões em uma hora por aplicativo. -If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). +Se você fizer mais de uma solicitação de token de acesso (`POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token`) no período mínimo necessário entre solicitações (ou `intervalo`), você atingirá o limite de taxa e receberá uma resposta de erro `slow_down`. A resposta de erro `slow_down`adiciona 5 segundos ao último `intervalo`. Para obter mais informações, consulte [Erros para o fluxo do dispositivo](#errors-for-the-device-flow). -#### Error codes for the device flow +#### Códigos de erro para o fluxo do dispositivo -| Error code | Description | -|----|----| -| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. | -| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use. -| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code. -| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. -| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow. -| `incorrect_device_code` | The device_code provided is not valid. -| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again. +| Código do erro | Descrição | +| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `authorization_pending` | Este erro ocorre quando a solicitação de autorização está pendente e o usuário ainda não inseriu o código do usuário. Espera-se que o aplicativo continue fazendo a sondagem da solicitação `POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token` sem exceder o [`intervalo`](#response-parameters), que exige um número mínimo de segundos entre cada solicitação. | +| `slow_down` | Ao receber o erro `slow_down`, são adicionados 5 segundos extras ao intervalo mínimo `` ou período de tempo necessário entre as suas solicitações usando `POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token`. Por exemplo, se o intervalo inicial for necessário pelo menos 5 segundos entre as solicitações e você receber uma resposta de erro de `slow_down`, você deverá aguardar pelo menos 10 segundos antes de fazer uma nova solicitação para um token de acesso OAuth. A resposta de erro inclui o novo `intervalo` que você deve usar. | +| `expired_token` | Se o código do dispositivo expirou, você verá o erro `token_expired`. Você deve fazer uma nova solicitação para um código de dispositivo. | +| `unsupported_grant_type` | O tipo de concessão deve ser `urn:ietf:params:oauth:grant-type:device_code` e incluído como um parâmetro de entrada quando você faz a sondagem da solicitação do token do OAuth `POST {% data variables.product.oauth_host_code %}/login/oauth/oaccess_token`. | +| `incorrect_client_credentials` | Para o fluxo do dispositivo, você deve passar o ID de cliente do aplicativo, que pode ser encontrado na página de configurações do aplicativo. O `client_secret` não é necessário para o fluxo do dispositivo. | +| `incorrect_device_code` | O device_code fornecido não é válido. | +| `access_denied` | Quando um usuário clica em cancelar durante o processo de autorização, você receberá uma mensagem de erro de `access_denied` e o usuário não poderá usar o código de verificação novamente. | -For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)." +Para obter mais informações, consulte "[Concessão de Autorização do Dispositivo OAuth 2.0](https://tools.ietf.org/html/rfc8628#section-3.5)". {% endif %} -### Non-Web application flow +### Fluxo do aplicativo que não são da web -Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. +A autenticação que não é da web está disponível para situações limitadas como testes. Se necessário, você pode usar a [autenticação básica](/rest/overview/other-authentication-methods#basic-authentication) para criar um token de acesso usando a sua [página pessoal de configurações de tokens de acesso](/articles/creating-an-access-token-for-command-line-use). Essa técnica permite ao usuário revogar o acesso a qualquer momento. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} {% note %} -**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with -two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if -you or your users have two-factor authentication enabled. +**Observação:** Quando usar o fluxo do aplicativo que não é web para criar um token do OAuth2, certifique-se de entender como [trabalhar com a autenticação de dois fatores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) se você ou seus usuários tiverem a autenticação de dois fatores habilitada. {% endnote %} {% endif %} -### Redirect URLs +### URLs de redirecionamento -The `redirect_uri` parameter is optional. If left out, GitHub will -redirect users to the callback URL configured in the OAuth Application -settings. If provided, the redirect URL's host and port must exactly -match the callback URL. The redirect URL's path must reference a -subdirectory of the callback URL. - - CALLBACK: http://example.com/path +O parâmetro `redirect_uri` é opcional. Se ignorado, o GitHub redirecionará os usuários para a URL de retorno de chamada definida nas configurações do aplicativo OAuth. Se fornecido, o host e porta do URL de redirecionamento deve exatamente corresponder à URL de retorno de chamada. O caminho da URL de redirecionamento deve fazer referência uma subpasta da URL de retorno de chamada. + RETORNO DE CHAMADA: http://example.com/path + GOOD: http://example.com/path GOOD: http://example.com/path/subdir/other BAD: http://example.com/bar @@ -266,29 +259,29 @@ subdirectory of the callback URL. BAD: http://oauth.example.com:8080/path BAD: http://example.org -#### Localhost redirect urls +#### URLs de redirecionamento do Localhost -The optional `redirect_uri` parameter can also be used for localhost URLs. If the application specifies a localhost URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback url for the app. +O parâmetro opcional `redirect_uri` também pode ser usado para URLs do localhhost. Se o aplicativo especificar uma URL do localhost e uma porta, após a autorização, os usuários do aplicativo serão redirecionados para a URL e porta fornecidas. O `redirect_uri` não precisa corresponder à porta especificada na URL de retorno de chamada do aplicativo. -For the `http://localhost/path` callback URL, you can use this `redirect_uri`: +Para a URL de retorno de chamada `http://localhost/path`, você poderá usar este `redirect_uri`: http://localhost:1234/path -### Creating multiple tokens for OAuth Apps +### Criar vários tokens para aplicativos OAuth -You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases. +Você pode criar vários tokens para uma combinação de usuário/aplicativo/escopo para criar tokens para casos de uso específicos. -This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories. +Isso é útil se o seu aplicativo OAuth for compatível com um fluxo de trabalho que usa o GitHub para iniciar sessão e exigir apenas informações básicas do usuário. Outro fluxo de trabalho pode exigir acesso aos repositórios privados de um usuário. Ao usar vários tokens, o seu aplicativo OAuth pode realizar o fluxo web para cada caso, solicitando apenas os escopos necessários. Se um usuário usar apenas seu aplicativo para iniciar a sessão, ele nunca será obrigado a conceder acesso do aplicativo OAuth aos seus repositórios privados. -There is a limit to the number of tokens that are issued per user/application/scope combination. If your application requests enough tokens to go over one of the limits, older tokens _with the same scope being requested_ will stop working. +Há um limite para o número de tokens emitidos por combinação de usuário/aplicativo/escopo. Se seu aplicativo solicitar tokens suficientes para ultrapassar um dos limites, os tokens antigos _com o mesmo escopo sendo solicitado_ irão parar de funcionar. {% data reusables.apps.deletes_ssh_keys %} -### Directing users to review their access +### Direcionar os usuários para revisar seus acessos -You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations. +Você pode vincular informações sobre a autorização de um aplicativo OAuth para que os usuários possam revisar e revogar as autorizações do seu aplicativo. -To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application. +Para criar esse vínculo, você precisará do `client_id` dos aplicativos OAuth, que você recebeu do GitHub quando fez o cadastro no aplicativo. ``` {% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id @@ -296,14 +289,14 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr {% tip %} -**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." +**Dica:** Para saber mais sobre os recursos que seu aplicativo OAuth pode acessar para um usuário, consulte "[Descobrindo recursos para um usuário](/rest/guides/discovering-resources-for-a-user). " {% endtip %} -### Troubleshooting +### Solução de Problemas -* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" -* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" +* "[Solucionando erros de solicitação de autorização](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" +* "[Solucionando erros na requisição de token de acesso do aplicativo OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -* "[Device flow errors](#errors-for-the-device-flow)" +* "[Erros do fluxo do dispositivo](#errors-for-the-device-flow)" {% endif %} 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 aca9d29137..8bce30d942 100644 --- a/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md +++ b/translations/pt-BR/content/developers/apps/creating-a-github-app-from-a-manifest.md @@ -52,16 +52,16 @@ A pessoa que está criando o aplicativo será redirecionada para uma página do ##### Parâmetros do manifesto do aplicativo GitHub - | Nome | Tipo | Descrição | - | --------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name` | `string` | O nome do aplicativo GitHub. | - | `url` | `string` | **Obrigatório.** A página inicial do seu aplicativo GitHub. | - | `hook_attributes` | `objeto` | A configuração do webhook do aplicativo GitHub. | - | `redirect_url` | `string` | A URL completa para onde redirecionar depois que a pessoa instalar o aplicativo GitHub. | - | `descrição` | `string` | Uma descrição do aplicativo GitHub. | - | `público` | `boolean` | Defina como `verdadeiro` quando o seu aplicativo GitHub estiver disponível para o público ou `falso` quando for acessível somente pelo proprietário do aplicativo. | - | `default_events` | `array` | Lista de [eventos](/webhooks/event-payloads) assinada pelo aplicativo GitHub. | - | `default_permissions` | `objeto` | The set of [permissions](/rest/reference/permissions-required-for-github-apps) needed by the GitHub App. O formato do objeto usa o nome de permissão para a chave (por exemplo, `problemas`) e o tipo de acesso para o valor (por exemplo, `gravar`). | + | 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`). | O objeto `hook_attributes` tem a chave a seguir: @@ -153,13 +153,13 @@ Se você forneceu um parâmetro `estado`, você também verá esse parâmetro em #### 3. Você troca o código temporário para recuperar a configuração do aplicativo -To complete the handshake, send the temporary `code` in a `POST` request to the [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest) endpoint. A resposta incluirá o `id` (ID do aplicativo GitHub), `pem` (chave privada) e `webhook_secret`. O GitHub cria um segredo webhook para o aplicativo automaticamente. Você pode armazenar esses valores em variáveis de ambiente no servidor do aplicativo. Por exemplo, se o aplicativo usar [dotenv](https://github.com/bkeepers/dotenv) para armazenar variáveis de ambiente, você armazenará as variáveis no arquivo `.env` do seu aplicativo. +Para concluir o handshake, enviar o código temporário `` em uma solicitação `POST` para [Criar um aplicativo GitHub a partir do ponto de extremidade](/rest/reference/apps#create-a-github-app-from-a-manifest) de um manifesto. A resposta incluirá o `id` (ID do aplicativo GitHub), `pem` (chave privada) e `webhook_secret`. O GitHub cria um segredo webhook para o aplicativo automaticamente. Você pode armazenar esses valores em variáveis de ambiente no servidor do aplicativo. Por exemplo, se o aplicativo usar [dotenv](https://github.com/bkeepers/dotenv) para armazenar variáveis de ambiente, você armazenará as variáveis no arquivo `.env` do seu aplicativo. Você deve concluir esta etapa do fluxo do manifesto do aplicativo GitHub em uma hora. {% note %} -**Observação:** Esse ponto final tem limite de taxa. See [Rate limits](/rest/reference/rate-limit) to learn how to get your current rate limit status. +**Observação:** Esse ponto final tem limite de taxa. Consulte [Limites de taxa](/rest/reference/rate-limit) para saber como obter seu status atual do limite de taxa. {% endnote %} @@ -170,7 +170,7 @@ Você deve concluir esta etapa do fluxo do manifesto do aplicativo GitHub em uma POST /app-manifests/:code/conversions -For more information about the endpoint's response, see [Create a GitHub App from a manifest](/rest/reference/apps#create-a-github-app-from-a-manifest). +Para obter mais informações sobre a resposta do ponto de extremidade, consulte [Criar um aplicativo GitHub a partir de um manifesto](/rest/reference/apps#create-a-github-app-from-a-manifest). Quando a etapa final do fluxo de manifesto for concluída, a pessoa que estiver criando o aplicativo a partir do fluxo será proprietária de um aplicativo GitHub registrado e poderá instalar em qualquer um dos seus repositórios pessoais. A pessoa pode optar por estender o aplicativo usando as APIs do GitHub, transferir a propriedade para outra pessoa ou excluí-lo a qualquer momento. @@ -191,4 +191,4 @@ Ao usar [dotenv](https://github.com/bkeepers/dotenv), o Probot cria um arquivo ` #### Hospedar seu aplicativo com Glitch -Você pode ver um [exemplo do aplicativo Probot](https://glitch.com/~auspicious-aardwolf) que usa o [Glitch](https://glitch.com/) para hospedar e compartilhar o aplicativo. The example uses the [Checks API](/rest/reference/checks) and selects the necessary Checks API events and permissions in the `app.yml` file. Glitch é uma ferramenta que permite que você "mescle seus próprios aplicativos". Mesclar um aplicativo cria uma cópia do aplicativo que a Glitch hospeda e implementa. Consulte "[Sobre a Glitch](https://glitch.com/about/)" para aprender sobre como mesclar aplicativos Glitch. +Você pode ver um [exemplo do aplicativo Probot](https://glitch.com/~auspicious-aardwolf) que usa o [Glitch](https://glitch.com/) para hospedar e compartilhar o aplicativo. O exemplo usa a [API de verificação](/rest/reference/checks) e seleciona as verificações e permissões necessárias dos eventos da API e no arquivo `app.yml`. Glitch é uma ferramenta que permite que você "mescle seus próprios aplicativos". Mesclar um aplicativo cria uma cópia do aplicativo que a Glitch hospeda e implementa. Consulte "[Sobre a Glitch](https://glitch.com/about/)" para aprender sobre como mesclar aplicativos Glitch. 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 1d7cdd6ec4..9a5a4fc628 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 @@ -73,7 +73,9 @@ Você pode selecionar permissões em uma string de consultas usando o nome da pe | `plano` | Concede acesso para obter informações sobre o plano de um usuário do GitHub que usa o ponto final "[Obter um usuário](/rest/reference/users#get-a-user)". Pode ser: `nenhum` ou `leitura`. | | [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Concede acesso a vários pontos finais do pull request. Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Concede acesso à [API de webhooks do repositório](/rest/reference/repos#hooks). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leutra`, `gravação` ou `administrador`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Concede acesso à [API de Projetos](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Concede acesso à [API de varredura de segredo](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Concede acesso à [API de varredura de código](/rest/reference/code-scanning/). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Concede acesso à [API de conteúdo](/rest/reference/repos#contents). Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`estrela`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Concede acesso à [API estrelada](/rest/reference/activity#starring). Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`Status`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Concede acesso à [API de status](/rest/reference/repos#statuses). Pode ser: `nenhum`, `leitura` ou `gravação`. | 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 59086b56d2..b0c7342f1e 100644 --- a/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md +++ b/translations/pt-BR/content/developers/apps/creating-ci-tests-with-the-checks-api.md @@ -12,7 +12,7 @@ versions: ### Introdução -This guide will introduce you to [Github Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests. +Este guia irá apresentá-lo aos [aplicativos Github](/apps/) e à [API de verificação](/rest/reference/checks), que você usará para criar um servidor de integração contínua (CI) que executa testes. A CI é uma prática de software que exige o commit do código em um repositório compartilhado. Fazer commits de códigos com frequência detecta erros com mais antecedência e reduz a quantidade de código necessária para depuração quando os desenvolvedores chegam à origem de um erro. As atualizações frequentes de código também facilitam o merge de alterações dos integrantes de uma equipe de desenvolvimento de software. Assim, os desenvolvedores podem se dedicar mais à gravação de códigos e se preocupar menos com erros de depuração ou conflitos de merge. 🙌 @@ -22,15 +22,15 @@ Um código de host do servidor de CI que executa testes de CI, como, por exemplo #### Visão geral da API de verificação -The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. A API de verificação relata informações detalhadas sobre cada verificação no GitHub na aba **Verificações** do pull request. Com a API de Verificações, você pode criar anotações com detalhes adicionais para linhas específicas de código. As anotações são visíveis na aba **Verificações**. Ao criar uma anotação para um arquivo que faz parte do pull request, as anotações também são exibidas na aba **Arquivos alterados**. +A [API de verificação](/rest/reference/checks) permite que você configure testes de CI executados automaticamente em cada commit de código em um repositório. A API de verificação relata informações detalhadas sobre cada verificação no GitHub na aba **Verificações** do pull request. Com a API de Verificações, você pode criar anotações com detalhes adicionais para linhas específicas de código. As anotações são visíveis na aba **Verificações**. Ao criar uma anotação para um arquivo que faz parte do pull request, as anotações também são exibidas na aba **Arquivos alterados**. -Um _conjunto de verificações_ é um grupo de _execuções de verificação _ (testes de CI individuais). Tanto o conjunto quanto a execução contêm _status_ visíveis em um pull request no GitHub. Você pode usar os status para determinar quando um commit de código introduz erros. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. Consulte "[Habilitando as verificações de status necessárias](/articles/enabling-required-status-checks/)" para mais detalhes. +Um _conjunto de verificações_ é um grupo de _execuções de verificação _ (testes de CI individuais). Tanto o conjunto quanto a execução contêm _status_ visíveis em um pull request no GitHub. Você pode usar os status para determinar quando um commit de código introduz erros. Usar esses status com [branches protegidos](/rest/reference/repos#branches) pode impedir que as pessoas mesclem de pull requests prematuramente. Consulte "[Habilitando as verificações de status necessárias](/articles/enabling-required-status-checks/)" para mais detalhes. -A API de verificações envia o evento do webhook [`check_suite` webhook](/webhooks/event-payloads/#check_suite) para todos os aplicativos GitHub instalados em um repositório sempre que um novo código for enviado para o repositório. Para receber todas as ações do evento de verificações da API, o aplicativo deverá ter a permissão de `checks:write`. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Veja como funciona o fluxo-padrão: +A API de verificações envia o evento do webhook [`check_suite` webhook](/webhooks/event-payloads/#check_suite) para todos os aplicativos GitHub instalados em um repositório sempre que um novo código for enviado para o repositório. Para receber todas as ações do evento de verificações da API, o aplicativo deverá ter a permissão de `checks:write`. O GitHub cria automaticamente eventos `check_suite` para novos códigos de commits em um repositório usando o fluxo-padrão, embora [Atualizar preferências do repositório para o conjunto de verificações](/rest/reference/checks#update-repository-preferences-for-check-suites) esteja disponível se desejar. Veja como funciona o fluxo-padrão: 1. Sempre que alguém fizer push do código para o repositório, o GitHub envia o evento `check_suite` com uma ação de `necessária` a todos os aplicativos GitHub instalados no repositório com a permissão `checks:write`. Este evento permite que os aplicativos saibam que o código foi enviado e que o GitHub criou um novo conjunto de verificações automaticamente. -1. When your app receives this event, it can [add check runs](/rest/reference/checks#create-a-check-run) to that suite. -1. Your check runs can include [annotations](/rest/reference/checks#annotations-object) that are displayed on specific lines of code. +1. Quando seu aplicativo recebe este evento, ele pode [adicionar uma verificação executa](/rest/reference/checks#create-a-check-run) para esse conjunto. +1. As suas execuções de verificação podem incluir [anotações](/rest/reference/checks#annotations-object), que são exibidas em linhas específicas de código. **Neste guia, você aprenderá:** @@ -49,7 +49,7 @@ Para ter uma ideia do que seu servidor de CI da API de verificações fará quan ### Pré-requisitos -Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). A API de Verificações também está disponível para uso no [GraphQL](/graphql), mas este início rápido foca no REST. Consulte o GraphQL [Conjunto de verificações](/graphql/reference/objects#checksuite) e os objetos de [execução de verificação](/graphql/reference/objects#checkrun) objetos para obter mais informações. +Antes de começar, é possível que você deseje familiarizar-se com os [aplicativos Github](/apps/), [Webhooks](/webhooks) e a [API de verificação](/rest/reference/checks), caso você ainda não esteja familiarizado. Você encontrará mais APIs na [documentação da API REST](/rest). A API de Verificações também está disponível para uso no [GraphQL](/graphql), mas este início rápido foca no REST. Consulte o GraphQL [Conjunto de verificações](/graphql/reference/objects#checksuite) e os objetos de [execução de verificação](/graphql/reference/objects#checkrun) objetos para obter mais informações. Você usará a [linguagem de programação Ruby](https://www.ruby-lang.org/en/), o serviço de entrega de da carga do webhook [Smee](https://smee.io/), a [biblioteca do Ruby Octokit.rb](http://octokit.github.io/octokit.rb/) para a API REST do GitHub e a [estrutura web Sinatra](http://sinatrarb.com/) para criar seu aplicativo do servidor de verificações de CI da API. @@ -175,7 +175,7 @@ end ``` {% endif %} -This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the generic [HTTP `POST` method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). Este método tem dois parâmetros: a URL do ponto final e os parâmetros de entrada do método. +Este código chama o ponto de extremidade "[Criar uma execução de verificação](/rest/reference/checks#create-a-check-run)" que usa o método genérico [HTTP `POST`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). Este método tem dois parâmetros: a URL do ponto final e os parâmetros de entrada do método. Para criar uma execução de verificação, são necessários apenas dois parâmetros de entrada: `nome` e `head_sha`. Vamos usar o [Rubocop](https://rubocop.readthedocs.io/en/latest/) para implementar o teste CI mais adiante início rápido. Por esse motivo, o nome "Octo Rubocop" é usado aqui, mas você pode escolher qualquer nome que desejar para a execução da verificação. @@ -305,11 +305,11 @@ end ``` {% endif %} -The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the generic [`patch` HTTP method](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) to update the check run that you already created. +O código acima chama o ponto de extremidade da API "[Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run)" usando o método genérico [`patch` HTTP](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) para atualizar a execução da verificação que você já criou. Veja o que este código está fazendo. Primeiro, ele atualiza o status de verificação de execução para `in_progress` e define o tempo do `started_at` para o tempo atual. Na [Parte 2](#part-2-creating-the-octo-rubocop-ci-test) deste início rápido, você irá adicionar um código que inicia um teste de CI real em `***** EXECUTAR UM TEST DE CI *****`. Por enquanto, você sairá da seção como um espaço reservado, para que o código que o segue apenas simule que o processo de CI seja bem-sucedido e todos os testes sejam aprovados. Finalmente, o código atualiza o status da execução de verificação novamente para `concluído`. -You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. A conclusão `` resume o resultado de uma verificação de resultado e pode ser `sucesso`, `falha`, `neutro`, `cancelado`, `timed_out` ou `action_required`. Você irá definir a conclusão como `sucesso`, o tempo `completed_at` como a hora atual e o status como `concluído`. +Na documentação "[Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run)", você observará que, ao fornecer um status de `concluído`, são necessários os parâmetros `conclusão` e `completed_at`. A conclusão `` resume o resultado de uma verificação de resultado e pode ser `sucesso`, `falha`, `neutro`, `cancelado`, `timed_out` ou `action_required`. Você irá definir a conclusão como `sucesso`, o tempo `completed_at` como a hora atual e o status como `concluído`. Você também pode fornecer mais informações sobre o que a sua verificação está fazendo, mas você poderá fazer isso na próxima seção. Vamos testar este código de novo executando `template_server.rb` novamente: @@ -435,7 +435,7 @@ O código acima obtém o nome completo do repositório e o SHA principal do comm ### Etapa 2.3. Executar o RuboCop -Ótimo! Você está clonando o repositório e criando execuções de verificação usando seu servidor de CI. Now you'll get into the nitty gritty details of the [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run). +Ótimo! Você está clonando o repositório e criando execuções de verificação usando seu servidor de CI. Agora você irá entrar nas informações principais do [RuboCop linter](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) e das [anotações da API de verificação](/rest/reference/checks#create-a-check-run). O código a seguir executa RuboCop e salva os erros do código de estilo no formato JSON. Adicione este código abaixo da chamada para `clone_repository` que você adicionou na [etapa anterior](#step-22-cloning-the-repository) e acima do código que atualiza a execução de verificação para concluir. @@ -523,11 +523,11 @@ Você deve ver os erros de linting na saída de depuração, embora não sejam i A variável `@output` contém os resultados do JSON analisados do relatório do RuboCop. Conforme mostrado acima, os resultados contêm uma seção `resumo` que seu código pode usar para determinar rapidamente se existem erros. O código a seguir definirá a conclusão de execução de verificação para o `sucesso` quando não houver erros relatados. O RuboCop relata erros para cada arquivo no array dos `arquivos`. Portanto, se houver erros, você deverá extrair alguns dados do objeto arquivo. -A API de verificação permite que você crie anotações para linhas específicas do código. Ao criar ou atualizar uma execução de verificação, você pode adicionar anotações. In this quickstart you are [updating the check run](/rest/reference/checks#update-a-check-run) with annotations. +A API de verificação permite que você crie anotações para linhas específicas do código. Ao criar ou atualizar uma execução de verificação, você pode adicionar anotações. Neste início rápido, você está [atualizando a execução de verificações](/rest/reference/checks#update-a-check-run) com anotações. -A API de verificação limita o número de anotações a um máximo de 50 por solicitação de API. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint three times. Cada uma das duas primeiras solicitações teria 50 anotações e a terceira solicitação incluiria as cinco anotações restantes. Cada vez que você atualizar a execução de verificação, as anotações são anexadas à lista de anotações que já existem para a execução de verificação. +A API de verificação limita o número de anotações a um máximo de 50 por solicitação de API. Para criar mais de 50 anotações, você deverá fazer várias solicitações para o ponto de extremidade [Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run). Por exemplo, para criar 105 anotações você deve chamar o ponto de extremidade [Atualizar uma execução de verificação](/rest/reference/checks#update-a-check-run) três vezes. Cada uma das duas primeiras solicitações teria 50 anotações e a terceira solicitação incluiria as cinco anotações restantes. Cada vez que você atualizar a execução de verificação, as anotações são anexadas à lista de anotações que já existem para a execução de verificação. -Uma execução de verificação espera anotações como um array de objetos. Cada objeto de anotação deve incluir o `caminho`, `start_line`,, `end_line`, `annotation_level` e `mensagem`. O RuboCop também fornece `start_column` e `end_column`. Portanto, você pode incluir esses parâmetros opcionais na anotação. As anotações são compatíveis apenas com `start_column` e `end_column` na mesma linha. See the [`annotations` object](/rest/reference/checks#annotations-object-1) reference documentation for details. +Uma execução de verificação espera anotações como um array de objetos. Cada objeto de anotação deve incluir o `caminho`, `start_line`,, `end_line`, `annotation_level` e `mensagem`. O RuboCop também fornece `start_column` e `end_column`. Portanto, você pode incluir esses parâmetros opcionais na anotação. As anotações são compatíveis apenas com `start_column` e `end_column` na mesma linha. Para obter mais informações, consulte a documentação de referência do objeto [`anotações`](/rest/reference/checks#annotations-object-1). Você irá extrair as informações necessárias do RuboCop para criar cada anotação. Acrescente o seguinte código ao código que você adicionou na [seção anterior](#step-23-running-rubocop): @@ -869,4 +869,4 @@ Depois ler este guia, você aprendeu os princípios básicos para usar a API de Aqui estão algumas ideias do que você pode fazer a seguir: * Atualmente, o botão "Corrija isso" sempre é exibido. Atualize o código que você escreveu para exibir o botão "Corrija isso" somente quando o RuboCop encontrar erros. -* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch. +* Se preferir que RuboCop não comprometa os arquivos diretamente para o branch principal, você pode atualizar o código para [criar um pull request](/rest/reference/pulls#create-a-pull-request) com um novo branch baseado no branch principal. 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 5b43679ee0..71e00597ca 100644 --- a/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/scopes-for-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Escopos para aplicativos OAuth +title: Scopes for OAuth Apps intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps/ @@ -11,20 +11,19 @@ versions: github-ae: '*' --- -Ao configurar um aplicativo OAuth no GitHub, os escopos solicitados são exibidos para o usuário no formulário de autorização. +When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form. {% note %} -**Observação:** Se você está criando um aplicativo no GitHub, você não precisa fornecer escopos na sua solicitação de autorização. Para obter mais informações sobre isso, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -Se o seu -{% data variables.product.prodname_oauth_app %} não tem acesso a um navegador, como uma ferramenta CLI, você não precisa especificar um escopo para que os usuários efetuem a autenticação no seu aplicativo. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)". +If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)." {% endif %} -Verifique os cabeçalhos para ver quais escopos do OAuth você tem e o que a ação da API aceita: +Check headers to see what OAuth scopes you have, and what the API action accepts: ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I @@ -33,51 +32,53 @@ X-OAuth-Scopes: repo, user X-Accepted-OAuth-Scopes: user ``` -* `X-OAuth-Scopes` lista o escopo que seu token autorizou. -* `X-Accepted-OAuth-Scopes` lista os escopos verificados pela ação. +* `X-OAuth-Scopes` lists the scopes your token has authorized. +* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for. -### Escopos disponíveis +### Available scopes -| Nome | Descrição | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| **`(sem escopo)`** | Concede acesso somente leitura a informações públicas (inclui informações de perfil do usuário público, informações de repositório público e gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| **`site_admin`** | Concede acesso de administrador aos pontos de extremidades da API de administração [{% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Concede acesso total a repositórios privados e públicos. Isso inclui acesso de leitura/gravação ao código, status do commit, repositório e projetos da organização, convites, colaboradores, adição de associações de equipe, status de implantação e webhooks de repositórios para repositórios e organizações públicos e privados. Também concede capacidade para gerenciar projetos de usuário. | -|  `repo:status` | Concede acesso de leitura/gravação aos status do commit do repositório público e privado. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso a status de compromisso de repositórios privados *sem* conceder acesso ao código. | -|  `repo_deployment` | Concede acesso aos [status de implantação](/rest/reference/repos#deployments) para repositórios públicos e privados. Esse escopo só é necessário para conceder a outros usuários ou serviços acesso ao status de implantação, *sem* conceder acesso ao código. | -|  `public_repo` | Limita o acesso a repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para repositórios públicos marcados com uma estrela. | -|  `repo:invite` | Concede habilidades de aceitar/recusar convites para colaborar em um repositório. Este escopo só é necessário para conceder a outros usuários ou servicos acesso a convites *sem* conceder acesso ao código.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} -|  `security_events` | Concede acesso de leitura e escrita a eventos de segurança na [API {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning).{% endif %} -| **`admin:repo_hook`** | Concede acesso de leitura, gravação e ping aos hooks do repositório em repositórios públicos e privados. O escopos do `repo` e `public_repo` concede acesso total aos repositórios, incluindo hooks de repositório. Use o escopo `admin:repo_hook` para limitar o acesso apenas a hooks de repositório. | -|  `write:repo_hook` | Concede acesso de leitura, escrita e ping para os hooks em repositórios públicos ou privados. | -|  `read:repo_hook` | Concede acesso de leitura e ping para hooks em repositórios públicos ou privados. | -| **`admin:org`** | Gerencia totalmente a organização e suas equipes, projetos e associações. | -|  `write:org` | Acesso de leitura e gravação à associação da organização, aos projetos da organização e à associação da equipe. | -|  `read:org` | Acesso somente leitura à associação da organização, aos projetos da organização e à associação da equipe. | -| **`admin:public_key`** | Gerenciar totalmente as chaves públicas. | -|  `write:public_key` | Criar, listar e visualizar informações das chaves públicas. | -|  `read:public_key` | Listar e visualizar informações para as chaves públicas. | -| **`admin:org_hook`** | Concede acesso de leitura, gravação, ping e e exclusão de hooks da organização. **Observação:** Os tokens do OAuth só serão capazes de realizar essas ações nos hooks da organização que foram criados pelo aplicativo OAuth. Os tokens de acesso pessoal só poderão realizar essas ações nos hooks da organização criados por um usuário. | -| **`gist`** | Concede acesso de gravação aos gists. | -| **`notificações`** | Condece:
      * acesso de gravação a notificações de um usuário
      * acesso para marcar como leitura nos threads
      * acesso para inspecionar e não inspecionar um repositório e
      * acesso de leitura, gravação e exclusão às assinaturas dos threads. | -| **`usuário`** | Concede acesso de leitura/gravação apenas às informações do perfil. Observe que este escopo inclui `user:email` e `user:follow`. | -|  `read:user` | Concede acesso para ler as informações do perfil de um usuário. | -|  `usuário:email` | Concede acesso de leitura aos endereços de e-mail de um usuário. | -|  `user:follow` | Concede acesso para seguir ou deixar de seguir outros usuários. | -| **`delete_repo`** | Concede acesso para excluir repositórios administráveis. | -| **`write:discussion`** | Permite acesso de leitura e gravação para discussões da equipe. | -|  `leia:discussion` | Permite acesso de leitura para as discussões de equipe.{% if currentVersion == "free-pro-team@latest" %} -| **`write:packages`** | Concede acesso ao para fazer o upload ou publicação de um pacote no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Publicar um pacote](/github/managing-packages-with-github-packages/publishing-a-package)". | -| **`read:packages`** | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Instalando um pacote](/github/managing-packages-with-github-packages/installing-a-package)". | -| **`delete:packages`** | Concede acesso para excluir pacotes de {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluir pacotes](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} -| **`admin:gpg_key`** | Gerenciar totalmente as chaves GPG. | -|  `write:gpg_key` | Criar, listar e visualizar informações das chaves GPG. | -|  `read:gpg_key` | Liste e visualize informações para as chaves GPG.{% if currentVersion == "free-pro-team@latest" %} -| **`fluxo de trabalho`** | Concede a capacidade de adicionar e atualizar arquivos do fluxo de trabalho do {% data variables.product.prodname_actions %}. Os arquivos do fluxo de trabalho podem ser confirmados sem este escopo se o mesmo arquivo (com o mesmo caminho e conteúdo) existir em outro branch no mesmo repositório. Os arquivos do fluxo de trabalho podem expor `GITHUB_TOKEN` que pode ter um conjunto diferente de escopos. Consulte https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token para detalhes.{% endif %} +Name | Description +-----|-----------| +**`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} +**`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. + `repo:status`| Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. + `repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. + `public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. + `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + `security_events` | Grants:
      read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).
      read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} + `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} +**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. + `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. + `read:repo_hook`| Grants read and ping access to hooks in public or private repositories. +**`admin:org`** | Fully manage the organization and its teams, projects, and memberships. + `write:org`| Read and write access to organization membership, organization projects, and team membership. + `read:org`| Read-only access to organization membership, organization projects, and team membership. +**`admin:public_key`** | Fully manage public keys. + `write:public_key`| Create, list, and view details for public keys. + `read:public_key`| List and view details for public keys. +**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user. +**`gist`** | Grants write access to gists. +**`notifications`** | Grants:
      * read access to a user's notifications
      * mark as read access to threads
      * watch and unwatch access to a repository, and
      * read, write, and delete access to thread subscriptions. +**`user`** | Grants read/write access to profile info only. Note that this scope includes `user:email` and `user:follow`. + `read:user`| Grants access to read a user's profile data. + `user:email`| Grants read access to a user's email addresses. + `user:follow`| Grants access to follow or unfollow other users. +**`delete_repo`** | Grants access to delete adminable repositories. +**`write:discussion`** | Allows read and write access for team discussions. + `read:discussion` | Allows read access for team discussions.{% if currentVersion == "free-pro-team@latest" %} +**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)". +**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)". +**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "[Deleting packages](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} +**`admin:gpg_key`** | Fully manage GPG keys. + `write:gpg_key`| Create, list, and view details for GPG keys. + `read:gpg_key`| List and view details for GPG keys.{% if currentVersion == "free-pro-team@latest" %} +**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes, see https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token for details.{% endif %} {% 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: +**Note:** Your OAuth App can request the scopes in the initial redirection. You +can specify multiple scopes by separating them with a space: https://github.com/login/oauth/authorize? client_id=...& @@ -85,16 +86,31 @@ X-Accepted-OAuth-Scopes: user {% endnote %} -### Escopos solicitados e escopos concedidos +### Requested scopes and granted scopes -O atributo `escopo` lista os escopos adicionados ao token que foram concedido pelo usuário. Normalmente, estes escopos são idênticos aos que você solicitou. No entanto, os usuários podem editar seus escopos, concedendo, efetivamente, ao seu aplicativo um acesso menor do que você solicitou originalmente. Além disso, os usuários podem editar o escopo do token depois que o fluxo do OAuth for concluído. Você deve ter em mente esta possibilidade e ajustar o comportamento do seu aplicativo de acordo com isso. +The `scope` attribute lists scopes attached to the token that were granted by +the user. Normally, these scopes will be identical to what you requested. +However, users can edit their scopes, effectively +granting your application less access than you originally requested. Also, users +can edit token scopes after the OAuth flow is completed. +You should be aware of this possibility and adjust your application's behavior +accordingly. -É importante lidar com casos de erro em que um usuário escolhe conceder menos acesso do que solicitado originalmente. Por exemplo, os aplicativos podem alertar ou informar aos seus usuários que a funcionalidade será reduzida ou não serão capazes de realizar algumas ações. +It's important to handle error cases where a user chooses to grant you +less access than you originally requested. For example, applications can warn +or otherwise communicate with their users that they will see reduced +functionality or be unable to perform some actions. -Além disso, os aplicativos sempre podem enviar os usuários de volta através do fluxo para obter permissão adicional, mas não se esqueça de que os usuários sempre podem dizer não. +Also, applications can always send users back through the flow again to get +additional permission, but don’t forget that users can always say no. -Confira o [Príncípios do guia de autenticação](/guides/basics-of-authentication/), que fornece dicas para lidar com escopos de token modificável. +Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which +provides tips on handling modifiable token scopes. -### Escopos normalizados +### Normalized scopes -Ao solicitar vários escopos, o token é salvo com uma lista normalizada de escopos, descartando aqueles que estão implicitamente incluídos pelo escopo solicitado. Por exemplo, a solicitação do usuário `user,gist,user:email` irá gerar apenas um token com escopos de `usuário` e `gist`, desde que o acesso concedido com o escopo `user:email` esteja incluído no escopo `usuário`. +When requesting multiple scopes, the token is saved with a normalized list +of scopes, discarding those that are implicitly included by another requested +scope. For example, requesting `user,gist,user:email` will result in a +token with `user` and `gist` scopes only since the access granted with +`user:email` scope is included in the `user` scope. diff --git a/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index ce366e1f24..cfee33a91c 100644 --- a/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -220,7 +220,7 @@ end #### Defina um gerenciador de encaminhamento -Um encaminhamento vazio está incluído no código do modelo. Este código gerencia todas as solicitações `POST` para o encaminhamento `/event_handler`. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. +Um encaminhamento vazio está incluído no código do modelo. Este código gerencia todas as solicitações `POST` para o encaminhamento `/event_handler`. Você não vai escrever este manipulador de eventos neste início rápido, mas veja os outros [guias de início rápido](/apps/quickstart-guides/) para obter exemplos de como estender o aplicativo deste modelo. ``` ruby post '/event_handler' do @@ -422,7 +422,7 @@ Aqui estão alguns problemas comuns e algumas soluções sugeridas. Se você tiv **R:** Você pode não estar executando o cliente da Smee ou você pode não ter o domínio Smee correto nas configurações do seu aplicativo GitHub. Primeiro verifique para certificar-se de que o cliente da Smee está em execução em uma aba do Terminal. Se esse não for o problema, acesse a sua [página de configurações do aplicativo](https://github.com/settings/apps) e verifique os campos exibidos na "[Etapa 2. Registre um novo aplicativo GitHub](#step-2-register-a-new-github-app)." Certifique-se de que o domínio nesses campos corresponde ao domínio que você usou no seu comando `smee -u ` na "[Etapa 1. Inicie um novo canal da Smee](#step-1-start-a-new-smee-channel)." -* **P:** Estou vendo um `Octokit::NotFound` 404 error na minha saída de depuração: +* **P:** Eu recebi uma mensagem de erro `Octokit::NotFound` 404 error na minha saída de depuração: ``` 2018-12-06 15:00:56 - Octokit::NotFound - POST https://api.github.com/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token: ``` diff --git a/translations/pt-BR/content/developers/apps/using-content-attachments.md b/translations/pt-BR/content/developers/apps/using-content-attachments.md index bca23e3044..3b4914fb4f 100644 --- a/translations/pt-BR/content/developers/apps/using-content-attachments.md +++ b/translations/pt-BR/content/developers/apps/using-content-attachments.md @@ -55,7 +55,7 @@ O fluxo de anexo de conteúdo mostra a relação entre a URL no problema ou pull } ``` -**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. Você também precisará do `id` da `instalação` para efetuar a autenticação como uma [instalação do aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**Etapa 4.** O aplicativo usa o `content_reference` `id` para [Criar um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment) usando a API REST. Você também precisará do `id` da `instalação` para efetuar a autenticação como uma [instalação do aplicativo GitHub](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -116,7 +116,7 @@ curl -X "POST" "https://api.github.com/graphql" \ }' ``` -For more information on `node_id`, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." +Para obter mais informações sobre `node_id`, consulte "[Usando IDs de nós globais](/graphql/guides/using-global-node-ids)". ### Exemplo de uso de manifestos do Probot e do aplicativo GitHub diff --git a/translations/pt-BR/content/developers/github-marketplace/about-github-marketplace.md b/translations/pt-BR/content/developers/github-marketplace/about-github-marketplace.md index bde4ed44e8..823e6a5468 100644 --- a/translations/pt-BR/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/pt-BR/content/developers/github-marketplace/about-github-marketplace.md @@ -1,6 +1,6 @@ --- title: Sobre o GitHub Marketplace -intro: 'Aprenda os princípios básicos para preparar seu aplicativo para revisão antes de entrar no {% data variables.product.prodname_marketplace %}.' +intro: 'Aprenda sobre {% data variables.product.prodname_marketplace %} em que você pode compartilhar seus aplicativos e ações publicamente com todos os usuários do {% data variables.product.product_name %}.' redirect_from: - /apps/marketplace/getting-started/ - /marketplace/getting-started @@ -18,48 +18,37 @@ Para saber mais sobre publicação de {% data variables.product.prodname_actions ### Aplicativos -Você pode listar os aplicativos verificados e não verificados no {% data variables.product.prodname_marketplace %}. Os aplicativos não verificados não passam por segurança, testes e ciclo de verificação que {% data variables.product.prodname_dotcom %} exige para aplicativos verificados. +Qualquer pessoa pode compartilhar seus aplicativos com outros usuários em {% data variables.product.prodname_marketplace %}, mas apenas os anúncios verificados por {% data variables.product.company_short %} podem incluir planos pagos. Para obter mais informações, consulte "[Sobre criadores verificados](/developers/github-marketplace/about-verified-creators)". -Os aplicativos verificados têm um selo verde no {% data variables.product.prodname_marketplace %}. Os aplicativos não verificados têm um selo cinza ao lado de sua listagem e só estão disponíveis como aplicativos gratuitos. +Se estiver interessado em criar um aplicativo para {% data variables.product.prodname_marketplace %}, mas você é novo em {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_app %}s, consulte "[Criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" ou "[Criar {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)". -![Selo verde para verificado e cinza para não verificado](/assets/images/marketplace/marketplace_verified_badges.png) - -Se você estiver interessado em criar um aplicativo para {% data variables.product.prodname_marketplace %}, mas você é novo no {% data variables.product.prodname_github_apps %} e no {% data variables.product.prodname_oauth_app %}, consulte "[Criando aplicativos](/apps/)". - -{% data reusables.marketplace.github_apps_preferred %}, embora você possa listar tanto o OAuth quanto {% data variables.product.prodname_github_app %}s no {% data variables.product.prodname_marketplace %}. Consulte "[Diferenças entre os aplicativos GitHub e OAuth](/apps/differences-between-apps/)" para obter mais detalhes. Para saber mais sobre como mudar do OAuth para {% data variables.product.prodname_github_apps %}, consulte [Migrando aplicativos OAuth para {% data variables.product.prodname_github_app %}s](/apps/migrating-oauth-apps-to-github-apps/). +{% data reusables.marketplace.github_apps_preferred %}, embora você possa listar tanto o OAuth quanto {% data variables.product.prodname_github_app %}s no {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" e[Migrando {% data variables.product.prodname_oauth_app %}s para {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/) Em caso de dúvidas dúvidas sobre {% data variables.product.prodname_marketplace %}, entre em contato diretamente com {% data variables.contact.contact_support %}. -#### Aplicativos não verificados +### Publicar um aplicativo em {% data variables.product.prodname_marketplace %} -Os aplicativos não verificados não precisam atender aos "[Requisitos de listagem de um aplicativo no {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)" ou passar pelo "[Processo de revisão de segurança](/marketplace/getting-started/security-review-process/)". +Ao terminar de criar seu aplicativo, você poderá compartilhá-lo com outros usuários publicando-o em {% data variables.product.prodname_marketplace %}. Em resumo, o processo é: -{% data reusables.marketplace.unverified-apps %} Ter um plano pago publicado impedirá que você possa enviar um aplicativo não verificado. Você deve remover os planos pagos ou mantê-los no modo rascunho antes de publicar um aplicativo não verificado. +1. Revise cuidadosamente o seu app para garantir que se comportará como esperado em outros repositórios e que segue as diretrizes das práticas recomendadas. Para obter mais informações, consulte "[as práticas de segurança recomendadas para os aplicativos](/developers/github-marketplace/security-best-practices-for-apps)" e "[requisitos para listar um app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)". -Para listar seu aplicativo não verificado no {% data variables.product.prodname_marketplace %}, você só precisa criar uma "[Listagem em {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)" e enviá-lo como uma listagem não verificada. +1. Adicionar eventos webhook ao aplicativo para rastrear solicitações de cobrança do usuário. Para obter mais informações sobre a API de {% data variables.product.prodname_marketplace %}, eventos de webhook e solicitações de cobrança, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". -{% data reusables.marketplace.launch-with-free %} +1. Crie um rascunho de listagem de {% data variables.product.prodname_marketplace %} Para obter mais informações, consulte "[Criar uma listagem para o seu aplicativo](/developers/github-marketplace/drafting-a-listing-for-your-app)". -#### Aplicativos verificados +1. Adicionar um plano de preços. Para obter mais informações, consulte "[Configurar planos de preços para sua listagem](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". -Se você já criou um aplicativo e está interessado em enviar uma listagem verificado no {% data variables.product.prodname_marketplace %}, comece aqui: +1. Verifique se seu aplicativo atende aos requisitos para a listagem em {% data variables.product.prodname_marketplace %} como um aplicativo grátis ou pago. Para obter mais informações, consulte "[Requisitos para listar um app](/developers/github-marketplace/requirements-for-listing-an-app)". -1. [Começando com {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)
      Saiba mais sobre requisitos, diretrizes e processo de envio de aplicativos. +1. Leia e aceite os termos do "[Contrato do Desenvolvedor de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)". -1. [Integrar com a API do {% data variables.product.prodname_marketplace %} ](/marketplace/integrating-with-the-github-marketplace-api/)
      Antes de poder listar seu aplicativo no {% data variables.product.prodname_marketplace %}, você deverá integrar os fluxos de cobrança usando a API do {% data variables.product.prodname_marketplace %} e os eventos de webhook. +1. Envie sua listagem para publicação em {% data variables.product.prodname_marketplace %}, solicitando verificação, se você desejar vender o aplicativo. Para obter mais informações, consulte "[Enviar sua listagem para publicação](/developers/github-marketplace/submitting-your-listing-for-publication)". -1. [Listar no {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)
      Crie uma listagem de rascunho {% data variables.product.prodname_marketplace %} de {% data variables.product.prodname_marketplace %}, defina as configurações de webhook e configure planos de preços. +Um especialista em integração entrará em contato com você com outras dúvidas ou etapas posteriores. Por exemplo, se você adicionou um plano pago, você deverá concluir o processo de verificação e concluir a integração financeira. Assim que seu anúncio for aprovado, o aplicativo será publicado em {% data variables.product.prodname_marketplace %}. -1. [Vendendo seu aplicativo](/marketplace/selling-your-app/)
      Saiba mais sobre os planos de preço, ciclos de cobrança e como receber pagamento do {% data variables.product.prodname_dotcom %} para o seu aplicativo. +### Ver como seu aplicativo está sendo executado -1. [{% data variables.product.prodname_marketplace %} Ideias](/marketplace/github-marketplace-insights/)
      Veja como seu aplicativo está sendo executado em {% data variables.product.prodname_marketplace %}. Você pode usar métricas coletadas pelo {% data variables.product.prodname_dotcom %} para orientar sua campanha de marketing e ter sucesso no {% data variables.product.prodname_marketplace %}. +Você pode acessar métricas e transações para a sua listagem. Para obter mais informações, consulte: -1. [ transações do {% data variables.product.prodname_marketplace %} ](/marketplace/github-marketplace-transactions/)
      Faça o download e veja os dados de transação para a sua listagem do {% data variables.product.prodname_marketplace %}. - -### Revisar seu aplicativo - -Queremos ter certeza de que os aplicativos oferecidos no {% data variables.product.prodname_marketplace %} são seguros, protegidos e bem testados. Os especialistas de integração do {% data variables.product.prodname_marketplace %} irão rever seu aplicativo para garantir que ele atende a todos os requisitos. Siga as diretrizes nestes artigos antes de enviar seu aplicativo: - - -* [Requisitos para listar um aplicativo no {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) -* [Processo de revisão de segurança](/marketplace/getting-started/security-review-process/) +- "[Visualizar métricas para a sua listagem](/developers/github-marketplace/viewing-metrics-for-your-listing)" +- "[Visualizar transações para a sua listagem](/developers/github-marketplace/viewing-transactions-for-your-listing)" diff --git a/translations/pt-BR/content/developers/github-marketplace/about-verified-creators.md b/translations/pt-BR/content/developers/github-marketplace/about-verified-creators.md new file mode 100644 index 0000000000..dfe5d350f0 --- /dev/null +++ b/translations/pt-BR/content/developers/github-marketplace/about-verified-creators.md @@ -0,0 +1,43 @@ +--- +title: Sobre criadores verificados +intro: 'Todas as organizações que desejam vender aplicativos em {% data variables.product.prodname_marketplace %}, devem seguir um processo de verificação. Sua identidade é verificada e seu processo de cobrança revisado.' +versions: + free-pro-team: '*' +--- + +### Sobre criadores verificados + +Um criador verificado é uma organização que {% data variables.product.company_short %} verificou. Qualquer pessoa pode compartilhar seus aplicativos com outros usuários em {% data variables.product.prodname_marketplace %}, mas somente organizações verificadas por {% data variables.product.company_short %} podem vender aplicativos. Para obter mais informações sobre organizações, consulte "[Sobre organizações](/github/setting-up-and-managing-organizations-and-teams/about-organizations)". + +O processo de verificação tem o objetivo de proteger os usuários. Por exemplo, ele verifica a identidade do vendedor, verifica se a sua organização de {% data variables.product.product_name %} está configurada de forma segura e se pode ser contatada para suporte. + +Depois de ser aprovado na verificação, todos os aplicativos que as listas da organização em {% data variables.product.prodname_marketplace %} são exibidos com um selo de criador verificado {% octicon "verified" aria-label="Verified creator badge" %}. A organização agora pode adicionar planos pagos a qualquer um de seus aplicativos. Cada aplicativo com um plano pago também passa por um processo de integração financeira para verificar se está configurado para lidar com a cobrança de forma correta. + +![selos de criadores verificados](/assets/images/marketplace/marketplace_verified_creator_badges_apps.png) + +Além do selo de criador verificado, você também verá selos referentes a aplicativos verificados e não verificados. Esses aplicativos foram publicados usando o método antigo para verificar aplicativos individuais. + +![Selo verde para verificado e cinza para não verificado](/assets/images/marketplace/marketplace_verified_badges.png) + +Para obter informações sobre como encontrar aplicativos para usar, consulte "[Pesquisar {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". + +### Sobre o processo de verificação + +A primeira vez que você solicitar verificação para uma listagem de um dos seus aplicativos, você entrará no processo de verificação. Um especialista em integração irá guiá-lo durante o processo. Isto inclui verificar: + +- Informações de perfil - As informações básicas do perfil são preenchidas com precisão e de forma adequada. +- Segurança - A organização habilitou a autenticação de dois fatores. +- Domínio verificado - A organização verificou o domínio da URL do site. +- Comprar evento webhook - O evento é tratado de forma correta pelo aplicativo. + +Quando sua organização é verificada, todos os seus aplicativos são exibidos com um selo de criador verificado. Agora você pode oferecer planos pagos para qualquer um dos seus aplicativos. + +Para obter mais informações sobre os requisitos para a listagem de um aplicativo em {% data variables.product.prodname_marketplace %}, consulte "[Requisitos para listar um aplicativo em {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como fazer isso, consulte: "[Enviar o seu anúncio para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". + +{% note %} + +**Nota:** Este processo de verificação para aplicativos substitui o processo anterior em que os aplicativos individuais foram verificados. O processo atual é semelhante ao processo de verificação de ações. Se você tiver aplicativos que foram verificados no processo antigo, eles não serão afetados pelas alterações. A equipe de {% data variables.product.prodname_marketplace %} entrará em contato com você com detalhes sobre como fazer a migração para uma verificação baseada na organização. + +{% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/billing-customers.md b/translations/pt-BR/content/developers/github-marketplace/billing-customers.md index 47d8bec872..818abf691a 100644 --- a/translations/pt-BR/content/developers/github-marketplace/billing-customers.md +++ b/translations/pt-BR/content/developers/github-marketplace/billing-customers.md @@ -13,7 +13,7 @@ versions: ### Entender o ciclo de cobrança -Os clientes podem escolher um ciclo de cobrança mensal ou anual quando ao comprar seu aplicativo. Todas as alterações que os clientes fazem no ciclo de cobrança e seleção de plano acionará um evento de `marketplace_purchase`. Você pode fazer referência à carga do webhook `marketplace_purchase` para ver qual ciclo de cobrança um cliente seleciona e quando começa a próxima data de cobrança (`effective_date`). Para obter mais informações sobre cargas do webhook, "[eventos de webhook {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)". +Os clientes podem escolher um ciclo de cobrança mensal ou anual quando ao comprar seu aplicativo. Todas as alterações que os clientes fazem no ciclo de cobrança e seleção de plano acionará um evento de `marketplace_purchase`. Você pode fazer referência à carga do webhook `marketplace_purchase` para ver qual ciclo de cobrança um cliente seleciona e quando começa a próxima data de cobrança (`effective_date`). Para obter mais informações sobre cargas de webhook, consulte "[eventos de Webhook para a API de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)". ### Fornecer serviços de cobrança na interface de usuário do seu aplicativo @@ -23,7 +23,7 @@ Os clientes devem ser capazes de executar as seguintes ações no site do seu ap ### Os serviços de cobrança para upgrade, downgrade e cancelamentos -Siga estas diretrizes para upgrades, downgrade e cancelamentos para manter um processo de cobrança claro e consistente. Para obter instruções mais detalhadas sobre os eventos de compra do {% data variables.product.prodname_marketplace %}, consulte "[Fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)". +Siga estas diretrizes para upgrades, downgrade e cancelamentos para manter um processo de cobrança claro e consistente. Para obter instruções mais detalhadas sobre os eventos de compra de {% data variables.product.prodname_marketplace %}, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". Você pode usar a chave do `marketplace_purchase` do webhook `effective_date` para determinar quando a mudança de um plano irá ocorrer e sincronizar periodicamente as [Lista de contas para um plano](/rest/reference/apps#list-accounts-for-a-plan). @@ -33,7 +33,7 @@ Quando um cliente atualiza seu plano de preços ou altera seu ciclo de cobrança {% data reusables.marketplace.marketplace-failed-purchase-event %} -Para obter informações sobre a construção de fluxos de trabalho de atualização e downgrade para seu aplicativo, consulte "[Atualizar e fazer downgrade de planos](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)". +For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)." #### Downgrades e cancelamentos @@ -45,4 +45,4 @@ Quando um cliente cancela um plano, você deve: {% data reusables.marketplace.cancellation-clarification %} - Habilitá-los para atualizar o plano por meio do GitHub, caso desejem continuar o plano mais adiante. -Para obter informações sobre a criação de fluxos de trabalho de construção no seu aplicativo, consulte "[Cancelar planos](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)". +Para obter informações sobre a construção de fluxos de trabalho de cancelamento no seu aplicativo, consulte "[Manipulação de cancelamento de plano](/developers/github-marketplace/handling-plan-cancellations)". diff --git a/translations/pt-BR/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md b/translations/pt-BR/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md new file mode 100644 index 0000000000..4a10106f62 --- /dev/null +++ b/translations/pt-BR/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md @@ -0,0 +1,20 @@ +--- +title: Práticas recomendadas de experiência do cliente para aplicativos +intro: 'Diretrizes para a criação de um aplicativo fácil de usar e entender.' +shortTitle: Práticas recomendadas de experiência do cliente +versions: + free-pro-team: '*' +--- + +Se você seguir essas práticas recomendadas, elas ajudarão você a oferecer uma boa experiência para o cliente. + +### Comunicação com o cliente + +- Os materiais de marketing do aplicativo devem representar com precisão o comportamento do aplicativo. +- Os aplicativos devem incluir links para a documentação do usuário que descreve como configurar e usar o aplicativo. +- Os clientes devem ser capazes de ver que tipo de plano eles têm na seção de configurações de cobrança, perfil ou conta do aplicativo. +- Os clientes devem poder instalar e usar seu aplicativo em uma conta pessoal e em uma conta de organização. Eles devem poder ver e gerenciar o app nessas contas separadamente. + +### Gerenciamento de plano + +{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/pt-BR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 5e8cc89690..6658599377 100644 --- a/translations/pt-BR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,8 +60,8 @@ Após criar um rascunho da listagem do {% data variables.product.prodname_market ### Enviar o seu aplicativo -Após concluir a sua listagem do {% data variables.product.prodname_marketplace %}, você poderá enviá-la para revisão na página **Visão geral**. Você vai precisar ler e aceitar o "[{% data variables.product.prodname_marketplace %} Contrato de desenvolvedor](/articles/github-marketplace-developer-agreement/)" e, em seguida, você poderá clicar em **Enviar para revisão**. Após enviar seu aplicativo para revisão , a equipe de integração do {% data variables.product.prodname_marketplace %} entrará em contato com você com informações adicionais sobre o processo de integração. Você pode saber mais sobre o processo de revisão de segurança e integração em "[Começando com {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)". +Após concluir a sua listagem do {% data variables.product.prodname_marketplace %}, você poderá enviá-la para revisão na página **Visão geral**. Você vai precisar ler e aceitar o "[{% data variables.product.prodname_marketplace %} Contrato de desenvolvedor](/articles/github-marketplace-developer-agreement/)" e, em seguida, você poderá clicar em **Enviar para revisão**. Depois de enviar seu aplicativo para análise, um especialista em integração entrará em contato com você com informações adicionais sobre o processo de integração. Você pode saber mais sobre o processo de revisão de segurança e integração em "[Começando com {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)". ### Remover uma listagem do {% data variables.product.prodname_marketplace %} -Se você não desejar mais listar seu aplicativo no {% data variables.product.prodname_marketplace %}, entre em contato com [marketplace@github.com](mailto:marketplace@github.com) para remover sua listagem. +Se você não quiser mais listar seu aplicativo em {% data variables.product.prodname_marketplace %}, entre em contato {% data variables.contact.contact_support %} para remover o seu anúncio. diff --git a/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index de8682dc7a..f8bad5dc24 100644 --- a/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/pt-BR/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -28,7 +28,7 @@ O GitHub envia a o webhook de [`marketplace_purchase`](/webhooks/event-payloads/ Leia o objeto `effective_date` e `marketplace_purchase` do webhook `marketplace_purchase` para determinar qual plano o cliente comprou, quando começa o ciclo de cobrança, e quando começa o próximo ciclo de cobrança. -Se o seu aplicativo oferecer um teste grátis, leia o atributo `marketplace_purchase[on_free_trial]` do webhook. Se o valor for `verdadeiro`, seu aplicativo deverá acompanhar a data de início de teste gratuito (`effective_date`) e a data em que o teste gratuito termina (`free_trial_ends_on`). Use a data `free_trial_ends_on` para exibir os dias restantes em um teste gratuito na interface de usuário do seu aplicativo. Você pode fazer isso em um banner ou na sua [interface de usuário de cobrança](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). Para aprender como gerenciar os cancelamentos antes de um teste gratuito terminar, consulte "[Planos de cancelamento](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)". Consulte "[Atualizar e fazer downgrade de planos](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)para descobrir como fazer a transição de um teste gratuito para um plano pago quando um teste gratuito termina. +Se o seu aplicativo oferecer um teste grátis, leia o atributo `marketplace_purchase[on_free_trial]` do webhook. Se o valor for `verdadeiro`, seu aplicativo deverá acompanhar a data de início de teste gratuito (`effective_date`) e a data em que o teste gratuito termina (`free_trial_ends_on`). Use a data `free_trial_ends_on` para exibir os dias restantes em um teste gratuito na interface de usuário do seu aplicativo. Você pode fazer isso em um banner ou na sua [interface de usuário de cobrança](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). Para aprender como lidar com os cancelamentos antes de um teste grátis, consulte "[Gerenciar cancelamentos de plano](/developers/github-marketplace/handling-plan-cancellations)". Consulte "[Gerenciamento das alterações de plano](/developers/github-marketplace/handling-plan-changes)" para descobrir como fazer transição de um teste grátis para um plano pago quando um teste gratuito expira. Consulte "[ eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)para obter um exemplo da carga de evento `marketplace_purchase`. diff --git a/translations/pt-BR/content/developers/github-marketplace/index.md b/translations/pt-BR/content/developers/github-marketplace/index.md index 0a245099ea..0842fc13a3 100644 --- a/translations/pt-BR/content/developers/github-marketplace/index.md +++ b/translations/pt-BR/content/developers/github-marketplace/index.md @@ -11,8 +11,10 @@ versions: {% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /about-github-marketplace %} + {% link_in_list /about-verified-creators %} {% link_in_list /requirements-for-listing-an-app %} - {% link_in_list /security-review-process-for-submitted-apps %} + {% link_in_list /security-best-practices-for-apps %} + {% link_in_list /customer-experience-best-practices-for-apps %} {% link_in_list /viewing-metrics-for-your-listing %} {% link_in_list /viewing-transactions-for-your-listing %} {% topic_link_in_list /using-the-github-marketplace-api-in-your-app %} @@ -27,7 +29,7 @@ versions: {% link_in_list /writing-a-listing-description-for-your-app %} {% link_in_list /setting-pricing-plans-for-your-listing %} {% link_in_list /configuring-a-webhook-to-notify-you-of-plan-changes %} - {% link_in_list /submitting-your-listing-for-review %} + {% link_in_list /submitting-your-listing-for-publication %} {% topic_link_in_list /selling-your-app-on-github-marketplace %} {% link_in_list /pricing-plans-for-github-marketplace-apps %} {% link_in_list /billing-customers %} diff --git a/translations/pt-BR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/pt-BR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md index 1fb9874593..8e0e8df6b4 100644 --- a/translations/pt-BR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/pt-BR/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -10,35 +10,45 @@ versions: -Os planos de preço em {% data variables.product.prodname_marketplace %} podem ser grátis, fixos ou por unidade, e o GitHub lista o preço em dólar. Os clientes compram o seu aplicativo usando um método de pagamento anexado à sua conta de {% data variables.product.product_name %}, sem ter de sair do GitHub.com. Você não precisa escrever código para executar transações de cobrança, mas terá que gerenciar os [fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) para os eventos de compra. +Os planos de preços de {% data variables.product.prodname_marketplace %} podem ser grátis, fixos ou por unidade. Os preços são definidos, exibidos e processados em dólares. Os planos pagos são restritos a anúncios verificados. + +Os clientes compram seu aplicativo usando um método de pagamento anexado à sua conta de {% data variables.product.product_name %} sem precisar sair de {% data variables.product.prodname_dotcom_the_website %}. Você não precisa escrever um código para realizar transações de cobrança, mas deverá gerenciar eventos da API de {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". Se o aplicativo que você está listando no {% data variables.product.prodname_marketplace %} tiver várias opções de plano, você poderá definir os planos de preços correspondentes. Por exemplo, se o app tiver duas opções de plano, um plano de código aberto e um plano profissional, você poderá criar um plano de preços grátis para o seu plano de código aberto e um plano de preço fixo para o seu plano profissional. Cada listagem do {% data variables.product.prodname_marketplace %} deve ter um preço anual e um preço mensal para todos os planos listados. Para obter mais informações sobre como criar um plano de preços, consulte "[Configurar um plano de preços da listagem de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". -{% note %} - -**Observação:** Se você estiver listando um aplicativo em {% data variables.product.prodname_marketplace %}, você não poderá listar seu aplicativo com um plano de preços grátis, caso você ofereça um serviço pago fora do {% data variables.product.prodname_marketplace %}. - -{% endnote %} +{% data reusables.marketplace.free-plan-note %} ### Tipos de planos de preços -Os **Planos de preços grátis** são completamente grátis para os usuários. Se você configurar um plano de preços grátis, você não poderá cobrar os usuários que escolherem o plano de preços grátis para o uso do seu aplicativo. Você pode criar planos grátis e pagos para a sua listagem. Os aplicativos grátis e não verificados não precisam implementar nenhum fluxo de cobrança. Os aplicativos grátis verificados pelo Github precisam implementar fluxos de cobrança para novas compras e cancelamentos, mas não precisam implementar fluxos de cobrança para testes grátis, atualizações e downgrade. Se você adicionar um plano pago a um aplicativo que já está listado no {% data variables.product.prodname_marketplace %} como um serviço grátis, você deverá reenviar o aplicativo para revisão. +#### Planos de preços grátis -**Os planos de preços fixos** cobram uma taxa definida mensalmente e anualmente. +{% data reusables.marketplace.free-apps-encouraged %} -**Os planos de preços por unidade** cobram uma taxa definida mensalmente ou anualmente para uma unidade que você especificar. Uma "unidade" pode ser qualquer coisa que você deseje (por exemplo, um usuário, estação ou pessoa). +Planos grátis são completamente grátis para os usuários. Se você configurar um plano de preços grátis, você não poderá cobrar os usuários que escolherem o plano de preços grátis para o uso do seu aplicativo. Você pode criar planos grátis e pagos para a sua listagem. -Os **Testes grátis do Marketplace** fornecem aos clientes testes grátis dos aplicativos OAuth ou GitHub por 14 dias. Ao [configurar um plano de preços do Marketplace](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/), Você poderá selecionar a opção de fornecer um teste grátis para planos de preços fixos ou por unidade. +Todos os aplicativos precisam gerenciar eventos para novas compras e cancelamentos. Os aplicativos que só têm planos grátis não precisam gerenciar eventos para testes, atualizações e downgrades grátis. Para mais informações, consulte: "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +Se você adicionar um plano pago a um aplicativo que já esteja listado em {% data variables.product.prodname_marketplace %} como um serviço grátis, você precisará solicitar verificação para o aplicativo e passar pela integração financeira. + +#### Planos de preços pagos + +Existem dois tipos de planos de preços pagos: + +- Os planos de preços fixos cobram uma taxa definida mensalmente e anualmente. + +- Os planos de preços por unidade cobram uma taxa definida mensalmente ou anualmente para uma unidade que você especificar. Uma "unidade" pode ser qualquer coisa que você deseje (por exemplo, um usuário, estação ou pessoa). + +Você também pode oferecer testes grátis. Eles fornecem gratuitamente testes de 14 dias referentes aos aplicativos OAuth ou GitHub para os clientes. Ao configurar um plano de preços do Marketplace você poderá selecionar a opção de fornecer um teste gratuito para planos de taxa fixa ou por unidade de preços ### Testes grátis -Os clientes podem iniciar um teste grátis para qualquer plano pago disponível em uma listagem do Marketplace, mas não poderão criar mais de um teste grátis para um produto do Mercado. +Os clientes podem iniciar uma avaliação gratuita para qualquer plano pago de um anúncio do Marketplace que inclui testes grátis. No entanto, os clientes não podem criar mais de um teste grátis por produto no marketplace. Os testes gratuitos têm uma duração fixa de 14 dias. Os clientes são notificados 4 dias antes do final do período de teste (no 11o dia do teste grátis) de que seu plano será atualizado. No final do teste grátis, os clientes serão inscritos automaticamente no plano que estão testando, caso não efetuem o cancelamento. -Consulte "[Novas compras e testes grátis](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para detalhes sobre como gerenciar testes grátis no seu aplicativo. +Para mais informações, consulte: "[Como gerenciar novas compras e testes grátis](/developers/github-marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)". {% note %} diff --git a/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md index 69a6a46962..b1f4925f6b 100644 --- a/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- title: Requisitos para listar um aplicativo -intro: 'Os aplicativos no {% data variables.product.prodname_marketplace %} devem atender aos requisitos definidos nesta página antes que nossos especialistas de integração do {% data variables.product.prodname_marketplace %} aprovem a listagem.' +intro: 'Os aplicativos em {% data variables.product.prodname_marketplace %} devem atender aos requisitos definidos nessa página antes que o anúncio possa ser publicado.' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ @@ -12,49 +12,62 @@ versions: free-pro-team: '*' --- + +The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app. -Antes de enviar seu aplicativo para revisão, você deve ler e aceitar os termos do "[{% data variables.product.prodname_marketplace %} Contrato do Desenvolvedor](/articles/github-marketplace-developer-agreement/)". Você aceitará os termos dentro do seu [rascunho de listagem](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) em {% data variables.product.product_name %}. Assim que enviar o seu aplicativo, um dos especialistas de integração de {% data variables.product.prodname_marketplace %} entrará em contato com mais informações sobre o processo de integração e irá revisar o seu aplicativo para garantir que atende a estes requisitos: +### Requisitos para todos os anúncios de {% data variables.product.prodname_marketplace %} -### Experiência do usuário +Todos os anúncios em {% data variables.product.prodname_marketplace %} devem ser para ferramentas que fornecem valor à comunidade de {% data variables.product.product_name %}. Ao enviar seu anúncio para publicação, você deverá ler e aceitar os termos do "[ Acordo de Desenvolvedor de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)". -- Os {% data variables.product.prodname_github_app %}s deve ter, no mínimo, 100 instalações. -- Os {% data variables.product.prodname_oauth_app %}s devem ter, no mínimo, 200 usuários. +#### Requisitos de experiência do usuário para todos os aplicativos + +Todos os anúncios devem atender aos requisitos a seguir, independentemente de serem para um aplicativo grátis ou pago. + +- Listings must not actively persuade users away from {% data variables.product.product_name %}. +- Os anúncios devem incluir informações de contato válidas para o editor. +- Os anúncios devem ter uma descrição relevante do aplicativo. +- Os anúncios devem especificar um plano de preços. - Os aplicativos devem fornecer valor aos clientes e integrar-se à plataforma de alguma forma além da autenticação. - Os aplicativos devem estar disponíveis publicamente em {% data variables.product.prodname_marketplace %} e não podem estar na versão beta ou disponíveis apenas por convite. -- Os aplicativos não podem persuadir ativamente os usuários ativamente para sair do {% data variables.product.product_name %}. -- Os materiais de marketing do aplicativo devem representar com precisão o comportamento do aplicativo. -- Os aplicativos devem incluir links para a documentação do usuário que descreve como configurá-lo e usá-lo. -- Quando um cliente compra um aplicativo e o GitHub o redireciona para o URL de instalação do aplicativo, o aplicativo deverá iniciar o fluxo do OAuth imediatamente. Para obter mais informações, consulte "[Gerenciando novas compras e testes grátis](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/#step-3-authorization)". +- Os aplicativos devem ter eventos webhook configurados para notificar o editor de qualquer alteração do plano ou cancelamentos usando a API de {% data variables.product.prodname_marketplace %} Para obter mais informações, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". -- Os clientes devem ser capazes de instalar seu app e selecionar repositórios em uma conta pessoal e de organização. Eles devem ser capazes de visualizar e gerenciar essas contas separadamente. +Para obter mais informações sobre como fornecer uma boa experiência com o cliente, consulte "[As práticas recomendadas com o cliente para aplicativos](/developers/github-marketplace/customer-experience-best-practices-for-apps)". -### Marca e listagem +#### Requisitos da marca e anúncios para todos os aplicativos -- Os aplicativos que usam logotipos do GitHub devem seguir as diretrizes de "[{% data variables.product.product_name %} Logotipos e Uso](https://github.com/logos)". +- Os aplicativos que usam logotipos do GitHub precisam seguir as diretrizes de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Logos e uso de {% data variables.product.company_short %}](https://github.com/logos)". - Os aplicativos devem ter um logotipo, cartões de recurso, e imagens de captura de tela que atendam às recomendações fornecidas em "[Escrevendo descrições da listagem de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". - As listagens devem incluir descrições bem escritas e sem erros gramaticais. Para obter orientação par escrever a sua listagem, consulte "[Escrevendo descrições de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". -### Segurança +Para proteger seus clientes, recomendamos que siga as práticas recomendadas em matéria de segurança. Para obter mais informações, consulte "[as práticas recomendadas de segurança para os aplicativos](/developers/github-marketplace/security-best-practices-for-apps)". -Os aplicativos passarão por uma revisão de segurança antes de serem listados em {% data variables.product.prodname_marketplace %}. Uma revisão bem-sucedida atenderá aos requisitos e seguirá as práticas recomendadas de segurança listadas no[processo de revisão de segurança](/marketplace/getting-started/security-review-process/)". Para obter informações sobre o processo de revisão, entre em contato com [marketplace@github.com](mailto:marketplace@github.com). +### Considerações para aplicativos gratuitos -### Fluxos de cobrança +{% data reusables.marketplace.free-apps-encouraged %} -Seu aplicativo deve integrar-se aos [os fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows), usando o [evento de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). +### Requisitos para aplicativos pagos -#### Aplicativos grátis +Além dos requisitos para todos os aplicativos acima, cada aplicativo que você oferece como serviço pago em {% data variables.product.prodname_marketplace %} também deve atender aos seguintes requisitos: -{% data reusables.marketplace.free-apps-encouraged %} Se você estiver listando um aplicativo grátis, você deverá atender a estes requisitos: +- Os {% data variables.product.prodname_github_app %}s deve ter, no mínimo, 100 instalações. +- Os {% data variables.product.prodname_oauth_app %}s devem ter, no mínimo, 200 usuários. +- Todos os aplicativos pagos devem lidar com eventos de compra de {% data variables.product.prodname_marketplace %} para novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter mais informações, consulte "[Requisitos de cobrança para aplicativos pagos](#billing-requirements-for-paid-apps)" abaixo. +- As organizações publicadoras devem ter um domínio verificado e devem habilitar a autenticação de dois fatores. 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.") -- Os clientes devem ser capazes de ver que eles têm um plano grátis seção de cobrança, perfil ou configurações de conta do aplicativo. -- Quando um cliente cancelar seu aplicativo, você deverá seguir o fluxo para [cancelar planos](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/). +Quando estiver pronto para publicar o aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar a verificação para o anúncio. -#### Aplicativos pagos +{% note %} -Para oferecer seu aplicativo como um serviço pago, você precisará atender a estes requisitos para listar seu aplicativo em {% data variables.product.prodname_marketplace %}: +O processo de verificação está aberto às organizações. {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como fazer isso, consulte: "[Enviar o seu anúncio para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". + +{% endnote %} + +### Requisitos de cobrança para aplicativos pagos + +Seu aplicativo não precisa gerenciar pagamentos, mas precisa usar eventos de compra de {% data variables.product.prodname_marketplace %} para gerenciar novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter informações sobre como integrar esses eventos no seu aplicativo, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +Usar a API de cobrança do GitHub permite aos clientes comprar um aplicativo sem sair do GitHub e pagar o serviço com o método de pagamento já anexado à sua conta em {% data variables.product.product_name %} -- Para vender seu aplicativo em {% data variables.product.prodname_marketplace %}, ele deverá usar o sistema de cobrança do GitHub. Seu aplicativo não precisa gerenciar pagamentos, mas deve usar "[ eventos de compra de {% data variables.product.prodname_marketplace %} ](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)para gerenciar novas compras, atualizações, downgrades, cancelamentos e testes grátis. Consulte "[Fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)para saber mais sobre como integrar esses eventos ao seu aplicativo. Usar o sistema de cobrança do GitHub permite aos clientes comprar um aplicativo sem sair do GitHub e pagar pelo serviço com o método de pagamento já anexado à sua conta {% data variables.product.product_name %}. - Os aplicativos devem ser compatíveis tanto com a cobrança anual quanto mensal para as compras de suas assinaturas pagas. - As listagens podem oferecer qualquer combinação de planos grátis e pagos. Os planos grátis são opcionais, porém incentivados. Para obter mais informações, consulte "[Definir um plano de preços da listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". -{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/pt-BR/content/developers/github-marketplace/security-best-practices-for-apps.md b/translations/pt-BR/content/developers/github-marketplace/security-best-practices-for-apps.md new file mode 100644 index 0000000000..2e3414d91f --- /dev/null +++ b/translations/pt-BR/content/developers/github-marketplace/security-best-practices-for-apps.md @@ -0,0 +1,59 @@ +--- +title: Práticas de segurança recomendadas para aplicativos +intro: 'Diretrizes para a preparação de um aplicativo seguro para compartilhar em {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/marketplace/getting-started/security-review-process/ + - /marketplace/getting-started/security-review-process + - /developers/github-marketplace/security-review-process-for-submitted-apps +shortTitle: Práticas recomendadas de segurança +versions: + free-pro-team: '*' +--- + +Se você seguir estas práticas recomendadas, elas ajudarão você a oferecer uma experiência de usuário segura. + +### Autorização, autenticação e controle de acesso + +Recomendamos criar um aplicativo GitHub em vez de um aplicativo OAuth. {% data reusables.marketplace.github_apps_preferred %}. Consulte "[Diferenças entre os aplicativos GitHub e os aplicativos OAuth](/apps/differences-between-apps/)" para obter mais informações. +- Os aplicativos devem usar o princípio do menor privilégio e devem solicitar apenas os escopos do OAuth e as permissões do aplicativo GitHub de que o aplicativo precisa para realizar suas funcionalidades pretendidas. Para obter mais informações, consulte [O princípio do menor privilégio](https://en.wikipedia.org/wiki/Principle_of_least_privilege) na Wikipédia. +- Os aplicativos devem fornecer aos clientes uma forma de excluir sua conta, sem ter de enviar um e-mail ou ligar para uma pessoa de suporte. +- Os aplicativos não devem compartilhar tokens entre diferentes implementações do aplicativo. Por exemplo, um aplicativo para computador deve ter um token separado de um aplicativo baseado na web. Os tokens individuais permitem que cada aplicativo solicite o acesso necessário aos recursos do GitHub separadamente. +- Crie seu aplicativo com diferentes funções de usuário, dependendo da funcionalidade necessária para cada tipo de usuário. Por exemplo, um usuário-padrão não deve ter acesso à funcionalidade de administração, e os gerentes de cobrança podem não precisar de acesso push ao código de repositório. +- Os aplicativos não devem compartilhar contas de serviço como, por exemplo, e-mail ou serviços de banco de dados para gerenciar seu serviço de SaaS. +- Todos os serviços usados no seu aplicativo devem ter credenciais de login e senha exclusivas. +- O acesso privilegiado de administrador à infraestrutura de hospedagem de produção deve ser concedido apenas a engenheiros e funcionários com funções administrativas. +- Os aplicativos não devem usar tokens de acesso pessoal para efetuar a autenticação e devem autenticar-se como um [aplicativo OAuth](/apps/about-apps/#about-oauth-apps) ou um [aplicativo GitHub](/apps/about-apps/#about-github-apps): + - Os aplicativos OAuth devem efetuar a autenticação usando um [token do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). + - Os aplicativos GitHub devem efetuar a autenticação usando um [Token web do JSON (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app),, [Token do OAuth](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) ou um [token de acesso à instalação](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). + +### Proteção de dados + +- Os aplicativos devem criptografar dados transferidos para internet pública usando HTTPS, com um certificado TLS válido ou SSH para o Git. +- Os aplicativos devem armazenar com segurança o ID do cliente e as chaves secretas do cliente. Recomendamos armazená-las como [variáveis de ambiente](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). +- Os aplicativos devem excluir todos os dados do usuário no prazo de 30 dias após receber uma solicitação do usuário ou dentro de 30 dias após o fim da relação jurídica do usuário com o GitHub. +- Aplicativos não devem exigir que o usuário forneça sua senha do GitHub. +- Os aplicativos devem criptografar tokens, IDs de clientes e segredos de clientes. + +### Registro e monitoramento + +Os aplicativos devem ter capacidade de registro e monitoramento. Os registros dos aplicativos devem ser mantidos pelo menos 30 dias e arquivados pelo menos um ano. Um log de segurança deve incluir: + +- Eventos de autenticação e autorização +- Alterações na configuração do serviço +- Leitura e gravação de objetos +- Todas as alterações de permissão do usuário e de grupo +- Elevação do papel para administrador +- Marca de tempo consistente para cada evento +- Usuários de origem, endereços IP e/ou nomes de host para todas as ações registradas + +### Fluxo de trabalho de resposta a incidente + +Para oferecer uma experiência segura aos usuários, você deve ter um plano de resposta de incidente claro em vigor antes de anunciar o seu aplicativo. Recomendamos ter uma equipe de resposta a incidentes de segurança e operações na sua empresa, em vez de usar um fornecedor terceiro. Você deve ter a capacidade de notificar {% data variables.product.product_name %} no prazo de 24 horas após a confirmação de um incidente. + +Para obter um exemplo de um fluxo de trabalho de resposta de incidente, consulte a "Política de Resposta de Violação de Dados" no [site do Instituto SANS](https://www.sans.org/information-security-policy/). Um documento breve com medidas claras a serem tomadas em caso de incidente é mais valioso do que um modelo político moroso. + +### Gerenciamento de vulnerabilidades e fluxo de trabalho de patch + +Você deveria realizar varreduras regulares de vulnerabilidades de infraestrutura de produção. Você deve classificar os resultados de verificações de vulnerabilidades e definir um período de tempo no qual você concorda em remediar a vulnerabilidade. + +Se você não estiver pronto para criar um programa completo de gerenciamento de vulnerabilidades, é importante começar criando um processo de patching. Para obter orientações sobre a criação de uma política de gerenciamento de correções, consulte este artigo da TechRepublic "[Estabeleça uma política de gerenciamento de patch](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)". diff --git a/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 5bd13f807f..5c5ade3356 100644 --- a/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/pt-BR/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Definir planos de cobrança para sua listagem -intro: 'Ao [listar seu aplicativo no {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/), você poderá optar por fornecer seu aplicativo como um serviço grátis ou vender seu aplicativo. Se você pretende vender seu aplicativo, você pode criar planos de preços diferentes para diferentes níveis de recursos.' +intro: 'Quando você listar seu aplicativo em {% data variables.product.prodname_marketplace %}, você poderá escolher fornecer seu aplicativo como um serviço grátis ou vender seu aplicativo. Se você pretende vender seu aplicativo, você pode criar planos de preços diferentes para diferentes níveis de recursos.' redirect_from: - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ @@ -17,57 +17,52 @@ versions: free-pro-team: '*' --- +### Sobre a configuração dos planos de preços +Se desejar vender um aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar verificação ao publicar o anúncio do seu aplicativo. Durante o processo de verificação, um especialista em integração verifica as configurações de identidade e segurança da organização. O especialista em integração fará com que a organização passe pela integração financeira. Para mais informações, consulte: "[Requisitos para anunciar um aplicativo em {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como fazer isso, consulte: "[Enviar o seu anúncio para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". + +{% data variables.product.prodname_marketplace %} oferece vários tipos diferentes de plano de preços. Para obter informações detalhadas, consulte "[Planos de preços para {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)". + +### Sobre como salvar planos de preços + +Você pode salvar planos de preços com status de rascunho ou publicado. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Depois de publicar um plano de preços em um anúncio publicado, os clientes poderão comprar imediatamente. Você pode publicar até 10 planos de preços. + +Para obter diretrizes sobre os clientes de cobrança, consulte "[Clientes de cobrança](/developers/github-marketplace/billing-customers)". ### Criar planos de preços -Para saber mais sobre os tipos de planos de preços que o {% data variables.product.prodname_marketplace %} oferece, consulte "[ planos de preços do {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/github-marketplace-pricing-plans/)". Você também encontrará as diretrizes úteis de cobrança em "[Vender seu aplicativo](/marketplace/selling-your-app/)". - -Os planos de preços podem ter status de rascunho ou publicado. Se você não enviou sua listagem do {% data variables.product.prodname_marketplace %} para aprovação, uma listagem publicada funcionará da mesma forma que as listagens de rascunho até que seu aplicativo seja aprovado e listado no {% data variables.product.prodname_marketplace %}. As listagens em rascunho permitem que você crie e salve novos planos de preços sem disponibiliz-alos na sua página de listagem do {% data variables.product.prodname_marketplace %}. Após publicar o plano de preços, ele será disponibilizado aos clientes para compra imediata. Você pode publicar até 10 planos de preços. - -Para criar um plano de preços para a sua listagem do {% data variables.product.prodname_marketplace %}, clique em **Planos e preços** na barra lateral esquerda da sua [página de listagem do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Se você ainda não criou uma listagem do {% data variables.product.prodname_marketplace %}, leia "[Criar uma listagem em rascunho do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" para aprender como fazê-lo. +Para criar um plano de preços para a sua listagem do {% data variables.product.prodname_marketplace %}, clique em **Planos e preços** na barra lateral esquerda da sua [página de listagem do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Para obter mais informações, consulte "[Criar um rascunho de anúncio de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)." Ao clicar em **Novo rascunho do plano**, você verá um formulário que permite que você personalize o seu plano de preços. Você precisará configurar os seguintes campos para criar um plano de preços: -#### Nome do plano +- **Nome do plano** - O nome do seu plano de preços aparecerá na página inicial do aplicativo de {% data variables.product.prodname_marketplace %}. Você pode personalizar o nome do seu plano de preços para se alinhar com os recursos do plano, o tamanho da empresa que usará o plano ou qualquer coisa que desejar. -O nome do seu plano de preços aparecerá na página inicial do seu aplicativo do {% data variables.product.prodname_marketplace %}. Você pode personalizar o nome do seu plano de preços para alinhar-se aos recursos do plano, ao tamanho da empresa que usará o plano ou qualquer coisa que desejar. +- **Modelos de preços** - Existem três tipos de plano de preços: gratuito, taxa fixa e por unidade. Todos os planos exigem que você processe novos eventos de compra e cancelamento da API do marketplace. Além disso, para os planos pagos: -#### Modelos de preços + - Você deve definir um preço para as assinaturas mensais e anuais em dólar. + - Seu aplicativo deve processar eventos de mudança de plano. + - Você deve solicitar verificação para publicar um anúncio com um plano pago. + - {% data reusables.marketplace.marketplace-pricing-free-trials %} -##### Planos grátis + For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.free-apps-encouraged %} Um plano grátis ainda exigue que você gerencie os fuxos de cobrança da [nova compra](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/) e do [cancelamento](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/). Consulte "[Fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" para obter mais informações. +- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. Por exemplo, se o seu plano de preços for por unidade e fornecer várias estações, você selecionaria **apenas contas de organização**, porque não há nenhuma maneira de atribuir estações a pessoas de uma organização a partir de uma conta pessoal. -##### Planos de preços fixos +- **Short description** - Write a brief summary of the details of the pricing plan. A descrição pode incluir o tipo de cliente para o qual o plano se destina ou os recursos que o plano inclui. -Os planos de preços fixos permitem que você ofereça seu serviço aos clientes a uma taxa fixa. {% data reusables.marketplace.marketplace-pricing-free-trials %} +- **Bullets** - You can write up to four bullets that include more details about your pricing plan. Os marcadores podem incluir casos de uso do seu aplicativo ou listar informações mais detalhadas sobre as características ou os recursos incluídos no plano. -Você deve definir um preço para as assinaturas mental e anual emS. dólar para os planos de preços fixos. - -##### Planos por unidade - -Os preços por unidade permite que você ofereça seu aplicativo em unidades. Por exemplo, uma unidade pode ser uma pessoa, estação ou usuário. Você precisará fornecer um nome para a unidade e definir um preço para assinaturas mental e anual em dólar. Dólar. - -#### Disponível para - -Os planos de preços do {% data variables.product.prodname_marketplace %} podem ser aplicados às **contas pessoais e de organizações**, **apenas às contas pessoais**, ou **apenas às contas de organizações**. Por exemplo, se o seu plano de preços for por unidade e fornecer várias estações, você selecionaria **apenas contas de organização**, porque não há nenhuma maneira de atribuir estações a pessoas de uma organização a partir de uma conta pessoal. - -#### Descrição curta - -Escreva um breve resumo das informações do plano de preços. A descrição pode incluir o tipo de cliente para o qual o plano se destina ou os recursos que o plano inclui. - -#### Marcadores - -Você pode escrever até quatro marcadores que incluem mais informações sobre seu plano de preços. Os marcadores podem incluir casos de uso do seu aplicativo ou listar informações mais detalhadas sobre as características ou os recursos incluídos no plano. +{% data reusables.marketplace.free-plan-note %} ### Alterar um plano de preços da listagem do {% data variables.product.prodname_marketplace %} -Se um plano de preços para seu plano do {% data variables.product.prodname_marketplace %} não for mais necessário ou se você precisar ajustar as informações de preço, será possível removê-lo. +If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it. ![Botão para remover o seu plano de preços](/assets/images/marketplace/marketplace_remove_this_plan.png) -Após publicar um plano de preços para um aplicativo já listado no {% data variables.product.prodname_marketplace %}, não será possível fazer alterações no plano. Em vez disso, você deverá remover o plano de preços. Os clientes que já compraram o plano de preços removido continuarão a usá-lo até que optem por sair o plano e passar para um novo plano de preços. Para obter mais informações sobre os planos de preços, consulte[ planos de preços do {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/github-marketplace-pricing-plans/)". +Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Em vez disso, você precisará remover o plano de preços e criar um novo plano. Os clientes que já compraram o plano de preços removido continuarão a usá-lo até que optem por sair o plano e passar para um novo plano de preços. Para obter mais informações sobre os planos de preços, consulte[ planos de preços do {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/github-marketplace-pricing-plans/)". Depois de remover um plano de preços, os usuários não poderão comprar seu aplicativo que usa esse plano. Os usuários existentes no plano de preços removido continuarão no plano até que cancelem sua assinatura do plano. diff --git a/translations/pt-BR/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/pt-BR/content/developers/github-marketplace/submitting-your-listing-for-publication.md new file mode 100644 index 0000000000..9cbf359890 --- /dev/null +++ b/translations/pt-BR/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -0,0 +1,37 @@ +--- +title: Enviando seu anúncio para publicação +intro: 'Você pode enviar seu anúncio para a comunidade {% data variables.product.prodname_dotcom %} usar.' +redirect_from: + - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review + - /developers/github-marketplace/submitting-your-listing-for-review +versions: + free-pro-team: '*' +--- + + + +Depois de concluir o anúncio do seu aplicativo, você verá dois botões que permitem que você solicite a publicação do anúncio, com ou sem verificação. O botão **Solicitar** para "Publicar sem verificação" encontra-se desabilitado se você tiver publicado algum plano de preços pago no anúncio. + +![Botão de solicitação verificada e não verificada](/assets/images/marketplace/marketplace-request-button.png) + +{% data reusables.marketplace.launch-with-free %} + +Depois de enviar seu anúncio para revisão, um especialista de integração entrará em contato com você com informações adicionais. + +Para uma visão geral do processo de criação e envio de uma listagem, consulte "[Sobre {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)". + +### Pré-requisitos para publicação com verificação + +Before you request verification of your listing, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your app. Para obter mais informações, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + +Se você cumpriu os requisitos para o anúncio integrou-se à API de {% data variables.product.prodname_marketplace %}, envie o seu anúncio. Para obter mais informações, consulte "[Requisitos para listar um app](/developers/github-marketplace/requirements-for-listing-an-app)". + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} Para informações sobre como fazer isso, consulte: "[Transferir um aplicativo para uma organização antes de enviar](#transferring-an-app-to-an-organization-before-you-submit)" abaixo. + +### Transferring an app to an organization before you submit + +You cannot sell an app that's owned by a user account. You need to transfer the app to an organization that is already a verified creator, or that can request verification for a listing for the app. For details, see: + +1. "[Creating an organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" + +1. "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" diff --git a/translations/pt-BR/content/developers/github-marketplace/testing-your-app.md b/translations/pt-BR/content/developers/github-marketplace/testing-your-app.md index 643eff4c24..0a809eb43f 100644 --- a/translations/pt-BR/content/developers/github-marketplace/testing-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/testing-your-app.md @@ -1,6 +1,6 @@ --- title: Testar seu aplicativo -intro: 'O GitHub recomenda testar seu aplicativo com APIs e webhooks antes de enviar sua listagem para o {% data variables.product.prodname_marketplace %}, para que você possa oferecer uma experiência ideal para os clientes. Antes de a equipe de integração do {% data variables.product.prodname_marketplace %} aprovar seu aplicativo, ele deve gerenciar, de modo adequado, os [fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows).' +intro: 'O GitHub recomenda testar seu aplicativo com APIs e webhooks antes de enviar sua listagem para o {% data variables.product.prodname_marketplace %}, para que você possa oferecer uma experiência ideal para os clientes. Antes que um especialista em integração aprove seu aplicativo, ele deverá tratar adequadamente os fluxos de cobrança.' redirect_from: - /apps/marketplace/testing-apps-apis-and-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ @@ -13,7 +13,7 @@ versions: ### Testar aplicativos -Você pode usar uma [listagem de rascunho do {% data variables.product.prodname_marketplace %} ](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) para simular cada um dos [fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows). Uma listagem com status de rascunho significa que não foi enviada à aprovação. Qualquer compra que você fizer usando uma listagem de rascunho do {% data variables.product.prodname_marketplace %} _não criará_ transações reais e o GitHub não efetuará nenhuma cobrança no seu cartão de crédito. +Você pode usar um rascunho de anúncio de {% data variables.product.prodname_marketplace %} para simular cada um dos fluxos de cobrança. Uma listagem com status de rascunho significa que não foi enviada à aprovação. Qualquer compra que você fizer usando uma listagem de rascunho do {% data variables.product.prodname_marketplace %} _não criará_ transações reais e o GitHub não efetuará nenhuma cobrança no seu cartão de crédito. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." #### Usar um aplicativo de desenvolvimento com uma listagem de rascunho para testar alterações diff --git a/translations/pt-BR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/pt-BR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index db521efa27..fd247c6122 100644 --- a/translations/pt-BR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/pt-BR/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -1,6 +1,6 @@ --- title: Eventos do Webhook para a API do GitHub Marketplace -intro: 'Um aplicativo do {% data variables.product.prodname_marketplace %} recebe informações sobre mudanças no plano de um usuário no webhook do evento de compra no Marketplace. Um evento de compra no Marketplace é acionado quando um usuário compra, cancela ou muda seu plano de pagamento. Para obter informações sobre como responder a cada um desses tipos de eventos, consulte "[fluxos de cobrança](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)".' +intro: 'Um aplicativo do {% data variables.product.prodname_marketplace %} recebe informações sobre mudanças no plano de um usuário no webhook do evento de compra no Marketplace. Um evento de compra no Marketplace é acionado quando um usuário compra, cancela ou muda seu plano de pagamento.' redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ diff --git a/translations/pt-BR/content/developers/overview/about-githubs-apis.md b/translations/pt-BR/content/developers/overview/about-githubs-apis.md index a8a337a2a7..19ff45086d 100644 --- a/translations/pt-BR/content/developers/overview/about-githubs-apis.md +++ b/translations/pt-BR/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,7 @@ versions: github-ae: '*' --- -Existem duas versões estáveis da API do GitHub: a [API REST](/rest) e a [API do GraphQL](/graphql). - -Ao usar a API REST, incentivamos que você a [solicite a v3 por meio do cabeçalho `Aceitar`](/rest/overview/media-types#request-specific-version). - -Para obter informações sobre como usar a API do GraphQL, consulte a [documentação da v4](/graphql). +Existem duas versões estáveis da API do GitHub: a [API REST](/rest) e a [API do GraphQL](/graphql). Ao usar a API REST, incentivamos que você a [solicite a v3 por meio do cabeçalho `Aceitar`](/v3/media/#request-specific-version). Para obter informações sobre como usar a API do GraphQL, consulte a [documentação da v4](/graphql). ## Versões obsoletas diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhook-events-and-payloads.md index f48511fa62..ca9d95fbef 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 @@ -145,7 +145,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {{ webhookPayloadsForCurrentVersion.check_suite.completed }} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### code_scanning_alert {% data reusables.webhooks.code_scanning_alert_event_short_desc %} @@ -445,7 +445,7 @@ Key | Type | Description #### Webhook payload object {% data reusables.webhooks.installation_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Webhook payload example @@ -469,7 +469,7 @@ Key | Type | Description #### Webhook payload object {% data reusables.webhooks.installation_repositories_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Webhook payload example @@ -1046,7 +1046,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends Key | Type | Description ----|------|------------- -`action` |`string` | The action that was performed. This can be one of:
      • `created` - A repository is created.
      • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
      • `archived` - A repository is archived.
      • `unarchived` - A repository is unarchived.
        • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
      • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
        • {% endif %}
      • `edited` - A repository's information is edited.
      • `renamed` - A repository is renamed.
      • `transferred` - A repository is transferred.
      • `publicized` - A repository is made public.
      • `privatized` - A repository is made private.
      +`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.
      {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1099,6 +1099,31 @@ Key | Type | Description {% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### secret_scanning_alert + +{% data reusables.webhooks.secret_scanning_alert_event_short_desc %} + +#### Availability + +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `secret_scanning_alerts:read` permission + +#### Webhook payload object + +{% 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. + +#### Webhook payload example + +{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} +{% endif %} + ### 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/)." 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 new file mode 100644 index 0000000000..c9f15039a8 --- /dev/null +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -0,0 +1,54 @@ +--- +title: Sobre discussões +intro: Use discussões para fazer e responder perguntas, compartilhar informações, fazer anúncios e conduzir ou participar de uma conversa sobre um projeto em {% data variables.product.product_name %}. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Sobre discussões + +Com {% data variables.product.prodname_discussions %}, a comunidade para o seu projeto pode criar e participar de conversas no repositório do projeto. As discussões capacitam os mantenedores, contribuidores e visitantes para reunirem e atingirem os objetivos seguintes em um local central, sem ferramentas de terceiros. + +- Compartilhar anúncios e informações, recolher feedback, planejar e tomar decisões +- Faça perguntas, discuta e responda às perguntas, e marque as discussões como respondidas +- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows + +![Discussions tab for a repository](/assets/images/help/discussions/hero.png) + +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. 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)". + +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)." + +### About categories and formats for discussions + +{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %} + +For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %} + +For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +### Best practices for discussions + +As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)." + +Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." + +### Compartilhando feedback + +You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). + +### Leia mais + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" +- "[Moderar comentários e conversas](/github/building-a-strong-community/moderating-comments-and-conversations)" +- "[Mantendo sua segurança no {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md new file mode 100644 index 0000000000..828f2145e1 --- /dev/null +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -0,0 +1,48 @@ +--- +title: Collaborating with maintainers using discussions +shortTitle: Collaborating with maintainers +intro: You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion. +permissions: People with read permissions to a repository can start and participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About collaboration with maintainers using discussions + +{% data reusables.discussions.about-discussions %} If you use or contribute to a project, you can start a discussion to make suggestions and engage with maintainers and community members about your plans, questions, ideas, and feedback. For more information, see "[‎About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +{% data reusables.discussions.about-categories-and-formats %} Repository administrators and project maintainers can delete a discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)." + +{% data reusables.discussions.github-recognizes-members %} These members appear in a list of the most helpful contributors to the project's discussions. As your project grows, you can grant higher access permissions to active members of your community. For more information, see "[Granting higher permissions to top contributors](/discussions/guides/granting-higher-permissions-to-top-contributors)" + +![Most helpful contributors to discussions for a project](/assets/images/help/discussions/most-helpful.png) + +For more information about participation in discussions, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +### Pré-requisitos + +To collaborate with maintainers using discussions, a repository administrator or project maintainer must enable discussions for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Starting a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Filtering the list of discussions + +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the **Search all discussions** field, type a search query. Optionally, to the right of the search field, click a button to further filter the results. ![Search bar and buttons for filtering discussions](/assets/images/help/discussions/search-and-filter-controls.png) +1. In the list of discussions, click the discussion you want to view. ![Discussion search results](/assets/images/help/discussions/search-result.png) + +### Converting an issue to a discussion + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)." + +### Leia mais + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Mantendo sua segurança no {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/index.md new file mode 100644 index 0000000000..44aed03c8b --- /dev/null +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/index.md @@ -0,0 +1,14 @@ +--- +title: Collaborating with your community using discussions +shortTitle: Collaborating using discussions +intro: Gather and discuss your project with community members and other maintainers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /about-discussions %} +{% link_in_list /participating-in-a-discussion %} +{% link_in_list /collaborating-with-maintainers-using-discussions %} + diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md new file mode 100644 index 0000000000..64de4a5496 --- /dev/null +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -0,0 +1,31 @@ +--- +title: Participating in a discussion +intro: You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}. +permissions: People with read permissions to a repository can participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About participation in a discussion + +{% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)." + +You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)." + +### Pré-requisitos + +Discussions must be enabled for the repository for you to participate in a discussion in the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Creating a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Marking a comment as an answer + +Discussion authors and users with the triage role or greater for a repository can mark a comment as the answer to a discussion in the repository. + +{% data reusables.discussions.marking-a-comment-as-an-answer %} 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 new file mode 100644 index 0000000000..60b8e1ce37 --- /dev/null +++ b/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -0,0 +1,49 @@ +--- +title: Best practices for community conversations on GitHub +shortTitle: Best practices for community conversations +intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to a discussion when you are ready to scope out the work.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Community conversations in {% data variables.product.prodname_discussions %} + +Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository and gather diverse feedback and ideas more quickly. You can help drive a productive conversation by: + +- Asking pointed questions and follow-up questions to garner specific feedback +- Capture a diverse experience and distill it down to main points +- Open an issue to take action based on the conversation, where applicable + +For more information about opening an issue and cross-referencing a discussion, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." + +### Learning about conversations on GitHub + +You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have. + +You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and spike out a project's specific details before committing it to an issue, which can then be scoped. Discussions are useful for teams if: +- You are in the discovery phase of a project and are still learning which director your team wants to go in +- You want to collect feedback from a wider community about a project +- You want to keep bug fixes, feature requests, and general conversations separate + +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](/articles/about-team-discussions)." + +### Following contributing guidelines + +Before you open a discussion, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project. + +Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Próximas etapas + +To continue learning about {% data variables.product.prodname_discussions %} and quickly create a discussion for your community, see "[Quickstart for {% data variables.product.prodname_discussions %}](/discussions/quickstart)." + +### Leia mais + +- "[Configurar seu projeto para contribuições úteis](/articles/setting-up-your-project-for-healthy-contributions)" +- "[Usando modelos para encorajar problemas úteis e pull requests](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Moderar comentários e conversas](/articles/moderating-comments-and-conversations)" +- "[Gravar no {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)" diff --git a/translations/pt-BR/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/pt-BR/content/discussions/guides/finding-discussions-across-multiple-repositories.md new file mode 100644 index 0000000000..418407746c --- /dev/null +++ b/translations/pt-BR/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -0,0 +1,20 @@ +--- +title: Finding discussions across multiple repositories +intro: 'You can easily access every discussion you''ve created or participated in across multiple repositories.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Finding discussions + +1. Navegue até o {% data variables.product.prodname_dotcom_the_website %}. +1. In the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your discussions**. !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. + +### Leia mais + +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" 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 new file mode 100644 index 0000000000..4b9119fee2 --- /dev/null +++ b/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -0,0 +1,32 @@ +--- +title: Granting higher permissions to top contributors +intro: 'Repository administrators can promote any community member to a moderator and maintainer.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Introdução + +The most helpful contributors for the past 30 days are highlighted on the {% data variables.product.prodname_discussions %} dashboard, based on how many comments were marked as answers by other community members. Helpful contributors can help drive a healthy community and moderate and guide the community space in addition to maintainers. + +### Step 1: Audit your discussions top contributors + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Compare the list of contributors with their access permissions to see who qualifies to moderate the discussion. + +### Step 2: Review permission levels for discussions + +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)." + +### Step 3: Change permissions levels for top contributors + +You can change a contributor's permission levels to give them more access to the tooling they need to moderate GitHub Discussions. To change a person's or team's permission levels, see "[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)." + +### Step 4: Notify community members of elevated access + +When you change a collaborators permission level, they will receive a notification for the change. diff --git a/translations/pt-BR/content/discussions/guides/index.md b/translations/pt-BR/content/discussions/guides/index.md new file mode 100644 index 0000000000..287d26a1e8 --- /dev/null +++ b/translations/pt-BR/content/discussions/guides/index.md @@ -0,0 +1,31 @@ +--- +title: Discussions guides +shortTitle: Guias +intro: 'Discover pathways to get started or learn best practices for participating or monitoring your community''s discussions.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Getting started with discussions + +{% link_in_list /about-discussions %} +{% link_in_list /best-practices-for-community-conversations-on-github %} +{% link_in_list /finding-discussions-across-multiple-repositories %} + +### Administering discussions + +{% link_in_list /granting-higher-permissions-to-top-contributors %} + + + + + diff --git a/translations/pt-BR/content/discussions/index.md b/translations/pt-BR/content/discussions/index.md new file mode 100644 index 0000000000..9925db4e08 --- /dev/null +++ b/translations/pt-BR/content/discussions/index.md @@ -0,0 +1,55 @@ +--- +title: GitHub Discussions Documentation +beta_product: true +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.' +introLinks: + quickstart: /discussions/quickstart +featuredLinks: + guides: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + gettingStarted: + - /discussions/quickstart + guideCards: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + popular: + - /discussions/guides/granting-higher-permissions-to-top-contributors + - /discussions/guides/best-practices-for-community-conversations-on-github + - /discussions/guides/finding-discussions-across-multiple-repositories + - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions + - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository +product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +layout: product-landing +versions: + free-pro-team: '*' +--- + + + + + + + +{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} +{% if discussionsCommunityExamples %} +
      +

      Communities using discussions

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

      Desculpe, não há resultados para

      +

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

      + Add your community {% octicon "arrow-right" %} +
      +
      +{% endif %} diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/index.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/index.md new file mode 100644 index 0000000000..8ccb2875b2 --- /dev/null +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/index.md @@ -0,0 +1,13 @@ +--- +title: Managing discussions for your community +shortTitle: Managing discussions +intro: 'You can enable and configure discussions for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /managing-discussions-in-your-repository %} +{% link_in_list /managing-categories-for-discussions-in-your-repository %} +{% link_in_list /moderating-discussions %} diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md new file mode 100644 index 0000000000..39ced19889 --- /dev/null +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md @@ -0,0 +1,56 @@ +--- +title: Managing categories for discussions in your repository +intro: You can categorize the discussions in your repository to organize conversations for your community members, and you can choose a format for each category. +permissions: Repository administrators and people with write or greater access to a repository can enable discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About categories for discussions + +{% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} + +Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations.{% data reusables.discussions.repository-category-limit %} + +For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +### Default categories + +| Categoria | Purpose | Tipo | +|:--------------- |:-------------------------------------------------------------------- |:--------------------- | +| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion | +| 💡Ideas | Ideas to change or improve the project | Open-ended discussion | +| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer | +| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion | + +### Creating a category + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.edit-categories %} +1. Click **New category**. !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png) +1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png) +1. Clique em **Criar**. !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png) + +### Editing a category + +You can edit a category to change the category's emoji, title, description, and discussion format. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} +![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png) +1. Clique em **Save changes** (Salvar alterações). !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +### Deleting a category + +When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png) +1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png) +1. Click **Delete & Move**. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png) 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 new file mode 100644 index 0000000000..5332fb0598 --- /dev/null +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -0,0 +1,94 @@ +--- +title: Managing discussions in your repository +intro: You can categorize, spotlight, transfer, or delete the discussions in a repository. +permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About management of discussions + +{% 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)." + +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](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)." + +For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/github/building-a-strong-community/moderating-comments-and-conversations)." + +### Pré-requisitos + +To manage discussions in a repository, discussions must be enabled for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Changing the category for a discussion + +You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" article. + +You can also move a discussion to a different category. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) + +### Pinning a discussion + +You can pin up to four important discussions above the list of discussions for the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png) +1. Optionally, customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Editing a pinned discussion + +Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Unpinning a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) +1. Read the warning, then click **Unpin discussion**. !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png) + +### Transferring a discussion + +To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png) +1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Click **Transfer discussion**. !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png) + +### Deleting a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png) +1. Read the warning, then click **Delete this discussion**. !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) + +### Converting issues based on labels + +You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Next to the label you want to convert to issues, click **Convert issues**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md new file mode 100644 index 0000000000..2c91d32d89 --- /dev/null +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -0,0 +1,39 @@ +--- +title: Moderating discussions +intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, and converting issues to discussions. and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct to discussions.' +permissions: People with triage access to a repository can moderate discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About moderating discussions + +{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you 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. + +### Marking a comment as an answer + +{% data reusables.discussions.marking-a-comment-as-an-answer %} + +### Locking discussions + +It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository will still be able to comment on the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the discussion you want to lock. ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the right margin of a discussion, click **Lock conversation**. +1. Read the information about locking conversations and click **Lock conversation on this discussion**. +1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**. + +### Converting an issue to a discussion + +When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository can bulk convert issues based on labels. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to convert. +1. In the right margin of an issue, click **Convert to discussion**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/pt-BR/content/discussions/quickstart.md b/translations/pt-BR/content/discussions/quickstart.md new file mode 100644 index 0000000000..c4c65670c7 --- /dev/null +++ b/translations/pt-BR/content/discussions/quickstart.md @@ -0,0 +1,58 @@ +--- +title: Quickstart for GitHub Discussions +intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository and start conversations with your community.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Introdução + +{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike issues. Discussions enable fluid, open conversation in a public forum. + +Discussions give a space for more collaborative conversations by connecting and giving a more centralized area to connect and find information. + +### Enabling {% data variables.product.prodname_discussions %} on your repository + +Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public repositories. + +When you first enable a {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. + +{% data reusables.repositories.navigate-to-repo %} +1. No nome do seu repositório, clique em {% octicon "gear" aria-label="The gear icon" %} **Configurações**. ![Public settings button](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", click **Set up discussions**. ![Set up a discussion button under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png) +1. Under "Start a new discussion," edit the template to align with the resources and tone you want to set for your community. +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) + +### Welcoming contributions to your discussions + +You can welcome your community and introduce a new way to communicate in a repository by creating a welcome post and pin the post to your {% data variables.product.prodname_discussions %} page. Pinning and locking discussions helps people know that a post is meant as an announcement. You can use announcements as a way to link people to more resources and offer guidance for opening discussions in your community. For more information about pinning a discussion, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + + +### Setting up community guidelines for contributors + +You can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. You can also update the repository's README to communicate expectations on when collaborators should open an issue or discussion. + +For more information about providing guidelines for your project, see "[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and "[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Creating a new discussion + +Anyone with access to a repository can create a discussion. + +{% data reusables.discussions.starting-a-discussion %} + +### Organizing discussions into relevant categories + +Repository owners and people with write access can create new categories to keep discussions organized. Collaborators participating and creating new discussions can group discussions into the most relevant existing categories. Discussions can also be recategorized after they are created. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" + +### Promoting healthy conversations + +People with write permissions for a repository can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +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)." + +### Próximas etapas + +Once there is a clear path to scope work out and move an idea from concept to reality, you can create an issue and start tracking your progress. For more information on creating an issue from a discussion, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." diff --git a/translations/pt-BR/content/education/guides.md b/translations/pt-BR/content/education/guides.md new file mode 100644 index 0000000000..4038560b11 --- /dev/null +++ b/translations/pt-BR/content/education/guides.md @@ -0,0 +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 +versions: + free-pro-team: '*' +--- + +### Get started with {% 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. + +- [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/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) + +### Run a software development course with {% 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 %}. + +- [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) + +### Learn to develop software + +Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. + +- [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/teach-and-learn-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) + +### Contribute to the community + +Participate in the community, get training from {% data variables.product.company_short %}, and learn or teach new skills. + +- [{% data variables.product.prodname_education_community %}](https://education.github.community) +- [Sobre Especialistas de campus](/education/teach-and-learn-with-github-education/about-campus-experts) +- [Sobre Consultores de campus](/education/teach-and-learn-with-github-education/about-campus-advisors) diff --git a/translations/pt-BR/content/education/index.md b/translations/pt-BR/content/education/index.md new file mode 100644 index 0000000000..c3827df288 --- /dev/null +++ b/translations/pt-BR/content/education/index.md @@ -0,0 +1,45 @@ +--- +title: GitHub Education Documentation +shortTitle: Education +intro: "{% data variables.product.prodname_education %} helps you teach or learn software development with the tools and support of {% data variables.product.company_short %}'s platform and community." +introLinks: + quickstart: /education/quickstart +featuredLinks: + guides: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + guideCards: + - /github/getting-started-with-github/signing-up-for-a-new-github-account + - /github/getting-started-with-github/git-and-github-learning-resources + - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom + popular: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /desktop + - /github/getting-started-with-github/github-cli + - /education/manage-coursework-with-github-classroom/teach-with-github-classroom +changelog: + - + title: 'Try something new at Local Hack Day: Learn' + date: '2020-10-15' + href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ + - + title: 'Remote Education: Creating community through shared experiences' + date: '2020-09-24' + href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ + - + title: 'Remote Education: A series of best practices for online campus communities' + date: '2020-09-10' + href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ + - + title: Welcome to the inaugural class of MLH Fellows + date: '2020-06-24' + href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ +layout: product-landing +versions: + free-pro-team: '*' +--- + + + diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md new file mode 100644 index 0000000000..07d4723dfc --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -0,0 +1,31 @@ +--- +title: About using MakeCode Arcade with GitHub Classroom +shortTitle: About using MakeCode Arcade +intro: You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-makecode +--- + +### About MakeCode Arcade + +MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade. + +For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. + +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. + +### About submission of assignments with MakeCode Arcade + +By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.product.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen. + +![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) + +### Leia mais + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md new file mode 100644 index 0000000000..b439d2342f --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: About using Repl.it with GitHub Classroom +shortTitle: About using Repl.it +intro: You can configure Repl.it as the online integrated development environment (IDE) for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-replit +--- + +### About Repl.it + +Repl.it is an online integrated development environment (IDE) that supports multiple programming languages. Students can write, edit, run, test, and debug code in a browser with Repl.it. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. + +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). + +For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. + +### About submission of assignments with Repl.it + +By default, Repl.it is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with Repl.it, students should push changes to {% data variables.product.product_location %} using the version control functionality in the left sidebar. + +![Repl.it version control functionality](/assets/images/help/classroom/ide-replit-version-control-button.png) + +For more information about using Git on Repl.it, see the [Repl.it + Git Tutorial](https://repl.it/talk/learn/Replit-Git-Tutorial/23331) on the Repl.it website. + +### Leia mais + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md new file mode 100644 index 0000000000..73507c7ec0 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: Basics of setting up GitHub Classroom +shortTitle: 'Noções básicas do {% data variables.product.prodname_classroom %}' +intro: Learn how to set up your classroom, manage assignments, and configure time-saving automation. +versions: + free-pro-team: '*' +--- + +### Videos about {% data variables.product.prodname_classroom %} + +You can watch a series of short video tutorials about the configuration and use of {% data variables.product.prodname_classroom %}. To watch all videos as part of a continuous playlist, see the [{% data variables.product.prodname_classroom %} Getting Started Guide](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) on YouTube. + +For more information about terminology for {% data variables.product.prodname_classroom %}, see "[Glossary](/education/manage-coursework-with-github-classroom/glossary)". + +1. Getting started {% octicon "link-external" aria-label="The external link icon" %} +2. Adding your student roster {% octicon "link-external" aria-label="The external link icon" %} +3. Creating assignments + - Creating an assignment using a {% data variables.product.prodname_dotcom %} repository {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Microsoft MakeCode as your online IDE {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Repl.it as your online IDE {% octicon "link-external" aria-label="The external link icon" %} +4. How students complete assignments {% octicon "link-external" aria-label="The external link icon" %} +5. How teachers review assignments {% octicon "link-external" aria-label="The external link icon" %} +6. Creating group assignments {% octicon "link-external" aria-label="The external link icon" %} +7. Next steps to get started {% octicon "link-external" aria-label="The external link icon" %} +8. {% data variables.product.prodname_dotcom %} Teacher Toolbox {% octicon "link-external" aria-label="The external link icon" %} + +### Próximas etapas + +For more information about teaching with {% data variables.product.prodname_classroom %}, see "[Teach with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom)." + +### Leia mais + +- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md new file mode 100644 index 0000000000..b9efc84cc3 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md @@ -0,0 +1,50 @@ +--- +title: Configure default settings for assignment repositories +shortTitle: Configure defaults for assignment repositories +intro: You can use the Probot Settings app to configure the default settings for repositories that {% data variables.product.prodname_classroom %} creates for an assignment. +permissions: Organization owners can configure default settings for assignment repositories by installing a {% data variables.product.prodname_github_app %} for the organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/probot-settings +--- + +### About configuration of defaults for assignment repositories + +{% data variables.product.prodname_classroom %} creates a repository that belongs for each student or team that accepts an assignment. The repository belongs to the organization that you use for {% data variables.product.prodname_classroom %}. Assignment repositories can be empty, or you can use a template repository. For more information, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} + +With the Probot Settings app, you can create a file named _.github/settings.yml_ in a repository that contains a list of settings for the repository, and then install a {% data variables.product.prodname_github_app %} for your organization that automatically applies the settings to the repository. + +You can include _.github/settings.yml_ in a template repository that you use for an assignment in {% data variables.product.prodname_classroom %}. When an individual or team accepts the assignment, {% data variables.product.prodname_classroom %} creates the assignment repository, and the Settings app automatically applies the settings from _.github/settings.yml_. + +Probot is a a project, framework, and collection of free apps to automate {% data variables.product.product_name %}. A Probot app can listen to repository events, like the creation of new commits, comments, and issues, and automatically respond to the event. + +For more information, see the [Probot website](https://probot.github.io) and the [Settings app website](https://probot.github.io/apps/settings/). For more information about {% data variables.product.prodname_github_apps %}, see "[About apps](/developers/apps/about-apps)." + +### Adding the Settings app to your organization + +After you install the Probot Settings app for your organization, the app will apply the settings that you define in _.github/settings.yml_ for any repository in your organization, including new assignment repositories that {% data variables.product.prodname_classroom %} creates. + +1. Navigate to the [Settings app page](https://github.com/apps/settings). +1. Click **Install**, then click the organization that you use for {% data variables.product.prodname_classroom %}. Provide the app full access to all repositories owned by the organization. ![Installing the Probot Settings app](/assets/images/help/classroom/probot-settings.gif) + +### Configuring default settings for an assignment repository + +1. Create a template repository that contains a _.github/settings.yml_ file. For a complete list of settings, see the [README](https://github.com/probot/settings#github-settings) for the `probot/settings` repository. For more information about using a template repository for starter code in {% data variables.product.prodname_classroom %}, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + + {% warning %} + + **Warning:** Do not define `collaborators` in the _.github/settings.yml_ file for your template repository. {% data variables.product.prodname_classroom %} automatically grants teachers and teaching assistants access to assignment repositories. + + {% endwarning %} + +1. Create an assignment using the template repository containing _.github/settings.yml_ as the starter code. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +The Probot Settings app for your organization will now apply the settings you define in _.github/settings.yml_ within the template repository to every assignment repository that {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} creates for a student or team. + +### Leia mais + +- [Probot apps](https://probot.github.io/apps/) +- [Probot documentation](https://probot.github.io/docs/) diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md new file mode 100644 index 0000000000..0c728ce14c --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -0,0 +1,138 @@ +--- +title: Connect a learning management system to GitHub Classroom +intro: You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom + - /education/manage-coursework-with-github-classroom/connect-to-lms + - /education/manage-coursework-with-github-classroom/generate-lms-credentials + - /education/manage-coursework-with-github-classroom/setup-canvas + - /education/manage-coursework-with-github-classroom/setup-generic-lms + - /education/manage-coursework-with-github-classroom/setup-moodle +--- + +### About configuration of your LMS + +You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS. + +### Pré-requisitos + +To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)." + +### Supported LMSes + +{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards. + +- LTI version 1.0 and/or 1.1 +- LTI Names and Roles Provisioning 1.X + +Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website. + +{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. + +- Canvas +- Google Classroom +- Moodle +- Sakai + +Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace + +### Generating configuration credentials for your classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster. + - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)." +1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**. ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. Read about connecting your LMS, then click **Connect to _LMS_**. +1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom. ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png) + +### Configuring a generic LMS + +You must configure the privacy settings for your LMS to allow external tools to receive roster information. + +1. Navigate to your LMS. +1. Configure an external tool. +1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}. + - Consumer key + - Segredo partilhado + - Launch URL (sometimes called "tool URL" or similar) + +### Configuring Canvas + +You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). + +1. Sign into [Canvas](https://www.instructure.com/canvas/#login). +1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}. +1. Na barra lateral esquerda, clique em **Configurações**. +1. Click the **Apps** tab. +1. Click **View app configurations**. +1. Click **+App**. +1. Select the **Configuration Type** drop-down menu, and click **By URL**. +1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Canvas app configuration | Value or setting | + |:------------------------------------------------------------------------- |:------------------------------------------------------------------ | + | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} + | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled | + | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} + + {% note %} + + **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website. + + {% endnote %} + +1. Clique em **Enviar**. +1. In the left sidebar, click **Home**. +1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}. + +### Configuring Moodle + +You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org). + +You must be using Moodle version 3.0 or greater. + +1. Sign into [Moodle](https://moodle.org/login/index.php). +1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}. +1. Click **Turn editing on**. +1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**. +1. Choose **External tool** and click **Add**. +1. In the "Activity name" field, type "GitHub Classroom". +1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**. +1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Moodle app configuration | Value or setting | + |:--------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_

      **Note**: You can use any name, but we suggest this value for clarity. | + | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} + | **LTI version** | LTI 1.0/1.1 | + | **Default launch container** | New window | + | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Segredo partilhado** | Shared secret from {% data variables.product.prodname_classroom %} + +1. Scroll to and click **Services**. +1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**. +1. Scroll to and click **Privacy**. +1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**. +1. Na parte inferior da página, clique em **Save changes** (Salvar alterações). +1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**. +1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**. +1. At the bottom of the page, click **Save and return to course**. +1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity. + +### Importing a roster from your LMS + +For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + +### Disconnecting your LMS + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Connect to a learning management system (LMS)", click **Connection Settings**. !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**. !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) 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 new file mode 100644 index 0000000000..cfc3f79291 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -0,0 +1,145 @@ +--- +title: Create a group assignment +intro: 'You can create a collaborative assignment for teams of students who participate in your course.' +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/create-group-assignments +--- + +### About group assignments + +{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers. + +When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment. + +{% data reusables.classroom.classroom-creates-group-repositories %} + +{% data reusables.classroom.about-assignments %} + +You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Sobre equipes](/github/setting-up-and-managing-organizations-and-teams/about-teams)". + +For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### Pré-requisitos + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Defining teams for an assignment](#defining-teams-for-an-assignment) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +#### Defining teams for an assignment + +If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams. + +{% tip %} + +**Dicas**: + +- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course. + +- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members. + +{% endtip %} + +![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png) + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +### Providing feedback + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the team. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
      + Group assignment +
      + +### Próximas etapas + +- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. + +- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### Leia mais + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md new file mode 100644 index 0000000000..fe5659bca5 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -0,0 +1,19 @@ +--- +title: Create an assignment from a template repository +intro: You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments +--- + +You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. Para obter mais informações, consulte "[Criar um repositório de modelos](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)". + +To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." + +### Leia mais + +- "[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)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md new file mode 100644 index 0000000000..c24274ef5c --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -0,0 +1,124 @@ +--- +title: Create an individual assignment +intro: You can create an assignment for students in your course to complete individually. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment + - /education/manage-coursework-with-github-classroom/create-an-individual-assignment +--- + +### About individual assignments + +{% data reusables.classroom.assignments-individual-definition %} + +{% data reusables.classroom.classroom-creates-individual-repositories %} + +{% data reusables.classroom.about-assignments %} + +For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### Pré-requisitos + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +### Providing feedback for an assignment + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the student. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
      + Individual assignment +
      + +### Próximas etapas + +- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." + +- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### Leia mais + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md new file mode 100644 index 0000000000..f0b63a9f98 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md @@ -0,0 +1,9 @@ +--- +title: Get started with GitHub Classroom +shortTitle: Começar +intro: Learn how to configure and use {% data variables.product.prodname_classroom %} to administer your course. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/glossary.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/glossary.md new file mode 100644 index 0000000000..c78d452507 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/glossary.md @@ -0,0 +1,52 @@ +--- +title: Glossário +intro: You can review explanations of terminology for {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +--- + +### atividade + +An assignment is coursework in {% data variables.product.prodname_classroom %}. A teacher can assign an assignment to an individual student or a group of students. Teachers can import starter code for the assignment, assign students, and create a deadline for each assignment. For more information, see the definitions for "[individual assignment](#individual-assignment)" and "[group assignment](#group-assignment)." + +--- + +### classroom + +A classroom is the basic unit of {% data variables.product.prodname_classroom %}. Teachers can use a classroom to organize and manage students, teaching assistants, and assignments for a single course. A classroom belongs to an organization on {% data variables.product.prodname_dotcom_the_website %}. To administer a classroom, you must be an organization owner for the organization on {% data variables.product.prodname_dotcom %}. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." + +--- + +### {% data variables.product.prodname_classroom %} + +{% data variables.product.prodname_classroom %} is a web application for educators that provides course administration tools integrated with {% data variables.product.prodname_dotcom %}. For more information, see the [{% data variables.product.prodname_classroom %}](https://classroom.github.com/) website. + +--- + +### group assignment + +{% data reusables.classroom.assignments-group-definition %} For more information, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +--- + +### identifier + +An identifier in {% data variables.product.prodname_classroom %} is a unique ID for a student participating in a course. For example, an identifier can be a student name, alphanumeric ID, or email address. + +--- + +### individual assignment + +{% data reusables.classroom.assignments-individual-definition %} For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +--- + +### roster + +A roster allows a teacher to manage students and assignment submissions in a classroom on {% data variables.product.prodname_classroom %}. Teachers can create a roster by entering a list of student identifiers, or by connecting {% data variables.product.prodname_classroom %} to a learning management system (LMS). For more information about identifiers, see the definition of "[identifier](#identifier)." For more information about connecting {% data variables.product.prodname_classroom %} to an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + +--- + +### Leia mais + +- "[Glossário do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/github-glossary)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/index.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/index.md new file mode 100644 index 0000000000..681061bf61 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/index.md @@ -0,0 +1,32 @@ +--- +title: Manage coursework with GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %}' +intro: With {% data variables.product.prodname_classroom %}, you can use {% data variables.product.product_name %} to administer or participate in a course about software development. +versions: + free-pro-team: '*' +--- + +### Índice + +{% topic_link_in_list /get-started-with-github-classroom %} + {% link_in_list /basics-of-setting-up-github-classroom %} + {% link_in_list /glossary %} + +{% topic_link_in_list /teach-with-github-classroom %} + {% link_in_list /manage-classrooms %} + {% link_in_list /create-an-individual-assignment %} + {% link_in_list /create-a-group-assignment %} + {% link_in_list /create-an-assignment-from-a-template-repository %} + {% link_in_list /leave-feedback-with-pull-requests %} + {% link_in_list /use-autograding %} + {% link_in_list /configure-default-settings-for-assignment-repositories %} + {% link_in_list /connect-a-learning-management-system-to-github-classroom %} + +{% topic_link_in_list /integrate-github-classroom-with-an-ide %} + {% link_in_list /integrate-github-classroom-with-an-online-ide %} + {% link_in_list /about-using-makecode-arcade-with-github-classroom %} + {% link_in_list /about-using-replit-with-github-classroom %} + {% link_in_list /run-student-code-in-an-online-ide %} + +{% topic_link_in_list /learn-with-github-classroom %} + {% link_in_list /view-autograding-results %} diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md new file mode 100644 index 0000000000..f4245ea672 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md @@ -0,0 +1,9 @@ +--- +title: Integrate GitHub Classroom with an IDE +shortTitle: Integrate with an IDE +intro: You can help your students write, test, and debug code by preconfiguring a development environment for assignment repositories on {% data variables.product.prodname_classroom %}. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md new file mode 100644 index 0000000000..6b4b6b5271 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md @@ -0,0 +1,42 @@ +--- +title: Integrate GitHub Classroom with an online IDE +shortTitle: Integrate with an online IDE +intro: You can preconfigure a supported online integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/online-ide-integrations +--- + +### About integration with an online IDE + +{% data reusables.classroom.about-online-ides %} + +After a student accepts an assignment with an online IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary. + +![Button for online IDE in README.md for assignment repository](/assets/images/help/classroom/assignment-repository-ide-button-in-readme.png) + +### Supported online IDEs + +{% data variables.product.prodname_classroom %} supports the following online IDEs. You can learn more about the student experience for each IDE. + +| IDE | Mais informações | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | +| Repl.it | "[About using Repl.it with GitHub Classroom](/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom)" | + +### Configuring an online IDE for an assignment + +You can choose the online IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an online IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Authorizing the OAuth app for an online IDE + +The first time you configure an assignment with an online IDE, you must authorize the OAuth app for the online IDE for your organization. + +!["Go grant access" button in popover for authorizing OAuth app for online IDE](/assets/images/help/classroom/assignment-ide-go-grant-access-button.png) + +For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". + +### Leia mais + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md new file mode 100644 index 0000000000..bca1150346 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Learn with GitHub Classroom +intro: You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md new file mode 100644 index 0000000000..59132bd745 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md @@ -0,0 +1,31 @@ +--- +title: Leave feedback with pull requests +intro: You can leave feedback for your students in a special pull request within the repository for each assignment. +permissions: People with read permissions to a repository can leave feedback in a pull request for the repository. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github +--- + +### About feedback pull requests for assignments + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +When you enable the pull request for feedback for an assignment, {% data variables.product.prodname_classroom %} will create a special pull request titled **Feedback** in the assignment repository for each student or team. The pull request automatically shows every commit that a student pushed to the assignment repository's default branch. + +### Pré-requisitos + +To create and access the feedback pull request, you must enable the feedback pull request when you create the assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +### Leaving feedback in a pull request for an assignment + +{% data reusables.classroom.sign-into-github-classroom %} +1. In the list of classrooms, click the classroom with the assignment you want to review. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **Review**. ![Review button for assignment in list of submissions for an assignment](/assets/images/help/classroom/assignments-click-review-button.png) +1. Review the pull request. Para obter mais informações, consulte "[Comentando em uma pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)." + +### Leia mais + +- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](http://localhost:4000/en/free-pro-team@latest/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" 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 new file mode 100644 index 0000000000..08cd6cc2f2 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -0,0 +1,106 @@ +--- +title: Manage classrooms +intro: You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}. +permissions: Organization owners can manage a classroom for an organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/archive-a-classroom +--- + +### About classrooms + +{% data reusables.classroom.about-classrooms %} + +![Classroom](/assets/images/help/classroom/classroom-hero.png) + +### About management of classrooms + +{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. + +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 classrom. 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)." + +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. + +### About classroom rosters + +Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course. + +When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment. + +![Classroom roster](/assets/images/help/classroom/roster-hero.png) + +### Pré-requisitos + +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 authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". + +### Creating a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **New classroom**. !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png) +{% data reusables.classroom.guide-create-new-classroom %} + +After you create a classroom, you can begin creating assignments for students. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Creating a roster for your classroom + +You can create a roster of the students who participate in your course. + +If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) +1. To create a roster manually, type your student identifiers. Optionally, click **Upload a CSV or text file** to upload a file containing the identifiers. ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png) +1. Click **Create roster**. !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png) + +### Adding students to the roster for your classroom + +Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classrom](#creating-a-roster-for-your-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To the right of "Classroom roster", click **Update students**. !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png) +1. Follow the instructions to add students to the roster. + - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**. ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) + +### Renaming a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Classroom name", type a new name for the classroom. ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png) +1. Click **Rename classroom**. !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png) + +### Archiving or unarchiving a classroom + +You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**. ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png) +1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**. ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) + +### Deleting a roster for a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Under "Delete this roster", click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png) +1. Read the warnings, then click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) + +### Deleting a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) +1. **Leia os avisos**. +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md new file mode 100644 index 0000000000..57e3f1e824 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md @@ -0,0 +1,21 @@ +--- +title: Run student code in an online IDE +intro: You can run the code from a student assignment within the online integrated development environment (IDE) that you configured for the assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/running-student-code +--- + +### About student code and online IDEs + +If you configure an online integrated development environment (IDE) for an assignment, you can run the code within the online IDE. You don't need to clone the assignment repository to your computer. + +For more information about online IDEs, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +### Running student code in the online IDE + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **View IDE**. !["View IDE" button for submission using an online IDE](/assets/images/help/classroom/assignments-click-view-ide.png) diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md new file mode 100644 index 0000000000..6e051e9d2d --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Teach with GitHub Classroom +intro: Learn how to set up your classroom and assignments. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/use-autograding.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/use-autograding.md new file mode 100644 index 0000000000..7522b2b202 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/use-autograding.md @@ -0,0 +1,83 @@ +--- +title: Use autograding +intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers +--- + +### About autograding + +{% data reusables.classroom.about-autograding %} + +After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding. + +You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." + +You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment. + +![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png) + +### Grading methods + +There are two grading methods: input/output tests and run command tests. + +#### Input/output test + +An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result. + +| Configuração | Descrição | +|:------------------- |:------------------------------------------------------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate standard output for evaluation | +| **Inputs** | Standard input for run command | +| **Expected output** | The output that you want to see as standard output from the run command | +| **Comparison** | The type of comparison between the run command's output and the expected output

      • **Included**: Passes when the expected output appears
        anywhere in the standard output from the run command
      • **Exact**: Passes when the expected output is completely identical
        to the standard output from the run command
      • **Regex**: Passes if the regular expression in expected
        output matches against the standard output from the run command
      | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +#### Run command test + +A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure. + +{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`. + +| Configuração | Descrição | +|:----------------- |:------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate an exit code for evaluation | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +### Configuring autograding tests for an assignment + +You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests. + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.assignments-click-pencil %} +1. In the left sidebar, click **Grading and feedback**. !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) +1. Add, edit, or delete an autograding test. + - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png) +1. At the bottom of the page, click **Update assignment**. !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png) + +### Viewing logs from autograding tests + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of a submission, click **View test**. !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png) +1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)." + +### Leia mais + +- [{% data variables.product.prodname_actions %} documentation](/actions) diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/view-autograding-results.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/view-autograding-results.md new file mode 100644 index 0000000000..a1e904e7b9 --- /dev/null +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/view-autograding-results.md @@ -0,0 +1,30 @@ +--- +title: View autograding results +intro: You can see results from autograding within the repository for your assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students +--- + +### About autograding + +Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.product.product_location %}. + +If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X. + +### Viewing autograding results for an assignment repository + +{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." + +The **Actions** tab shows the full history of test runs. + +!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png) + +You can click a specific test run to review log output, like compilation errors and test failures. + +![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) + +### Leia mais + +- "[Sobre verificações de status](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/pt-BR/content/education/quickstart.md b/translations/pt-BR/content/education/quickstart.md new file mode 100644 index 0000000000..2516977083 --- /dev/null +++ b/translations/pt-BR/content/education/quickstart.md @@ -0,0 +1,87 @@ +--- +title: Quickstart for GitHub Educators +intro: In about 15 minutes, teachers can get started with discounts, training, and tools for {% data variables.product.company_short %}, then create a classroom for the students in a software development course using {% data variables.product.prodname_classroom %}. +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +### Introdução + +Educators who teach a course on software development can use discounts, partnerships, training, and tools from {% data variables.product.prodname_education %} to effectively teach relevant skills to students. + +In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}. + +{% tip %} + +**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Applying for a student developer pack](/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack)." + +{% endtip %} + +### Creating accounts on {% data variables.product.product_name %} + +First, you'll need to create a free user account on {% data variables.product.product_name %}. + +{% data reusables.accounts.create-account %} +1. Follow the prompts to create your free user account. + +After you create your user account, create a free organization account. You'll use this organization account to create and manage classrooms {% data variables.product.prodname_classroom %}. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Follow the prompts to create a free organization. + +For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." + +### Applying for an educator discount + +Next, you'll sign up for discounts on services from {% data variables.product.company_short %}. {% data reusables.education.educator-requirements %} + +{% tip %} + +**Tip** In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website. + +{% endtip %} + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Set up {% data variables.product.prodname_classroom %} + +With your user account and organization account, you're ready to get started with {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %} is free to use. You can track and manage assignments, grade work automatically, and provide feedback to your students. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To authorize {% data variables.product.prodname_classroom %} to access your user account on {% data variables.product.prodname_dotcom %}, review the information, then click **Authorize {% data variables.product.prodname_classroom %}**. !["Authorize {% data variables.product.prodname_classroom %}" button for user account](/assets/images/help/classroom/setup-click-authorize-github-classroom.png) +1. Review the information. To authorize {% data variables.product.prodname_classroom %} to access your organization account on {% data variables.product.prodname_dotcom %}, click **Grant**. !["Grant" button for organization](/assets/images/help/classroom/setup-click-grant.png) + + {% tip %} + + **Tip**: If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps#oauth-apps-and-organizations)". + + {% endtip %} + +1. Click **Authorize github**. ![Click "Authorize" button for organization](/assets/images/help/classroom/setup-click-authorize-github.png) + +### Create your classroom + +{% data reusables.classroom.about-classrooms %} + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **Create your first classroom** or **New classroom**. +{% data reusables.classroom.guide-create-new-classroom %} + +### Próximas etapas + +You've created a classroom, and you're ready to enrich your course with {% data variables.product.product_name %} and {% data variables.product.prodname_classroom %}! 🎉 + +- Watch some videos about {% data variables.product.prodname_classroom %}. For more information, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." +- Manage your classrooms and classroom admins, and create a roster of students for your classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." +- Create an assignment for individual students or teams. {% data reusables.classroom.for-more-information-about-assignment-creation %} +- Write and implement automated tests to provide immediate feedback to students directly in assignment repositories. For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." +- Participate in {% data variables.product.prodname_education_community_with_url %}. diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-campus-advisors.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..c057fa9a4d --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-campus-advisors.md @@ -0,0 +1,17 @@ +--- +title: Sobre Consultores de campus +intro: 'Como um instrutor ou mentor, aprenda a usar o {% data variables.product.prodname_dotcom %} na sua escola com treinamento e suporte de Consultores de campus.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +Os mestres, professores e mentores podem usar o treinamento online Consultores de campus para dominar o Git e o {% data variables.product.prodname_dotcom %}, bem como para conhecer as práticas recomendadas de ensino com o {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Consultores de campus](https://education.github.com/teachers/advisors)". + +{% note %} + +**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 %} diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-campus-experts.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..d04c0543bc --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-campus-experts.md @@ -0,0 +1,11 @@ +--- +title: Sobre Especialistas de campus +intro: 'Como aluno, adquira as habilidades necessárias para criar a comunidade tecnológica da sua escola e um portfólio do mundo real com o treinamento Especialistas de campus do {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +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)". diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..dec242f776 --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,31 @@ +--- +title: Sobre o GitHub Education para educadores e pesquisadores +intro: 'O {% data variables.product.prodname_education %} oferece várias ferramentas para ajudar os educadores e pesquisadores a trabalhar de maneira mais eficaz dentro e fora da sala de aula.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} para educadores + +Com os serviços e ferramentas do {% data variables.product.prodname_education %} para educadores de todos os níveis, você pode: + - Usar o [{% data variables.product.prodname_classroom %}](https://classroom.github.com) para distribuir código, dar feedback aos alunos e coletar atribuições no {% data variables.product.prodname_dotcom %}. + - Ingressar na nossa [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) para discutir tendências atuais na educação tecnológica com seus colegas ao redor do mundo. + - Acessar e adaptar nossos [planos de estudo de código aberto](https://education.github.community/t/open-source-lesson-plans/1591) para ensinar sobre o Git e o {% data variables.product.prodname_dotcom %}. + - [Solicitar um kit surpresa do {% data variables.product.prodname_dotcom %}](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) com materiais e brindes educativos para os estudantes. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} para pesquisadores + +Com os serviços e ferramentas do {% data variables.product.prodname_education %} para pesquisadores, você pode: + - Colaborar com outras pessoas no trabalho de pesquisa ao redor do mundo no {% data variables.product.prodname_dotcom %}. + - [Aprender](https://education.github.com/stories) como as instituições acadêmicas ao redor do mundo estão usando o {% data variables.product.prodname_dotcom %} para suas pesquisas. + {% data reusables.education.apply-for-team %} + +### Leia mais + +- "[Sobre o {% data variables.product.prodname_education %} para estudantes](/articles/about-github-education-for-students)" diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..f18ee1feda --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md @@ -0,0 +1,21 @@ +--- +title: Sobre o GitHub Education para estudantes +intro: 'O {% data variables.product.prodname_education %} proporciona aos estudantes do mundo real experiência com acesso grátis a várias ferramentas de desenvolvedor de parceiros do {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Usar o {% data variables.product.prodname_dotcom %} nos projetos da sua escola é uma maneira prática de colaborar com outras pessoas e de criar um portfólio que demonstra experiência no mundo real. + +{% data reusables.education.about-github-education-link %} + +Cada pessoa com uma conta do {% data variables.product.prodname_dotcom %} pode colaborar em repositórios públicos e privados ilimitados com o {% data variables.product.prodname_free_user %}. Como estudante, você também pode solicitar o {% data variables.product.prodname_student_pack %}, que oferece acesso grátis às ferramentas e aos serviços usados por desenvolvedores profissionais. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +Se você for integrante de um clube de robótica FIRST, seu mentor poderá solicitar um desconto para educador para que sua equipe possa colaborar usando o {% data variables.product.prodname_team %}, que permite repositórios privados e de usuários ilimitados, gratuitamente. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." + +### Leia mais + +- "[Sobre o {% data variables.product.prodname_education %} para educadores e pesquisadores](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education.md new file mode 100644 index 0000000000..f7a264408f --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/about-github-education.md @@ -0,0 +1,23 @@ +--- +title: Sobre o GitHub Education +intro: 'O {% data variables.product.prodname_education %} oferece um produto gratuito especial para escolas que querem aproveitar o {% data variables.product.prodname_dotcom %} ao máximo na respectiva comunidade e que concordam com os requisitos específicos do programa.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +Se a sua escola concorda em atender a determinados requisitos, sua escola secundária, universidade ou bootcamp pode obter o {% data variables.product.prodname_education %}, que oferece o melhor do {% data variables.product.prodname_dotcom %} gratuitamente, incluindo: +- {% data variables.product.prodname_ghe_cloud %} e/ou {% data variables.product.prodname_ghe_server %} +- Treinamento do professor para domínio do Git e do {% data variables.product.prodname_dotcom %} com nosso programa de consultores de campus +- Acesso automatizado a recursos premium do {% data variables.product.prodname_education %}, como o {% data variables.product.prodname_student_pack %} +- Desenvolvimento da liderança e treinamento técnico para estudantes com o programa de especialistas de campus + +Para obter mais informações, consulte a página [oficial do {% data variables.product.prodname_education %}](https://education.github.com/partners/schools). + +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)." + +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)". + +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_education %}, ainda assim é possível solicitar descontos individualmente para usar o {% 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/pt-BR/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..e6ec950234 --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,53 @@ +--- +title: Apply for a student developer pack +intro: 'Como um estudante, você pode se candidatar ao {% data variables.product.prodname_student_pack %}, que inclui ofertas e benefícios dos parceiros {% data variables.product.prodname_dotcom %}.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### Requisitos + +Para se qualificar para o {% data variables.product.prodname_student_pack %}, você deve: +- Estar atualmente matriculado em um curso superior ou curso que conceda um diploma, tal como ensino médio, ensino secundário, faculdade, universidade, educação domiciliar ou instituição de ensino similar +- Ter um endereço de e-mail verificável concedido pela instituição de ensino ou fazer upload de documentos que comprovem seu status de estudante +- Ter uma conta de usuário do [{% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account) +- Ter pelo menos 13 anos + +Os documentos que comprovam seu status atual de estudante incluem uma foto de sua identificação escolar, horário de aulas, certificado e carta de confirmação de matrícula ou inscrição. + +Durante o período como estudante, pode ser que você seja solicitado a verificar periodicamente seu status acadêmico atual. + +{% note %} + +**Observação:** não é possível transferir descontos acadêmicos de uma conta para outra. Se você tiver mais de uma conta em que queira aplicar o desconto, considere [fazer merge](/articles/merging-multiple-user-accounts) das suas contas de usuários e [renomear](/articles/changing-your-github-username) a conta retida se desejado. + +{% endnote %} + +Para obter informações sobre como renovar seu {% data variables.product.prodname_student_pack %}, consulte "[Vencimento e renovações](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)". + +### Candidatar-se a um {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. Em "Which best describes your academic status?" (Qual opção melhor descreve seu status acadêmico?), selecione **Student** (Estudante). ![Selecione o status acadêmico](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Vencimento e renovações + +Assim que seu acesso ao {% data variables.product.prodname_student_pack %} expirar, você poderá se recandidatar se ainda estiver qualificado, embora algumas das nossas ofertas de parceiro não possam ser renovadas. A maioria das ofertas com tempo limitado de nossos parceiros entra em vigor assim que você as configura. Para obter mais informações, consulte a página do [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). + +Para ver quando seu acesso grátis ao {% data variables.product.prodname_student_pack %} expira, visite as [configurações de cobrança](https://github.com/settings/billing) da sua conta. + +### Leia mais + +- "[Por que minha solicitação para um {% data variables.product.prodname_student_pack %} não foi aprovada?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..f4affa6009 --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,57 @@ +--- +title: Apply for an educator or researcher discount +intro: 'Sendo um educador ou pesquisador, você pode se candidatar para receber o {% data variables.product.prodname_team %} gratuitamente para a conta da sua organização.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### Sobre descontos para educador e pesquisador + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### Candidatar-se a um desconto de educador ou pesquisador + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Atualizar sua organização + +Depois que sua solicitação para desconto de educador ou pesquisador for aprovada, você poderá atualizar as organizações que usa com sua comunidade de aprendizagem para o {% data variables.product.prodname_team %}, o que permite usuários ilimitados e repositórios privados com recursos completos, gratuitamente. Você pode atualizar uma organização existente ou criar uma para atualizar. + +#### Atualizar uma organização existente + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Atualizar uma nova organização + +{% data reusables.education.upgrade-page %} +1. Clique em {% octicon "plus" aria-label="The plus symbol" %} **Create an organization** (Criar uma organização). ![Botão Create an organization (Criar uma organização)](/assets/images/help/education/create-org-button.png) +3. Leia as informações e clique em **Criar organização**. ![Botão Create an organization (Criar uma organização)](/assets/images/help/education/create-organization-button.png) +4. Em "Choose a plan" (Escolher um plano), clique em **Escolher {% data variables.product.prodname_free_team %}**. +5. Siga as instruções para criar sua organização. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### Leia mais + +- "[Por que minha solicitação para desconto de educador ou pesquisador não foi aprovada?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [Vídeos do {% data variables.product.prodname_classroom %}](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/index.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/index.md new file mode 100644 index 0000000000..b4486fff9a --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Teach and learn +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Índice + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..61c4dd4446 --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub at your educational institution +intro: 'Maximize os benefícios de usar o {% data variables.product.prodname_dotcom %} na sua instituição para alunos, instrutores e equipe de TI com o {% data variables.product.prodname_education %} e nossos diversos programas de treinamento para alunos e instrutores.' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..ce60906c64 --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub for your schoolwork +intro: 'Como aluno, use o {% data variables.product.prodname_dotcom %} para colaborar nos projetos da sua escola e ganhar experiência no mundo real.' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..7b41342ce2 --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub in your classroom and research +intro: 'Como educador ou pesquisador, use o {% data variables.product.prodname_dotcom %} para colaborar no seu trabalho em sala de aula, em um grupo de pesquisa ou de alunos, e muito mais.' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..f900972e32 --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,67 @@ +--- +title: Motivos da reprovação da candidatura ao pacote de desenvolvedor para estudante +intro: 'Analise os motivos comuns para a reprovação de candidaturas ao {% data variables.product.prodname_student_pack %} e veja dicas para se candidatar novamente sem problemas.' +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved + - /articles/why-was-my-application-for-a-student-developer-pack-denied/ + - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved + - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Dica:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Falta de clareza em documentos de afiliação acadêmica + +Se a imagem que você enviou por upload não identificar claramente seu status acadêmico atual, exigiremos mais provas dele. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Uso de e-mail acadêmico com domínio não verificado + +Se o seu endereço de e-mail acadêmico tiver um domínio não verificado, exigiremos mais provas do seu status acadêmico. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Uso de e-mail acadêmico de uma escola com políticas de e-mail pouco rígidas + +Se os seus endereços de e-mail concedidos pela instituição de ensino forem anteriores à inscrição paga por aluno, exigiremos mais provas do seu status acadêmico. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +Se você tiver outras dúvidas sobre o domínio da instituição de ensino, peça à equipe de TI dela para entrar em contato conosco. + +### Endereço de e-mail acadêmico já usado + +Se o seu endereço de e-mail acadêmico já tiver sido usado para solicitar um {% data variables.product.prodname_student_pack %} para outra conta do {% data variables.product.prodname_dotcom %}, você não poderá reutilizá-lo para se candidatar a outro {% data variables.product.prodname_student_pack %} enquanto o desconto estiver válido. + +{% note %} + +**Observação:** é contra os [Termos de serviço](/articles/github-terms-of-service/#3-account-requirements) do {% data variables.product.prodname_dotcom %} manter mais de uma conta individual. + +{% endnote %} + +Se você tiver mais de uma conta de usuário pessoal, precisará fazer merge delas. Para não perder o desconto, mantenha a conta que recebeu o desconto. Você pode renomear a conta mantida e permanecer com o histórico de contribuições adicionando todos os seus endereços de e-mail à conta mantida. + +Para obter mais informações, consulte: +- "[Fazer merge de várias contas de usuário](/articles/merging-multiple-user-accounts)" +- "[Alterar seu nome de usuário do {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username)" +- "[Adicionar um endereço de e-mail à sua conta do {% data variables.product.prodname_dotcom %}](/articles/adding-an-email-address-to-your-github-account)" + +### Status de aluno não qualificado + +Você não estará qualificado para um {% data variables.product.prodname_student_pack %} se: +- 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. +- 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). + +### Leia mais + +- "[Candidatar-se a um pacote de desenvolvedor para estudante](/articles/applying-for-a-student-developer-pack)" +- "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/pt-BR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/pt-BR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..0cfefb8db8 --- /dev/null +++ b/translations/pt-BR/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,45 @@ +--- +title: Motivos da reprovação da candidatura ao desconto de educador ou pesquisador +intro: Analise os motivos comuns para a reprovação de candidaturas ao desconto de educador ou pesquisador e veja dicas para se candidatar novamente sem problemas. +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Dica:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Falta de clareza em documentos que comprovam a afiliação + +Se a imagem que você enviou por upload não identificar claramente sua ocupação atual em uma instituição de ensino ou universidade, você precisará se candidatar novamente e enviar por upload outra imagem do seu crachá na faculdade ou de uma carta de verificação de referência pessoal com informações claras. + +{% data reusables.education.pdf-support %} + +### Uso de e-mail acadêmico com domínio não verificado + +Se o seu endereço de e-mail acadêmico tiver um domínio não verificado, poderemos exigir mais provas do seu status acadêmico. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Uso de e-mail acadêmico de uma escola com políticas de e-mail pouco rígidas + +Se ex-alunos e professores aposentados da sua instituição de ensino tiverem acesso vitalício a endereços de e-mail concedidos pela escola, poderemos exigir mais provas do seu status acadêmico. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +Se você tiver outras dúvidas sobre o domínio da instituição de ensino, peça à equipe de TI dela para entrar em contato conosco. + +### Candidatura de não alunos ao pacote de desenvolvedor para estudante + +Educadores e pesquisadores não estão qualificados para as ofertas de parceiros que acompanham o [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). Quando você se candidatar novamente, lembre-se de escolher **Faculty** (Faculdade) para descrever seu status acadêmico. + +### Leia mais + +- "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md index 942931397c..d6b53afb59 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -32,14 +32,14 @@ Se tiver habilitado atualizações de segurança, às vezes você verá atualiza ### Repositórios e ecossistemas suportados +É possível configurar atualizações de versão para repositórios que contenham um manifesto de dependência ou arquivo de bloqueio para um dos gerentes de pacotes suportados. Para alguns gerenciadores de pacotes, você também pode configurar o armazenamento para dependências. 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#vendor)". + {% note %} -{% data reusables.dependabot.private-dependencies %} +{% 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. See the details in the table below. {% endnote %} -É possível configurar atualizações de versão para repositórios que contenham um manifesto de dependência ou arquivo de bloqueio para um dos gerentes de pacotes suportados. Para alguns gerenciadores de pacotes, você também pode configurar o armazenamento para dependências. 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#vendor)". - {% data reusables.dependabot.supported-package-managers %} Se o seu repositório já usa uma integração para gerenciamento de dependências, você precisará desativar isso antes de habilitar o {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Sobre integrações](/github/customizing-your-github-workflow/about-integrations)". diff --git a/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md b/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md index dc44c26603..d6bae2a97e 100644 --- a/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/pt-BR/content/github/administering-a-repository/about-secret-scanning.md @@ -36,6 +36,7 @@ O {% data variables.product.product_name %} atualmente verifica repositórios p - Databricks - Datadog - Discord +- Doppler - Dropbox - Dynatrace - Finicity @@ -79,6 +80,8 @@ Quando o {% data variables.product.prodname_secret_scanning %} detecta um segred Os administradores do repositório e proprietários da organização podem conceder acesso a alertas de {% data variables.product.prodname_secret_scanning %} aos usuários e à equipe. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." + O {% data variables.product.product_name %} atualmente verifica repositórios públicos para encontrar segredos emitidos pelos seguintes provedores de serviços. - Adafruit @@ -90,6 +93,7 @@ O {% data variables.product.product_name %} atualmente verifica repositórios p - CloudBees CodeShip - Databricks - Discord +- Doppler - Dropbox - Dynatrace - Finicity diff --git a/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index 5a1f04a204..17e647855b 100644 --- a/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -290,25 +290,26 @@ Você pode usar a opção `ignore` para personalizar quais dependências são at {% data reusables.dependabot.option-affects-security-updates %} ```yaml -# Personalizando as dependências para manter com "ignore" +# Customizing the dependencies to maintain with `ignore` -versão: 2 -atualizações: +version: 2 +updates: - package-ecosystem: "npm" directory: "/" schedule: interval: "daily" ignore: - dependency-name: "express" - # Para Express, ignore todas as atualizações para a versão 4 e 5 - versões: ["4.x", "5.x"] - # Para Loadash, ignore todas as atualizações - - dependency-name: "loadash" + # For Express, ignore all updates for version 4 and 5 + versions: ["4.x", "5.x"] + # For Lodash, ignore all updates + - dependency-name: "lodash" ``` {% note %} -**Observação**: {% data variables.product.prodname_dependabot_version_updates %} não pode executar atualizações de versão para nenhuma dependência no manifesto que contém dependências do git privadas ou registros do git privados, mesmo que você adicione as dependências privadas à opção `ignorar` do seu arquivo de configuração. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot#supported-repositories-and-ecosystems)". +**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-repositories)" 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/pt-BR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/pt-BR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md index 451a2bfdcc..9c1c4fd935 100644 --- a/translations/pt-BR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md +++ b/translations/pt-BR/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -14,14 +14,10 @@ Você habilita {% data variables.product.prodname_dependabot_version_updates %}, {% data reusables.dependabot.initial-updates %} Para obter mais informações, consulte "[Personalizar atualizações de dependência](/github/administering-a-repository/customizing-dependency-updates)". +{% 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)." + ### Habilitar {% data variables.product.prodname_dependabot_version_updates %} -{% note %} - -{% data reusables.dependabot.private-dependencies %} - -{% endnote %} - {% data reusables.dependabot.create-dependabot-yml %} 1. Use `package-ecosystem` para especificar os gerenciadores de pacote a monitorar. 1. Para cada gerenciador de pacotes, use: diff --git a/translations/pt-BR/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/pt-BR/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md new file mode 100644 index 0000000000..c0dbdb12e5 --- /dev/null +++ b/translations/pt-BR/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -0,0 +1,20 @@ +--- +title: Enabling or disabling GitHub Discussions for a repository +intro: 'You can use discussions in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.' +product: '{% data reusables.gated-features.discussions %}' +permissions: People with admin permissions to a repository can enable discussions for the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Enabling or disabling discussions for your repository + +{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} +1. To disable discussions, under "Features", unselect **Discussions**. + +### Leia mais + +- "[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/pt-BR/content/github/administering-a-repository/index.md b/translations/pt-BR/content/github/administering-a-repository/index.md index 2608509eee..efc34afdff 100644 --- a/translations/pt-BR/content/github/administering-a-repository/index.md +++ b/translations/pt-BR/content/github/administering-a-repository/index.md @@ -12,36 +12,25 @@ versions: ### Índice {% topic_link_in_list /managing-repository-settings %} - {% link_in_list /setting-repository-visibility %}{% if currentVersion == "free-pro-team@latest" %} - {% link_in_list /managing-teams-and-people-with-access-to-your-repository %}{% endif %} + {% link_in_list /setting-repository-visibility %} + {% link_in_list /managing-teams-and-people-with-access-to-your-repository %} {% link_in_list /classifying-your-repository-with-topics %} {% link_in_list /customizing-how-changed-files-appear-on-github %} {% link_in_list /about-email-notifications-for-pushes-to-your-repository %} - {% link_in_list /displaying-a-sponsor-button-in-your-repository %} - - {% link_in_list /customizing-your-repositorys-social-media-preview %} - - {% link_in_list /viewing-deployment-activity-for-your-repository %} - {% link_in_list /managing-the-forking-policy-for-your-repository %} - {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository %} - {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %} + {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /enabling-or-disabling-github-discussions-for-a-repository %}{% endif %} {% link_in_list /managing-git-lfs-objects-in-archives-of-your-repository %} {% link_in_list /enabling-anonymous-git-read-access-for-a-repository %} - - {% link_in_list /configuring-autolinks-to-reference-external-resources %} - {% link_in_list /renaming-a-repository %} {% link_in_list /transferring-a-repository %} {% link_in_list /deleting-a-repository %} - {% link_in_list /restoring-a-deleted-repository %} - {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} {% link_in_list /changing-the-default-branch %} @@ -50,9 +39,7 @@ versions: {% link_in_list /about-merge-methods-on-github %} {% link_in_list /configuring-commit-squashing-for-pull-requests %} {% link_in_list /configuring-commit-rebasing-for-pull-requests %} - {% link_in_list /managing-the-automatic-deletion-of-branches %} - {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} {% link_in_list /configuring-protected-branches %} @@ -65,31 +52,22 @@ versions: {% link_in_list /enabling-required-reviews-for-pull-requests %} {% link_in_list /about-required-commit-signing %} {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} {% link_in_list /enabling-force-pushes-to-a-protected-branch %} {% link_in_list /enabling-deletion-of-a-protected-branch %} - {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} {% link_in_list /viewing-your-repositorys-releases-and-tags %} {% link_in_list /linking-to-releases %} - {% link_in_list /comparing-releases %} - - {% link_in_list /automation-for-release-forms-with-query-parameters %} - - {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} {% link_in_list /configuring-secret-scanning-for-private-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} - - {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} {% link_in_list /about-dependabot-version-updates %} {% link_in_list /enabling-and-disabling-version-updates %} @@ -98,4 +76,3 @@ versions: {% link_in_list /customizing-dependency-updates %} {% link_in_list /configuration-options-for-dependency-updates %} {% link_in_list /keeping-your-actions-up-to-date-with-dependabot %} - diff --git a/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md index f44c8b8f6c..afc9c467e7 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/pt-BR/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -19,9 +19,9 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product {% mac %} -1. Copie a chave SSH na área de transferência. +1. Copy the SSH public key to your clipboard. - Se o arquivo da chave SSH tiver um nome diferente do código de exemplo, modifique o nome do arquivo para corresponder à sua configuração atual. Ao copiar sua chave, não adicione novas linhas nem espaços em branco. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. Ao copiar sua chave, não adicione novas linhas nem espaços em branco. ```shell $ pbcopy < ~/.ssh/id_ed25519.pub @@ -46,9 +46,9 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product {% windows %} -1. Copie a chave SSH na área de transferência. +1. Copy the SSH public key to your clipboard. - Se o arquivo da chave SSH tiver um nome diferente do código de exemplo, modifique o nome do arquivo para corresponder à sua configuração atual. Ao copiar sua chave, não adicione novas linhas nem espaços em branco. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. Ao copiar sua chave, não adicione novas linhas nem espaços em branco. ```shell $ clip < ~/.ssh/id_ed25519.pub @@ -73,9 +73,9 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product {% linux %} -1. Copie a chave SSH na área de transferência. +1. Copy the SSH public key to your clipboard. - Se o arquivo da chave SSH tiver um nome diferente do código de exemplo, modifique o nome do arquivo para corresponder à sua configuração atual. Ao copiar sua chave, não adicione novas linhas nem espaços em branco. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. Ao copiar sua chave, não adicione novas linhas nem espaços em branco. ```shell $ sudo apt-get install xclip 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 2a23715422..e27c96d6cc 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 @@ -9,7 +9,7 @@ versions: enterprise-server: '*' --- -Você deve escolher ou gerar uma senha para sua conta do {% data variables.product.product_name %} que tenha: +You must choose or generate a password for your {% data variables.product.product_name %} account that is at least: - Oito caracteres, se incluir um número e uma letra minúscula, ou - 16 caracteres com qualquer combinação de caracteres diff --git a/translations/pt-BR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/pt-BR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index 9872e4d6cc..a04967ebe8 100644 --- a/translations/pt-BR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/pt-BR/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -40,6 +40,12 @@ Para substituir todo o texto relacionado no `passwords.txt` sempre que ele for e $ bfg --replace-text passwords.txt ``` +After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. + +```shell +$ git push --force +``` + Consulte as instruções completas de download e uso na documentação do [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/). #### Usar o filter-branch 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 51f7b922a7..73c964f158 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 @@ -176,7 +176,7 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev | `repo_funding_link_button_toggle` | Acionada quando você habilita ou desabilita um botão de patrocinador no repositório (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | `repo_funding_links_file_action` | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | `sponsor_sponsorship_cancel` | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | -| `sponsor_sponsorship_create` | Acionadas quando você patrocina um desenvolvedor (consulte "[Patrocinar um colaborador de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor#sponsoring-a-developer)") | +| `sponsor_sponsorship_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` | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/articles/managing-your-sponsorship)") | | `sponsor_sponsorship_tier_change` | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | | `sponsored_developer_approve` | Acionada quando sua conta do {% data variables.product.prodname_sponsors %} é aprovada (ver "[Configuração de {% data variables.product.prodname_sponsors %} para sua conta de usuário](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | diff --git a/translations/pt-BR/content/github/building-a-strong-community/index.md b/translations/pt-BR/content/github/building-a-strong-community/index.md index dbe945aa36..f61f016916 100644 --- a/translations/pt-BR/content/github/building-a-strong-community/index.md +++ b/translations/pt-BR/content/github/building-a-strong-community/index.md @@ -13,21 +13,15 @@ versions: ### Índice {% topic_link_in_list /setting-up-your-project-for-healthy-contributions %} - {% link_in_list /about-community-management-and-moderation %} {% link_in_list /about-community-profiles-for-public-repositories %} {% link_in_list /accessing-a-projects-community-profile %} {% link_in_list /adding-a-code-of-conduct-to-your-project %} - {% link_in_list /setting-guidelines-for-repository-contributors %} {% link_in_list /adding-a-license-to-a-repository %} {% link_in_list /adding-support-resources-to-your-project %} - {% link_in_list /creating-a-default-community-health-file %} - - {% link_in_list /encouraging-helpful-contributions-to-your-project-with-labels %} - {% topic_link_in_list /using-templates-to-encourage-useful-issues-and-pull-requests %} {% link_in_list /about-issue-and-pull-request-templates %} {% link_in_list /configuring-issue-templates-for-your-repository %} @@ -42,7 +36,6 @@ versions: {% link_in_list /tracking-changes-in-a-comment %} {% link_in_list /managing-how-contributors-report-abuse-in-your-organizations-repository %} {% link_in_list /managing-reported-content-in-your-organizations-repository %} - {% topic_link_in_list /maintaining-your-safety-on-github %} {% link_in_list /blocking-a-user-from-your-personal-account %} {% link_in_list /viewing-users-youve-blocked-from-your-personal-account %} @@ -51,7 +44,6 @@ versions: {% link_in_list /viewing-users-who-are-blocked-from-your-organization %} {% link_in_list /unblocking-a-user-from-your-organization %} {% link_in_list /reporting-abuse-or-spam %} - {% topic_link_in_list /documenting-your-project-with-wikis %} {% link_in_list /about-wikis %} {% link_in_list /adding-or-editing-wiki-pages %} @@ -60,10 +52,8 @@ versions: {% link_in_list /viewing-a-wikis-history-of-changes %} {% link_in_list /changing-access-permissions-for-wikis %} {% link_in_list /disabling-wikis %} - {% topic_link_in_list /collaborating-with-your-team %} {% link_in_list /about-team-discussions %} {% link_in_list /creating-a-team-discussion %} {% link_in_list /editing-or-deleting-a-team-discussion %} {% link_in_list /pinning-a-team-discussion %} - diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md index f35f3404d0..67485ea4ce 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -22,7 +22,11 @@ versions: {% data reusables.pull_requests.automatically-delete-branches %} -Se o branch que você deseja excluir for o branch-padrão do repositório, você deverá escolher um novo branch-padrão antes de excluir o branch. For more information, see "[Setting the default branch](/github/administering-a-repository/setting-the-default-branch)." +{% note %} + +**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Setting the default branch](/github/administering-a-repository/setting-the-default-branch)." + +{% endnote %} Se o branch que você deseja excluir estiver associado a um pull request aberto, você deverá fazer o merge ou fechar o pull request antes de excluir o branch. Para obter mais informações, consulte "[Fazer merge de um pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)" ou "[Fechar um pull request](/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request)". diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/index.md index 37564976af..c31fdfcdae 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/index.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/index.md @@ -29,9 +29,7 @@ versions: {% link_in_list /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility %} {% topic_link_in_list /collaborating-on-repositories-with-code-quality-features %} {% link_in_list /about-status-checks %} - {% link_in_list /working-with-pre-receive-hooks %} - {% topic_link_in_list /proposing-changes-to-your-work-with-pull-requests %} {% link_in_list /about-branches %} {% link_in_list /creating-and-deleting-branches-within-your-repository %} @@ -39,9 +37,7 @@ versions: {% link_in_list /about-comparing-branches-in-pull-requests %} {% link_in_list /creating-a-pull-request %} {% link_in_list /creating-a-pull-request-from-a-fork %} - {% link_in_list /changing-the-stage-of-a-pull-request %} - {% link_in_list /requesting-a-pull-request-review %} {% link_in_list /changing-the-base-branch-of-a-pull-request %} {% link_in_list /committing-changes-to-a-pull-request-branch-created-from-a-fork %} @@ -52,15 +48,12 @@ versions: {% topic_link_in_list /reviewing-changes-in-pull-requests %} {% link_in_list /about-pull-request-reviews %} {% link_in_list /reviewing-proposed-changes-in-a-pull-request %} - {% link_in_list /filtering-files-in-a-pull-request %} - {% link_in_list /finding-changed-methods-and-functions-in-a-pull-request %} {% link_in_list /commenting-on-a-pull-request %} {% link_in_list /viewing-a-pull-request-review %} - + {% link_in_list /reviewing-dependency-changes-in-a-pull-request %} {% link_in_list /incorporating-feedback-in-your-pull-request %} - {% link_in_list /approving-a-pull-request-with-required-reviews %} {% link_in_list /dismissing-a-pull-request-review %} {% link_in_list /checking-out-pull-requests-locally %} 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 new file mode 100644 index 0000000000..18bdb43690 --- /dev/null +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -0,0 +1,74 @@ +--- +title: Reviewing dependency changes in a pull request +intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Dependency review is currently in beta and subject to change. + +{% endnote %} + +### About dependency review + +If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. + +Dependency review is available in: + +* All public repositories. +* Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. 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#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". + +Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. + +By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. {% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix them at some later date. 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)". + +Dependency review supports the same languages and package management ecosystems as the dependency graph. 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)". + +### Reviewing dependencies in a pull request + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} + +1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. + + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + + {% note %} + + **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% endnote %} + +1. Check the dependencies listed in the dependency review. + + ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) + + Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name. + + The icon beside each dependency indicates whether the dependency has been added ({% octicon "diff-added" aria-label="Dependency added icon" %}), updated ({% octicon "diff-modified" aria-label="Dependency modified icon" %}), or removed ({% octicon "diff-removed" aria-label="Dependency removed icon" %}) in this pull request. + + Other information includes: + + * The version, or version range, of the new, updated, or deleted dependency. + * For a specific version of a dependency: + * The age of that release of the dependency. + * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency. + * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project. + + Where a dependency has a known vulnerability, the warning message includes: + + * A brief description of the vulnerability. + * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability. + * The severity of the vulnerability. + * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. + +1. You can return to the original view of the file by clicking the source diff button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 655476bc9b..1536c3211a 100644 --- a/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -29,6 +29,18 @@ Antes de enviar a revisão, os comentários em linha ficam com status _pendente_ ![Botão Cancel review (Cancelar revisão)](/assets/images/help/pull_requests/cancel-review-button.png) +{% if currentVersion == "free-pro-team@latest" %} +### Reviewing dependency changes + +If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. 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 reusables.repositories.changed-files %} + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) +{% endif %} + ### Marcar um arquivo como visualizado Quando terminar de revisar um arquivo, você pode marcar o arquivo como visualizado, e o arquivo será aninhado. Se o arquivo for alterado após ser visualizado, será desmarcado como visualizado. @@ -53,8 +65,5 @@ Quando terminar de revisar os arquivos que deseja incluir na pull request, envie ### Leia mais -- "[Sobre revisões de solicitação pull](/articles/about-pull-request-reviews)" -- "[Sobre revisões obrigatórias para pull requests](/articles/about-required-reviews-for-pull-requests)" -- "[Aprovar uma pull request com revisões obrigatórias](/articles/approving-a-pull-request-with-required-reviews)" -- "[Comentar em uma pull request](/articles/commenting-on-a-pull-request)" -- "[Filtrar pull requests por status de revisão](/articles/filtering-pull-requests-by-review-status)" +- "[Sobre revisões obrigatórias para pull requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[Filtrar pull requests por status de revisão](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/index.md b/translations/pt-BR/content/github/committing-changes-to-your-project/index.md index ec85e37f5d..17c6778ed0 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/index.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/index.md @@ -16,9 +16,7 @@ versions: {% topic_link_in_list /creating-and-editing-commits %} {% link_in_list /about-commits %} {% link_in_list /creating-a-commit-with-multiple-authors %} - {% link_in_list /creating-a-commit-on-behalf-of-an-organization %} - {% link_in_list /changing-a-commit-message %} {% topic_link_in_list /viewing-and-comparing-commits %} {% link_in_list /commit-branch-and-tag-labels %} 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 0c1307f2a5..3a9d7d1717 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 @@ -40,9 +40,9 @@ Para que os proprietários do código recebam solicitações de revisão, o arqu ### Sintaxe de CODEOWNERS -Um arquivo CODEOWNERS usa um padrão que segue as mesmas regras usadas nos arquivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format). O padrão é seguido por um ou mais nomes de usuário ou nomes de equipe do {% data variables.product.prodname_dotcom %} usando o formato padrão `@username` ou `@org/team-name`. Você também pode consultar um usuário por um endereço de e-mail que tenha sido adicionado à respectiva conta do {% data variables.product.product_name %}, por exemplo `user@example.com`. +A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). O padrão é seguido por um ou mais nomes de usuário ou nomes de equipe do {% data variables.product.prodname_dotcom %} usando o formato padrão `@username` ou `@org/team-name`. Você também pode consultar um usuário por um endereço de e-mail que tenha sido adicionado à respectiva conta do {% data variables.product.product_name %}, por exemplo `user@example.com`. -Se qualquer linha do seu arquivo CODEOWNERS contiver uma sintaxe inválida, o arquivo não será detectado e não será usado para solicitar revisões. A sintaxe inválida inclui comentários embutidos e nomes de usuário ou equipe que não existem em {% data variables.product.product_name %}. +Se qualquer linha do seu arquivo CODEOWNERS contiver uma sintaxe inválida, o arquivo não será detectado e não será usado para solicitar revisões. #### Exemplo de um arquivo CODEOWNERS ``` # Este é um comentário. @@ -84,6 +84,13 @@ apps/ @octocat # subdirectories. /docs/ @doctocat ``` +#### Syntax exceptions +There are some syntax rules for gitignore files that do not work in CODEOWNERS files: +- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment +- Using `!` to negate a pattern +- Using `[ ]` to define a character range + + ### Leia mais diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index a234d85baa..a65e495f1c 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -1,6 +1,6 @@ --- title: Sobre repositórios -intro: Um repositório é como uma pasta para seu projeto. O repositório do seu projeto contém todos os arquivos do projeto e armazena cada histórico de revisão do arquivo. Você também pode discutir e gerenciar o trabalho do projeto dentro do repositório. +intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository. redirect_from: - /articles/about-repositories versions: @@ -22,9 +22,11 @@ Com Cada pessoa e organização podem ter repositórios ilimitados e convidar um número ilimitado de colaboradores para todos os repositórios. {% endif %} -Você pode colaborar em seu projeto com outras pessoas usando os problemas, as pull requests e os quadros de projeto do repositório. - -![Página principal do repositório octocat/Hello-World](/assets/images/help/repository/repo-main-page.png) +You can use repositories to manage your work and collaborate with others. +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)." +- {% data reusables.discussions.you-can-use-discussions %} +- You can use pull requests to propose changes to a repository. Para obter mais informações, consulte "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". +- You can use project boards to organize and prioritize your issues and pull requests. Para obter mais informações, consulte "[Sobre quadros de projeto](/github/managing-your-work-on-github/about-project-boards)". {% data reusables.repositories.repo-size-limit %} diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md index f9b752862c..39859f4586 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md @@ -45,16 +45,16 @@ Você pode localizar a URL do repositório local abrindo a linha de comando e di ```shell $ git remote -v # Visualiza remotes existentes -> origem https://github.com/github/reactivecocoa.git (fetch) -> origem https://github.com/github/reactivecocoa.git (push) +> origem https://github.com/ghost/reactivecocoa.git (fetch) +> origem https://github.com/ghost/reactivecocoa.git (push) -$ git remote set-url origin https://github.com/github/ReactiveCocoa.git +$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git # Altere a 'origem' da URL do remote $ git remote -v # Verifica nova URL remota -> origin https://github.com/github/ReactiveCocoa.git (fetch) -> origin https://github.com/github/ReactiveCocoa.git (push) +> origin https://github.com/ghost/ReactiveCocoa.git (fetch) +> origin https://github.com/ghost/ReactiveCocoa.git (push) ``` Aternativamente, você pode alterar a URL por meio de nosso aplicativo [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). diff --git a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/index.md index d5e30bf3ab..6a383e89b8 100644 --- a/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/index.md +++ b/translations/pt-BR/content/github/creating-cloning-and-archiving-repositories/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repositories %} {% link_in_list /about-repository-visibility %} {% link_in_list /creating-a-new-repository %} - {% link_in_list /creating-a-repository-from-a-template %} - {% link_in_list /about-readmes %} {% link_in_list /about-code-owners %} {% link_in_list /about-repository-languages %} {% link_in_list /licensing-a-repository %} - {% link_in_list /creating-a-template-repository %} - {% link_in_list /creating-an-issues-only-repository %} {% link_in_list /limits-for-viewing-content-and-diffs-in-a-repository %} {% link_in_list /duplicating-a-repository %} @@ -39,8 +35,6 @@ versions: {% topic_link_in_list /archiving-a-github-repository %} {% link_in_list /about-archiving-repositories %} {% link_in_list /archiving-repositories %} - {% link_in_list /about-archiving-content-and-data-on-github %} {% link_in_list /referencing-and-citing-content %} - {% link_in_list /backing-up-a-repository %} diff --git a/translations/pt-BR/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/pt-BR/content/github/customizing-your-github-workflow/about-github-marketplace.md index 9ff4337862..600dd155d7 100644 --- a/translations/pt-BR/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/pt-BR/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -7,26 +7,27 @@ versions: free-pro-team: '*' --- -É possível descobrir, procurar e instalar ferramentas grátis e pagas, incluindo [{% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/) e {% data variables.product.prodname_actions %} no [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). +You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Ao comprar uma ferramenta paga, você pagará pela assinatura da sua ferramenta com as mesmas informações de cobrança usadas para pagar sua assinatura do {% data variables.product.product_name %} e receberá uma fatura na data regular da cobrança. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". -Você também pode ter a opção de selecionar uma versão de avaliação grátis de 14 dias das ferramentas escolhidas. É possível fazer o cancelamento a qualquer momento durante a avaliação, e você não será cobrado, mas perderá automaticamente o acesso à ferramenta. A assinatura paga começará a ser contada no fim da versão de avaliação de 14 dias. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". +You may also have the option to select a free 14-day trial on some tools. É possível fazer o cancelamento a qualquer momento durante a avaliação, e você não será cobrado, mas perderá automaticamente o acesso à ferramenta. A assinatura paga começará a ser contada no fim da versão de avaliação de 14 dias. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". -Os {% data variables.product.prodname_github_app %}s e {% data variables.product.prodname_oauth_app %}s podem ser verificados ou não verificados. Os apps verificados atendem a requisitos específicos definidos pelo {% data variables.product.prodname_dotcom %} e passam por uma revisão de segurança para que possam ser listados no {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Requisitos para listar um aplicativo no GitHub Marketplace](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." +### Finding tools on {% data variables.product.prodname_marketplace %} -### {% data variables.product.prodname_actions %} no {% data variables.product.prodname_marketplace %} +You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." -Você pode descobrir, pesquisar e instalar o {% data variables.product.prodname_actions %} criado por outras pessoas no {% data variables.product.prodname_marketplace %}. Consulte "[Pesquisar {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". +{% data reusables.actions.actions-not-verified %} -Qualquer pessoa pode listar uma ação no {% data variables.product.prodname_marketplace %}. Diferentemente de alguns apps, os {% data variables.product.prodname_actions %} listados no {% data variables.product.prodname_marketplace %} nunca são verificados pelo {% data variables.product.prodname_dotcom %}. +Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About verified creators](/developers/github-marketplace/about-verified-creators)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### Criar e listar uma ferramenta no {% data variables.product.prodname_marketplace %} -Para obter mais informações sobre a criação de sua própria ferramenta para listar em {% data variables.product.prodname_marketplace %}, consulte "[Aplicativos](/apps)" e "[{% data variables.product.prodname_actions %}](/actions)". +Para obter mais informações sobre a criação de sua própria ferramenta para listar em {% data variables.product.prodname_marketplace %}, consulte "[Aplicativos](/developers/apps)" e "[{% data variables.product.prodname_actions %}](/actions)". ### Leia mais - "[Comprar e instalar apps no {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" - "[Gerenciar cobrança para aplicativos do {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" - "[Suporte do {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" +- "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)" diff --git a/translations/pt-BR/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/pt-BR/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md index 7e24ef2c68..a9f7804777 100644 --- a/translations/pt-BR/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/pt-BR/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -15,7 +15,7 @@ versions: {% data reusables.codespaces.about-configuration %} -Se você não definir uma configuração no repositório, o {% data variables.product.prodname_dotcom %} criará um código com uma imagem-base do Linux. A imagem-base do Linux inclui ferramentas para Node.js, JavaScript, TypeScript, Python, C++, Java, C#, .NET Core, PHP, e PowerShell. Para obter mais informações sobre a imagem base do Linux, consulte o repositório [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux). +Se você não definir uma configuração no repositório, o {% data variables.product.prodname_dotcom %} criará um código com uma imagem-base do Linux. The base Linux image includes tools for Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, PowerShell, Go, Ruby, and Rust. Para obter mais informações sobre a imagem base do Linux, consulte o repositório [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux). {% data reusables.codespaces.about-personalization %} {% data reusables.codespaces.codespace-config-order %} Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para a sua conta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)". 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 9e982a020e..0cc5af03be 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 @@ -179,17 +179,17 @@ jobs: - name: Install dependencies run: | python -m pip install --upgrade pip - if [ -f requirements.txt ]; + if [ -f requirements.txt ]; then pip install -r requirements.txt; fi # Set the `CODEQL-PYTHON` environment variable to the Python executable # that includes the dependencies - echo "::set-env name=CODEQL_PYTHON::$(which python)" + echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV - name: Initialize CodeQL uses: github/codeql-action/init@v1 with: languages: python - # Override the default behavior so that the action doesn't attempt + # Override the default behavior so that the action doesn't attempt # to auto-install Python dependencies setup-python-dependencies: false ``` @@ -261,8 +261,8 @@ Para as linguagens interpretadas com as quais {% data variables.product.prodname ``` yaml paths: - - src -paths-ignore: + - src +paths-ignore: - src/node_modules - '**/*.test.js' ``` @@ -294,18 +294,18 @@ Você pode rapidamente analisar pequenas partes de um monorepo ao modificar o c 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 `github/foo`, `github/bar` e `github/baz` em {% data variables.product.prodname_dotcom_the_website %} por URLs que incluem o token de acesso pessoal que você armazena na variável de ambiente `ACCESS_TOKEN`. +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 repository on GitHub.com +- name: Configure access to private repositories env: TOKEN: ${{ secrets.ACCESS_TOKEN }} run: | - git config --global url."https://${TOKEN}@github.com/github/foo".insteadOf "https://github.com/github/foo" - git config --global url."https://${TOKEN}@github.com/github/bar".insteadOf "https://github.com/github/bar" - git config --global url."https://${TOKEN}@github.com/github/baz".insteadOf "https://github.com/github/baz" + 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 %} diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md index 832b143ee8..480991a80a 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md @@ -21,7 +21,7 @@ Você precisa executar {% data variables.product.prodname_codeql %} no mesmo con Você pode ter dificuldade para executar {% data variables.product.prodname_code_scanning %} se o contêiner que você está usando estiver com certas dependências ausentes (por exemplo, o Git deve ser instalado e adicionado à variável PATH). Se você encontrar problemas de dependência, revise a lista de software geralmente incluída nos ambientes virtuais de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte os arquivos de `readme` específicos da versão nesses locais: * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* MacOS: https://github.com/actions/virtual-environments/tree/main/images/macos +* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos * Windows: https://github.com/actions/virtual-environments/tree/main/images/win ### Exemplo de fluxo de trabalho diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index c30dbe8c30..505a6b96b7 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -40,7 +40,7 @@ No Linux: chmod +x codeql-runner-linux ``` -No MacOS: +No macOS: ```shell chmod +x codeql-runner-macos diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 49535badc3..22fa4181b4 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -107,13 +107,13 @@ Um local dentro de um artefato de programação, como, por exemplo, um arquivo n #### Objeto `physicalLocation` -| Nome | Descrição | -| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `artifactLocation.uri` | **Obrigatório.** Um URI indicando o local de um artefato, geralmente um arquivo no repositório ou gerado durante uma criação. Se o URI for relativo, ele deverá ser relativo à raiz do repositório do {% data variables.product.prodname_dotcom %} que está sendo analisado. Por exemplo, main.js ou src/script.js são relativos à raiz do repositório. Se o URI for absoluto, o {% data variables.product.prodname_code_scanning %} poderá usar o URI para fazer checkout do artefato e corresponder os arquivos no repositório. Por exemplo, `https://github.com/github/example/blob/00/src/promiseUtils.js`. | -| `region.startLine` | **Obrigatório.** O número da linha do primeiro caractere na região. | -| `region.startColumn` | **Obrigatório.** O número da coluna do primeiro caractere na região. | -| `region.endLine` | **Requerido.** O número da linha do último caractere na região. | -| `region.endColumn` | **Obrigatório.** O número da coluna do caractere após o final da região. | +| Nome | Descrição | +| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `artifactLocation.uri` | **Obrigatório.** Um URI indicando o local de um artefato, geralmente um arquivo no repositório ou gerado durante uma criação. Se o URI for relativo, ele deverá ser relativo à raiz do repositório do {% data variables.product.prodname_dotcom %} que está sendo analisado. Por exemplo, main.js ou src/script.js são relativos à raiz do repositório. Se o URI for absoluto, o {% data variables.product.prodname_code_scanning %} poderá usar o URI para fazer checkout do artefato e corresponder os arquivos no repositório. For example, `https://github.com/ghost/example/blob/00/src/promiseUtils.js`. | +| `region.startLine` | **Obrigatório.** O número da linha do primeiro caractere na região. | +| `region.startColumn` | **Obrigatório.** O número da coluna do primeiro caractere na região. | +| `region.endLine` | **Requerido.** O número da linha do último caractere na região. | +| `region.endColumn` | **Obrigatório.** O número da coluna do caractere após o final da região. | ### Exemplos de arquivos de saída SARIF diff --git a/translations/pt-BR/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/pt-BR/content/github/getting-started-with-github/git-and-github-learning-resources.md index 0593eb0cce..1919591b2b 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/pt-BR/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +authors: + - GitHub --- ### Usar o Git diff --git a/translations/pt-BR/content/github/getting-started-with-github/github-glossary.md b/translations/pt-BR/content/github/getting-started-with-github/github-glossary.md index 9ff825606d..ce4004330d 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/github-glossary.md +++ b/translations/pt-BR/content/github/getting-started-with-github/github-glossary.md @@ -10,8 +10,8 @@ versions: --- {% for term in site.data.glossaries.external %} - ### {{term.term}} - {{term.description}} + ### {% data glossaries.external[forloop.index0].term %} + {% data glossaries.external[forloop.index0].description %} --- {% endfor %} diff --git a/translations/pt-BR/content/github/getting-started-with-github/index.md b/translations/pt-BR/content/github/getting-started-with-github/index.md index 54504e2f51..97e4f61fac 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/index.md +++ b/translations/pt-BR/content/github/getting-started-with-github/index.md @@ -27,37 +27,27 @@ versions: {% link_in_list /fork-a-repo %} {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} - {% link_in_list /githubs-products %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} - {% link_in_list /types-of-github-accounts %} - {% link_in_list /faq-about-changes-to-githubs-plans %} {% link_in_list /github-cli %} {% link_in_list /github-desktop %} {% link_in_list /github-for-mobile %} - {% link_in_list /access-permissions-on-github %} {% link_in_list /github-glossary %} {% link_in_list /git-cheatsheet %} {% link_in_list /git-and-github-learning-resources %} {% topic_link_in_list /signing-up-for-github %} - {% link_in_list /signing-up-for-a-new-github-account %} {% link_in_list /verifying-your-email-address %} - {% link_in_list /setting-up-a-trial-of-github-enterprise-cloud %} {% link_in_list /setting-up-a-trial-of-github-enterprise-server %} {% topic_link_in_list /exploring-projects-on-github %} - {% link_in_list /finding-ways-to-contribute-to-open-source-on-github %} - {% link_in_list /saving-repositories-with-stars %} {% link_in_list /following-people %} {% topic_link_in_list /using-github %} {% link_in_list /supported-browsers %} - {% link_in_list /troubleshooting-connectivity-problems %} - {% link_in_list /keyboard-shortcuts %} diff --git a/translations/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 a5c927908e..f3f7cbdb3b 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 @@ -123,9 +123,9 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |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 +|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 +|command + → or command + l or control + → or control + l | Move column to the rightmost position #### Moving a card @@ -135,17 +135,17 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |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 +|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 +|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 +|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 +|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 #### Previewing a card @@ -158,7 +158,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ -|command space or control space | In the workflow editor, get suggestions for your workflow file. +|command + space or control + space | In the workflow editor, get suggestions for your workflow file. {% endif %} @@ -168,16 +168,16 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr | Keyboard shortcut | Description |-----------|------------ |e | Mark as done -| shift u| Mark as unread -| shift i| Mark as read -| shift m | Unsubscribe +| shift + u| Mark as unread +| shift + i| Mark as read +| shift + m | Unsubscribe {% else %} | Keyboard shortcut | Description |-----------|------------ |e or I or y | Mark as read -|shift m | Mute thread +|shift + m | Mute thread {% endif %} ### Network graph @@ -188,7 +188,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |→ 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 +|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 diff --git a/translations/pt-BR/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md b/translations/pt-BR/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md index 35a21f872d..184e6bfdfb 100644 --- a/translations/pt-BR/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md +++ b/translations/pt-BR/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md @@ -1,5 +1,6 @@ --- title: Fazer o registro em uma conta conta do GitHub +shortTitle: Sign up for a new GitHub account intro: 'O {% data variables.product.product_name %} oferece contas de usuário para pessoas e organizações para que equipes de pessoas trabalhem juntas.' redirect_from: - /articles/signing-up-for-a-new-github-account @@ -9,9 +10,8 @@ versions: Para obter mais informações sobre tipos de contas e produtos, consulte "[Tipos de contas do {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" e "[Produtos do {% data variables.product.product_name %}](/articles/github-s-products)". -1. Acesse a página de [Preços]({% data variables.product.pricing_url %}) do {% data variables.product.product_name %}. -2. Leia as informações sobre os diferentes produtos e assinaturas que o {% data variables.product.product_name %} oferece e clique no botão de upgrade abaixo da assinatura desejada. -3. Siga as instruções para criar a conta pessoa ou organização. +{% data reusables.accounts.create-account %} +1. Siga as instruções para criar a conta pessoa ou organização. ### Próximas etapas diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/index.md b/translations/pt-BR/content/github/importing-your-projects-to-github/index.md index 3e17ceceea..89f3178db4 100644 --- a/translations/pt-BR/content/github/importing-your-projects-to-github/index.md +++ b/translations/pt-BR/content/github/importing-your-projects-to-github/index.md @@ -15,11 +15,9 @@ versions: ### Índice {% topic_link_in_list /importing-source-code-to-github %} - {% link_in_list /about-github-importer %} {% link_in_list /importing-a-repository-with-github-importer %} {% link_in_list /updating-commit-author-attribution-with-github-importer %} - {% link_in_list /importing-a-git-repository-using-the-command-line %} {% link_in_list /adding-an-existing-project-to-github-using-the-command-line %} {% link_in_list /source-code-migration-tools %} diff --git a/translations/pt-BR/content/github/index.md b/translations/pt-BR/content/github/index.md index 038d3fea24..ea86322b6d 100644 --- a/translations/pt-BR/content/github/index.md +++ b/translations/pt-BR/content/github/index.md @@ -64,7 +64,6 @@ versions: {% link_in_list /working-with-github-pages %} {% link_in_list /supporting-the-open-source-community-with-github-sponsors %} -{% link_in_list /teaching-and-learning-with-github-education %} {% link_in_list /finding-talent-with-github-jobs %} {% link_in_list /working-with-github-support %} {% link_in_list /understanding-how-github-uses-and-protects-your-data %} diff --git a/translations/pt-BR/content/github/managing-files-in-a-repository/index.md b/translations/pt-BR/content/github/managing-files-in-a-repository/index.md index 41de4ba422..d7b9a300d9 100644 --- a/translations/pt-BR/content/github/managing-files-in-a-repository/index.md +++ b/translations/pt-BR/content/github/managing-files-in-a-repository/index.md @@ -14,9 +14,7 @@ versions: ### Índice {% topic_link_in_list /managing-files-on-github %} - {% link_in_list /navigating-code-on-github %} - {% link_in_list /creating-new-files %} {% link_in_list /adding-a-file-to-a-repository %} {% link_in_list /moving-a-file-to-a-new-location %} diff --git a/translations/pt-BR/content/github/managing-large-files/index.md b/translations/pt-BR/content/github/managing-large-files/index.md index 64fa26983b..7aaefea94f 100644 --- a/translations/pt-BR/content/github/managing-large-files/index.md +++ b/translations/pt-BR/content/github/managing-large-files/index.md @@ -15,16 +15,12 @@ versions: {% link_in_list /conditions-for-large-files %} {% link_in_list /removing-files-from-a-repositorys-history %} {% link_in_list /distributing-large-binaries %} - {% link_in_list /what-is-my-disk-quota %} - {% topic_link_in_list /versioning-large-files %} {% link_in_list /about-git-large-file-storage %} {% link_in_list /installing-git-large-file-storage %} {% link_in_list /configuring-git-large-file-storage %} - {% link_in_list /about-storage-and-bandwidth-usage %} - {% link_in_list /collaboration-with-git-large-file-storage %} {% link_in_list /moving-a-file-in-your-repository-to-git-large-file-storage %} {% link_in_list /removing-files-from-git-large-file-storage %} 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 a628b146fd..67f9613edb 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 @@ -25,6 +25,8 @@ When your code depends on a package that has a security vulnerability, this vuln - 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 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)." {% note %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md new file mode 100644 index 0000000000..c499d62ca6 --- /dev/null +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -0,0 +1,24 @@ +--- +title: About managing vulnerable dependencies +intro: '{% data variables.product.prodname_dotcom %} helps you to avoid using third-party software that contains known vulnerabilities.' +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies. + +#### Dependency graph +O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". + +#### Dependency review +By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + +#### {% data variables.product.prodname_dependabot_alerts %} +{% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" + +#### {% data variables.product.prodname_dependabot_security_updates %} +When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." + + +#### {% data variables.product.prodname_dependabot_version_updates %} +Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 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 2b32234811..f85505ecaf 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 @@ -12,7 +12,7 @@ versions: {% 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-features-for-new-repositories)." +{% 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)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %} diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/index.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/index.md index d2056ce545..d82aa3eea3 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/index.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/index.md @@ -9,8 +9,6 @@ versions: ### Índice - - {% topic_link_in_list /managing-security-vulnerabilities-in-your-project %} {% link_in_list /adding-a-security-policy-to-your-repository %} {% link_in_list /about-github-security-advisories %} @@ -22,17 +20,13 @@ versions: {% link_in_list /publishing-a-security-advisory %} {% link_in_list /editing-a-security-advisory %} {% link_in_list /withdrawing-a-security-advisory %} - {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %} - + {% link_in_list /about-managing-vulnerable-dependencies %} {% link_in_list /browsing-security-vulnerabilities-in-the-github-advisory-database %} - {% link_in_list /about-alerts-for-vulnerable-dependencies %} {% link_in_list /configuring-notifications-for-vulnerable-dependencies %} - {% link_in_list /about-dependabot-security-updates %} {% link_in_list /configuring-dependabot-security-updates %} {% link_in_list /viewing-and-updating-vulnerable-dependencies-in-your-repository %} {% link_in_list /troubleshooting-the-detection-of-vulnerable-dependencies %} {% link_in_list /troubleshooting-dependabot-errors %} - diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index 5d56a02585..cbb3ca596a 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -76,6 +76,12 @@ Existem limites separados para solicitações de atualização de versões e seg A melhor maneira de resolver este erro é fazer o merge ou fechar alguns dos pull requests existentes e acionar um novo pull request manualmente. Para obter mais informações, consulte "[Acionar um pull request de {% data variables.product.prodname_dependabot %} manualmente](#triggering-a-dependabot-pull-request-manually)". +#### {% data variables.product.prodname_dependabot %} can't resolve your dependency files + +**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". + +{% 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)." + ### Acionar um pull request de {% data variables.product.prodname_dependabot %} manualmente Se você desbloquear {% data variables.product.prodname_dependabot %}, você poderá iniciar manualmente uma nova tentativa de criar um pull request. diff --git a/translations/pt-BR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/pt-BR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 1a8935eb50..e214d51c45 100644 --- a/translations/pt-BR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/pt-BR/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -13,9 +13,11 @@ A aba de alertas do {% data variables.product.prodname_dependabot %} do seu repo É possível habilitar atualizações de segurança automáticas para qualquer repositório que usa o {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +{% data reusables.repositories.dependency-review %} + ### Sobre atualizações para dependências vulneráveis no seu repositório -O {% data variables.product.product_name %} gera {% data variables.product.prodname_dependabot_alerts %} quando detectamos vulnerabilidades que afetam o seu repositório. Para repositórios em que o {% data variables.product.prodname_dependabot_security_updates %} está ativado, quando {% data variables.product.product_name %} detecta uma dependência vulnerável, {% data variables.product.prodname_dependabot %} cria um pull request para corrigi-la. O pull request irá atualizar a dependência para a versão minimamente segura possível, o que é necessário para evitar a vulnerabilidade. +{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. O pull request irá atualizar a dependência para a versão minimamente segura possível, o que é necessário para evitar a vulnerabilidade. ### Visualizar e atualizar dependências vulneráveis 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 01b445461a..f8fda0941b 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 @@ -124,7 +124,8 @@ To filter notifications for specific activity on {% data variables.product.produ - `is:repository-invitation`{% if currentVersion != "github-ae@latest" %} - `is:repository-vulnerability-alert` - `is:repository-advisory`{% endif %} -- `is:team-discussion` +- `is:team-discussion`{% if currentVersion == "free-pro-team@latest" %} +- `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)." 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 dfabe37b53..273387a467 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 @@ -10,8 +10,14 @@ versions: github-ae: '*' --- +### About issues + 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. +Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} + +{% data reusables.discussions.you-cannot-convert-a-discussion %} + {% 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 %}." diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/index.md b/translations/pt-BR/content/github/managing-your-work-on-github/index.md index 6cdef8cdcd..10aa2e20c9 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/index.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/index.md @@ -17,15 +17,11 @@ versions: {% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} - {% link_in_list /deleting-an-issue %} - {% link_in_list /opening-an-issue-from-a-comment %} {% link_in_list /opening-an-issue-from-code %} - {% link_in_list /transferring-an-issue-to-another-repository %} {% link_in_list /pinning-an-issue-to-your-repository %} - {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} @@ -43,9 +39,7 @@ versions: {% link_in_list /linking-a-repository-to-a-project-board %} {% link_in_list /about-automation-for-project-boards %} {% link_in_list /configuring-automation-for-project-boards %} - {% link_in_list /copying-a-project-board %} - {% link_in_list /closing-a-project-board %} {% link_in_list /reopening-a-closed-project-board %} {% link_in_list /deleting-a-project-board %} diff --git a/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index d394bcb1bb..7d41fef484 100644 --- a/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/pt-BR/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -25,6 +25,7 @@ Com os termos da pesquisa de problemas e pull requests, é possível: - Filtrar problemas e pull requests que envolvem determinadas pessoas, mas não necessariamente as [**@mencionam**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams): `state:open type:issue involves:octocat` - Filtrar problemas e pull requests por responsável: `state:open type:issue assignee:octocat` - Filtrar problemas e pull requests por etiqueta: `state:open type:issue label:"bug"` +- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} Para problemas, você também pode usar a busca para: diff --git a/translations/pt-BR/content/github/receiving-notifications-about-activity-on-github/index.md b/translations/pt-BR/content/github/receiving-notifications-about-activity-on-github/index.md index c999b9fd39..e1276d3968 100644 --- a/translations/pt-BR/content/github/receiving-notifications-about-activity-on-github/index.md +++ b/translations/pt-BR/content/github/receiving-notifications-about-activity-on-github/index.md @@ -14,16 +14,10 @@ versions: {% link_in_list /choosing-the-delivery-method-for-your-notifications %} {% topic_link_in_list /managing-your-notifications %} {% link_in_list /marking-notifications-as-read %} - {% link_in_list /saving-notifications-for-later %} - {% link_in_list /subscribing-to-and-unsubscribing-from-notifications %} - {% link_in_list /listing-the-issues-and-pull-requests-youre-subscribed-to %} - {% link_in_list /watching-and-unwatching-repositories %} - {% link_in_list /watching-and-unwatching-releases-for-a-repository %} - {% link_in_list /watching-and-unwatching-team-discussions %} {% link_in_list /listing-the-repositories-youre-watching %} diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/pt-BR/content/github/searching-for-information-on-github/about-searching-on-github.md index b217de6f11..50dadcbea0 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -41,7 +41,8 @@ You can search for the following information across all repositories you can acc - [Repositórios](/articles/searching-for-repositories) - [Tópicos](/articles/searching-topics) -- [Problemas e pull requests](/articles/searching-issues-and-pull-requests) +- [Issues and pull requests](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} +- [Discussions](/github/searching-for-information-on-github/searching-discussions){% endif %} - [Código](/articles/searching-code) - [Commits](/articles/searching-commits) - [Usuários](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/index.md b/translations/pt-BR/content/github/searching-for-information-on-github/index.md index 795741dc69..0570ef630e 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/index.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/index.md @@ -26,6 +26,7 @@ versions: {% link_in_list /searching-code %} {% link_in_list /searching-commits %} {% link_in_list /searching-issues-and-pull-requests %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /searching-discussions %} {% link_in_list /searching-github-marketplace %}{% endif %} {% link_in_list /searching-users %} {% link_in_list /searching-for-packages %} diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-discussions.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-discussions.md new file mode 100644 index 0000000000..0f1e21ca39 --- /dev/null +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-discussions.md @@ -0,0 +1,110 @@ +--- +title: Searching discussions +intro: You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". + +{% data reusables.search.syntax_tips %} + +### Pesquisar por título, texto ou comentários + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| Qualifier | Exemplo | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +### Pesquisar nos repositórios de um usuário ou uma organização + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| Qualifier | Exemplo | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +### Filter by repository visibility + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +| Qualifier | Example | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +### Pesquisar por autor + +The `author` qualifier finds discussions created by a certain user. + +| Qualifier | Exemplo | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +### Pesquisar por autor do comentário + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| Qualifier | Exemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +### Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| Qualifier | Exemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +### Pesquisar por número de comentários + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Exemplo | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +### Pesquisar por número de interações + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Exemplo | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +### Pesquisar por número de reações + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Exemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +### Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +### Leia mais + +- "[Ordenar os resultados da pesquisa](/articles/sorting-search-results/)" diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index a392df187c..f71a73a793 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -203,7 +203,7 @@ Você pode usar o qualificador `comments` com os [qualificadores maior que, meno | Qualifier | Exemplo | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3C100&type=Issues) identifica os problemas fechados com mais de 100 comentários. | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) identifica os problemas fechados com mais de 100 comentários. | | | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) identifica os problemas com 500 a 1.000 comentários. | ### Pesquisar por número de interações diff --git a/translations/pt-BR/content/github/searching-for-information-on-github/searching-topics.md b/translations/pt-BR/content/github/searching-for-information-on-github/searching-topics.md index 9968a4eb78..6216c7b1e4 100644 --- a/translations/pt-BR/content/github/searching-for-information-on-github/searching-topics.md +++ b/translations/pt-BR/content/github/searching-for-information-on-github/searching-topics.md @@ -26,7 +26,7 @@ Se quiser explorar repositórios sobre um tópico específico, encontrar projeto O qualificador de pesquisa `is:featured` limita os resultados da pequisa aos tópicos com mais repositórios no {% data variables.product.product_name %}. Esses tópicos também são apresentados em https://github.com/topics/. -O qualificador de pesquisa `is:curated` limita os resultados da pequisa aos tópicos que os integrantes da comunidade adicionaram informações adicionais. Para obter mais informações, consulte o repositório explore em https://github.com/github/explore. +O qualificador de pesquisa `is:curated` limita os resultados da pequisa aos tópicos que os integrantes da comunidade adicionaram informações adicionais. For more information, see the [explore repository](https://github.com/github/explore). Você pode filtrar os tópicos com base na data de criação usando parâmetro de data e `created:` ou com base em quantos repositórios estão associados ao tópico usando `repositories:n`. Esses dois qualificadores podem usar os [qualificadores maior que, menor que e intervalo](/articles/understanding-the-search-syntax). diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index cec29aa9ed..48c1aef7d2 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -8,7 +8,9 @@ versions: ### Sobre a cobrança do {% data variables.product.prodname_actions %} -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} + +{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." Os minutos são reiniciados todos os meses, mas o uso do armazenamento não. @@ -69,8 +71,8 @@ Se uso de {% data variables.product.prodname_actions %} compartilha a data de co ### Sobre limites de gastos -Por padrão, sua conta terá um limite de gastos de $0 para o uso de {% data variables.product.prodname_actions %}. Para habilitar o uso de minutos e armazenamento para repositórios privados além dos valores incluídos em sua conta, você pode aumentar o limite de gastos ou permitir gastos ilimitados. Para obter mais informações, consulte "[Gerenciar seu limite de gastos para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)". +{% data reusables.github-actions.actions-spending-limit-detailed %} -{% data reusables.github-actions.spending-limit-enterprise-account %} +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 reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index b77d93457b..0acda75efa 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -10,6 +10,8 @@ versions: {% data reusables.package_registry.packages-billing %} +{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." + {% data reusables.package_registry.container-registry-beta-billing-note %} A transferência de dados é reiniciada todos os meses, mas o uso do armazenamento não. @@ -50,8 +52,8 @@ Se uso de {% data variables.product.prodname_registry %} compartilha a data de c ### Sobre limites de gastos -Por padrão, sua conta terá um limite de gastos de $0 para o uso de {% data variables.product.prodname_registry %}. Para habilitar a transferência de armazenamento e dados para pacotes privados além dos valores incluídos em sua conta, você pode aumentar o limite de gastos ou permitir gastos ilimitados. Para obter mais informações, consulte "[Gerenciar seu limite de gastos para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)". +{% data reusables.package_registry.packages-spending-limit-detailed %} -{% data reusables.package_registry.spending-limit-enterprise-account %} +For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md index 35ffe1950b..a89941adb1 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md @@ -9,6 +9,8 @@ versions: {% data reusables.sponsors.sponsorship-details %} +{% data reusables.sponsors.no-fees %} + {% data reusables.dotcom_billing.view-all-subscriptions %} ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index 35e7f2d440..05d1cd3926 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### Descontos para contas pessoais -Além de repositórios públicos e privados ilimitados para alunos e docentes com o {% data variables.product.prodname_free_user %}, os alunos confirmados podem se inscrever no {% data variables.product.prodname_student_pack %} para receber outros benefícios de parceiros do {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Inscrever-se em um pacote de desenvolvedor para estudante](/articles/applying-for-a-student-developer-pack)." +Além de repositórios públicos e privados ilimitados para alunos e docentes com o {% data variables.product.prodname_free_user %}, os alunos confirmados podem se inscrever no {% data variables.product.prodname_student_pack %} para receber outros benefícios de parceiros do {% data variables.product.prodname_dotcom %}. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." ### Descontos para escolas e universidades -Os docentes acadêmicos confirmados podem se inscrever na {% data variables.product.prodname_team %} para atividades de ensino ou pesquisa acadêmica. Para obter mais informações, consulte "[Usar o {% data variables.product.prodname_dotcom %} em sala de aula e pesquisa](/articles/using-github-in-your-classroom-and-research)". Também é possível solicitar brindes de material educacional para os alunos. Para obter mais informações, visite [{% data variables.product.prodname_education %}](https://education.github.com/). +Os docentes acadêmicos confirmados podem se inscrever na {% data variables.product.prodname_team %} para atividades de ensino ou pesquisa acadêmica. 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)." Também é possível solicitar brindes de material educacional para os alunos. Para obter mais informações, visite [{% data variables.product.prodname_education %}](https://education.github.com/). ### Descontos para organizações sem fins lucrativos e bibliotecas 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 2cd3cf9c54..973bef1568 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 @@ -7,24 +7,24 @@ versions: free-pro-team: '*' --- +{% 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 %} + ### Fazer downgrade de um patrocínio -Quando você faz downgrade de um patrocínio, a alteração entra em vigor na próxima data de cobrança. {% data reusables.sponsors.no-refunds %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. No lado direito da página, próximo ao nível selecionado, clique em **Edit** (Editar). ![Botão Edit tier (Editar nível)](/assets/images/help/billing/edit-tier-button.png) +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### Cancelar um patrocínio -Quando você cancela um patrocínio, a alteração entra em vigor na próxima data de cobrança. {% data reusables.sponsors.no-refunds %} - {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.billing %} +{% 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/managing-your-spending-limit-for-github-actions.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 505d458137..4cdd70f72c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -8,13 +8,15 @@ versions: ### Sobre sintaxe limites de gastos para o {% data variables.product.prodname_actions %} -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} -Você pode definir um limite de gastos mais alto ou, em algumas contas, permitir gastos ilimitados. Se você pagar a conta da organização ou empresa por fatura, você poderá pagar antecipadamente por excessos para definir um limite de despesas mais elevado. O limite de gastos aplica-se aos seus excessos conjuntos para {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %}. Para obter mais informações sobre preços para o uso de {% data variables.product.prodname_actions %}, consulte "[Sobre cobranças para o {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." +{% data reusables.github-actions.actions-spending-limit-brief %} -Assim que você definir um limite de gastos acima de $0, você será responsável por quaisquer excessos ocorridos no passado. Por exemplo, se a sua organização usa o {% data variables.product.prodname_team %}, não permite excessos, e cria artefatos de fluxo de trabalho que aumentam seu uso de armazenamento para o mês de 1.9GB para 2.1GB, você usará um pouco mais de armazenamento do que os 2GB que seu produto inclui. +{% 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)." -Como você não ativou os excessos, sua próxima tentativa de publicar uma versão do pacote irá falhar. Você não receberá uma fatura pelo excesso de 0.1GB naquele mês. No entanto, se você habilitar excessos em um mês futuro, sua primeira fatura incluirá o 0.1 GB de excesso do passado, além de qualquer excesso para o ciclo de faturamento atual. +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. Por exemplo, se a sua organização usa o {% data variables.product.prodname_team %}, não permite excessos, e cria artefatos de fluxo de trabalho que aumentam seu uso de armazenamento para o mês de 1.9GB para 2.1GB, você usará um pouco mais de armazenamento do que os 2GB que seu produto inclui. + +Because you have not enabled overages, your next attempt to create a workflow artifact will fail. Você não receberá uma fatura pelo excesso de 0.1GB naquele mês. 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. ### Gerenciando o limite de gastos de {% data variables.product.prodname_actions %} para sua conta de usuário @@ -30,8 +32,6 @@ Qualquer pessoa pode gerenciar o limite de gastos do {% data variables.product.p Proprietários de organizações e gestores de faturamento podem gerenciar o limite de gastos de {% data variables.product.prodname_actions %} para uma organização. -Se você pagar pela conta da organização por fatura, você não poderá gerenciar o limite de gastos para a conta corporativa em {% data variables.product.product_name %}. Se desejar permitir que repositórios pertencentes à sua organização usem o {% data variables.product.prodname_actions %} além do armazenamento ou a transferência de dados incluída em cada repositório, você pode efetuar um pré-pagamento por excessos. Como os excessos devem ser pagos antecipadamente, você não pode permitir gastos ilimitados em contas pagas por fatura. Seu limite de gastos será de 150% do valor que você pagou antecipadamente. Se tiver alguma dúvida, [entre em contato com nossa equipe de gerenciamento de conta](https://enterprise.github.com/contact). - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ Se você pagar pela conta da organização por fatura, você não poderá gerenc Proprietários de organizações e gestores de faturamento podem gerenciar o limite de gastos de {% data variables.product.prodname_actions %} para uma conta corporativa. -{% data reusables.github-actions.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 0ece59b577..6334ab2cea 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -10,11 +10,13 @@ versions: {% data reusables.package_registry.packages-billing %} -Você pode definir um limite de gastos mais alto ou, em algumas contas, permitir gastos ilimitados. Se você pagar a conta da organização ou empresa por fatura, você poderá pagar antecipadamente por excessos para definir um limite de despesas mais elevado. O limite de gastos aplica-se aos seus excessos conjuntos para {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %}. Para obter mais informações sobre preços para o uso de {% data variables.product.prodname_registry %}, consulte "[Sobre cobranças para o {% 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-spending-limit-brief %} -Assim que você definir um limite de gastos acima de $0, você será responsável por quaisquer excessos ocorridos no passado. Por exemplo, se a sua organização usa o {% data variables.product.prodname_team %}, não permite excessos, e publica uma nova versão de um pacote privado que aumenta seu uso de armazenamento para o mês de 1.9GB para 2.1GB, a publicar a versão, você usará um pouco mais de armazenamento do que os 2GB que seu produto inclui. +{% 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)." -Como você não ativou os excessos, sua próxima tentativa de publicar uma versão do pacote irá falhar. Você não receberá uma fatura pelo excesso de 0.1GB naquele mês. No entanto, se você habilitar excessos em um mês futuro, sua primeira fatura incluirá o 0.1 GB de excesso do passado, além de qualquer excesso para o ciclo de faturamento atual. +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. Por exemplo, se a sua organização usa o {% data variables.product.prodname_team %}, não permite excessos, e publica uma nova versão de um pacote privado que aumenta seu uso de armazenamento para o mês de 1.9GB para 2.1GB, a publicar a versão, você usará um pouco mais de armazenamento do que os 2GB que seu produto inclui. + +Como você não ativou os excessos, sua próxima tentativa de publicar uma versão do pacote irá falhar. Você não receberá uma fatura pelo excesso de 0.1GB naquele mês. 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. ### Gerenciando o limite de gastos de {% data variables.product.prodname_registry %} para sua conta de usuário @@ -30,8 +32,6 @@ Qualquer pessoa pode gerenciar o limite de gastos do {% data variables.product.p Proprietários de organizações e gestores de faturamento podem gerenciar o limite de gastos de {% data variables.product.prodname_registry %} para uma organização. -Se você pagar pela conta da organização por fatura, você não poderá gerenciar o limite de gastos para a conta corporativa em {% data variables.product.product_name %}. Se desejar permitir que repositórios pertencentes à sua organização usem o {% data variables.product.prodname_registry %} além do armazenamento ou da transferência de dados incluída em cada repositório, você pode efetuar um pré-pagamento por excessos. Como os excessos devem ser pagos antecipadamente, você não pode permitir gastos ilimitados em contas pagas por fatura. Seu limite de gastos será de 150% do valor que você pagou antecipadamente. Se tiver alguma dúvida, [entre em contato com nossa equipe de gerenciamento de conta](https://enterprise.github.com/contact). - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ Se você pagar pela conta da organização por fatura, você não poderá gerenc Proprietários de organizações e gestores de faturamento podem gerenciar o limite de gastos de {% data variables.product.prodname_registry %} para uma conta corporativa. -{% data reusables.package_registry.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 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 15d37f9e65..d1df520918 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 @@ -7,12 +7,15 @@ versions: free-pro-team: '*' --- +{% data reusables.sponsors.org-sponsors-release-phase %} + +### About sponsorship upgrades + Quando você atualiza a camada do patrocínio, a alteração entra em vigor imediatamente. {% data reusables.sponsors.prorated-sponsorship %} -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. No lado direito da página, próximo ao nível selecionado, clique em **Edit** (Editar). ![Botão Edit tier (Editar nível)](/assets/images/help/billing/edit-tier-button.png) +### Atualizar um patrocínio + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.update-sponsorship %} +{% data reusables.sponsors.update-sponsorship %} \ No newline at end of file diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md index fc3639035d..b6edad6a2a 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md @@ -20,7 +20,7 @@ versions: ### 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, verifique se que você tem na conta uma cópia de todos os repositórios, wikis e problemas. +Depois que você exclui uma organização, o GitHub **não pode restaurar o conteúdo que você tem lá**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. ### 2. Excluir a organização diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md index 578b0122ca..a1494e70d4 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -19,4 +19,4 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.oauth_app_access %} 5. 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 Remove confirmation button (Remover botão de confirmação)](/assets/images/help/settings/settings-third-party-confirm-disable.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). ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md index 2940a02758..db435ffb35 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -20,42 +20,30 @@ versions: {% link_in_list /creating-a-new-organization-from-scratch %} {% link_in_list /accessing-your-organizations-settings %} {% link_in_list /about-your-organizations-news-feed %} - {% link_in_list /viewing-insights-for-your-organization %} - {% topic_link_in_list /managing-membership-in-your-organization %} - {% link_in_list /inviting-users-to-join-your-organization %} {% link_in_list /canceling-or-editing-an-invitation-to-join-your-organization %} {% link_in_list /adding-people-to-your-organization %} - {% link_in_list /removing-a-member-from-your-organization %} {% link_in_list /reinstating-a-former-member-of-your-organization %} - {% link_in_list /can-i-create-accounts-for-people-in-my-organization %} - {% topic_link_in_list /managing-peoples-access-to-your-organization-with-roles %} {% link_in_list /permission-levels-for-an-organization %} {% link_in_list /maintaining-ownership-continuity-for-your-organization %} {% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %} - {% link_in_list /adding-a-billing-manager-to-your-organization %} {% link_in_list /removing-a-billing-manager-from-your-organization %} - {% topic_link_in_list /organizing-members-into-teams %} {% link_in_list /about-teams %} {% link_in_list /creating-a-team %} {% link_in_list /setting-your-teams-profile-picture %} {% link_in_list /adding-organization-members-to-a-team %} - {% link_in_list /managing-code-review-assignment-for-your-team %} - {% link_in_list /renaming-a-team %} {% link_in_list /changing-team-visibility %} - {% link_in_list /synchronizing-a-team-with-an-identity-provider-group %} - {% link_in_list /moving-a-team-in-your-organizations-hierarchy %} {% link_in_list /requesting-to-add-a-child-team %} {% link_in_list /requesting-to-add-or-change-a-parent-team %} @@ -66,9 +54,7 @@ versions: {% topic_link_in_list /managing-access-to-your-organizations-repositories %} {% link_in_list /repository-permission-levels-for-an-organization %} {% link_in_list /setting-base-permissions-for-an-organization %} - {% link_in_list /viewing-people-with-access-to-your-repository %} - {% link_in_list /managing-an-individuals-access-to-an-organization-repository %} {% link_in_list /managing-team-access-to-an-organization-repository %} {% link_in_list /adding-outside-collaborators-to-repositories-in-your-organization %} @@ -84,83 +70,54 @@ versions: {% link_in_list /managing-an-individuals-access-to-an-organization-project-board %} {% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %} {% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %} - {% topic_link_in_list /managing-access-to-your-organizations-apps %} {% link_in_list /adding-github-app-managers-in-your-organization %} {% link_in_list /removing-github-app-managers-from-your-organization %} - {% topic_link_in_list /managing-organization-settings %} - {% link_in_list /verifying-your-organizations-domain %} - {% link_in_list /renaming-an-organization %} {% link_in_list /transferring-organization-ownership %} {% link_in_list /restricting-repository-creation-in-your-organization %} {% link_in_list /setting-permissions-for-deleting-or-transferring-repositories %} {% link_in_list /restricting-repository-visibility-changes-in-your-organization %} {% link_in_list /managing-the-forking-policy-for-your-organization %} - {% link_in_list /disabling-or-limiting-github-actions-for-your-organization %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization %} - - {% link_in_list /setting-permissions-for-adding-outside-collaborators %} - {% link_in_list /allowing-people-to-delete-issues-in-your-organization %} - - + {% link_in_list /allowing-people-to-delete-issues-in-your-organization %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /managing-discussion-creation-for-repositories-in-your-organization %}{% endif %} {% link_in_list /setting-team-creation-permissions-in-your-organization %} - - {% link_in_list /managing-scheduled-reminders-for-your-organization %} - - {% link_in_list /managing-the-default-branch-name-for-repositories-in-your-organization %} - - {% link_in_list /managing-default-labels-for-repositories-in-your-organization %} - - {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} - - {% link_in_list /managing-the-display-of-member-names-in-your-organization %} - + {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} - {% link_in_list /integrating-jira-with-your-organization-project-board %} - - {% link_in_list /upgrading-to-the-corporate-terms-of-service %} - {% topic_link_in_list /migrating-to-improved-organization-permissions %} {% link_in_list /converting-an-owners-team-to-improved-organization-permissions %} {% link_in_list /converting-an-admin-team-to-improved-organization-permissions %} {% link_in_list /migrating-admin-teams-to-improved-organization-permissions %} - {% topic_link_in_list /restricting-access-to-your-organizations-data %} {% link_in_list /about-oauth-app-access-restrictions %} {% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /approving-oauth-apps-for-your-organization %} {% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %} - {% topic_link_in_list /keeping-your-organization-secure %} {% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %} {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} - {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} {% link_in_list /managing-secret-scanning-for-your-organization %} - {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} - {% link_in_list /restricting-email-notifications-to-an-approved-domain %} - {% link_in_list /reviewing-the-audit-log-for-your-organization %} {% link_in_list /reviewing-your-organizations-installed-integrations %} - {% topic_link_in_list /managing-saml-single-sign-on-for-your-organization %} {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} {% link_in_list /about-scim %} @@ -170,17 +127,12 @@ versions: {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} {% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %} - {% link_in_list /managing-team-synchronization-for-your-organization %} - {% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %} {% topic_link_in_list /granting-access-to-your-organization-with-saml-single-sign-on %} {% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %} {% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %} - - {% topic_link_in_list /managing-git-access-to-your-organizations-repositories %} {% link_in_list /about-ssh-certificate-authorities %} {% link_in_list /managing-your-organizations-ssh-certificate-authorities %} - diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..2c4efbef23 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Managing discussion creation for repositories in your organization +intro: You can choose the permission levels that members require to create discussions in repositories owned by your organization. +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Allowing or disallowing users with read access to create discussions + +By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. Clique em **Salvar**. !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png) + +### Leia mais + +- "[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/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index 51c58a7724..373a6aa0f8 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -9,29 +9,39 @@ versions: ### 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. - {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% endif %} - -### Habilitar ou desabilitar recursos para repositórios existentes +### 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 %} -5. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -6. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -7. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização. ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) -### Habilitar ou desabilitar recursos para novos repositórios +The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. + +### Enabling or disabling a feature for all existing repositories + +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. Em "Configurar recursos de segurança e análise" à direita do recurso, clique em **Desabilitar tudo** ou **Habilitar tudo**. ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) +1. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão. ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) +1. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização. ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + +### Enabling or disabling a feature for all new repositories when they are added + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Em "Configurar recursos de segurança e análise", à direita do recurso, habilite ou desabilite o recurso por padrão para novos repositórios na sua organização. ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + +### Allowing Dependabot to access private repositories + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) +1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. +1. Click **Select repositories**. -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. Em "Configurar recursos de segurança e análise", à direita do recurso, habilite ou desabilite o recurso por padrão para novos repositórios na sua organização. ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..3c299456e6 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,23 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +--- + +{% 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. 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. 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. Clique em **Update profile** (Atualizar perfil). ![Botão Update profile (Atualizar perfil)](/assets/images/help/organizations/update-profile-button.png) + +### Leia mais + +- "[Supporting the open source community with {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors)" \ No newline at end of file diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index df986ffaf5..85584e4752 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -55,6 +55,9 @@ Os integrantes da organização podem ter funções de *proprietário*{% if curr | 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** | | |{% if currentVersion == "free-pro-team@latest" %} | 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** | | |{% endif %} | 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** | | | +| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | Desabilitar a publicação de sites do {% data variables.product.prodname_pages %} em repositórios na organização (consulte "[Desabilitar a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" para obter 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](/github/setting-up-and-managing-organizations-and-teams/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** | | | diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 0eec265fd8..11a1b19126 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -114,7 +114,19 @@ Além de gerenciar as configurações da organização, os proprietários da org | [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** | +| Criar referências de link automático para recursos externos, como JIRA ou Zendesk (consulte "[Configurar links automáticos para apontar para recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Criar [consultorias de segurança](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [Lista, descarta e exclui alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} ### Leia mais diff --git a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 1c3a69af50..fcb5bd5ba7 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -81,7 +81,9 @@ Each category has a set of associated actions that you can filter on. For exampl Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} -{% data reusables.search.date_gt_lt %} For example: +{% data reusables.search.date_gt_lt %} + +For example: * `created:2014-07-08` finds all events that occurred on July 8th, 2014. * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. @@ -105,25 +107,53 @@ Using the qualifier `country`, you can filter events in the audit log based on t {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -### Using the Audit log API +### 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 API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} +**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 API to keep copies of your audit log data and monitor: -* Access to your organization or repository settings. -* Changes in permissions. -* Added or removed users in an organization, repository, or team. -* Users being promoted to admin. -* Changes to permissions of a GitHub App. +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. +{% 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 as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +{% 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)" in the REST API documentation. + +{% endif %} + ### Audit log actions An overview of some of the most common actions that are recorded as events in the audit log. @@ -213,6 +243,28 @@ An overview of some of the most common actions that are recorded as events in th | `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). +{% 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. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| Action | Description +|---------|---------------------------- +| `clone` | Triggered when a repository is cloned. +| `fetch` | Triggered when changes are fetched from a repository. +| `push` | Triggered when changes are pushed to a repository. + +{% endif %} + #### `hook` category actions | Action | Description @@ -500,8 +552,20 @@ For more information, see "[Restricting publication of {% data variables.product | 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)") +| `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 organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") +| 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 %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 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 839d95ba87..22b05410df 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 @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and{% endif %}private repositories, with specific details of your activity in private repositories anonymized. Para obter mais informações, consulte "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. Para obter mais informações, consulte "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". {% note %} 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 6ce7743d9f..352849bd57 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 @@ -14,6 +14,7 @@ versions: {% topic_link_in_list /managing-user-account-settings %} {% link_in_list /about-your-personal-dashboard %} + {% link_in_list /managing-your-theme-settings %} {% link_in_list /changing-your-github-username %} {% link_in_list /merging-multiple-user-accounts %} {% link_in_list /converting-a-user-into-an-organization %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md new file mode 100644 index 0000000000..eab669c1f6 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -0,0 +1,22 @@ +--- +title: Managing your theme settings +intro: You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode. +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Theme settings is currently in beta and subject to change. + +{% endnote %} + +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. + +{% data reusables.user_settings.access_settings %} +1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) + +### Leia mais + +- "[Configurar tema para o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md b/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md index 4321e8fb88..49a1a976b3 100644 --- a/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md +++ b/translations/pt-BR/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -Entrada em vigor desta versão: 13 de novembro de 2020 +Version Effective Date: December 14, 2020 Quando você cria uma Conta, tem acesso a vários recursos e produtos diferentes que fazem parte do Serviço. Como muitos desses recursos e produtos oferecem diferentes funcionalidades, eles podem exigir termos e condições adicionais específicos para esse recurso ou produto. Abaixo, listamos esses recursos e produtos, juntamente com os termos adicionais correspondentes que se aplicam ao uso deles. @@ -46,13 +46,11 @@ O GitHub Pages está sujeito a limites específicos de uso e largura de banda e ### 5. Ações e Pacotes #### a. Uso das Ações -As Ações GitHub permitem criar fluxos de trabalho personalizados do ciclo de vida de desenvolvimento de softwares diretamente no seu repositório GitHub. Cada Conta vem com quantidades de computação e armazenamento incluídas para uso com Ações, dependendo do seu plano de conta, que podem ser encontradas na [documentação de Ações](/actions). O uso de computação de suas Ações está disponível em [suas configurações da sua Conta](https://github.com/settings/billing), e você será notificado por e-mail antes de atingir o limite das quantidades incluídas. Se você deseja usar ações além das quantidades incluídas, poderá [permitir excedentes](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions). +GitHub Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. -O uso da computação para quantidades incluídas e pagas é calculado em minutos, com base no tipo de Ações que você executa (por exemplo, Linux, Windows, macOS). Os minutos usados ​​para cada trabalho ou tarefa da Ação serão arredondados para o minuto mais próximo. Para quantidades incluídas e dependendo do tipo de Ação, um multiplicador pode ser aplicado à quantidade de tempo usada para executar cada tarefa ou trabalho, antes de ser arredondada para o minuto mais próximo. Minutos excedentes são cobrados na [base de preço por minuto](https://github.com/features/actions) nos tipos de Ações que você executa. Ações e Pacotes compartilham armazenamento e seu uso de armazenamento é mostrado nas [configurações de conta](https://github.com/settings/billing). Para obter informações adicionais sobre os cálculos de uso de quantidade incluída, consulte a [documentação de Ações](/actions). - -Ações e quaisquer elementos do serviço de Ação não podem ser usados ​​em violação ao Acordo, à [Política de Uso Aceitável](/github/site-policy/github-acceptable-use-policies), ou às [limitações de serviço](/actions/reference/usage-limits-billing-and-administration/#usage-limits) das Ações do GitHub. Além disso, as Ações não devem ser usadas para: +Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions). Além disso, as Ações não devem ser usadas para: - mineração de criptomoedas; -- usar nossos servidores para interromper ou ganhar ou tentar ganhar acesso não autorizado a qualquer serviço, dispositivo, dados, conta ou rede (a menos que autorizado pelo [programa GitHub Bug Bounty](https://bounty.github.com)) +- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); - fornecimento de um aplicativo ou serviço independente ou integrado que ofereça Ações ou quaisquer elementos de Ações para fins comerciais; - qualquer atividade que coloque um peso em nossos servidores, em que esse peso é desproporcional aos benefícios oferecidos aos usuários (por exemplo, não usar Ações como uma rede de entrega de conteúdo ou como parte de um aplicativo sem servidor, mas uma Ação de baixo benefício pode ser realizada se também tiver um peso baixo); ou - qualquer outra atividade não relacionada à produção, teste, implantação ou publicação do projeto de software associado ao repositório onde as Ações do GitHub são usadas. @@ -60,16 +58,7 @@ Ações e quaisquer elementos do serviço de Ação não podem ser usados ​​ Para evitar violações dessas limitações e abuso de Ações do GitHub, o GitHub pode monitorar seu uso das Ações do GitHub. O uso indevido de Ações do GitHub pode resultar no encerramento de trabalhos ou restrições na sua capacidade de usar as Ações do GitHub. #### b. Uso do pacotes -Os Pacotes GitHub podem ser usados ​​para baixar, publicar e gerenciar pacotes de Conteúdo. Cada plano de Conta vem com uma largura de banda e quantidade de armazenamento incluídos para o uso com Pacotes, que podem ser encontrados na [documentação dos Pacotes](/github/managing-packages-with-github-package-registry/about-github-package-registry). Ações e Pacotes compartilham o armazenamento entre dois recursos de Serviço. O armazenamento e o uso da largura de banda são exibidos dentro de suas [configurações de conta](https://github.com/settings/billing), e você será notificado por e-mail antes de atingir o limite de suas quantidades incluídas. Se você quiser usar Pacotes além de suas quantidades de largura de banda e armazenamento incluídos, então você pode [permitir excedentes](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages). - -O uso da largura de banda é calculado com base na quantidade de dados transferidos de seus repositórios por meio de Pacotes, mas as transferências de pacote por meio de Ações não contarão para suas quantidades incluídas ou pagas. O uso da largura de banda dos pacotes é limitado pela [Política de Uso Aceitável](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use), e a quantidade de largura de banda incluída é determinada por seu [plano de Conta](https://github.com/pricing). - -O uso de armazenamento pelas Ações e Pacotes é compartilhado entre os dois recursos de Serviço. O uso do armazenamento é calculado como uma média ponderada ao longo do mês e não é redefinido a cada mês. Os repositórios públicos e privados têm diferentes quantidades de armazenamento incluídas, e as quantidades incluídas para repositórios privados dependem de seu [plano de Conta](https://github.com/pricing). - -#### c. Pagamento e Faturamento para Ações e Pacotes -O faturamento de Ações e Pacotes é baseado no uso. Quantidades adicionais de Ações ou Pacotes não podem ser adquiridos separadamente. Para clientes com cobrança mensal, é necessário ter um método de pagamento registrado para optar por pagar por quantidades adicionais desses recursos do Serviço. Você será cobrado mensalmente, com base no seu uso no mês anterior, a menos que seja cobrado por fatura. Para clientes faturados, você deve pagar as taxas no prazo de trinta (30) dias a contar da data da fatura do GitHub. Para os clientes que pagam antecipadamente os excedentes dos recursos de Serviço, os minutos pré-pagos não utilizados não serão transferidos para o próximo período de cobrança e não serão reembolsados. - -Você pode definir um limite mensal de gastos em suas [configurações de conta](https://github.com/settings/billing/cost_management). Você será notificado por e-mail antes de atingir o limite das quantidades incluídas e o limite de gastos designado das suas quantidades adicionais pagas. +GitHub Packages is billed on a usage basis. The [Packages documentation](/packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies). ### 6. Learning Lab @@ -108,3 +97,13 @@ Precisamos do direito de submeter suas contribuições para o Banco de Dados Con #### b. Licença para o Banco de Dados Consultivo GitHub O Banco de Dados Consultivo GitHub está licenciado sob a [licença 4.0 Creative Commons Attribution](https://creativecommons.org/licenses/by/4.0/). O termo de atribuição pode ser cumprido linkando para o Banco de Dados Consultivo do GitHub em ou para registros individuais do Banco de Dados Consultivo do GitHub usado e prefixado por . + +### 13. GitHub Enterprise Server + +#### a. SQL Server Images + +You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. A Microsoft Corporation pode desativar o SQL Server Images a qualquer momento. + +#### b. Third-party components + +O Software inclui componentes licenciados para o GitHub por terceiros, como programas de software cujas licenças exigem que o GitHub disponibilize o código-fonte desses componentes, que será fornecido mediante solicitação. 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 4d9b5211e7..d2c46ae272 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 @@ -191,7 +191,7 @@ Os Afiliados do Cliente estão autorizados a utilizar os Produtos de acordo com #### 1. Preços; Taxas -**Condições de Pagamento** Os preços estão disponíveis em [github.com/pricing](https://github.com/pricing) (a menos que o contrário seja negociado pelas partes e indicado em um Formulário de Pedido). O Cliente concorda em pagar as Taxas na íntegra, antecipadamente e sem dedução ou compensação de qualquer tipo, em dólares americanos. Dólar. O Cliente deve pagar as Taxas dentro de 30 (trinta) dias da data da fatura do GitHub. Os montantes a pagar ao abrigo deste Contrato não podem ser reembolsados, exceto se for o caso previsto neste Contrato. Se o Cliente não pagar nenhuma Taxa dentro do vencimento, o GitHub reserva o direito, para além de qualquer outra ação ou medida prevista em lei, a (i) cobrar juros sobre os montantes vencidos a 1% ao mês ou a taxa de juros mais alta permitida por lei, a que for menor, e cobrar todas as despesas de cobrança, e (ii) encerrar o Formulário de Pedido ou SOW aplicável. O Cliente é o único responsável por todos os impostos, taxas, deveres e avaliações governamentais (exceto impostos baseados no lucro líquido do GitHub) que sejam instituídos ou passem a ser devidos em relação a este Contrato. +**Condições de Pagamento** Os preços estão disponíveis em [github.com/pricing](https://github.com/pricing) (a menos que o contrário seja negociado pelas partes e indicado em um Formulário de Pedido). O Cliente concorda em pagar as Taxas na íntegra, antecipadamente e sem dedução ou compensação de qualquer tipo, em dólares americanos. Dólar. O Cliente deve pagar as Taxas dentro de 30 (trinta) dias da data da fatura do GitHub. Os montantes a pagar ao abrigo deste Contrato não podem ser reembolsados, exceto se for o caso previsto neste Contrato. Se o Cliente não pagar alguma Taxa dentro do prazo, o GitHub se reserva o direito de, além de tomar qualquer outra providência na lei ou na justiça, (i) cobrar juros sobre os montantes devidos de 1,0% ao mês ou a maior taxa de juros permitida por lei, o que for menor, e cobrar todas as despesas de recuperação, e (II) rescindir o Formulário de pedido ou a SOW (Statement of Work, Proposta de Serviço) aplicável. O Cliente é o único responsável por todos os impostos, taxas, deveres e avaliações governamentais (exceto impostos baseados no lucro líquido do GitHub) que sejam instituídos ou passem a ser devidos em relação a este Contrato. **Pagamento com Base no Uso** Alguns recursos de Serviço são cobrados com base no seu uso. Uma quantidade limitada destes recursos de Serviço pode ser incluída no seu plano por um termo limitado sem custos adicionais. Se você optar por comprar recursos de Serviço pagos além da quantidade incluída no seu plano, você paga por esses recursos de Serviço com base no seu uso real no mês anterior. O pagamento mensal em atraso desses pedidos será cobrado periodicamente, contanto que para clientes faturados. Recursos de Serviço pago são cobrados com antecedência. Veja [Termos do Produto Adicionais GitHub para mais detalhes](/github/site-policy/github-additional-product-terms). diff --git a/translations/pt-BR/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/pt-BR/content/github/site-policy/github-enterprise-service-level-agreement.md index 5bef77e454..28dfb96df6 100644 --- a/translations/pt-BR/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/pt-BR/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -8,22 +8,22 @@ versions: free-pro-team: '*' --- -**Versão curta:** O GitHub garante um compromisso de 99,8% de tempo de atividade trimestral para o serviço de nuvem do GitHub Enterprise (o “**Nível de Serviço**ou “**SLA**”). Se o GitHub não atender ao SLA, o Cliente terá direito a um crédito de serviço para a conta do Cliente (“**Créditos de Serviço**"). +**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the applicable GitHub service (the “**Service Level**” or “**SLA**”). Se o GitHub não atender ao SLA, o Cliente terá direito a um crédito de serviço para a conta do Cliente (“**Créditos de Serviço**"). -Para definições de cada recurso de serviço (“**Recurso de serviço**”) e para revisar a versão histórica e atual, acesse a [Página de Status do GitHub](https://www.githubstatus.com/). Os termos em maiúsculas usados, mas não definidos neste SLA, têm o significado atribuído ao contrato aplicável do cliente. +For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Os termos em maiúsculas usados, mas não definidos neste SLA, têm o significado atribuído ao contrato aplicável do cliente. ## Garantia de tempo de atividade -“**Tempo de atividade**” é a porcentagem do total de minutos possíveis que o Serviço estava disponível em um determinado trimestre. O GitHub compromete-se a manter um tempo de atividade de pelo menos 99,9% para o Serviço. O cálculo do tempo de atividade para cada Recurso de Serviço é descrito abaixo (“**Cálculo de Tempo de Atividade**"). Se o GitHub não atender ao SLA, O cliente terá direito a Créditos de Serviço com base no cálculo abaixo (“**Cálculo de Créditos de Serviço**"). Observe que o tempo de inatividade não afeta todos os clientes ao mesmo tempo ou da mesma forma. +“**Uptime**” is the percentage of total possible minutes the applicable GitHub service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service. The Uptime calculation for each Service Feature that may be included with the applicable GitHub service is described below (“**Uptime Calculation**”). Se o GitHub não atender ao SLA, O cliente terá direito a Créditos de Serviço com base no cálculo abaixo (“**Cálculo de Créditos de Serviço**"). Observe que o tempo de inatividade não afeta todos os clientes ao mesmo tempo ou da mesma forma. -| **Recurso de serviço** | **Cálculo do tempo de atividade** | **Definições** | **Cálculo dos créditos de serviço** | -| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -| O **serviço** inclui os recursos de serviço a seguir:
      • Problemas
      • Pull Requests
      • Operações do Git
      • Solicitações da API
      • Webhooks
      • Pages
      • Ações
      • Pacotes
      | (total de minutos em um trimestre do calendário - tempo de inatividade) / total de minutos em um trimestre do calendário | “**Tempo de inatividade**” é um período de tempo em que (a) a taxa de erro excede 5% (cinco por cento) em um dado minuto para qualquer Recurso de Serviço ou (b) o Serviço ficou indisponível conforme determinado por uma combinação de sistemas de monitoramento interno e externo do GitHub. | Uma reivindicação de Serviço Créditos pode ser baseada em qualquer um (não em ambos) dos seguintes cálculos:
      • 10% do montante que o Cliente pagou por um recurso de serviço em um trimestre de calendário, em que o tempo de atividade para este recurso de serviço foi inferior ou igual a 99,9%, mas superior a 99,0%.

        OU

      • 25% do montante que o Cliente pagou por um recurso de serviço em um trimestre do calendário, em que o tempo de atividade foi inferior a 99,0%.
      | | -| **Ações** | (Total de Execuções Acionadas – Execuções Indisponíveis) / (Total de Execuções Acionadas) x 100 | “**Total de execuções acionadas**” é o número total de todas as execuções de ações acionadas pelo Cliente em um trimestre do calendário.

      “**Execuções Indisponíveis**" é o número total de execuções no Total de Execuções Acionadas que não foram executadas em um trimestre da agenda. Falha ao executar uma execução quando o registro do histórico de ações não capturou nenhuma saída 5 (cinco) minutos após o gatilho ter sido acionado com sucesso. | Igual ao de acima | -| **Pacotes** | Tempo de atividade de transferência = mesmo que ações

      Tempo de atividade de armazenamento = 100% - Taxa média de erro*

      *O cálculo do tempo de atividade exclui o uso público e as transações de armazenamento que não contam nem para Transações de Armazenamento Total ou Transações com falha de Armazenamento (incluindo falhas de pré-autenticação; falhas de autenticação; tentativas de transações para contas de armazenamento acima das suas cotas prescritas). | “**Taxa de erro**" é o número total de Transações de Falhas de Armazenamento dividido pelas Transações Totais de Armazenamento durante um intervalo de tempo definido (definido atualmente em uma hora). Se as Transações de Armazenamento Total em um determinado intervalo de uma hora for zero, a taxa de erro para esse intervalo será 0%.

      “**Taxa de erro média**” é a soma das taxas de erro por cada hora em um trimestre do calendário dividido pelo número total de horas em um trimestre do calendário. | Igual ao de acima | +| **Recurso de serviço** | **Cálculo do tempo de atividade** | **Definições** | **Cálculo dos créditos de serviço** | +| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | +| **Issues**,
      **Pull Requests**,
      **Git Operations**,
      **API Requests**,
      **Webhooks**,
      **Pages** | (total de minutos em um trimestre do calendário - tempo de inatividade) / total de minutos em um trimestre do calendário | “**Tempo de inatividade**” é um período de tempo em que (a) a taxa de erro excede 5% (cinco por cento) em um dado minuto para qualquer Recurso de Serviço ou (b) o Serviço ficou indisponível conforme determinado por uma combinação de sistemas de monitoramento interno e externo do GitHub. | Uma reivindicação de Serviço Créditos pode ser baseada em qualquer um (não em ambos) dos seguintes cálculos:
      • 10% do montante que o Cliente pagou por um recurso de serviço em um trimestre de calendário, em que o tempo de atividade para este recurso de serviço foi inferior ou igual a 99,9%, mas superior a 99,0%.

        OU

      • 25% do montante que o Cliente pagou por um recurso de serviço em um trimestre do calendário, em que o tempo de atividade foi inferior a 99,0%.
      | | +| **Ações** | (Total de Execuções Acionadas – Execuções Indisponíveis) / (Total de Execuções Acionadas) x 100 | “**Total de execuções acionadas**” é o número total de todas as execuções de ações acionadas pelo Cliente em um trimestre do calendário.

      “**Execuções Indisponíveis**" é o número total de execuções no Total de Execuções Acionadas que não foram executadas em um trimestre da agenda. Falha ao executar uma execução quando o registro do histórico de ações não capturou nenhuma saída 5 (cinco) minutos após o gatilho ter sido acionado com sucesso. | Igual ao de acima | +| **Pacotes** | Tempo de atividade de transferência = mesmo que ações

      Tempo de atividade de armazenamento = 100% - Taxa média de erro*

      *O cálculo do tempo de atividade exclui o uso público e as transações de armazenamento que não contam nem para Transações de Armazenamento Total ou Transações com falha de Armazenamento (incluindo falhas de pré-autenticação; falhas de autenticação; tentativas de transações para contas de armazenamento acima das suas cotas prescritas). | “**Taxa de erro**" é o número total de Transações de Falhas de Armazenamento dividido pelas Transações Totais de Armazenamento durante um intervalo de tempo definido (definido atualmente em uma hora). Se as Transações de Armazenamento Total em um determinado intervalo de uma hora for zero, a taxa de erro para esse intervalo será 0%.

      “**Taxa de erro média**” é a soma das taxas de erro por cada hora em um trimestre do calendário dividido pelo número total de horas em um trimestre do calendário. | Igual ao de acima | ## Exclusões -São excluídos do Cálculo de Tempo de Atividade as falhas de recursos de serviço resultantes de (i) atos, omissões ou abuso do Serviço, incluindo violações do Contrato; (ii) falha na conexão à internet do Cliente; (iii) fatores fora do controle razoável do GitHub, incluindo eventos de força maior; ou (iv) equipamento do Cliente, serviços ou outra tecnologia. +Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the applicable GitHub service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Serviço de resgate de crédito Se o GitHub não atender a este SLA, O cliente só poderá resgatar Créditos de Serviço mediante solicitação por escrito ao GitHub no prazo de 30 (trinta) dias a partir do final do trimestre do calendário. Solicitações por escrito de resgate de Créditos de serviço e Relatórios personalizados mensais ou trimestrais do GitHub Enterprise Cloud devem ser enviados para o [Suporte do GitHub](https://support.github.com/contact). diff --git a/translations/pt-BR/content/github/site-policy/github-registered-developer-agreement.md b/translations/pt-BR/content/github/site-policy/github-registered-developer-agreement.md index 48158a971c..0cecbcc3cf 100644 --- a/translations/pt-BR/content/github/site-policy/github-registered-developer-agreement.md +++ b/translations/pt-BR/content/github/site-policy/github-registered-developer-agreement.md @@ -86,7 +86,7 @@ Este Contrato é um acordo legal entre você ("você") e o GitHub, Inc. ("GitHub 13. **Direitos Proprietários** - Você concorda que o GitHub e seus licenciadores possuem todos os direitos, o título e o interesse na API, nos Materiais de Pré-Lançamento e em todos os outros produtos e serviços do GitHub; todas as informações e dados relacionados às suas configurações e combinações; e todas as modificações e trabalhos derivados de qualquer um dos itens mencionados acima. Você concorda em não remover, alterar, cobrir ou ofuscar quaisquer avisos de direitos autorais ou outros direitos proprietários que colocamos ou incorporamos na API, nos Materiais de Pré-lançamento ou em quaisquer outros produtos e serviços do GitHub. + Você concorda que o GitHub e seus licenciadores possuem todos os direitos, o título e o interesse na API, nos Materiais de Pré-Lançamento e em todos os outros produtos e serviços do GitHub; todas as informações e dados relacionados às suas configurações e combinações; e todas as modificações e trabalhos derivados de qualquer um dos itens mencionados acima. You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services. 14. **Usuários do Governo** 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 4925b36cf9..e8c74a55e7 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 @@ -9,7 +9,9 @@ versions: ### Sobre o {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.sponsorship-details %} {% 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)". +{% data reusables.sponsors.sponsorship-details %} + +{% 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)". {% data reusables.sponsors.you-can-be-a-sponsored-developer %} Para mais informações consulte "[Sobre {% data variables.product.prodname_sponsors %} para contribuidores de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" e "[Configurando {% 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)." @@ -25,7 +27,7 @@ Quando você se tornar um desenvolvedor patrocinado ou uma organização patroci {% endnote %} -O {% data variables.product.prodname_matching_fund %} visa beneficiar os membros da comunidade {% data variables.product.prodname_dotcom %} que desenvolvem softwares de código aberto que promovem as [{% data variables.product.prodname_dotcom %}Diretrizes da Comunidade](/github/site-policy/github-community-guidelines). Organizações patrocinadas não são elegíveis para {% data variables.product.prodname_matching_fund %}. +O {% data variables.product.prodname_matching_fund %} visa beneficiar os membros da comunidade {% data variables.product.prodname_dotcom %} que desenvolvem softwares de código aberto que promovem as [{% data variables.product.prodname_dotcom %}Diretrizes da Comunidade](/github/site-policy/github-community-guidelines). Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}. Para ser elegível para o {% data variables.product.prodname_matching_fund %}, você deve criar um perfil que atrairá uma comunidade que irá sustentar você a longo prazo. Para obter mais informações sobre criar um perfil forte, consulte "[Editando os detalhes de seu perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)". @@ -35,8 +37,6 @@ Para ser elegível para o {% data variables.product.prodname_matching_fund %}, v 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). -Atualmente, apenas usuários individuais podem patrocinar desenvolvedores e organizações. Se sua organização estiver interessada em patrocinar desenvolvedores, entre em contato por [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). - ### Leia mais - "[Patrocinando contribuidores de código aberto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" - "[Recebendo patrocínio através do {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)" diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md new file mode 100644 index 0000000000..57b1b5a4d6 --- /dev/null +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md @@ -0,0 +1,13 @@ +--- +title: Attributing sponsorships to your organization +intro: 'You can attribute the sponsorships paid by one of your organizations to another organization.' +versions: + free-pro-team: '*' +permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization. +--- + +1. Navigate to the organization whose sponsorships you want to attribute to another organization. +1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png) +1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png) +1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png) +1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md index c9b579f70b..9525f6ca64 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -13,38 +13,20 @@ versions: {% data reusables.sponsors.maximum-tier %} -### Adicionando uma camada ao seu perfil de desenvolvedor patrocinado +### Adicionar uma camada -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} -### Adicionando uma camada ao seu perfil de organização patrocinada +### Editing or retiring a tier -{% data reusables.sponsors.navigate-to-org-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 aposentando uma camada para o seu perfil de desenvolvedor patrocinado - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} - -### Editando ou aposentando uma camada para o seu perfil de organização patrocinada - -{% data reusables.sponsors.navigate-to-org-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 %} +{% data reusables.sponsors.retire-tier %} \ No newline at end of file diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md index ec58b9c1e0..76e12fb4fe 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md @@ -5,11 +5,13 @@ versions: free-pro-team: '*' --- -Para monitorar as alterações de seus patrocínios, como os cancelamentos no final de um período de pagamento, você pode criar webhooks para sua conta de usuário ou organização patrocinada. Quando você configurar um webhook para sua conta de usuário ou organização patrocinada, você receberá atualizações quando patrocínios forem criados, editados ou excluídos. Para obter mais informações, consulte o [`evento de patrocínio` de webhook](/webhooks/event-payloads/#sponsorship). +### About webhooks for events in your sponsored account -### Gerenciando webhooks para sua conta de usuário patrocinada +Para monitorar as alterações de seus patrocínios, como os cancelamentos no final de um período de pagamento, você pode criar webhooks para sua conta de usuário ou organização patrocinada. When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. Para obter mais informações, consulte o [`evento de patrocínio` de webhook](/webhooks/event-payloads/#sponsorship). -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +### Managing webhooks for events in your sponsored account + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-webhooks-tab %} {% data reusables.sponsors.add-webhook %} {% data reusables.sponsors.add-payload-url %} @@ -17,18 +19,4 @@ Para monitorar as alterações de seus patrocínios, como os cancelamentos no fi {% data reusables.sponsors.webhook-secret-token %} {% data reusables.sponsors.add-active-triggers %} {% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} - -### Gerenciando webhooks para sua organização patrocinada - -Os proprietários da organização podem configurar webhooks para uma organização patrocinada. - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-webhooks-tab %} -{% data reusables.sponsors.add-webhook %} -{% data reusables.sponsors.add-payload-url %} -{% data reusables.sponsors.webhook-content-formatting %} -{% data reusables.sponsors.webhook-secret-token %} -{% data reusables.sponsors.add-active-triggers %} -{% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} +{% data reusables.sponsors.manage-existing-webhooks %} \ No newline at end of file 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 b5a0852483..a2f37ed2bf 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 @@ -7,22 +7,15 @@ versions: free-pro-team: '*' --- +### About sponsorship updates + Seus patrocinadores podem escolher se querem receber atualizações sobre seu trabalho por e-mail. Para obter mais informações, consulte "[Gerenciar o patrocínio](/articles/managing-your-sponsorship)". -A atualização virá do endereço de e-mail principal da sua conta de usuário ou do endereço de e-mail da conta da organização `noreply@github.com`. 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 obter mais informações, consulte "[Setting your commit email address](/articles/setting-your-commit-email-address)." +For sponsored developer accounts, the update will come from your user account's primary email address. 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`. For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. Para obter mais informações, consulte "[Setting your commit email address](/articles/setting-your-commit-email-address)." -### Contactando patrocinadores da sua conta de usuário +### Entrar em contato com os patrocinadores -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.sponsors-updates-tab %} -{% data reusables.sponsors.draft-new-update %} -{% data reusables.sponsors.send-update-to-sponsors %} -{% data reusables.sponsors.write-sponsor-update %} -{% data reusables.sponsors.publish-sponsor-update %} - -### Contactando patrocinadores da sua organização - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.sponsors-updates-tab %} {% data reusables.sponsors.draft-new-update %} {% data reusables.sponsors.send-update-to-sponsors %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md index 15a3efb43d..e85a0cd300 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md @@ -10,30 +10,17 @@ versions: ### Sobre os perfis dos patrocinadores -Seu perfil do {% data variables.product.prodname_sponsors %} diz aos patrocinadores potenciais por que eles devem apoiá-lo. As pessoas veem seu perfil de patrocinador quando clicam no botão **Patrocinador** no seu perfil pessoal ou na organização. Recomendamos incluir as seguintes informações. +Seu perfil do {% data variables.product.prodname_sponsors %} diz aos patrocinadores potenciais por que eles devem apoiá-lo. People see your sponsor profile when they click the **Sponsor** button on your profile. Recomendamos incluir as seguintes informações. -- Trabalho de código aberto para o qual você contribui. -- Por que você está comprometido com o desenvolvimento de código aberto. +- Trabalho de código aberto para o qual você contribui +- Por que você está comprometido com o desenvolvimento de código aberto -Você também pode definir metas para explicar o que os diferentes níveis de patrocínio lhe permitirão fazer pela comunidade. +### Editing your profile details -### Editar seu perfil de desenvolvedor patrocinado - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### Editando seu perfil de organização patrocinada - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.meet-the-team %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} +{% data reusables.sponsors.save-profile %} \ No newline at end of file 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 e84acdcfef..7aa027fc52 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 @@ -16,6 +16,7 @@ versions: {% topic_link_in_list /sponsoring-open-source-contributors %} {% link_in_list /sponsoring-an-open-source-contributor %} {% link_in_list /managing-your-sponsorship %} + {% link_in_list /attributing-sponsorships-to-your-organization %} {% topic_link_in_list /receiving-sponsorships-through-github-sponsors %} {% link_in_list /about-github-sponsors-for-open-source-contributors %} {% link_in_list /setting-up-github-sponsors-for-your-user-account %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md index a630aee54d..169aec7b60 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md @@ -13,14 +13,8 @@ Só é possível gerenciar seus pagamentos {% data variables.product.prodname_sp {% data reusables.sponsors.payout-info %} -### Visualizando e editando informações de pagamento para sua conta de usuário patrocinado +### Viewing and editing payout information -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} - -### Visualizando e editando informações de pagamento para sua organização patrocinada - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} +{% data reusables.sponsors.edit-bank-information %} \ No newline at end of file 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 5fcf993951..80757c3bfc 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 @@ -1,27 +1,19 @@ --- title: Gerenciando sua meta de patrocínio -intro: Você pode definir uma meta para o seu desenvolvedor patrocinado ou para o perfil de organização patrocinada para ajudar a comunidade a entender o impacto de patrocinar você. +intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you. versions: free-pro-team: '*' --- ### Sobre metas de patrocínio -Você pode definir uma meta para seu desenvolvedor patrocinado ou perfil de organização e compartilhar a meta com sua comunidade. Metas ajudam você a entender o impacto que você tem na comunidade de código aberto e construir sua presença no programa {% data variables.product.prodname_sponsors %}. +You can set a funding goal for your sponsored account and share the goal with your community. Metas ajudam você a entender o impacto que você tem na comunidade de código aberto e construir sua presença no programa {% data variables.product.prodname_sponsors %}. 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. -### Estabelecendo uma meta para uma organização patrocinada +### Setting a goal -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.set-a-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### Estabelecendo uma meta para um desenvolvedor patrocinado - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.set-a-goal %} {% data reusables.sponsors.select-goal-type %} @@ -31,6 +23,7 @@ Sua meta pode definir um objetivo para o número de patrocinadores que você des Ao editar uma meta, você não pode escolher uma meta que já atingiu. Por exemplo, se você já tem 5 patrocinadores, você não pode editar sua meta buscando 4 patrocinadores. +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.select-goal-type %} @@ -40,6 +33,7 @@ Ao editar uma meta, você não pode escolher uma meta que já atingiu. Por exemp Depois de retirar uma meta, você não poderá reativá-la. Você deve criar uma nova meta em vez disso. +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.retire-goal %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md index 9e75ed96b7..dc253cf0d9 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -1,42 +1,35 @@ --- title: Gerenciar o patrocínio -intro: Você pode gerenciar quem pode ver o seu patrocínio e se você receberá atualizações por e-mail do contribuidor de código aberto patrocinado. +intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account. redirect_from: - /articles/managing-your-sponsorship versions: free-pro-team: '*' --- -Para obter informações sobre como alterar sua categoria de patrocínio, consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)". +{% data reusables.sponsors.org-sponsors-release-phase %} -### Gerenciamento da configuração de privacidade para seu patrocínio do desenvolvedor +### Gerenciar as configurações de privacidade para seu patrocínio -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} {% data reusables.sponsors.who-can-see-your-sponsorship %} {% data reusables.sponsors.update-sponsorship %} -### Gerenciamento da configuração de privacidade para seu patrocínio da organização +### Managing email updates for your sponsorship -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.who-can-see-your-sponsorship %} +You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address. + +{% data reusables.sponsors.manage-updates-for-orgs %} + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} +{% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.update-sponsorship %} -### Gerenciar atualizações por e-mail de um desenvolvedor patrocinado +### Leia mais -É possível escolher se um desenvolvedor patrocinado pode enviar atualizações por e-mail a você sobre o trabalho dele. O desenvolvedor patrocinado não terá acesso ao seu endereço de e-mail. - -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} -{% data reusables.sponsors.developer-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} - -### Gerenciamento de atualizações de e-mail de uma organização patrocinada - -Você pode escolher se uma organização patrocinada pode enviar por e-mail atualizações sobre o trabalho deles. A organização patrocinada não terá acesso ao seu endereço de e-mail. - -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.org-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} +- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" +- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)" \ No newline at end of file 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 9231e0ba4f..915fea6f35 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 @@ -25,7 +25,7 @@ Para se juntar ao {% data variables.product.prodname_sponsors %} como colaborado ### Preencher seu perfil de organização patrocinada -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ Para se juntar ao {% data variables.product.prodname_sponsors %} como colaborado {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% 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 %} @@ -54,7 +54,7 @@ Como organização patrocinada, você deve receber pagamentos em uma conta banc {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} Para obter mais informações sobre como configurar o Stripe Connect usando o Open Collective, consulte [Configurando {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) no Open Collective Docs. @@ -63,7 +63,7 @@ Para obter mais informações sobre como configurar o Stripe Connect usando o Op {% data reusables.sponsors.tax-form-information-org %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -75,7 +75,7 @@ Antes de sua organização se tornar uma organização patrocinada, você deve h ### Enviar seu aplicativo ao {% data variables.product.prodname_dotcom %} para aprovação -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %} {% data reusables.sponsors.github-review-app %} 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 abf574972b..8467b116e0 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 @@ -26,7 +26,7 @@ Se você tiver uma conta bancária em uma região aceita, o {% data variables.pr Depois de {% data variables.product.prodname_dotcom %} avaliar sua solicitação, você pode configurar o seu perfil de desenvolvedor patrocinado para que as pessoas possam começar a patrocinar você. -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ Depois de {% data variables.product.prodname_dotcom %} avaliar sua solicitação {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} @@ -54,14 +54,14 @@ Se você vive em uma região aceita, você pode seguir essas instruções para e {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} ### Enviando suas informações fiscais {% data reusables.sponsors.tax-form-information-dev %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -73,7 +73,7 @@ Antes de se tornar um desenvolvedor patrocinado, você deve habilitar a 2FA em s ### Enviar seu aplicativo ao {% data variables.product.prodname_dotcom %} para aprovação -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 4. Clique em **Request approval** (Solicitar aprovação). ![Botão Request approval (Solicitar aprovação)](/assets/images/help/sponsors/request-approval-button.png) {% data reusables.sponsors.github-review-app %} 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 9edd0800fc..19af563a9a 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 @@ -7,17 +7,32 @@ redirect_from: - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer versions: free-pro-team: '*' +permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization. --- -### Sobre os desenvolvedores e organizações patrocinados +{% data reusables.sponsors.org-sponsors-release-phase %} -{% data reusables.sponsors.sponsorship-details %} {% 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)". +### About sponsorships -Quando você patrocina um colaborador de código aberto, a alteração entra em vigor imediatamente. {% data reusables.sponsors.prorated-sponsorship %} +{% data reusables.sponsors.sponsorship-details %} -Se o colaborador de código aberto patrocinado retirar sua camada, ela permanecerá em vigor até você escolher uma camada diferente ou cancelar sua assinatura. Para obter mais informações, consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)". +You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons. +- Sustaining specific libraries that your organization's work depends on +- Investing in the ecosystem you rely on as a organization (such as blockchain) +- Developing brand awareness as an organization that values open source +- Thanking open source developers for building libraries that complement the product your organization offers -Se o colaborador de código aberto que você deseja patrocinar não tiver um desenvolvedor patrocinado ou perfil de organização, você pode incentivar o colaborador a criar um desenvolvedor ou perfil de organização patrocinado. 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)" e "[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)." +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). + +{% data 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)". + +When you sponsor an account using a credit card, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} + +{% data reusables.sponsors.manage-updates-for-orgs %} + +If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. Para obter mais informações, consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)". + +If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. 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)" e "[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)." {% data reusables.sponsors.sponsorships-not-tax-deductible %} @@ -27,30 +42,20 @@ Se o colaborador de código aberto que você deseja patrocinar não tiver um des {% endnote %} -### Patrocinar desenvolvedor +### Sponsoring an account -Antes de poder patrocinar um desenvolvedor, você deve ter um endereço de e-mail verificado. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address)". +Before you can sponsor an account, you must have a verified email address. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address)". -1. No {% data variables.product.product_name %}, navegue até o perfil da pessoa que deseja patrocinar. -2. No nome do desenvolvedor, clique em **Sponsor** (Patrocinar). ![Botão Sponsor (Patrocinar)](/assets/images/help/profile/sponsor-button.png) +1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor. +1. Navigate to your sponsorship dashboard for the account. + - To sponsor a developer, under the developer's name, click **Sponsor**. ![Botão Sponsor (Patrocinar)](/assets/images/help/profile/sponsor-button.png) + - To sponsor an organization, to the right of the the organization's name, click **Sponsor**. ![Botão Sponsor (Patrocinar)](/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.select-a-tier %} +{% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} ![Botão para editar pagamento](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) {% data reusables.sponsors.who-can-see-your-sponsorship %} ![Botões de opção para escolher quem pode ver seu patrocínio](/assets/images/help/sponsors/who-can-see-sponsorship.png) -{% data reusables.sponsors.developer-sponsored-choose-updates %} -7. Clique em **Sponsor _DEVELOPER_** (Patrocinar DESENVOLVEDOR). ![Botão Sponsor developer (desenvolvedor patrocinado)](/assets/images/help/sponsors/sponsor-developer-button.png) - -### Patrocínio de uma organização - -Antes de poder patrocinar uma organização, você deve ter um endereço de e-mail verificado. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/verifying-your-email-address)". - -1. No {% data variables.product.product_name %}, navegue até o perfil da organização que você deseja patrocinar. -2. Ao lado do nome da organização, clique em **Patrocinar**. ![Botão Sponsor (Patrocinar)](/assets/images/help/sponsors/sponsor-org-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.select-sponsorship-billing %} - ![Botão para editar pagamento](/assets/images/help/sponsors/edit-org-sponsorship-payment-button.png) -{% data reusables.sponsors.who-can-see-your-sponsorship %} - ![Botões de opção para escolher quem pode ver seu patrocínio](/assets/images/help/sponsors/who-can-see-org-sponsorship.png) -{% data reusables.sponsors.org-sponsored-choose-updates %} -7. Clique em **Patrocinar _ORGANIZAÇÃO_**. ![Botão de Patrocinar organização ](/assets/images/help/sponsors/sponsor-org-confirm-button.png) +{% data reusables.sponsors.choose-updates %} +{% data reusables.sponsors.sponsor-account %} diff --git a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index d1662b7cb5..ee78f5bc1d 100644 --- a/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/pt-BR/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -7,34 +7,25 @@ versions: free-pro-team: '*' --- +### About sponsors and sponsorships + Você pode ver a análise sobre seus patrocínios atuais e anteriores, os pagamentos que recebeu de patrocinadores e eventos, como cancelamentos e mudanças na camada dos patrocinadores para seus patrocínios. Você também pode visualizar as atividades, tais como novos patrocinadores, alterações e cancelamentos nos patrocínios. Você pode filtrar a lista de atividades por data. Você também pode exportar dados de patrocínio para a conta que você está visualizando em formato CSV ou JSON. -Você acessa todas essas informações do seu Painel de Patrocinadores. - -### Visualizando seu painel de Patrocinadores - -1. No canto superior direito de qualquer página, clique na sua foto do perfil e depois em **{% data variables.product.prodname_sponsors %}**. ![Botão {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. Na lista exibida, à direita da conta ou da organização cujo painel de Patrocinadores você deseja visualizar, clique em **Painel**. ![Botão do painel de patrocinadores de desenvolvedor](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) - ### Exibir patrocinadores e patrocínios -1. Vá para seu painel de Patrocinadores, consulte [Visualizar seu painel de Patrocinadores](#viewing-your-sponsors-dashboard). -{% data reusables.sponsors.navigate-to-sponsors-tab %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. Como alternativa, para filtrar os patrocinadores por nível, use o menu suspenso **Filter** (Filtro), clique em **Active tiers** (Níveis ativos) ou **Retired tiers** (Níveis removidos) e selecione um nível. ![Menu suspenso para filtrar por nível](/assets/images/help/sponsors/filter-drop-down.png) ### Visualizando atividade de patrocínio recente -1. Vá para seu painel de Patrocinadores, consulte [Visualizar seu painel de Patrocinadores](#viewing-your-sponsors-dashboard). +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. Na barra lateral esquerda, clique em **Atividade**. ![Aba de atividade](/assets/images/help/sponsors/activity-tab.png) ### Exportando seus dados de patrocínio -1. Vá para seu painel de Patrocinadores, consulte [Visualizar seu painel de Patrocinadores](#viewing-your-sponsors-dashboard). +If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsors-tab %} 1. Clique em **Exportar tudo**. ![Botão Exportar tudo](/assets/images/help/sponsors/export-all.png) - - Este botão não será exibido se você não tiver nenhum patrocinador. - -1. Escolha um período de tempo e um formato para os dados que você gostaria de exportar, e clique em **Iniciar a exportação**. ![Opções de Exportar dados](/assets/images/help/sponsors/export-your-sponsors.png) - - O {% data variables.product.prodname_dotcom %} começa a exportar dados de todos os seus patrocinadores a partir do mês selecionado. Você receberá e-mail em breve com um anexo contendo os dados. Depois que a exportação estiver concluída, você pode exportar mais um mês de dados. Você pode exportar até 10 conjuntos de dados por hora para qualquer uma das suas organizações patrocinadas ou contas de usuário. +1. Escolha um período de tempo e um formato para os dados que você gostaria de exportar, e clique em **Iniciar a exportação**. ![Opções de Exportar dados](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/pt-BR/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/pt-BR/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 542df49eb0..af36b2a398 100644 --- a/translations/pt-BR/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/pt-BR/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -36,8 +36,8 @@ Se você criar um clone do repositório, não perderá nenhuma alteração ou hi {% endwindows %} - `BRANCH-NAME`: O branch-padrão para seu projeto atual, por exemplo, `main` ou `gh-pages`. ```shell - $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME - # Filtra o branch especificado no diretório e remove os commits vazios + $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME + # Filter the specified branch in your directory and remove empty commits > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) > Ref 'refs/heads/BRANCH-NAME' was rewritten ``` diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/about-the-dependency-graph.md index ee6e10f5bc..1a66878f1a 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 @@ -21,6 +21,10 @@ 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)." +{% 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: @@ -41,7 +45,8 @@ 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. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +- 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 diff --git a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/index.md b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/index.md index af8f6423e6..f225c0c441 100644 --- a/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/index.md +++ b/translations/pt-BR/content/github/visualizing-repository-data-with-graphs/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repository-graphs %} {% link_in_list /viewing-a-summary-of-repository-activity %} {% link_in_list /viewing-a-projects-contributors %} - {% link_in_list /viewing-traffic-to-a-repository %} - {% topic_link_in_list /analyzing-changes-to-a-repositorys-content %} {% link_in_list /visualizing-commits-in-a-repository %} {% link_in_list /visualizing-additions-and-deletions-to-content-in-a-repository %} {% topic_link_in_list /understanding-connections-between-repositories %} {% link_in_list /viewing-a-repositorys-network %} {% link_in_list /listing-the-forks-of-a-repository %} - {% link_in_list /about-the-dependency-graph %} {% link_in_list /exploring-the-dependencies-of-a-repository %} - diff --git a/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 1989971723..7cfca48654 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/pt-BR/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -51,7 +51,7 @@ O tema engloba layouts, inclusões e folhas de estilo padrão que serão aplicad 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: page + layout: post title: "POST TITLE" date: YYYY-MM-DD hh:mm:ss -0000 categories: CATEGORY-1 CATEGORY-2 diff --git a/translations/pt-BR/content/github/working-with-github-pages/index.md b/translations/pt-BR/content/github/working-with-github-pages/index.md index 149c8e142c..4bcb52d95e 100644 --- a/translations/pt-BR/content/github/working-with-github-pages/index.md +++ b/translations/pt-BR/content/github/working-with-github-pages/index.md @@ -23,15 +23,11 @@ versions: {% topic_link_in_list /getting-started-with-github-pages %} {% link_in_list /about-github-pages %} {% link_in_list /creating-a-github-pages-site %} - {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} - {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} - {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} - {% link_in_list /unpublishing-a-github-pages-site %} {% topic_link_in_list /setting-up-a-github-pages-site-with-jekyll %} {% link_in_list /about-github-pages-and-jekyll %} @@ -42,9 +38,7 @@ versions: {% link_in_list /adding-a-theme-to-your-github-pages-site-using-jekyll %} {% link_in_list /about-jekyll-build-errors-for-github-pages-sites %} {% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %} - {% topic_link_in_list /configuring-a-custom-domain-for-your-github-pages-site %} {% link_in_list /about-custom-domains-and-github-pages %} {% link_in_list /managing-a-custom-domain-for-your-github-pages-site %} {% link_in_list /troubleshooting-custom-domains-and-github-pages %} - diff --git a/translations/pt-BR/content/github/working-with-github-support/index.md b/translations/pt-BR/content/github/working-with-github-support/index.md index 4c3695607e..997c299db9 100644 --- a/translations/pt-BR/content/github/working-with-github-support/index.md +++ b/translations/pt-BR/content/github/working-with-github-support/index.md @@ -2,6 +2,7 @@ title: Suporte do GitHub redirect_from: - /categories/working-with-github-support + - /forum versions: free-pro-team: '*' --- diff --git a/translations/pt-BR/content/graphql/README.md b/translations/pt-BR/content/graphql/README.md new file mode 100644 index 0000000000..f29fbc5131 --- /dev/null +++ b/translations/pt-BR/content/graphql/README.md @@ -0,0 +1,10 @@ +# GraphQL + +The `/content/graphql` directory is where the GitHub GraphQL API docs live! + +* The `/content/graphql/guides` and `/content/graphql/overview` directories contain articles that are human-editable. +* The `/content/graphql/reference` directory contains an article for each GraphQL data type used in the GitHub GraphQL API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/graphql/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/graphql/README.md`](/lib/graphql/README.md). + + **As a result, we cannot accept contributions to GraphQL API reference content in this repository.** diff --git a/translations/pt-BR/content/graphql/overview/explorer.md b/translations/pt-BR/content/graphql/overview/explorer.md index c941ffdc36..591d464bec 100644 --- a/translations/pt-BR/content/graphql/overview/explorer.md +++ b/translations/pt-BR/content/graphql/overview/explorer.md @@ -7,6 +7,6 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +layout: graphql-explorer --- -Você pode acessar o Explorador GraphQL do GitHub em https://developer.github.com/v4/explorer. diff --git a/translations/pt-BR/content/packages/guides/about-github-container-registry.md b/translations/pt-BR/content/packages/guides/about-github-container-registry.md new file mode 100644 index 0000000000..2fe4f657d1 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/about-github-container-registry.md @@ -0,0 +1,105 @@ +--- +title: Sobre o 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 %}. O {% data variables.product.prodname_github_container_registry %} permite que você configure quem pode gerenciar e acessar pacotes usando permissões refinadas.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/about-github-container-registry + - /packages/managing-container-images-with-github-container-registry +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Durante o beta, o armazenamento e a banda larga são grátis. Para usar {% data variables.product.prodname_github_container_registry %}, você deve habilitar o recurso para sua conta. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/guides/enabling-improved-container-support)". + +{% endnote %} + +### Sobre o {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.container-registry-feature-highlights %} + +Para compartilhar o contexto sobre o uso do seu pacote, você pode vincular um repositório à sua imagem de contêiner no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Conectar um repositório a uma imagem de contêiner](/packages/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. + +| | Registros de pacotes | {% data variables.product.prodname_github_container_registry %} +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Locais de hospedagem | Você pode hospedar vários pacotes em um só repositório. | Você pode hospedar várias imagens de contêiner em uma organização ou conta de usuário. | +| Permissões | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | Para cada imagem de container, você pode escolher o nível de acesso que os outros têm. As permissões para acesso a imagens do contêiner são separadas da sua organização e das permissões do repositório. | + Visibilidade | {% data reusables.package_registry.public-or-private-packages %} | Você pode definir a visibilidade de cada uma de suas imagens de contêiner. Uma imagem privada de contêiner só é visível para pessoas e equipes às quais é fornecido acesso na sua organização. Qualquer pessoa pode ver uma imagem pública de contêiner. | acesso anônimo | N/A | Você pode acessar imagens de contêineres públicas anonimamente. + +For more information, see "[About scopes and permissions for {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)." + +### Formatos compatíveis + +O {% data variables.product.prodname_container_registry %} é atualmente compatível com os seguintes formatos de imagem do contêiner: + +* [Docker Image Manifest V2, Modelo 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Especificações de Open Container Initiative (OCI)](https://github.com/opencontainers/image-spec) + +O {% data variables.product.prodname_github_container_registry %} hospeda contêineres em `ghcr.io/OWNER/IMAGE-NAME`. + +| Cliente do pacote | Linguagem | Formato do pacote | Descrição | +| ----------------- | --------- | ----------------- | ----------------------------------------------- | +| arquivo Docker | N/A | `arquivo Docker` | Plataforma de gerenciamento de contêiner Docker | + + +#### Lista de manifestos/Índices de imagens + +{% data variables.product.prodname_github_container_registry %} também é compatível com +formatos das [ Listas de Manifesto do Docker](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[Índice de Imagens de OCI](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) definidos nas especificações do Docker V2, Esquema 2 e na imagem de OCI.

      + + + +### Visibilidade e permissões de acesso para imagens de contêiner + +Se você tem permissões de administrador para uma imagem de contêiner, você pode definir a imagem do contêiner como privada ou pública. As imagens públicas permitem acesso anônimo e podem ser carregadas sem autenticação ou login via CLI. + +Como administrador, você também pode conceder permissões de acesso para uma imagem contêiner separada das permissões que você configurou nos níveis da organização e repositório. + +Para imagens de contêiner publicadas e pertencentes a uma conta de usuário, você pode dar a qualquer pessoa uma função de acesso. Para imagens de contêineres publicadas e pertencentes a uma organização, você pode dar uma função de acesso a qualquer pessoa ou equipe na organização. + +| Função de permissão | Descrição de acesso | +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Leitura | Pode fazer o download do pacote.
      Pode ler metadados do pacote. | +| Gravação | Pode fazer upload e download deste pacote.
      Pode ler gravar metadados do pacote. | +| Administrador | Pode fazer upload, download, excluir e gerenciar este pacote.
      Pode ler gravar metadados do pacote.
      Pode conceder permissões de pacote. | + + +Para obter mais informações, consulte "[Configurar controle de acesso e visibilidade para imagens de contêiner](/packages/guides/configuring-access-control-and-visibility-for-container-images)". + + + +### About tokens + +To install or publish a package, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. + +| Escopo | Descrição | +| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `read:packages` | Faça o download e instale as imagens de contêiner de {% data variables.product.prodname_github_container_registry %} +| `write:packages` | Faça o upload e publique as imagens do contêiner para {% data variables.product.prodname_github_container_registry %} +| `delete:packages` | Exclua versões especificadas de imagens privadas ou públicas de contêiner do {% data variables.product.prodname_github_container_registry %}. Para obter mais informações, consulte "[Excluir uma imagem de contêiner](/packages/guides/deleting-a-container-image)". | + + +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 obter mais informações, consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token/)" e "[Escopos disponíveis](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)". + + + +### Sobre a cobrança do {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.billing-for-container-registry %} + + + +### Entrar em contato com o suporte + +Se você tiver feedback ou solicitações de recursos para {% data variables.product.prodname_github_container_registry %}, use o [formulário de feedback](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages). + +Entre em contato com {% data variables.contact.github_support %} sobre {% data variables.product.prodname_github_container_registry %} usando o [nosso formulário de contato](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) se: + +* Você encontrar qualquer coisa que contradiga a documentação. +* Você encontra erros vagos ou pouco claros. +* Seu pacote publicado contém dados confidenciais, como violações do GDPR, Chaves de API ou informações de identificação pessoal. diff --git a/translations/pt-BR/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md b/translations/pt-BR/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md new file mode 100644 index 0000000000..e73173b0d4 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md @@ -0,0 +1,69 @@ +--- +title: Configurar controle de acesso e visibilidade para imagens de contêiner +intro: 'Escolha quem tem acesso de leitura, gravação ou administrador à sua imagem de contêiner e a visibilidade das suas imagens de contêiner em {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### Configurar acesso a imagens de contêiner para sua conta pessoal + +Se você tiver permissões de administrador para uma imagem de contêiner pertencente a uma conta de usuário, você poderá atribuir funções de leitura, gravação ou administrador para outros usuários. Para obter mais informações sobre essas funções de permissão, consulte "[Visibilidade e permissões de acesso para imagens de contêiner](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)". + +{% data reusables.package_registry.package-settings-from-user-level %} +1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. As equipes não podem ter acesso a uma imagem de contêiner de uma conta de usuário. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png) +1. Ao lado do nome de usuário ou nome de equipe, use o menu suspenso "Função" para selecionar um nível de permissão desejado. ![Opções de acesso ao contêiner](/assets/images/help/package-registry/container-access-control-options.png) + +Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro. + +### Configurar o acesso a imagens de contêiner para uma organização + +Se você tiver permissões de administrador para uma imagem de contêiner pertencente à organização, pode atribuir funções de leitura, gravação ou administrador para outros usuários e equipes. Para obter mais informações sobre essas funções de permissão, consulte "[Visibilidade e permissões de acesso para imagens de contêiner](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)". + +Se o seu pacote pertencer a uma organização e for privado, você só poderá conceder acesso a outros integrantes da organização ou equipes. + +Para a organização de contêineres de imagens, os administradores das organizações devem habilitar pacotes antes que você possa definir a visibilidade como pública. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". + +{% data reusables.package_registry.package-settings-from-org-level %} +1. Na página de configurações do pacote, clique em **Convidar equipes ou pessoas** e digite o nome, nome de usuário ou e-mail da pessoa à qual você deseja conceder acesso. Você também pode inserir um nome de equipe da organização para dar acesso a todos os integrantes da equipe. ![Botão de convite de acesso ao contêiner](/assets/images/help/package-registry/container-access-invite.png) +1. Ao lado do nome de usuário ou nome de equipe, use o menu suspenso "Função" para selecionar um nível de permissão desejado. ![Opções de acesso ao contêiner](/assets/images/help/package-registry/container-access-control-options.png) + +Os usuários selecionados receberão acesso automaticamente e não precisarão aceitar um convite primeiro. + +### Configurar a visibilidade de imagens de contêiner para sua conta pessoal + +Ao publicar um pacote, a visibilidade-padrão é privada e só você poderá ver o pacote. Você pode modificar o acesso de uma imagem do contêiner privada ou pública, alterando as configurações de acesso. + +Um pacote público pode ser acessado anonimamente sem autenticação. Uma vez que você torna público o seu pacote, mas você não poderá tornar o seu pacote privado novamente. + +{% data reusables.package_registry.package-settings-from-user-level %} +5. Em "Zona de Perigo", escolha uma configuração de visibilidade: + - Para tornar a imagem do contêiner visível para qualquer pessoa, clique em **Tornar pública**. + {% warning %} + + **Aviso:** Depois de tornar um pacote público, você não poderá torná-lo privado novamente. + + {% endwarning %} + - Para tornar a imagem do contêiner visível para uma seleção personalizada de pessoas, clique em **Tornar privada**. ![Opções de visibilidade do contêiner](/assets/images/help/package-registry/container-visibility-option.png) + +### Configurar a visibilidade de imagens de contêiner para uma organização + +Ao publicar um pacote, a visibilidade-padrão é privada e só você poderá ver o pacote. Você pode conceder a usuários ou equipes diferentes funções de acesso para sua imagem de contêiner por meio das configurações de acesso. + +Um pacote público pode ser acessado anonimamente sem autenticação. Uma vez que você torna público o seu pacote, mas você não poderá tornar o seu pacote privado novamente. + +Para a organização de contêineres de imagens, os administradores das organizações devem habilitar pacotes públicos antes que você possa definir a visibilidade como pública. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". + +{% data reusables.package_registry.package-settings-from-org-level %} +5. Em "Zona de Perigo", escolha uma configuração de visibilidade: + - Para tornar a imagem do contêiner visível para qualquer pessoa, clique em **Tornar pública**. + {% warning %} + + **Aviso:** Depois de tornar um pacote público, você não poderá torná-lo privado novamente. + + {% endwarning %} + - Para tornar a imagem do contêiner visível para uma seleção personalizada de pessoas, clique em **Tornar privada**. ![Opções de visibilidade do contêiner](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/pt-BR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md new file mode 100644 index 0000000000..080fbaa0c6 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -0,0 +1,195 @@ +--- +title: Configurar o Apache Maven para uso com o GitHub Packages +intro: 'Você pode configurar o Apache Maven para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto Java.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Autenticar-se no {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Efetuando a autenticação com um token de acesso pessoal + +{% data reusables.package_registry.required-scopes %} + +Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com o Apache Maven editando seu arquivo *~/.m2/settings.xml* para incluir seu token de acesso pessoal. Criar um novo arquivo *~/.m2/settings.xml*, caso não exista um. + +Na etiqueta `servidores`, adicione uma etiqueta `servidor` secundário com um `Id`, substituindo *USERNAME* pelo o seu nome de usuário {% data variables.product.prodname_dotcom %} e *Token* pelo seu token de acesso pessoal. + +Na etiqueta `repositórios`, configure um repositório mapeando o `id` do repositório com o `id` que você adicionou na etiqueta `servidor` que contém as suas credenciais. Substituir {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* pelo nome do host de sua instância {% data variables.product.prodname_ghe_server %} {% endif %}*REPOSITÓRIO* com o nome do repositório no qual você gostaria de publicar um pacote ou instalar um pacote, e *OWNER* com o nome do usuário ou conta de organização proprietária do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas. + +Se desejar interagir com vários repositórios, você poderá adicionar cada repositório para separar os `repositório` secundários na etiqueta `repositórios`, mapeando o `ID` de cada um com as credenciais na etiqueta `servidores`. + +{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio desabilitado: + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` +{% endif %} + +#### Efetuando a autenticação com o `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar um pacote + +O {% data reusables.package_registry.default-name %} por exemplo, o {% data variables.product.prodname_dotcom %} publicará um pacote denominado `com.example:test` em um repositório denominado`OWNER/test`. + +Caso queira publicar vários pacotes no mesmo repositório, você poderá incluir a URL do repositório no `` elemento do arquivo *pom.xml*. O {% data variables.product.prodname_dotcom %} fará a correspondência do repositório com base nesse campo. Como o nome do repositório também faz parte do elemento `distributionManagement`, não há etapas adicionais para publicar vários pacotes no mesmo repositório. + +Para obter mais informações sobre como criar um pacote, consulte a [documentação maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + +1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing `OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. + +{% if enterpriseServerVersions contains currentVersion %}*NOME DE HOST* pelo nome de host da sua instância de {% data variables.product.prodname_ghe_server %} {% endif %}`PROPRIETÁRIO` pelo nome do usuário ou conta da organização proprietária do repositório e `REPOSITÓRIO` pelo nome do repositório que contém o seu projeto. + {% if enterpriseServerVersions contains currentVersion %} + Se sua instância tem o isolamento de subdomínio habilitado: + {% endif %} + ``` + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + ``` + {% if enterpriseServerVersions contains currentVersion %} + Se sua instância tem o isolamento de subdomínio desabilitado: + ``` + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + ``` + {% endif %} +2. Publique o pacote. + + ```shell + $ mvn deploy + ``` + +{% data reusables.package_registry.viewing-packages %} + +### Instalar um pacote + +Para instalar um pacote de Apache Maven a partir do {% data variables.product.prodname_registry %}, edite o arquivo *pom.xml* para incluir o pacote como uma dependência. Se você desejar instalar pacotes de mais de um repositório, adicione uma etiqueta de `repositório` para cada um. Para obter mais informações sobre como usar o arquivo *pom.xml* no seu projeto, consulte "[Introdução a POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" na documentação do Apache Maven. + +{% data reusables.package_registry.authenticate-step %} +2. Adicione as dependências do pacote ao elemento `dependências` do arquivo *pom.xml* do seu projeto, substituindo `com.exemplo:test` pelo seu pacote. + + ``` + + + com.example + test + 1.0.0-SNAPSHOT + + + ``` +3. Instale o pacote. + + ```shell + $ mvn install + ``` + +### Leia mais + +- "[Configurar o Gradle para uso com o {% data variables.product.prodname_registry %}](/packages/guides/configuring-gradle-for-use-with-github-packages)" +- "[Excluir um pacote](/packages/manage-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-docker-for-use-with-github-packages.md new file mode 100644 index 0000000000..d59297d76a --- /dev/null +++ b/translations/pt-BR/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -0,0 +1,214 @@ +--- +title: Configurar o Docker para usar com o GitHub Packages +intro: 'Você pode configurar o cliente do Docker para usar o {% data variables.product.prodname_registry %} para publicar e recuperar imagens do Docker.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Autenticar-se no {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +Ao instalar ou publicar uma imagem do docker, o {% data variables.product.prodname_registry %} não é compatível camadas externas, como imagens do Windows. + +{% if enterpriseServerVersions contains currentVersion %} + +Antes de poder usar o registro do Docker no {% data variables.product.prodname_registry %}, o administrador do site para {% data variables.product.product_location %} deve habilitar o suporte do Docker e o isolamento do subdomínio para a sua instância. Para obter mais informações, consulte "[Gerenciar pacotes do GitHub para a sua empresa](/enterprise/admin/packages)". + +{% endif %} + +### Autenticar-se no {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Efetuando a autenticação com um token de acesso pessoal + +{% data reusables.package_registry.required-scopes %} + +Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} usando o comando de login do `docker`. + +Para manter suas credenciais seguras, recomendamos que você salve seu token de acesso pessoal em um arquivo local no seu computador e use o sinalizador `--password-stdin` do Docker que lê o seu token a partir de um arquivo local. + +{% if currentVersion == "free-pro-team@latest" %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + ``` +{% endraw %} +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + +Para usar este exemplo de comando de login, substitua `NOME DE USUÁRIO` pelo seu nome de usuário de {% data variables.product.product_name %} {% if enterpriseServerVersions contains currentVersion %}, `NOME DE HOST` pela URL para {% data variables.product.product_location %},{% endif %} e `~/TOKEN. xt` pelo caminho do arquivo para o seu token de acesso pessoal para {% data variables.product.product_name %}. + +Para obter mais informações, consulte "[Login do Docker](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)". + +#### Efetuando a autenticação com o `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar uma imagem + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% note %} + +**Observação:** Os nomes de imagem devem usar apenas letras minúsculas. + +{% endnote %} + +O {% data variables.product.prodname_registry %} aceita várias imagens do Docker de nível superior por repositório. Um repositório pode ter qualquer número de tags de imagem. Você poderá conhecer uma publicação de serviço degradada ou instalar imagens do Docker com tamanho superior a 10 GB. As camadas são limitadas em 5 GB cada. Para obter mais informações, consulte "[Tag do Docker](https://docs.docker.com/engine/reference/commandline/tag/)" na documentação Docker. + +{% data reusables.package_registry.viewing-packages %} + +1. Determine o nome da imagem e o ID da sua imagem do docker usando `imagens do docker`. + ```shell + $ docker images + > < > + > REPOSITORY TAG IMAGE ID CREATED SIZE + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + ``` +2. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time, and *PATH* to the image if it isn't in the current working directory. +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* com o nome de host de {% data variables.product.product_location %},{% endif %} e *VERSÃO* com a versão do pacote no momento da criação. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} +3. Se você ainda não criou uma imagem do docker para o pacote, crie a imagem, substituindo *PROPRIETÁRIO* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* pelo o nome do repositório que contém o seu projeto, *IMAGE_NAME* pelo o nome do pacote ou imagem, *VERSÃO* com a versão do pacote no momento da criação, +{% if enterpriseServerVersions contains currentVersion %} *NOME DE HOST* pelo o nome de host de {% data variables.product.product_location %},{% endif %} e *PATH* para a imagem se não estiver no diretório de trabalho atual. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% else %} + ```shell + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} +4. Publicar a imagem em +{% data variables.product.prodname_registry %}. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} + {% note %} + + **Observação:** Você deve enviar sua imagem usando `IMAGE_NAME:VERSION` e não `IMAGE_NAME:SHA`. + + {% endnote %} + +#### Exemplo de publicação de uma imagem do Docker + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +Você pode publicar a versão 1.0 da imagem de `monalisa` para o repositório `octocat/octo-app` usando um ID de imagem. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} + +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` + +{% endif %} + +Você pode publicar uma nova imagem do Docker pela primeira vez e nomeá-la como `monalisa`. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +# Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . + +# Faça push da imagem no {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} +```shell +# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` +{% endif %} + +### Fazer o download de uma imagem + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +Você pode usar o comando `docker pull` para instalar uma imagem docker a partir de {% data variables.product.prodname_registry %}, substituindo *OWNER* pelo nome do usuário ou conta de organização proprietária do repositório, *REPOSITÓRIO* com o nome do repositório que contém seu projeto, *IMAGE_NAME* com o nome do pacote ou da imagem,{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* com o nome do host da sua {% data variables.product.prodname_ghe_server %} instância {% endif %} e *TAG_NAME* com tag para a imagem que você deseja instalar. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% else %} +```shell +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} + +{% note %} + +**Nota:** Você deve fazer pull da imagem usando `IMAGE_NAME:VERSION` e não usar `IMAGE_NAME:SHA`. + +{% endnote %} + +### Leia mais + +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" 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 new file mode 100644 index 0000000000..4c70530c6f --- /dev/null +++ b/translations/pt-BR/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -0,0 +1,196 @@ +--- +title: Configurar a CLI `dotnet` para uso com o GitHub Packages +intro: 'Você pode configurar a interface de linha de comando `dotnet` (CLI) para publicar pacotes NuGet no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto .NET.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages + - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Autenticar-se no {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Efetuando a autenticação com um token de acesso pessoal + +{% data reusables.package_registry.required-scopes %} + +Para efetuar a autenticação em {% data variables.product.prodname_registry %} com a interface da linha de comando (CLI) `dotnet`, crie um arquivo *nuget.config* no diretório do seu projeto, especificando {% data variables.product.prodname_registry %} como uma fonte em `packageSources` para o cliente da CLI `Dotnet`. + +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 %}. + +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} + +```xml + + + + + + + + + + + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio desabilitado: + +```xml + + + + + + + + + + + + + +``` +{% endif %} + +#### Efetuando a autenticação com o `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### 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. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Criar um novo projeto + ```shell + dotnet new console --name OctocatApp + ``` +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 %} + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + ``` +4. Empacotar o projeto. + ```shell + dotnet pack --configuration Release + ``` + +5. Publique o pacote usando a `chave` que você especificou no arquivo *nuget.config*. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" + ``` + +### 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. + +Por exemplo, os projetos *OctodogApp* e *OctocatApp* irão publicar no mesmo repositório: + +``` xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +### Instalar um pacote + +Usar pacotes do {% data variables.product.prodname_dotcom %} no seu projeto é semelhante a usar pacotes do *nuget.org*. Adicione suas dependências de pacote ao seu arquivo *.csproj* especificando o nome e a versão do pacote. Para obter mais informações sobre como usar um arquivo *.csproj* no seu projeto, consulte "[Trabalhar com pacotes NuGet](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" na documentação da Microsoft. + +{% data reusables.package_registry.authenticate-step %} + +2. Para usar um pacote, adicione `ItemGroup` e configure o campo `PackageReference` no arquivo de projeto *.csproj*, substituindo o pacote `OctokittenApp` pelo seu pacote de dependência e `1.0.0` pela versão que você deseja usar: + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + ``` + +3. Instale os pacotes com o comando `restaurar`. + ```shell + restaurar dotnet + ``` + +### Leia mais + +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/guides/configuring-gradle-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-gradle-for-use-with-github-packages.md new file mode 100644 index 0000000000..43f576cd5b --- /dev/null +++ b/translations/pt-BR/content/packages/guides/configuring-gradle-for-use-with-github-packages.md @@ -0,0 +1,215 @@ +--- +title: Configurar o Gradle para uso com o GitHub Packages +intro: 'Você pode configurar o Gradle para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto Java.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Autenticar-se no {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Efetuando a autenticação com um token de acesso pessoal + +{% data reusables.package_registry.required-scopes %} + +Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com Gradle usando Gradle Groovy ou Kotlin DSL e editando o seu arquivo *build.gradle* (Gradle Groovy) ou o arquivo *build.gradle.kts* (Kotlin DSL) para incluir seu token de acesso pessoal. Também é possível configurar o Gradle Groovy e o Kotlin DSL para reconhecer um único pacote ou vários pacotes em um repositório. + +{% if enterpriseServerVersions contains currentVersion %} +Substitua *REGISTRY-URL* pela URL do registro do Maven para a sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `maven.HOSTNAME`. Se sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/maven`. Em ambos os casos, substitua *HOSTNAME* pelo nome do host da sua +instância de {% data variables.product.prodname_ghe_server %}. +{% endif %} + +Substitua *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %} *TOKEN* pelo seu token de acesso pessoal, *REPOSITÓRIO* pelo nome do repositório que contém o pacote que você deseja publicar, e *PROPRIETÁRIO* pelo nome do usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas. + +{% note %} + +**Observação:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} Por exemplo, consulte "[Configuraro Apache Maven para uso com {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)". + +{% endnote %} + +##### Exemplo de uso do Gradle Groovy para um único pacote em um repositório + +```shell +plugins { + id("maven-publish") +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } +} +``` + +##### Exemplo de uso do Gradle Groovy para vários pacotes no mesmo repositório + +```shell +plugins { + id("maven-publish") apply false +} + +subprojects { + apply plugin: "maven-publish" + publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } + } +} +``` + +##### Exemplo de uso do Kotlin DSL para um único pacote no mesmo repositório + +```shell +plugins { + `maven-publish` +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } +} +``` + +##### Exemplo de uso do Kotlin DSL para vários pacotes no mesmo repositório + +```shell +plugins { + `maven-publish` apply false +} + +subprojects { + apply(plugin = "maven-publish") + configure { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } + } +} +``` + + #### Efetuar a autenticação com o `GITHUB_TOKEN` + + {% data reusables.package_registry.package-registry-with-github-tokens %} + + Para obter mais informações sobre como usar o `GITHUB_TOKEN` com Maven, consulte "[Publicar pacotes Java com Maven](/actions/language-and-framework-guides/publishing-java-packages-with-maven#publishing-packages-to-github-packages)". + + ### Publicar um pacote + + {% data reusables.package_registry.default-name %} Por exemplo, {% data variables.product.prodname_dotcom %} publicará um pacote denominado `com.example.test` no repositório `OWNER/test` {% data variables.product.prodname_registry %}. + + {% data reusables.package_registry.viewing-packages %} + + {% data reusables.package_registry.authenticate-step %} + 2. Depois de criar seu pacote, você poderá publicá-lo. + + ```shell + $ gradle publish + ``` + +### Instalar um pacote + +Você pode instalar um pacote adicionando-o como uma dependência ao seu projeto. Para obter mais informações, consulte "[Declarar dependências](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" na documentação do Gradle. + +{% data reusables.package_registry.authenticate-step %} +2. Adicione as dependências do pacote ao seu arquivo *build.gradle* (Gradle Groovy) ou ao arquivo *build.gradle.kts* (arquivo de Kotlin DSL). + + Exemplo do uso do Gradle Groovy: + ```shell + dependencies { + implementation 'com.example:package' + } + ``` + Exemplo de uso do Kotlin DSL: + ```shell + dependencies { + implementation("com.example:package") + } + ``` + +3. Adicione o plugin do maven ao seu arquivo *build.gradle* (Gradle Groovy) ou ao arquivo *build.gradle.kts* (arquivo Kotlin DSL). + + Exemplo do uso do Gradle Groovy: + ```shell + plugins { + id 'maven' + } + ``` + Exemplo de uso do Kotlin DSL: + ```shell + plugins { + `maven` + } + ``` + + 3. Instale o pacote. + + ```shell + $ gradle install + ``` + +### Leia mais + +- "[Configurar o Apache Maven para uso com {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)" +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md new file mode 100644 index 0000000000..a3283e899f --- /dev/null +++ b/translations/pt-BR/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -0,0 +1,203 @@ +--- +title: Configurar o npm para usar com o GitHub Packages +intro: 'Você pode configurar o npm para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto npm.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Autenticar-se no {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Efetuando a autenticação com um token de acesso pessoal + +{% data reusables.package_registry.required-scopes %} + +Você pode efetuar a autenticação no {% data variables.product.prodname_registry %} com o npm editando seu arquivo *~/.npmrc* por usuário para incluir o seu token de acesso pessoal ou fazer o login no npm na linha de comando usando seu nome de usuário e token de acesso pessoal. + +Para efetuar a autenticação adicionando seu token de acesso pessoal ao seu arquivo *~/.npmrc*, edite o arquivo *~/.npmrc* para que o seu projeto inclua a linha a seguir substituindo {% if enterpriseServerVersions contains currentVersion %}*NOME DE HOST* pelo nome do host da sua instância {% data variables.product.prodname_ghe_server %} e {% endif %}*TOKEN* pelo seu token de acesso pessoal. Crie um novo arquivo *~/.npmrc* se um não existir. + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} + +```shell +//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN +``` + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio desabilitado: + +```shell +$ npm login --registry=https://npm.pkg.github.com +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +Para efetuar a autenticação conectado no npm, use o comando `npm login` , substituindo o *NOME DE USUÁRIO* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %}, o *TOKEN* pelo seu token de acesso pessoal e *PUBLIC-EMAIL-ADDRESS* pelo seu endereço de e-mail. + +Se {% data variables.product.prodname_registry %} não é seu registro de pacote padrão para usar npm e você deseja usar o comando `npm audit` , recomendamos que você use o sinalizador `--scope` com o proprietário do pacote quando você efetuar a autenticação no {% data variables.product.prodname_registry %}. + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} + +```shell +$ npm login --scope=@OWNER --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} + +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio desabilitado: + +```shell +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +#### Efetuando a autenticação com o `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar um pacote + +{% note %} + +**Nota:** Os nomes dos pacotes e escopos só devem usar letras minúsculas. + +{% endnote %} + +Por padrão, o {% data variables.product.prodname_registry %} publica um pacote no repositório {% data variables.product.prodname_dotcom %} que você especificar no campo nome do arquivo *package.json*. Por exemplo, você publicaria um pacote denominado `@my-org/test` no repositório `my-org/test` do {% data variables.product.prodname_dotcom %}. Você pode adicionar um resumo da página de listagem do pacote incluindo um arquivo *README.md* no diretório do seu pacote. Para obter mais informações, consulte "[Trabalhando com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" e "[Como criar Módulos de Node.js](https://docs.npmjs.com/getting-started/creating-node-modules)" na documentação do npm. + +Você pode publicar vários pacotes no mesmo repositório do {% data variables.product.prodname_dotcom %} incluindo um campo de `URL` no arquivo *package.json*. Para obter mais informações, consulte "[Publicar vários pacotes no mesmo repositório](#publishing-multiple-packages-to-the-same-repository)". + +É possível definir o mapeamento do escopo para o seu projeto usando um arquivo local *.npmrc* no projeto ou usando a opção `publishConfig` em *package.json*. {% data variables.product.prodname_registry %} só é compatível com pacotes npm com escopo definido. Pacotes com escopo têm nomes no formato `@owner/name`. Os pacotes com escopo sempre começam pelo símbolo `@`. Talvez seja necessário atualizar o nome no *package.json* para usar o nome com escopo. Por exemplo, `"name": "@codertocat/hello-world-npm"`. + +{% data reusables.package_registry.viewing-packages %} + +#### Publicar um pacote usando o arquivo *.npmrc* local + +Você pode usar um arquivo *.npmrc* para configurar o mapeamento do escopo para o seu projeto. No arquivo *.npmrc*, use a URL e o proprietário da conta de {% data variables.product.prodname_registry %} para que {% data variables.product.prodname_registry %} saiba onde rotear as solicitações de pacotes. O uso de um arquivo *.npmrc* impede que outros desenvolvedores publiquem acidentalmente o pacote no npmjs.org em vez de {% data variables.product.prodname_registry %}. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +1. Verifique o nome do pacote no *package.json* do seu projeto. O campo `name` (nome) deve conter o escopo e o nome do pacote. Por exemplo, se o pacote é denominado de "test" e você está publicando em "My-org" +organização de {% data variables.product.prodname_dotcom %}, o campo `nome` no seu *package.json* deve ser `@my-org/test`. +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +#### Publicar um pacote usando o `publishConfig` no arquivo *package.json* + +Você pode usar o elemento `publishConfig` no arquivo *package.json* para especificar o registro onde você quer o pacote publicado. Para obter mais informações, consulte "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" na documentação npm. + +1. Edite o arquivo *package.json* do seu pacote e inclua uma entrada `publishConfig`. + {% if enterpriseServerVersions contains currentVersion %} + Se sua instância tem o isolamento de subdomínio habilitado: + {% endif %} + ```shell + "publishConfig": { + "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + }, + ``` + {% if enterpriseServerVersions contains currentVersion %} + Se sua instância tem o isolamento de subdomínio desabilitado: + ```shell + "publishConfig": { + "registry":"https://HOSTNAME/_registry/npm/" + }, + ``` + {% endif %} +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +### Publicar vários pacotes no mesmo repositório + +Para publicar vários pacotes no mesmo repositório, você pode incluir a URL do repositório do {% data variables.product.prodname_dotcom %} no campo `repositório` do arquivo *package.json* para cada pacote. + +Para garantir que a URL do repositório esteja correta, substitua REPOSITÓRIO pelo nome do repositório que contém o pacote que você deseja publicar, e o PROPRIETÁRIO pelo nome de usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. + +O {% data variables.product.prodname_registry %} corresponderá ao repositório baseado na URL, em vez de ser baseado no nome do pacote. + +```shell +"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", +``` + +### Instalar um pacote + +Você pode instalar pacotes do {% data variables.product.prodname_registry %} adicionando os pacotes como dependências no arquivo *package.json* para o seu projeto. Para obter mais informações sobre como usar um pacote *package.json* no projeto, consulte "[Trabalhar com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" na documentação npm. + +Por padrão, você pode adicionar pacotes a partir de uma organização. Para obter mais informações, consulte [Instalar pacotes de outras organizações](#installing-packages-from-other-organizations)." + +Você também precisa adicionar o arquivo *.npmrc* ao seu projeto para que todas as solicitações de instalação passem pelo {% data variables.product.prodname_registry %}. Ao encaminhar todas as solicitações através de {% data variables.product.prodname_registry %}, você pode usar pacotes com escopo e sem escopo de *npmjs.com*. Para obter mais informações, consulte "[npm-scope](https://docs.npmjs.com/misc/scope)" na documentação npm. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +4. Configure *package.json* no seu projeto para usar o pacote que você está instalando. Para adicionar as suas dependências de pacote ao arquivo *package.json* para {% data variables.product.prodname_registry %}, especifique o nome do pacote com escopo completo, como, por exemplo, `@my-org/server`. Para pacotes do *npmjs.com*, especifique o nome completo, como `@babel/core` ou `@lodash`. Por exemplo, o arquivo *package.json* a seguir usa o pacote `@octo-org/octo-app` como uma dependência. + + ``` + { + "name": "@my-org/server", + "version": "1.0.0", + "description": "Server app that uses the @octo-org/octo-app package", + "main": "index.js", + "author": "", + "license": "MIT", + "dependencies": { + "@octo-org/octo-app": "1.0.0" + } + } + ``` +5. Instale o pacote. + + ```shell + $ npm install + ``` + +#### Instalar pacotes de outras organizações + +Por padrão, você só pode usar pacotes do {% data variables.product.prodname_registry %} de uma organização. Se você deseja encaminhar solicitações de pacotes para várias organizações e usuários, você pode adicionar linhas ao seu arquivo *.npmrc* substituindo {% if enterpriseServerVersions contains currentVersion %}*NOME DE HOST* pelo nome do host da sua instância de {% data variables.product.prodname_ghe_server %} e {% endif %}*PROPRIETÁRIO* pelo nome do usuário ou organização que possui o repositório que contém o seu projeto. + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio habilitado: +{% endif %} + +```shell +registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}/OWNER +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +``` + +{% if enterpriseServerVersions contains currentVersion %} +Se sua instância tem o isolamento de subdomínio desabilitado: + +```shell +registry=https://HOSTNAME/_registry/npm/OWNER +@OWNER:registry=https://HOSTNAME/_registry/npm/ +@OWNER:registry=https://HOSTNAME/_registry/npm/ +``` +{% endif %} + +### Leia mais + +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/pt-BR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md new file mode 100644 index 0000000000..ae268f8a43 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -0,0 +1,148 @@ +--- +title: Configurar o RubyGems para uso com o GitHub Packages +intro: 'Você pode configurar RubyGems para publicar um pacote em {% data variables.product.prodname_registry %} e usar pacotes armazenados em {% data variables.product.prodname_registry %} como dependências em um projeto Ruby com o Bundler.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +### Pré-requisitos + +- Você deve ter o rubygems 2.4.1 ou superior. Para encontrar sua versão do rubygems: + + ```shell + $ gem --version + ``` + + - Você deve ter o bundler 1.6.4 ou superior. Para encontrar sua versão do Bundler: + ```shell + $ bundle --version + Bundler version 1.13.7 + ``` + + - Instale o keycutter para gerenciar várias credenciais. Para instalar o keycutter: + ```shell + $ gem install keycutter + ``` + +### Autenticar-se no {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Efetuando a autenticação com um token de acesso pessoal + +{% data reusables.package_registry.required-scopes %} + +Você pode efetuar a autenticação em {% data variables.product.prodname_registry %} com o RubyGems editando o arquivo *~/.gem/credentials* para publicação de gems, editando o arquivo *~/.gemrc* para instalar um único gem, ou usando o Bundler para rastrear e instalar um ou mais gems. + +Para publicar novos gems, você precisa efetuar a autenticação no {% data variables.product.prodname_registry %} com RubyGems, editando seu arquivo *~/.gem/credentials* para incluir seu token de acesso pessoal. Crie um novo arquivo *~/.gem/credentials* se este arquivo não existir. + +Por exemplo, você criaria ou editaria um arquivo *~/.gem/credentials* para incluir o indicado a seguir, substituindo *TOKEN* pelo seu token de acesso pessoal. + +```shell +gem.metadata = { "github_repo" => "ssh://github.com/OWNER/REPOSITORY" } +``` + +Para instalar gems, você deve efetuar a autenticação no {% data variables.product.prodname_registry %}, editando o arquivo *~/.gemrc* para o seu projeto incluir `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. Você deve substituir: + - `NOME DE USUÁRIO` pelo seu nome de usuário no {% data variables.product.prodname_dotcom %}. + - `TOKEN` pelo seu token de acesso pessoal. + - `PROPRIETÁRIO` com o nome da conta do usuário ou da organização que é proprietário do repositório que contém o seu projeto.{% if enterpriseServerVersions contains currentVersion %} + - `URL` com a URL para o registro do Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %}. +{% endif %} + +Se você não tiver um arquivo *~/.gemrc*, crie um arquivo *~/.gemrc* usando este exemplo. + +```shell +--- +:backtrace: false +:bulk_threshold: 1000 +:sources: +- https://rubygems.org/ +- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ +:update_sources: true +:verbose: true + +``` + +Para autenticar com o bundler, configure o Bundler para usar o seu token de acesso pessoal, substituindo *USERNAME* com seu {% data variables.product.prodname_dotcom %} nome de usuário, *TOKEN* com seu token de acesso pessoal, e *OWNER* com o nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto.{% if enterpriseServerVersions contains currentVersion %} Substitua `URL REGISTRO` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %} .{% endif %} + +```shell +$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN +``` + +#### Efetuando a autenticação com o `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publicar um pacote + +{% data reusables.package_registry.default-name %} Por exemplo, ao publicar `octo-gem` na organização `octo-org` , {% data variables.product.prodname_registry %} publicará o gem no repositório `octo-org/octo-gem`. Para obter mais informações sobre como criar seu gem, consulte "[Criar seu próprio gem](http://guides.rubygems.org/make-your-own-gem/)" na documentação do RubyGems. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Crie o pacote da *gemspec* para criar o pacote *.gem*. + ```shell + gem build OCTO-GEM.gemspec + ``` +3. Publicar um pacote em {% data variables.product.prodname_registry %}, substituindo o `OWNER` pelo nome do usuário ou conta da organização proprietária do repositório que contém o seu projeto e `OCTO-GEM` pelo nome do seu pacote de gemas.{% if enterpriseServerVersions contains currentVersion %} substitui `REGISTRY-URL` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %} .{% endif %} + + ```shell + $ gem push --key github \ + --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem + ``` + +### Publicar vários pacotes no mesmo repositório + +Para publicar vários gems no mesmo repositório, você pode incluir a URL no repositório de {% data variables.product.prodname_dotcom %} no campo `github_repo` em `gem.metadata`. Se você incluir este campo, {% data variables.product.prodname_dotcom %} irá corresponde ao repositório baseado neste valor, em vez de usar o nome do gem.{% if enterpriseServerVersions contains currentVersion %} Substitua o *NOME DE HOST* pelo nome do host da sua instância {% data variables.product.prodname_ghe_server %}.{% endif %} + +``` +gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } +``` + +### Instalar um pacote + +É possível usar gems do {% data variables.product.prodname_registry %} assim como você usa gems de *rubygems.org*. Você precisa efetuar a autenticação no {% data variables.product.prodname_registry %} , adicionando o seu usuário ou organização do {% data variables.product.prodname_dotcom %} como fonte ao arquivo *~/.gemrc* ou usando o Bundler e editando-o *Gemfile*. + +{% data reusables.package_registry.authenticate-step %} +2. Para o Bundler, adicione seu usuário ou organização {% data variables.product.prodname_dotcom %} como uma fonte no seu *Gemfile* para buscar gems a partir desta nova fonte. Por exemplo, você pode adicionar um novo bloco`de fonte`ao seu *Gemfile* que usa {% data variables.product.prodname_registry %} apenas para os pacotes que você especificar, substituindo *GEM NOME* pelo pacote que deseja instalar de {% data variables.product.prodname_registry %} e *OWNER* pelo usuário ou organização que possui o repositório que contém a gema que deseja instalar.{% if enterpriseServerVersions contains currentVersion %} substitua `URL REGISTRY` pelo URL do registro Rubygems da sua instância. Se sua instância tiver o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância estiver com o isolamento de subdomínio desabilitado, use `HOSTNAME/registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome de host da sua instância do {% data variables.product.prodname_ghe_server %} .{% endif %} + + ``` + source "https://rubygems.org" + + gem "rails" + + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do + gem "GEM NAME" + end + ``` + +3. Para versões do Bundler anteriores à 1.7.0, você deve adicionar uma nova `fonte` global. Para obter mais informações sobre como usar o Bundler, consulte a [documentação bundler.io](http://bundler.io/v1.5/gemfile.html). + + ``` + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" + source "https://rubygems.org" + + gem "rails" + gem "GEM NAME" + ``` + +4. Instale o pacote: + ```shell + $ gem install octo-gem --version "0.1.1" + ``` + +### Leia mais + +- "[Excluir um pacote](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md new file mode 100644 index 0000000000..f93f99d14a --- /dev/null +++ b/translations/pt-BR/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -0,0 +1,83 @@ +--- +title: Conectar um repositório a uma imagem de contêiner +intro: 'É possível vincular um repositório a uma imagem de contêiner localmente e no {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image +versions: + free-pro-team: '*' +--- + +Ao vincular um contêiner a um repositório, a página de destino do pacote mostrará informações e links do repositório, como, por exemplo, LEIAME. + +Para conectar um repositório e uma imagem de contêiner no {% data variables.product.prodname_dotcom %}, eles devem compartilhar o mesmo proprietário no {% data variables.product.prodname_dotcom %}. Por exemplo, `my_repo` e `hello_docker` são propriedade do usuário `monalisa`: +```shell +https://github.com/monalisa/my_repo +https://github.com/monalisa/hello_docker +``` + +### Conectar um repositório a uma imagem de contêiner de propriedade do usuário no {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Conectar um repositório a uma imagem de contêiner de propriedade de organização no {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Conectar um repositório a uma imagem de contêiner na linha de comando + +1. No seu arquivo Docker, adicione esta linha, substituindo `PROPRIETÁRIO` e `REPO` pelas suas informações: + + ```shell + ETIQUETA org.opencontainers.image.source https://github.com/OWNER/REPO + ``` + Por exemplo, se você é o usuário de `monalisa` e proprietário de `my-repo`, você adicionaria essa linha ao seu arquivo Docker: + ```shell + ETIQUETA org.opencontainers.image.source https://github.com/monalisa/my-repo + ``` + Para obter mais informações, consulte "[ETIQUETA](https://docs.docker.com/engine/reference/builder/#label)" na documentação oficial do Docker e "[Chaves de anotação pré-definidas](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" no repositório `opencontainers/image-spec`. + +2. Construa a sua imagem do contêiner. Este exemplo cria uma imagem do arquivo Docker no diretório atual e atribui o nome da imagem `hello_docker`. + + ```shell + $ docker build -t hello_docker . + ``` +3. Opcionalmente, revise os detalhes para a imagem do Docker que você deseja marcar. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +4. Marque sua imagem Docker com o nome de imagem desejado e hospedagem de destino. + ```shell + $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG + ``` + Por exemplo: + ```shell + $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest + ``` + +5. Se você ainda não o fez, efetue a autenticação em + +{% data variables.product.prodname_github_container_registry %}. Para obter mais informações, consulte "[Efetuar a autenticação no GitHub Container Registry](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-github-container-registry)". + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + > Login Succeeded + ``` + {% endraw %} +6. Faça push da sua imagem de contêiner para {% data variables.product.prodname_github_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG + ``` + Por exemplo: + ```shell + $ docker push ghcr.io/monalisa/hello_docker:latest + ``` diff --git a/translations/pt-BR/content/packages/guides/container-guides-for-github-packages.md b/translations/pt-BR/content/packages/guides/container-guides-for-github-packages.md new file mode 100644 index 0000000000..31b8f63889 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/container-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Container guides for GitHub Packages +shortTitle: Container guides for GitHub Packages +intro: 'You can publish and retrieve Docker images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/pt-BR/content/packages/guides/deleting-a-container-image.md b/translations/pt-BR/content/packages/guides/deleting-a-container-image.md new file mode 100644 index 0000000000..5157d0388e --- /dev/null +++ b/translations/pt-BR/content/packages/guides/deleting-a-container-image.md @@ -0,0 +1,33 @@ +--- +title: Excluir uma imagem de contêiner +intro: 'É possível excluir uma versão de uma imagem privada de contêiner usando o GraphQL ou em {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### Sobre a exclusão de pacotes + +Você pode remover uma imagem de contêiner inteira ou uma versão específica em {% data variables.product.prodname_dotcom %}. Para excluir uma imagem de contêiner, você deve usar a interface do usuário. O uso do GraphQL para excluir uma imagem de contêiner não é compatível no momento. + +Para excluir uma imagem do contêiner, você deve ter permissões de administrador para a imagem do contêiner. + +Ao excluir pacotes públicos, esteja ciente de que você pode quebrar projetos que dependem do seu pacote. + +### Excluir uma versão de uma imagem de contêiner de usuário em {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} +5. À esquerda, clique em **Gerenciar versões**. +5. À direita da versão que você deseja excluir, clique em **Excluir**. ![Botão de excluir pacote](/assets/images/help/package-registry/delete-package-button.png) +6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Excluir uma versão de uma imagem de contêiner de uma organização no {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} +5. À esquerda, clique em **Gerenciar versões**. +5. À direita da versão que você deseja excluir, clique em **Excluir**. ![Botão de excluir pacote](/assets/images/help/package-registry/delete-package-button.png) +6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-package-deletion.png) diff --git a/translations/pt-BR/content/packages/guides/enabling-improved-container-support.md b/translations/pt-BR/content/packages/guides/enabling-improved-container-support.md new file mode 100644 index 0000000000..e078325f04 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/enabling-improved-container-support.md @@ -0,0 +1,39 @@ +--- +title: Habilitar suporte ao contêiner aprimorado +intro: 'Para usar {% data variables.product.prodname_github_container_registry %}, você precisa habilitá-lo para a sua conta de usuário ou organização.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/enabling-improved-container-support +versions: + free-pro-team: '*' +--- + +{% note %} + +**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Durante o beta, o armazenamento e a banda larga são grátis. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." + +{% endnote %} + +### Habilitar {% data variables.product.prodname_github_container_registry %} para sua conta pessoal + +Uma vez que {% data variables.product.prodname_github_container_registry %} está habilitado para a sua conta pessoal de usuário, você pode publicar contêineres em {% data variables.product.prodname_github_container_registry %} que pertencem à sua conta de usuário. + +Para usar {% data variables.product.prodname_github_container_registry %} em uma organização, o dono da organização deve habilitar o recurso para os integrantes da organização. + +{% data reusables.feature-preview.feature-preview-setting %} +2. À esquerda, selecione "Suporte ao contêiner aprimorado" e, em seguida, clique em **Habilitar**. ![Suporte ao contêiner aprimorado](/assets/images/help/settings/improved-container-support.png) + +### Habilitar {% data variables.product.prodname_github_container_registry %} para a conta da sua organização + +Antes que os proprietários ou integrantes da organização possam publicar imagens do contêiner para {% data variables.product.prodname_github_container_registry %}, um proprietário da organização deve habilitar a pré-visualização do recurso para a organização. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. À esquerda, clique em **Pacotes**. +5. Em "Melhorar suporte ao container", selecione "Suporte ao contêiner aprimorado" e clique em **Salvar**. ![Opção de habilitar suporte de registro do contêiner e botão de salvar](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Em "Criação de contêiner", escolha se deseja habilitar a criação de imagens de recipientes públicas e/ou privadas. + - Para permitir que os integrantes da organização criem imagens de contêiner público, clique em **Público**. + - Para permitir que os integrantes da organização criem imagens privadas de contêiner visíveis apenas para outros integrantes da organização, clique em **Privado**. Você pode personalizar ainda mais a visibilidade de imagens de contêiner privado. Para obter mais informações, consulte "[Configurar controle de acesso e visibilidade para imagens de contêiner](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)". + + ![Opções para habilitar pacotes públicos ou privados ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/pt-BR/content/packages/guides/index.md b/translations/pt-BR/content/packages/guides/index.md new file mode 100644 index 0000000000..13e5e7bb73 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/index.md @@ -0,0 +1,33 @@ +--- +title: Guias +shortTitle: Guias +intro: 'These guides help you configure {% data variables.product.prodname_actions %} or your package client to work with {% data variables.product.prodname_registry %}.' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem + - /packages/using-github-packages-with-your-projects-ecosystem +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Índice + +{% topic_link_in_list /package-client-guides-for-github-packages %} + {% link_in_list /using-github-packages-with-github-actions %} + {% link_in_list /configuring-apache-maven-for-use-with-github-packages %} + {% link_in_list /configuring-gradle-for-use-with-github-packages %} + {% link_in_list /configuring-npm-for-use-with-github-packages %} + {% link_in_list /configuring-dotnet-cli-for-use-with-github-packages %} + {% link_in_list /configuring-rubygems-for-use-with-github-packages %} +{% topic_link_in_list /container-guides-for-github-packages %} + {% link_in_list /configuring-docker-for-use-with-github-packages %} + {% link_in_list /about-github-container-registry %} + {% link_in_list /migrating-to-github-container-registry-for-docker-images %} + {% link_in_list /enabling-improved-container-support %} + {% link_in_list /configuring-access-control-and-visibility-for-container-images %} + {% link_in_list /connecting-a-repository-to-a-container-image %} + {% link_in_list /pushing-and-pulling-docker-images %} + {% link_in_list /deleting-a-container-image %} + diff --git a/translations/pt-BR/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md b/translations/pt-BR/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md new file mode 100644 index 0000000000..38c1d410c8 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md @@ -0,0 +1,115 @@ +--- +title: Fazer a migração para o GitHub Container Registry para imagens do Docker +intro: 'Se você usou o Docker do GitHub Packages Docker Registry para armazenar imagens do Docker, você pode fazer a migração para o novo {% data variables.product.prodname_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images +versions: + free-pro-team: '*' +--- + +### Principais diferenças entre {% data variables.product.prodname_github_container_registry %} e o registro do pacote do Docker + +{% data reusables.package_registry.container-registry-beta %} + +O {% data variables.product.prodname_github_container_registry %} substitui o registro do Docker de Pacotes existente e é otimizado para atender a algumas das necessidades únicas dos contêineres. + +{% data reusables.package_registry.container-registry-feature-highlights %} + +Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." + +### Alterações de cobrança + +{% data reusables.package_registry.billing-for-container-registry %} + +### Alterações de domínio + +O domínio para o {% data variables.product.prodname_container_registry %} é `ghcr.io`. + +| Registro | Exemplo de URL | +| ----------------------------------------------------------------- | --------------------------------------------------- | +| Registro Docker de {% data variables.product.prodname_registry %} | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` | +| {% data variables.product.prodname_github_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME` | + +### Efetuar a autenticação com o registro do contêiner + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +Você deverá efetuar a autenticação no {% data variables.product.prodname_container_registry %} com a URL de base `ghcr.io`. Recomendamos criar um novo token de acesso para usar o {% data variables.product.prodname_container_registry %}. + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Fazer a migração de uma imagem do Docker usando a CLI do Docker + +Para mover imagens do Docker que você hospeda no registro do Docker do {% data variables.product.prodname_registry %}, você deve republicar as imagens para {% data variables.product.prodname_container_registry %}. Recomendamos republicar as imagens do Docker existentes usando a linha de comando na sua máquina local. + +1. Faça o login no registro do Docker usando um PAT temporário com pelo menos o escopo de `read:packages`. Este PAT só será usado para fazer o login no registro do Docker para puxar imagens e poderá ser excluído posteriormente. + {% raw %} + ```shell + $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin + ``` + {% endraw %} +2. Puxe para baixo a imagem que você gostaria de migrar, substituindo o PROPRIETÁRIO pelo nome do usuário ou conta de organização proprietária do repositório, REPOSITÓRIO pelo nome do repositório que contém seu projeto, IMAGE_NAME pelo o nome do pacote ou imagem, VERSÃO pela tag para a imagem que você deseja instalar. Por exemplo, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` move a tag mais recente da imagem `octoshift/octoshift` na organização octo-org. + ```shell + $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + +3. Remarque a imagem com o novo domínio e um novo nome de imagem. Para obter mais informações, consulte "[Tag do Docker](https://docs.docker.com/engine/reference/commandline/tag/)" na documentação Docker. Use a mesma URL que você usou na etapa anterior para a URL FONTE. Substitua TARGET_OWNER pelo usuário ou organização para o qual você está migrando a imagem do contêiner e substitua TARGET_IMAGE_NAME pelo novo nome de imagem de {% data variables.product.prodname_container_registry %}. + ```shell + $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION + ``` + +4. Fazer login no novo + +{% data variables.product.prodname_container_registry %}. Recomendamos criar um novo PAT limitado aos escopos `read:packages` e `write: packages` já que você não precisa mais do escopo `repositório` e seu PAT anterior pode não ter o escopo `write:packages`. + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + ``` + {% endraw %} +5. Faça push da sua imagem re-etiquetada para o {% data variables.product.prodname_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION + ``` + +### Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %} + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +Se tiver um fluxo de trabalho de {% data variables.product.prodname_actions %} que usa uma imagem do Docker do registro Docker do {% data variables.product.prodname_registry %}, você deverá atualizar seu fluxo de trabalho para {% data variables.product.prodname_container_registry %} para permitir acesso anônimo para imagens públicas de contêiner, permissões de acesso refinado e melhor compatibilidade de armazenamento e largura de banda para contêineres. + +1. Migre as suas imagens do Docker para o novo {% data variables.product.prodname_container_registry %} em `ghcr.io`. Por exemplo, consulte "[Migrar uma imagem do Docker usando a CLI do Docker](#migrating-a-docker-image-using-the-docker-cli)". + +2. No seu arquivo de fluxo de trabalho do {% data variables.product.prodname_actions %}, atualize a URL do pacote de `https://docker.pkg.github.com` para `ghcr.io`. + +3. Adicione seu novo token de acesso de autenticação pessoal (PAT) de {% data variables.product.prodname_container_registry %} como um segredo do GitHub Action. {% data variables.product.prodname_github_container_registry %} não é compatível com o uso do `GITHUB_TOKEN` para o seu PAT. Portanto, você deve usar uma variável personalizada diferente, como `CR_PAT`. Para obter mais informações, consulte "[Criar e armazenar segredos encriptados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". + +4. No seu arquivo de fluxo de trabalho de {% data variables.product.prodname_actions %} atualize a autenticação do PAT substituindo o seu PAT do registro do Docker ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) por uma nova variável para o seu PAT de {% data variables.product.prodname_container_registry %}, como, por exemplo, {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}. + +#### Exemplo de fluxo de trabalho atualizado + +Se parte de seu fluxo de trabalho acessou uma imagem do Docker hospedada pelo registro Docker dessa forma: + +{% raw %} +```yaml +echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin +docker pull docker.pkg.github.com/github/octoshift/octoshift:latest +docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest +docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA +``` +{% endraw %} + +Você deverá atualizar o seu fluxo de trabalho com a nova URL de {% data variables.product.prodname_container_registry %} e PAT dessa forma: + +{% raw %} +```yaml +# new login with new container registry url and PAT +echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin +# new container registry urls added +docker pull ghcr.io/github/octoshift:latest +docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest +docker push ghcr.io/github/octoshift:$GITHUB_SHA +``` +{% endraw %} diff --git a/translations/pt-BR/content/packages/guides/package-client-guides-for-github-packages.md b/translations/pt-BR/content/packages/guides/package-client-guides-for-github-packages.md new file mode 100644 index 0000000000..6f77e8b9bd --- /dev/null +++ b/translations/pt-BR/content/packages/guides/package-client-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Package client guides for GitHub Packages +shortTitle: Package client guides for GitHub Packages +intro: 'You can publish and retrieve package client images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/pt-BR/content/packages/guides/pushing-and-pulling-docker-images.md b/translations/pt-BR/content/packages/guides/pushing-and-pulling-docker-images.md new file mode 100644 index 0000000000..f9d2af67f2 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/pushing-and-pulling-docker-images.md @@ -0,0 +1,106 @@ +--- +title: Fazer push e pull das imagens do Docker +intro: 'Você pode armazenar e gerenciar imagens de Docker em {% data variables.product.prodname_github_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +Para fazer push e pull das imagens de contêiner pertencentes a uma organização, um administrador da organização deve habilitar o {% data variables.product.prodname_github_container_registry %} para a organização. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". + +### Autenticar-se no {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Fazer push das imagens do contêiner + +Este exemplo faz push da versão mais recente de `IMAGE-NAME`. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +Este exemplo faz push da versão `2.5` da imagem. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 + ``` + +Ao publicar um pacote pela primeira vez a visibilidade-padrão será privada. Para alterar a visibilidade ou definir permissões de acesso, consulte "[Configurar controle de acesso e visibilidade para imagens de contêiner](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)". + +### Fazer pull das imagens de contêiner + +#### Pull por resumo + +Para garantir que você esteja sempre usando a mesma imagem, você pode especificar a versão exata da imagem de contêiner que você deseja fazer pull pelo valor do SHA do `resumo`. + +1. Para encontrar o valor do SHA do resumo, use `docker inspect` or `docker pull` e copie o valor de SHA após `Digest:` + ```shell + $ docker inspect ghcr.io/OWNER/IMAGE_NAME + ``` +2. Remova a imagem localmente, conforme necessário. + ```shell + $ docker rmi ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +3. Faça pull da imagem do contêiner com `@YOUR_SHA_VALUE` após o nome da imagem. + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs + ``` + +#### Pull por nome + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME + ``` + +#### Pull por nome e versão + +Exemplo de CLI do Docker mostrando uma imagem extraída pelo seu nome e a tag de versão `1.14.1`: + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1 + > 5e35bd43cf78: Pull complete + > 0c48c2209aab: Pull complete + > fd45dd1aad5a: Pull complete + > db6eb50c2d36: Pull complete + > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e + > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 + > ghcr.io/orgname/image-name/release:1.14.1 + ``` + +#### Pull por nome e última versão + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest + > latest: Pulling from user/image-name + > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 + > Status: Downloaded newer image for ghcr.io/user/image-name:latest + > ghcr.io/user/image-name:latest + ``` + +### Criar imagens de contêiner + +Este exemplo cria a imagem `hello_docker`: + ```shell + $ docker build -t hello_docker . + ``` + +### Marcar imagens de contêiner + +1. Encontre o ID da imagem do Docker que você deseja marcar. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +2. Marque a sua imagem do Docker usando o ID da imagem, o nome da imagem desejada e a hospedagem de destino. + ```shell + $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest + ``` diff --git a/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md b/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md new file mode 100644 index 0000000000..cdb03488b8 --- /dev/null +++ b/translations/pt-BR/content/packages/guides/using-github-packages-with-github-actions.md @@ -0,0 +1,55 @@ +--- +title: Usar o GitHub Packages com o GitHub Actions +intro: 'É possível configurar um fluxo de trabalho no {% data variables.product.prodname_actions %} para publicar ou instalar automaticamente um pacote do {% data variables.product.prodname_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions + - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Sobre {% data variables.product.prodname_registry %} com {% data variables.product.prodname_actions %} + +{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)". + +Você pode estender os recursos de CI e CD do seu repositório publicando ou instalando pacotes como parte do seu fluxo de trabalho. + +{% if currentVersion == "free-pro-team@latest" %} +#### Autenticar-se no {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.container-registry-beta %} + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +Para um exemplo de autenticação, consulte "[Efetuar a autenticação com o {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)". + +{% endif %} + +#### Efetuar a autenticação nos registros do pacote em {% data variables.product.prodname_dotcom %} + +{% if currentVersion == "free-pro-team@latest" %}Se você deseja que o fluxo de trabalho efetue a autenticação em {% data variables.product.prodname_registry %} para acessar um registro de pacotes diferentes do {% data variables.product.prodname_container_registry %} em {% data variables.product.product_name %}, {% else %}Para efetuar a autenticação nos registros de pacotes no {% data variables.product.product_name %},{% endif %} recomendamos usar o `GITHUB_TOKEN` que {% data variables.product.product_name %} cria automaticamente para o seu repositório quando você habilita {% data variables.product.prodname_actions %} em vez de um token de acesso pessoal para autenticação. O `GITHUB_TOKEN` tem escopos `read:packages` e `write:packages` do repositório atual. Para bifurcações, o token também tem o escopo `read:packages` para o repositório principal. + +Você pode fazer referência ao `GITHUB_TOKEN` no seu arquivo de fluxo de trabalho usando o contexto {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %}. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". + +### Publicar um pacote usando uma ação + +Você pode publicar pacotes como parte do fluxo da sua integração contínua (CI) usando o {% data variables.product.prodname_actions %}. Por exemplo, você pode configurar um fluxo de trabalho para que sempre que um desenvolvedor fizer push do código para o branch-padrão, o fluxo de trabalho executará testes de CI. Se esses testes passarem, o fluxo de trabalho publicará uma nova versão de pacote no {% data variables.product.prodname_registry %}. Este fluxo de trabalho automatiza a criação de novas versões de pacotes somente se o código atender aos seus padrões de qualidade. + +{% data reusables.package_registry.actions-configuration %} + +### Instalar um pacote usando uma ação + +Você pode instalar pacotes como parte de seu fluxo de CI usando o {% data variables.product.prodname_actions %}. Por exemplo, você poderia configurar um fluxo de trabalho para que sempre que um desenvolvedor fizesse push do código para um pull request, o fluxo de trabalho resolveria as dependências, fazendo o download e instalando pacotes hospedados pelo {% data variables.product.prodname_registry %}. Em seguida, o fluxo de trabalho pode executar testes de CI que exigem as dependências. + +Instalar pacotes hospedados pelo {% data variables.product.prodname_registry %} através de {% data variables.product.prodname_actions %} exige uma configuração mínima ou autenticação adicional ao usar `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} A transferência de dados também é grátis quando uma ação instala um pacote. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)".{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +`GITHUB_TOKEN` não pode instalar pacotes a partir de qualquer repositório privado além do repositório onde a ação é executada. Atualmente, você não pode usar `GITHUB_TOKEN` para efetuar a autenticação +{% data variables.product.prodname_github_container_registry %}. +{% endif %} + +{% data reusables.package_registry.actions-configuration %} diff --git a/translations/pt-BR/content/packages/index.md b/translations/pt-BR/content/packages/index.md index e19eda88bc..5f69c1a281 100644 --- a/translations/pt-BR/content/packages/index.md +++ b/translations/pt-BR/content/packages/index.md @@ -2,31 +2,46 @@ title: Documentação de GitHub Packages shortTitle: GitHub Package Registry intro: 'Aprenda a publicar e consumir com segurança pacotes, armazene seus pacotes junto com o seu código e compartilhe seus pacotes de forma privada com sua equipe ou publicamente com a comunidade de código aberto. Você também pode automatizar seus pacotes com {% data variables.product.prodname_actions %}.' +introLinks: + quickstart: /packages/quickstart + reference: /packages/manage-packages featuredLinks: - gettingStarted: - - /packages/publishing-and-managing-packages/about-github-packages - - /packages/getting-started-with-github-container-registry/about-github-container-registry - - /packages/getting-started-with-github-container-registry - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/publishing-and-managing-packages/publishing-a-package - - /packages/publishing-and-managing-packages/installing-a-package + guides: + - /packages/learn-github-packages + - /packages/guides/using-github-packages-with-github-actions + - /packages/manage-packages/installing-a-package popular: - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-apache-maven-for-use-with-github-packages + guideCards: + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/guides/enabling-improved-container-support + - /packages/guides/configuring-rubygems-for-use-with-github-packages +changelog: + - + title: Packages container support is an opt-in beta + date: '2020-11-17' + href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support + - + title: Organization admins access to containers + date: '2020-11-16' + href: https://github.blog/changelog/2020-11-16-packages-organization-admins-access-to-containers/ + - + title: Packages now respects IP allow list settings + date: '2020-11-12' + href: https://github.blog/changelog/2020-11-12-packages-now-respects-ip-allow-list-settings/ redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry - /github/managing-packages-with-github-package-registry +layout: product-landing versions: free-pro-team: '*' enterprise-server: '>=2.22' --- -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% link_with_intro /getting-started-with-github-container-registry %} -{% link_with_intro /managing-container-images-with-github-container-registry %} -{% link_with_intro /publishing-and-managing-packages %} -{% link_with_intro /using-github-packages-with-your-projects-ecosystem %} + + + + diff --git a/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md new file mode 100644 index 0000000000..021a4427ea --- /dev/null +++ b/translations/pt-BR/content/packages/learn-github-packages/about-github-packages.md @@ -0,0 +1,166 @@ +--- +title: Sobre o GitHub Packages +intro: '{% data variables.product.prodname_registry %} é um serviço de hospedagem de pacotes de software que permite que você hospede os seus pacotes de software de forma privada ou pública e que você use os pacotes como dependências nos seus projetos.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/about-github-package-registry + - /github/managing-packages-with-github-package-registry/about-github-package-registry + - /github/managing-packages-with-github-packages/about-github-packages + - /packages/publishing-and-managing-packages/about-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Sobre o {% data variables.product.prodname_registry %} + +{% data variables.product.prodname_registry %} is a package hosting service, fully integrated with {% data variables.product.prodname_dotcom %}. O {% data variables.product.prodname_registry %} combina seu código-fonte e pacotes em um só lugar para fornecer gerenciamento integrado de permissões e cobrança, para poder centralizar o desenvolvimento do seu software no {% data variables.product.product_name %}. + +Você pode integrar {% data variables.product.prodname_registry %} com as APIs de {% data variables.product.product_name %}, {% data variables.product.prodname_actions %} e webhooks para criar um fluxo de trabalho de ponta a ponta que inclui as suas soluções de código, CI e implantação. + +You can host multiple packages in one repository and see more information about each package by viewing the package's README, download statistics, version history, and more. + +{% if currentVersion == "free-pro-team@latest" %} +When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." + +{% data reusables.package_registry.container-registry-beta %} + +![Diagrama que mostra Node, RubyGems, Apache Maven, Gradle, Nuget e o registro do contêiner com suas urls de hospedagem](/assets/images/help/package-registry/packages-overview-diagram.png) + +{% endif %} + +#### Visualizar pacotes + +You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)." + +#### Sobre permissões e visibilidade de pacotes + +| | Registros de pacotes | +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Locais de hospedagem | Você pode hospedar vários pacotes em um só repositório. | +| Permissões | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | +| Visibilidade | {% data reusables.package_registry.public-or-private-packages %} + +{% if currentVersion == "free-pro-team@latest" %} +### Sobre a cobrança do {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". + +{% data reusables.package_registry.container-registry-beta-billing-note %} +{% endif %} + +### Clientes e formatos compatíveis + +O {% data variables.product.prodname_registry %} usa os comandos nativos de ferramentas de pacotes com os quais você já está familiarizado para publicar e instalar versões de pacote. +#### Suporte para registros de pacotes + +{% if currentVersion == "free-pro-team@latest" %} +Os registros do pacote usam `PACKAGE-TYPE.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` como a URL do host do pacote, substituindo `PACKAGE-TYPE` pelo espaço de nome do pacote. Por exemplo, o seu Gemfile será hospedado em `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`. + +{% else %} + +Os tipos de pacotes suportados no {% data variables.product.product_location %} podem variar, uma vez que o administrador do site pode habilitar ou desabilitar o suporte para diferentes tipos de pacotes. Para obter mais informações, consulte "[Gerenciar pacotes do GitHub para a sua empresa](/enterprise/admin/packages)". + +Se {% data variables.product.product_location %} tiver o isolamento de subdomínio habilitado, os registros dos pacotes usarão `PACKAGE-TYPE. OSTNAME/OWNER/REPOSITORY/IMAGE-NAME` como a URL hospedada do pacote, substituindo `PACKAGE-TYPE` pelo espaço de nome do pacote. Por exemplo, o seu arquivo Docker será hospedado em `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME`. + +Se o {% data variables.product.product_location %} tiver o isolamento de subdomínio desabilitado, os registros do pacote usarão `HOSTNAME/_registry/PACKAGE-TYPE/OWNER/REPOSITORY/IMAGE-NAME` como URL de host do pacote. Por exemplo, o seu Gemfile será hospedado em `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME`, substituindo *NOME DE HOST* pelo nome do host da sua instância do {% data variables.product.prodname_ghe_server %}. |{% endif %} + +{% if currentVersion == "free-pro-team@latest" %} +| Linguagem | Descrição | Formato do pacote | Cliente do pacote | Espaço de nome do pacote | +| ---------- | --------------------------------------------------------------------- | ------------------------------------ | ----------------- | ----------------------------------------------------- | +| JavaScript | Gerenciador de pacotes de nó | `package.json` | `npm` | `npm.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| Ruby | Gerenciador de pacotes de RubyGems | `Gemfile` | `gem` | `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Ferramenta de gerenciamento de projetos e compreensão do Apache Maven | `pom.xml` | `mvn` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Ferramenta de automação do build Gradle para Java | `build.gradle` ou `build.gradle.kts` | `gradle` | `maven.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | Gerenciamento de pacotes NuGet para .NET | `nupkg` | `dotnet` CLI | `nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | + +{% else %} + +Com o isolamento de subdomínio habilitado em {% data variables.product.product_location %}: + +| Linguagem | Descrição | Formato do pacote | Cliente do pacote | Espaço de nome do pacote | +| ---------- | --------------------------------------------------------------------- | ------------------------------------ | ----------------- | ----------------------------------------------- | +| JavaScript | Gerenciador de pacotes de nó | `package.json` | `npm` | `npm.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| Ruby | Gerenciador de pacotes de RubyGems | `Gemfile` | `gem` | `rubygems.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Ferramenta de gerenciamento de projetos e compreensão do Apache Maven | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Ferramenta de automação do build Gradle para Java | `build.gradle` ou `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | Gerenciamento de pacotes NuGet para .NET | `nupkg` | `dotnet` CLI | `nuget.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | +| N/A | Gerenciamento do contêiner do Docker | `arquivo Docker` | `Docker` | `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | + +Com o isolamento de subdomínio desabilitado em {% data variables.product.product_location %}: + +| Linguagem | Descrição | Formato do pacote | Cliente do pacote | Espaço de nome do pacote | +| ---------- | --------------------------------------------------------------------- | ------------------------------------ | ----------------- | --------------------------------------------------------- | +| JavaScript | Gerenciador de pacotes de nó | `package.json` | `npm` | `HOSTNAME/_registry/npm/OWNER/REPOSITORY/IMAGE-NAME` | +| Ruby | Gerenciador de pacotes de RubyGems | `Gemfile` | `gem` | `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Ferramenta de gerenciamento de projetos e compreensão do Apache Maven | `pom.xml` | `mvn` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | +| Java | Ferramenta de automação do build Gradle para Java | `build.gradle` ou `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | +| .NET | Gerenciamento de pacotes NuGet para .NET | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` | + +{% note %} + +**Observação:** O Docker não é compatível quando o isolamento de subdomínio está desativado. + +{% endnote %} + +Para obter mais informações sobre o isolamento de subdomínio, consulte "[Habilitar o isolamento de subdomínio](/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)." + +{% 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)." +{% endif %} +### Autenticar-se no {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +### Sobre escopos e permissões para registros de pacotes + +To install or publish a package, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. + +Por exemplo: +- Para fazer o download e instalar pacotes a partir de um repositório, seu token deve ter o escopo `read:packages`, e sua conta de usuário deve ter permissões de leitura para o repositório. +- Para excluir uma versão especificada de um pacote privado no {% data variables.product.product_name %}, seu token deve ter o escopo `delete:packages` e `repo`. Não é possível excluir pacotes públicos. Para obter mais informações, consulte "[Excluir um pacote](/packages/manage-packages/deleting-a-package)". + +| Escopo | Descrição | Permissões do repositório | +| ----------------- | --------------------------------------------------------------------------------------------------- | ------------------------- | +| `read:packages` | Faça o download e instale pacotes do {% data variables.product.prodname_registry %} | leitura | +| `write:packages` | Faça o upload e publique os pacotes em {% data variables.product.prodname_registry %} | gravação | +| `delete:packages` | Excluir versões especificadas de pacotes privados de {% data variables.product.prodname_registry %} | administrador | +| `repo` | Faça o upload e exclua os pacotes (junto com `write:packages` ou `delete:packages`) | gravação ou admin | + +Ao criar um fluxo de trabalho de {% data variables.product.prodname_actions %}, você pode usar o `GITHUB_TOKEN` para publicar e instalar pacotes no {% data variables.product.prodname_registry %} sem precisar armazenar e gerenciar um token de acesso pessoal. + +Para obter mais informações, consulte: +- "[Usando {% data variables.product.prodname_registry %} com {% data variables.product.prodname_actions %}](/packages/using-github-packages-with-your-projects-ecosystem/)" +- "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token/)" +- "[Escopos disponíveis](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)" + +### Gerenciar pacotes + +Você pode excluir uma versão de um pacote privado em {% data variables.product.product_name %} ou usar a API do GraphQL. Ao usar a API do GraphQL para consultar e excluir pacotes privados, você deve usar o mesmo token que você usa para efetuar a autenticação no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluir um pacote](/packages/manage-packages/deleting-a-package)" e "[Formando chamadas com GraphQL](/graphql/guides/forming-calls-with-graphql)". + +Você pode configurar webhooks para assinar eventos relacionados aos pacotes, como quando um pacote é publicado ou atualizado. Para obter mais informações, consulte o evento de webhook de "[`pacote`](/webhooks/event-payloads/#package)". + +### Entrar em contato com o suporte + +{% if currentVersion == "free-pro-team@latest" %} +Se você tiver feedback ou pedidos de recursos para +{% data variables.product.prodname_registry %}, use o [formulário de feedback para {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages). + +Entre em contato com {% data variables.contact.github_support %} sobre {% data variables.product.prodname_registry %} usando o [nosso formulário de contato](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) se: + +* Você encontrar qualquer coisa que contradiga a documentação +* Você encontra erros vagos ou pouco claros +* Seu pacote publicado contém dados confidenciais, como violações do RGPD, chaves API ou informações de identificação pessoal + +{% else %} +Se precisar de suporte para +{% data variables.product.prodname_registry %}, entre em contato com os administradores do site. + +{% endif %} diff --git a/translations/pt-BR/content/packages/learn-github-packages/core-concepts-for-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/core-concepts-for-github-packages.md new file mode 100644 index 0000000000..fb69acff2b --- /dev/null +++ b/translations/pt-BR/content/packages/learn-github-packages/core-concepts-for-github-packages.md @@ -0,0 +1,28 @@ +--- +title: Core concepts for GitHub Packages +intro: 'Abaixo está uma lista de termos comuns de {% data variables.product.prodname_registry %} que usamos em todos os nossos sites e documentação.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Package + +Um pacote é um software auto-contido e reutilizável que inclui código e metadados que um desenvolvedor agrupa em um local comum para que os outros possam usar. Os metadados de um pacote podem incluir o número da versão, o nome e as dependências do código. Os pacotes simplificam a utilização e distribuição de soluções para problemas comuns, como a necessidade de estruturas para o desenvolvimento ou o teste de um projeto, linters para melhorar a qualidade do código ou ferramentas de aprendizado de máquina padrão do setor para energizar sua aplicação. Há pacotes em muitos ecossistemas. Por exemplo, você pode empacotar Node.js e código Java ou imagens de contêiner. + +### Contêiner + +Um contêiner é uma unidade de software projetada para implantar, de forma confiável, o software de forma padronizada em qualquer plataforma. Um contêiner opera como um ambiente virtual ou instância isolada que pode executar vários pacotes de software e componentes no mesmo kernel do seu sistema operacional. Os contêineres usam menos recursos do que as máquinas virtuais, porque não precisam incluir seu próprio hardware virtual para ser executado. Os contêineres são criados usando um arquivo de imagem de contêiner, como um arquivo Docker e um cliente do contêiner ou um programa de tempo de execução. + +### Imagem do contêiner + +Uma imagem de contêiner é um tipo de arquivo de pacote que especifica os requisitos de software para executar um aplicativo a partir de um container. Uma imagem de contêiner normalmente inclui código do aplicativo, bibliotecas e instruções de tempo de execução. Para garantir que os mesmos detalhes de imagem são usados onde uma imagem é implantada e executada, uma imagem de contêiner é versionada automaticamente e não pode ser alterada, uma vez que é construída em um container. + +### Contêiner Docker + +Um contêiner do Docker é um tipo de contêiner de código aberto construído na plataforma do Docker. O formato de imagem original do Docker tornou-se a Especificação de Imagem de OCI (Iniciativa de Contêiner Aberto). Para obter mais informações, consulte a "[Documentação do Docker](https://docs.docker.com/get-started/overview/)". diff --git a/translations/pt-BR/content/packages/learn-github-packages/index.md b/translations/pt-BR/content/packages/learn-github-packages/index.md new file mode 100644 index 0000000000..a21e10fe4c --- /dev/null +++ b/translations/pt-BR/content/packages/learn-github-packages/index.md @@ -0,0 +1,16 @@ +--- +title: Learn GitHub Packages +shortTitle: Learn GitHub Packages +intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.' +redirect_from: + - /packages/getting-started-with-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /about-github-packages %} +{% link_in_list /core-concepts-for-github-packages %} +{% link_in_list /publishing-a-package %} diff --git a/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md new file mode 100644 index 0000000000..07d6e7ef7d --- /dev/null +++ b/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md @@ -0,0 +1,37 @@ +--- +title: Publicar um pacote +intro: 'Você pode publicar um pacote no {% data variables.product.prodname_registry %} para disponibilizar o pacote para que outros façam download e reutilizem.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-a-package + - /packages/publishing-and-managing-packages/publishing-a-package +permissions: Qualquer pessoa com permissões de gravação para um repositório pode publicar um pacote nesse repositório. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Sobre os pacotes publicados + +Você pode ajudar as pessoas a entender e usar seu pacote fornecendo uma descrição e outros detalhes como, por exemplo, a instalação e instruções de uso na página do pacote. GitHub provides metadata for each version, such as the publication date, download activity, and recent versions. Para uma página de pacote de exemplo, veja [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). + +{% data reusables.package_registry.public-or-private-packages %} Um repositório pode conter mais de um pacote. Para evitar confusão, certifique-se de que o LEIAME e a descrição fornecem informações claras sobre cada pacote. + +{% if currentVersion == "free-pro-team@latest" %} +Se uma nova versão de um pacote corrigir uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório. +{% data variables.product.prodname_dotcom %} revisa a cada consultoria de segurança publicado e pode usá-lo para enviar {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)." +{% endif %} + +### Publicar um pacote + +Você pode publicar um pacote em {% data variables.product.prodname_registry %} usando qualquer {% if currentVersion == "free-pro-team@latest" %}cliente do pacote compatível{% else %}pacote habilitado para sua instância{% endif %}, seguindo as mesmas diretrizes gerais. + +1. Crie ou use um token de acesso existente com os escopos apropriados para a tarefa que você deseja realizar. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +2. Efetue a autenticação em {% data variables.product.prodname_registry %} usando seu token de acesso e as instruções para seu cliente do pacote. +3. Publique o pacote usando as instruções do seu cliente de pacote. + +Para obter instruções específicas para o seu cliente de pacotes, consulte "[Usar o {% data variables.product.prodname_registry %} com o ecossistema do seu projeto](/packages/using-github-packages-with-your-projects-ecosystem)". + +Após publicar um pacote, você poderá visualizá-lo no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte “[Visualizar pacotes](/packages/publishing-and-managing-packages/viewing-packages).” diff --git a/translations/pt-BR/content/packages/manage-packages/deleting-a-package.md b/translations/pt-BR/content/packages/manage-packages/deleting-a-package.md new file mode 100644 index 0000000000..f8be92a63f --- /dev/null +++ b/translations/pt-BR/content/packages/manage-packages/deleting-a-package.md @@ -0,0 +1,81 @@ +--- +title: Excluir um pacote +intro: 'Você pode excluir uma versão de um pacote privado usando o GraphQL ou no {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/deleting-a-package + - /packages/publishing-and-managing-packages/deleting-a-package +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% if currentVersion == "free-pro-team@latest" %} +### Sobre a exclusão de imagem de contêiner + +To delete a container image package on {% data variables.product.product_name %}, see "[Deleting a container image](/packages/guides/deleting-a-container-image)." + +{% endif %} + +### Sobre a exclusão de pacotes privados + +Você só pode excluir uma versão específica de um pacote privado no {% data variables.product.product_name %} ou com a API do GraphQL. Para impedir que um pacote privado inteiro apareça no {% data variables.product.product_name %}, você deve primeiro excluir todas as versões do pacote. + +{% if currentVersion == "free-pro-team@latest" %} +### Sobre a exclusão de pacotes públicos + +Para evitar quebrar projetos que podem depender dos seus pacotes, você não pode excluir um pacote público inteiro ou versões específicas de um pacote público. + +Em circunstâncias especiais, como por razões legais ou para estar de acordo com os padrões do RGPD, você pode pedir que {% data variables.contact.github_support %} exclua um pacote público para você, usando [nosso formulário de contato](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry). + +{% else %} + +No momento, {% data variables.product.prodname_registry %} em {% data variables.product.product_location %} não é compatível com a exclusão de pacotes públicos. + +{% endif %} + +### Excluir uma versão de um pacote privado no {% data variables.product.product_name %} + +Para excluir uma versão privada, você deve ter permissões de administrador no repositório. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +3. Clique no nome do pacote que você deseja excluir. ![Nome do pacote](/assets/images/help/package-registry/select-pkg-cloud.png) +4. À direita, use o menu suspenso **Editar pacote** e selecione "Gerenciar versões". ![Nome do pacote](/assets/images/help/package-registry/manage-versions.png) +5. À direita da versão que você deseja excluir, clique em **Excluir**. ![Botão de excluir pacote](/assets/images/help/package-registry/delete-package-button.png) +6. Para confirmar a exclusão, digite o nome do pacote e clique em **Eu entendo as consequências. Exclua esta versão**. ![Botão de confirmar exclusão de pacote](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Excluir uma versão de um pacote privado com o GraphQL + +Use a mutação `deletePackageVersion` na API do GraphQL. Você deve usar um token com os escopos `read:packages`, `delete:packages` e `repo`. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#about-tokens)." + +Aqui está um exemplo de comando cURL para excluir uma versão de pacote com o ID de versão do pacote `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, usando um token de acesso pessoal. + +{% if currentVersion == "free-pro-team@latest" %} +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +https://api.github.com/graphql +``` + +{% else %} + +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +HOSTNAME/graphql +``` + +{% endif %} + +To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `registryPackagesForQuery` connection. Você vai precisar de um token com os escopos `read:packages` e `repo`. You will need a token with the `read:packages` and `repo` scopes. + +Para obter mais informações sobre a mutação `deletePackageVersion`, consulte "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)". + +Você não pode excluir um pacote inteiro, mas se excluir todas as versões de um pacote, o pacote não será mais exibido em {% data variables.product.product_name %} diff --git a/translations/pt-BR/content/packages/manage-packages/index.md b/translations/pt-BR/content/packages/manage-packages/index.md new file mode 100644 index 0000000000..b2f8bd537c --- /dev/null +++ b/translations/pt-BR/content/packages/manage-packages/index.md @@ -0,0 +1,18 @@ +--- +title: Managing GitHub packages +shortTitle: Managing GitHub packages +intro: 'Você pode publicar novos pacotes no {% data variables.product.prodname_registry %}, visualizar e instalar pacotes existentes e, em circunstâncias especiais, excluir pacotes existentes.' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-and-managing-packages + - /github/packages/publishing-and-managing-packages + - /packages/publishing-and-managing-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /viewing-packages %} +{% link_in_list /installing-a-package %} +{% link_in_list /deleting-a-package %} diff --git a/translations/pt-BR/content/packages/manage-packages/installing-a-package.md b/translations/pt-BR/content/packages/manage-packages/installing-a-package.md new file mode 100644 index 0000000000..b8231b1b85 --- /dev/null +++ b/translations/pt-BR/content/packages/manage-packages/installing-a-package.md @@ -0,0 +1,29 @@ +--- +title: Instalar um pacote +intro: 'Você pode instalar um pacote do {% data variables.product.prodname_registry %} e usá-lo como uma dependência no seu próprio projeto.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/installing-a-package + - /packages/publishing-and-managing-packages/installing-a-package +permissions: Qualquer pessoa com permissões de leitura para um repositório pode instalar um pacote a partir desse repositório. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Sobre a instalação do pacote + +Você pode pesquisar {% data variables.product.product_name %} para encontrar pacotes no {% data variables.product.prodname_registry %} que você pode instalar no seu próprio projeto. Para obter mais informações, consulte "[Pesquisar pacotes no {% data variables.product.prodname_registry %}](/github/searching-for-information-on-github/searching-for-packages)". + +Depois de encontrar um pacote, você pode ler a descrição e as instruções de instalação e utilização na página de pacotes. + +### Instalar um pacote + +Você pode instalar um pacote de {% data variables.product.prodname_registry %} usando qualquer {% if currentVersion == "free-pro-team@latest" %}tipo de pacote cliente compatível{% else %}pacote habilitado para sua instância{% endif %}, seguindo as mesmas diretrizes gerais. + +1. Efetue a autenticação com {% data variables.product.prodname_registry %} usando as instruções para seu cliente de pacote. Para obter mais informações, consulte "[Sobre tokens](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". +2. Instale o pacote usando as instruções para seu cliente de pacote. + +Para obter instruções específicas para o seu cliente de pacotes, consulte "[Usar o {% data variables.product.prodname_registry %} com o ecossistema do seu projeto](/packages/using-github-packages-with-your-projects-ecosystem)". diff --git a/translations/pt-BR/content/packages/manage-packages/viewing-packages.md b/translations/pt-BR/content/packages/manage-packages/viewing-packages.md new file mode 100644 index 0000000000..c6b94cdd42 --- /dev/null +++ b/translations/pt-BR/content/packages/manage-packages/viewing-packages.md @@ -0,0 +1,50 @@ +--- +title: Visualizar pacotes +intro: 'É possível ver informações sobre pacotes publicados em um repositório e limitar os resultados por organização ou usuário.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/viewing-packages + - /packages/publishing-and-managing-packages/viewing-packages +permissions: Qualquer pessoa com permissão de leitura em um repositório pode ver os pacotes do repositório. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Sobre a visualização de pacotes + +Os pacotes devem ser instalados no nível do repositório, mas você pode visualizar todos os pacotes em uma organização e todos os pacotes que você publicou. {% data reusables.package_registry.package-page-info %} + +### Visualizar pacotes de um repositório + +É possível ver todos os pacotes em um repositório e pesquisar um pacote específico no repositório. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + +### Visualizar pacotes de uma organização + +Você pode ver todos os pacotes instalados em uma organização e pesquisar um pacote específico instalado nos repositórios de uma organização. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Abaixo do nome da sua organização, clique em +{% octicon "package" aria-label="The package icon" %} **Pacotes**. +{% data reusables.package_registry.navigate-to-packages %} + +### Visualizar seus pacotes + +Você pode ver todos os pacotes que você instalou e pesquisar um pacote específico que você instalou em todas as organizações e repositórios. + +{% data reusables.profile.access_profile %} +2. No topo da página de perfil, na navegação principal, clique em **Pacotes**. ![Aba Project (Projeto)](/assets/images/help/package-registry/user-packages-tab.png) +{% data reusables.package_registry.navigate-to-packages %} + +### Leia mais + +- "[Procurar pacotes](/github/searching-for-information-on-github/searching-for-packages)" diff --git a/translations/pt-BR/content/packages/quickstart.md b/translations/pt-BR/content/packages/quickstart.md new file mode 100644 index 0000000000..19bfb06577 --- /dev/null +++ b/translations/pt-BR/content/packages/quickstart.md @@ -0,0 +1,110 @@ +--- +title: Quickstart for GitHub Packages +intro: 'Publish to {% data variables.product.prodname_registry %} in 5 minutes or less with {% data variables.product.prodname_actions %}.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Introdução + +You only need an existing {% data variables.product.prodname_dotcom %} repository to publish a package to {% data variables.product.prodname_registry %}. In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}. Feel free to create a new repository for this Quickstart. You can use it to test this and future {% data variables.product.prodname_actions %} workflows. + +### Publishing your package + +1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. Create a private repository if you’d like to delete this package later, public packages cannot be deleted. Para obter mais informações, consulte "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clone the repository to your local machine. + {% raw %} + ```shell + $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git + $ cd YOUR-REPOSITORY + ``` + {% endraw %} +3. Create an `index.js` file and add a basic alert to say "Hello world!" + {% raw %} + ```javascript{:copy} + alert("Hello, World!"); + ``` + {% endraw %} +4. Initialize an npm package. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0` if you do not have any tests. Commit your changes and push them to +{% data variables.product.prodname_dotcom %}. + {% raw %} + ```shell + $ npm init + ... + package name: @YOUR-USERNAME/YOUR-REPOSITORY + ... + test command: exit 0 + ... + + $ npm install + $ git add index.js package.json package-lock.json + $ git commit -m "initialize npm package" + $ git push + ``` + {% endraw %} +5. Do seu repositório no {% data variables.product.prodname_dotcom %}, crie um novo arquivo no diretório `.github/workflows` denominado `release-package.yml`. Para obter mais informações, consulte "[Criar arquivos](/github/managing-files-in-a-repository/creating-new-files)". +6. Copy the following YAML content into the `release-package.yml` file. + {% raw %} + ```yaml{:copy} + name: Node.js Package + + on: + release: + types: [created] + + jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm ci + - run: npm test + + publish-gpr: + needs: build + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + registry-url: https://npm.pkg.github.com/ + - run: npm ci + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + ``` + {% endraw %} +7. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Em seguida, para criar um pull request, clique em **Propor novo arquivo**. +8. **Merge** the pull request. +9. Navigate to the **Code** tab and create a new release to test the workflow. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." + +Creating a new release in your repository triggers the workflow to build and test your code. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. + +### Viewing your published package + +Packages are published at the repository level. You can see all the packages in a repository and search for a specific package. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + + +### Installing a published package + +Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)." + +### Próximas etapas + +The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more. + +Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Pronto para começar? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}: + +- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions +- "[Guides](/packages/guides)" for specific uses cases and examples diff --git a/translations/pt-BR/content/rest/README.md b/translations/pt-BR/content/rest/README.md new file mode 100644 index 0000000000..55aaa5edda --- /dev/null +++ b/translations/pt-BR/content/rest/README.md @@ -0,0 +1,10 @@ +# REST + +The `/content/rest` directory is where the GitHub REST API docs live! + +* The `/content/rest/guides` and `/content/rest/overview` directories contain regular articles. These are human-editable. +* The `/content/rest/reference` directory contains an article for each group of endpoints in the GitHub REST API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/rest/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/rest/README.md`](/lib/rest/README.md). + + **As a result, we cannot accept contributions to REST API reference content in this repository.** 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 c789e30d45..67fda91bcb 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 @@ -376,7 +376,7 @@ Continue aprendendo com o próximo guia da API [Princípios básicos da autentic [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore [issues-api]: /rest/reference/issues -[link-header]: http://www.w3.org/wiki/LinkHeader/ +[link-header]: https://www.w3.org/wiki/LinkHeader [conditional-requests]: /rest#conditional-requests [rate-limiting]: /rest#rate-limiting [rate-limiting]: /rest#rate-limiting diff --git a/translations/pt-BR/content/rest/overview/api-previews.md b/translations/pt-BR/content/rest/overview/api-previews.md index 672a4051f1..7111220899 100644 --- a/translations/pt-BR/content/rest/overview/api-previews.md +++ b/translations/pt-BR/content/rest/overview/api-previews.md @@ -61,7 +61,7 @@ Cria, lista, atualiza e exclui ambientes para hooks pre-receive. ### Integrações -Gerencie as [integrações](/early-access/integrations/) através da API. +Gerencie as [integrações](/v3/integrations) através da API. **Tipo de mídia personalizada:** `machine-man-preview` **Anunciado em:** [2016-09-14](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/) diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md index 15ce3204cc..11477bb9a2 100644 --- a/translations/pt-BR/content/rest/overview/libraries.md +++ b/translations/pt-BR/content/rest/overview/libraries.md @@ -72,7 +72,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md index 30cc142a97..0dce111619 100644 --- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md @@ -301,18 +301,22 @@ gem: ### 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, +default. You can specify further pages with the `page` parameter. For some +resources, you can also set a custom page size up to 100 with the `per_page` parameter. +Note that for technical reasons not all endpoints respect the `per_page` parameter, see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -Note that page numbering is 1-based and that omitting the `?page` +Note that page numbering is 1-based and that omitting the `page` parameter will return the first 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. + For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. #### Link header @@ -323,13 +327,17 @@ For more information on pagination, check out our guide on [Traversing with Pagi {% endnote %} -The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information: +The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information. For example: Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" _The example includes a line break for readability._ +Or, if the endpoint uses cursor-based pagination: + + Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next", + This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](http://tools.ietf.org/html/rfc6570). The possible `rel` values are: diff --git a/translations/pt-BR/content/rest/overview/troubleshooting.md b/translations/pt-BR/content/rest/overview/troubleshooting.md index 3ae646ccf1..a1cdb2c8d3 100644 --- a/translations/pt-BR/content/rest/overview/troubleshooting.md +++ b/translations/pt-BR/content/rest/overview/troubleshooting.md @@ -52,7 +52,7 @@ curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos #### Calls to OAuth Authorizations API -If you're making [OAuth Authorization API](/enterprise-server@2.22/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: +If you're making [OAuth Authorization API](/enterprise-server/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: ```bash curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}' diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md index b8401b873d..bcbefb21d9 100644 --- a/translations/pt-BR/content/rest/reference/enterprise-admin.md +++ b/translations/pt-BR/content/rest/reference/enterprise-admin.md @@ -57,6 +57,16 @@ The current version of your enterprise is returned in the response header of eve {% endif %} +{% if currentVersion == "free-pro-team@latest" %} + +## Log de auditoria + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ## Cobrança diff --git a/translations/pt-BR/content/rest/reference/index.md b/translations/pt-BR/content/rest/reference/index.md index f109f0aae3..eddc048fad 100644 --- a/translations/pt-BR/content/rest/reference/index.md +++ b/translations/pt-BR/content/rest/reference/index.md @@ -15,8 +15,6 @@ versions: {% link_in_list /apps %} {% link_in_list /billing %} {% link_in_list /checks %} - - {% link_in_list /codes-of-conduct %} {% link_in_list /code-scanning %} {% link_in_list /emojis %} @@ -39,6 +37,7 @@ versions: {% link_in_list /repos %} {% link_in_list /scim %} {% link_in_list /search %} +{% link_in_list /secret-scanning %} {% link_in_list /teams %} {% link_in_list /users %} {% link_in_list /permissions-required-for-github-apps %} diff --git a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md index 627e225519..f4336a141c 100644 --- a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md @@ -819,10 +819,19 @@ _Equipes_ * [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) - {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Permission on "secret scanning alerts" + +- [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) + +- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read) + +- [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permissão em "eventos de segurança" - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) diff --git a/translations/pt-BR/content/rest/reference/secret-scanning.md b/translations/pt-BR/content/rest/reference/secret-scanning.md new file mode 100644 index 0000000000..01661c31b2 --- /dev/null +++ b/translations/pt-BR/content/rest/reference/secret-scanning.md @@ -0,0 +1,12 @@ +--- +title: Varredura secreta +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.secret-scanning.api-beta %} + +The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a private repository. For more information on secret scanning for private repositories, see "[Securing your repository](/github/administering-a-repository/securing-your-repository)." + +{% include rest_operations_at_current_path %} diff --git a/translations/pt-BR/data/glossaries/external.yml b/translations/pt-BR/data/glossaries/external.yml index 9ec9566950..ec1b5ac095 100644 --- a/translations/pt-BR/data/glossaries/external.yml +++ b/translations/pt-BR/data/glossaries/external.yml @@ -390,7 +390,7 @@ - term: main description: >- - Branch de desenvolvimento padrão. Sempre que um repositório do Git é criado, um branch "mestre" também é criado e passa a ser o branch ativo. Contém o desenvolvimento local na maioria dos casos, embora isso ocorra meramente por convenção e não seja obrigatório. + The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. - term: mestre description: >- diff --git a/translations/pt-BR/data/products.yml b/translations/pt-BR/data/products.yml index 3757cfc57b..dbdfad2a91 100644 --- a/translations/pt-BR/data/products.yml +++ b/translations/pt-BR/data/products.yml @@ -5,10 +5,12 @@ productsInOrder: - github - administrador + - discussões - ações - pacotes - developers - rest - graphql - insights + - education - desktop diff --git a/translations/pt-BR/data/release-notes/2-20/0.yml b/translations/pt-BR/data/release-notes/2-20/0.yml new file mode 100644 index 0000000000..f3e2ef1aa5 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/0.yml @@ -0,0 +1,44 @@ +--- +date: '11-02-2020' +sections: + features: + - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" + - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" + - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + changes: + - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..343d6b8786 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/1.yml @@ -0,0 +1,21 @@ +--- +date: '27-02-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + bugs: + - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..d8ca3f980d --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/10.yml @@ -0,0 +1,21 @@ +--- +date: '23-06-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" + - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..8965ed161c --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/11.yml @@ -0,0 +1,19 @@ +--- +date: '09-07-2020' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..55a7c1bcea --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/12.yml @@ -0,0 +1,17 @@ +--- +date: '21-07-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + bugs: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + changes: + - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..6a3fd499f1 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/13.yml @@ -0,0 +1,22 @@ +--- +date: '11-08-2020' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..9278f5df95 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/14.yml @@ -0,0 +1,13 @@ +--- +date: '12-08-2020' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..aa3c664487 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/15.yml @@ -0,0 +1,24 @@ +date: '2020-08-26' +sections: + security_fixes: + - >- + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, + https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} + - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + bugs: + - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' + changes: + - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-20/16.yml b/translations/pt-BR/data/release-notes/2-20/16.yml new file mode 100644 index 0000000000..3e39a00d39 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/16.yml @@ -0,0 +1,13 @@ +--- +date: '08-09-2020' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..c3a1844547 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/17.yml @@ -0,0 +1,13 @@ +--- +date: '23-09-2020' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..a49ccb6fb3 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/18.yml @@ -0,0 +1,26 @@ +--- +date: '09-10-2020' +sections: + security_fixes: + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..6fab675bea --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/19.yml @@ -0,0 +1,14 @@ +--- +date: '20-10-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..32b64d7d47 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/2.yml @@ -0,0 +1,28 @@ +--- +date: '10-03-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + bugs: + - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + changes: + - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..e07b39c737 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/20.yml @@ -0,0 +1,16 @@ +--- +date: '03-11-2020' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..3efb239e52 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/21.yml @@ -0,0 +1,15 @@ +--- +date: '17-11-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..3042cc087d --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/22.yml @@ -0,0 +1,19 @@ +--- +date: '03-12-2020' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..152f8862a0 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/3.yml @@ -0,0 +1,15 @@ +--- +date: '12-03-2020' +sections: + bugs: + - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..a2a4dddbad --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/4.yml @@ -0,0 +1,18 @@ +--- +date: '25-03-2020' +sections: + bugs: + - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..d7fa4e230c --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/5.yml @@ -0,0 +1,20 @@ +--- +date: '07-04-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + bugs: + - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..e51046e01c --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/6.yml @@ -0,0 +1,27 @@ +--- +date: '23-04-2020' +sections: + security_fixes: + - '**HIGH**: OpenSSL has been updated to address [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 %}' + - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + bugs: + - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" + - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + changes: + - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% 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: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..eb697aace6 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/7.yml @@ -0,0 +1,21 @@ +--- +date: '05-05-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + bugs: + - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' + - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..65c54e653e --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/8.yml @@ -0,0 +1,20 @@ +--- +date: '19-05-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + bugs: + - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..faacf79cb1 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-20/9.yml @@ -0,0 +1,17 @@ +--- +date: '02-06-2020' +sections: + security_fixes: + - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + bugs: + - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% 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 new file mode 100644 index 0000000000..f3552d808f --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/0.yml @@ -0,0 +1,72 @@ +--- +date: '09-06-2020' +sections: + features: + - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + security_fixes: + - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + bugs: + - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' + changes: + - 'The web notifications interface, including new [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - 'Admins can [enable security alerts](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' + - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/1.yml b/translations/pt-BR/data/release-notes/2-21/1.yml new file mode 100644 index 0000000000..f70397b28a --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/1.yml @@ -0,0 +1,20 @@ +--- +date: '23-06-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/10.yml b/translations/pt-BR/data/release-notes/2-21/10.yml new file mode 100644 index 0000000000..a8408ed42b --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/10.yml @@ -0,0 +1,15 @@ +--- +date: '20-10-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% 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 new file mode 100644 index 0000000000..88d9575ebc --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/11.yml @@ -0,0 +1,18 @@ +--- +date: '03-11-2020' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% 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 new file mode 100644 index 0000000000..d27dfc69ec --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/12.yml @@ -0,0 +1,16 @@ +--- +date: '17-11-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% 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 new file mode 100644 index 0000000000..cbfb87c249 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/13.yml @@ -0,0 +1,19 @@ +--- +date: '03-12-2020' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/2.yml b/translations/pt-BR/data/release-notes/2-21/2.yml new file mode 100644 index 0000000000..887f56c697 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/2.yml @@ -0,0 +1,20 @@ +--- +date: '09-07-2020' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/3.yml b/translations/pt-BR/data/release-notes/2-21/3.yml new file mode 100644 index 0000000000..86d4d282fb --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/3.yml @@ -0,0 +1,17 @@ +--- +date: '21-07-2020' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% 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: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/4.yml b/translations/pt-BR/data/release-notes/2-21/4.yml new file mode 100644 index 0000000000..0d262d293d --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/4.yml @@ -0,0 +1,27 @@ +--- +date: '11-08-2020' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" + - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/5.yml b/translations/pt-BR/data/release-notes/2-21/5.yml new file mode 100644 index 0000000000..89f7156e55 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/5.yml @@ -0,0 +1,15 @@ +--- +date: '12-08-2020' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/6.yml b/translations/pt-BR/data/release-notes/2-21/6.yml new file mode 100644 index 0000000000..8638d1d9cd --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/6.yml @@ -0,0 +1,26 @@ +date: '2020-08-26' +sections: + security_fixes: + - >- + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, + https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} + - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + bugs: + - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' + - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' + changes: + - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/2-21/7.yml b/translations/pt-BR/data/release-notes/2-21/7.yml new file mode 100644 index 0000000000..629d651529 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/7.yml @@ -0,0 +1,14 @@ +--- +date: '08-09-2020' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% 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 new file mode 100644 index 0000000000..d09450096e --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/8.yml @@ -0,0 +1,16 @@ +--- +date: '23-09-2020' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + bugs: + - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% 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 new file mode 100644 index 0000000000..1792704db3 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-21/9.yml @@ -0,0 +1,29 @@ +--- +date: '09-10-2020' +sections: + security_fixes: + - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% 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 new file mode 100644 index 0000000000..f25e465abd --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-22/0.yml @@ -0,0 +1,130 @@ +--- +intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. +date: '23-09-2020' +sections: + features: + - + heading: GitHub Actions Beta + notes: + - | + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + + You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + - + heading: GitHub Packages Beta + notes: + - | + [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + - + heading: Advanced Security Code Scanning Beta + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. + + Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + - + heading: Pull Request Retargeting + notes: + - | + When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + - + heading: Suspend and Unsuspend an App Installation + notes: + - | + Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + - + heading: Improved Large Scale Performance + notes: + - | + We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% 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 %}'' + + Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + - + heading: View All of Your Users + notes: + - | + For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](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: Administration Changes + notes: + - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} + - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](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 %}' + - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% 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 %} + - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% 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: Security Changes + notes: + - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](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 %} + - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - + heading: Developer Changes + notes: + - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' + - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' + - + heading: Users and organizations can add Twitter usernames to their GitHub profiles + notes: + - '[Developers and organizations can now add their Twitter username to their profile](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: API Changes + notes: + - | + #### Graduated Previews + + The following previews are now an official part of the API: + * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} + * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} + - | + #### GraphQL Schema Changes + + * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + bugs: + - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + deprecations: + - + heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020** That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + #- type: Backup and Disaster recovery + #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} + - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} + - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a 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 %}' + - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 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 new file mode 100644 index 0000000000..1bd076d4ab --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-22/1.yml @@ -0,0 +1,71 @@ +--- +date: '09-10-2020' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - | + The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - | + Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + - | + Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + - | + System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + - | + The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + - | + `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + - | + Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + - | + Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + - | + Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + - | + When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + - | + The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + - | + OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + - | + Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + - | + On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + - | + When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + - | + When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + - | + Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + - | + Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + - | + The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + - | + Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + - | + A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + - | + When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + - | + [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + - | + GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management 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: + - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} + - GitHub App Manifests now include the `request_oauth_on_install` field. {% 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: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/pt-BR/data/release-notes/2-22/2.yml b/translations/pt-BR/data/release-notes/2-22/2.yml new file mode 100644 index 0000000000..cb8c4025e8 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-22/2.yml @@ -0,0 +1,29 @@ +--- +date: '20-10-2020' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + bugs: + - | + If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + - | + A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} + - | + On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + - | + When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + - | + Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} + - | + The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + - | + On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 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 new file mode 100644 index 0000000000..58ccdc054d --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-22/3.yml @@ -0,0 +1,23 @@ +--- +date: '03-11-2020' +sections: + security_fixes: + - | + **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + - | + **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + - | + Packages have been updated to the latest security versions. {% 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: + - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% 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 new file mode 100644 index 0000000000..5323f58085 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-22/4.yml @@ -0,0 +1,16 @@ +--- +date: '17-11-2020' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + bugs: + - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% 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 new file mode 100644 index 0000000000..ad39fe92d9 --- /dev/null +++ b/translations/pt-BR/data/release-notes/2-22/5.yml @@ -0,0 +1,22 @@ +--- +date: '03-12-2020' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' + - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/pt-BR/data/reusables/accounts/create-account.md b/translations/pt-BR/data/reusables/accounts/create-account.md new file mode 100644 index 0000000000..980fc8a6db --- /dev/null +++ b/translations/pt-BR/data/reusables/accounts/create-account.md @@ -0,0 +1,2 @@ +1. Acesse a página de [Preços]({% data variables.product.pricing_url %}) do {% data variables.product.product_name %}. +2. Leia as informações sobre os diferentes produtos e assinaturas que o {% data variables.product.product_name %} oferece e clique no botão de upgrade abaixo da assinatura desejada. diff --git a/translations/pt-BR/data/reusables/actions/actions-not-verified.md b/translations/pt-BR/data/reusables/actions/actions-not-verified.md index 61c3a7cdfa..76e742631a 100644 --- a/translations/pt-BR/data/reusables/actions/actions-not-verified.md +++ b/translations/pt-BR/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Qualquer pessoa pode publicar uma ação em {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifica algumas organizações parceiras, mas, diferentemente dos aplicativos verificados, {% data variables.product.prodname_dotcom %} não revisa ou verifica ações individuais listadas em {% data variables.product.prodname_marketplace %}. +Qualquer pessoa pode publicar uma ação em {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/pt-BR/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/pt-BR/data/reusables/actions/actions-packages-set-spending-limit.md new file mode 100644 index 0000000000..c0cb547262 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/actions-packages-set-spending-limit.md @@ -0,0 +1 @@ +You can set a specific spending limit or, for some accounts, allow unlimited spending. O limite de gastos aplica-se aos seus excessos conjuntos para {% data variables.product.prodname_registry %} e {% data variables.product.prodname_actions %}. diff --git a/translations/pt-BR/data/reusables/actions/visualization-beta.md b/translations/pt-BR/data/reusables/actions/visualization-beta.md new file mode 100644 index 0000000000..ee3ad11ef4 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/visualization-beta.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** The workflow visualization graph for {% data variables.product.prodname_actions %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-api-info.md b/translations/pt-BR/data/reusables/audit_log/audit-log-api-info.md new file mode 100644 index 0000000000..55728a1692 --- /dev/null +++ b/translations/pt-BR/data/reusables/audit_log/audit-log-api-info.md @@ -0,0 +1,5 @@ +* Access to your organization or repository settings +* Changes in permissions +* Added or removed users in an organization, repository, or team +* Users being promoted to admin +* Changes to permissions of a {% data variables.product.prodname_github_app %} diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/pt-BR/data/reusables/audit_log/audit-log-git-events-retention.md new file mode 100644 index 0000000000..3f1584bf91 --- /dev/null +++ b/translations/pt-BR/data/reusables/audit_log/audit-log-git-events-retention.md @@ -0,0 +1 @@ +The audit log retains Git events for 7 days. This is shorter than other audit log events, which can be retained for 90 days. diff --git a/translations/pt-BR/data/reusables/classroom/about-assignments.md b/translations/pt-BR/data/reusables/classroom/about-assignments.md new file mode 100644 index 0000000000..65a3506229 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/about-assignments.md @@ -0,0 +1 @@ +Each assignment has a title and an optional deadline. You can choose the visibility of repositories that {% data variables.product.prodname_classroom %} creates and choose access permissions. You can also automatically grade assignments and create a dedicated space to discuss the assignment with the student. diff --git a/translations/pt-BR/data/reusables/classroom/about-autograding.md b/translations/pt-BR/data/reusables/classroom/about-autograding.md new file mode 100644 index 0000000000..04ed2b067c --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/about-autograding.md @@ -0,0 +1 @@ +You can use autograding to automatically check a student's work for an assignment on {% data variables.product.prodname_classroom %}. You configure tests for an assignment, and the tests run immediately every time a student pushes to an assignment repository on {% data variables.product.product_location %}. The student can view the test results, make changes, and push to see new results. diff --git a/translations/pt-BR/data/reusables/classroom/about-classrooms.md b/translations/pt-BR/data/reusables/classroom/about-classrooms.md new file mode 100644 index 0000000000..5d19bbb44a --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/about-classrooms.md @@ -0,0 +1 @@ +A classroom in {% data variables.product.prodname_classroom %} is where teachers and students interact during a course. Teachers can create a student roster for the classroom, then create, assign, review, and grade assignments within the classroom. diff --git a/translations/pt-BR/data/reusables/classroom/about-online-ides.md b/translations/pt-BR/data/reusables/classroom/about-online-ides.md new file mode 100644 index 0000000000..43818e691f --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/about-online-ides.md @@ -0,0 +1 @@ +You can optionally configure an assignment to use an online integrated development environment (IDE). Online IDEs allow your students to write code, run programs, and collaborate in a browser, without installing Git and a full development toolchain on the student's computer. If you choose an online IDE for an assignment, students can still check out and run code locally on a computer with the necessary software. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/pt-BR/data/reusables/classroom/assignments-classroom-prerequisite.md new file mode 100644 index 0000000000..06284dad51 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-classroom-prerequisite.md @@ -0,0 +1 @@ +You must create a classroom before you can create an assignment. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." diff --git a/translations/pt-BR/data/reusables/classroom/assignments-click-pencil.md b/translations/pt-BR/data/reusables/classroom/assignments-click-pencil.md new file mode 100644 index 0000000000..820afd5260 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-click-pencil.md @@ -0,0 +1 @@ +1. To the right of the assignment you want to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing assignment in list of assignments](/assets/images/help/classroom/assignments-click-pencil.png) diff --git a/translations/pt-BR/data/reusables/classroom/assignments-group-definition.md b/translations/pt-BR/data/reusables/classroom/assignments-group-definition.md new file mode 100644 index 0000000000..3143cddc70 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-group-definition.md @@ -0,0 +1 @@ +A group assignment is collaborative coursework for groups of students on {% data variables.product.prodname_classroom %}. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-assign-a-deadline.md new file mode 100644 index 0000000000..6e8e29cc11 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-assign-a-deadline.md @@ -0,0 +1,5 @@ +Optionally, you can assign a deadline to the assignment. Under "Deadline (optional)", click in the text field, then use the date picker to assign a deadline. + +
      + Date picker for assignment deadline +
      diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md new file mode 100644 index 0000000000..54858178a5 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -0,0 +1,5 @@ +To choose an online IDE for the assignment, select the **Select an online IDE** drop-down menu, then click the IDE you'd like your students to use. + +
      + Using the 'Select an online IDE' drop-down menu to click an online IDE for the assignment +
      diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-template-repository.md new file mode 100644 index 0000000000..15bcb66cb5 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-template-repository.md @@ -0,0 +1,5 @@ +Under "Add a template repository to give students starter code", select the **Select a repository** drop-down, then type a search query. In the list of results, click the template repository you'd like to use for starter code. + +
      + Using the 'Select a repository' drop-down menu to find a template repository to use as starter code for an assignment +
      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 new file mode 100644 index 0000000000..3f4f17e1b2 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -0,0 +1,9 @@ +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)." + +Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. + +
      + Visibility options for assignment repositories +
      diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md new file mode 100644 index 0000000000..b82d19fe8e --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-basics.md @@ -0,0 +1,7 @@ +
      + +When you're done, click **Continue** to configure starter code and a development environment for the assignment. + +
      + 'Continue' button +
      diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md new file mode 100644 index 0000000000..4607b61065 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md @@ -0,0 +1,7 @@ +
      + +When you're done, click **Continue** to configure automatic grading and feedback for the project. + +
      + 'Continue' button +
      diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md new file mode 100644 index 0000000000..935d73f5df --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-click-create-assignment-button.md @@ -0,0 +1,5 @@ +To create the assignment, click **Create assignment**. + +
      + 'Create assignment' button +
      diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-create-review-pull-request.md new file mode 100644 index 0000000000..5cc14ee9ff --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-create-review-pull-request.md @@ -0,0 +1,5 @@ +To create pull requests for the discussion of feedback, select **Enable feedback pull requests**. + +
      + Checkbox for 'Enable feedback pull requests' +
      diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-create-the-assignment.md new file mode 100644 index 0000000000..051e169c57 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -0,0 +1,5 @@ +To create an assignment, sign into {% data variables.product.prodname_classroom_with_url %} and navigate to a classroom. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click **New assignment**. + +
      + The 'New assignment' button +
      diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-intro-for-environment.md new file mode 100644 index 0000000000..bda2c39723 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-intro-for-environment.md @@ -0,0 +1 @@ +Optionally, decide whether to provide empty repositories or starter code, and preconfigure a development environment for your students. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md new file mode 100644 index 0000000000..6290d808ad --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md @@ -0,0 +1,3 @@ +{% data reusables.classroom.classroom-enables-invitation-urls %} + +{% data reusables.classroom.invitation-url-warning %} diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-prevent-changes.md new file mode 100644 index 0000000000..9ef39a18b9 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-prevent-changes.md @@ -0,0 +1,7 @@ +You can prevent students from changing files that contain tests for autograding, or other important files in the assignment repository. + +Under "Protected file paths", type relative paths within the repository to protect. + +
      + Text field for typing protected file paths +
      \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/pt-BR/data/reusables/classroom/assignments-guide-using-autograding.md new file mode 100644 index 0000000000..5f50beec64 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-guide-using-autograding.md @@ -0,0 +1,23 @@ +{% data reusables.classroom.about-autograding %} For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." + +{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} For more information, see "[Grading methods](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)." + +
      + Using the 'Add test' drop-down menu to click a grading method +
      + +
      + +Define the parameters of your test case, like the name, commands, inputs, outputs, timeout, and points. When you're done, click **Save test case**. + +
      + 'Save test case' button for an autograding test +
      + +
      + +You can add more tests with the **Add test** drop-down menu, and you can edit or delete existing tests with {% octicon "pencil" aria-label="The pencil icon" %} or {% octicon "trash" aria-label="The trash icon" %}. + +
      + Pencil and trash icons to edit or delete an autograding test +
      \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/classroom/assignments-individual-definition.md b/translations/pt-BR/data/reusables/classroom/assignments-individual-definition.md new file mode 100644 index 0000000000..33425ae2c3 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-individual-definition.md @@ -0,0 +1 @@ +An individual assignment is coursework for each student who participates in a course on {% data variables.product.prodname_classroom %}. The student is intended to complete an individual assignment without help from other students. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md new file mode 100644 index 0000000000..62bd9cc2da --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-to-prevent-submission.md @@ -0,0 +1 @@ +To prevent acceptance or submission of an assignment by students, deselect **Enable assignment invitation URL**. To edit the assignment, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment**. diff --git a/translations/pt-BR/data/reusables/classroom/assignments-type-a-title.md b/translations/pt-BR/data/reusables/classroom/assignments-type-a-title.md new file mode 100644 index 0000000000..20d32397ac --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/assignments-type-a-title.md @@ -0,0 +1,5 @@ +Type a title for the assignment. Optionally, click {% octicon "pencil" aria-label="The pencil icon" %} to edit the prefix. + +
      + Assignment title and prefix +
      diff --git a/translations/pt-BR/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/pt-BR/data/reusables/classroom/classroom-creates-group-repositories.md new file mode 100644 index 0000000000..10cdc5924a --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/classroom-creates-group-repositories.md @@ -0,0 +1 @@ +For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.product_name %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. diff --git a/translations/pt-BR/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/pt-BR/data/reusables/classroom/classroom-creates-individual-repositories.md new file mode 100644 index 0000000000..4108abf9ad --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -0,0 +1 @@ +When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.product_name %}. diff --git a/translations/pt-BR/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/pt-BR/data/reusables/classroom/classroom-enables-invitation-urls.md new file mode 100644 index 0000000000..1b357c3a2d --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/classroom-enables-invitation-urls.md @@ -0,0 +1 @@ +By default, {% data variables.product.prodname_classroom %} enables an invitation URL for each assignment you create. Students can accept and submit the assignment while the invitation URL is enabled. You can share the URL with your students on your LMS, course homepage, or wherever you post assignments. Students can also navigate to the assignment on {% data variables.product.prodname_classroom %} if the student has already accepted an assignment for the classroom. diff --git a/translations/pt-BR/data/reusables/classroom/click-assignment-in-list.md b/translations/pt-BR/data/reusables/classroom/click-assignment-in-list.md new file mode 100644 index 0000000000..347d0bc108 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/click-assignment-in-list.md @@ -0,0 +1 @@ +1. In the list of assignments, click the assignment you want to view. ![Assignment in list of assignments for an classroom](/assets/images/help/classroom/click-assignment-in-list.png) diff --git a/translations/pt-BR/data/reusables/classroom/click-classroom-in-list.md b/translations/pt-BR/data/reusables/classroom/click-classroom-in-list.md new file mode 100644 index 0000000000..fe7d091cdc --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/click-classroom-in-list.md @@ -0,0 +1 @@ +1. In the list of classrooms, click the classroom you want to view. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) diff --git a/translations/pt-BR/data/reusables/classroom/click-settings.md b/translations/pt-BR/data/reusables/classroom/click-settings.md new file mode 100644 index 0000000000..9fe6b33d6b --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/click-settings.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" tab for classroom](/assets/images/help/classroom/click-settings.png) diff --git a/translations/pt-BR/data/reusables/classroom/click-students.md b/translations/pt-BR/data/reusables/classroom/click-students.md new file mode 100644 index 0000000000..13df0b1e40 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/click-students.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**. !["Students" tab for classroom](/assets/images/help/classroom/click-students.png) diff --git a/translations/pt-BR/data/reusables/classroom/for-more-information-about-assignment-creation.md b/translations/pt-BR/data/reusables/classroom/for-more-information-about-assignment-creation.md new file mode 100644 index 0000000000..8fd113d763 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/for-more-information-about-assignment-creation.md @@ -0,0 +1 @@ +For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." 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 new file mode 100644 index 0000000000..d5ab6d0f93 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/guide-create-new-classroom.md @@ -0,0 +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. 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)". ![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/pt-BR/data/reusables/classroom/invitation-url-warning.md b/translations/pt-BR/data/reusables/classroom/invitation-url-warning.md new file mode 100644 index 0000000000..f85e808ddc --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/invitation-url-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning**: Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a user account on {% data variables.product.product_name %} with an identifier in your roster. + +{% endwarning %} diff --git a/translations/pt-BR/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/pt-BR/data/reusables/classroom/readme-contains-button-for-online-ide.md new file mode 100644 index 0000000000..fac85f79f1 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -0,0 +1 @@ +When a student accepts an assignment with an online IDE, the assignment repository will include a _README.md_ file with a special button at the top of the file. The button links the student directly to the workspace in the online IDE. diff --git a/translations/pt-BR/data/reusables/classroom/sign-into-github-classroom.md b/translations/pt-BR/data/reusables/classroom/sign-into-github-classroom.md new file mode 100644 index 0000000000..578bf7213e --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/sign-into-github-classroom.md @@ -0,0 +1 @@ +1. Sign into {% data variables.product.prodname_classroom_with_url %}. diff --git a/translations/pt-BR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/pt-BR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md new file mode 100644 index 0000000000..2486daf0a4 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md @@ -0,0 +1 @@ +Under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. diff --git a/translations/pt-BR/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/pt-BR/data/reusables/classroom/you-can-choose-a-template-repository.md new file mode 100644 index 0000000000..40eb9d273b --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -0,0 +1 @@ +You can optionally choose a template repository as starter code for the assignment. The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}. diff --git a/translations/pt-BR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/pt-BR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md new file mode 100644 index 0000000000..e9592fb832 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md @@ -0,0 +1 @@ +You can automatically create a pull request where you can provide feedback and answer a student's questions about an assignment. For more information about the review of changes in a pull request, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)." diff --git a/translations/pt-BR/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md b/translations/pt-BR/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md new file mode 100644 index 0000000000..af5be0c098 --- /dev/null +++ b/translations/pt-BR/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md @@ -0,0 +1 @@ +You may want to predefine the default settings for the assignment repositories that {% data variables.product.prodname_classroom %} creates from a template repository. For example, you may want to disable issues, define labels for pull requests, or protect a branch in some or all of the repositories. diff --git a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md new file mode 100644 index 0000000000..dc1266d067 --- /dev/null +++ b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md @@ -0,0 +1,3 @@ +When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)". + +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file 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 b8babbe472..16df667726 100644 --- a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md @@ -1,20 +1,23 @@ -| Gerenciador de pacotes | Suporta vendoring | -| -------------------------------- |:-----------------:| -| Bundler: `bundler` | **X** | -| Cargo: `cargo` | | -| Composer: `composer` | | -| Docker: `docker` | | -| Elm: `elm` | | -| git submodule: `gitsubmodule` | | -| GitHub Actions: `github-actions` | | -| Go modules: `gomod` | **X** | -| Gradle: `gradle` | | -| Maven: `maven` | | -| Mix: `mix` | | -| npm: `npm` | | -| NuGet: `nuget` | | -| pip: `pip` | | -| Terraform: `terraform` | | +The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. + +| Gerenciador de pacotes | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | +| -------------------------------- |:-----------------------------------------------------------------:|:---------:| +| Bundler: `bundler` | | **✓** | +| Cargo: `cargo` | **✓** | | +| Composer: `composer` | **✓** | | +| Docker: `docker` | **✓** | | +| Elixir: `hex` | | | +| Elm: `elm` | **✓** | | +| git submodule: `gitsubmodule` | **✓** | | +| GitHub Actions: `github-actions` | **✓** | | +| Go modules: `gomod` | **✓** | **✓** | +| Gradle: `gradle` | **✓** | | +| Maven: `maven` | **✓** | | +| Mix: `mix` | **✓** | | +| npm: `npm` | **✓** | | +| NuGet: `nuget` | **✓** | | +| pip: `pip` | | | +| Terraform: `terraform` | **✓** | | {% note %} diff --git a/translations/pt-BR/data/reusables/discussions/about-categories-and-formats.md b/translations/pt-BR/data/reusables/discussions/about-categories-and-formats.md new file mode 100644 index 0000000000..a17ca2ca53 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/about-categories-and-formats.md @@ -0,0 +1 @@ +All discussions must be created in a category, and repository administrators and maintainers define the categories for a repository. Categories can contain open-ended conversations, or conversations with a question/answer format. diff --git a/translations/pt-BR/data/reusables/discussions/about-discussions.md b/translations/pt-BR/data/reusables/discussions/about-discussions.md new file mode 100644 index 0000000000..c61b8b0f0a --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/about-discussions.md @@ -0,0 +1 @@ +Discussions are an open forum for conversation among maintainers and the community for a project on {% data variables.product.product_name %}. diff --git a/translations/pt-BR/data/reusables/discussions/beta.md b/translations/pt-BR/data/reusables/discussions/beta.md new file mode 100644 index 0000000000..b46e034834 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Nota:** {% data variables.product.prodname_discussions %} está atualmente em versão beta e sujeito a alterações. + +{% endnote %} diff --git a/translations/pt-BR/data/reusables/discussions/click-discussion-in-list.md b/translations/pt-BR/data/reusables/discussions/click-discussion-in-list.md new file mode 100644 index 0000000000..8156c86331 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/click-discussion-in-list.md @@ -0,0 +1 @@ +1. In the list of discussions, click the discussion you want to view. ![Discussion in list of discussions for a repository](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/pt-BR/data/reusables/discussions/discussions-tab.md b/translations/pt-BR/data/reusables/discussions/discussions-tab.md new file mode 100644 index 0000000000..67795aa5ae --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/discussions-tab.md @@ -0,0 +1 @@ +1. Under your repository name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. !["Discussions" tab for a repository](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/translations/pt-BR/data/reusables/discussions/edit-categories.md b/translations/pt-BR/data/reusables/discussions/edit-categories.md new file mode 100644 index 0000000000..6f4f6af574 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/edit-categories.md @@ -0,0 +1 @@ +1. To the right of "Categories", click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing categories](/assets/images/help/discussions/click-edit-categories.png) diff --git a/translations/pt-BR/data/reusables/discussions/edit-category-details.md b/translations/pt-BR/data/reusables/discussions/edit-category-details.md new file mode 100644 index 0000000000..8004b70314 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/edit-category-details.md @@ -0,0 +1 @@ +Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." diff --git a/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md new file mode 100644 index 0000000000..88327eecec --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -0,0 +1,5 @@ +You can enable or disable discussions for a repository. + +{% data reusables.repositories.navigate-to-repo %} +1. No nome do seu repositório, clique em {% octicon "gear" aria-label="The gear icon" %} **Configurações**. ![Botão de configurações do repositório](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", select **Discussions**. ![Checkbox under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/pt-BR/data/reusables/discussions/github-recognizes-members.md b/translations/pt-BR/data/reusables/discussions/github-recognizes-members.md new file mode 100644 index 0000000000..b6874b910d --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/github-recognizes-members.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. diff --git a/translations/pt-BR/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/pt-BR/data/reusables/discussions/marking-a-comment-as-an-answer.md new file mode 100644 index 0000000000..bdefffdea0 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -0,0 +1,14 @@ +You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +When you mark a question as an answer, {% data variables.product.product_name %} will highlight the comment and replies to the comment to help visitors quickly find the answer. + +![Comment marked as answer to a discussion](/assets/images/help/discussions/comment-marked-as-answer.png) + +You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the unanswered discussion you want to mark as answered. ![Unanswered discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the discussion, find the comment you want to mark as the answer. +1. In the upper-right corner of the comment, click {% octicon "check-circle" aria-label="The circular check icon" %}. !["Mark as answer" circular check icon for marking comment as answer in a discussion](/assets/images/help/discussions/comment-mark-as-answer-button.png) +1. Optionally, to unmark a comment as the answer, click {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. diff --git a/translations/pt-BR/data/reusables/discussions/repository-category-limit.md b/translations/pt-BR/data/reusables/discussions/repository-category-limit.md new file mode 100644 index 0000000000..293d3632b5 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/repository-category-limit.md @@ -0,0 +1 @@ +Each repository can have up to 10 categories. diff --git a/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md b/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md new file mode 100644 index 0000000000..242e3abf9b --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md @@ -0,0 +1,6 @@ +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Click **New discussion**. !["New discussion" button within the "Discussions" tab for a repository](/assets/images/help/discussions/new-discussion-button.png) +1. Select the **Select Category** drop-down menu, and click a category for your discussion. !["Select Category" drop-down menu and list of available categories in a repository](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) +1. Type a title and body for your discussion. ![Text fields for new discussion's title and body](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) diff --git a/translations/pt-BR/data/reusables/discussions/you-can-categorize-discussions.md b/translations/pt-BR/data/reusables/discussions/you-can-categorize-discussions.md new file mode 100644 index 0000000000..bb05316d77 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/you-can-categorize-discussions.md @@ -0,0 +1 @@ +You can categorize discussions to help community members begin conversations in the right place, and to help community members find related discussions. diff --git a/translations/pt-BR/data/reusables/discussions/you-can-convert-an-issue.md b/translations/pt-BR/data/reusables/discussions/you-can-convert-an-issue.md new file mode 100644 index 0000000000..1421256e1f --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/you-can-convert-an-issue.md @@ -0,0 +1 @@ +If an issue turns out to be a question or open-ended conversation instead of a work item to track and prioritize, you can convert the issue to a discussion. diff --git a/translations/pt-BR/data/reusables/discussions/you-can-use-discussions.md b/translations/pt-BR/data/reusables/discussions/you-can-use-discussions.md new file mode 100644 index 0000000000..27c1ba7cb2 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/you-can-use-discussions.md @@ -0,0 +1 @@ +You can use discussions to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/discussions/you-cannot-convert-a-discussion.md b/translations/pt-BR/data/reusables/discussions/you-cannot-convert-a-discussion.md new file mode 100644 index 0000000000..9e9b687b67 --- /dev/null +++ b/translations/pt-BR/data/reusables/discussions/you-cannot-convert-a-discussion.md @@ -0,0 +1 @@ +You cannot convert a discussion to an issue. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/pt-BR/data/reusables/dotcom_billing/actions-packages-unpaid-account.md index 6321a17d56..ce5874d3af 100644 --- a/translations/pt-BR/data/reusables/dotcom_billing/actions-packages-unpaid-account.md +++ b/translations/pt-BR/data/reusables/dotcom_billing/actions-packages-unpaid-account.md @@ -2,4 +2,4 @@ Se a sua conta tiver cobranças por pagar pendentes: * O armazenamento ou minutos incluídos na sua conta para {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %} não serão redefinidos até que o pagamento seja processado com sucesso. * Para contas com armazenamento ou minutos restantes para o período de faturamento atual, {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %} continuarão disponíveis até que qualquer uso incluído tenha sido alcançado. -* Para contas que atingiram o uso incluído para o período de faturamento atual para {% data variables.product.prodname_actions %} ou {% data variables.product.prodname_registry %}, ambos {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %} serão desativadas para evitar maiores excessos. Se você pagar sua conta por fatura, deverá [contact our account management team](https://enterprise.github.com/contact) para processar o pagamento e redefinir seu uso. +* Para contas que atingiram o uso incluído para o período de faturamento atual para {% data variables.product.prodname_actions %} ou {% data variables.product.prodname_registry %}, ambos {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %} serão desativadas para evitar maiores excessos. 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 57cbdb5350..ee42ff7b3e 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 %}](https://education.github.com/partners/schools)". +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/teach-and-learn-with-github-education/about-github-education)". diff --git a/translations/pt-BR/data/reusables/education/apply-for-team.md b/translations/pt-BR/data/reusables/education/apply-for-team.md index 58a46e9584..fcec4b895c 100644 --- a/translations/pt-BR/data/reusables/education/apply-for-team.md +++ b/translations/pt-BR/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Solicite o [{% data variables.product.prodname_team %}](/articles/github-s-products) grátis, que permite usuários e repositórios privados ilimitados. Para obter mais informações, consulte "[Solicitar um desconto para educador ou pesquisador](/articles/applying-for-an-educator-or-researcher-discount)". +- Solicite o [{% data variables.product.prodname_team %}](/articles/github-s-products) grátis, que permite usuários e repositórios privados ilimitados. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." diff --git a/translations/pt-BR/data/reusables/education/click-get-teacher-benefits.md b/translations/pt-BR/data/reusables/education/click-get-teacher-benefits.md new file mode 100644 index 0000000000..25bbacd747 --- /dev/null +++ b/translations/pt-BR/data/reusables/education/click-get-teacher-benefits.md @@ -0,0 +1 @@ +1. Under "Individuals", click **Get teacher benefits**. !["Get teacher benefits" on {% data variables.product.prodname_education %} homepage](/assets/images/help/education/click-get-teacher-benefits.png) diff --git a/translations/pt-BR/data/reusables/education/educator-requirements.md b/translations/pt-BR/data/reusables/education/educator-requirements.md new file mode 100644 index 0000000000..5738b11a67 --- /dev/null +++ b/translations/pt-BR/data/reusables/education/educator-requirements.md @@ -0,0 +1,6 @@ +To apply for an educator or researcher discount, you must meet the following requirements. + +- Ser um educador, integrante do corpo docente ou pesquisador. +- Tenha um endereço de e-mail verificável emitido pela escola. +- Faça upload dos documentos que comprovam a sua afiliação à escola. +- Have a user account on {% data variables.product.product_name %}. diff --git a/translations/pt-BR/data/reusables/gated-features/discussions.md b/translations/pt-BR/data/reusables/gated-features/discussions.md new file mode 100644 index 0000000000..5ada0a25ee --- /dev/null +++ b/translations/pt-BR/data/reusables/gated-features/discussions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_discussions %} is available in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/pt-BR/data/reusables/github-actions/actions-billing.md b/translations/pt-BR/data/reusables/github-actions/actions-billing.md index f5ef5b45d9..e822bf0930 100644 --- a/translations/pt-BR/data/reusables/github-actions/actions-billing.md +++ b/translations/pt-BR/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -O uso de {% data variables.product.prodname_actions %} é grátis para repositórios públicos e executores auto-hospedados. Para repositórios privados, cada conta {% data variables.product.prodname_dotcom %} recebe uma certa quantidade de minutos e armazenamento gratuitos, dependendo do produto usado com a conta. +O uso de {% data variables.product.prodname_actions %} é grátis para repositórios públicos e executores auto-hospedados. Para repositórios privados, cada conta {% data variables.product.prodname_dotcom %} recebe uma certa quantidade de minutos e armazenamento gratuitos, dependendo do produto usado com a conta. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md b/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md index 71107ce120..a8b1b279dd 100644 --- a/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md +++ b/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -##### **Exemplo com um único evento** +##### Exemplo com um único evento ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -##### **Exemplo com uma lista de eventos** +##### Exemplo com uma lista de eventos ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -##### **Exemplo usando vários eventos com tipos de atividade ou configuração** +##### Exemplo usando vários eventos com tipos de atividade ou configuração Se você precisar especificar tipos de atividade ou configuração para um evento, você deve configurar cada evento separadamente. Você deve anexar dois pontos (`:`) a todos os eventos, incluindo eventos sem configuração. diff --git a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-brief.md new file mode 100644 index 0000000000..20d912fb21 --- /dev/null +++ b/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md new file mode 100644 index 0000000000..0ce0975905 --- /dev/null +++ b/translations/pt-BR/data/reusables/github-actions/actions-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.github-actions.actions-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where a workflow is run. Quaisquer cupons em sua conta não se aplicam a {% data variables.product.prodname_actions %} excessos. diff --git a/translations/pt-BR/data/reusables/github-actions/contacting-support.md b/translations/pt-BR/data/reusables/github-actions/contacting-support.md index 23e9b1c8dc..bb90d99862 100644 --- a/translations/pt-BR/data/reusables/github-actions/contacting-support.md +++ b/translations/pt-BR/data/reusables/github-actions/contacting-support.md @@ -1,4 +1,4 @@ -Se precisar de ajuda com algo relacionado com a configuração do fluxo de trabalho, como sintaxe, executores hospedados no {% data variables.product.prodname_dotcom %}, ou ações de criação, procure por um tópico existente ou comece um novo na placa de [{% data variables.product.prodname_gcf %} {% data variables.product.prodname_actions %} ](https://github.community/c/github-actions). +If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). Se você tiver comentários ou solicitações de recursos para {% data variables.product.prodname_actions %}, compartilhe-os na {% data variables.contact.contact_feedback_actions %}. diff --git a/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md b/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md index 4d2509b3ea..e6db4f8803 100644 --- a/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/pt-BR/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Nota:** O ambiente virtual do MacOS 11.0 é atualmente fornecido apenas como visualização. A etiqueta do fluxo de trabalho do YAML `macos-latest` ainda usa o ambiente virtual do MacOS 10.15. +**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/pt-BR/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/pt-BR/data/reusables/github-actions/publish-to-maven-workflow-step.md index 366671e3e6..1b507c1673 100644 --- a/translations/pt-BR/data/reusables/github-actions/publish-to-maven-workflow-step.md +++ b/translations/pt-BR/data/reusables/github-actions/publish-to-maven-workflow-step.md @@ -1 +1 @@ -Executa o comando `mvn -B deploy` para publicar no repositório `ossrh`. A variável de ambiente `MAVEN_USERNAME` será definida com o conteúdo do seu segredo `OSSRH_USERNAME`, e a variável de ambiente `MAVEN_PASSWORD` será definida com o conteúdo do seu segredo `OSSRH_TOKEN`. +Runs the `mvn --batch-mode deploy` command to publish to the `ossrh` repository. A variável de ambiente `MAVEN_USERNAME` será definida com o conteúdo do seu segredo `OSSRH_USERNAME`, e a variável de ambiente `MAVEN_PASSWORD` será definida com o conteúdo do seu segredo `OSSRH_TOKEN`. diff --git a/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md index a70dc24215..9cf11e40f3 100644 --- a/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ b/translations/pt-BR/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -Executa o comando `mvn -B deploy` para publicar no {% data variables.product.prodname_registry %}. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`. +Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. A variável de ambiente `GITHUB_TOKEN` será definida com o conteúdo do segredo `GITHUB_TOKEN`. diff --git a/translations/pt-BR/data/reusables/github-insights/download-latest-release.md b/translations/pt-BR/data/reusables/github-insights/download-latest-release.md index 711f09f9f3..1f2f02fba1 100644 --- a/translations/pt-BR/data/reusables/github-insights/download-latest-release.md +++ b/translations/pt-BR/data/reusables/github-insights/download-latest-release.md @@ -1,3 +1,3 @@ -1. Do servidor do aplicativo, navegue até a versão mais recente do {% data variables.product.prodname_insights %} na [Releases page](https://github.com/github/insights-releases/releases/latest) para `github/insights-releases`. +1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the Releases page for `github/insights-releases`. 2. Para baixar a última versão, em "Assets", clique em `insights-VERSION.tar.gz`. ![Configuração da instalação](/assets/images/help/insights/installation-tgz.png) 3. Descompacte o diretório. diff --git a/translations/pt-BR/data/reusables/marketplace/app-transfer-to-org-for-verification.md b/translations/pt-BR/data/reusables/marketplace/app-transfer-to-org-for-verification.md new file mode 100644 index 0000000000..0621a9e6e9 --- /dev/null +++ b/translations/pt-BR/data/reusables/marketplace/app-transfer-to-org-for-verification.md @@ -0,0 +1 @@ +If you want to sell an app that's owned by your user account, first you'll need to transfer the app to an organization, and then request verification for a listing created by the organization. diff --git a/translations/pt-BR/data/reusables/marketplace/free-plan-note.md b/translations/pt-BR/data/reusables/marketplace/free-plan-note.md new file mode 100644 index 0000000000..8fbdd6ab11 --- /dev/null +++ b/translations/pt-BR/data/reusables/marketplace/free-plan-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Observação:** Se você estiver listando um aplicativo em {% data variables.product.prodname_marketplace %}, você não poderá listar seu aplicativo com um plano de preços grátis, caso você ofereça um serviço pago fora do {% data variables.product.prodname_marketplace %}. + +{% endnote %} diff --git a/translations/pt-BR/data/reusables/marketplace/launch-with-free.md b/translations/pt-BR/data/reusables/marketplace/launch-with-free.md index 152515a4c3..2151c241cc 100644 --- a/translations/pt-BR/data/reusables/marketplace/launch-with-free.md +++ b/translations/pt-BR/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -Você pode enviar um aplicativo não verificado e verificado. Isso permitirá que você inicie com uma versão gratuita do seu aplicativo. Assim que o GitHub verificar o seu aplicativo, seu anúncio mudará de não verificado para verificado em {% data variables.product.prodname_marketplace %} e o GitHub publicará os seus novos planos de preços. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/pt-BR/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/pt-BR/data/reusables/marketplace/marketplace-billing-ui-requirements.md index 9b5af2a281..5b688a9c6c 100644 --- a/translations/pt-BR/data/reusables/marketplace/marketplace-billing-ui-requirements.md +++ b/translations/pt-BR/data/reusables/marketplace/marketplace-billing-ui-requirements.md @@ -1,7 +1,7 @@ -- Os clientes que cancelarem um plano pago comprado em {% data variables.product.prodname_marketplace %} devem ser automaticamente rebaixados para o plano gratuito do aplicativo, se ele existir. {% data reusables.marketplace.cancellation-clarification %} é altamente recomendável permitir que os clientes reativem seu plano anterior. -- Os clientes devem ser capazes de atualizar a partir da interface de usuário do seu aplicativo, se você fornecer um [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) neste formato: `https://www.github.com/marketplace//upgrade//` -- Os clientes devem ser capazes de modificar quais usuários têm acesso ao seu aplicativo a partir do site do seu aplicativo, caso tenham comprado assentos (por plano de preços unitários) ou que o plano ofereça colaboradores ilimitados. -- Os clientes devem poder ver as seguintes alterações em sua conta imediatamente na faturação, perfil ou seção de configurações de conta do site: +- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} should be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} é altamente recomendável permitir que os clientes reativem seu plano anterior. +- Customers should be able to upgrade from your app's user interface if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` +- Customers should be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. +- Customers should be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: - Plano e preço atuais. - Novos planos comprados. - Upgrades, downgrades, cancelamentos e o número de dias restantes em uma avaliação gratuita. diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md b/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md index c4f23eaebf..9b3a16efa4 100644 --- a/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md +++ b/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md @@ -3,7 +3,7 @@ Você precisa de um token de acesso para publicar, instalar e excluir pacotes no {% if currentVersion == "free-pro-team@latest" %} Para efetuar a autenticação usando um fluxo de trabalho do {% data variables.product.prodname_actions %}: -- Para registros de pacotes (`PACKAGE-REGISTRY.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`), você pode usar um `GITHUB_TOKEN`. +- Para registros de pacotes (`PACKAGE-REGISTRY.pkg.github.com`), você pode usar um `GITHUB_TOKEN`. - Para o registro do contêiner (`ghcr.io/OWNER/IMAGE-NAME`), você deve usar um token de acesso pessoal. {% else %} Para efetuar a autenticação em diff --git a/translations/pt-BR/data/reusables/package_registry/billing-for-container-registry.md b/translations/pt-BR/data/reusables/package_registry/billing-for-container-registry.md index d24584e0b0..75b9772ced 100644 --- a/translations/pt-BR/data/reusables/package_registry/billing-for-container-registry.md +++ b/translations/pt-BR/data/reusables/package_registry/billing-for-container-registry.md @@ -1,3 +1,3 @@ -Durante o beta de {% data variables.product.prodname_github_container_registry %}, tanto o novo {% data variables.product.prodname_container_registry %} quanto o registro do Docker de {% data variables.product.prodname_registry %} existente será grátis. Para obter mais informações sobre o registro Docker do {% data variables.product.prodname_registry %}, consulte "[Configurar o Docker para uso com {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)". +Durante o beta de {% data variables.product.prodname_github_container_registry %}, tanto o novo {% data variables.product.prodname_container_registry %} quanto o registro do Docker de {% data variables.product.prodname_registry %} existente será grátis. Para obter mais informações sobre o registro Docker do {% data variables.product.prodname_registry %}, consulte "[Configurar o Docker para uso com {% data variables.product.prodname_registry %}](/packages/guides/configuring-docker-for-use-with-github-packages)". Após o beta, as mesmas taxas de cobrança e armazenamento que os outros registros do {% data variables.product.prodname_registry %} usam serão aplicadas ao registro do contêiner. Para obter mais informações, consulte "[Sobre a cobrança para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". diff --git a/translations/pt-BR/data/reusables/package_registry/container-registry-beta-billing-note.md b/translations/pt-BR/data/reusables/package_registry/container-registry-beta-billing-note.md index 0bce7d1d39..a6b9a73c3b 100644 --- a/translations/pt-BR/data/reusables/package_registry/container-registry-beta-billing-note.md +++ b/translations/pt-BR/data/reusables/package_registry/container-registry-beta-billing-note.md @@ -1,5 +1,5 @@ {% note %} -**Atualização de cobrança para armazenamento de imagem contêiner:** Durante a fase beta de {% data variables.product.prodname_github_container_registry %}, o armazenamento de imagem do Docker e a largura de banda são grátis para os serviços de hospedagem antigo `docker. kg.github.com` e novo `ghcr.io`. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." +**Atualização de cobrança para armazenamento de imagem contêiner:** Durante a fase beta de {% data variables.product.prodname_github_container_registry %}, o armazenamento de imagem do Docker e a largura de banda são grátis para os serviços de hospedagem antigo `docker. kg.github.com` e novo `ghcr.io`. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." {% endnote %} diff --git a/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md b/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md index 18458e7c76..5e789b1e8f 100644 --- a/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md +++ b/translations/pt-BR/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Durante o beta, o armazenamento e a banda larga são grátis. Para usar {% data variables.product.prodname_github_container_registry %}, você precisa habilitar a pré-visualização de recursos. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" e "[Habilitar melhor suporte ao contêiner](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". +**Nota:** {% data variables.product.prodname_github_container_registry %} está atualmente em versão beta público e sujeito a alterações. Durante o beta, o armazenamento e a banda larga são grátis. Para usar {% data variables.product.prodname_github_container_registry %}, você precisa habilitar a pré-visualização de recursos. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" e "[Habilitar melhor suporte ao contêiner](/packages/guides/enabling-improved-container-support)". {% endnote %} diff --git a/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md index f513fc27c6..a23fdc598b 100644 --- a/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md +++ b/translations/pt-BR/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -1,5 +1,5 @@ {% warning %} -**Observação:** O registro do Docker de {% data variables.product.prodname_registry %} será substituído por {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} em uma versão futura de {% data variables.product.product_name %} {% endif %}.{% if currentVersion == "free-pro-team@latest" %} Para aprender como migrar suas imagens Docker existentes e quaisquer fluxos de trabalho usando-as, consulte "[Migrar para {% data variables.product.prodname_github_container_registry %} para imagens do Docker](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" e "[Começar com {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry).{% endif %} +**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 %} {% endwarning %} diff --git a/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md index 76a2a8bc43..bed975aa5e 100644 --- a/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md +++ b/translations/pt-BR/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -1,5 +1,5 @@ {% note %} -**Observação:** Antes de poder usar {% data variables.product.prodname_github_container_registry %}, você deve habilitar o recurso para sua conta. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)". +**Observação:** Antes de poder usar {% data variables.product.prodname_github_container_registry %}, você deve habilitar o recurso para sua conta. Para obter mais informações, consulte "[Habilitar suporte ao contêiner aprimorado](/packages/guides/enabling-improved-container-support)". {% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/package_registry/packages-billing.md b/translations/pt-BR/data/reusables/package_registry/packages-billing.md index 7b62256a39..76d249ec9c 100644 --- a/translations/pt-BR/data/reusables/package_registry/packages-billing.md +++ b/translations/pt-BR/data/reusables/package_registry/packages-billing.md @@ -1 +1 @@ -O uso de {% data variables.product.prodname_registry %} é gratuito para pacotes públicos. Para pacotes privados, cada conta {% data variables.product.product_name %} recebe uma certa quantidade de armazenamento gratuito e transferência de dados, dependendo do produto usado com a conta. Por padrão, a sua conta terá um limite de gastos de $0, que impede o uso adicional de armazenamento ou transferência de dados após atingir o valor incluído. Se você aumentar seu limite de gastos acima do padrão de $0, você será cobrado por qualquer armazenamento adicional ou transferência de dados, também chamado de excedentes, até seu limite de gastos. Quaisquer cupons em sua conta não se aplicam a excedentes de {% data variables.product.prodname_registry %}. +O uso de {% data variables.product.prodname_registry %} é gratuito para pacotes públicos. Para pacotes privados, cada conta {% data variables.product.product_name %} recebe uma certa quantidade de armazenamento gratuito e transferência de dados, dependendo do produto usado com a conta. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/pt-BR/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/pt-BR/data/reusables/package_registry/packages-spending-limit-brief.md new file mode 100644 index 0000000000..ea07621d29 --- /dev/null +++ b/translations/pt-BR/data/reusables/package_registry/packages-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/pt-BR/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/pt-BR/data/reusables/package_registry/packages-spending-limit-detailed.md new file mode 100644 index 0000000000..c1cce5b2c9 --- /dev/null +++ b/translations/pt-BR/data/reusables/package_registry/packages-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.package_registry.packages-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. Quaisquer cupons em sua conta não se aplicam a excedentes de {% data variables.product.prodname_registry %}. diff --git a/translations/pt-BR/data/reusables/package_registry/required-scopes.md b/translations/pt-BR/data/reusables/package_registry/required-scopes.md index ee398bcc9a..f9a858bbcc 100644 --- a/translations/pt-BR/data/reusables/package_registry/required-scopes.md +++ b/translations/pt-BR/data/reusables/package_registry/required-scopes.md @@ -1 +1 @@ -Você deve usar um token de acesso pessoal com os escopos apropriados para publicar e instalar pacotes no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +Você deve usar um token de acesso pessoal com os escopos apropriados para publicar e instalar pacotes no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)." diff --git a/translations/pt-BR/data/reusables/package_registry/viewing-packages.md b/translations/pt-BR/data/reusables/package_registry/viewing-packages.md index 13cfc8851a..1c46cfcf8b 100644 --- a/translations/pt-BR/data/reusables/package_registry/viewing-packages.md +++ b/translations/pt-BR/data/reusables/package_registry/viewing-packages.md @@ -1 +1 @@ -Após publicar um pacote, você poderá visualizá-lo no {% data variables.product.prodname_dotcom %}. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)." +Após publicar um pacote, você poderá visualizá-lo no {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)." diff --git a/translations/pt-BR/data/reusables/repositories/dependency-review.md b/translations/pt-BR/data/reusables/repositories/dependency-review.md new file mode 100644 index 0000000000..e780074c3c --- /dev/null +++ b/translations/pt-BR/data/reusables/repositories/dependency-review.md @@ -0,0 +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)." +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/navigate-to-job-superlinter.md b/translations/pt-BR/data/reusables/repositories/navigate-to-job-superlinter.md index f550a69227..9e9529aacf 100644 --- a/translations/pt-BR/data/reusables/repositories/navigate-to-job-superlinter.md +++ b/translations/pt-BR/data/reusables/repositories/navigate-to-job-superlinter.md @@ -1,5 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Em **Trabalhos** ou no gráfico de visualização, clique no trabalho que você deseja ver. ![Lint do trabalho do código-base](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. Na barra lateral esquerda, clique no trabalho que você deseja ver. ![Lint do trabalho do código-base](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% else %} 1. Na barra lateral esquerda, clique no trabalho que você deseja ver. ![Selecione um trabalho do fluxo de trabalho](/assets/images/help/repository/workflow-job.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/pt-BR/data/reusables/repositories/two-dot-diff-comparison-example-urls.md index 4f8cd11efa..1a25944892 100644 --- a/translations/pt-BR/data/reusables/repositories/two-dot-diff-comparison-example-urls.md +++ b/translations/pt-BR/data/reusables/repositories/two-dot-diff-comparison-example-urls.md @@ -1 +1 @@ -Por exemplo, esta URL usa os códigos SHA de sete caracteres encurtados para comparar commits `c3a414e` e `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f.` +For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`. diff --git a/translations/pt-BR/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/pt-BR/data/reusables/repositories/view-failed-job-results-superlinter.md index 6b8c983bf8..3b0025fafb 100644 --- a/translations/pt-BR/data/reusables/repositories/view-failed-job-results-superlinter.md +++ b/translations/pt-BR/data/reusables/repositories/view-failed-job-results-superlinter.md @@ -1,5 +1,8 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Todas as etapas com falha são automaticamente expandidas para exibir os resultados. ![Resultados do fluxo de trabalho do Super linter](/assets/images/help/repository/super-linter-workflow-results-updated.png) +1. Todas as etapas com falha são automaticamente expandidas para exibir os resultados. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Resultados do fluxo de trabalho do Super linter](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %} +![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png){% endif %} {% else %} 1. Expanda a etapa **Executar Super-Linter** para visualizar os resultados. ![Resultados do fluxo de trabalho do Super linter](/assets/images/help/repository/super-linter-workflow-results.png) {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/view-specific-line-superlinter.md b/translations/pt-BR/data/reusables/repositories/view-specific-line-superlinter.md index 5293027a7b..563940861f 100644 --- a/translations/pt-BR/data/reusables/repositories/view-specific-line-superlinter.md +++ b/translations/pt-BR/data/reusables/repositories/view-specific-line-superlinter.md @@ -1,5 +1,10 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Para obter um link para uma linha específica nos logs, clique no número da linha da etapa. Em seguida, você pode copiar o link da barra de endereço do seu navegador da web. ![Botão para copiar link](/assets/images/help/repository/copy-link-button-updated.png) +1. Para obter um link para uma linha específica nos logs, clique no número da linha da etapa. Em seguida, você pode copiar o link da barra de endereço do seu navegador da web. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Botão para copiar link](/assets/images/help/repository/copy-link-button-updated-2.png) + {% else %} + ![Botão para copiar link](/assets/images/help/repository/copy-link-button-updated.png) + {% endif %} {% else %} 1. Para obter um link para uma linha específica nos logs, clique no número da linha da etapa. Em seguida, você pode copiar o link da barra de endereço do seu navegador da web. ![Botão para copiar link](/assets/images/help/repository/copy-link-button.png) {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/search/date_gt_lt.md b/translations/pt-BR/data/reusables/search/date_gt_lt.md index 43292355c9..57a206f28c 100644 --- a/translations/pt-BR/data/reusables/search/date_gt_lt.md +++ b/translations/pt-BR/data/reusables/search/date_gt_lt.md @@ -1 +1 @@ -Datas são compatíveis com os [qualificadores maior que, menor que e de intervalo](/articles/understanding-the-search-syntax). +When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." diff --git a/translations/pt-BR/data/reusables/secret-scanning/api-beta.md b/translations/pt-BR/data/reusables/secret-scanning/api-beta.md new file mode 100644 index 0000000000..510473ea8d --- /dev/null +++ b/translations/pt-BR/data/reusables/secret-scanning/api-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The {% data variables.product.prodname_secret_scanning %} API is currently in beta and subject to change. + +{% endnote %} diff --git a/translations/pt-BR/data/reusables/sponsors/billing-switcher.md b/translations/pt-BR/data/reusables/sponsors/billing-switcher.md new file mode 100644 index 0000000000..4831c34a3b --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/billing-switcher.md @@ -0,0 +1 @@ +1. Optionally, to manage your sponsorship on behalf of an organization, in the upper-left corner, use the **Personal settings** drop-down menu, and click the organization. ![Drop-down menu to switch accounts for settings](/assets/images/help/sponsors/billing-account-switcher.png) diff --git a/translations/pt-BR/data/reusables/sponsors/change-tier.md b/translations/pt-BR/data/reusables/sponsors/change-tier.md index 5902c35ca3..48d6dbe339 100644 --- a/translations/pt-BR/data/reusables/sponsors/change-tier.md +++ b/translations/pt-BR/data/reusables/sponsors/change-tier.md @@ -1 +1 @@ -1. Em "{% data variables.product.prodname_sponsors %}", à direita do colaborador de código aberto patrocinado, clique em {% octicon "triangle-down" aria-label="The down triangle octicon" %} ao lado do valor patrocinado e, em seguida, clique em **Alterar a camada**. ![Botão de alterar camada](/assets/images/help/billing/edit-sponsor-billing.png) +1. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored account, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your tier amount, then click **Change tier**. ![Botão de alterar camada](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/pt-BR/data/reusables/sponsors/choose-updates.md b/translations/pt-BR/data/reusables/sponsors/choose-updates.md new file mode 100644 index 0000000000..ade59cf05b --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/choose-updates.md @@ -0,0 +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) diff --git a/translations/pt-BR/data/reusables/sponsors/manage-sponsorship.md b/translations/pt-BR/data/reusables/sponsors/manage-sponsorship.md new file mode 100644 index 0000000000..7134ce4f18 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/manage-sponsorship.md @@ -0,0 +1 @@ +1. To the right of your current tier, click **Manage**. ![Botão de gerenciar o seu patrocínio](/assets/images/help/sponsors/manage-your-sponsorship-button.png) \ No newline at end of file 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 new file mode 100644 index 0000000000..0cd08d5382 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/manage-updates-for-orgs.md @@ -0,0 +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)." diff --git a/translations/pt-BR/data/reusables/sponsors/maximum-tier.md b/translations/pt-BR/data/reusables/sponsors/maximum-tier.md index 4b151d90ea..803658fba4 100644 --- a/translations/pt-BR/data/reusables/sponsors/maximum-tier.md +++ b/translations/pt-BR/data/reusables/sponsors/maximum-tier.md @@ -1 +1 @@ -O preço máximo é US$ 6.000 por mês. +The maximum price is US$12,000 per month. diff --git a/translations/pt-BR/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/pt-BR/data/reusables/sponsors/navigate-to-sponsored-account.md new file mode 100644 index 0000000000..def70f43f1 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/navigate-to-sponsored-account.md @@ -0,0 +1 @@ +1. On {% data variables.product.product_name %}, navigate to the sponsored account's profile. diff --git a/translations/pt-BR/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/pt-BR/data/reusables/sponsors/navigate-to-sponsors-dashboard.md new file mode 100644 index 0000000000..c479d32612 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/navigate-to-sponsors-dashboard.md @@ -0,0 +1,2 @@ +1. No canto superior direito de qualquer página, clique na sua foto do perfil e depois em **{% data variables.product.prodname_sponsors %}**. ![Botão {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) +2. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**. ![Botão do painel de patrocinadores de desenvolvedor](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) diff --git a/translations/pt-BR/data/reusables/sponsors/no-fees.md b/translations/pt-BR/data/reusables/sponsors/no-fees.md index 1bbcc16c97..3857ae3185 100644 --- a/translations/pt-BR/data/reusables/sponsors/no-fees.md +++ b/translations/pt-BR/data/reusables/sponsors/no-fees.md @@ -1 +1 @@ -{% data variables.product.prodname_sponsors %} não cobra taxas por patrocínios de contas de usuários. Portanto, 100% desse patrocínio vai para o desenvolvedor ou organização patrocinada. +{% data variables.product.prodname_sponsors %} não cobra taxas por patrocínios de contas de usuários. Portanto, 100% desse patrocínio vai para o desenvolvedor ou organização patrocinada. The 10% fee for sponsorships from organizations is waived during the beta. diff --git a/translations/pt-BR/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/pt-BR/data/reusables/sponsors/org-sponsors-release-phase.md new file mode 100644 index 0000000000..75983073a4 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/org-sponsors-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Sponsoring on behalf of an organization is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/sponsors/pay-prorated-amount.md b/translations/pt-BR/data/reusables/sponsors/pay-prorated-amount.md new file mode 100644 index 0000000000..f201de957c --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/pay-prorated-amount.md @@ -0,0 +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 diff --git a/translations/pt-BR/data/reusables/sponsors/prorated-sponsorship.md b/translations/pt-BR/data/reusables/sponsors/prorated-sponsorship.md index 4e0b440277..56a047d867 100644 --- a/translations/pt-BR/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/pt-BR/data/reusables/sponsors/prorated-sponsorship.md @@ -1 +1 @@ -Você receberá uma cobrança automática de um valor rateado até a data da sua próxima cobrança normal. +If you're sponsoring on behalf of your user account, you will immediately be charged a prorated amount for the time until your next regular billing date. If you're sponsoring on behalf of an organization, you can choose to pay the prorated amount or make the full monthly payment. diff --git a/translations/pt-BR/data/reusables/sponsors/sponsor-account.md b/translations/pt-BR/data/reusables/sponsors/sponsor-account.md new file mode 100644 index 0000000000..d345cd73fe --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/sponsor-account.md @@ -0,0 +1 @@ +1. Click **Sponsor _ACCOUNT_**. ![Botão Sponsor (Patrocinar)](/assets/images/help/sponsors/sponsor-developer-button.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/sponsors/sponsorship-dashboard.md b/translations/pt-BR/data/reusables/sponsors/sponsorship-dashboard.md new file mode 100644 index 0000000000..579e36cf57 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/sponsorship-dashboard.md @@ -0,0 +1,4 @@ +1. Navigate to your sponsorship dashboard for the account. + - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![Botão de Patrocínio](/assets/images/help/profile/sponsoring-button.png) + - If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![Botão de Patrocínio](/assets/images/help/sponsors/org-sponsoring-button.png) +1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/pt-BR/data/reusables/sponsors/sponsorship-details.md b/translations/pt-BR/data/reusables/sponsors/sponsorship-details.md index 5d7c1362dc..a13cace30a 100644 --- a/translations/pt-BR/data/reusables/sponsors/sponsorship-details.md +++ b/translations/pt-BR/data/reusables/sponsors/sponsorship-details.md @@ -1 +1 @@ -Qualquer pessoa com uma conta de {% data variables.product.product_name %} pode patrocinar qualquer pessoa com um perfil de desenvolvedor patrocinado ou perfil de organização patrocinado através de um pagamento mensal recorrente. Você pode escolher entre várias camadas de patrocínio, com quantias e benefícios de pagamento mensais definidos pelo desenvolvedor ou organização patrocinado. O seu patrocínio compartilhará a data de cobrança existente da sua conta, o método de pagamento e o recibo. +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. 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/webhooks/app_always_desc.md b/translations/pt-BR/data/reusables/webhooks/app_always_desc.md new file mode 100644 index 0000000000..4c63628597 --- /dev/null +++ b/translations/pt-BR/data/reusables/webhooks/app_always_desc.md @@ -0,0 +1 @@ +`instalação` | `objeto` | A instalação de {% data variables.product.prodname_github_app %}. diff --git a/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_properties.md new file mode 100644 index 0000000000..b80259f64e --- /dev/null +++ b/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -0,0 +1,4 @@ +| Tecla | Tipo | Descrição | +| -------- | -------- | ---------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação que foi executada. This can be either `created`, `resolved`, or `reopened`. | +| `alerta` | `objeto` | The secret scanning alert involved in the event. | diff --git a/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md new file mode 100644 index 0000000000..270eb40ff9 --- /dev/null +++ b/translations/pt-BR/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -0,0 +1 @@ +Activity related to secret scanning alerts in a repository. O tipo de atividade é especificado na propriedade ação do objeto da carga. For more information, see “[About secret scanning](/github/administering-a-repository/about-secret-scanning).” diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml index a008706277..f959350afe 100644 --- a/translations/pt-BR/data/ui.yml +++ b/translations/pt-BR/data/ui.yml @@ -7,7 +7,7 @@ header: release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para obter as informações mais recentes, acesse a documentação em inglês. Se houver problemas com a tradução desta página, entre em contato conosco. localization_in_progress: Olá! No momento, esta página ainda está sendo desenvolvida ou traduzida. Para obter as informações mais recentes, acesse a documentação em inglês. - early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' + early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' search: need_help: Precisa de ajuda? placeholder: Pesquisar tópicos, produtos... @@ -56,6 +56,14 @@ contribution_cta: button: Faça uma contribuição or: Ou, to_guidelines: aprenda como contribuir. +enterprise_releases_list: + title: Enterprise Server Releases + currently_supported: Currently supported + currently_supported_message: See GitHub Enterprise for information about the latest release. + deprecated: Deprecated + deprecated_message: 'These docs remain available but are no longer maintained:' + deprecated_developer: Deprecated on developer.github.com + deprecated_developer_message: 'These docs remain available on the legacy developer site but are no longer maintained:' products: graphql: reference: @@ -123,3 +131,4 @@ footer: product_landing: quick_start: QuickStart reference_guides: Reference guides + overview: Visão Geral diff --git a/translations/pt-BR/data/variables/action_code_examples.yml b/translations/pt-BR/data/variables/action_code_examples.yml index 473c0a7438..cb6d66ecf9 100644 --- a/translations/pt-BR/data/variables/action_code_examples.yml +++ b/translations/pt-BR/data/variables/action_code_examples.yml @@ -1,12 +1,4 @@ --- -- - title: Fluxos de trabalho iniciais - description: Arquivos do fluxo de trabalho para ajudar pessoas a dar os primeiros passos com o GitHub Actions - languages: TypeScript - href: actions/starter-workflows - tags: - - official - - fluxo de trabalho - title: Example services description: Example workflows using service containers @@ -334,3 +326,10 @@ - monorepo - copybara - fluxo de trabalho +- + title: Deploy static files to GitHub Pages + description: GitHub Action to publish website to GitHub Pages automatically + languages: 'TypeScript, JavaScript' + href: peaceiris/actions-gh-pages + tags: + - publishing diff --git a/translations/pt-BR/data/variables/command_line.yml b/translations/pt-BR/data/variables/command_line.yml index 805c67903e..5d1f568716 100644 --- a/translations/pt-BR/data/variables/command_line.yml +++ b/translations/pt-BR/data/variables/command_line.yml @@ -1,5 +1,5 @@ --- -#Use this variable wherever backticks are necessary: https://github.com/github/docs-internal/pull/1176#discussion-diff-19853931 +#Use this variable wherever backticks are necessary backticks: >- {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} #Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!) diff --git a/translations/pt-BR/data/variables/discussions_community_examples.yml b/translations/pt-BR/data/variables/discussions_community_examples.yml new file mode 100644 index 0000000000..8b3594f2ec --- /dev/null +++ b/translations/pt-BR/data/variables/discussions_community_examples.yml @@ -0,0 +1,38 @@ +--- +- + #Images and descriptions are pulled directly from the repo + repo: vercel/next.js + description: The React Framework +- + repo: gatsbyjs/gatsby + description: Build blazing fast, modern apps and websites with React +- + repo: nodejs/node + description: Node.js JavaScript runtime ✨🐢🚀✨ +- + repo: tailwindlabs/tailwindcss + description: A utility-first CSS framework for rapid UI development. +- + repo: laravel/framework + description: Laravel is a web application framework with expressive, elegant syntax. +- + repo: prisma/prisma + description: Modern database access (ORM alternative) for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite +- + repo: dotnet/csharplang + description: 'The official repo for the design of the C# programming language' +- + repo: home-assistant/frontend + description: '🍭 Frontend for Home Assistant' +- + repo: jspsych/jsPsych + description: A JavaScript library for creating and running behavioral experiments in a web browser +- + repo: adonisjs/core + description: '🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence' +- + repo: ImageMagick/ImageMagick + description: '🧙‍♂️ ImageMagick 7' +- + repo: react-hook-form/react-hook-form + description: '📋 React Hooks for forms validation (Web + React Native)' diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index 547b62cacc..e9fc1d446a 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -37,7 +37,10 @@ prodname_unified_search: 'pesquisa unificada' #GitHub Education prodname_education: 'GitHub Education' prodname_education_community: 'Education Community' +prodname_education_community_with_url: 'the [GitHub Education Community](https://education.github.community)' prodname_classroom: 'GitHub Classroom' +prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)' +prodname_campus_program: 'GitHub Campus Program' prodname_student_pack: 'GitHub Student Developer Pack' #GitHub CLI prodname_cli: 'GitHub CLI' @@ -69,6 +72,8 @@ ae_azure_ad_app_link: 'the [GitHub AE application](https://azuremarketplace.micr prodname_actions: 'GitHub Actions' #GitHub Debug prodname_debug: 'GitHub Debug' +#GitHub Discussions +prodname_discussions: 'GitHub Discussions' #GitHub Packages prodname_registry: 'GitHub Package Registry' prodname_github_container_registry: 'Registro de contêiner do GitHub' @@ -103,7 +108,7 @@ support_ticket_priority_low: 'Baixo' #Security features / code scanning platform / Security Lab prodname_security: 'Laboratório de Segurança GitHub' prodname_security_link: 'https://securitylab.github.com/' -prodname_security_advisories: 'Consultoria de segurança GitHub' +prodname_security_advisories: 'Aviso de Segurança do GitHub' #Security features and code scanning platform prodname_secret_scanning: 'varredura secreta' prodname_secret_scanning_caps: 'Varredura secreta' 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 ab237deca6..c9e81f04b7 100644 --- a/translations/ru-RU/content/actions/creating-actions/about-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/about-actions.md @@ -33,8 +33,8 @@ You can build Docker container and JavaScript actions. Actions require a metadat | Тип | Operating system | | ------------------- | --------------------- | | Docker container | Linux | -| JavaScript | Linux, MacOS, Windows | -| Composite run steps | Linux, MacOS, Windows | +| JavaScript | Linux, macOS, Windows | +| Composite run steps | Linux, macOS, Windows | #### Docker container actions 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 a049477ac5..b4e0de3322 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 @@ -226,6 +226,10 @@ jobs: ``` {% endraw %} -From your repository, click the **Actions** tab, and select the latest workflow run. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +From your repository, click the **Actions** tab, and select the latest workflow run. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png) +{% else %} ![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run.png) +{% endif %} 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 06ffca01fb..dde101d2a8 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 @@ -176,7 +176,7 @@ git tag -a -m "My first action release" v1 git push --follow-tags ``` -As an alternative to checking in your `node_modules` directory you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. +Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. 1. Install `vercel/ncc` by running this command in your terminal. `npm i -g @vercel/ncc` @@ -256,9 +256,11 @@ jobs: ``` {% endraw %} -From your repository, click the **Actions** tab, and select the latest workflow run. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. +From your repository, click the **Actions** tab, and select the latest workflow run. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Under **Jobs** or in the visualization graph, click **A job to say hello**. {% endif %}You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} ![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png) {% else %} ![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run.png) 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 885efa3b2b..03c54ad08c 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 @@ -22,19 +22,19 @@ Docker and JavaScript actions require a metadata file. The metadata filename mus Action metadata files use YAML syntax. If you're new to YAML, you can read "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." -### **`name`** +### `name` **Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job. -### **`автор`** +### `автор` **Optional** The name of the action's author. -### **`описание`** +### `описание` **Required** A short description of the action. -### **`inputs`** +### `inputs` **Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids. @@ -57,23 +57,23 @@ When you specify an input to an action in a workflow file or use a default input 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.`** +#### `inputs.` **Required** A `string` identifier to associate with the input. The value of `` is a map of the input's metadata. The `` must be a unique identifier within the `inputs` object. The `` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`. -#### **`inputs..description`** +#### `inputs..description` **Required** A `string` description of the input parameter. -#### **`inputs..required`** +#### `inputs..required` **Required** A `boolean` to indicate whether the action requires the input parameter. Set to `true` when the parameter is required. -#### **`inputs..default`** +#### `inputs..default` **Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file. -### **`outputs`** +### `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. @@ -87,15 +87,15 @@ outputs: description: 'The sum of the inputs' ``` -#### **`outputs.`** +#### `outputs.` **Required** A `string` identifier to associate with the output. The value of `` is a map of the output's metadata. The `` must be a unique identifier within the `outputs` object. The `` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`. -#### **`outputs..description`** +#### `outputs..description` **Required** A `string` description of the output parameter. -### **`outputs`** for composite run steps actions +### `outputs` for composite run steps actions **Optional** `outputs` use the same parameters as `outputs.` and `outputs..description` (see "[`outputs` for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), but also includes the `value` token. @@ -116,12 +116,12 @@ runs: ``` {% endraw %} -#### **`outputs.`** +#### `outputs..value` **Required** The value that the output parameter will be mapped to. You can set this to a `string` or an expression with context. For example, you can use the `steps` context to set the `value` of an output to the output value of a step. For more information on how to use context and expression syntax, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". -### **`runs`** for JavaScript actions +### `runs` for JavaScript actions **Required** Configures the path to the action's code and the application used to execute the code. @@ -133,15 +133,15 @@ runs: main: 'main.js' ``` -#### **`runs.using`** +#### `runs.using` **Required** The application used to execute the code specified in [`main`](#runsmain). -#### **`runs.main`** +#### `runs.main` **Required** The file that contains your action code. The application specified in [`using`](#runsusing) executes this file. -#### **`pre`** +#### `pre` **Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The application specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if). @@ -155,7 +155,7 @@ runs: post: 'cleanup.js' ``` -#### **`pre-if`** +#### `pre-if` **Optional** Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`. Note that the `step` context is unavailable, as no steps have run yet. @@ -166,7 +166,7 @@ In this example, `cleanup.js` only runs on Linux-based runners: pre-if: 'runner.os == linux' ``` -#### **`сообщение`** +#### `сообщение` **Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The application specified with the [`using`](#runsusing) syntax will execute this file. @@ -181,7 +181,7 @@ runs: The `post:` action always runs by default but you can override this using `post-if`. -#### **`post-if`** +#### `post-if` **Optional** Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`. @@ -192,19 +192,19 @@ For example, this `cleanup.js` will only run on Linux-based runners: post-if: 'runner.os == linux' ``` -### **`runs`** for composite run steps actions +### `runs` for composite run steps actions **Required** Configures the path to the composite action, and the application used to execute the code. -#### **`runs.using`** +#### `runs.using` **Required** To use a composite run steps action, set this to `"composite"`. -#### **`runs.steps`** +#### `runs.steps` **Required** The run steps that you plan to run in this action. -##### **`runs.steps.run`** +##### `runs.steps.run` **Required** The command you want to run. This can be inline or a script in your action repository: ```yaml @@ -227,27 +227,27 @@ runs: For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". -##### **`runs.steps.shell`** +##### `runs.steps.shell` **Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell). -##### **`runs.steps.name`** +##### `runs.steps.name` **Optional** The name of the composite run step. -##### **`runs.steps.id`** +##### `runs.steps.id` **Optional** 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)". -##### **`runs.steps.env`** +##### `runs.steps.env` **Optional** Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} in a composite run step. -##### **`runs.steps.working-directory`** +##### `runs.steps.working-directory` **Optional** Specifies the working directory where the command is run. -### **`runs`** for Docker actions +### `runs` for Docker actions **Required** Configures the image used for the Docker action. @@ -267,11 +267,11 @@ runs: image: 'docker://debian:stretch-slim' ``` -#### **`runs.using`** +#### `runs.using` **Required** You must set this value to `'docker'`. -#### **`pre-entrypoint`** +#### `pre-entrypoint` **Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if). @@ -289,21 +289,21 @@ runs: entrypoint: 'main.sh' ``` -#### **`runs.image`** +#### `runs.image` **Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. To reference a `Dockerfile` local to your repository, use a path relative to your action metadata file. The `docker` application will execute this file. -#### **`runs.env`** +#### `runs.env` **Optional** Specifies a key/value map of environment variables to set in the container environment. -#### **`runs.entrypoint`** +#### `runs.entrypoint` **Optional** Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Use `entrypoint` when the `Dockerfile` does not specify an `ENTRYPOINT` or you want to override the `ENTRYPOINT` instruction. If you omit `entrypoint`, the commands you specify in the Docker `ENTRYPOINT` instruction will execute. The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction. For more information about how the `entrypoint` executes, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)." -#### **`post-entrypoint`** +#### `post-entrypoint` **Optional** Allows you to run a cleanup script once the `runs.entrypoint` action has completed. {% data variables.product.prodname_actions %} uses `docker run` to launch this action. Because {% data variables.product.prodname_actions %} runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using [`post-if`](#post-if). @@ -317,7 +317,7 @@ runs: post-entrypoint: 'cleanup.sh' ``` -#### **`runs.args`** +#### `runs.args` **Optional** An array of strings that define the inputs for a Docker container. Inputs can include hardcoded strings. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. @@ -343,7 +343,7 @@ runs: ``` {% endraw %} -### **`branding`** +### `branding` You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. Badges are shown next to your action name in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). @@ -355,11 +355,11 @@ branding: color: 'green' ``` -#### **`branding.color`** +#### `branding.color` The background color of the badge. Can be one of: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, or `gray-dark`. -#### **`branding.icon`** +#### `branding.icon` The name of the [Feather](https://feathericons.com/) icon to use. 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 eb7356bed3..ccc1b09e9c 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 @@ -25,7 +25,11 @@ Creating a package at the end of a continuous integration workflow can help duri Now, when reviewing a pull request, you'll be able to look at the workflow run and download the artifact that was produced. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png) +{% else %} ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png) +{% endif %} This will let you run the code in the pull request on your machine, which can help with debugging or testing the pull request. 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 8bf1dc05d5..d3dbce807e 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 @@ -53,7 +53,7 @@ jobs: with: java-version: 1.8 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -85,7 +85,7 @@ steps: with: java-version: 1.8 - name: Run the Maven verify phase - run: mvn -B verify --file pom-ci.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -108,7 +108,7 @@ steps: key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} restore-keys: ${{ runner.os }}-m2 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -125,7 +125,7 @@ Maven will usually create output files like JARs, EARs, or WARs in the `target` steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 - - run: mvn -B package --file pom.xml + - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 with: 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 dec09e228b..11a2a58d30 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 @@ -60,7 +60,11 @@ jobs: * `run: Test-Path resultsfile.log` - Check whether a file called `resultsfile.log` is present in the repository's root directory. * `Should -Be $true` - Uses Pester to define an expected result. If the result is unexpected, then {% data variables.product.prodname_actions %} flags this as a failed test. Например: + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test-updated.png) + {% else %} ![Failed Pester test](/assets/images/help/repository/actions-failed-pester-test.png) + {% endif %} * `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following: ``` 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 c70bc9a782..6279546b58 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 @@ -84,7 +84,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -143,7 +143,7 @@ jobs: with: java-version: 1.8 - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` @@ -182,7 +182,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish to the Maven Central Repository - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -191,7 +191,7 @@ jobs: with: java-version: 1.8 - name: Publish to GitHub Packages - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` 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 6fcd92f8fc..8069dc936c 100644 --- a/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/ru-RU/content/actions/guides/publishing-nodejs-packages.md @@ -8,8 +8,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 2e25b7201b..b04280b570 100644 --- a/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/ru-RU/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,8 +11,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/ru-RU/content/actions/guides/storing-workflow-data-as-artifacts.md index 2ebfa58e4a..e4c841fe28 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 @@ -108,8 +108,6 @@ jobs: path: output/test/code-coverage.html ``` -![Image of workflow upload artifact workflow run](/assets/images/help/repository/upload-build-test-artifact.png) - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Configuring a custom artifact retention period @@ -238,7 +236,12 @@ jobs: echo The result is $value ``` +The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% else %} ![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +{% endif %} {% if currentVersion == "free-pro-team@latest" %} 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 022c544673..28591c40bf 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 @@ -87,7 +87,7 @@ The following operating systems are supported for the self-hosted runner applica - Windows Server 2016 64-bit - Windows Server 2019 64-bit -#### MacOS +#### macOS - macOS 10.13 (High Sierra) or later diff --git a/translations/ru-RU/content/actions/index.md b/translations/ru-RU/content/actions/index.md index a52b17016f..4365c6f495 100644 --- a/translations/ru-RU/content/actions/index.md +++ b/translations/ru-RU/content/actions/index.md @@ -41,6 +41,7 @@ changelog: title: Self-Hosted Runner Group Access Changes date: '2020-10-16' href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ +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/ @@ -69,18 +70,18 @@ versions:

      Code examples

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

      Sorry, there is no result for

      +

      Sorry, there is no result for

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

      Learn how to add a code example {% octicon "arrow-right" %}
      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 345235b252..be54e37e62 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 @@ -204,13 +204,18 @@ In this diagram, you can see the workflow file you just created and how the {% d ### Viewing the job's activity -Once your job has started running, you can view each step's activity on {% data variables.product.prodname_dotcom %}. +Once your job has started running, you can {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}see a visualization graph of the run's progress and {% endif %}view each step's activity on {% data variables.product.prodname_dotcom %}. {% data reusables.repositories.navigate-to-repo %} 1. Under your repository name, click **Actions**. ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png) 1. In the left sidebar, click the workflow you want to see. ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png) 1. Under "Workflow runs", click the name of the run you want to see. ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Select job](/assets/images/help/images/overview-actions-result-navigate.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. View the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. Click on the job name to see the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated.png) {% else %} 1. Click on the job name to see the results of each step. ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result.png) 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 f55cb35349..5e104fc5b9 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 @@ -54,6 +54,8 @@ This means that a compromise of a single action within a workflow can be very si **Warning:** The short version of the commit SHA is insecure and should never be used for specifying an action's Git reference. Because of how repository networks work, any user can fork the repository and push a crafted commit to it that collides with the short SHA. This causes subsequent clones at that SHA to fail because it becomes an ambiguous commit. As a result, any workflows that use the shortened SHA will immediately fail. {% endwarning %} + + * **Audit the source code of the action** Ensure that the action is handling the content of your repository and secrets as expected. For example, check that secrets are not sent to unintended hosts, or are not inadvertently logged. @@ -92,10 +94,14 @@ This list describes the recommended approaches for accessing repository data wit As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be cautious when using self-hosted runners on private repositories, as anyone who can fork the repository and open a PR (generally those with read-access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the more privileged `GITHUB_TOKEN` which grants write-access permissions on the repository. +When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)." + You should also consider the environment of the self-hosted runner machines: - What sensitive information resides on the machine configured as a self-hosted runner? For example, private SSH keys, API access tokens, among others. - Does the machine have network access to sensitive services? For example, Azure or AWS metadata services. The amount of sensitive information in this environment should be kept to a minimum, and you should always be mindful that any user capable of invoking workflows has access to this environment. +Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. + ### Auditing {% data variables.product.prodname_actions %} events 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. @@ -130,5 +136,3 @@ The following tables describe the {% data variables.product.prodname_actions %} | `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. | - - diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/canceling-a-workflow.md index 031f4cb53f..80174965ed 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -17,8 +17,13 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} -{% data reusables.repositories.view-run %} -1. In the upper-right corner of the workflow, click **Cancel workflow**. ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite.png) +1. From the list of workflow runs, click the name of the `queued` or `in progress` run that you want to cancel. ![Name of workflow run](/assets/images/help/repository/in-progress-run.png) +1. In the upper-right corner of the workflow, click **Cancel workflow**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite-updated.png) +{% else %} + ![Cancel check suite button](/assets/images/help/repository/cancel-check-suite.png) +{% endif %} ### Steps {% data variables.product.prodname_dotcom %} takes to cancel a workflow run diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 591f969666..64daea7ddb 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -19,4 +19,9 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under **Artifacts**, click the artifact you want to download. ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png) +1. Under **Artifacts**, click the artifact you want to download. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down-updated.png) + {% else %} + ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png) + {% endif %} diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/index.md b/translations/ru-RU/content/actions/managing-workflow-runs/index.md index 5096b761c7..8905d8b087 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/index.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/index.md @@ -18,6 +18,7 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% link_in_list /using-the-visualization-graph %}{% endif %} {% link_in_list /viewing-workflow-run-history %} {% link_in_list /using-workflow-run-logs %} {% link_in_list /manually-running-a-workflow %} diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md index 5c46ed4da5..323ebab2d3 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -16,4 +16,4 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**. ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png) +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index a7eb83e1c6..ae9e20f6f5 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -26,7 +26,13 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under **Artifacts**, click {% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove. ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact.png) +1. Under **Artifacts**, click +{% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact-updated.png) + {% else %} + ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact.png) + {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### Setting the retention period for an artifact diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/ru-RU/content/actions/managing-workflow-runs/using-the-visualization-graph.md new file mode 100644 index 0000000000..f1ef803e42 --- /dev/null +++ b/translations/ru-RU/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -0,0 +1,21 @@ +--- +title: Using the visualization graph +intro: Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.visualization-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} + +1. The graph displays each job in the workflow. An icon to the left of the job name indicates the status of the job. Lines between jobs indicate dependencies. ![Workflow graph](/assets/images/help/images/workflow-graph.png) + +2. Click on a job to view the job log. ![Workflow graph](/assets/images/help/images/workflow-graph-job.png) diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md index a6150cf4bf..bc67775e57 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -44,7 +44,12 @@ You can search the build logs for a particular step. When you search logs, only {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query. ![Search box to search logs](/assets/images/help/repository/search-log-box-updated.png) +1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Search box to search logs](/assets/images/help/repository/search-log-box-updated-2.png) +{% else %} + ![Search box to search logs](/assets/images/help/repository/search-log-box-updated.png) +{% endif %} {% else %} 1. To expand each step you want to include in your search, click the step. ![Step name](/assets/images/help/repository/failed-check-step.png) 1. In the upper-right corner of the log output, in the **Search logs** search box, type a search query. ![Search box to search logs](/assets/images/help/repository/search-log-box.png) @@ -61,8 +66,12 @@ You can download the log files from your workflow run. You can also download a w {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 1. In the upper right corner, click -{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Download log archive**. +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated-2.png) + {% else %} ![Download logs drop-down menu](/assets/images/help/repository/download-logs-drop-down-updated.png) + {% endif %} {% else %} 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Download log archive**. @@ -78,8 +87,20 @@ You can delete the log files from your workflow run. {% data reusables.repositor {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) -2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. +1. In the upper right corner, click +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) + {% else %} + ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) + {% endif %} +2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated-2.png) + {% else %} + ![Delete all logs](/assets/images/help/repository/delete-all-logs-updated.png) + {% endif %} +After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. {% else %} 1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png) 2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt. ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) After the logs have been deleted, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run. diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/ru-RU/content/actions/managing-workflow-runs/viewing-job-execution-time.md index 709a7343a9..402220c3c0 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/viewing-job-execution-time.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -15,7 +15,7 @@ Billable job execution minutes are only shown for jobs run on private repositori {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. Under the job summary, you can view the job's execution time. To view the billable job execution time, click **Run and billable time details**. ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png) +1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, click the time under **Billable time**. ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png) {% note %} diff --git a/translations/ru-RU/content/actions/quickstart.md b/translations/ru-RU/content/actions/quickstart.md index 803a2f1f9c..9410275136 100644 --- a/translations/ru-RU/content/actions/quickstart.md +++ b/translations/ru-RU/content/actions/quickstart.md @@ -59,7 +59,11 @@ Committing the workflow file in your repository triggers the `push` event and ru {% 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 %} ### More starter workflows @@ -101,7 +105,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o # When the event is triggered, GitHub Actions will run the jobs indicated jobs: say_hello: - # Uses a ubuntu-lates runner to complete the requested steps + # Uses a ubuntu-latest runner to complete the requested steps runs-on: ubuntu-latest steps: - run: | diff --git a/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md index 4c9f3de9f1..3830d74d03 100644 --- a/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,7 +75,7 @@ In order to use property dereference syntax, the property name must: - start with `a-Z` or `_`. - be followed by `a-Z` `0-9` `-` or `_`. -#### **`github` context** +#### `github` context The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." @@ -103,7 +103,7 @@ The `github` context contains information about the workflow run and the event t | `github.workflow` | `строка` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. | | `github.workspace` | `строка` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | -#### **`env` context** +#### `env` context The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)." @@ -117,7 +117,7 @@ You can only use the `env` context in the value of the `with` and `name` keys, o | `env.` | `строка` | The value of a specific environment variable. | -#### **`job` context** +#### `job` context The `job` context contains information about the currently running job. @@ -133,7 +133,7 @@ The `job` context contains information about the currently running job. | `job.services..ports` | `объект` | The exposed ports of the service container. | | `job.status` | `строка` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. | -#### **`steps` context** +#### `steps` context The `steps` context contains information about the steps in the current job that have already run. @@ -145,7 +145,7 @@ The `steps` context contains information about the steps in the current job that | `steps..outcome` | `строка` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. | | `steps..outputs.` | `строка` | The value of a specific output. | -#### **`runner` context** +#### `runner` context The `runner` context contains information about the runner that is executing the current job. @@ -155,7 +155,7 @@ The `runner` context contains information about the runner that is executing the | `runner.temp` | `строка` | The path of the temporary directory for the runner. This directory is guaranteed to be empty at the start of each job, even on self-hosted runners. | | `runner.tool_cache` | `строка` | The path of the directory containing some of the preinstalled tools for {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". | -#### **`needs` context** +#### `needs` context The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)." diff --git a/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md b/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md index 9295302d18..10b9a27f87 100644 --- a/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/ru-RU/content/actions/reference/events-that-trigger-workflows.md @@ -137,9 +137,9 @@ jobs: #### `repository_dispatch` -| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------- | -------------- | -------------------------------------- | ----------------------------- | -| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Last commit on the `GITHUB_REF` branch | Branch that received dispatch | +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------------------- | -------------- | ----------------------------- | -------------- | +| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Last commit on default branch | Default branch | {% data reusables.github-actions.branch-requirement %} @@ -699,6 +699,8 @@ on: {% data reusables.webhooks.workflow_run_desc %} +{% data reusables.github-actions.branch-requirement %} + | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------- | -------------- | ----------------------------- | -------------- | | [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - n/a | Last commit on default branch | Default branch | diff --git a/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md index 5adf188b42..3c419f5b28 100644 --- a/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/ru-RU/content/actions/reference/specifications-for-github-hosted-runners.md @@ -63,8 +63,8 @@ The software tools included in {% data variables.product.prodname_dotcom %}-host * [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md) * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md) -* [MacOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) -* [MacOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) +* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) {% data reusables.github-actions.ubuntu-runner-preview %} {% data reusables.github-actions.macos-runner-preview %} diff --git a/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md index 77ce7b885f..71898fbdfd 100644 --- a/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/reference/workflow-syntax-for-github-actions.md @@ -21,17 +21,17 @@ Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file ex You must store workflow files in the `.github/workflows` directory of your repository. -### **`name`** +### `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. -### **`on`** +### `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)." {% data reusables.github-actions.actions-on-examples %} -### **`on..types`** +### `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. @@ -45,7 +45,7 @@ on: types: [published, created, edited] ``` -### **`on..`** +### `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. @@ -112,7 +112,7 @@ on: - '!releases/**-alpha' ``` -### **`on..paths`** +### `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. @@ -179,13 +179,13 @@ The filter determines if a workflow should run by evaluating the changed files a For more information, see "[About comparing branches in pull requests](/articles/about-comparing-branches-in-pull-requests)." -### **`on.schedule`** +### `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)." -### **`env`** +### `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). @@ -198,13 +198,13 @@ env: SERVER: production ``` -### **`defaults`** +### `defaults` 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). {% data reusables.github-actions.defaults-override %} -### **`defaults.run`** +### `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. @@ -219,7 +219,7 @@ defaults: working-directory: scripts ``` -### **`jobs`** +### `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. @@ -229,7 +229,7 @@ You can run an unlimited number of jobs as long as you are within the workflow u If you need to find the unique identifier of a job running in a workflow run, you can use the {% data variables.product.prodname_dotcom %} API. For more information, see "[Workflow Jobs](/rest/reference/actions#workflow-jobs)." -### **`jobs.`** +### `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 `_`. @@ -243,15 +243,15 @@ jobs: name: My second job ``` -### **`jobs..name`** +### `jobs..name` The name of the job displayed on {% data variables.product.prodname_dotcom %}. -### **`jobs..needs`** +### `jobs..needs` -Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional statement that causes the job to continue. +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. -#### Пример +#### Example requiring dependent jobs to be successful ```yaml jobs: @@ -270,7 +270,21 @@ The jobs in this example run sequentially: 2. `job2` 3. `job3` -### **`jobs..runs-on`** +#### Example not requiring dependent jobs to be successful + +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + if: always() + 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)." + +### `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. @@ -286,7 +300,7 @@ Available {% data variables.product.prodname_dotcom %}-hosted runner types are: {% data reusables.github-actions.ubuntu-runner-preview %} -##### **Пример** +##### Пример ```yaml runs-on: ubuntu-latest @@ -298,7 +312,7 @@ For more information, see "[Virtual environments for {% data variables.product.p {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -##### **Пример** +##### Пример ```yaml runs-on: [self-hosted, linux] @@ -306,7 +320,7 @@ 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)." -### **`jobs..outputs`** +### `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). @@ -314,7 +328,7 @@ Job outputs are strings, and job outputs containing expressions are evaluated on 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)." -#### **Пример** +#### Пример {% raw %} ```yaml @@ -338,13 +352,13 @@ jobs: ``` {% endraw %} -### **`jobs..env`** +### `jobs..env` A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs..steps.env`](#jobsjob_idstepsenv). {% data reusables.repositories.actions-env-var-note %} -#### **Пример** +#### Пример ```yaml jobs: @@ -353,13 +367,13 @@ jobs: FIRST_NAME: Mona ``` -### **`jobs..defaults`** +### `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). {% data reusables.github-actions.defaults-override %} -### **`jobs..defaults.run`** +### `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. @@ -379,13 +393,13 @@ jobs: working-directory: scripts ``` -### **`jobs..if`** +### `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. {% 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)." -### **`jobs..steps`** +### `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. @@ -415,17 +429,17 @@ jobs: ``` {% endraw %} -#### **`jobs..steps.id`** +### `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)." -#### **`jobs..steps.if`** +### `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. {% 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)." -##### Example using contexts +#### Example using contexts This step only runs when the event type is a `pull_request` and the event action is `unassigned`. @@ -436,7 +450,7 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -##### Example using status check functions +#### Example using status check functions 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)." @@ -449,11 +463,11 @@ steps: uses: actions/heroku@1.0.0 ``` -#### **`jobs..steps.name`** +### `jobs..steps.name` A name for your step to display on {% data variables.product.prodname_dotcom %}. -#### **`jobs..steps.uses`** +### `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/). @@ -466,7 +480,7 @@ Some actions require inputs that you must set using the [`with`](#jobsjob_idstep 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). -##### Example using versioned actions +#### Example using versioned actions ```yaml steps: @@ -480,7 +494,7 @@ steps: - uses: actions/setup-node@main ``` -##### Example using a public action +#### Example using a public action `{owner}/{repo}@{ref}` @@ -498,7 +512,7 @@ jobs: uses: actions/aws@v2.0.1 ``` -##### Example using a public action in a subdirectory +#### Example using a public action in a subdirectory `{owner}/{repo}/{path}@{ref}` @@ -512,7 +526,7 @@ jobs: uses: actions/aws/ec2@main ``` -##### Example using action in the same repository as the workflow +#### Example using action in the same repository as the workflow `./path/to/dir` @@ -528,7 +542,7 @@ jobs: uses: ./.github/actions/my-action ``` -##### Example using a Docker Hub action +#### Example using a Docker Hub action `docker://{image}:{tag}` @@ -542,7 +556,7 @@ jobs: uses: docker://alpine:3.8 ``` -##### Example using a Docker public registry action +#### Example using a Docker public registry action `docker://{host}/{image}:{tag}` @@ -556,7 +570,7 @@ jobs: uses: docker://gcr.io/cloud-builders/gradle ``` -#### **`jobs..steps.run`** +### `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. @@ -588,7 +602,7 @@ Using the `working-directory` keyword, you can specify the working directory of working-directory: ./temp ``` -##### Using a specific shell +#### Using a specific shell You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. @@ -601,7 +615,7 @@ You can override the default shell settings in the runner's operating system usi | 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}'"`. | -##### Example running a script using bash +#### Example running a script using bash ```yaml steps: @@ -610,7 +624,7 @@ steps: shell: bash ``` -##### Example running a script using Windows `cmd` +#### Example running a script using Windows `cmd` ```yaml steps: @@ -619,7 +633,7 @@ steps: shell: cmd ``` -##### Example running a script using PowerShell Core +#### Example running a script using PowerShell Core ```yaml steps: @@ -628,7 +642,7 @@ steps: shell: pwsh ``` -##### Example running a python script +#### Example running a python script ```yaml steps: @@ -639,11 +653,11 @@ steps: shell: python ``` -##### Custom shell +#### Custom shell You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`. -##### Exit codes and error action preference +#### Exit codes and error action preference 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. @@ -661,11 +675,11 @@ For built-in shell keywords, we provide the following defaults that are executed - 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. -#### **`jobs..steps.with`** +### `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. -##### Пример +#### Пример 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. @@ -681,11 +695,11 @@ jobs: last_name: Octocat ``` -#### **`jobs..steps.with.args`** +### `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. -##### Пример +#### Пример {% raw %} ```yaml @@ -704,11 +718,11 @@ The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you 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. -#### **`jobs..steps.with.entrypoint`** +### `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. -##### Пример +#### Пример ```yaml steps: @@ -720,7 +734,7 @@ steps: The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs. -#### **`jobs..steps.env`** +### `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). @@ -728,7 +742,7 @@ Sets environment variables for steps to use in the runner environment. You can a 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)." -##### Пример +#### Пример {% raw %} ```yaml @@ -741,23 +755,23 @@ steps: ``` {% endraw %} -#### **`jobs..steps.continue-on-error`** +### `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. -#### **`jobs..steps.timeout-minutes`** +### `jobs..steps.timeout-minutes` The maximum number of minutes to run the step before killing the process. -### **`jobs..timeout-minutes`** +### `jobs..timeout-minutes` The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360 -### **`jobs..strategy`** +### `jobs..strategy` A strategy creates a build matrix for your jobs. You can define different variations of an environment to run each job in. -#### **`jobs..strategy.matrix`** +### `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. @@ -767,7 +781,7 @@ Each option you define in the `matrix` has a key and value. The keys you define The order that you define a `matrix` matters. The first option you define will be the first job that runs in your workflow. -##### Example running with more than one version of Node.js +#### Example running with more than one version of 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`. @@ -789,7 +803,7 @@ steps: 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. -##### Example running with more than one operating system +#### Example running with more than one operating system 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: @@ -814,7 +828,7 @@ steps: 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)." -##### Example including additional values into combinations +#### Example including additional values into combinations 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. @@ -834,7 +848,7 @@ strategy: ``` {% endraw %} -##### Example including new combinations +#### Example including new combinations 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. @@ -852,7 +866,7 @@ strategy: ``` {% endraw %} -##### Example excluding configurations from a matrix +#### Example excluding configurations from a matrix 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`). @@ -882,11 +896,11 @@ You can add custom environment variables for each test combination by using the {% data reusables.github-actions.matrix-variable-example %} -### **`jobs..strategy.fail-fast`** +### `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` -### **`jobs..strategy.max-parallel`** +### `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. @@ -895,7 +909,7 @@ strategy: max-parallel: 2 ``` -### **`jobs..continue-on-error`** +### `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. @@ -920,7 +934,7 @@ strategy: ``` {% endraw %} -### **`jobs..container`** +### `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. @@ -950,16 +964,17 @@ jobs: container: node:10.16-jessie ``` -#### **`jobs..container.image`** +### `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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..container.credentials`** + +### `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -##### Пример +#### Пример {% raw %} ```yaml @@ -972,15 +987,15 @@ container: {% endraw %} {% endif %} -#### **`jobs..container.env`** +### `jobs..container.env` Sets a `map` of environment variables in the container. -#### **`jobs..container.ports`** +### `jobs..container.ports` Sets an `array` of ports to expose on the container. -#### **`jobs..container.volumes`** +### `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. @@ -990,7 +1005,7 @@ To specify a volume, you specify the source and destination path: The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -##### Пример +#### Пример ```yaml volumes: @@ -999,11 +1014,11 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..container.options`** +### `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)." -### **`jobs..services`** +### `jobs..services` {% data reusables.github-actions.docker-container-os-support %} @@ -1033,16 +1048,17 @@ services: - 6379/tcp ``` -#### **`jobs..services..image`** +### `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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..services..credentials`** + +### `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -##### Пример +#### Пример {% raw %} ```yaml @@ -1061,15 +1077,15 @@ services: {% endraw %} {% endif %} -#### **`jobs..services..env`** +### `jobs..services..env` Sets a `map` of environment variables in the service container. -#### **`jobs..services..ports`** +### `jobs..services..ports` Sets an `array` of ports to expose on the service container. -#### **`jobs..services..volumes`** +### `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. @@ -1079,7 +1095,7 @@ To specify a volume, you specify the source and destination path: The `` is a volume name or an absolute path on the host machine, and `` is an absolute path in the container. -##### Пример +#### Пример ```yaml volumes: @@ -1088,7 +1104,7 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..services..options`** +### `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)." diff --git a/translations/ru-RU/content/admin/configuration/index.md b/translations/ru-RU/content/admin/configuration/index.md index 736ec887b6..4efeb57618 100644 --- a/translations/ru-RU/content/admin/configuration/index.md +++ b/translations/ru-RU/content/admin/configuration/index.md @@ -31,9 +31,7 @@ versions: {% link_in_list /enabling-private-mode %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} - {% link_in_list /configuring-applications %} - {% link_in_list /troubleshooting-ssl-errors %} {% link_in_list /configuring-time-synchronization %} {% link_in_list /command-line-utilities %} @@ -54,11 +52,7 @@ versions: {% link_in_list /connecting-github-enterprise-server-to-github-enterprise-cloud %} {% link_in_list /enabling-unified-search-between-github-enterprise-server-and-githubcom %} {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %} - {% link_in_list /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server %} {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} - - {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} - diff --git a/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md index abb0d22717..a47ef30184 100644 --- a/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/ru-RU/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -37,7 +37,7 @@ The time required to failover depends on how long it takes to manually promote t ``` - On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace *`UUID`* with a UUID you retrieved in the previous step. ```shell - $ ghe-repl-teardown -u UUNID + $ ghe-repl-teardown -u UUID ``` ### Дополнительная литература 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 fe5215e4fb..c4f769fc23 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 @@ -24,7 +24,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ### Требования -* Before using the 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](/github/setting-up-and-managing-organizations-and-teams/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)." ### Example: Using the `actions-sync` tool diff --git a/translations/ru-RU/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ru-RU/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 83a7d50425..7fe7ae7d9a 100644 --- a/translations/ru-RU/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ru-RU/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -1,6 +1,6 @@ --- title: Setting up the tool cache on self-hosted runners without internet access -intro: 'To use the the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' +intro: 'To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' redirect_from: - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access versions: diff --git a/translations/ru-RU/content/admin/index.md b/translations/ru-RU/content/admin/index.md index 14c3aca964..6928e31fc4 100644 --- a/translations/ru-RU/content/admin/index.md +++ b/translations/ru-RU/content/admin/index.md @@ -28,3 +28,5 @@ versions: {% link_with_intro /packages %} {% link_with_intro /enterprise-support %} + +{% link_with_intro /release-notes %} diff --git a/translations/ru-RU/content/admin/overview/about-enterprise-accounts.md b/translations/ru-RU/content/admin/overview/about-enterprise-accounts.md index 02c92ad31d..26731d2fac 100644 --- a/translations/ru-RU/content/admin/overview/about-enterprise-accounts.md +++ b/translations/ru-RU/content/admin/overview/about-enterprise-accounts.md @@ -15,7 +15,7 @@ An enterprise account allows you to manage multiple organizations{% if enterpris - 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) +- 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 reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." diff --git a/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md b/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md index ec679b8d8c..8305fed871 100644 --- a/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/ru-RU/content/developers/apps/authenticating-with-github-apps.md @@ -28,7 +28,7 @@ To generate a private key: {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. In "Private keys," click **Generate a private key**. ![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png) +5. In "Private keys", click **Generate a private key**. ![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png) 6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key. {% note %} 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 79419f195d..c2ec9ed768 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 @@ -73,7 +73,9 @@ You can select permissions in a query string using the permission name in the fo | `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. | | [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. | | [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`. | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %} | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. | | [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. | | [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. | diff --git a/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md b/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md index c2d1e6230d..bc626b0025 100644 --- a/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/scopes-for-oauth-apps.md @@ -46,7 +46,8 @@ X-Accepted-OAuth-Scopes: user |  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | |  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | |  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | -|  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} +|  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +|  `security_events` | Grants:
      read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).
      read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning).{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} |  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} | **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | |  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | diff --git a/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index 631fe6f7e7..c90a2d5c48 100644 --- a/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/ru-RU/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -422,7 +422,7 @@ Here are a few common problems and some suggested solutions. If you run into any **A:** You may not be running the Smee client, or you may not have the correct Smee domain in your GitHub App settings. First check to make sure the Smee client is running in a Terminal tab. If that's not the problem, visit your [app settings page](https://github.com/settings/apps) and check the fields shown in "[Step 2. Register a new GitHub App](#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u ` command in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." -* **Q:** I'm getting seeing an `Octokit::NotFound` 404 error in my debug output: +* **Q:** I'm getting an `Octokit::NotFound` 404 error in my debug output: ``` 2018-12-06 15:00:56 - Octokit::NotFound - POST https://api.github.com/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token: ``` diff --git a/translations/ru-RU/content/developers/github-marketplace/about-github-marketplace.md b/translations/ru-RU/content/developers/github-marketplace/about-github-marketplace.md index fd42d3a91c..1ad70da5ab 100644 --- a/translations/ru-RU/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/ru-RU/content/developers/github-marketplace/about-github-marketplace.md @@ -1,6 +1,6 @@ --- title: About GitHub Marketplace -intro: 'Learn the basics to prepare your app for review before joining {% data variables.product.prodname_marketplace %}.' +intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.' redirect_from: - /apps/marketplace/getting-started/ - /marketplace/getting-started @@ -14,52 +14,41 @@ versions: {% data reusables.actions.actions-not-verified %} -To learn about publishing {% data variables.product.prodname_actions %} in the {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." +To learn about publishing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." ### Приложения -You can list verified and unverified apps in {% data variables.product.prodname_marketplace %}. Unverified apps do not go through the security, testing, and verification cycle {% data variables.product.prodname_dotcom %} requires for verified apps. +Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only listings that are verified by {% data variables.product.company_short %} can include paid plans. For more information, see "[About verified creators](/developers/github-marketplace/about-verified-creators)." -Verified apps have a green badge in {% data variables.product.prodname_marketplace %}. Unverified apps have a grey badge next to their listing and are only available as free apps. +If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)." -![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) - -If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s, see "[Building apps](/apps/)." - -{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. See "[Differences between GitHub and OAuth apps](/apps/differences-between-apps/)" for more details. To learn more about switching from OAuth to {% data variables.product.prodname_github_apps %}, see [Migrating OAuth Apps to {% data variables.product.prodname_github_app %}s](/apps/migrating-oauth-apps-to-github-apps/). +{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_app %}s to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. -#### Unverified Apps +### Publishing an app to {% data variables.product.prodname_marketplace %} -Unverified apps do not need to meet the "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)" or go through the "[Security review process](/marketplace/getting-started/security-review-process/)". +When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: -{% data reusables.marketplace.unverified-apps %} Having a published paid plan will prevent you from being able to submit an unverified app. You must remove paid plans or keep them in draft mode before publishing an unverified app. +1. Review your app carefully to ensure that it will behave as expected in other repositories and that it follows best practice guidelines. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)." -To list your unverified app in {% data variables.product.prodname_marketplace %}, you only need to create a "[Listing on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)" and submit it as an unverified listing. +1. Add webhook events to the app to track user billing requests. For more information about the {% data variables.product.prodname_marketplace %} API, webhook events, and billing requests, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.launch-with-free %} +1. Create a draft {% data variables.product.prodname_marketplace %} listing. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -#### Verified Apps +1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -If you've already built an app and you're interested in submitting a verified listing in {% data variables.product.prodname_marketplace %}, start here: +1. Check whether your app meets the requirements for listing on {% data variables.product.prodname_marketplace %} as a free or a paid app. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." -1. [Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)
      Learn about requirements, guidelines, and the app submission process. +1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -1. [Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)
      Before you can list your app on {% data variables.product.prodname_marketplace %}, you'll need to integrate billing flows using the {% data variables.product.prodname_marketplace %} API and webhook events. +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}, requesting verification if you want to sell the app. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." -1. [Listing on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)
      Create a draft {% data variables.product.prodname_marketplace %} listing, configure webhook settings, and set up pricing plans. +An onboarding expert will contact you with any questions or further steps. For example, if you have added a paid plan, you will need to complete the verification process and complete financial onboarding. As soon as your listing is approved the app is published to {% data variables.product.prodname_marketplace %}. -1. [Selling your app](/marketplace/selling-your-app/)
      Learn about pricing plans, billing cycles, and how to receive payment from {% data variables.product.prodname_dotcom %} for your app. +### Seeing how your app is performing -1. [{% data variables.product.prodname_marketplace %} Insights](/marketplace/github-marketplace-insights/)
      See how your app is performing in {% data variables.product.prodname_marketplace %}. You can use metrics collected by {% data variables.product.prodname_dotcom %} to guide your marketing campaign and be successful in {% data variables.product.prodname_marketplace %}. +You can access metrics and transactions for your listing. Дополнительные сведения см. в: -1. [{% data variables.product.prodname_marketplace %} transactions](/marketplace/github-marketplace-transactions/)
      Download and view transaction data for your {% data variables.product.prodname_marketplace %} listing. - -### Reviewing your app - -We want to make sure that the apps offered on {% data variables.product.prodname_marketplace %} are safe, secure, and well tested. The {% data variables.product.prodname_marketplace %} onboarding specialists will review your app to ensure that it meets all requirements. Follow the guidelines in these articles before submitting your app: - - -* [Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) -* [Security review process](/marketplace/getting-started/security-review-process/) +- "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" +- "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" diff --git a/translations/ru-RU/content/developers/github-marketplace/about-verified-creators.md b/translations/ru-RU/content/developers/github-marketplace/about-verified-creators.md new file mode 100644 index 0000000000..915c221b27 --- /dev/null +++ b/translations/ru-RU/content/developers/github-marketplace/about-verified-creators.md @@ -0,0 +1,43 @@ +--- +title: About verified creators +intro: 'Each organization that wants to sell apps on {% data variables.product.prodname_marketplace %} must follow a verification process. Their identity is checked and their billing process reviewed.' +versions: + free-pro-team: '*' +--- + +### About verified creators + +A verified creator is an organization that {% data variables.product.company_short %} has checked. Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only organizations that are verified by {% data variables.product.company_short %} can sell apps. For more information about organizations, see "[About organizations](/github/setting-up-and-managing-organizations-and-teams/about-organizations)." + +The verification process aims to protect users. For example, it verifies the seller's identity, checks that their {% data variables.product.product_name %} organization is set up securely, and that they can be contacted for support. + +After passing the verification checks, any apps that the organization lists on {% data variables.product.prodname_marketplace %} are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. The organization can now add paid plans to any of their apps. Each app with a paid plan also goes through a financial onboarding process to check that it's set up to handle billing correctly. + +![verified creator badges](/assets/images/marketplace/marketplace_verified_creator_badges_apps.png) + +In addition to the verified creator badge, you'll also see badges for unverified and verified apps. These apps were published using the old method for verifying individual apps. + +![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) + +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." + +### About the verification process + +The first time you request verification for a listing of one of your apps, you will enter the verification process. An onboarding expert will guide you through the process. This includes checking: + +- Profile information - The basic profile information is populated accurately and appropriately. +- Security - The organization has enabled two-factor authentication. +- Verified domain - The organization has verified the domain of the site URL. +- Purchase webhook event - The event is handled correctly by the app. + +When your organization is verified, all your apps are shown with a verified creator badge. You are now able to offer paid plans for any of your apps. + +For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% note %} + +**Note:** This verification process for apps replaces the previous process where individual apps were verified. The current process is similar to the verification process for actions. If you have apps that were verified under the old process, these will not be affected by the changes. The {% data variables.product.prodname_marketplace %} team will contact you with details of how to migrate to organization-based verification. + +{% endnote %} diff --git a/translations/ru-RU/content/developers/github-marketplace/billing-customers.md b/translations/ru-RU/content/developers/github-marketplace/billing-customers.md index fdea7d49a4..f8133baba4 100644 --- a/translations/ru-RU/content/developers/github-marketplace/billing-customers.md +++ b/translations/ru-RU/content/developers/github-marketplace/billing-customers.md @@ -13,17 +13,17 @@ versions: ### Understanding the billing cycle -Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[Webhook events for the {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)." ### Providing billing services in your app's UI -Customers must be able to perform the following actions from your app's website: -- Customers must be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. +Customers should be able to perform the following actions from your app's website: +- Customers should be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. {% data reusables.marketplace.marketplace-billing-ui-requirements %} ### Billing services for upgrades, downgrades, and cancellations -Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)." +Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). @@ -33,7 +33,7 @@ When a customer upgrades their pricing plan or changes their billing cycle from {% data reusables.marketplace.marketplace-failed-purchase-event %} -For information about building upgrade and downgrade workflows into your app, see "[Upgrading and downgrading plans](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)." +For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)." #### Downgrades and cancellations @@ -45,4 +45,4 @@ When a customer cancels a plan, you must: {% data reusables.marketplace.cancellation-clarification %} - Enable them to upgrade the plan through GitHub if they would like to continue the plan at a later time. -For information about building cancellation workflows into your app, see "[Cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)." +For information about building cancellation workflows into your app, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." diff --git a/translations/ru-RU/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md b/translations/ru-RU/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md new file mode 100644 index 0000000000..4107fa4427 --- /dev/null +++ b/translations/ru-RU/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md @@ -0,0 +1,20 @@ +--- +title: Customer experience best practices for apps +intro: 'Guidelines for creating an app that will be easy to use and understand.' +shortTitle: Customer experience best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a good customer experience. + +### Customer communication + +- Marketing materials for the app should accurately represent the app's behavior. +- Apps should include links to user-facing documentation that describe how to set up and use the app. +- Customers should be able to see what type of plan they have in the billing, profile, or account settings section of the app. +- Customers should be able to install and use your app on both a personal account and an organization account. They should be able to view and manage the app on those accounts separately. + +### Plan management + +{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/ru-RU/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/ru-RU/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 7bc6b6e542..52c2c64dc9 100644 --- a/translations/ru-RU/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/ru-RU/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -60,8 +60,8 @@ Once you've created a {% data variables.product.prodname_marketplace %} draft li ### Submitting your app -Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, the {% data variables.product.prodname_marketplace %} onboarding team will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." +Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." ### Removing a {% data variables.product.prodname_marketplace %} listing -If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact [marketplace@github.com](mailto:marketplace@github.com) to remove your listing. +If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing. diff --git a/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index eda04f7c45..a7c7bcf379 100644 --- a/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/ru-RU/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -28,7 +28,7 @@ GitHub then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketp Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins. -If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)." See "[Upgrading and downgrading plans](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)" to find out how to transition a free trial to a paid plan when a free trial expires. +If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." See "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)" to find out how to transition a free trial to a paid plan when a free trial expires. See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload. diff --git a/translations/ru-RU/content/developers/github-marketplace/index.md b/translations/ru-RU/content/developers/github-marketplace/index.md index 13bae303f1..51116f4b8e 100644 --- a/translations/ru-RU/content/developers/github-marketplace/index.md +++ b/translations/ru-RU/content/developers/github-marketplace/index.md @@ -11,8 +11,10 @@ versions: {% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /about-github-marketplace %} + {% link_in_list /about-verified-creators %} {% link_in_list /requirements-for-listing-an-app %} - {% link_in_list /security-review-process-for-submitted-apps %} + {% link_in_list /security-best-practices-for-apps %} + {% link_in_list /customer-experience-best-practices-for-apps %} {% link_in_list /viewing-metrics-for-your-listing %} {% link_in_list /viewing-transactions-for-your-listing %} {% topic_link_in_list /using-the-github-marketplace-api-in-your-app %} @@ -27,7 +29,7 @@ versions: {% link_in_list /writing-a-listing-description-for-your-app %} {% link_in_list /setting-pricing-plans-for-your-listing %} {% link_in_list /configuring-a-webhook-to-notify-you-of-plan-changes %} - {% link_in_list /submitting-your-listing-for-review %} + {% link_in_list /submitting-your-listing-for-publication %} {% topic_link_in_list /selling-your-app-on-github-marketplace %} {% link_in_list /pricing-plans-for-github-marketplace-apps %} {% link_in_list /billing-customers %} diff --git a/translations/ru-RU/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/ru-RU/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md index bb33fe004f..aa9d924b49 100644 --- a/translations/ru-RU/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/ru-RU/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -10,35 +10,45 @@ versions: -{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit, and GitHub lists the price in US dollars. Customers purchase your app using a payment method attached to their {% data variables.product.product_name %} account, without having to leave GitHub.com. You don't have to write code to perform billing transactions, but you will have to handle [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) for purchase events. +{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to verified listings. + +Customers purchase your app using a payment method attached to their {% data variables.product.product_name %} account, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed. For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." -{% note %} - -**Note:** If you're listing an app on {% data variables.product.prodname_marketplace %}, you can't list your app with a free pricing plan if you offer a paid service outside of {% data variables.product.prodname_marketplace %}. - -{% endnote %} +{% data reusables.marketplace.free-plan-note %} ### Types of pricing plans -**Free pricing plans** are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. Unverified free apps do not need to implement any billing flows. Free apps that are verified by Github need to implement billing flows for new purchases and cancellations, but do not need to implement billing flows for free trials, upgrades, and downgrades. If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to resubmit the app for review. +#### Free pricing plans -**Flat rate pricing plans** charge a set fee on a monthly and yearly basis. +{% data reusables.marketplace.free-apps-encouraged %} -**Per-unit pricing plans** charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). +Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. -**Marketplace free trials** provide 14-day free trials of OAuth or GitHub Apps to customers. When you [set up a Marketplace pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/), you can select the option to provide a free trial for flat-rate or per-unit pricing plans. +All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding. + +#### Paid pricing plans + +There are two types of paid pricing plan: + +- Flat rate pricing plans charge a set fee on a monthly and yearly basis. + +- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). + +You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans. ### Free trials -Customers can start a free trial for any available paid plan on a Marketplace listing, but will not be able to create more than one free trial for a Marketplace product. +Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product. Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel. -See "[New purchases and free trials](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for details on how to handle free trials in your app. +For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)." {% note %} diff --git a/translations/ru-RU/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/ru-RU/content/developers/github-marketplace/requirements-for-listing-an-app.md index fd6c08763e..2ae24c334e 100644 --- a/translations/ru-RU/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/ru-RU/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- title: Requirements for listing an app -intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before our {% data variables.product.prodname_marketplace %} onboarding specialists will approve the listing.' +intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ @@ -12,49 +12,62 @@ versions: free-pro-team: '*' --- + +The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app. -Before you submit your app for review, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." You'll accept the terms within your [draft listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) on {% data variables.product.product_name %}. Once you've submitted your app, one of the {% data variables.product.prodname_marketplace %} onboarding specialists will reach out to you with more information about the onboarding process, and review your app to ensure it meets these requirements: +### Requirements for all {% data variables.product.prodname_marketplace %} listings -### User experience +All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -- {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. -- {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. +#### User experience requirements for all apps + +All listings should meet the following requirements, regardless of whether they are for a free or paid app. + +- Listings must not actively persuade users away from {% data variables.product.product_name %}. +- Listings must include valid contact information for the publisher. +- Listings must have a relevant description of the application. +- Listings must specify a pricing plan. - Apps must provide value to customers and integrate with the platform in some way beyond authentication. - Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only. -- Apps cannot actively persuade users away from {% data variables.product.product_name %}. -- Marketing materials for the app must accurately represent the app's behavior. -- Apps must include links to user-facing documentation that describe how to set up and use the app. -- When a customer purchases an app and GitHub redirects them to the app's installation URL, the app must begin the OAuth flow immediately. For details, see "[Handling new purchases and free trials](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/#step-3-authorization)." +- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -- Customers must be able to install your app and select repositories on both a personal and organization account. They should be able to view and manage those accounts separately. +For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)." -### Brand and listing +#### Brand and listing requirements for all apps -- Apps that use GitHub logos must follow the "[{% data variables.product.product_name %} Logos and Usage](https://github.com/logos)" guidelines. +- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)." - Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." - Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." -### Безопасность +To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)." -Apps will go through a security review before being listed on {% data variables.product.prodname_marketplace %}. A successful review will meet the requirements and follow the security best practices listed in "[Security review process](/marketplace/getting-started/security-review-process/)." For information on the review process, contact [marketplace@github.com](mailto:marketplace@github.com). +### Considerations for free apps -### Billing flows +{% data reusables.marketplace.free-apps-encouraged %} -Your app must integrate [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) using the [{% data variables.product.prodname_marketplace %} webhook event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). +### Requirements for paid apps -#### Free apps +In addition to the requirements for all apps above, each app that you offer as a paid service on {% data variables.product.prodname_marketplace %} must also meet the following requirements: -{% data reusables.marketplace.free-apps-encouraged %} If you are listing a free app, you'll need to meet these requirements: +- {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. +- {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. +- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. +- Publishing organizations must have a verified domain and must enable two-factor authentication. 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.") -- Customers must be able to see that they have a free plan in the billing, profile, or account settings section of the app. -- When a customer cancels your app, you must follow the flow for [cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/). +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the listing. -#### Paid apps +{% note %} -To offer your app as a paid service, you'll need to meet these requirements to list your app on {% data variables.product.prodname_marketplace %}: +The verification process is open to organizations. {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% endnote %} + +### Billing requirements for paid apps + +Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their {% data variables.product.product_name %} account. -- To sell your app in {% data variables.product.prodname_marketplace %}, it must use GitHub's billing system. Your app does not need to handle payments but does need to use "[{% data variables.product.prodname_marketplace %} purchase events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" to manage new purchases, upgrades, downgrades, cancellations, and free trials. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" to learn about how to integrate these events into your app. Using GitHub's billing system allows customers to purchase an app without leaving GitHub and pay for the service with the payment method already attached to their {% data variables.product.product_name %} account. - Apps must support both monthly and annual billing for paid subscriptions purchases. - Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." -{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/ru-RU/content/developers/github-marketplace/security-best-practices-for-apps.md b/translations/ru-RU/content/developers/github-marketplace/security-best-practices-for-apps.md new file mode 100644 index 0000000000..eaec8c6874 --- /dev/null +++ b/translations/ru-RU/content/developers/github-marketplace/security-best-practices-for-apps.md @@ -0,0 +1,59 @@ +--- +title: Security best practices for apps +intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.' +redirect_from: + - /apps/marketplace/getting-started/security-review-process/ + - /marketplace/getting-started/security-review-process + - /developers/github-marketplace/security-review-process-for-submitted-apps +shortTitle: Security best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a secure user experience. + +### Authorization, authentication, and access control + +We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details. +- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia. +- Apps should provide customers with a way to delete their account, without having to email or call a support person. +- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately. +- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code. +- Apps should not share service accounts such as email or database services to manage your SaaS service. +- All services used in your app should have unique login and password credentials. +- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties. +- Apps should not use personal access tokens to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps): + - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/). + - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). + +### Data protection + +- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git. +- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). +- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub. +- Apps should not require the user to provide their GitHub password. +- Apps should encrypt tokens, client IDs, and client secrets. + +### Logging and monitoring + +Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year. A security log should include: + +- Authentication and authorization events +- Service configuration changes +- Object reads and writes +- All user and group permission changes +- Elevation of role to admin +- Consistent timestamping for each event +- Source users, IP addresses, and/or hostnames for all logged actions + +### Incident response workflow + +To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident. + +For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template. + +### Vulnerability management and patching workflow + +You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. + +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)." diff --git a/translations/ru-RU/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/ru-RU/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 205978a5f6..9ab919817d 100644 --- a/translations/ru-RU/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/ru-RU/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -1,6 +1,6 @@ --- title: Setting pricing plans for your listing -intro: 'When [listing your app on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/), you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' +intro: 'When you list your app on {% data variables.product.prodname_marketplace %}, you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' redirect_from: - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ @@ -17,57 +17,52 @@ versions: free-pro-team: '*' --- +### About setting pricing plans +If you want to sell an app on {% data variables.product.prodname_marketplace %}, you need to request verification when you publish the listing for your app. During the verification process, an onboarding expert checks the organization's identity and security settings. The onboarding expert will also take the organization through financial onboarding. For more information, see: "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." + +{% data variables.product.prodname_marketplace %} offers several different types of pricing plan. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." + +### About saving pricing plans + +You can save pricing plans in a draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish a pricing plan on a published listing, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. + +For guidelines on billing customers, see "[Billing customers](/developers/github-marketplace/billing-customers)." ### Creating pricing plans -To learn about the types of pricing plans that {% data variables.product.prodname_marketplace %} offers, see "[{% data variables.product.prodname_marketplace %} Pricing Plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." You'll also find helpful billing guidelines in "[Selling your app](/marketplace/selling-your-app/)." - -Pricing plans can be in the draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published listing will function the same way as draft listings until your app is approved and listed on {% data variables.product.prodname_marketplace %}. Draft listings allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish the pricing plan, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. - -To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). If you haven't created a {% data variables.product.prodname_marketplace %} listing yet, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how. +To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). For more information, see "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)." When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan: -#### Plan name +- **Plan name** - Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align with the plan's resources, the size of the company that will use the plan, or anything you'd like. -Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align to the plan's resources, the size of the company that will use the plan, or anything you'd like. +- **Pricing models** - There are three types of pricing plan: free, flat-rate, and per-unit. All plans require you to process new purchase and cancellation events from the marketplace API. In addition, for paid plans: -#### Pricing models + - You must set a price for both monthly and yearly subscriptions in US dollars. + - Your app must process plan change events. + - You must request verification to publish a listing with a paid plan. + - {% data reusables.marketplace.marketplace-pricing-free-trials %} -##### Free plans + For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.free-apps-encouraged %} A free plan still requires you to handle [new purchase](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/) and [cancellation](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/) billing flows. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" for more details. +- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. -##### Flat-rate plans +- **Short description** - Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. -Flat-rate pricing plans allow you to offer your service to customers for a flat-rate fee. {% data reusables.marketplace.marketplace-pricing-free-trials %} +- **Bullets** - You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. -You must set a price for both monthly and yearly subscriptions in U.S. Dollars for flat-rate plans. - -##### Per-unit plans - -Per-unit pricing allows you to offer your app in units. For example, a unit can be a person, seat, or user. You'll need to provide a name for the unit and set a price for both monthly and yearly subscriptions, in U.S. Dollars. - -#### Available for - -{% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. - -#### Short description - -Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. - -#### Bullets - -You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. +{% data reusables.marketplace.free-plan-note %} ### Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan -If a pricing plan for your {% data variables.product.prodname_marketplace %} plan is no longer needed or if you need to adjust pricing details, you can remove it. +If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it. ![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png) -Once you publish a pricing plan for an app already listed in the {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." +Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan and create a new plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription. diff --git a/translations/ru-RU/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/ru-RU/content/developers/github-marketplace/submitting-your-listing-for-publication.md new file mode 100644 index 0000000000..b25c4580ae --- /dev/null +++ b/translations/ru-RU/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -0,0 +1,37 @@ +--- +title: Submitting your listing for publication +intro: 'You can submit your listing for the {% data variables.product.prodname_dotcom %} community to use.' +redirect_from: + - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review + - /developers/github-marketplace/submitting-your-listing-for-review +versions: + free-pro-team: '*' +--- + + + +Once you've completed the listing for your app, you'll see two buttons that allow you to request publication of the listing with or without verification. The **Request** button for "Publish without verification" is disabled if you have published any paid pricing plans in the listing. + +![Unverified and verified request button](/assets/images/marketplace/marketplace-request-button.png) + +{% data reusables.marketplace.launch-with-free %} + +After you submit your listing for review, an onboarding expert will reach out to you with additional information. + +For an overview of the process for creating and submitting a listing, see "[About {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)." + +### Prerequisites for publishing with verification + +Before you request verification of your listing, you'll need to integrate the {% data variables.product.prodname_marketplace %} billing flows and webhook into your app. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." + +If you've met the requirements for listing and you've integrated with the {% data variables.product.prodname_marketplace %} API, go ahead and submit your listing. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to do this, see: "[Transferring an app to an organization before you submit](#transferring-an-app-to-an-organization-before-you-submit)" below. + +### Transferring an app to an organization before you submit + +You cannot sell an app that's owned by a user account. You need to transfer the app to an organization that is already a verified creator, or that can request verification for a listing for the app. For details, see: + +1. "[Creating an organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)" + +1. "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)" diff --git a/translations/ru-RU/content/developers/github-marketplace/testing-your-app.md b/translations/ru-RU/content/developers/github-marketplace/testing-your-app.md index 09e79b1a7a..577b6d624a 100644 --- a/translations/ru-RU/content/developers/github-marketplace/testing-your-app.md +++ b/translations/ru-RU/content/developers/github-marketplace/testing-your-app.md @@ -1,6 +1,6 @@ --- title: Testing your app -intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before the {% data variables.product.prodname_marketplace %} onboarding team approves your app, it must adequately handle the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows).' +intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.' redirect_from: - /apps/marketplace/testing-apps-apis-and-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ @@ -13,7 +13,7 @@ versions: ### Testing apps -You can use a [draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) to simulate each of the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows). A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. +You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." #### Using a development app with a draft listing to test changes diff --git a/translations/ru-RU/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/ru-RU/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index c507787cdb..84f77537a2 100644 --- a/translations/ru-RU/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/ru-RU/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -1,6 +1,6 @@ --- title: Webhook events for the GitHub Marketplace API -intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan. For details on how to respond to each of these types of events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)."' +intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.' redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ diff --git a/translations/ru-RU/content/developers/overview/about-githubs-apis.md b/translations/ru-RU/content/developers/overview/about-githubs-apis.md index 0d647b78cb..e60baa72e3 100644 --- a/translations/ru-RU/content/developers/overview/about-githubs-apis.md +++ b/translations/ru-RU/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,7 @@ versions: github-ae: '*' --- -There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). - -When using the REST API, we encourage you to [request v3 via the `Accept` header](/rest/overview/media-types#request-specific-version). - -For information on using the GraphQL API, see the [v4 docs](/graphql). +There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). For information on using the GraphQL API, see the [v4 docs](/graphql). ## Deprecated versions diff --git a/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md b/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md index 25924a8d36..76ba712dae 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/webhook-events-and-payloads.md @@ -145,7 +145,7 @@ Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. {{ webhookPayloadsForCurrentVersion.check_suite.completed }} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### code_scanning_alert {% data reusables.webhooks.code_scanning_alert_event_short_desc %} @@ -445,7 +445,7 @@ When someone revokes their authorization of a {% data variables.product.prodname #### Webhook payload object {% data reusables.webhooks.installation_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Webhook payload example @@ -469,7 +469,7 @@ When someone revokes their authorization of a {% data variables.product.prodname #### Webhook payload object {% data reusables.webhooks.installation_repositories_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Webhook payload example @@ -1047,7 +1047,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends | Клавиша | Тип | Description | | ---------- | -------- | --------------------------------------------------------------------------- | -| `действие` | `строка` | The action that was performed. This can be one of:
      • `created` - A repository is created.
      • `deleted` - A repository is deleted. This event type is only available to [organization hooks](/v3/orgs/hooks/)
      • `archived` - A repository is archived.
      • `unarchived` - A repository is unarchived.
        • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
      • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/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.
      | +| `действие` | `строка` | 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.
      | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1100,6 +1100,31 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### secret_scanning_alert + +{% data reusables.webhooks.secret_scanning_alert_event_short_desc %} + +#### Availability + +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_app %}s with the `secret_scanning_alerts:read` permission + +#### Webhook payload object + +{% 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. + +#### Webhook payload example + +{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} +{% endif %} + ### 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/)." 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 new file mode 100644 index 0000000000..0c6777352f --- /dev/null +++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -0,0 +1,54 @@ +--- +title: About discussions +intro: Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About discussions + +With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools. + +- Share announcements and information, gather feedback, plan, and make decisions +- Ask questions, discuss and answer the questions, and mark the discussions as answered +- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows + +![Discussions tab for a repository](/assets/images/help/discussions/hero.png) + +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)." + +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)." + +### About categories and formats for discussions + +{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %} + +For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %} + +For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +### Best practices for discussions + +As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)." + +Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." + +### Sharing feedback + +You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). + +### Дополнительная литература + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" +- "[Moderating comments and conversations](/github/building-a-strong-community/moderating-comments-and-conversations)" +- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md new file mode 100644 index 0000000000..63406ba46b --- /dev/null +++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -0,0 +1,48 @@ +--- +title: Collaborating with maintainers using discussions +shortTitle: Collaborating with maintainers +intro: You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion. +permissions: People with read permissions to a repository can start and participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About collaboration with maintainers using discussions + +{% data reusables.discussions.about-discussions %} If you use or contribute to a project, you can start a discussion to make suggestions and engage with maintainers and community members about your plans, questions, ideas, and feedback. For more information, see "[‎About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +{% data reusables.discussions.about-categories-and-formats %} Repository administrators and project maintainers can delete a discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)." + +{% data reusables.discussions.github-recognizes-members %} These members appear in a list of the most helpful contributors to the project's discussions. As your project grows, you can grant higher access permissions to active members of your community. For more information, see "[Granting higher permissions to top contributors](/discussions/guides/granting-higher-permissions-to-top-contributors)" + +![Most helpful contributors to discussions for a project](/assets/images/help/discussions/most-helpful.png) + +For more information about participation in discussions, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +### Требования + +To collaborate with maintainers using discussions, a repository administrator or project maintainer must enable discussions for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Starting a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Filtering the list of discussions + +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the **Search all discussions** field, type a search query. Optionally, to the right of the search field, click a button to further filter the results. ![Search bar and buttons for filtering discussions](/assets/images/help/discussions/search-and-filter-controls.png) +1. In the list of discussions, click the discussion you want to view. ![Discussion search results](/assets/images/help/discussions/search-result.png) + +### Converting an issue to a discussion + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)." + +### Дополнительная литература + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" diff --git a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/index.md new file mode 100644 index 0000000000..44aed03c8b --- /dev/null +++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/index.md @@ -0,0 +1,14 @@ +--- +title: Collaborating with your community using discussions +shortTitle: Collaborating using discussions +intro: Gather and discuss your project with community members and other maintainers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /about-discussions %} +{% link_in_list /participating-in-a-discussion %} +{% link_in_list /collaborating-with-maintainers-using-discussions %} + diff --git a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md new file mode 100644 index 0000000000..f22f877dc5 --- /dev/null +++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -0,0 +1,31 @@ +--- +title: Participating in a discussion +intro: You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}. +permissions: People with read permissions to a repository can participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About participation in a discussion + +{% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)." + +You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)." + +### Требования + +Discussions must be enabled for the repository for you to participate in a discussion in the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Creating a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Marking a comment as an answer + +Discussion authors and users with the triage role or greater for a repository can mark a comment as the answer to a discussion in the repository. + +{% data reusables.discussions.marking-a-comment-as-an-answer %} 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 new file mode 100644 index 0000000000..5694c548e1 --- /dev/null +++ b/translations/ru-RU/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -0,0 +1,49 @@ +--- +title: Best practices for community conversations on GitHub +shortTitle: Best practices for community conversations +intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to a discussion when you are ready to scope out the work.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Community conversations in {% data variables.product.prodname_discussions %} + +Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository and gather diverse feedback and ideas more quickly. You can help drive a productive conversation by: + +- Asking pointed questions and follow-up questions to garner specific feedback +- Capture a diverse experience and distill it down to main points +- Open an issue to take action based on the conversation, where applicable + +For more information about opening an issue and cross-referencing a discussion, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." + +### Learning about conversations on GitHub + +You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have. + +You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and spike out a project's specific details before committing it to an issue, which can then be scoped. Discussions are useful for teams if: +- You are in the discovery phase of a project and are still learning which director your team wants to go in +- You want to collect feedback from a wider community about a project +- You want to keep bug fixes, feature requests, and general conversations separate + +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](/articles/about-team-discussions)." + +### Following contributing guidelines + +Before you open a discussion, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project. + +For more information, see "[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Дальнейшие шаги + +To continue learning about {% data variables.product.prodname_discussions %} and quickly create a discussion for your community, see "[Quickstart for {% data variables.product.prodname_discussions %}](/discussions/quickstart)." + +### Дополнительная литература + +- "[Setting up your project for healthy contributions](/articles/setting-up-your-project-for-healthy-contributions)" +- "[Using templates to encourage useful issues and pull requests](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[Moderating comments and conversations](/articles/moderating-comments-and-conversations)" +- "[Writing on {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)" diff --git a/translations/ru-RU/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/ru-RU/content/discussions/guides/finding-discussions-across-multiple-repositories.md new file mode 100644 index 0000000000..c16dc05bb0 --- /dev/null +++ b/translations/ru-RU/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -0,0 +1,20 @@ +--- +title: Finding discussions across multiple repositories +intro: 'You can easily access every discussion you''ve created or participated in across multiple repositories.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Finding discussions + +1. Navigate to {% data variables.product.prodname_dotcom_the_website %}. +1. In the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your discussions**. !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. + +### Дополнительная литература + +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" 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 new file mode 100644 index 0000000000..8ded0aaa3a --- /dev/null +++ b/translations/ru-RU/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -0,0 +1,32 @@ +--- +title: Granting higher permissions to top contributors +intro: 'Repository administrators can promote any community member to a moderator and maintainer.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Introduction + +The most helpful contributors for the past 30 days are highlighted on the {% data variables.product.prodname_discussions %} dashboard, based on how many comments were marked as answers by other community members. Helpful contributors can help drive a healthy community and moderate and guide the community space in addition to maintainers. + +### Step 1: Audit your discussions top contributors + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Compare the list of contributors with their access permissions to see who qualifies to moderate the discussion. + +### Step 2: Review permission levels for discussions + +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)." + +### Step 3: Change permissions levels for top contributors + +You can change a contributor's permission levels to give them more access to the tooling they need to moderate GitHub Discussions. To change a person's or team's permission levels, see "[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)." + +### Step 4: Notify community members of elevated access + +When you change a collaborators permission level, they will receive a notification for the change. diff --git a/translations/ru-RU/content/discussions/guides/index.md b/translations/ru-RU/content/discussions/guides/index.md new file mode 100644 index 0000000000..b40ee4c730 --- /dev/null +++ b/translations/ru-RU/content/discussions/guides/index.md @@ -0,0 +1,31 @@ +--- +title: Discussions guides +shortTitle: Руководства +intro: 'Discover pathways to get started or learn best practices for participating or monitoring your community''s discussions.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Getting started with discussions + +{% link_in_list /about-discussions %} +{% link_in_list /best-practices-for-community-conversations-on-github %} +{% link_in_list /finding-discussions-across-multiple-repositories %} + +### Administering discussions + +{% link_in_list /granting-higher-permissions-to-top-contributors %} + + + + + diff --git a/translations/ru-RU/content/discussions/index.md b/translations/ru-RU/content/discussions/index.md new file mode 100644 index 0000000000..66dca4f270 --- /dev/null +++ b/translations/ru-RU/content/discussions/index.md @@ -0,0 +1,55 @@ +--- +title: GitHub Discussions Documentation +beta_product: true +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.' +introLinks: + quickstart: /discussions/quickstart +featuredLinks: + guides: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + gettingStarted: + - /discussions/quickstart + guideCards: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + popular: + - /discussions/guides/granting-higher-permissions-to-top-contributors + - /discussions/guides/best-practices-for-community-conversations-on-github + - /discussions/guides/finding-discussions-across-multiple-repositories + - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions + - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository +product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +layout: product-landing +versions: + free-pro-team: '*' +--- + + + + + + + +{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} +{% if discussionsCommunityExamples %} +
      +

      Communities using discussions

      + +
      + {% 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" %} +
      +
      +{% endif %} diff --git a/translations/ru-RU/content/discussions/managing-discussions-for-your-community/index.md b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/index.md new file mode 100644 index 0000000000..8ccb2875b2 --- /dev/null +++ b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/index.md @@ -0,0 +1,13 @@ +--- +title: Managing discussions for your community +shortTitle: Managing discussions +intro: 'You can enable and configure discussions for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /managing-discussions-in-your-repository %} +{% link_in_list /managing-categories-for-discussions-in-your-repository %} +{% link_in_list /moderating-discussions %} diff --git a/translations/ru-RU/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md new file mode 100644 index 0000000000..cca80f5388 --- /dev/null +++ b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md @@ -0,0 +1,56 @@ +--- +title: Managing categories for discussions in your repository +intro: You can categorize the discussions in your repository to organize conversations for your community members, and you can choose a format for each category. +permissions: Repository administrators and people with write or greater access to a repository can enable discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About categories for discussions + +{% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} + +Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations.{% data reusables.discussions.repository-category-limit %} + +For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +### Default categories + +| Категория | Purpose | Тип | +|:--------------- |:-------------------------------------------------------------------- |:--------------------- | +| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion | +| 💡Ideas | Ideas to change or improve the project | Open-ended discussion | +| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer | +| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion | + +### Creating a category + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.edit-categories %} +1. Click **New category**. !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png) +1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png) +1. Click **Create**. !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png) + +### Editing a category + +You can edit a category to change the category's emoji, title, description, and discussion format. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} +![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png) +1. Click **Save changes**. !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +### Deleting a category + +When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png) +1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png) +1. Click **Delete & Move**. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png) 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 new file mode 100644 index 0000000000..4c14476019 --- /dev/null +++ b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -0,0 +1,94 @@ +--- +title: Managing discussions in your repository +intro: You can categorize, spotlight, transfer, or delete the discussions in a repository. +permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About management of discussions + +{% 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)." + +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](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)." + +For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/github/building-a-strong-community/moderating-comments-and-conversations)." + +### Требования + +To manage discussions in a repository, discussions must be enabled for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Changing the category for a discussion + +You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" article. + +You can also move a discussion to a different category. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) + +### Pinning a discussion + +You can pin up to four important discussions above the list of discussions for the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png) +1. Optionally, customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Editing a pinned discussion + +Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Unpinning a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) +1. Read the warning, then click **Unpin discussion**. !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png) + +### Transferring a discussion + +To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png) +1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Click **Transfer discussion**. !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png) + +### Deleting a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png) +1. Read the warning, then click **Delete this discussion**. !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) + +### Converting issues based on labels + +You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Next to the label you want to convert to issues, click **Convert issues**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/ru-RU/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/moderating-discussions.md new file mode 100644 index 0000000000..2c91d32d89 --- /dev/null +++ b/translations/ru-RU/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -0,0 +1,39 @@ +--- +title: Moderating discussions +intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, and converting issues to discussions. and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct to discussions.' +permissions: People with triage access to a repository can moderate discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About moderating discussions + +{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you 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. + +### Marking a comment as an answer + +{% data reusables.discussions.marking-a-comment-as-an-answer %} + +### Locking discussions + +It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository will still be able to comment on the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the discussion you want to lock. ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the right margin of a discussion, click **Lock conversation**. +1. Read the information about locking conversations and click **Lock conversation on this discussion**. +1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**. + +### Converting an issue to a discussion + +When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository can bulk convert issues based on labels. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to convert. +1. In the right margin of an issue, click **Convert to discussion**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/ru-RU/content/discussions/quickstart.md b/translations/ru-RU/content/discussions/quickstart.md new file mode 100644 index 0000000000..1213fb53fe --- /dev/null +++ b/translations/ru-RU/content/discussions/quickstart.md @@ -0,0 +1,58 @@ +--- +title: Quickstart for GitHub Discussions +intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository and start conversations with your community.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Introduction + +{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike issues. Discussions enable fluid, open conversation in a public forum. + +Discussions give a space for more collaborative conversations by connecting and giving a more centralized area to connect and find information. + +### Enabling {% data variables.product.prodname_discussions %} on your repository + +Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public repositories. + +When you first enable a {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. + +{% data reusables.repositories.navigate-to-repo %} +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. ![Public settings button](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", click **Set up discussions**. ![Set up a discussion button under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png) +1. Under "Start a new discussion," edit the template to align with the resources and tone you want to set for your community. +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) + +### Welcoming contributions to your discussions + +You can welcome your community and introduce a new way to communicate in a repository by creating a welcome post and pin the post to your {% data variables.product.prodname_discussions %} page. Pinning and locking discussions helps people know that a post is meant as an announcement. You can use announcements as a way to link people to more resources and offer guidance for opening discussions in your community. For more information about pinning a discussion, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + + +### Setting up community guidelines for contributors + +You can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. You can also update the repository's README to communicate expectations on when collaborators should open an issue or discussion. + +For more information about providing guidelines for your project, see "[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and "[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Creating a new discussion + +Anyone with access to a repository can create a discussion. + +{% data reusables.discussions.starting-a-discussion %} + +### Organizing discussions into relevant categories + +Repository owners and people with write access can create new categories to keep discussions organized. Collaborators participating and creating new discussions can group discussions into the most relevant existing categories. Discussions can also be recategorized after they are created. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" + +### Promoting healthy conversations + +People with write permissions for a repository can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +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)." + +### Дальнейшие шаги + +Once there is a clear path to scope work out and move an idea from concept to reality, you can create an issue and start tracking your progress. For more information on creating an issue from a discussion, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." diff --git a/translations/ru-RU/content/education/guides.md b/translations/ru-RU/content/education/guides.md new file mode 100644 index 0000000000..0265b53633 --- /dev/null +++ b/translations/ru-RU/content/education/guides.md @@ -0,0 +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 +versions: + free-pro-team: '*' +--- + +### Get started with {% 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. + +- [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/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) + +### Run a software development course with {% 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 %}. + +- [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) + +### Learn to develop software + +Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. + +- [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/teach-and-learn-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) + +### Contribute to the community + +Participate in the community, get training from {% data variables.product.company_short %}, and learn or teach new skills. + +- [{% data variables.product.prodname_education_community %}](https://education.github.community) +- [About Campus Experts](/education/teach-and-learn-with-github-education/about-campus-experts) +- [About Campus Advisors](/education/teach-and-learn-with-github-education/about-campus-advisors) diff --git a/translations/ru-RU/content/education/index.md b/translations/ru-RU/content/education/index.md new file mode 100644 index 0000000000..c3827df288 --- /dev/null +++ b/translations/ru-RU/content/education/index.md @@ -0,0 +1,45 @@ +--- +title: GitHub Education Documentation +shortTitle: Education +intro: "{% data variables.product.prodname_education %} helps you teach or learn software development with the tools and support of {% data variables.product.company_short %}'s platform and community." +introLinks: + quickstart: /education/quickstart +featuredLinks: + guides: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + guideCards: + - /github/getting-started-with-github/signing-up-for-a-new-github-account + - /github/getting-started-with-github/git-and-github-learning-resources + - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom + popular: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /desktop + - /github/getting-started-with-github/github-cli + - /education/manage-coursework-with-github-classroom/teach-with-github-classroom +changelog: + - + title: 'Try something new at Local Hack Day: Learn' + date: '2020-10-15' + href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ + - + title: 'Remote Education: Creating community through shared experiences' + date: '2020-09-24' + href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ + - + title: 'Remote Education: A series of best practices for online campus communities' + date: '2020-09-10' + href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ + - + title: Welcome to the inaugural class of MLH Fellows + date: '2020-06-24' + href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ +layout: product-landing +versions: + free-pro-team: '*' +--- + + + diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md new file mode 100644 index 0000000000..1695a75530 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -0,0 +1,31 @@ +--- +title: About using MakeCode Arcade with GitHub Classroom +shortTitle: About using MakeCode Arcade +intro: You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-makecode +--- + +### About MakeCode Arcade + +MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade. + +For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. + +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. + +### About submission of assignments with MakeCode Arcade + +By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.product.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen. + +![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) + +### Дополнительная литература + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md new file mode 100644 index 0000000000..2909630974 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: About using Repl.it with GitHub Classroom +shortTitle: About using Repl.it +intro: You can configure Repl.it as the online integrated development environment (IDE) for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-replit +--- + +### About Repl.it + +Repl.it is an online integrated development environment (IDE) that supports multiple programming languages. Students can write, edit, run, test, and debug code in a browser with Repl.it. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. + +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). + +For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. + +### About submission of assignments with Repl.it + +By default, Repl.it is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with Repl.it, students should push changes to {% data variables.product.product_location %} using the version control functionality in the left sidebar. + +![Repl.it version control functionality](/assets/images/help/classroom/ide-replit-version-control-button.png) + +For more information about using Git on Repl.it, see the [Repl.it + Git Tutorial](https://repl.it/talk/learn/Replit-Git-Tutorial/23331) on the Repl.it website. + +### Дополнительная литература + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md new file mode 100644 index 0000000000..86285be4fd --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: Basics of setting up GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %} basics' +intro: Learn how to set up your classroom, manage assignments, and configure time-saving automation. +versions: + free-pro-team: '*' +--- + +### Videos about {% data variables.product.prodname_classroom %} + +You can watch a series of short video tutorials about the configuration and use of {% data variables.product.prodname_classroom %}. To watch all videos as part of a continuous playlist, see the [{% data variables.product.prodname_classroom %} Getting Started Guide](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) on YouTube. + +For more information about terminology for {% data variables.product.prodname_classroom %}, see "[Glossary](/education/manage-coursework-with-github-classroom/glossary)". + +1. Getting started {% octicon "link-external" aria-label="The external link icon" %} +2. Adding your student roster {% octicon "link-external" aria-label="The external link icon" %} +3. Creating assignments + - Creating an assignment using a {% data variables.product.prodname_dotcom %} repository {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Microsoft MakeCode as your online IDE {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Repl.it as your online IDE {% octicon "link-external" aria-label="The external link icon" %} +4. How students complete assignments {% octicon "link-external" aria-label="The external link icon" %} +5. How teachers review assignments {% octicon "link-external" aria-label="The external link icon" %} +6. Creating group assignments {% octicon "link-external" aria-label="The external link icon" %} +7. Next steps to get started {% octicon "link-external" aria-label="The external link icon" %} +8. {% data variables.product.prodname_dotcom %} Teacher Toolbox {% octicon "link-external" aria-label="The external link icon" %} + +### Дальнейшие шаги + +For more information about teaching with {% data variables.product.prodname_classroom %}, see "[Teach with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom)." + +### Дополнительная литература + +- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md new file mode 100644 index 0000000000..747b1e3236 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md @@ -0,0 +1,50 @@ +--- +title: Configure default settings for assignment repositories +shortTitle: Configure defaults for assignment repositories +intro: You can use the Probot Settings app to configure the default settings for repositories that {% data variables.product.prodname_classroom %} creates for an assignment. +permissions: Organization owners can configure default settings for assignment repositories by installing a {% data variables.product.prodname_github_app %} for the organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/probot-settings +--- + +### About configuration of defaults for assignment repositories + +{% data variables.product.prodname_classroom %} creates a repository that belongs for each student or team that accepts an assignment. The repository belongs to the organization that you use for {% data variables.product.prodname_classroom %}. Assignment repositories can be empty, or you can use a template repository. For more information, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} + +With the Probot Settings app, you can create a file named _.github/settings.yml_ in a repository that contains a list of settings for the repository, and then install a {% data variables.product.prodname_github_app %} for your organization that automatically applies the settings to the repository. + +You can include _.github/settings.yml_ in a template repository that you use for an assignment in {% data variables.product.prodname_classroom %}. When an individual or team accepts the assignment, {% data variables.product.prodname_classroom %} creates the assignment repository, and the Settings app automatically applies the settings from _.github/settings.yml_. + +Probot is a a project, framework, and collection of free apps to automate {% data variables.product.product_name %}. A Probot app can listen to repository events, like the creation of new commits, comments, and issues, and automatically respond to the event. + +For more information, see the [Probot website](https://probot.github.io) and the [Settings app website](https://probot.github.io/apps/settings/). For more information about {% data variables.product.prodname_github_apps %}, see "[About apps](/developers/apps/about-apps)." + +### Adding the Settings app to your organization + +After you install the Probot Settings app for your organization, the app will apply the settings that you define in _.github/settings.yml_ for any repository in your organization, including new assignment repositories that {% data variables.product.prodname_classroom %} creates. + +1. Navigate to the [Settings app page](https://github.com/apps/settings). +1. Click **Install**, then click the organization that you use for {% data variables.product.prodname_classroom %}. Provide the app full access to all repositories owned by the organization. ![Installing the Probot Settings app](/assets/images/help/classroom/probot-settings.gif) + +### Configuring default settings for an assignment repository + +1. Create a template repository that contains a _.github/settings.yml_ file. For a complete list of settings, see the [README](https://github.com/probot/settings#github-settings) for the `probot/settings` repository. For more information about using a template repository for starter code in {% data variables.product.prodname_classroom %}, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + + {% warning %} + + **Warning:** Do not define `collaborators` in the _.github/settings.yml_ file for your template repository. {% data variables.product.prodname_classroom %} automatically grants teachers and teaching assistants access to assignment repositories. + + {% endwarning %} + +1. Create an assignment using the template repository containing _.github/settings.yml_ as the starter code. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +The Probot Settings app for your organization will now apply the settings you define in _.github/settings.yml_ within the template repository to every assignment repository that {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} creates for a student or team. + +### Дополнительная литература + +- [Probot apps](https://probot.github.io/apps/) +- [Probot documentation](https://probot.github.io/docs/) diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md new file mode 100644 index 0000000000..acea9a9e03 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -0,0 +1,138 @@ +--- +title: Connect a learning management system to GitHub Classroom +intro: You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom + - /education/manage-coursework-with-github-classroom/connect-to-lms + - /education/manage-coursework-with-github-classroom/generate-lms-credentials + - /education/manage-coursework-with-github-classroom/setup-canvas + - /education/manage-coursework-with-github-classroom/setup-generic-lms + - /education/manage-coursework-with-github-classroom/setup-moodle +--- + +### About configuration of your LMS + +You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS. + +### Требования + +To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)." + +### Supported LMSes + +{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards. + +- LTI version 1.0 and/or 1.1 +- LTI Names and Roles Provisioning 1.X + +Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website. + +{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. + +- Canvas +- Google Classroom +- Moodle +- Sakai + +Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace + +### Generating configuration credentials for your classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster. + - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)." +1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**. ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. Read about connecting your LMS, then click **Connect to _LMS_**. +1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom. ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png) + +### Configuring a generic LMS + +You must configure the privacy settings for your LMS to allow external tools to receive roster information. + +1. Navigate to your LMS. +1. Configure an external tool. +1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}. + - Consumer key + - Shared secret + - Launch URL (sometimes called "tool URL" or similar) + +### Configuring Canvas + +You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). + +1. Sign into [Canvas](https://www.instructure.com/canvas/#login). +1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}. +1. In the left sidebar, click **Settings**. +1. Click the **Apps** tab. +1. Click **View app configurations**. +1. Click **+App**. +1. Select the **Configuration Type** drop-down menu, and click **By URL**. +1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Canvas app configuration | Value or setting | + |:------------------------------------------------------------------------- |:------------------------------------------------------------------ | + | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} + | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled | + | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} + + {% note %} + + **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website. + + {% endnote %} + +1. Click **Submit**. +1. In the left sidebar, click **Home**. +1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}. + +### Configuring Moodle + +You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org). + +You must be using Moodle version 3.0 or greater. + +1. Sign into [Moodle](https://moodle.org/login/index.php). +1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}. +1. Click **Turn editing on**. +1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**. +1. Choose **External tool** and click **Add**. +1. In the "Activity name" field, type "GitHub Classroom". +1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**. +1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Moodle app configuration | Value or setting | + |:--------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_

      **Note**: You can use any name, but we suggest this value for clarity. | + | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} + | **LTI version** | LTI 1.0/1.1 | + | **Default launch container** | New window | + | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared secret** | Shared secret from {% data variables.product.prodname_classroom %} + +1. Scroll to and click **Services**. +1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**. +1. Scroll to and click **Privacy**. +1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**. +1. At the bottom of the page, click **Save changes**. +1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**. +1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**. +1. At the bottom of the page, click **Save and return to course**. +1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity. + +### Importing a roster from your LMS + +For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + +### Disconnecting your LMS + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Connect to a learning management system (LMS)", click **Connection Settings**. !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**. !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) 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 new file mode 100644 index 0000000000..f0150b6df5 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -0,0 +1,145 @@ +--- +title: Create a group assignment +intro: 'You can create a collaborative assignment for teams of students who participate in your course.' +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/create-group-assignments +--- + +### About group assignments + +{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers. + +When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment. + +{% data reusables.classroom.classroom-creates-group-repositories %} + +{% data reusables.classroom.about-assignments %} + +You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/github/setting-up-and-managing-organizations-and-teams/about-teams)." + +For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### Требования + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Defining teams for an assignment](#defining-teams-for-an-assignment) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +#### Defining teams for an assignment + +If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams. + +{% tip %} + +**Tips**: + +- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course. + +- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members. + +{% endtip %} + +![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png) + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +### Providing feedback + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the team. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
      + Group assignment +
      + +### Дальнейшие шаги + +- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. + +- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### Дополнительная литература + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md new file mode 100644 index 0000000000..a2a6085963 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -0,0 +1,19 @@ +--- +title: Create an assignment from a template repository +intro: You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments +--- + +You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. For more information, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." + +### Дополнительная литература + +- "[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)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md new file mode 100644 index 0000000000..854d759837 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -0,0 +1,124 @@ +--- +title: Create an individual assignment +intro: You can create an assignment for students in your course to complete individually. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment + - /education/manage-coursework-with-github-classroom/create-an-individual-assignment +--- + +### About individual assignments + +{% data reusables.classroom.assignments-individual-definition %} + +{% data reusables.classroom.classroom-creates-individual-repositories %} + +{% data reusables.classroom.about-assignments %} + +For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### Требования + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +### Providing feedback for an assignment + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the student. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
      + Individual assignment +
      + +### Дальнейшие шаги + +- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." + +- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### Дополнительная литература + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md new file mode 100644 index 0000000000..2f73288786 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md @@ -0,0 +1,9 @@ +--- +title: Get started with GitHub Classroom +shortTitle: Начать работу +intro: Learn how to configure and use {% data variables.product.prodname_classroom %} to administer your course. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/glossary.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/glossary.md new file mode 100644 index 0000000000..2a66fdcb3d --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/glossary.md @@ -0,0 +1,52 @@ +--- +title: Глоссарий +intro: You can review explanations of terminology for {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +--- + +### assignment + +An assignment is coursework in {% data variables.product.prodname_classroom %}. A teacher can assign an assignment to an individual student or a group of students. Teachers can import starter code for the assignment, assign students, and create a deadline for each assignment. For more information, see the definitions for "[individual assignment](#individual-assignment)" and "[group assignment](#group-assignment)." + +--- + +### classroom + +A classroom is the basic unit of {% data variables.product.prodname_classroom %}. Teachers can use a classroom to organize and manage students, teaching assistants, and assignments for a single course. A classroom belongs to an organization on {% data variables.product.prodname_dotcom_the_website %}. To administer a classroom, you must be an organization owner for the organization on {% data variables.product.prodname_dotcom %}. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." + +--- + +### {% data variables.product.prodname_classroom %} + +{% data variables.product.prodname_classroom %} is a web application for educators that provides course administration tools integrated with {% data variables.product.prodname_dotcom %}. For more information, see the [{% data variables.product.prodname_classroom %}](https://classroom.github.com/) website. + +--- + +### group assignment + +{% data reusables.classroom.assignments-group-definition %} For more information, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +--- + +### identifier + +An identifier in {% data variables.product.prodname_classroom %} is a unique ID for a student participating in a course. For example, an identifier can be a student name, alphanumeric ID, or email address. + +--- + +### individual assignment + +{% data reusables.classroom.assignments-individual-definition %} For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +--- + +### roster + +A roster allows a teacher to manage students and assignment submissions in a classroom on {% data variables.product.prodname_classroom %}. Teachers can create a roster by entering a list of student identifiers, or by connecting {% data variables.product.prodname_classroom %} to a learning management system (LMS). For more information about identifiers, see the definition of "[identifier](#identifier)." For more information about connecting {% data variables.product.prodname_classroom %} to an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + +--- + +### Дополнительная литература + +- "[{% data variables.product.prodname_dotcom %} glossary](/github/getting-started-with-github/github-glossary)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/index.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/index.md new file mode 100644 index 0000000000..f5a8689fa7 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/index.md @@ -0,0 +1,32 @@ +--- +title: Manage coursework with GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %}' +intro: With {% data variables.product.prodname_classroom %}, you can use {% data variables.product.product_name %} to administer or participate in a course about software development. +versions: + free-pro-team: '*' +--- + +### Table of Contents + +{% topic_link_in_list /get-started-with-github-classroom %} + {% link_in_list /basics-of-setting-up-github-classroom %} + {% link_in_list /glossary %} + +{% topic_link_in_list /teach-with-github-classroom %} + {% link_in_list /manage-classrooms %} + {% link_in_list /create-an-individual-assignment %} + {% link_in_list /create-a-group-assignment %} + {% link_in_list /create-an-assignment-from-a-template-repository %} + {% link_in_list /leave-feedback-with-pull-requests %} + {% link_in_list /use-autograding %} + {% link_in_list /configure-default-settings-for-assignment-repositories %} + {% link_in_list /connect-a-learning-management-system-to-github-classroom %} + +{% topic_link_in_list /integrate-github-classroom-with-an-ide %} + {% link_in_list /integrate-github-classroom-with-an-online-ide %} + {% link_in_list /about-using-makecode-arcade-with-github-classroom %} + {% link_in_list /about-using-replit-with-github-classroom %} + {% link_in_list /run-student-code-in-an-online-ide %} + +{% topic_link_in_list /learn-with-github-classroom %} + {% link_in_list /view-autograding-results %} diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md new file mode 100644 index 0000000000..f4245ea672 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md @@ -0,0 +1,9 @@ +--- +title: Integrate GitHub Classroom with an IDE +shortTitle: Integrate with an IDE +intro: You can help your students write, test, and debug code by preconfiguring a development environment for assignment repositories on {% data variables.product.prodname_classroom %}. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md new file mode 100644 index 0000000000..13d4c3f7da --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md @@ -0,0 +1,42 @@ +--- +title: Integrate GitHub Classroom with an online IDE +shortTitle: Integrate with an online IDE +intro: You can preconfigure a supported online integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/online-ide-integrations +--- + +### About integration with an online IDE + +{% data reusables.classroom.about-online-ides %} + +After a student accepts an assignment with an online IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary. + +![Button for online IDE in README.md for assignment repository](/assets/images/help/classroom/assignment-repository-ide-button-in-readme.png) + +### Supported online IDEs + +{% data variables.product.prodname_classroom %} supports the following online IDEs. You can learn more about the student experience for each IDE. + +| IDE | More information | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | +| Repl.it | "[About using Repl.it with GitHub Classroom](/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom)" | + +### Configuring an online IDE for an assignment + +You can choose the online IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an online IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Authorizing the OAuth app for an online IDE + +The first time you configure an assignment with an online IDE, you must authorize the OAuth app for the online IDE for your organization. + +!["Go grant access" button in popover for authorizing OAuth app for online IDE](/assets/images/help/classroom/assignment-ide-go-grant-access-button.png) + +For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)." + +### Дополнительная литература + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md new file mode 100644 index 0000000000..bca1150346 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Learn with GitHub Classroom +intro: You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md new file mode 100644 index 0000000000..f936e901cd --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md @@ -0,0 +1,31 @@ +--- +title: Leave feedback with pull requests +intro: You can leave feedback for your students in a special pull request within the repository for each assignment. +permissions: People with read permissions to a repository can leave feedback in a pull request for the repository. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github +--- + +### About feedback pull requests for assignments + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +When you enable the pull request for feedback for an assignment, {% data variables.product.prodname_classroom %} will create a special pull request titled **Feedback** in the assignment repository for each student or team. The pull request automatically shows every commit that a student pushed to the assignment repository's default branch. + +### Требования + +To create and access the feedback pull request, you must enable the feedback pull request when you create the assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +### Leaving feedback in a pull request for an assignment + +{% data reusables.classroom.sign-into-github-classroom %} +1. In the list of classrooms, click the classroom with the assignment you want to review. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **Review**. ![Review button for assignment in list of submissions for an assignment](/assets/images/help/classroom/assignments-click-review-button.png) +1. Review the pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)." + +### Дополнительная литература + +- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](http://localhost:4000/en/free-pro-team@latest/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" 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 new file mode 100644 index 0000000000..e72ff05c12 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -0,0 +1,106 @@ +--- +title: Manage classrooms +intro: You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}. +permissions: Organization owners can manage a classroom for an organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/archive-a-classroom +--- + +### About classrooms + +{% data reusables.classroom.about-classrooms %} + +![Classroom](/assets/images/help/classroom/classroom-hero.png) + +### About management of classrooms + +{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. + +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 classrom. 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)." + +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. + +### About classroom rosters + +Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course. + +When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment. + +![Classroom roster](/assets/images/help/classroom/roster-hero.png) + +### Требования + +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 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)." + +### Creating a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **New classroom**. !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png) +{% data reusables.classroom.guide-create-new-classroom %} + +After you create a classroom, you can begin creating assignments for students. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Creating a roster for your classroom + +You can create a roster of the students who participate in your course. + +If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) +1. To create a roster manually, type your student identifiers. Optionally, click **Upload a CSV or text file** to upload a file containing the identifiers. ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png) +1. Click **Create roster**. !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png) + +### Adding students to the roster for your classroom + +Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classrom](#creating-a-roster-for-your-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To the right of "Classroom roster", click **Update students**. !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png) +1. Follow the instructions to add students to the roster. + - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**. ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) + +### Renaming a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Classroom name", type a new name for the classroom. ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png) +1. Click **Rename classroom**. !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png) + +### Archiving or unarchiving a classroom + +You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**. ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png) +1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**. ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) + +### Deleting a roster for a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Under "Delete this roster", click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png) +1. Read the warnings, then click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) + +### Deleting a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) +1. **Read the warnings**. +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md new file mode 100644 index 0000000000..57e3f1e824 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md @@ -0,0 +1,21 @@ +--- +title: Run student code in an online IDE +intro: You can run the code from a student assignment within the online integrated development environment (IDE) that you configured for the assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/running-student-code +--- + +### About student code and online IDEs + +If you configure an online integrated development environment (IDE) for an assignment, you can run the code within the online IDE. You don't need to clone the assignment repository to your computer. + +For more information about online IDEs, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +### Running student code in the online IDE + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **View IDE**. !["View IDE" button for submission using an online IDE](/assets/images/help/classroom/assignments-click-view-ide.png) diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md new file mode 100644 index 0000000000..6e051e9d2d --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Teach with GitHub Classroom +intro: Learn how to set up your classroom and assignments. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/use-autograding.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/use-autograding.md new file mode 100644 index 0000000000..8f273a84d8 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/use-autograding.md @@ -0,0 +1,83 @@ +--- +title: Use autograding +intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers +--- + +### About autograding + +{% data reusables.classroom.about-autograding %} + +After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding. + +You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." + +You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment. + +![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png) + +### Grading methods + +There are two grading methods: input/output tests and run command tests. + +#### Input/output test + +An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result. + +| Setting | Description | +|:------------------- |:------------------------------------------------------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate standard output for evaluation | +| **Inputs** | Standard input for run command | +| **Expected output** | The output that you want to see as standard output from the run command | +| **Comparison** | The type of comparison between the run command's output and the expected output

      • **Included**: Passes when the expected output appears
        anywhere in the standard output from the run command
      • **Exact**: Passes when the expected output is completely identical
        to the standard output from the run command
      • **Regex**: Passes if the regular expression in expected
        output matches against the standard output from the run command
      | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +#### Run command test + +A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure. + +{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`. + +| Setting | Description | +|:----------------- |:------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate an exit code for evaluation | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +### Configuring autograding tests for an assignment + +You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests. + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.assignments-click-pencil %} +1. In the left sidebar, click **Grading and feedback**. !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) +1. Add, edit, or delete an autograding test. + - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png) +1. At the bottom of the page, click **Update assignment**. !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png) + +### Viewing logs from autograding tests + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of a submission, click **View test**. !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png) +1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)." + +### Дополнительная литература + +- [{% data variables.product.prodname_actions %} documentation](/actions) diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/view-autograding-results.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/view-autograding-results.md new file mode 100644 index 0000000000..05e7f79243 --- /dev/null +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/view-autograding-results.md @@ -0,0 +1,30 @@ +--- +title: View autograding results +intro: You can see results from autograding within the repository for your assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students +--- + +### About autograding + +Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.product.product_location %}. + +If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X. + +### Viewing autograding results for an assignment repository + +{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." + +The **Actions** tab shows the full history of test runs. + +!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png) + +You can click a specific test run to review log output, like compilation errors and test failures. + +![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) + +### Дополнительная литература + +- "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/ru-RU/content/education/quickstart.md b/translations/ru-RU/content/education/quickstart.md new file mode 100644 index 0000000000..a56bf9ce6d --- /dev/null +++ b/translations/ru-RU/content/education/quickstart.md @@ -0,0 +1,87 @@ +--- +title: Quickstart for GitHub Educators +intro: In about 15 minutes, teachers can get started with discounts, training, and tools for {% data variables.product.company_short %}, then create a classroom for the students in a software development course using {% data variables.product.prodname_classroom %}. +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +### Introduction + +Educators who teach a course on software development can use discounts, partnerships, training, and tools from {% data variables.product.prodname_education %} to effectively teach relevant skills to students. + +In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}. + +{% tip %} + +**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Applying for a student developer pack](/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack)." + +{% endtip %} + +### Creating accounts on {% data variables.product.product_name %} + +First, you'll need to create a free user account on {% data variables.product.product_name %}. + +{% data reusables.accounts.create-account %} +1. Follow the prompts to create your free user account. + +After you create your user account, create a free organization account. You'll use this organization account to create and manage classrooms {% data variables.product.prodname_classroom %}. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Follow the prompts to create a free organization. + +For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." + +### Applying for an educator discount + +Next, you'll sign up for discounts on services from {% data variables.product.company_short %}. {% data reusables.education.educator-requirements %} + +{% tip %} + +**Tip** In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website. + +{% endtip %} + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Set up {% data variables.product.prodname_classroom %} + +With your user account and organization account, you're ready to get started with {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %} is free to use. You can track and manage assignments, grade work automatically, and provide feedback to your students. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To authorize {% data variables.product.prodname_classroom %} to access your user account on {% data variables.product.prodname_dotcom %}, review the information, then click **Authorize {% data variables.product.prodname_classroom %}**. !["Authorize {% data variables.product.prodname_classroom %}" button for user account](/assets/images/help/classroom/setup-click-authorize-github-classroom.png) +1. Review the information. To authorize {% data variables.product.prodname_classroom %} to access your organization account on {% data variables.product.prodname_dotcom %}, click **Grant**. !["Grant" button for organization](/assets/images/help/classroom/setup-click-grant.png) + + {% tip %} + + **Tip**: If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps#oauth-apps-and-organizations)." + + {% endtip %} + +1. Click **Authorize github**. ![Click "Authorize" button for organization](/assets/images/help/classroom/setup-click-authorize-github.png) + +### Create your classroom + +{% data reusables.classroom.about-classrooms %} + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **Create your first classroom** or **New classroom**. +{% data reusables.classroom.guide-create-new-classroom %} + +### Дальнейшие шаги + +You've created a classroom, and you're ready to enrich your course with {% data variables.product.product_name %} and {% data variables.product.prodname_classroom %}! 🎉 + +- Watch some videos about {% data variables.product.prodname_classroom %}. For more information, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." +- Manage your classrooms and classroom admins, and create a roster of students for your classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." +- Create an assignment for individual students or teams. {% data reusables.classroom.for-more-information-about-assignment-creation %} +- Write and implement automated tests to provide immediate feedback to students directly in assignment repositories. For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." +- Participate in {% data variables.product.prodname_education_community_with_url %}. diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-campus-advisors.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..4bc9c6fd0c --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-campus-advisors.md @@ -0,0 +1,17 @@ +--- +title: About Campus Advisors +intro: 'As an instructor or mentor, learn to use {% data variables.product.prodname_dotcom %} at your school with Campus Advisors training and support.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +Professors, teachers and mentors can use the Campus Advisors online training to master Git and {% data variables.product.prodname_dotcom %} and learn best practices for teaching students with {% data variables.product.prodname_dotcom %}. For more information, see "[Campus Advisors](https://education.github.com/teachers/advisors)." + +{% note %} + +**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 %} diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-campus-experts.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..9bda70a042 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-campus-experts.md @@ -0,0 +1,11 @@ +--- +title: About Campus Experts +intro: 'As a student, learn the skills you need to build your school''s technology community and a real-world portfolio, with {% data variables.product.prodname_dotcom %} Campus Experts training.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +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)." diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..4ed2ace9e2 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,31 @@ +--- +title: About GitHub Education for educators and researchers +intro: '{% data variables.product.prodname_education %} offers a variety of tools to help educators and researchers work more effectively inside and outside of the classroom.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### {% data variables.product.prodname_education %} for educators + +With {% data variables.product.prodname_education %}'s tools and services for educators of all levels, you can: + - Use [{% data variables.product.prodname_classroom %}](https://classroom.github.com) to distribute code, give students feedback, and collect assignments on {% data variables.product.prodname_dotcom %}. + - Join our [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) to discuss current trends in technology education with your peers from around the world. + - Access and adapt our [open source lesson plans](https://education.github.community/t/open-source-lesson-plans/1591) for teaching Git and {% data variables.product.prodname_dotcom %}. + - [Request a {% data variables.product.prodname_dotcom %} swag bag](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) with educational materials and goodies for your students. + {% data reusables.education.apply-for-team %} + +### {% data variables.product.prodname_education %} for researchers + +With {% data variables.product.prodname_education %}'s tools and services for researchers, you can: + - Collaborate with others on your research work around the world on {% data variables.product.prodname_dotcom %}. + - [Learn](https://education.github.com/stories) how academic institutions around the world are using {% data variables.product.prodname_dotcom %} for their research. + {% data reusables.education.apply-for-team %} + +### Дополнительная литература + +- "[About {% data variables.product.prodname_education %} for students](/articles/about-github-education-for-students)" diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..6f0fb965f4 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md @@ -0,0 +1,21 @@ +--- +title: About GitHub Education for students +intro: '{% data variables.product.prodname_education %} offers students real-world experience with free access to various developer tools from {% data variables.product.prodname_dotcom %}''s partners.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +Using {% data variables.product.prodname_dotcom %} for your school projects is a practical way to collaborate with others and build a portfolio that showcases real-world experience. + +{% data reusables.education.about-github-education-link %} + +Everyone with a {% data variables.product.prodname_dotcom %} account can collaborate in unlimited public and private repositories with {% data variables.product.prodname_free_user %}. As a student, you can also apply for the {% data variables.product.prodname_student_pack %}, which offers free access to tools and services used by professional developers. For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +If you're a member of a FIRST robotics club, your mentor can apply for an educator discount so your team can collaborate using {% data variables.product.prodname_team %}, which allows unlimited users and private repositories, for free. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." + +### Дополнительная литература + +- "[About {% data variables.product.prodname_education %} for educators and researchers](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education.md new file mode 100644 index 0000000000..e02c546320 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/about-github-education.md @@ -0,0 +1,23 @@ +--- +title: About GitHub Education +intro: '{% data variables.product.prodname_education %} offers a special free product for schools that want to make the most of {% data variables.product.prodname_dotcom %} for their community and agree to specific program requirements.' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +If your school agrees to meet certain requirements, your secondary school, university, or bootcamp can get {% data variables.product.prodname_education %}, which offers the best of {% data variables.product.prodname_dotcom %} for free, including: +- {% data variables.product.prodname_ghe_cloud %} and/or {% data variables.product.prodname_ghe_server %} +- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our Campus Advisor program +- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %} +- Leadership development and technical training for students with the Campus Experts program + +For more information, see the [official {% data variables.product.prodname_education %}](https://education.github.com/partners/schools) page. + +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)." + +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)." + +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_education %} 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/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..eb64ed7324 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,53 @@ +--- +title: Apply for a student developer pack +intro: 'As a student, you can apply for the {% data variables.product.prodname_student_pack %}, which includes offers and benefits from {% data variables.product.prodname_dotcom %} partners.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### Требования + +To be eligible for the {% data variables.product.prodname_student_pack %}, you must: +- Be currently enrolled in a degree or diploma granting course of study such as a high school, secondary school, college, university, homeschool, or similar educational institution +- Have a verifiable school-issued email address or upload documents that prove your current student status +- Have a [{% data variables.product.prodname_dotcom %} user account](/articles/signing-up-for-a-new-github-account) +- Be at least 13 years old + +Documents that prove your current student status include a picture of your school ID, class schedule, transcript, and affiliation or enrollment verification letter. + +During your tenure as a student, you may be prompted to periodically re-verify your current academic status. + +{% note %} + +**Note:** You cannot transfer academic discounts from one account to another. If you have more than one account you want to apply the discount to, consider [merging](/articles/merging-multiple-user-accounts) your user accounts and [renaming](/articles/changing-your-github-username) the retained account if desired. + +{% endnote %} + +For information about renewing your {% data variables.product.prodname_student_pack %}, see "[Expiration and renewals](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)." + +### Applying for a {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. Under "Which best describes your academic status?", select **Student**. ![Select academic status](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Expiration and renewals + +Once your {% data variables.product.prodname_student_pack %} access expires, you may reapply if you're still eligible, although some of our partner offers cannot renew. Most of the timed offers from our partners start once you set them up. For more information, see the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) page. + +To see when your free access to the {% data variables.product.prodname_student_pack %} expires, visit your account's [billing settings](https://github.com/settings/billing). + +### Дополнительная литература + +- "[Why wasn't my application for a {% data variables.product.prodname_student_pack %} approved?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..faf18ee5b0 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,57 @@ +--- +title: Apply for an educator or researcher discount +intro: 'If you''re an educator or a researcher, you can apply to receive {% data variables.product.prodname_team %} for your organization account for free.' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### About educator and researcher discounts + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### Applying for an educator or researcher discount + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Upgrading your organization + +After your request for an educator or researcher discount has been approved, you can upgrade the organizations you use with your learning community to {% data variables.product.prodname_team %}, which allows unlimited users and private repositories with full features, for free. You can upgrade an existing organization or create a new organization to upgrade. + +#### Upgrading an existing organization + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### Upgrading a new organization + +{% data reusables.education.upgrade-page %} +1. Click {% octicon "plus" aria-label="The plus symbol" %} **Create an organization**. ![Create an organization button](/assets/images/help/education/create-org-button.png) +3. Read the information, then click **Create organization**. ![Create organization button](/assets/images/help/education/create-organization-button.png) +4. Under "Choose your plan", click **Choose {% data variables.product.prodname_free_team %}**. +5. Follow the prompts to create your organization. +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### Дополнительная литература + +- "[Why wasn't my application for an educator or researcher discount approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %} Videos](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/index.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/index.md new file mode 100644 index 0000000000..fa8223b8ed --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Teach and learn +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### Table of Contents + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..6fc2cf9659 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,11 @@ +--- +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 +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..9419a99fef --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,11 @@ +--- +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 +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..fb952f6a09 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,11 @@ +--- +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 +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..ecf21b18dc --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,67 @@ +--- +title: Why wasn't my application for a student developer pack approved? +intro: 'Review common reasons that applications for the {% data variables.product.prodname_student_pack %} are not approved and learn tips for reapplying successfully.' +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved + - /articles/why-was-my-application-for-a-student-developer-pack-denied/ + - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved + - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tip:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unclear academic affiliation documents + +If the image you uploaded doesn't clearly identify your current academic status, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Using an academic email with an unverified domain + +If your academic email address has an unverified domain, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### Using an academic email from a school with lax email policies + +If your school issues email addresses prior to paid student enrollment, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +If you have other questions or concerns about the school domain please ask your school IT staff to contact us. + +### Academic email address already used + +If your academic email address was already used to request a {% data variables.product.prodname_student_pack %} for a different {% data variables.product.prodname_dotcom %} account, you cannot reuse the academic email address to successfully apply for another {% data variables.product.prodname_student_pack %} until that discount expires. + +{% note %} + +**Note:** It is against the {% data variables.product.prodname_dotcom %} [Terms of Service](/articles/github-terms-of-service/#3-account-requirements) to maintain more than one individual account. + +{% endnote %} + +If you have more than one personal user account, you must merge your accounts. To retain the discount, keep the account that was granted the discount. You can rename the retained account and keep your contribution history by adding all your email addresses to the retained account. + +Дополнительные сведения см. в: +- "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)" +- "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)" +- "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account)" + +### 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 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). + +### Дополнительная литература + +- "[How to get the GitHub Student Developer Pack without a student ID](https://github.blog/2019-07-30-how-to-get-the-github-student-developer-pack-without-a-student-id/)" on {% data variables.product.prodname_blog %} +- "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/ru-RU/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/ru-RU/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..82f18e7766 --- /dev/null +++ b/translations/ru-RU/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,45 @@ +--- +title: Why wasn't my application for an educator or researcher discount approved? +intro: Review common reasons that applications for an educator or researcher discount are not approved and learn tips for reapplying successfully. +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**Tip:** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### Unclear proof of affiliation documents + +If the image you uploaded doesn't clearly identify your current employment with a school or university, you must reapply and upload another image of your faculty ID or employment verification letter with clear information. + +{% data reusables.education.pdf-support %} + +### Using an academic email with an unverified domain + +If your academic email address has an unverified domain, we may require further proof of your academic status. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### Using an academic email from a school with lax email policies + +If alumni and retired faculty of your school have lifetime access to school-issued email addresses, we may require further proof of your academic status. {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +If you have other questions or concerns about the school domain, please ask your school IT staff to contact us. + +### Non-student applying for Student Developer Pack + +Educators and researchers are not eligible for the partner offers that come with the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). When you reapply, make sure that you choose **Faculty** to describe your academic status. + +### Дополнительная литература + +- "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md index a49e5c06ec..b792b6c4a3 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -32,14 +32,14 @@ If you've enabled security updates, you'll sometimes see extra pull requests for ### Supported repositories and ecosystems +You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)." + {% note %} -{% data reusables.dependabot.private-dependencies %} +{% 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. See the details in the table below. {% endnote %} -You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for dependency updates](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)." - {% data reusables.dependabot.supported-package-managers %} If your repository already uses an integration for dependency management, you will need to disable this before enabling {% data variables.product.prodname_dependabot %}. For more information, see "[About integrations](/github/customizing-your-github-workflow/about-integrations)." diff --git a/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md b/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md index 25fb6899c0..78fdf8996c 100644 --- a/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/ru-RU/content/github/administering-a-repository/about-secret-scanning.md @@ -36,6 +36,7 @@ When {% data variables.product.prodname_secret_scanning %} detects a set of cred - Databricks - Datadog - Discord +- Doppler - Dropbox - Dynatrace - Finicity @@ -79,6 +80,8 @@ When {% data variables.product.prodname_secret_scanning %} detects a secret in a Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +To monitor results from {% data variables.product.prodname_secret_scanning %} across your private repositories or your organization, you can use the {% data variables.product.prodname_secret_scanning %} API. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)." + {% data variables.product.product_name %} currently scans private repositories for secrets issued by the following service providers. - Adafruit @@ -90,6 +93,7 @@ Repository administrators and organization owners can grant users and team acces - CloudBees CodeShip - Databricks - Discord +- Doppler - Dropbox - Dynatrace - Finicity diff --git a/translations/ru-RU/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/ru-RU/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index c7e69bac77..b230a28cd8 100644 --- a/translations/ru-RU/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/ru-RU/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -302,13 +302,14 @@ updates: - dependency-name: "express" # For Express, ignore all updates for version 4 and 5 versions: ["4.x", "5.x"] - # For Loadash, ignore all updates - - dependency-name: "loadash" + # For Lodash, ignore all updates + - dependency-name: "lodash" ``` {% note %} -{% data variables.product.prodname_dependabot_version_updates %} can't run version updates for any dependencies in manifests containing private git dependencies or private git registries, even if you add the private dependencies to the `ignore` option of your configuration file. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot#supported-repositories-and-ecosystems)." +**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-repositories)" 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/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/ru-RU/content/github/administering-a-repository/enabling-and-disabling-version-updates.md index 5604b5f003..a2732f9641 100644 --- a/translations/ru-RU/content/github/administering-a-repository/enabling-and-disabling-version-updates.md +++ b/translations/ru-RU/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -14,14 +14,10 @@ You enable {% data variables.product.prodname_dependabot_version_updates %} by c {% data reusables.dependabot.initial-updates %} For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)." +{% 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)." + ### Enabling {% data variables.product.prodname_dependabot_version_updates %} -{% note %} - -{% data reusables.dependabot.private-dependencies %} - -{% endnote %} - {% data reusables.dependabot.create-dependabot-yml %} 1. Use `package-ecosystem` to specify the package managers to monitor. 1. For each package manager, use: diff --git a/translations/ru-RU/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/ru-RU/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md new file mode 100644 index 0000000000..1d4ea16307 --- /dev/null +++ b/translations/ru-RU/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -0,0 +1,20 @@ +--- +title: Enabling or disabling GitHub Discussions for a repository +intro: 'You can use discussions in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.' +product: '{% data reusables.gated-features.discussions %}' +permissions: People with admin permissions to a repository can enable discussions for the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Enabling or disabling discussions for your repository + +{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} +1. To disable discussions, under "Features", unselect **Discussions**. + +### Дополнительная литература + +- "[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/github/administering-a-repository/index.md b/translations/ru-RU/content/github/administering-a-repository/index.md index 66c0dfa383..c3d2b35b54 100644 --- a/translations/ru-RU/content/github/administering-a-repository/index.md +++ b/translations/ru-RU/content/github/administering-a-repository/index.md @@ -12,36 +12,25 @@ versions: ### Table of Contents {% topic_link_in_list /managing-repository-settings %} - {% link_in_list /setting-repository-visibility %}{% if currentVersion == "free-pro-team@latest" %} - {% link_in_list /managing-teams-and-people-with-access-to-your-repository %}{% endif %} + {% link_in_list /setting-repository-visibility %} + {% link_in_list /managing-teams-and-people-with-access-to-your-repository %} {% link_in_list /classifying-your-repository-with-topics %} {% link_in_list /customizing-how-changed-files-appear-on-github %} {% link_in_list /about-email-notifications-for-pushes-to-your-repository %} - {% link_in_list /displaying-a-sponsor-button-in-your-repository %} - - {% link_in_list /customizing-your-repositorys-social-media-preview %} - - {% link_in_list /viewing-deployment-activity-for-your-repository %} - {% link_in_list /managing-the-forking-policy-for-your-repository %} - {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository %} - {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %} + {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /enabling-or-disabling-github-discussions-for-a-repository %}{% endif %} {% link_in_list /managing-git-lfs-objects-in-archives-of-your-repository %} {% link_in_list /enabling-anonymous-git-read-access-for-a-repository %} - - {% link_in_list /configuring-autolinks-to-reference-external-resources %} - {% link_in_list /renaming-a-repository %} {% link_in_list /transferring-a-repository %} {% link_in_list /deleting-a-repository %} - {% link_in_list /restoring-a-deleted-repository %} - {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} {% link_in_list /changing-the-default-branch %} @@ -50,9 +39,7 @@ versions: {% link_in_list /about-merge-methods-on-github %} {% link_in_list /configuring-commit-squashing-for-pull-requests %} {% link_in_list /configuring-commit-rebasing-for-pull-requests %} - {% link_in_list /managing-the-automatic-deletion-of-branches %} - {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} {% link_in_list /configuring-protected-branches %} @@ -65,31 +52,22 @@ versions: {% link_in_list /enabling-required-reviews-for-pull-requests %} {% link_in_list /about-required-commit-signing %} {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} {% link_in_list /enabling-force-pushes-to-a-protected-branch %} {% link_in_list /enabling-deletion-of-a-protected-branch %} - {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} {% link_in_list /viewing-your-repositorys-releases-and-tags %} {% link_in_list /linking-to-releases %} - {% link_in_list /comparing-releases %} - - {% link_in_list /automation-for-release-forms-with-query-parameters %} - - {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} {% link_in_list /configuring-secret-scanning-for-private-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} - - {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} {% link_in_list /about-dependabot-version-updates %} {% link_in_list /enabling-and-disabling-version-updates %} @@ -98,4 +76,3 @@ versions: {% link_in_list /customizing-dependency-updates %} {% link_in_list /configuration-options-for-dependency-updates %} {% link_in_list /keeping-your-actions-up-to-date-with-dependabot %} - diff --git a/translations/ru-RU/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/ru-RU/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md index c3a3a069af..fc0d175bf9 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/ru-RU/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -19,9 +19,9 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc {% mac %} -1. Copy the SSH key to your clipboard. +1. Copy the SSH public key to your clipboard. - If your SSH key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ pbcopy < ~/.ssh/id_ed25519.pub @@ -46,9 +46,9 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc {% windows %} -1. Copy the SSH key to your clipboard. +1. Copy the SSH public key to your clipboard. - If your SSH key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ clip < ~/.ssh/id_ed25519.pub @@ -73,9 +73,9 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc {% linux %} -1. Copy the SSH key to your clipboard. +1. Copy the SSH public key to your clipboard. - If your SSH key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. + If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell $ sudo apt-get install xclip 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 9b77dd9882..5aeb5dd84a 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 @@ -9,7 +9,7 @@ versions: enterprise-server: '*' --- -You must choose or generate a password for your {% data variables.product.product_name %} account that is: +You must choose or generate a password for your {% data variables.product.product_name %} account that is at least: - Eight characters long, if it includes a number and a lowercase letter, or - 16 characters long with any combination of characters diff --git a/translations/ru-RU/content/github/authenticating-to-github/index.md b/translations/ru-RU/content/github/authenticating-to-github/index.md index 1ea2f31cb2..30e51c7087 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/index.md +++ b/translations/ru-RU/content/github/authenticating-to-github/index.md @@ -35,11 +35,9 @@ versions: {% link_in_list /reviewing-your-authorized-applications-oauth %} {% link_in_list /reviewing-your-security-log %} {% link_in_list /removing-sensitive-data-from-a-repository %} - {% link_in_list /about-anonymized-image-urls %} {% link_in_list /about-githubs-ip-addresses %} {% link_in_list /githubs-ssh-key-fingerprints %} - {% link_in_list /sudo-mode %} {% link_in_list /preventing-unauthorized-access %} {% topic_link_in_list /securing-your-account-with-two-factor-authentication-2fa %} @@ -48,18 +46,14 @@ versions: {% link_in_list /configuring-two-factor-authentication-recovery-methods %} {% link_in_list /accessing-github-using-two-factor-authentication %} {% link_in_list /recovering-your-account-if-you-lose-your-2fa-credentials %} - {% link_in_list /changing-two-factor-authentication-delivery-methods-for-your-mobile-device %} {% link_in_list /countries-where-sms-authentication-is-supported %} - {% link_in_list /disabling-two-factor-authentication-for-your-personal-account %} - {% topic_link_in_list /authenticating-with-saml-single-sign-on %} {% link_in_list /about-authentication-with-saml-single-sign-on %} {% link_in_list /authorizing-an-ssh-key-for-use-with-saml-single-sign-on %} {% link_in_list /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-your-active-saml-sessions %} - {% topic_link_in_list /connecting-to-github-with-ssh %} {% link_in_list /about-ssh %} {% link_in_list /checking-for-existing-ssh-keys %} @@ -68,13 +62,9 @@ versions: {% link_in_list /testing-your-ssh-connection %} {% link_in_list /working-with-ssh-key-passphrases %} {% topic_link_in_list /troubleshooting-ssh %} - {% link_in_list /using-ssh-over-the-https-port %} - {% link_in_list /recovering-your-ssh-key-passphrase %} - {% link_in_list /deleted-or-missing-ssh-keys %} - {% link_in_list /error-permission-denied-publickey %} {% link_in_list /error-bad-file-number %} {% link_in_list /error-key-already-in-use %} @@ -82,9 +72,7 @@ versions: {% link_in_list /error-permission-to-userrepo-denied-to-userother-repo %} {% link_in_list /error-agent-admitted-failure-to-sign %} {% link_in_list /error-ssh-add-illegal-option----k %} - {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %} - {% link_in_list /error-were-doing-an-ssh-key-audit %} {% topic_link_in_list /managing-commit-signature-verification %} {% link_in_list /about-commit-signature-verification %} diff --git a/translations/ru-RU/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/ru-RU/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index d6d831d88f..d3bd28cdfe 100644 --- a/translations/ru-RU/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/ru-RU/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -40,6 +40,12 @@ To replace all text listed in `passwords.txt` wherever it can be found in your r $ bfg --replace-text passwords.txt ``` +After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. + +```shell +$ git push --force +``` + See the [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. #### Using filter-branch 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 c38bd1da83..fb61dd8974 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 @@ -176,7 +176,7 @@ An overview of some of the most common actions that are recorded as events in th | `repo_funding_link_button_toggle` | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") | -| `sponsor_sponsorship_create` | Triggered when you sponsor a developer (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor#sponsoring-a-developer)") | +| `sponsor_sponsorship_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)") | diff --git a/translations/ru-RU/content/github/building-a-strong-community/index.md b/translations/ru-RU/content/github/building-a-strong-community/index.md index 854d6d0950..70d3a13506 100644 --- a/translations/ru-RU/content/github/building-a-strong-community/index.md +++ b/translations/ru-RU/content/github/building-a-strong-community/index.md @@ -13,21 +13,15 @@ versions: ### Table of Contents {% topic_link_in_list /setting-up-your-project-for-healthy-contributions %} - {% link_in_list /about-community-management-and-moderation %} {% link_in_list /about-community-profiles-for-public-repositories %} {% link_in_list /accessing-a-projects-community-profile %} {% link_in_list /adding-a-code-of-conduct-to-your-project %} - {% link_in_list /setting-guidelines-for-repository-contributors %} {% link_in_list /adding-a-license-to-a-repository %} {% link_in_list /adding-support-resources-to-your-project %} - {% link_in_list /creating-a-default-community-health-file %} - - {% link_in_list /encouraging-helpful-contributions-to-your-project-with-labels %} - {% topic_link_in_list /using-templates-to-encourage-useful-issues-and-pull-requests %} {% link_in_list /about-issue-and-pull-request-templates %} {% link_in_list /configuring-issue-templates-for-your-repository %} @@ -42,7 +36,6 @@ versions: {% link_in_list /tracking-changes-in-a-comment %} {% link_in_list /managing-how-contributors-report-abuse-in-your-organizations-repository %} {% link_in_list /managing-reported-content-in-your-organizations-repository %} - {% topic_link_in_list /maintaining-your-safety-on-github %} {% link_in_list /blocking-a-user-from-your-personal-account %} {% link_in_list /viewing-users-youve-blocked-from-your-personal-account %} @@ -51,7 +44,6 @@ versions: {% link_in_list /viewing-users-who-are-blocked-from-your-organization %} {% link_in_list /unblocking-a-user-from-your-organization %} {% link_in_list /reporting-abuse-or-spam %} - {% topic_link_in_list /documenting-your-project-with-wikis %} {% link_in_list /about-wikis %} {% link_in_list /adding-or-editing-wiki-pages %} @@ -60,10 +52,8 @@ versions: {% link_in_list /viewing-a-wikis-history-of-changes %} {% link_in_list /changing-access-permissions-for-wikis %} {% link_in_list /disabling-wikis %} - {% topic_link_in_list /collaborating-with-your-team %} {% link_in_list /about-team-discussions %} {% link_in_list /creating-a-team-discussion %} {% link_in_list /editing-or-deleting-a-team-discussion %} {% link_in_list /pinning-a-team-discussion %} - diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md index dea5b437d8..a74e6eac66 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -22,7 +22,11 @@ versions: {% data reusables.pull_requests.automatically-delete-branches %} -If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." +{% note %} + +**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." + +{% endnote %} If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)" or "[Closing a pull request](/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request)." diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/index.md index fe2b997f77..ae4915c002 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/index.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/index.md @@ -29,9 +29,7 @@ versions: {% link_in_list /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility %} {% topic_link_in_list /collaborating-on-repositories-with-code-quality-features %} {% link_in_list /about-status-checks %} - {% link_in_list /working-with-pre-receive-hooks %} - {% topic_link_in_list /proposing-changes-to-your-work-with-pull-requests %} {% link_in_list /about-branches %} {% link_in_list /creating-and-deleting-branches-within-your-repository %} @@ -39,9 +37,7 @@ versions: {% link_in_list /about-comparing-branches-in-pull-requests %} {% link_in_list /creating-a-pull-request %} {% link_in_list /creating-a-pull-request-from-a-fork %} - {% link_in_list /changing-the-stage-of-a-pull-request %} - {% link_in_list /requesting-a-pull-request-review %} {% link_in_list /changing-the-base-branch-of-a-pull-request %} {% link_in_list /committing-changes-to-a-pull-request-branch-created-from-a-fork %} @@ -52,15 +48,12 @@ versions: {% topic_link_in_list /reviewing-changes-in-pull-requests %} {% link_in_list /about-pull-request-reviews %} {% link_in_list /reviewing-proposed-changes-in-a-pull-request %} - {% link_in_list /filtering-files-in-a-pull-request %} - {% link_in_list /finding-changed-methods-and-functions-in-a-pull-request %} {% link_in_list /commenting-on-a-pull-request %} {% link_in_list /viewing-a-pull-request-review %} - + {% link_in_list /reviewing-dependency-changes-in-a-pull-request %} {% link_in_list /incorporating-feedback-in-your-pull-request %} - {% link_in_list /approving-a-pull-request-with-required-reviews %} {% link_in_list /dismissing-a-pull-request-review %} {% link_in_list /checking-out-pull-requests-locally %} diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md new file mode 100644 index 0000000000..308d7f0f33 --- /dev/null +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -0,0 +1,74 @@ +--- +title: Reviewing dependency changes in a pull request +intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Dependency review is currently in beta and subject to change. + +{% endnote %} + +### About dependency review + +If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. + +Dependency review is available in: + +* All public repositories. +* Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[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)." + +Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. + +By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. {% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix them at some later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)." + +Dependency review supports the same languages and package management ecosystems as the dependency graph. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." + +### Reviewing dependencies in a pull request + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} + +1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. + + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + + {% note %} + + **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% endnote %} + +1. Check the dependencies listed in the dependency review. + + ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) + + Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name. + + The icon beside each dependency indicates whether the dependency has been added ({% octicon "diff-added" aria-label="Dependency added icon" %}), updated ({% octicon "diff-modified" aria-label="Dependency modified icon" %}), or removed ({% octicon "diff-removed" aria-label="Dependency removed icon" %}) in this pull request. + + Other information includes: + + * The version, or version range, of the new, updated, or deleted dependency. + * For a specific version of a dependency: + * The age of that release of the dependency. + * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency. + * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project. + + Where a dependency has a known vulnerability, the warning message includes: + + * A brief description of the vulnerability. + * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability. + * The severity of the vulnerability. + * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. + +1. You can return to the original view of the file by clicking the source diff button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index e8c4a5c61d..9df09823e9 100644 --- a/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -29,6 +29,18 @@ Before you submit your review, your line comments are _pending_ and only visible ![Cancel review button](/assets/images/help/pull_requests/cancel-review-button.png) +{% if currentVersion == "free-pro-team@latest" %} +### Reviewing dependency changes + +If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. 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 reusables.repositories.changed-files %} + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) +{% endif %} + ### Marking a file as viewed After you finish reviewing a file, you can mark the file as viewed, and the file will collapse. If the file changes after you view the file, it will be unmarked as viewed. @@ -53,8 +65,5 @@ After you've finished reviewing all the files you want in the pull request, subm ### Дополнительная литература -- "[About pull request reviews](/articles/about-pull-request-reviews)" -- "[About required reviews for pull requests](/articles/about-required-reviews-for-pull-requests)" -- "[Approving a pull request with required reviews](/articles/approving-a-pull-request-with-required-reviews)" -- "[Commenting on a pull request](/articles/commenting-on-a-pull-request)" -- "[Filtering pull requests by review status](/articles/filtering-pull-requests-by-review-status)" +- "[About required reviews for pull requests](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[Filtering pull requests by review status](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" diff --git a/translations/ru-RU/content/github/committing-changes-to-your-project/index.md b/translations/ru-RU/content/github/committing-changes-to-your-project/index.md index 6a0d69b0c6..d08959632a 100644 --- a/translations/ru-RU/content/github/committing-changes-to-your-project/index.md +++ b/translations/ru-RU/content/github/committing-changes-to-your-project/index.md @@ -16,9 +16,7 @@ versions: {% topic_link_in_list /creating-and-editing-commits %} {% link_in_list /about-commits %} {% link_in_list /creating-a-commit-with-multiple-authors %} - {% link_in_list /creating-a-commit-on-behalf-of-an-organization %} - {% link_in_list /changing-a-commit-message %} {% topic_link_in_list /viewing-and-comparing-commits %} {% link_in_list /commit-branch-and-tag-labels %} 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 ff4e10876d..9c16a5ffd4 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 @@ -40,9 +40,9 @@ For code owners to receive review requests, the CODEOWNERS file must be on the b ### CODEOWNERS syntax -A CODEOWNERS file uses a pattern that follows the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files. The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. You can also refer to a user by an email address that has been added to their {% data variables.product.product_name %} account, for example `user@example.com`. +A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files, with [some exceptions](#syntax-exceptions). The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. You can also refer to a user by an email address that has been added to their {% data variables.product.product_name %} account, for example `user@example.com`. -If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. Invalid syntax includes inline comments and user or team names that do not exist on {% data variables.product.product_name %}. +If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. #### Example of a CODEOWNERS file ``` # This is a comment. @@ -84,6 +84,13 @@ apps/ @octocat # subdirectories. /docs/ @doctocat ``` +#### Syntax exceptions +There are some syntax rules for gitignore files that do not work in CODEOWNERS files: +- Escaping a pattern starting with `#` using `\` so it is treated as a pattern and not a comment +- Using `!` to negate a pattern +- Using `[ ]` to define a character range + + ### Дополнительная литература diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index abfe9a14e0..08a397f1d3 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -1,6 +1,6 @@ --- title: About repositories -intro: A repository is like a folder for your project. Your project's repository contains all of your project's files and stores each file's revision history. You can also discuss and manage your project's work within the repository. +intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository. redirect_from: - /articles/about-repositories versions: @@ -22,9 +22,11 @@ With Each person and organization can own unlimited repositories and invite an unlimited number of collaborators to all repositories. {% endif %} -You can collaborate on your project with others using your repository's issues, pull requests, and project boards. - -![Main page of the octocat/Hello-World repository](/assets/images/help/repository/repo-main-page.png) +You can use repositories to manage your work and collaborate with others. +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)." +- {% data reusables.discussions.you-can-use-discussions %} +- You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." +- You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)." {% data reusables.repositories.repo-size-limit %} diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md index 3dfc5d732a..9848b72fff 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md @@ -45,16 +45,16 @@ You can find the URL of the local repository by opening the command line and typ ```shell $ git remote -v # View existing remotes -> origin https://github.com/github/reactivecocoa.git (fetch) -> origin https://github.com/github/reactivecocoa.git (push) +> origin https://github.com/ghost/reactivecocoa.git (fetch) +> origin https://github.com/ghost/reactivecocoa.git (push) -$ git remote set-url origin https://github.com/github/ReactiveCocoa.git +$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git # Change the 'origin' remote's URL $ git remote -v # Verify new remote URL -> origin https://github.com/github/ReactiveCocoa.git (fetch) -> origin https://github.com/github/ReactiveCocoa.git (push) +> origin https://github.com/ghost/ReactiveCocoa.git (fetch) +> origin https://github.com/ghost/ReactiveCocoa.git (push) ``` Alternatively, you can change the URL through our [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) application. diff --git a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/index.md index c3f6d3e54d..d590e22a92 100644 --- a/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/index.md +++ b/translations/ru-RU/content/github/creating-cloning-and-archiving-repositories/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repositories %} {% link_in_list /about-repository-visibility %} {% link_in_list /creating-a-new-repository %} - {% link_in_list /creating-a-repository-from-a-template %} - {% link_in_list /about-readmes %} {% link_in_list /about-code-owners %} {% link_in_list /about-repository-languages %} {% link_in_list /licensing-a-repository %} - {% link_in_list /creating-a-template-repository %} - {% link_in_list /creating-an-issues-only-repository %} {% link_in_list /limits-for-viewing-content-and-diffs-in-a-repository %} {% link_in_list /duplicating-a-repository %} @@ -39,8 +35,6 @@ versions: {% topic_link_in_list /archiving-a-github-repository %} {% link_in_list /about-archiving-repositories %} {% link_in_list /archiving-repositories %} - {% link_in_list /about-archiving-content-and-data-on-github %} {% link_in_list /referencing-and-citing-content %} - {% link_in_list /backing-up-a-repository %} diff --git a/translations/ru-RU/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/ru-RU/content/github/customizing-your-github-workflow/about-github-marketplace.md index fe8b0775d3..3a21217379 100644 --- a/translations/ru-RU/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/ru-RU/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -7,26 +7,27 @@ versions: free-pro-team: '*' --- -You can discover, browse, and install free and paid tools, including [{% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/), and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). +You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). If you purchase a paid tool, you'll pay for your tool subscription with the same billing information you use to pay for your {% data variables.product.product_name %} subscription, and receive one bill on your regular billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)." -You may also have the option to select a free 14-day trial on select tools. You can cancel at any time during your trial and you won't be charged, but you will automatically lose access to the tool. Your paid subscription will start at the end of the 14-day trial. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)." +You may also have the option to select a free 14-day trial on some tools. You can cancel at any time during your trial and you won't be charged, but you will automatically lose access to the tool. Your paid subscription will start at the end of the 14-day trial. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)." -{% data variables.product.prodname_github_app %}s and {% data variables.product.prodname_oauth_app %}s can be verified or unverified. Verified apps meet specific requirements set by {% data variables.product.prodname_dotcom %} and go through a security review before they are listed on {% data variables.product.prodname_marketplace %}. For more information, see "[Requirements for listing an app on GitHub Marketplace](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." +### Finding tools on {% data variables.product.prodname_marketplace %} -### {% data variables.product.prodname_actions %} on {% data variables.product.prodname_marketplace %} +You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." -You can discover, browse, and install {% data variables.product.prodname_actions %} created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +{% data reusables.actions.actions-not-verified %} -Anyone can list an action on {% data variables.product.prodname_marketplace %}. Unlike some apps, {% data variables.product.prodname_actions %} listed on {% data variables.product.prodname_marketplace %} are never verified by {% data variables.product.prodname_dotcom %}. +Anyone can list a free {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} on {% data variables.product.prodname_marketplace %}. Publishers of paid apps are verified by {% data variables.product.company_short %} and listings for these apps are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. You will also see badges for unverified and verified apps. These apps were published using the previous method for verifying individual apps. For more information about the current process, see "[About verified creators](/developers/github-marketplace/about-verified-creators)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." ### Building and listing a tool on {% data variables.product.prodname_marketplace %} -For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/apps)" and "[{% data variables.product.prodname_actions %}](/actions)." +For more information on creating your own tool to list on {% data variables.product.prodname_marketplace %}, see "[Apps](/developers/apps)" and "[{% data variables.product.prodname_actions %}](/actions)." ### Дополнительная литература - "[Purchasing and installing apps in {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" - "[Managing billing for {% data variables.product.prodname_marketplace %} apps](/articles/managing-billing-for-github-marketplace-apps)" - "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)" +- "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)" diff --git a/translations/ru-RU/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/ru-RU/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md index bae90e2db4..07781dde1b 100644 --- a/translations/ru-RU/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/ru-RU/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -15,7 +15,7 @@ versions: {% data reusables.codespaces.about-configuration %} -If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes tools for Node.js, JavaScript, TypeScript, Python, C++, Java, C#, .NET Core, PHP, and PowerShell. For more information about the base Linux image, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) repository. +If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace with a base Linux image. The base Linux image includes tools for Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, PowerShell, Go, Ruby, and Rust. For more information about the base Linux image, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) repository. {% data reusables.codespaces.about-personalization %} {% data reusables.codespaces.codespace-config-order %} For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)." diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 48d380143d..84f7b31d9f 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md @@ -181,17 +181,17 @@ jobs: - name: Install dependencies run: | python -m pip install --upgrade pip - if [ -f requirements.txt ]; + if [ -f requirements.txt ]; then pip install -r requirements.txt; fi # Set the `CODEQL-PYTHON` environment variable to the Python executable # that includes the dependencies - echo "::set-env name=CODEQL_PYTHON::$(which python)" + echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV - name: Initialize CodeQL uses: github/codeql-action/init@v1 with: languages: python - # Override the default behavior so that the action doesn't attempt + # Override the default behavior so that the action doesn't attempt # to auto-install Python dependencies setup-python-dependencies: false ``` @@ -263,8 +263,8 @@ For the interpreted languages that {% data variables.product.prodname_codeql %} ``` yaml paths: - - src -paths-ignore: + - src +paths-ignore: - src/node_modules - '**/*.test.js' ``` @@ -296,7 +296,7 @@ You can quickly analyze small portions of a monorepo when you modify code in spe 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 `github/foo`, `github/bar`, and `github/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. +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 @@ -305,9 +305,9 @@ steps: env: TOKEN: ${{ secrets.ACCESS_TOKEN }} run: | - git config --global url."https://${TOKEN}@github.com/github/foo".insteadOf "https://github.com/github/foo" - git config --global url."https://${TOKEN}@github.com/github/bar".insteadOf "https://github.com/github/bar" - git config --global url."https://${TOKEN}@github.com/github/baz".insteadOf "https://github.com/github/baz" + 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 %} diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md index d32e59c2c2..8b0021e943 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md @@ -21,7 +21,7 @@ You must run {% data variables.product.prodname_codeql %} in the same container You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations: * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* MacOS: https://github.com/actions/virtual-environments/tree/main/images/macos +* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos * Windows: https://github.com/actions/virtual-environments/tree/main/images/win ### Example workflow diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 5fdb172f9d..1a1c575002 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -40,7 +40,7 @@ On Linux: chmod +x codeql-runner-linux ``` -On MacOS: +На macOS: ```shell chmod +x codeql-runner-macos diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 747a4dfb9d..80c5b6b9a4 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -107,13 +107,13 @@ A location within a programming artifact, such as a file in the repository or a #### `physicalLocation` object -| 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/github/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. | +| 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. | ### SARIF output file examples diff --git a/translations/ru-RU/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/ru-RU/content/github/getting-started-with-github/git-and-github-learning-resources.md index 27fb88e098..6d38b73c1a 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/ru-RU/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +authors: + - GitHub --- ### Using Git diff --git a/translations/ru-RU/content/github/getting-started-with-github/github-glossary.md b/translations/ru-RU/content/github/getting-started-with-github/github-glossary.md index 774abaf924..38e07a11e2 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/github-glossary.md +++ b/translations/ru-RU/content/github/getting-started-with-github/github-glossary.md @@ -10,8 +10,8 @@ versions: --- {% for term in site.data.glossaries.external %} - ### {{term.term}} - {{term.description}} + ### {% data glossaries.external[forloop.index0].term %} + {% data glossaries.external[forloop.index0].description %} --- {% endfor %} diff --git a/translations/ru-RU/content/github/getting-started-with-github/index.md b/translations/ru-RU/content/github/getting-started-with-github/index.md index 58792d38bc..c8b857b90e 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/index.md +++ b/translations/ru-RU/content/github/getting-started-with-github/index.md @@ -27,37 +27,27 @@ versions: {% link_in_list /fork-a-repo %} {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} - {% link_in_list /githubs-products %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} - {% link_in_list /types-of-github-accounts %} - {% link_in_list /faq-about-changes-to-githubs-plans %} {% link_in_list /github-cli %} {% link_in_list /github-desktop %} {% link_in_list /github-for-mobile %} - {% link_in_list /access-permissions-on-github %} {% link_in_list /github-glossary %} {% link_in_list /git-cheatsheet %} {% link_in_list /git-and-github-learning-resources %} {% topic_link_in_list /signing-up-for-github %} - {% link_in_list /signing-up-for-a-new-github-account %} {% link_in_list /verifying-your-email-address %} - {% link_in_list /setting-up-a-trial-of-github-enterprise-cloud %} {% link_in_list /setting-up-a-trial-of-github-enterprise-server %} {% topic_link_in_list /exploring-projects-on-github %} - {% link_in_list /finding-ways-to-contribute-to-open-source-on-github %} - {% link_in_list /saving-repositories-with-stars %} {% link_in_list /following-people %} {% topic_link_in_list /using-github %} {% link_in_list /supported-browsers %} - {% link_in_list /troubleshooting-connectivity-problems %} - {% link_in_list /keyboard-shortcuts %} diff --git a/translations/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 c49633d781..103e1e49c9 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 @@ -117,35 +117,35 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr #### Moving a column -| 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 | +| 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 | #### Moving a card -| 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 | +| 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 | #### Previewing a card @@ -156,38 +156,38 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr {% 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. | +| Keyboard shortcut | Description | +| --------------------------------------------------------- | --------------------------------------------------------------- | +| command + space or control + space | In the workflow editor, get suggestions for your workflow file. | {% endif %} ### Notification (Оповещения) {% 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 | +| Keyboard shortcut | Description | +| -------------------- | -------------- | +| e | Mark as done | +| shift + u | Mark as unread | +| shift + i | Mark as read | +| shift + m | Unsubscribe | {% else %} | Keyboard shortcut | Description | | -------------------------------------------- | ------------ | | e or I or y | Mark as read | -| shift m | Mute thread | +| shift + m | Mute thread | {% endif %} ### Сетевая диаграмма -| 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 | +| 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 | diff --git a/translations/ru-RU/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md b/translations/ru-RU/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md index 423632c341..e87051f222 100644 --- a/translations/ru-RU/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md +++ b/translations/ru-RU/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md @@ -1,5 +1,6 @@ --- title: Signing up for a new GitHub account +shortTitle: Sign up for a new GitHub account intro: '{% data variables.product.product_name %} offers user accounts for individuals and organizations for teams of people working together.' redirect_from: - /articles/signing-up-for-a-new-github-account @@ -9,9 +10,8 @@ versions: For more information about account types and products, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)" and "[{% data variables.product.product_name %}'s products](/articles/github-s-products)." -1. Go to {% data variables.product.product_name %}'s [Pricing]({% data variables.product.pricing_url %}) page. -2. Read the information about the different products and subscriptions that {% data variables.product.product_name %} offers, then click the upgrade button under the subscription you'd like to choose. -3. Follow the prompts to create your personal account or organization. +{% data reusables.accounts.create-account %} +1. Follow the prompts to create your personal account or organization. ### Дальнейшие шаги diff --git a/translations/ru-RU/content/github/importing-your-projects-to-github/index.md b/translations/ru-RU/content/github/importing-your-projects-to-github/index.md index 1ebc5ad0d3..7882a47ea4 100644 --- a/translations/ru-RU/content/github/importing-your-projects-to-github/index.md +++ b/translations/ru-RU/content/github/importing-your-projects-to-github/index.md @@ -15,11 +15,9 @@ versions: ### Table of Contents {% topic_link_in_list /importing-source-code-to-github %} - {% link_in_list /about-github-importer %} {% link_in_list /importing-a-repository-with-github-importer %} {% link_in_list /updating-commit-author-attribution-with-github-importer %} - {% link_in_list /importing-a-git-repository-using-the-command-line %} {% link_in_list /adding-an-existing-project-to-github-using-the-command-line %} {% link_in_list /source-code-migration-tools %} diff --git a/translations/ru-RU/content/github/index.md b/translations/ru-RU/content/github/index.md index 768349e16a..ea86322b6d 100644 --- a/translations/ru-RU/content/github/index.md +++ b/translations/ru-RU/content/github/index.md @@ -20,24 +20,14 @@ versions: {% link_in_list /authenticating-to-github %} - {% link_in_list /managing-subscriptions-and-notifications-on-github %} - - {% link_in_list /receiving-notifications-about-activity-on-github %} - {% link_in_list /setting-up-and-managing-organizations-and-teams %} - - {% link_in_list /setting-up-and-managing-your-enterprise %} - - - {% link_in_list /setting-up-and-managing-billing-and-payments-on-github %} - {% link_in_list /writing-on-github %} @@ -50,10 +40,7 @@ versions: {% link_in_list /collaborating-with-issues-and-pull-requests %} {% link_in_list /managing-your-work-on-github %} - - {% link_in_list /developing-online-with-codespaces %} - {% link_in_list /building-a-strong-community %} @@ -64,45 +51,20 @@ versions: {% link_in_list /administering-a-repository %} {% link_in_list /visualizing-repository-data-with-graphs %} - - {% link_in_list /managing-security-vulnerabilities %} - {% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %} {% link_in_list /managing-files-in-a-repository %} {% link_in_list /managing-large-files %} - - {% link_in_list /customizing-your-github-workflow %} - {% link_in_list /extending-github %} {% link_in_list /working-with-github-pages %} - - {% link_in_list /supporting-the-open-source-community-with-github-sponsors %} - - - -{% link_in_list /teaching-and-learning-with-github-education %} - - - {% link_in_list /finding-talent-with-github-jobs %} - - - {% link_in_list /working-with-github-support %} - - - {% link_in_list /understanding-how-github-uses-and-protects-your-data %} - - - {% link_in_list /site-policy %} - diff --git a/translations/ru-RU/content/github/managing-files-in-a-repository/index.md b/translations/ru-RU/content/github/managing-files-in-a-repository/index.md index ebc35dd973..d1765daf5e 100644 --- a/translations/ru-RU/content/github/managing-files-in-a-repository/index.md +++ b/translations/ru-RU/content/github/managing-files-in-a-repository/index.md @@ -14,9 +14,7 @@ versions: ### Table of Contents {% topic_link_in_list /managing-files-on-github %} - {% link_in_list /navigating-code-on-github %} - {% link_in_list /creating-new-files %} {% link_in_list /adding-a-file-to-a-repository %} {% link_in_list /moving-a-file-to-a-new-location %} diff --git a/translations/ru-RU/content/github/managing-large-files/index.md b/translations/ru-RU/content/github/managing-large-files/index.md index bc1db5f762..576ce0e49f 100644 --- a/translations/ru-RU/content/github/managing-large-files/index.md +++ b/translations/ru-RU/content/github/managing-large-files/index.md @@ -15,16 +15,12 @@ versions: {% link_in_list /conditions-for-large-files %} {% link_in_list /removing-files-from-a-repositorys-history %} {% link_in_list /distributing-large-binaries %} - {% link_in_list /what-is-my-disk-quota %} - {% topic_link_in_list /versioning-large-files %} {% link_in_list /about-git-large-file-storage %} {% link_in_list /installing-git-large-file-storage %} {% link_in_list /configuring-git-large-file-storage %} - {% link_in_list /about-storage-and-bandwidth-usage %} - {% link_in_list /collaboration-with-git-large-file-storage %} {% link_in_list /moving-a-file-in-your-repository-to-git-large-file-storage %} {% link_in_list /removing-files-from-git-large-file-storage %} 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 7e79109557..c8beaa69ea 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 @@ -25,6 +25,8 @@ When your code depends on a package that has a security vulnerability, this vuln - 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 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)." {% note %} diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md new file mode 100644 index 0000000000..c03292e26f --- /dev/null +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -0,0 +1,24 @@ +--- +title: About managing vulnerable dependencies +intro: '{% data variables.product.prodname_dotcom %} helps you to avoid using third-party software that contains known vulnerabilities.' +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies. + +#### Dependency graph +The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." + +#### Dependency review +By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + +#### {% data variables.product.prodname_dependabot_alerts %} +{% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + +#### {% data variables.product.prodname_dependabot_security_updates %} +When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." + + +#### {% data variables.product.prodname_dependabot_version_updates %} +Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 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 2a6c9269f2..a1001d67e4 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 @@ -12,7 +12,7 @@ versions: {% 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-features-for-new-repositories)." +{% 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)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %} diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/index.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/index.md index 819e4c4e24..9afde0213a 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/index.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/index.md @@ -9,8 +9,6 @@ versions: ### Table of Contents - - {% topic_link_in_list /managing-security-vulnerabilities-in-your-project %} {% link_in_list /adding-a-security-policy-to-your-repository %} {% link_in_list /about-github-security-advisories %} @@ -22,17 +20,13 @@ versions: {% link_in_list /publishing-a-security-advisory %} {% link_in_list /editing-a-security-advisory %} {% link_in_list /withdrawing-a-security-advisory %} - {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %} - + {% link_in_list /about-managing-vulnerable-dependencies %} {% link_in_list /browsing-security-vulnerabilities-in-the-github-advisory-database %} - {% link_in_list /about-alerts-for-vulnerable-dependencies %} {% link_in_list /configuring-notifications-for-vulnerable-dependencies %} - {% link_in_list /about-dependabot-security-updates %} {% link_in_list /configuring-dependabot-security-updates %} {% link_in_list /viewing-and-updating-vulnerable-dependencies-in-your-repository %} {% link_in_list /troubleshooting-the-detection-of-vulnerable-dependencies %} {% link_in_list /troubleshooting-dependabot-errors %} - diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index c33aa46aba..dd179ef0df 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -76,6 +76,12 @@ There are separate limits for security and version update pull requests, so that 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 %} can't resolve your dependency files + +**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". + +{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)." + ### Triggering a {% data variables.product.prodname_dependabot %} pull request manually If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request. diff --git a/translations/ru-RU/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/ru-RU/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 3cf6fc4e9c..44e22ef4aa 100644 --- a/translations/ru-RU/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/ru-RU/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -13,9 +13,11 @@ Your repository's {% data variables.product.prodname_dependabot %} alerts tab li You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +{% data reusables.repositories.dependency-review %} + ### About updates for vulnerable dependencies in your repository -{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. +{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability. ### Viewing and updating vulnerable dependencies diff --git a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 79274eff29..08fe0842d6 100644 --- a/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/ru-RU/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -124,7 +124,8 @@ To filter notifications for specific activity on {% data variables.product.produ - `is:repository-invitation`{% if currentVersion != "github-ae@latest" %} - `is:repository-vulnerability-alert` - `is:repository-advisory`{% endif %} -- `is:team-discussion` +- `is:team-discussion`{% if currentVersion == "free-pro-team@latest" %} +- `is:discussions`{% endif %} {% if currentVersion != "github-ae@latest" %} For information about reducing noise from notifications for diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/about-issues.md b/translations/ru-RU/content/github/managing-your-work-on-github/about-issues.md index fd3fc3010c..144b772e0f 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/about-issues.md @@ -10,8 +10,14 @@ versions: github-ae: '*' --- +### About issues + 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. +Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} + +{% data reusables.discussions.you-cannot-convert-a-discussion %} + {% 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 %}." diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/index.md b/translations/ru-RU/content/github/managing-your-work-on-github/index.md index d882a90b1d..eb501619b0 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/index.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/index.md @@ -17,15 +17,11 @@ versions: {% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} - {% link_in_list /deleting-an-issue %} - {% link_in_list /opening-an-issue-from-a-comment %} {% link_in_list /opening-an-issue-from-code %} - {% link_in_list /transferring-an-issue-to-another-repository %} {% link_in_list /pinning-an-issue-to-your-repository %} - {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} @@ -43,9 +39,7 @@ versions: {% link_in_list /linking-a-repository-to-a-project-board %} {% link_in_list /about-automation-for-project-boards %} {% link_in_list /configuring-automation-for-project-boards %} - {% link_in_list /copying-a-project-board %} - {% link_in_list /closing-a-project-board %} {% link_in_list /reopening-a-closed-project-board %} {% link_in_list /deleting-a-project-board %} diff --git a/translations/ru-RU/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/ru-RU/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index cea534ba2e..e1d6c5d4db 100644 --- a/translations/ru-RU/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/ru-RU/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -25,6 +25,7 @@ With issue and pull request search terms, you can: - Filter issues and pull requests that involve, but don't necessarily [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), certain people: `state:open type:issue involves:octocat` - Filter issues and pull requests by assignee: `state:open type:issue assignee:octocat` - Filter issues and pull requests by label: `state:open type:issue label:"bug"` +- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} For issues, you can also use search to: diff --git a/translations/ru-RU/content/github/receiving-notifications-about-activity-on-github/index.md b/translations/ru-RU/content/github/receiving-notifications-about-activity-on-github/index.md index 31ad8c870e..cbb97cfc98 100644 --- a/translations/ru-RU/content/github/receiving-notifications-about-activity-on-github/index.md +++ b/translations/ru-RU/content/github/receiving-notifications-about-activity-on-github/index.md @@ -14,16 +14,10 @@ versions: {% link_in_list /choosing-the-delivery-method-for-your-notifications %} {% topic_link_in_list /managing-your-notifications %} {% link_in_list /marking-notifications-as-read %} - {% link_in_list /saving-notifications-for-later %} - {% link_in_list /subscribing-to-and-unsubscribing-from-notifications %} - {% link_in_list /listing-the-issues-and-pull-requests-youre-subscribed-to %} - {% link_in_list /watching-and-unwatching-repositories %} - {% link_in_list /watching-and-unwatching-releases-for-a-repository %} - {% link_in_list /watching-and-unwatching-team-discussions %} {% link_in_list /listing-the-repositories-youre-watching %} diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/ru-RU/content/github/searching-for-information-on-github/about-searching-on-github.md index ac24eb8d19..4e4edf749f 100644 --- a/translations/ru-RU/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/ru-RU/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -41,7 +41,8 @@ You can search for the following information across all repositories you can acc - [Repositories](/articles/searching-for-repositories) - [Topics](/articles/searching-topics) -- [Issues and pull requests](/articles/searching-issues-and-pull-requests) +- [Issues and pull requests](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} +- [Discussions](/github/searching-for-information-on-github/searching-discussions){% endif %} - [Code](/articles/searching-code) - [Commits](/articles/searching-commits) - [Users](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/index.md b/translations/ru-RU/content/github/searching-for-information-on-github/index.md index 1c417eade8..e95408d576 100644 --- a/translations/ru-RU/content/github/searching-for-information-on-github/index.md +++ b/translations/ru-RU/content/github/searching-for-information-on-github/index.md @@ -26,6 +26,7 @@ versions: {% link_in_list /searching-code %} {% link_in_list /searching-commits %} {% link_in_list /searching-issues-and-pull-requests %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /searching-discussions %} {% link_in_list /searching-github-marketplace %}{% endif %} {% link_in_list /searching-users %} {% link_in_list /searching-for-packages %} diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/searching-discussions.md b/translations/ru-RU/content/github/searching-for-information-on-github/searching-discussions.md new file mode 100644 index 0000000000..4e6a90aa13 --- /dev/null +++ b/translations/ru-RU/content/github/searching-for-information-on-github/searching-discussions.md @@ -0,0 +1,110 @@ +--- +title: Searching discussions +intro: You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)." + +{% data reusables.search.syntax_tips %} + +### Search by the title, body, or comments + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| Qualifier | Пример | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +### Search within a user's or organization's repositories + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| Qualifier | Пример | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +### Filter by repository visibility + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." + +| Qualifier | Example | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +### Search by author + +The `author` qualifier finds discussions created by a certain user. + +| Qualifier | Пример | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +### Search by commenter + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| Qualifier | Пример | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +### Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| Qualifier | Пример | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +### Search by number of comments + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +### Search by number of interactions + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +### Search by number of reactions + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +### Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +### Дополнительная литература + +- "[Sorting search results](/articles/sorting-search-results/)" diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 0bf0c6ab43..d4ec220a4a 100644 --- a/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/ru-RU/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -203,7 +203,7 @@ You can use the `comments` qualifier along with [greater than, less than, and ra | Qualifier | Пример | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3C100&type=Issues) matches closed issues with more than 100 comments. | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. | | | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. | ### Search by number of interactions diff --git a/translations/ru-RU/content/github/searching-for-information-on-github/searching-topics.md b/translations/ru-RU/content/github/searching-for-information-on-github/searching-topics.md index 9e4d8751db..e79ac2ed28 100644 --- a/translations/ru-RU/content/github/searching-for-information-on-github/searching-topics.md +++ b/translations/ru-RU/content/github/searching-for-information-on-github/searching-topics.md @@ -26,7 +26,7 @@ If you want to explore repositories about a certain topic, find projects to cont The `is:featured` search qualifier will narrow search results to the topics with the most repositories on {% data variables.product.product_name %}. These topics are also featured at https://github.com/topics/. -The `is:curated` search qualifier will narrow search results to topics that community members have added extra information to. For more information, see the explore repository at https://github.com/github/explore. +The `is:curated` search qualifier will narrow search results to topics that community members have added extra information to. For more information, see the [explore repository](https://github.com/github/explore). You can filter topics based when they were created using the date parameter and `created:` or based on how many repositories are associated with this topic using `repositories:n`. Both of these qualifiers can use the [greater than and less than range qualifiers](/articles/understanding-the-search-syntax). diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index daf74f355e..4b001281e3 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -8,7 +8,9 @@ versions: ### About billing for {% data variables.product.prodname_actions %} -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} + +{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." Minutes reset every month, while storage usage does not. @@ -69,8 +71,8 @@ Your {% data variables.product.prodname_actions %} usage shares your account's e ### About spending limits -By default, your account will have a spending limit of $0 for {% data variables.product.prodname_actions %} usage. To enable using minutes and storage for private repositories beyond the amounts included with your account, you can increase the spending limit or allow unlimited spending. For more information, 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 reusables.github-actions.actions-spending-limit-detailed %} -{% data reusables.github-actions.spending-limit-enterprise-account %} +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 reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 5b1e0b2859..4674dc6c72 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -10,6 +10,8 @@ versions: {% data reusables.package_registry.packages-billing %} +{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." + {% data reusables.package_registry.container-registry-beta-billing-note %} Data transfer resets every month, while storage usage does not. @@ -50,8 +52,8 @@ Your {% data variables.product.prodname_registry %} usage shares your account's ### About spending limits -By default, your account will have a spending limit of $0 for {% data variables.product.prodname_registry %} usage. To enable storage and data transfer for private packages beyond the amounts included with your account, you can increase the spending limit or allow unlimited spending. For more information, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." +{% data reusables.package_registry.packages-spending-limit-detailed %} -{% data reusables.package_registry.spending-limit-enterprise-account %} +For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md index 9bc9e3447a..77b9655907 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md @@ -9,6 +9,8 @@ versions: {% data reusables.sponsors.sponsorship-details %} +{% data reusables.sponsors.no-fees %} + {% data reusables.dotcom_billing.view-all-subscriptions %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md index 2893905679..b8d96745e0 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### Discounts for personal accounts -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 "[Applying for a student developer pack](/articles/applying-for-a-student-developer-pack)." +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/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." ### Discounts for schools and universities -Verified academic faculty can apply for {% data variables.product.prodname_team %} for teaching or academic research. For more information, see "[Using {% data variables.product.prodname_dotcom %} in your classroom and research](/articles/using-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/). +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/teach-and-learn-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/). ### Discounts for nonprofits and libraries 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 68a7d36c58..340d65b9b2 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 @@ -7,24 +7,24 @@ versions: free-pro-team: '*' --- +{% 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 %} + ### Downgrading a sponsorship -When you downgrade a sponsorship, the change will become effective on your next billing date. {% data reusables.sponsors.no-refunds %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. On the right side of the page, next to your selected tier, click **Edit**. ![Edit tier button](/assets/images/help/billing/edit-tier-button.png) +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### Canceling a sponsorship -When you cancel a sponsorship, the change will become effective on your next billing date. {% data reusables.sponsors.no-refunds %} - {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.billing %} +{% 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/managing-your-spending-limit-for-github-actions.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index bc99201f6a..8ae1262da6 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -8,13 +8,15 @@ versions: ### About spending limits for {% data variables.product.prodname_actions %} -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} -You can set a higher spending limit or, for some accounts, allow unlimited spending. If you pay for your organization or enterprise account by invoice, you can prepay for overages to set a higher spending limit. The spending limit applies to your combined overages for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. 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.github-actions.actions-spending-limit-brief %} -As soon as you set a spending limit above $0, you will be responsible for any overages that occurred in the past. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and creates workflow artifacts that increase your storage usage for the month from 1.9GB to 2.1GB, you will use slightly more storage than the 2GB your product includes. +{% 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)." -Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages in a future month, your first bill will include the 0.1GB of overage from the past in addition to any overages for the current billing cycle. +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and creates workflow artifacts that increase your storage usage for the month from 1.9GB to 2.1GB, you will use slightly more storage than the 2GB your product includes. + +Because you have not enabled overages, your next attempt to create a workflow artifact will fail. You will not receive a bill for the 0.1GB overage that month. 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. ### Managing the spending limit for {% data variables.product.prodname_actions %} for your user account @@ -30,8 +32,6 @@ Anyone can manage the spending limit for {% data variables.product.prodname_acti Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an organization. -If you pay for your organization account by invoice, you cannot manage the spending limit for your enterprise account on {% data variables.product.product_name %}. If you want to allow repositories owned by your organization to use {% data variables.product.prodname_actions %} beyond the storage or data transfer included for each repository, you can prepay for overages. Because overages must prepaid, you cannot enable unlimited spending on accounts paid by invoice. Your spending limit will be 150% of the amount you prepaid. If you have any questions, [contact our account management team](https://enterprise.github.com/contact). - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ If you pay for your organization account by invoice, you cannot manage the spend Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an enterprise account. -{% data reusables.github-actions.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 4fd980b821..a89aca74c9 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -10,11 +10,13 @@ versions: {% data reusables.package_registry.packages-billing %} -You can set a higher spending limit or, for some accounts, allow unlimited spending. If you pay for your organization or enterprise account by invoice, you can prepay for overages to set a higher spending limit. The spending limit applies to your combined overages for {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}. 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.package_registry.packages-spending-limit-brief %} -As soon as you set a spending limit above $0, you will be responsible for any overages that occurred in the past. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and publishes a new version of a private package that increases your storage usage for the month from 1.9GB to 2.1GB, publishing the version will use slightly more than the 2GB your product includes. +{% 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)." -Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages in a future month, your first bill will include the 0.1GB of overage from the past in addition to any overages for the current billing cycle. +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and publishes a new version of a private package that increases your storage usage for the month from 1.9GB to 2.1GB, publishing the version will use slightly more than the 2GB your product includes. + +Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. 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. ### Managing the spending limit for {% data variables.product.prodname_registry %} for your user account @@ -30,8 +32,6 @@ Anyone can manage the spending limit for {% data variables.product.prodname_regi Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an organization. -If you pay for your organization account by invoice, you cannot manage the spending limit for your enterprise account on {% data variables.product.product_name %}. If you want to allow repositories owned by your organization to use {% data variables.product.prodname_registry %} beyond the storage or data transfer included for each repository, you can prepay for overages. Because overages must prepaid, you cannot enable unlimited spending on accounts paid by invoice. Your spending limit will be 150% of the amount you prepaid. If you have any questions, [contact our account management team](https://enterprise.github.com/contact). - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ If you pay for your organization account by invoice, you cannot manage the spend Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an enterprise account. -{% data reusables.package_registry.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 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 43f0ab53e7..f1ff761223 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 @@ -7,12 +7,15 @@ versions: free-pro-team: '*' --- +{% data reusables.sponsors.org-sponsors-release-phase %} + +### About sponsorship upgrades + When you upgrade your sponsorship tier, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. On the right side of the page, next to your selected tier, click **Edit**. ![Edit tier button](/assets/images/help/billing/edit-tier-button.png) +### Upgrading a sponsorship + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.update-sponsorship %} +{% data reusables.sponsors.update-sponsorship %} \ No newline at end of file diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md index 65902675cb..6cc19fc18b 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md @@ -20,7 +20,7 @@ versions: ### 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, and issues from the account. +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 diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md index a60e0307b4..858bd85d4a 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -19,4 +19,4 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.oauth_app_access %} 5. 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 button](/assets/images/help/settings/settings-third-party-confirm-disable.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/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md index 51d361dd56..d1c440e8c5 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -20,42 +20,30 @@ versions: {% link_in_list /creating-a-new-organization-from-scratch %} {% link_in_list /accessing-your-organizations-settings %} {% link_in_list /about-your-organizations-news-feed %} - {% link_in_list /viewing-insights-for-your-organization %} - {% topic_link_in_list /managing-membership-in-your-organization %} - {% link_in_list /inviting-users-to-join-your-organization %} {% link_in_list /canceling-or-editing-an-invitation-to-join-your-organization %} {% link_in_list /adding-people-to-your-organization %} - {% link_in_list /removing-a-member-from-your-organization %} {% link_in_list /reinstating-a-former-member-of-your-organization %} - {% link_in_list /can-i-create-accounts-for-people-in-my-organization %} - {% topic_link_in_list /managing-peoples-access-to-your-organization-with-roles %} {% link_in_list /permission-levels-for-an-organization %} {% link_in_list /maintaining-ownership-continuity-for-your-organization %} {% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %} - {% link_in_list /adding-a-billing-manager-to-your-organization %} {% link_in_list /removing-a-billing-manager-from-your-organization %} - {% topic_link_in_list /organizing-members-into-teams %} {% link_in_list /about-teams %} {% link_in_list /creating-a-team %} {% link_in_list /setting-your-teams-profile-picture %} {% link_in_list /adding-organization-members-to-a-team %} - {% link_in_list /managing-code-review-assignment-for-your-team %} - {% link_in_list /renaming-a-team %} {% link_in_list /changing-team-visibility %} - {% link_in_list /synchronizing-a-team-with-an-identity-provider-group %} - {% link_in_list /moving-a-team-in-your-organizations-hierarchy %} {% link_in_list /requesting-to-add-a-child-team %} {% link_in_list /requesting-to-add-or-change-a-parent-team %} @@ -66,9 +54,7 @@ versions: {% topic_link_in_list /managing-access-to-your-organizations-repositories %} {% link_in_list /repository-permission-levels-for-an-organization %} {% link_in_list /setting-base-permissions-for-an-organization %} - {% link_in_list /viewing-people-with-access-to-your-repository %} - {% link_in_list /managing-an-individuals-access-to-an-organization-repository %} {% link_in_list /managing-team-access-to-an-organization-repository %} {% link_in_list /adding-outside-collaborators-to-repositories-in-your-organization %} @@ -84,83 +70,54 @@ versions: {% link_in_list /managing-an-individuals-access-to-an-organization-project-board %} {% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %} {% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %} - {% topic_link_in_list /managing-access-to-your-organizations-apps %} {% link_in_list /adding-github-app-managers-in-your-organization %} {% link_in_list /removing-github-app-managers-from-your-organization %} - {% topic_link_in_list /managing-organization-settings %} - {% link_in_list /verifying-your-organizations-domain %} - {% link_in_list /renaming-an-organization %} {% link_in_list /transferring-organization-ownership %} {% link_in_list /restricting-repository-creation-in-your-organization %} {% link_in_list /setting-permissions-for-deleting-or-transferring-repositories %} {% link_in_list /restricting-repository-visibility-changes-in-your-organization %} {% link_in_list /managing-the-forking-policy-for-your-organization %} - {% link_in_list /disabling-or-limiting-github-actions-for-your-organization %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization %} - - {% link_in_list /setting-permissions-for-adding-outside-collaborators %} - {% link_in_list /allowing-people-to-delete-issues-in-your-organization %} - - + {% link_in_list /allowing-people-to-delete-issues-in-your-organization %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /managing-discussion-creation-for-repositories-in-your-organization %}{% endif %} {% link_in_list /setting-team-creation-permissions-in-your-organization %} - - {% link_in_list /managing-scheduled-reminders-for-your-organization %} - - {% link_in_list /managing-the-default-branch-name-for-repositories-in-your-organization %} - - {% link_in_list /managing-default-labels-for-repositories-in-your-organization %} - - {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} - - {% link_in_list /managing-the-display-of-member-names-in-your-organization %} - + {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} - {% link_in_list /integrating-jira-with-your-organization-project-board %} - - {% link_in_list /upgrading-to-the-corporate-terms-of-service %} - {% topic_link_in_list /migrating-to-improved-organization-permissions %} {% link_in_list /converting-an-owners-team-to-improved-organization-permissions %} {% link_in_list /converting-an-admin-team-to-improved-organization-permissions %} {% link_in_list /migrating-admin-teams-to-improved-organization-permissions %} - {% topic_link_in_list /restricting-access-to-your-organizations-data %} {% link_in_list /about-oauth-app-access-restrictions %} {% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /approving-oauth-apps-for-your-organization %} {% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %} - {% topic_link_in_list /keeping-your-organization-secure %} {% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %} {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} - {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} {% link_in_list /managing-secret-scanning-for-your-organization %} - {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} - {% link_in_list /restricting-email-notifications-to-an-approved-domain %} - {% link_in_list /reviewing-the-audit-log-for-your-organization %} {% link_in_list /reviewing-your-organizations-installed-integrations %} - {% topic_link_in_list /managing-saml-single-sign-on-for-your-organization %} {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} {% link_in_list /about-scim %} @@ -170,17 +127,12 @@ versions: {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} {% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %} - {% link_in_list /managing-team-synchronization-for-your-organization %} - {% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %} {% topic_link_in_list /granting-access-to-your-organization-with-saml-single-sign-on %} {% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %} {% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %} - - {% topic_link_in_list /managing-git-access-to-your-organizations-repositories %} {% link_in_list /about-ssh-certificate-authorities %} {% link_in_list /managing-your-organizations-ssh-certificate-authorities %} - diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..8390b96ff6 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Managing discussion creation for repositories in your organization +intro: You can choose the permission levels that members require to create discussions in repositories owned by your organization. +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Allowing or disallowing users with read access to create discussions + +By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. 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/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index b7ffd2ac9c..c69629d637 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -9,29 +9,39 @@ versions: ### About management of security and analysis settings {% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. - {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% endif %} - -### Enabling or disabling features for existing repositories +### 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 %} -5. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -6. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) -### Enabling or disabling features for new repositories +The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. + +### Enabling or disabling a feature for all existing repositories + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) +1. Optionally, enable the feature by default for new repositories in your organization. !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) +1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization. ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + +### Enabling or disabling a feature for all new repositories when they are added + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + +### Allowing Dependabot to access private repositories + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) +1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. +1. Click **Select repositories**. -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories in your organization. ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..b97c8ba261 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,23 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +--- + +{% 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)" \ No newline at end of file diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 6e1bceca83..a71187af6e 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -55,6 +55,9 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late | Disable team discussions for an organization (see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)" for details) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} | 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** | | |{% endif %} | 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](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | | Manage security and analysis settings (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)" for details) | **X** | | | | Enable and enforce [SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 4c9a5eed7b..48439b2507 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -114,7 +114,19 @@ In addition to managing organization-level settings, organization owners have ad | [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** | +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} ### Дополнительная литература diff --git a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 5f2377b56c..7f8fbaceef 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -82,7 +82,9 @@ Each category has a set of associated actions that you can filter on. Напри Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} -{% data reusables.search.date_gt_lt %} For example: +{% 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. @@ -106,25 +108,53 @@ Using the qualifier `country`, you can filter events in the audit log based on t {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -### Using the Audit log API +### 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 API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} +**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 API to keep copies of your audit log data and monitor: -* Access to your organization or repository settings. -* Changes in permissions. -* Added or removed users in an organization, repository, or team. -* Users being promoted to admin. -* Changes to permissions of a GitHub App. +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. +{% 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 as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +{% 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)" in the REST API documentation. + +{% endif %} + ### Audit log actions An overview of some of the most common actions that are recorded as events in the audit log. @@ -214,6 +244,28 @@ An overview of some of the most common actions that are recorded as events in th | `обновление` | 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" %} + +#### `git` category actions + +{% note %} + +**Note:** To access Git events in the audit log, you must use the audit log REST API. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. + +{% 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 | @@ -499,10 +551,22 @@ For more information, see "[Restricting publication of {% data variables.product {% 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)") | +| Действие | 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 organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") | +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") | +| 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 %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index 7a366d5ccc..f081c2d719 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and{% endif %}private repositories, with specific details of your activity in private repositories anonymized. 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 %}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)." {% note %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/index.md index 19615ecffa..aff371dd59 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/index.md @@ -14,41 +14,28 @@ versions: {% topic_link_in_list /managing-user-account-settings %} {% link_in_list /about-your-personal-dashboard %} + {% link_in_list /managing-your-theme-settings %} {% link_in_list /changing-your-github-username %} - {% link_in_list /merging-multiple-user-accounts %} {% link_in_list /converting-a-user-into-an-organization %} - {% link_in_list /deleting-your-user-account %} {% link_in_list /permission-levels-for-a-user-account-repository %} {% link_in_list /permission-levels-for-user-owned-project-boards %} {% link_in_list /managing-the-default-branch-name-for-your-repositories %} {% link_in_list /managing-security-and-analysis-settings-for-your-user-account %} - {% link_in_list /managing-access-to-your-user-accounts-project-boards %} - + {% link_in_list /managing-access-to-your-user-accounts-project-boards %} {% link_in_list /integrating-jira-with-your-personal-projects %} - - {% link_in_list /best-practices-for-leaving-your-company %} - - {% link_in_list /what-does-the-available-for-hire-checkbox-do %} - {% topic_link_in_list /managing-email-preferences %} {% link_in_list /adding-an-email-address-to-your-github-account %} {% link_in_list /changing-your-primary-email-address %} {% link_in_list /setting-a-backup-email-address %} {% link_in_list /setting-your-commit-email-address %} - {% link_in_list /blocking-command-line-pushes-that-expose-your-personal-email-address %} - {% link_in_list /remembering-your-github-username-or-email %} - {% link_in_list /types-of-emails-github-sends %} - - {% link_in_list /managing-marketing-emails-from-github %} - {% topic_link_in_list /managing-access-to-your-personal-repositories %} {% link_in_list /inviting-collaborators-to-a-personal-repository %} {% link_in_list /removing-a-collaborator-from-a-personal-repository %} @@ -58,9 +45,7 @@ versions: {% link_in_list /about-organization-membership %} {% link_in_list /accessing-an-organization %} {% link_in_list /viewing-peoples-roles-in-an-organization %} - {% link_in_list /requesting-organization-approval-for-oauth-apps %} - {% link_in_list /publicizing-or-hiding-organization-membership %} {% link_in_list /managing-your-scheduled-reminders %} {% link_in_list /removing-yourself-from-an-organization %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md new file mode 100644 index 0000000000..66f66f6b82 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -0,0 +1,22 @@ +--- +title: Managing your theme settings +intro: You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode. +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Theme settings is currently in beta and subject to change. + +{% endnote %} + +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. + +{% data reusables.user_settings.access_settings %} +1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) + +### Дополнительная литература + +- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md b/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md index e278733ac5..28803d95d9 100644 --- a/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md +++ b/translations/ru-RU/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -Version Effective Date: November 13, 2020 +Version Effective Date: December 14, 2020 When you create an Account, you're given access to lots of different features and products that are all a part of the Service. Because many of these features and products offer different functionality, they may require additional terms and conditions specific to that feature or product. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -46,13 +46,11 @@ GitHub Pages are subject to some specific bandwidth and usage limits, and may no ### 5. Actions and Packages #### a. Actions Usage -GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Each Account comes with included compute and storage quantities for use with Actions, depending on your Account plan, which can be found in the [Actions documentation](/actions). Your Actions compute usage is displayed within [your account settings](https://github.com/settings/billing), and you will be notified by email in advance of reaching the limit of your included quantities. If you want to use Actions beyond your included quantities, then you may [enable overages](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions). +GitHub Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. -Compute usage for included and paid quantities is calculated in minutes based on the type of Actions you execute (e.g. Linux, Windows, macOS). The minutes used for each Action's job or task will be rounded up to the nearest minute. For included quantities and depending on the type of Action, a multiplier may be applied to the amount of time used to execute each job or task, prior to being rounded up to the nearest minute. Overage minutes are charged at the [stated per minute price](https://github.com/features/actions) based on the type of Actions you execute. Actions and Packages share storage, and your storage usage is displayed within your [account settings](https://github.com/settings/billing). For additional details about included quantity usage calculations, see the [Actions documentation](/actions). - -Actions and any elements of the Action service may not be used in violation of the Agreement, the [Acceptable Use Policy](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions [service limitations](/actions/reference/usage-limits-billing-and-administration/#usage-limits). Additionally, Actions should not be used for: +Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions). Additionally, Actions should not be used for: - cryptomining; -- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)) +- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); - the provision of a stand-alone or integrated application or service offering Actions or any elements of Actions for commercial purposes; - any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden); or - any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used. @@ -60,16 +58,7 @@ Actions and any elements of the Action service may not be used in violation of t In order to prevent violations of these limitations and abuse of GitHub Actions, GitHub may monitor your use of GitHub Actions. Misuse of GitHub Actions may result in termination of jobs, or restrictions in your ability to use GitHub Actions. #### b. Packages Usage -GitHub Packages may be used to download, publish, and manage packages of Content. Each Account plan comes with included bandwidth and storage quantities for use with Packages, which can be found in the [Packages documentation](/github/managing-packages-with-github-package-registry/about-github-package-registry). Actions and Packages share storage between the two Service features. Storage and bandwidth usage are displayed within your [account settings](https://github.com/settings/billing), and you will be notified by email in advance of reaching the limit of your included quantities. If you want to use Packages beyond your included bandwidth and storage quantities, then you may [enable overages](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages). - -Bandwidth usage is calculated based on the amount of data transferred out of your repositories through Packages, but package transfers through Actions will not count toward your included or paid quantities. Packages bandwidth usage is limited by the [Acceptable Use Policy](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use), and included bandwidth quantities are determined by your [account plan](https://github.com/pricing). - -Actions and Packages storage usage is shared between the two Service features. Storage usage is calculated as a weighted average over the course of the month and does not reset each month. Public and private repositories have different included storage quantities, and the included quantities for private repositories depend on your [account plan](https://github.com/pricing). - -#### c. Payment and Billing for Actions and Packages -Billing for Actions and Packages is usage-based. Additional quantities of Actions or Packages cannot be purchased separately. For monthly-billed customers, you must have a payment method on file to choose to pay for additional quantities of these Service features. You will be charged on a monthly, recurring basis based on your usage in the preceding month, unless you are billed by invoice. For invoiced customers, you must pay the fees within thirty (30) days of the GitHub invoice date. For customers paying for Service feature overages in advance, unused prepaid minutes will not roll over to the next billing period and will not be refunded. - -You can set a monthly spending limit in your [account settings](https://github.com/settings/billing/cost_management). You will be notified by email in advance of reaching the limit of your included quantities and the designated spending limit of your paid additional quantities. +GitHub Packages is billed on a usage basis. The [Packages documentation](/packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies). ### 6. Learning Lab @@ -108,3 +97,13 @@ We need the legal right to submit your contributions to the GitHub Advisory Data #### b. License to the GitHub Advisory Database The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at or to individual GitHub Advisory Database records used, prefixed by . + +### 13. Корпоративный сервер GitHub + +#### a. SQL Server Images + +You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation may disable SQL Server Images at any time. + +#### b. Third-party components + +The Software includes components licensed to GitHub by third parties, including software whose licenses require GitHub to make the source code for those components available. The source code for such components will be provided upon request. 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 009fbc608c..badb73a01e 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 @@ -191,7 +191,7 @@ Customer’s Affiliates are authorized to use the Products in accordance with th #### 1. Pricing; Fees -**Payment Terms** Our pricing is available at [github.com/pricing](https://github.com/pricing) (unless otherwise negotiated by the parties and stated in an Order Form). Customer agrees to pay the Fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. Customer must pay the Fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If Customer fails to pay any Fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable Order Form or SOW. Customer is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. +**Payment Terms** Our pricing is available at [github.com/pricing](https://github.com/pricing) (unless otherwise negotiated by the parties and stated in an Order Form). Customer agrees to pay the Fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. Customer must pay the Fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If Customer fails to pay any Fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable Order Form or SOW. Customer is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. **Usage-Based Billing** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to purchase paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears, provided that for invoiced customers, paid Service features are billed in advance. See [GitHub Additional Product Terms for details](/github/site-policy/github-additional-product-terms). diff --git a/translations/ru-RU/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/ru-RU/content/github/site-policy/github-enterprise-service-level-agreement.md index efd1e9b9b4..0e9f368e5d 100644 --- a/translations/ru-RU/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/ru-RU/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -8,22 +8,22 @@ versions: free-pro-team: '*' --- -**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the GitHub Enterprise Cloud service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). +**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the applicable GitHub service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). -For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. +For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. ## Uptime Guarantee -“**Uptime**” is the percentage of total possible minutes the Service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the Service. The Uptime calculation for each Service Feature is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. +“**Uptime**” is the percentage of total possible minutes the applicable GitHub service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service. The Uptime calculation for each Service Feature that may be included with the applicable GitHub service is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. -| **Service Feature** | **Uptime Calculation** | **Определения** | **Service Credits Calculation** | -| --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -| The **Service** includes the following Service Features:
      • Вопросы
      • Запросы на слияние
      • Git Operations
      • API Requests
      • Webhooks
      • Pages
      • Actions
      • Packages
      | (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
      • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than or equal to 99.9%, but greater than 99.0%.

        OR

      • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
      | | -| **Actions** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

      “**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | -| **Packages** | Transfers Uptime = same as Actions

      Storage Uptime = 100% - Average Error Rate*

      *The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

      “**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | +| **Service Feature** | **Uptime Calculation** | **Определения** | **Service Credits Calculation** | +| -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | +| **Issues**,
      **Pull Requests**,
      **Git Operations**,
      **API Requests**,
      **Webhooks**,
      **Pages** | (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
      • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than or equal to 99.9%, but greater than 99.0%.

        OR

      • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
      | | +| **Actions** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

      “**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | +| **Packages** | Transfers Uptime = same as Actions

      Storage Uptime = 100% - Average Error Rate*

      *The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

      “**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | ## Exclusions -Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. +Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the applicable GitHub service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## Service Credits Redemption If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). diff --git a/translations/ru-RU/content/github/site-policy/github-registered-developer-agreement.md b/translations/ru-RU/content/github/site-policy/github-registered-developer-agreement.md index 98c90d694d..234ef5d9f0 100644 --- a/translations/ru-RU/content/github/site-policy/github-registered-developer-agreement.md +++ b/translations/ru-RU/content/github/site-policy/github-registered-developer-agreement.md @@ -86,7 +86,7 @@ This Agreement is a legal agreement between you (“you”) and GitHub, Inc. ( 13. **Proprietary Rights** - You agree that GitHub and its licensors own all right, title and interest in and to the API, the Pre-release Materials, and all other GitHub products and services; all information and data relating to their configurations and combinations; and all modifications to and derivative works of any of the foregoing. You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other other GitHub products and services. + You agree that GitHub and its licensors own all right, title and interest in and to the API, the Pre-release Materials, and all other GitHub products and services; all information and data relating to their configurations and combinations; and all modifications to and derivative works of any of the foregoing. You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services. 14. **Government Users** 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 49d85bf15b..cc0eaae72c 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 @@ -9,7 +9,9 @@ versions: ### About {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.sponsorship-details %} {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." +{% data reusables.sponsors.sponsorship-details %} + +{% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." {% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[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)." @@ -25,7 +27,7 @@ When you become a sponsored developer or sponsored organization, additional term {% endnote %} -The {% data variables.product.prodname_matching_fund %} aims to benefit members of the {% data variables.product.prodname_dotcom %} community who develop open source software that promotes the [{% data variables.product.prodname_dotcom %} Community Guidelines](/github/site-policy/github-community-guidelines). Sponsored organizations are not eligible for {% data variables.product.prodname_matching_fund %}. +The {% data variables.product.prodname_matching_fund %} aims to benefit members of the {% data variables.product.prodname_dotcom %} community who develop open source software that promotes the [{% data variables.product.prodname_dotcom %} Community Guidelines](/github/site-policy/github-community-guidelines). Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}. To be eligible for the {% data variables.product.prodname_matching_fund %}, you must create a profile that will attract a community that will sustain you for the long term. For more information about creating a strong 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)." @@ -35,8 +37,6 @@ To be eligible for the {% data variables.product.prodname_matching_fund %}, you 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). -Currently, only individual users can sponsor developers and organizations. If your organization is interested in sponsoring developers, please let us know by contacting [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). - ### Дополнительная литература - "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" - "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)" diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md new file mode 100644 index 0000000000..57b1b5a4d6 --- /dev/null +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md @@ -0,0 +1,13 @@ +--- +title: Attributing sponsorships to your organization +intro: 'You can attribute the sponsorships paid by one of your organizations to another organization.' +versions: + free-pro-team: '*' +permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization. +--- + +1. Navigate to the organization whose sponsorships you want to attribute to another organization. +1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png) +1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png) +1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png) +1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md index 4bed524e3c..f9b176f55d 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -13,38 +13,20 @@ versions: {% data reusables.sponsors.maximum-tier %} -### Adding a tier for your sponsored developer profile +### Adding a tier -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} -### Adding a tier for your sponsored organization profile +### Editing or retiring a tier -{% data reusables.sponsors.navigate-to-org-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 for your sponsored developer profile - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} - -### Editing or retiring a tier for your sponsored organization profile - -{% data reusables.sponsors.navigate-to-org-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 %} +{% data reusables.sponsors.retire-tier %} \ No newline at end of file diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md index ba6e771ba3..0cae836a8f 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md @@ -5,11 +5,13 @@ versions: free-pro-team: '*' --- -To monitor changes to your sponsorships, such as cancellations at the end of a pay period, you can create webhooks for your sponsored user or organization account. When you set up a webhook for your sponsored user or organization account, you'll receive updates when sponsorships are created, edited, or deleted. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship). +### About webhooks for events in your sponsored account -### Managing webhooks for your sponsored user account +To monitor changes to your sponsorships, such as cancellations at the end of a pay period, you can create webhooks for your sponsored user or organization account. When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. For more information, see the [`sponsorship` webhook event](/webhooks/event-payloads/#sponsorship). -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +### Managing webhooks for events in your sponsored account + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-webhooks-tab %} {% data reusables.sponsors.add-webhook %} {% data reusables.sponsors.add-payload-url %} @@ -17,18 +19,4 @@ To monitor changes to your sponsorships, such as cancellations at the end of a p {% data reusables.sponsors.webhook-secret-token %} {% data reusables.sponsors.add-active-triggers %} {% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} - -### Managing webhooks for your sponsored organization - -Organization owners can configure webhooks for a sponsored organization. - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-webhooks-tab %} -{% data reusables.sponsors.add-webhook %} -{% data reusables.sponsors.add-payload-url %} -{% data reusables.sponsors.webhook-content-formatting %} -{% data reusables.sponsors.webhook-secret-token %} -{% data reusables.sponsors.add-active-triggers %} -{% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} +{% data reusables.sponsors.manage-existing-webhooks %} \ No newline at end of file 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 80e23f3cf5..640d965448 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 @@ -7,22 +7,15 @@ versions: free-pro-team: '*' --- +### About sponsorship updates + Your sponsors can choose whether they receive email updates about your work. For more information, see "[Managing your sponsorship](/articles/managing-your-sponsorship)." -The update will come from your user account's primary email address or organization account's `noreply@github.com` email address. If you've enabled email address privacy on your user account, the update will come from `noreply@github.com` instead. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +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)." -### Contacting your user account's sponsors +### Contacting your sponsors -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.sponsors-updates-tab %} -{% data reusables.sponsors.draft-new-update %} -{% data reusables.sponsors.send-update-to-sponsors %} -{% data reusables.sponsors.write-sponsor-update %} -{% data reusables.sponsors.publish-sponsor-update %} - -### Contacting your organization's sponsors - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.sponsors-updates-tab %} {% data reusables.sponsors.draft-new-update %} {% data reusables.sponsors.send-update-to-sponsors %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md index e841276f04..53004b7463 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md @@ -10,30 +10,17 @@ versions: ### About sponsor profiles -Your {% data variables.product.prodname_sponsors %} profile tells potential sponsors why they should support you. People see your sponsor profile when they click the **Sponsor** button on your personal or organization profile. We recommend including the following information. +Your {% data variables.product.prodname_sponsors %} profile tells potential sponsors why they should support you. People see your sponsor profile when they click the **Sponsor** button on your profile. We recommend including the following information. -- Open source work that you contribute to. -- Why you are committed to open source development. +- Open source work that you contribute to +- Why you are committed to open source development -You can also set goals to explain what different of levels of sponsorship will allow you to do for the community. +### Editing your profile details -### Editing your sponsored developer profile - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### Editing your sponsored organization profile - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.meet-the-team %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} +{% data reusables.sponsors.save-profile %} \ No newline at end of file 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 def51bcb47..48892ef8f2 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 @@ -16,6 +16,7 @@ versions: {% topic_link_in_list /sponsoring-open-source-contributors %} {% link_in_list /sponsoring-an-open-source-contributor %} {% link_in_list /managing-your-sponsorship %} + {% link_in_list /attributing-sponsorships-to-your-organization %} {% topic_link_in_list /receiving-sponsorships-through-github-sponsors %} {% link_in_list /about-github-sponsors-for-open-source-contributors %} {% link_in_list /setting-up-github-sponsors-for-your-user-account %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md index 295daca888..abfed9bd2c 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md @@ -13,14 +13,8 @@ You can only manage your payouts from {% data variables.product.prodname_sponsor {% data reusables.sponsors.payout-info %} -### Viewing and editing payout information for your sponsored user account +### Viewing and editing payout information -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} - -### Viewing and editing payout information for your sponsored organization - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} +{% data reusables.sponsors.edit-bank-information %} \ No newline at end of file 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 07a67e1a88..a4d3bdc206 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 @@ -1,27 +1,19 @@ --- title: Managing your sponsorship goal -intro: You can set a goal for your sponsored developer or sponsored organization profile to help the community understand the impact of sponsoring you. +intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you. versions: free-pro-team: '*' --- ### About sponsorship goals -You can set a funding goal for your sponsored developer or organization profile and share the goal with your community. Goals help you understand the impact you have in the open source community and build up your presence in the {% data variables.product.prodname_sponsors %} program. +You can set a funding goal for your sponsored account and share the goal with your community. Goals help you understand the impact you have in the open source community and build up your presence in the {% data variables.product.prodname_sponsors %} program. 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. -### Setting a goal for a sponsored organization +### Setting a goal -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.set-a-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### Setting a goal for a sponsored developer - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.set-a-goal %} {% data reusables.sponsors.select-goal-type %} @@ -31,6 +23,7 @@ Your goal can set a target for the number of sponsors you want to have or the am When you edit a goal, you can't choose a goal you've already achieved. For example, if you already have 5 sponsors, you can't edit your goal so that you're aiming for 4 sponsors. +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.select-goal-type %} @@ -40,6 +33,7 @@ When you edit a goal, you can't choose a goal you've already achieved. For examp After you retire a goal, you won't be able to reactivate the goal. You must create a new goal instead. +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.retire-goal %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md index 17c1100ced..7c07733adb 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -1,42 +1,35 @@ --- title: Managing your sponsorship -intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored open source contributor. +intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account. redirect_from: - /articles/managing-your-sponsorship versions: free-pro-team: '*' --- -For information about changing your sponsorship tier, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)." +{% data reusables.sponsors.org-sponsors-release-phase %} -### Managing the privacy setting for your developer sponsorship +### Managing the privacy setting for your sponsorship -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} {% data reusables.sponsors.who-can-see-your-sponsorship %} {% data reusables.sponsors.update-sponsorship %} -### Managing the privacy setting for your organization sponsorship +### Managing email updates for your sponsorship -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.who-can-see-your-sponsorship %} +You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address. + +{% data reusables.sponsors.manage-updates-for-orgs %} + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} +{% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.update-sponsorship %} -### Managing email updates from a sponsored developer +### Дополнительная литература -You can choose whether a sponsored developer can send you email updates about their work. The sponsored developer will not have access to your email address. - -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} -{% data reusables.sponsors.developer-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} - -### Managing email updates from a sponsored organization - -You can choose whether a sponsored organization can send you email updates about their work. The sponsored organization will not have access to your email address. - -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.org-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} +- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" +- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)" \ No newline at end of file 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 6d38f23277..4d3d78e15e 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 @@ -25,7 +25,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu ### Completing your sponsored organization profile -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% 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 %} @@ -54,7 +54,7 @@ As a sponsored organization, you must receive payouts to a dedicated bank accoun {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} For more information about setting up Stripe Connect using Open Collective, see [Setting up {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) in the Open Collective Docs. @@ -63,7 +63,7 @@ For more information about setting up Stripe Connect using Open Collective, see {% data reusables.sponsors.tax-form-information-org %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -75,7 +75,7 @@ Before your organization can become a sponsored organization, you must enable 2F ### Submitting your application to {% data variables.product.prodname_dotcom %} for approval -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %} {% data reusables.sponsors.github-review-app %} 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 f11ff74a9a..e47f54497f 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 @@ -26,7 +26,7 @@ If you have a bank account in a supported region, {% data variables.product.prod After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you. -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ After {% data variables.product.prodname_dotcom %} reviews your application, you {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} @@ -54,14 +54,14 @@ If you live in a supported region, you can follow these instructions to submit y {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} ### Submitting your tax information {% data reusables.sponsors.tax-form-information-dev %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -73,7 +73,7 @@ Before you can become a sponsored developer, you must enable 2FA on your {% data ### Submitting your application to {% data variables.product.prodname_dotcom %} for approval -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 4. Click **Request approval**. ![Request approval button](/assets/images/help/sponsors/request-approval-button.png) {% data reusables.sponsors.github-review-app %} 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 8fb3e7686c..69bff67d4a 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 @@ -7,17 +7,32 @@ redirect_from: - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer versions: free-pro-team: '*' +permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization. --- -### About sponsoring developers and organizations +{% data reusables.sponsors.org-sponsors-release-phase %} -{% data reusables.sponsors.sponsorship-details %} {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." +### About sponsorships -When you sponsor an open source contributor, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} +{% data reusables.sponsors.sponsorship-details %} -If the sponsored open source contributor retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. For more information, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)." +You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons. +- Sustaining specific libraries that your organization's work depends on +- Investing in the ecosystem you rely on as a organization (such as blockchain) +- Developing brand awareness as an organization that values open source +- Thanking open source developers for building libraries that complement the product your organization offers -If the open source contributor you want to sponsor does not have a sponsored developer or organization profile, you can encourage the contributor to create a sponsored developer or organization profile. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). + +{% data 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 %} + +{% data reusables.sponsors.manage-updates-for-orgs %} + +If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. For more information, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)." + +If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data reusables.sponsors.sponsorships-not-tax-deductible %} @@ -27,30 +42,20 @@ If the open source contributor you want to sponsor does not have a sponsored dev {% endnote %} -### Sponsoring a developer +### Sponsoring an account -Before you can sponsor a developer, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)." +Before you can sponsor an account, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)." -1. On {% data variables.product.product_name %}, navigate to the profile of the person you want to sponsor. -2. Under the developer's name, click **Sponsor**. ![Sponsor button](/assets/images/help/profile/sponsor-button.png) +1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor. +1. Navigate to your sponsorship dashboard for the account. + - To sponsor a developer, under the developer's name, click **Sponsor**. ![Sponsor button](/assets/images/help/profile/sponsor-button.png) + - To sponsor an organization, to the right of the 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.select-a-tier %} +{% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} ![Edit payment button](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) {% data reusables.sponsors.who-can-see-your-sponsorship %} ![Radio buttons to choose who can see your sponsorship](/assets/images/help/sponsors/who-can-see-sponsorship.png) -{% data reusables.sponsors.developer-sponsored-choose-updates %} -7. Click **Sponsor _DEVELOPER_**. ![Sponsor developer button](/assets/images/help/sponsors/sponsor-developer-button.png) - -### Sponsoring an organization - -Before you can sponsor an organization, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)." - -1. On {% data variables.product.product_name %}, navigate to the page of the organization you want to sponsor. -2. Next to the the organization's name, click **Sponsor**. ![Sponsor button](/assets/images/help/sponsors/sponsor-org-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.select-sponsorship-billing %} - ![Edit payment button](/assets/images/help/sponsors/edit-org-sponsorship-payment-button.png) -{% data reusables.sponsors.who-can-see-your-sponsorship %} - ![Radio buttons to choose who can see your sponsorship](/assets/images/help/sponsors/who-can-see-org-sponsorship.png) -{% data reusables.sponsors.org-sponsored-choose-updates %} -7. Click **Sponsor _ORGANIZATION_**. ![Sponsor organization button](/assets/images/help/sponsors/sponsor-org-confirm-button.png) +{% data reusables.sponsors.choose-updates %} +{% data reusables.sponsors.sponsor-account %} diff --git a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 8504c6fad5..62daa89c40 100644 --- a/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/ru-RU/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -7,34 +7,25 @@ versions: free-pro-team: '*' --- +### About sponsors and sponsorships + You can view analytics on your current and past sponsorships, the payments you've received from sponsors, and events, such as cancellations and sponsor tier changes for your sponsorships. You can also view activity such as new sponsorships, changes to sponsorships, and canceled sponsorships. You can filter the list of activities by date. You can also export sponsorship data for the account you're viewing in CSV or JSON format. -You access all of this information from your Sponsors dashboard. - -### Viewing your Sponsors dashboard - -1. In the upper-right corner of any page, click your profile photo, then click **{% data variables.product.prodname_sponsors %}**. ![{% data variables.product.prodname_sponsors %} button](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. In the list that's displayed, to the right of the account or organization whose Sponsors dashboard you want to view, click **Dashboard**. ![Developer sponsors dashboard button](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) - ### Viewing your sponsors and sponsorships -1. Go to your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard). -{% data reusables.sponsors.navigate-to-sponsors-tab %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. Optionally, to filter your sponsors by tier, use the **Filter** drop-down menu, click **Active tiers** or **Retired tiers**, and select a tier. ![Drop-down menu to filter by tier](/assets/images/help/sponsors/filter-drop-down.png) ### Viewing recent sponsorship activity -1. Go to your your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard). +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. In the left sidebar, click **Activity**. ![Activity tab](/assets/images/help/sponsors/activity-tab.png) ### Exporting your sponsorship data -1. Go to your your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard). +If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsors-tab %} 1. Click **Export all**. ![Export all button](/assets/images/help/sponsors/export-all.png) - - This button is not displayed if you don't have any sponsors. - -1. Choose a timeframe and a format for the data you'd like to export, then click **Start export**. ![Options for data export](/assets/images/help/sponsors/export-your-sponsors.png) - - {% data variables.product.prodname_dotcom %} starts exporting data for all of your sponsors for the month you selected. You'll be emailed shortly with an attachment containing the data. After the export is complete you can export another month of data. You can export up to 10 sets of data an hour for any of your sponsored organizations or user accounts. +1. Choose a timeframe and a format for the data you'd like to export, then click **Start export**. ![Options for data export](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/ru-RU/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/ru-RU/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 092b539416..767490b515 100644 --- a/translations/ru-RU/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/ru-RU/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -36,7 +36,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist {% endwindows %} - `BRANCH-NAME`: The default branch for your current project, for example, `main` or `gh-pages`. ```shell - $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME + $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME # Filter the specified branch in your directory and remove empty commits > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) > Ref 'refs/heads/BRANCH-NAME' was rewritten 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 cb87848239..66e7dac8c1 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 @@ -21,6 +21,11 @@ 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)." +{% 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: @@ -41,7 +46,8 @@ 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. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +- 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 diff --git a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/index.md b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/index.md index fb095cfc5f..bbe4472b6b 100644 --- a/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/index.md +++ b/translations/ru-RU/content/github/visualizing-repository-data-with-graphs/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repository-graphs %} {% link_in_list /viewing-a-summary-of-repository-activity %} {% link_in_list /viewing-a-projects-contributors %} - {% link_in_list /viewing-traffic-to-a-repository %} - {% topic_link_in_list /analyzing-changes-to-a-repositorys-content %} {% link_in_list /visualizing-commits-in-a-repository %} {% link_in_list /visualizing-additions-and-deletions-to-content-in-a-repository %} {% topic_link_in_list /understanding-connections-between-repositories %} {% link_in_list /viewing-a-repositorys-network %} {% link_in_list /listing-the-forks-of-a-repository %} - {% link_in_list /about-the-dependency-graph %} {% link_in_list /exploring-the-dependencies-of-a-repository %} - diff --git a/translations/ru-RU/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/ru-RU/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index 85593b8030..6425b245ec 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/ru-RU/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -51,7 +51,7 @@ Your theme includes default layouts, includes, and stylesheets that will automat 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: page + layout: post title: "POST TITLE" date: YYYY-MM-DD hh:mm:ss -0000 categories: CATEGORY-1 CATEGORY-2 diff --git a/translations/ru-RU/content/github/working-with-github-pages/index.md b/translations/ru-RU/content/github/working-with-github-pages/index.md index 33410c9e3c..ce33893982 100644 --- a/translations/ru-RU/content/github/working-with-github-pages/index.md +++ b/translations/ru-RU/content/github/working-with-github-pages/index.md @@ -23,15 +23,11 @@ versions: {% topic_link_in_list /getting-started-with-github-pages %} {% link_in_list /about-github-pages %} {% link_in_list /creating-a-github-pages-site %} - {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} - {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} - {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} - {% link_in_list /unpublishing-a-github-pages-site %} {% topic_link_in_list /setting-up-a-github-pages-site-with-jekyll %} {% link_in_list /about-github-pages-and-jekyll %} @@ -42,9 +38,7 @@ versions: {% link_in_list /adding-a-theme-to-your-github-pages-site-using-jekyll %} {% link_in_list /about-jekyll-build-errors-for-github-pages-sites %} {% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %} - {% topic_link_in_list /configuring-a-custom-domain-for-your-github-pages-site %} {% link_in_list /about-custom-domains-and-github-pages %} {% link_in_list /managing-a-custom-domain-for-your-github-pages-site %} {% link_in_list /troubleshooting-custom-domains-and-github-pages %} - diff --git a/translations/ru-RU/content/github/working-with-github-support/index.md b/translations/ru-RU/content/github/working-with-github-support/index.md index 176ea10515..1ea83fac6b 100644 --- a/translations/ru-RU/content/github/working-with-github-support/index.md +++ b/translations/ru-RU/content/github/working-with-github-support/index.md @@ -2,6 +2,7 @@ title: Working with GitHub Support redirect_from: - /categories/working-with-github-support + - /forum versions: free-pro-team: '*' --- diff --git a/translations/ru-RU/content/graphql/README.md b/translations/ru-RU/content/graphql/README.md new file mode 100644 index 0000000000..f29fbc5131 --- /dev/null +++ b/translations/ru-RU/content/graphql/README.md @@ -0,0 +1,10 @@ +# GraphQL + +The `/content/graphql` directory is where the GitHub GraphQL API docs live! + +* The `/content/graphql/guides` and `/content/graphql/overview` directories contain articles that are human-editable. +* The `/content/graphql/reference` directory contains an article for each GraphQL data type used in the GitHub GraphQL API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/graphql/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/graphql/README.md`](/lib/graphql/README.md). + + **As a result, we cannot accept contributions to GraphQL API reference content in this repository.** diff --git a/translations/ru-RU/content/graphql/overview/explorer.md b/translations/ru-RU/content/graphql/overview/explorer.md index e317574b03..ba81e4808e 100644 --- a/translations/ru-RU/content/graphql/overview/explorer.md +++ b/translations/ru-RU/content/graphql/overview/explorer.md @@ -7,6 +7,6 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +layout: graphql-explorer --- -You can access GitHub's GraphQL Explorer at https://developer.github.com/v4/explorer. diff --git a/translations/ru-RU/content/packages/guides/about-github-container-registry.md b/translations/ru-RU/content/packages/guides/about-github-container-registry.md new file mode 100644 index 0000000000..e2b0fb0927 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/about-github-container-registry.md @@ -0,0 +1,94 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/about-github-container-registry + - /packages/managing-container-images-with-github-container-registry +versions: + free-pro-team: '*' +--- + +{% note %} + +**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)." + +{% endnote %} + +### About {% 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)." + +{% data variables.product.prodname_github_container_registry %} has different hosting locations, permission, and visibility than other package registries. + +| | 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. + +For more information, see "[About scopes and permissions for {% data variables.product.prodname_github_container_registry %}](#about-scopes-and-permissions-for-github-container-registry)." + +### Supported formats + +The {% data variables.product.prodname_container_registry %} currently supports the following container image formats: + +* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec) + +The {% data variables.product.prodname_github_container_registry %} hosts containers at `ghcr.io/OWNER/IMAGE-NAME`. + +| Package client | Language | Package format | Description | +| -------------- | -------- | ----------------- | ------------------------- | +| Docker CLI | Нет | `Файл Dockerfile` | Docker container support. | + + +#### Manifest Lists/Image Indexes + +{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications. + +### Visibility and access permissions for container images + +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. + +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. + +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. + +| 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. | + +For more information, see "[Configuring access control and visibility for container images](/packages/guides/configuring-access-control-and-visibility-for-container-images)." + +### About scopes and permissions for {% data variables.product.prodname_github_container_registry %} + +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. + +| 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)." | + +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)." + +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)." + +### About billing for {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.billing-for-container-registry %} + +### Contacting support + +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). + +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: + +* 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. diff --git a/translations/ru-RU/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md b/translations/ru-RU/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md new file mode 100644 index 0000000000..1d66526320 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md @@ -0,0 +1,69 @@ +--- +title: Configuring access control and visibility for container images +intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### Configuring access to container images for your personal account + +If you have admin permissions to a user-account owned container image, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)." + +{% data reusables.package_registry.package-settings-from-user-level %} +1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a user account. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) +1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) + +The selected users will automatically be given access and don't need to accept an invitation first. + +### Configuring access to container images for an organization + +If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)." + +If your package is owned by an organization and private, then you can only give access to other organization members or teams. + +For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% data reusables.package_registry.package-settings-from-org-level %} +1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) +1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) + +The selected users or teams will automatically be given access and don't need to accept an invitation first. + +### Configuring visibility of container images for your personal account + +When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings. + +A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. + +{% data reusables.package_registry.package-settings-from-user-level %} +5. Under "Danger Zone", choose a visibility setting: + - To make the container image visible to anyone, click **Make public**. + {% warning %} + + **Warning:** Once you make a package public, you cannot make it private again. + + {% endwarning %} + - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) + +### Configuring visibility of container images for an organization + +When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings. + +A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. + +For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +{% data reusables.package_registry.package-settings-from-org-level %} +5. Under "Danger Zone", choose a visibility setting: + - To make the container image visible to anyone, click **Make public**. + {% warning %} + + **Warning:** Once you make a package public, you cannot make it private again. + + {% endwarning %} + - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/ru-RU/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md new file mode 100644 index 0000000000..1a8ae48f06 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -0,0 +1,195 @@ +--- +title: Configuring Apache Maven for use with GitHub Packages +intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Authenticating to {% 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 Apache Maven by editing your *~/.m2/settings.xml* file to include your personal access token. Create a new *~/.m2/settings.xml* file if one doesn't exist. + +In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your personal access token. + +In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}*REPOSITORY* with the name of the repository you'd like to publish a package to or install a package from, and *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. + +If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag. + +{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` +{% endif %} + +#### 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, {% data variables.product.prodname_dotcom %} will publish a package named `com.example:test` in a repository called `OWNER/test`. + +If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository. + +For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). + +1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing + +{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation enabled: + {% endif %} + ``` + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + ``` + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation disabled: + ``` + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + ``` + {% endif %} +2. Publish the package. + + ```shell + $ mvn deploy + ``` + +{% data reusables.package_registry.viewing-packages %} + +### Installing a package + +To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation. + +{% data reusables.package_registry.authenticate-step %} +2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package. + + ``` + + + com.example + test + 1.0.0-SNAPSHOT + + + ``` +3. Install the package. + + ```shell + $ mvn install + ``` + +### Дополнительная литература + +- "[Configuring Gradle for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-gradle-for-use-with-github-packages)" +- "[Deleting a package](/packages/manage-packages/deleting-a-package/)" diff --git a/translations/ru-RU/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-docker-for-use-with-github-packages.md new file mode 100644 index 0000000000..eafc9638b3 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -0,0 +1,213 @@ +--- +title: Configuring Docker for use with GitHub Packages +intro: 'You can configure the Docker client to use {% data variables.product.prodname_registry %} to publish and retrieve docker images.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### About Docker and {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. + +{% if enterpriseServerVersions contains currentVersion %} + +Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." + +{% endif %} + +### Authenticating to {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Authenticating with a personal access token + +{% data reusables.package_registry.required-scopes %} + +You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command. + +To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file. + +{% if currentVersion == "free-pro-team@latest" %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + ``` +{% endraw %} +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + +To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if enterpriseServerVersions contains currentVersion %}, `HOSTNAME` with the URL for {% data variables.product.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. + +For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)." + +#### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publishing an image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% note %} + +**Note:** Image names must only use lowercase letters. + +{% endnote %} + +{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. + +{% data reusables.package_registry.viewing-packages %} + +1. Determine the image name and ID for your docker image using `docker images`. + ```shell + $ docker images + > < > + > REPOSITORY TAG IMAGE ID CREATED SIZE + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + ``` +2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} +3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time, +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% else %} + ```shell + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} +4. Publish the image to +{% data variables.product.prodname_registry %}. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} + {% note %} + + **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. + + {% endnote %} + +#### Example publishing a Docker image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} + +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` + +{% endif %} + +You can publish a new Docker image for the first time and name it `monalisa`. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +# Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} +```shell +# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` +{% endif %} + +### Downloading an image + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %} and *TAG_NAME* with tag for the image you want to install. + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% else %} +```shell +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} + +{% note %} + +**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. + +{% endnote %} + +### Дополнительная литература + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ru-RU/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md new file mode 100644 index 0000000000..ad3f8a39b5 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -0,0 +1,196 @@ +--- +title: Configuring `dotnet` CLI for use with GitHub Packages +intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages + - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Authenticating to {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +#### Authenticating with a personal access token + +{% data reusables.package_registry.required-scopes %} + +To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client. + +You must replace: +- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}. +- `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 %} +- `HOSTNAME` with the host name for your {% data variables.product.prodname_ghe_server %} instance. + +If your instance has subdomain isolation enabled: +{% endif %} + +```xml + + + + + + + + + + + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```xml + + + + + + + + + + + + + +``` +{% endif %} + +#### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publishing a package + +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file. When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Create a new project. + ```shell + dotnet new console --name OctocatApp + ``` +3. Add your project's specific information to your project's file, which ends in *.csproj*. You must replace: + - `OWNER` with the name of the user or organization account that owns the repository containing your project. + - `REPOSITORY` with the name of the repository containing the package you want to publish. + - `1.0.0` with the version number of the package.{% if enterpriseServerVersions contains currentVersion %} + - `HOSTNAME` with the host name for your {% data variables.product.prodname_ghe_server %} instance.{% endif %} + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + ``` +4. Package the project. + ```shell + dotnet pack --configuration Release + ``` + +5. Publish the package using the `key` you specified in the *nuget.config* file. + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" + ``` + +### Publishing multiple packages to the same repository + +To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. + +For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository: + +``` xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +### Installing a package + +Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. + +{% data reusables.package_registry.authenticate-step %} + +2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use: + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + ``` + +3. Install the packages with the `restore` command. + ```shell + dotnet restore + ``` + +### Дополнительная литература + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ru-RU/content/packages/guides/configuring-gradle-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-gradle-for-use-with-github-packages.md new file mode 100644 index 0000000000..3b025736b9 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/configuring-gradle-for-use-with-github-packages.md @@ -0,0 +1,215 @@ +--- +title: Configuring Gradle for use with GitHub Packages +intro: 'You can configure Gradle to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Authenticating to {% 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 Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your personal access token. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository. + +{% if enterpriseServerVersions contains currentVersion %} +Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your +{% data variables.product.prodname_ghe_server %} instance. +{% endif %} + +Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. + +{% note %} + +**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)." + +{% endnote %} + +##### Example using Gradle Groovy for a single package in a repository + +```shell +plugins { + id("maven-publish") +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } +} +``` + +##### Example using Gradle Groovy for multiple packages in the same repository + +```shell +plugins { + id("maven-publish") apply false +} + +subprojects { + apply plugin: "maven-publish" + publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } + } +} +``` + +##### Example using Kotlin DSL for a single package in the same repository + +```shell +plugins { + `maven-publish` +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } +} +``` + +##### Example using Kotlin DSL for multiple packages in the same repository + +```shell +plugins { + `maven-publish` apply false +} + +subprojects { + apply(plugin = "maven-publish") + configure { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } + } +} +``` + + #### Authenticating with the `GITHUB_TOKEN` + + {% data reusables.package_registry.package-registry-with-github-tokens %} + + For more information about using `GITHUB_TOKEN` with Maven, see "[Publishing Java packages with Maven](/actions/language-and-framework-guides/publishing-java-packages-with-maven#publishing-packages-to-github-packages)." + + ### Publishing a package + + {% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository. + + {% data reusables.package_registry.viewing-packages %} + + {% data reusables.package_registry.authenticate-step %} + 2. After creating your package, you can publish the package. + + ```shell + $ gradle publish + ``` + +### Installing a package + +You can install a package by adding the package as a dependency to your project. For more information, see "[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" in the Gradle documentation. + +{% data reusables.package_registry.authenticate-step %} +2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. + + Example using Gradle Groovy: + ```shell + dependencies { + implementation 'com.example:package' + } + ``` + Example using Kotlin DSL: + ```shell + dependencies { + implementation("com.example:package") + } + ``` + +3. Add the maven plugin to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. + + Example using Gradle Groovy: + ```shell + plugins { + id 'maven' + } + ``` + Example using Kotlin DSL: + ```shell + plugins { + `maven` + } + ``` + + 3. Install the package. + + ```shell + $ gradle install + ``` + +### Дополнительная литература + +- "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)" +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ru-RU/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-npm-for-use-with-github-packages.md new file mode 100644 index 0000000000..838e7835cb --- /dev/null +++ b/translations/ru-RU/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -0,0 +1,200 @@ +--- +title: Configuring npm for use with GitHub Packages +intro: 'You can configure npm to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in an npm project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Authenticating to {% 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 npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token. + +To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +//HOSTNAME/_registry/npm/:_authToken=TOKEN +``` +{% endif %} + +To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address. + +If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +$ npm login --scope=@OWNER --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} + +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +#### Authenticating with the `GITHUB_TOKEN` + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### Publishing a package + +{% note %} + +**Note:** Package names and scopes must only use lowercase letters. + +{% endnote %} + +By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. You can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation. + +You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)." + +You can set up the scope mapping for your project using either a local *.npmrc* file in the project or using the `publishConfig` option in the *package.json*. {% data variables.product.prodname_registry %} only supports scoped npm packages. Scoped packages have names with the format of `@owner/name`. Scoped packages always begin with an `@` symbol. You may need to update the name in your *package.json* to use the scoped name. For example, `"name": "@codertocat/hello-world-npm"`. + +{% data reusables.package_registry.viewing-packages %} + +#### Publishing a package using a local *.npmrc* file + +You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +1. Verify the name of your package in your project's *package.json*. The `name` field must contain the scope and the name of the package. For example, if your package is called "test", and you are publishing to the "My-org" +{% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`. +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +#### Publishing a package using `publishConfig` in the *package.json* file + +You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation. + +1. Edit the *package.json* file for your package and include a `publishConfig` entry. + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation enabled: + {% endif %} + ```shell + "publishConfig": { + "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + }, + ``` + {% if enterpriseServerVersions contains currentVersion %} + If your instance has subdomain isolation disabled: + ```shell + "publishConfig": { + "registry":"https://HOSTNAME/_registry/npm/" + }, + ``` + {% endif %} +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +### Publishing multiple packages to the same repository + +To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package. + +To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. + +{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name. + +```shell +"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", +``` + +### Installing a package + +You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation. + +By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." + +You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency. + + ``` + { + "name": "@my-org/server", + "version": "1.0.0", + "description": "Server app that uses the @octo-org/octo-app package", + "main": "index.js", + "author": "", + "license": "MIT", + "dependencies": { + "@octo-org/octo-app": "1.0.0" + } + } + ``` +5. Install the package. + + ```shell + $ npm install + ``` + +#### Installing packages from other organizations + +By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation enabled: +{% endif %} + +```shell +registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}/OWNER +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +``` + +{% if enterpriseServerVersions contains currentVersion %} +If your instance has subdomain isolation disabled: + +```shell +registry=https://HOSTNAME/_registry/npm/OWNER +@OWNER:registry=https://HOSTNAME/_registry/npm/ +@OWNER:registry=https://HOSTNAME/_registry/npm/ +``` +{% endif %} + +### Дополнительная литература + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ru-RU/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md b/translations/ru-RU/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md new file mode 100644 index 0000000000..68f9e49703 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -0,0 +1,149 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Требования + +- You must have rubygems 2.4.1 or higher. To find your rubygems version: + + ```shell + $ gem --version + ``` + + - You must have bundler 1.6.4 or higher. To find your Bundler version: + ```shell + $ bundle --version + Bundler version 1.13.7 + ``` + + - Install keycutter to manage multiple credentials. To install keycutter: + ```shell + $ gem install keycutter + ``` + +### Authenticating to {% 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. + +```shell +--- +:github: Bearer TOKEN +``` + +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. + +```shell +--- +:backtrace: false +:bulk_threshold: 1000 +:sources: +- https://rubygems.org/ +- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ +:update_sources: true +:verbose: true + +``` + +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 %} + +```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. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Build the package from the *gemspec* to create the *.gem* package. + ```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 %} + + ```shell + $ gem push --key github \ + --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem + ``` + +### 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.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 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 %} + + ``` + source "https://rubygems.org" + + gem "rails" + + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do + gem "GEM NAME" + end + ``` + +3. 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). + + ``` + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" + source "https://rubygems.org" + + gem "rails" + gem "GEM NAME" + ``` + +4. Install the package: + ```shell + $ gem install octo-gem --version "0.1.1" + ``` + +### Дополнительная литература + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/ru-RU/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/ru-RU/content/packages/guides/connecting-a-repository-to-a-container-image.md new file mode 100644 index 0000000000..2ae7987139 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -0,0 +1,83 @@ +--- +title: Connecting a repository to a container image +intro: 'You can link a repository with a container image locally and on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image +versions: + free-pro-team: '*' +--- + +When you link a container image with a repository, the package landing page will show information and links from the repository, such as the README. + +To connect a repository and a container image on {% data variables.product.prodname_dotcom %}, they must share the same owner on {% data variables.product.prodname_dotcom %}. For example, both `my_repo` and `hello_docker` are owned by the user `monalisa`: +```shell +https://github.com/monalisa/my_repo +https://github.com/monalisa/hello_docker +``` + +### Connecting a repository to a user-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Connecting a repository to an organization-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### Connecting a repository to a container image on the command line + +1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details: + + ```shell + LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + ``` + For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile: + ```shell + LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + ``` + For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. + +2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`. + + ```shell + $ docker build -t hello_docker . + ``` +3. Optionally, review details for the Docker image you want to tag. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +4. Tag your Docker image with your desired image name and hosting destination. + ```shell + $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG + ``` + Например: + ```shell + $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest + ``` + +5. If you haven't already, authenticate to + +{% data variables.product.prodname_github_container_registry %}. For more information, see "[Authenticating to GitHub Container Registry](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-github-container-registry)." + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + > Login Succeeded + ``` + {% endraw %} +6. Push your container image to {% data variables.product.prodname_github_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG + ``` + Например: + ```shell + $ docker push ghcr.io/monalisa/hello_docker:latest + ``` diff --git a/translations/ru-RU/content/packages/guides/container-guides-for-github-packages.md b/translations/ru-RU/content/packages/guides/container-guides-for-github-packages.md new file mode 100644 index 0000000000..31b8f63889 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/container-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Container guides for GitHub Packages +shortTitle: Container guides for GitHub Packages +intro: 'You can publish and retrieve Docker images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/ru-RU/content/packages/guides/deleting-a-container-image.md b/translations/ru-RU/content/packages/guides/deleting-a-container-image.md new file mode 100644 index 0000000000..33451deeaa --- /dev/null +++ b/translations/ru-RU/content/packages/guides/deleting-a-container-image.md @@ -0,0 +1,33 @@ +--- +title: Deleting a container image +intro: 'You can delete a version of a private container image using GraphQL or on {% data variables.product.prodname_dotcom %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### About package deletion + +You can remove an entire container image or a specific version on {% data variables.product.prodname_dotcom %}. To delete a container image, you must use the UI. Using GraphQL to delete a container image is not supported at this time. + +To delete a container image, you must have admin permissions to the container image. + +When deleting public packages, be aware that you may break projects that depend on your package. + +### Deleting a version of a user-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-user-level %} +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Deleting a version of an organization-owned container image on {% data variables.product.prodname_dotcom %} + +{% data reusables.package_registry.package-settings-from-org-level %} +5. On the left, click **Manage versions**. +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) diff --git a/translations/ru-RU/content/packages/guides/enabling-improved-container-support.md b/translations/ru-RU/content/packages/guides/enabling-improved-container-support.md new file mode 100644 index 0000000000..d0b4d98741 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/enabling-improved-container-support.md @@ -0,0 +1,39 @@ +--- +title: Enabling improved container support +intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/enabling-improved-container-support +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." + +{% endnote %} + +### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account + +Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account. + +To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members. + +{% data reusables.feature-preview.feature-preview-setting %} +2. On the left, select "Improved container support", then click **Enable**. ![Improved container support](/assets/images/help/settings/improved-container-support.png) + +### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account + +Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. On the left, click **Packages**. +5. Under "Improved container support", select "Enable improved container support" and click **Save**. ![Enable container registry support option and save button](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images. + - To enable organization members to create public container images, click **Public**. + - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + + ![Options to enable public or private packages ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/ru-RU/content/packages/guides/index.md b/translations/ru-RU/content/packages/guides/index.md new file mode 100644 index 0000000000..19f744a53d --- /dev/null +++ b/translations/ru-RU/content/packages/guides/index.md @@ -0,0 +1,33 @@ +--- +title: Руководства +shortTitle: Руководства +intro: 'These guides help you configure {% data variables.product.prodname_actions %} or your package client to work with {% data variables.product.prodname_registry %}.' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem + - /packages/using-github-packages-with-your-projects-ecosystem +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Table of Contents + +{% topic_link_in_list /package-client-guides-for-github-packages %} + {% link_in_list /using-github-packages-with-github-actions %} + {% link_in_list /configuring-apache-maven-for-use-with-github-packages %} + {% link_in_list /configuring-gradle-for-use-with-github-packages %} + {% link_in_list /configuring-npm-for-use-with-github-packages %} + {% link_in_list /configuring-dotnet-cli-for-use-with-github-packages %} + {% link_in_list /configuring-rubygems-for-use-with-github-packages %} +{% topic_link_in_list /container-guides-for-github-packages %} + {% link_in_list /configuring-docker-for-use-with-github-packages %} + {% link_in_list /about-github-container-registry %} + {% link_in_list /migrating-to-github-container-registry-for-docker-images %} + {% link_in_list /enabling-improved-container-support %} + {% link_in_list /configuring-access-control-and-visibility-for-container-images %} + {% link_in_list /connecting-a-repository-to-a-container-image %} + {% link_in_list /pushing-and-pulling-docker-images %} + {% link_in_list /deleting-a-container-image %} + diff --git a/translations/ru-RU/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md b/translations/ru-RU/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md new file mode 100644 index 0000000000..0a37abf195 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md @@ -0,0 +1,115 @@ +--- +title: Migrating to GitHub Container Registry for Docker images +intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate to the new {% data variables.product.prodname_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images +versions: + free-pro-team: '*' +--- + +### Key differences between {% data variables.product.prodname_github_container_registry %} and the Docker package registry + +{% data reusables.package_registry.container-registry-beta %} + +The {% data variables.product.prodname_github_container_registry %} supersedes the existing Packages Docker registry and is optimized to support some of the unique needs of containers. + +{% data reusables.package_registry.container-registry-feature-highlights %} + +For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." + +### Billing changes + +{% data reusables.package_registry.billing-for-container-registry %} + +### Domain changes + +The domain for the {% data variables.product.prodname_container_registry %} is `ghcr.io`. + +| Registry | Example URL | +| ----------------------------------------------------------------- | --------------------------------------------------- | +| {% data variables.product.prodname_registry %} Docker registry | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` | +| {% data variables.product.prodname_github_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME` | + +### Authenticating with the container registry + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}. + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Migrating a Docker image using the Docker CLI + +To move Docker images that you host on {% data variables.product.prodname_registry %} Docker registry, you must republish the images to {% data variables.product.prodname_container_registry %}. We recommend republishing your existing Docker images using the command line on your local machine. + +1. Sign in to the Docker registry using a temporary PAT with at least the `read:packages` scope. This PAT will only be used to sign in to the Docker registry to pull down images and can be deleted afterward. + {% raw %} + ```shell + $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin + ``` + {% endraw %} +2. Pull down the image you'd like to migrate, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with tag for the image you want to install. For example, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` pulls the latest tag of the `octoshift/octoshift` image in the octo-org organization. + ```shell + $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + +3. Re-tag the image with the new domain and a new image name. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. Use the same URL that you used in the previous step for the SOURCE URL. Replace the TARGET_OWNER with the user or organization that you are migrating the container image to and replace the TARGET_IMAGE_NAME with the new {% data variables.product.prodname_container_registry %} image name. + ```shell + $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION + ``` + +4. Sign in to the new + +{% data variables.product.prodname_container_registry %}. We recommend creating a new PAT limited to the `read:packages` and `write:packages` scopes since you no longer need the `repo` scope and your previous PAT may not have the `write:packages` scope. + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + ``` + {% endraw %} +5. Push your re-tagged image to the {% data variables.product.prodname_container_registry %}. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION + ``` + +### Updating your {% data variables.product.prodname_actions %} workflow + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers. + +1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)." + +2. In your {% data variables.product.prodname_actions %} workflow file, update the package url from `https://docker.pkg.github.com` to `ghcr.io`. + +3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub Actions secret. {% data variables.product.prodname_github_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." + +4. In your {% data variables.product.prodname_actions %} workflow file, update the authentication PAT by replacing your Docker registry PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) with a new variable for your {% data variables.product.prodname_container_registry %} PAT, such as {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}. + +#### Example of updated workflow + +If part of your workflow accessed a Docker image hosted by the Docker registry like this: + +{% raw %} +```yaml +echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin +docker pull docker.pkg.github.com/github/octoshift/octoshift:latest +docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest +docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA +``` +{% endraw %} + +Then you'll need to update your workflow with the new {% data variables.product.prodname_container_registry %} URL and PAT like this: + +{% raw %} +```yaml +# new login with new container registry url and PAT +echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin +# new container registry urls added +docker pull ghcr.io/github/octoshift:latest +docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest +docker push ghcr.io/github/octoshift:$GITHUB_SHA +``` +{% endraw %} diff --git a/translations/ru-RU/content/packages/guides/package-client-guides-for-github-packages.md b/translations/ru-RU/content/packages/guides/package-client-guides-for-github-packages.md new file mode 100644 index 0000000000..6f77e8b9bd --- /dev/null +++ b/translations/ru-RU/content/packages/guides/package-client-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: Package client guides for GitHub Packages +shortTitle: Package client guides for GitHub Packages +intro: 'You can publish and retrieve package client images using {% data variables.product.prodname_registry %}.' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/ru-RU/content/packages/guides/pushing-and-pulling-docker-images.md b/translations/ru-RU/content/packages/guides/pushing-and-pulling-docker-images.md new file mode 100644 index 0000000000..de286a6be1 --- /dev/null +++ b/translations/ru-RU/content/packages/guides/pushing-and-pulling-docker-images.md @@ -0,0 +1,106 @@ +--- +title: Pushing and pulling Docker images +intro: 'You can store and manage Docker images in {% data variables.product.prodname_github_container_registry %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." + +### Authenticating to {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### Pushing container images + +This example pushes the latest version of `IMAGE-NAME`. + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +This example pushes the `2.5` version of the image. + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 + ``` + +When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." + +### Pulling container images + +#### Pull by digest + +To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value. + +1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:` + ```shell + $ docker inspect ghcr.io/OWNER/IMAGE_NAME + ``` +2. Remove image locally as needed. + ```shell + $ docker rmi ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +3. Pull the container image with `@YOUR_SHA_VALUE` after the image name. + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs + ``` + +#### Pull by name + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME + ``` + +#### Pull by name and version + +Docker CLI example showing an image pulled by its name and the `1.14.1` version tag: + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1 + > 5e35bd43cf78: Pull complete + > 0c48c2209aab: Pull complete + > fd45dd1aad5a: Pull complete + > db6eb50c2d36: Pull complete + > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e + > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 + > ghcr.io/orgname/image-name/release:1.14.1 + ``` + +#### Pull by name and latest version + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest + > latest: Pulling from user/image-name + > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 + > Status: Downloaded newer image for ghcr.io/user/image-name:latest + > ghcr.io/user/image-name:latest + ``` + +### Building container images + +This example builds the `hello_docker` image: + ```shell + $ docker build -t hello_docker . + ``` + +### Tagging container images + +1. Find the ID for the Docker image you want to tag. + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +2. Tag your Docker image using the image ID and your desired image name and hosting destination. + ```shell + $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest + ``` diff --git a/translations/ru-RU/content/packages/guides/using-github-packages-with-github-actions.md b/translations/ru-RU/content/packages/guides/using-github-packages-with-github-actions.md new file mode 100644 index 0000000000..b66eb8628a --- /dev/null +++ b/translations/ru-RU/content/packages/guides/using-github-packages-with-github-actions.md @@ -0,0 +1,55 @@ +--- +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 %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions + - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About {% data variables.product.prodname_registry %} with {% 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)." + +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 %} + +{% 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)." + +{% endif %} + +#### Authenticating to package registries on {% 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. + +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)." + +### Publishing a package using an action + +You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. + +{% data reusables.package_registry.actions-configuration %} + +### 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 %} + +{% 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 %} diff --git a/translations/ru-RU/content/packages/index.md b/translations/ru-RU/content/packages/index.md index e00d89f22a..c40765a9dc 100644 --- a/translations/ru-RU/content/packages/index.md +++ b/translations/ru-RU/content/packages/index.md @@ -2,31 +2,46 @@ title: GitHub Packages Documentation shortTitle: GitHub Packages intro: 'Learn to safely publish and consume packages, store your packages alongside your code, and share your packages privately with your team or publicly with the open source community. You can also automate your packages with {% data variables.product.prodname_actions %}.' +introLinks: + quickstart: /packages/quickstart + reference: /packages/manage-packages featuredLinks: - gettingStarted: - - /packages/publishing-and-managing-packages/about-github-packages - - /packages/getting-started-with-github-container-registry/about-github-container-registry - - /packages/getting-started-with-github-container-registry - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/publishing-and-managing-packages/publishing-a-package - - /packages/publishing-and-managing-packages/installing-a-package + guides: + - /packages/learn-github-packages + - /packages/guides/using-github-packages-with-github-actions + - /packages/manage-packages/installing-a-package popular: - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-apache-maven-for-use-with-github-packages + guideCards: + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/guides/enabling-improved-container-support + - /packages/guides/configuring-rubygems-for-use-with-github-packages +changelog: + - + title: Packages container support is an opt-in beta + date: '2020-11-17' + href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support + - + title: Organization admins access to containers + date: '2020-11-16' + href: https://github.blog/changelog/2020-11-16-packages-organization-admins-access-to-containers/ + - + title: Packages now respects IP allow list settings + date: '2020-11-12' + href: https://github.blog/changelog/2020-11-12-packages-now-respects-ip-allow-list-settings/ redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry - /github/managing-packages-with-github-package-registry +layout: product-landing versions: free-pro-team: '*' enterprise-server: '>=2.22' --- -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% link_with_intro /getting-started-with-github-container-registry %} -{% link_with_intro /managing-container-images-with-github-container-registry %} -{% link_with_intro /publishing-and-managing-packages %} -{% link_with_intro /using-github-packages-with-your-projects-ecosystem %} + + + + diff --git a/translations/ru-RU/content/packages/learn-github-packages/about-github-packages.md b/translations/ru-RU/content/packages/learn-github-packages/about-github-packages.md new file mode 100644 index 0000000000..cc1409285c --- /dev/null +++ b/translations/ru-RU/content/packages/learn-github-packages/about-github-packages.md @@ -0,0 +1,166 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/about-github-package-registry + - /github/managing-packages-with-github-package-registry/about-github-package-registry + - /github/managing-packages-with-github-packages/about-github-packages + - /packages/publishing-and-managing-packages/about-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About {% 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 %}. + +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. + +{% data variables.product.prodname_registry %} offers different package registries for commonly used packages, such as for Node, RubyGems, Apache Maven, Gradle, and Nuget. + +{% if currentVersion == "free-pro-team@latest" %} +{% data variables.product.prodname_registry %} also offers a {% data variables.product.prodname_container_registry %} designed to support the unique needs of container images. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." + +{% data reusables.package_registry.container-registry-beta %} + +![Diagram showing Node, RubyGems, Apache Maven, Gradle, Nuget, and the container registry with their hosting urls](/assets/images/help/package-registry/packages-overview-diagram.png) + +{% endif %} + +#### Viewing packages + +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)." + +#### About package permissions and visibility + +| | 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 %} + +{% if currentVersion == "free-pro-team@latest" %} +### About billing for {% 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.container-registry-beta-billing-note %} +{% endif %} + +### Supported clients and formats + +{% 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 + +{% 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` | +| Нет | Docker container management | `Файл Dockerfile` | `Докер` | `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` | + +{% note %} + +**Note:** Docker is not supported when subdomain isolation is disabled. + +{% endnote %} + +For more information about subdomain isolation, see "[Enabling subdomain isolation](/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)." + +{% 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)." +{% endif %} +### Authenticating to {% data variables.product.prodname_registry %} + +{% data reusables.package_registry.authenticate-packages %} + +### About scopes and permissions for package registries + +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. + +Например: +- 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)." + +| 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 | + +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. + +Дополнительные сведения см. в: +- "[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)" + +### Managing packages + +You can delete a version of a private package on {% data variables.product.product_name %} or using the GraphQL API. When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting a package](/packages/manage-packages/deleting-a-package)" and "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." + +You can 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 + +{% 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). + +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: + +* 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 + +{% else %} +If you need support for +{% data variables.product.prodname_registry %}, please contact your site administrators. + +{% endif %} diff --git a/translations/ru-RU/content/packages/learn-github-packages/core-concepts-for-github-packages.md b/translations/ru-RU/content/packages/learn-github-packages/core-concepts-for-github-packages.md new file mode 100644 index 0000000000..07b7774cd7 --- /dev/null +++ b/translations/ru-RU/content/packages/learn-github-packages/core-concepts-for-github-packages.md @@ -0,0 +1,28 @@ +--- +title: Core concepts for GitHub Packages +intro: 'Below is a list of common {% data variables.product.prodname_registry %} terms we use across our sites and documentation.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### Package + +A package is a self-contained and reusable piece of software that includes code and metadata that a developer bundles together in a common place for others to use. A package's metadata may include the version number, name, and the code's dependencies. Packages simplify using and distributing solutions to common problems such as needing frameworks for developing or testing a project, linters to improve code quality, or industry-standard machine learning tools to power your application. Packages exist in many ecosystems. For example, you can package Node.js and Java code or container images. + +### Container + +A container is a unit of software designed to reliably deploy software in a standardized way on any platform. A container operates as an isolated virtual environment or instance that can run various software packages and components on the same host kernel as your operating system. Containers use fewer resources than virtual machines because they don't need to include their own virtual hardware to run. Containers are created using a container image file, such as a Dockerfile, and a container client or runtime program. + +### Container image + +A container image is a type of package archive that specifies the software requirements to run an app from a container. A container image typically includes the app's code, libraries, and runtime instructions. To ensure that the same image details are used wherever an image is deployed and run, a container image is automatically versioned and cannot be changed once a container image is built in a container. + +### Docker container + +A Docker container is a type of open source container built on the Docker platform. Docker's original image format has become the OCI (Open Container Initiative) Image Specification. For more information, see the "[Docker documentation](https://docs.docker.com/get-started/overview/)." diff --git a/translations/ru-RU/content/packages/learn-github-packages/index.md b/translations/ru-RU/content/packages/learn-github-packages/index.md new file mode 100644 index 0000000000..a21e10fe4c --- /dev/null +++ b/translations/ru-RU/content/packages/learn-github-packages/index.md @@ -0,0 +1,16 @@ +--- +title: Learn GitHub Packages +shortTitle: Learn GitHub Packages +intro: 'You can find out more about GitHub Packages, including publishing new packages to {% data variables.product.prodname_registry %}.' +redirect_from: + - /packages/getting-started-with-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /about-github-packages %} +{% link_in_list /core-concepts-for-github-packages %} +{% link_in_list /publishing-a-package %} diff --git a/translations/ru-RU/content/packages/learn-github-packages/publishing-a-package.md b/translations/ru-RU/content/packages/learn-github-packages/publishing-a-package.md new file mode 100644 index 0000000000..41d764d306 --- /dev/null +++ b/translations/ru-RU/content/packages/learn-github-packages/publishing-a-package.md @@ -0,0 +1,37 @@ +--- +title: Publishing a package +intro: 'You can publish a package to {% data variables.product.prodname_registry %} to make the package available for others to download and re-use.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-a-package + - /packages/publishing-and-managing-packages/publishing-a-package +permissions: Anyone with write permissions for a repository can publish a package to that repository. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About published packages + +You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. {% data variables.product.product_name %} provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). + +{% data reusables.package_registry.public-or-private-packages %} A repository can contain more than one package. To prevent confusion, make sure the README and description clearly provide information about each package. + +{% if currentVersion == "free-pro-team@latest" %} +If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. +{% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +{% endif %} + +### Publishing a package + +You can publish a package to {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. + +1. Create or use an existing access token with the appropriate scopes for the task you want to accomplish. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +2. Authenticate to {% data variables.product.prodname_registry %} using your access token and the instructions for your package client. +3. Publish the package using the instructions for your package client. + +For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)." + +After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see “[Viewing packages](/packages/publishing-and-managing-packages/viewing-packages).” diff --git a/translations/ru-RU/content/packages/manage-packages/deleting-a-package.md b/translations/ru-RU/content/packages/manage-packages/deleting-a-package.md new file mode 100644 index 0000000000..dec649cf0b --- /dev/null +++ b/translations/ru-RU/content/packages/manage-packages/deleting-a-package.md @@ -0,0 +1,81 @@ +--- +title: Deleting a package +intro: 'You can delete a version of a private package using GraphQL or on {% data variables.product.product_name %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/deleting-a-package + - /packages/publishing-and-managing-packages/deleting-a-package +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% if currentVersion == "free-pro-team@latest" %} +### About container image deletion + +To delete a container image package on {% data variables.product.product_name %}, see "[Deleting a container image](/packages/guides/deleting-a-container-image)." + +{% endif %} + +### About private package deletion + +You can only delete a specified version of a private package on {% data variables.product.product_name %} or with the GraphQL API. To remove an entire private package from appearing on {% data variables.product.product_name %}, you must delete every version of the package first. + +{% if currentVersion == "free-pro-team@latest" %} +### About public package deletion + +To avoid breaking projects that may depend on your packages, you cannot delete an entire public package or specific versions of a public package. + +Under special circumstances, such as for legal reasons or to conform with GDPR standards, you can ask {% data variables.contact.github_support %} to delete a public package for you, using [our contact form](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry). + +{% else %} + +At this time, {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} does not support deleting public packages. + +{% endif %} + +### Deleting a version of a private package on {% data variables.product.product_name %} + +To delete a private package version, you must have admin permissions in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +3. Click the name of the package that you want to delete. ![Package name](/assets/images/help/package-registry/select-pkg-cloud.png) +4. On the right, use the **Edit package** drop-down and select "Manage versions". ![Package name](/assets/images/help/package-registry/manage-versions.png) +5. To the right of the version you want to delete, click **Delete**. ![Delete package button](/assets/images/help/package-registry/delete-package-button.png) +6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**. ![Confirm package deletion button](/assets/images/help/package-registry/confirm-package-deletion.png) + +### Deleting a version of a private package with GraphQL + +Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." + +Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token. + +{% if currentVersion == "free-pro-team@latest" %} +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +https://api.github.com/graphql +``` + +{% else %} + +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +HOSTNAME/graphql +``` + +{% endif %} + +To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface. + +For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)." + +You cannot delete an entire package, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %} diff --git a/translations/ru-RU/content/packages/manage-packages/index.md b/translations/ru-RU/content/packages/manage-packages/index.md new file mode 100644 index 0000000000..7f313028a1 --- /dev/null +++ b/translations/ru-RU/content/packages/manage-packages/index.md @@ -0,0 +1,18 @@ +--- +title: Managing GitHub packages +shortTitle: Managing GitHub packages +intro: 'You can publish new packages to {% data variables.product.prodname_registry %}, view and install existing packages, and, in special circumstances, delete existing packages.' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-and-managing-packages + - /github/packages/publishing-and-managing-packages + - /packages/publishing-and-managing-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /viewing-packages %} +{% link_in_list /installing-a-package %} +{% link_in_list /deleting-a-package %} diff --git a/translations/ru-RU/content/packages/manage-packages/installing-a-package.md b/translations/ru-RU/content/packages/manage-packages/installing-a-package.md new file mode 100644 index 0000000000..007e344089 --- /dev/null +++ b/translations/ru-RU/content/packages/manage-packages/installing-a-package.md @@ -0,0 +1,29 @@ +--- +title: Installing a package +intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/installing-a-package + - /packages/publishing-and-managing-packages/installing-a-package +permissions: Anyone with read permissions for a repository can install a package from that repository. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About package installation + +You can search {% data variables.product.product_name %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)." + +After you find a package, you can read the package's description and installation and usage instructions on the package page. + +### Installing a package + +You can install a package from {% data variables.product.prodname_registry %} using any {% if currentVersion == "free-pro-team@latest" %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. + +1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[About tokens](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +2. Install the package using the instructions for your package client. + +For instructions specific to your package client, see "[Using {% data variables.product.prodname_registry %} with your project's ecosystem](/packages/using-github-packages-with-your-projects-ecosystem)." diff --git a/translations/ru-RU/content/packages/manage-packages/viewing-packages.md b/translations/ru-RU/content/packages/manage-packages/viewing-packages.md new file mode 100644 index 0000000000..9934b1bf29 --- /dev/null +++ b/translations/ru-RU/content/packages/manage-packages/viewing-packages.md @@ -0,0 +1,50 @@ +--- +title: Viewing packages +intro: 'You can see details about packages published to a repository, and narrow results by organization or user.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/viewing-packages + - /packages/publishing-and-managing-packages/viewing-packages +permissions: Anyone with read permissions to a repository can view the repository's packages. +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About package views + +Packages must be installed at the repository level, but you can view all packages in an organization and all packages you've published. {% data reusables.package_registry.package-page-info %} + +### Viewing a repository's packages + +You can see all the packages in a repository and search for a specific package in the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + +### Viewing an organization's packages + +You can see all the packages installed in an organization and search for a specific package installed in an organization's repositories. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. Под названием вашей организации щелкните +{% octicon "package" aria-label="The package icon" %} **Packages**. +{% data reusables.package_registry.navigate-to-packages %} + +### Viewing your packages + +You can see all the packages you've installed and search for a specific package you've installed across all organizations and repositories. + +{% data reusables.profile.access_profile %} +2. On the top of the profile page, in the main navigation, click **Packages**. ![Project tab](/assets/images/help/package-registry/user-packages-tab.png) +{% data reusables.package_registry.navigate-to-packages %} + +### Дополнительная литература + +- "[Searching for packages](/github/searching-for-information-on-github/searching-for-packages)" diff --git a/translations/ru-RU/content/packages/quickstart.md b/translations/ru-RU/content/packages/quickstart.md new file mode 100644 index 0000000000..8928caee4b --- /dev/null +++ b/translations/ru-RU/content/packages/quickstart.md @@ -0,0 +1,110 @@ +--- +title: Quickstart for GitHub Packages +intro: 'Publish to {% data variables.product.prodname_registry %} in 5 minutes or less with {% data variables.product.prodname_actions %}.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### Introduction + +You only need an existing {% data variables.product.prodname_dotcom %} repository to publish a package to {% data variables.product.prodname_registry %}. In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}. Feel free to create a new repository for this Quickstart. You can use it to test this and future {% data variables.product.prodname_actions %} workflows. + +### Publishing your package + +1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. Create a private repository if you’d like to delete this package later, public packages cannot be deleted. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)." +2. Clone the repository to your local machine. + {% raw %} + ```shell + $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git + $ cd YOUR-REPOSITORY + ``` + {% endraw %} +3. Create an `index.js` file and add a basic alert to say "Hello world!" + {% raw %} + ```javascript{:copy} + alert("Hello, World!"); + ``` + {% endraw %} +4. Initialize an npm package. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0` if you do not have any tests. Commit your changes and push them to +{% data variables.product.prodname_dotcom %}. + {% raw %} + ```shell + $ npm init + ... + package name: @YOUR-USERNAME/YOUR-REPOSITORY + ... + test command: exit 0 + ... + + $ npm install + $ git add index.js package.json package-lock.json + $ git commit -m "initialize npm package" + $ git push + ``` + {% endraw %} +5. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `release-package.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)." +6. Copy the following YAML content into the `release-package.yml` file. + {% raw %} + ```yaml{:copy} + name: Node.js Package + + on: + release: + types: [created] + + jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm ci + - run: npm test + + publish-gpr: + needs: build + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + registry-url: https://npm.pkg.github.com/ + - run: npm ci + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + ``` + {% endraw %} +7. 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**. +8. **Merge** the pull request. +9. Navigate to the **Code** tab and create a new release to test the workflow. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)." + +Creating a new release in your repository triggers the workflow to build and test your code. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}. + +### Viewing your published package + +Packages are published at the repository level. You can see all the packages in a repository and search for a specific package. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + + +### Installing a published package + +Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Configuring npm for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)." + +### Дальнейшие шаги + +The basic workflow you just added runs any time a new release is created in your repository. But, this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more. + +Combining {% data variables.product.prodname_registry %} and {% 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_registry %} and {% data variables.product.prodname_actions %}: + +- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages +- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions +- "[Guides](/packages/guides)" for specific uses cases and examples diff --git a/translations/ru-RU/content/rest/README.md b/translations/ru-RU/content/rest/README.md new file mode 100644 index 0000000000..55aaa5edda --- /dev/null +++ b/translations/ru-RU/content/rest/README.md @@ -0,0 +1,10 @@ +# REST + +The `/content/rest` directory is where the GitHub REST API docs live! + +* The `/content/rest/guides` and `/content/rest/overview` directories contain regular articles. These are human-editable. +* The `/content/rest/reference` directory contains an article for each group of endpoints in the GitHub REST API. Most of the content in this directory is rendered using `include` tags. + + The content rendered by `include` tags is sourced from the `/lib/rest/static` directory, which is automatically generated from the API source code internally in GitHub, and should not be edited by a human. For more information, see the [`/lib/rest/README.md`](/lib/rest/README.md). + + **As a result, we cannot accept contributions to REST API reference content in this repository.** 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 c0e4e63f87..9924ff24b6 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 @@ -373,7 +373,7 @@ Keep learning with the next API guide [Basics of Authentication][auth guide]! [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore [issues-api]: /rest/reference/issues -[link-header]: http://www.w3.org/wiki/LinkHeader/ +[link-header]: https://www.w3.org/wiki/LinkHeader [conditional-requests]: /rest#conditional-requests [rate-limiting]: /rest#rate-limiting [rate-limiting]: /rest#rate-limiting diff --git a/translations/ru-RU/content/rest/overview/api-previews.md b/translations/ru-RU/content/rest/overview/api-previews.md index d103d50a56..4fae0855c3 100644 --- a/translations/ru-RU/content/rest/overview/api-previews.md +++ b/translations/ru-RU/content/rest/overview/api-previews.md @@ -53,7 +53,7 @@ Create, list, update, and delete environments for pre-receive hooks. {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### Integrations -Manage [integrations](/early-access/integrations/) through the API. +Manage [integrations](/v3/integrations) through the API. **Custom media type:** `machine-man-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/) {% endif %} diff --git a/translations/ru-RU/content/rest/overview/libraries.md b/translations/ru-RU/content/rest/overview/libraries.md index 169441d839..c44db06aa8 100644 --- a/translations/ru-RU/content/rest/overview/libraries.md +++ b/translations/ru-RU/content/rest/overview/libraries.md @@ -72,7 +72,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby diff --git a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md index 4b76372d51..c01a946b00 100644 --- a/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ru-RU/content/rest/overview/resources-in-the-rest-api.md @@ -262,13 +262,15 @@ You can then expand these templates using something like the [uri_template][uri] ### Pagination -Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `?page` parameter. For some resources, you can also set a custom page size up to 100 with the `?per_page` parameter. Note that for technical reasons not all endpoints respect the `?per_page` parameter, see [events](/rest/reference/activity#events) for example. +Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the `page` parameter. For some resources, you can also set a custom page size up to 100 with the `per_page` parameter. Note that for technical reasons not all endpoints respect the `per_page` parameter, see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -Note that page numbering is 1-based and that omitting the `?page` parameter will return the first page. +Note that page numbering is 1-based and that omitting the `page` parameter will return the first 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. For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. @@ -280,13 +282,17 @@ For more information on pagination, check out our guide on [Traversing with Pagi {% endnote %} -The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information: +The [Link header](http://tools.ietf.org/html/rfc5988) includes pagination information. Например: Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" _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). The possible `rel` values are: diff --git a/translations/ru-RU/content/rest/overview/troubleshooting.md b/translations/ru-RU/content/rest/overview/troubleshooting.md index fe452f17d8..f730651c16 100644 --- a/translations/ru-RU/content/rest/overview/troubleshooting.md +++ b/translations/ru-RU/content/rest/overview/troubleshooting.md @@ -52,7 +52,7 @@ curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos #### Calls to OAuth Authorizations API -If you're making [OAuth Authorization API](/enterprise-server@2.22/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: +If you're making [OAuth Authorization API](/enterprise-server/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example: ```bash curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}' diff --git a/translations/ru-RU/content/rest/reference/enterprise-admin.md b/translations/ru-RU/content/rest/reference/enterprise-admin.md index 5437c29df8..9325448ec8 100644 --- a/translations/ru-RU/content/rest/reference/enterprise-admin.md +++ b/translations/ru-RU/content/rest/reference/enterprise-admin.md @@ -57,6 +57,16 @@ The current version of your enterprise is returned in the response header of eve {% endif %} +{% if currentVersion == "free-pro-team@latest" %} + +## Audit log + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ## Billing diff --git a/translations/ru-RU/content/rest/reference/index.md b/translations/ru-RU/content/rest/reference/index.md index dfeb1f0648..d235a3280e 100644 --- a/translations/ru-RU/content/rest/reference/index.md +++ b/translations/ru-RU/content/rest/reference/index.md @@ -15,8 +15,6 @@ versions: {% link_in_list /apps %} {% link_in_list /billing %} {% link_in_list /checks %} - - {% link_in_list /codes-of-conduct %} {% link_in_list /code-scanning %} {% link_in_list /emojis %} @@ -39,6 +37,7 @@ versions: {% link_in_list /repos %} {% link_in_list /scim %} {% link_in_list /search %} +{% link_in_list /secret-scanning %} {% link_in_list /teams %} {% link_in_list /users %} {% link_in_list /permissions-required-for-github-apps %} diff --git a/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md b/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md index 21dd7104f7..787917734e 100644 --- a/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/ru-RU/content/rest/reference/permissions-required-for-github-apps.md @@ -819,10 +819,19 @@ _Teams_ * [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) - {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### Permission on "secret scanning alerts" + +- [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) + +- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read) + +- [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### Permission on "security events" - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) diff --git a/translations/ru-RU/content/rest/reference/secret-scanning.md b/translations/ru-RU/content/rest/reference/secret-scanning.md new file mode 100644 index 0000000000..6c266b8488 --- /dev/null +++ b/translations/ru-RU/content/rest/reference/secret-scanning.md @@ -0,0 +1,12 @@ +--- +title: Secret scanning +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.secret-scanning.api-beta %} + +The {% data variables.product.prodname_secret_scanning %} API lets you retrieve and update secret scanning alerts from a private repository. For more information on secret scanning for private repositories, see "[Securing your repository](/github/administering-a-repository/securing-your-repository)." + +{% include rest_operations_at_current_path %} diff --git a/translations/ru-RU/data/glossaries/external.yml b/translations/ru-RU/data/glossaries/external.yml index 8797ef2840..a0b87986d5 100644 --- a/translations/ru-RU/data/glossaries/external.yml +++ b/translations/ru-RU/data/glossaries/external.yml @@ -390,7 +390,7 @@ - term: main description: >- - The default development branch. Whenever you create a Git repository, a branch named "main" is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. + The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. - term: главная (ветвь) description: >- diff --git a/translations/ru-RU/data/products.yml b/translations/ru-RU/data/products.yml index d8ced2f7d7..d4806d6564 100644 --- a/translations/ru-RU/data/products.yml +++ b/translations/ru-RU/data/products.yml @@ -5,10 +5,12 @@ productsInOrder: - github - admin + - discussions - actions - пакеты - developers - rest - graphql - insights + - education - desktop diff --git a/translations/ru-RU/data/release-notes/2-20/0.yml b/translations/ru-RU/data/release-notes/2-20/0.yml new file mode 100644 index 0000000000..5623123354 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/0.yml @@ -0,0 +1,44 @@ +--- +date: '2020-02-11' +sections: + features: + - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" + - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" + - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + changes: + - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/1.yml b/translations/ru-RU/data/release-notes/2-20/1.yml new file mode 100644 index 0000000000..e303f5525e --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/1.yml @@ -0,0 +1,21 @@ +--- +date: '2020-02-27' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + bugs: + - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/10.yml b/translations/ru-RU/data/release-notes/2-20/10.yml new file mode 100644 index 0000000000..58a38245c0 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/10.yml @@ -0,0 +1,21 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" + - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/11.yml b/translations/ru-RU/data/release-notes/2-20/11.yml new file mode 100644 index 0000000000..0bdd30cf96 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/11.yml @@ -0,0 +1,19 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/12.yml b/translations/ru-RU/data/release-notes/2-20/12.yml new file mode 100644 index 0000000000..5b286392f5 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/12.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + bugs: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + changes: + - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/13.yml b/translations/ru-RU/data/release-notes/2-20/13.yml new file mode 100644 index 0000000000..7388ff5103 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/13.yml @@ -0,0 +1,22 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/14.yml b/translations/ru-RU/data/release-notes/2-20/14.yml new file mode 100644 index 0000000000..d33fe2b58d --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/14.yml @@ -0,0 +1,13 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/15.yml b/translations/ru-RU/data/release-notes/2-20/15.yml new file mode 100644 index 0000000000..651811695b Binary files /dev/null and b/translations/ru-RU/data/release-notes/2-20/15.yml differ diff --git a/translations/ru-RU/data/release-notes/2-20/16.yml b/translations/ru-RU/data/release-notes/2-20/16.yml new file mode 100644 index 0000000000..4ca63bc213 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/16.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/17.yml b/translations/ru-RU/data/release-notes/2-20/17.yml new file mode 100644 index 0000000000..5f3bf87a25 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/17.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/18.yml b/translations/ru-RU/data/release-notes/2-20/18.yml new file mode 100644 index 0000000000..3aab7ba337 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/18.yml @@ -0,0 +1,26 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/19.yml b/translations/ru-RU/data/release-notes/2-20/19.yml new file mode 100644 index 0000000000..b686131852 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/19.yml @@ -0,0 +1,14 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/2.yml b/translations/ru-RU/data/release-notes/2-20/2.yml new file mode 100644 index 0000000000..78e2faa7e1 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/2.yml @@ -0,0 +1,28 @@ +--- +date: '2020-03-10' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + bugs: + - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + changes: + - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/20.yml b/translations/ru-RU/data/release-notes/2-20/20.yml new file mode 100644 index 0000000000..0cf4def9e0 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/20.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/21.yml b/translations/ru-RU/data/release-notes/2-20/21.yml new file mode 100644 index 0000000000..4b970a92ee --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/21.yml @@ -0,0 +1,15 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/22.yml b/translations/ru-RU/data/release-notes/2-20/22.yml new file mode 100644 index 0000000000..099ce93b0d --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/22.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/3.yml b/translations/ru-RU/data/release-notes/2-20/3.yml new file mode 100644 index 0000000000..23c25312e5 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/3.yml @@ -0,0 +1,15 @@ +--- +date: '2020-03-12' +sections: + bugs: + - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/4.yml b/translations/ru-RU/data/release-notes/2-20/4.yml new file mode 100644 index 0000000000..0f06a203cd --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/4.yml @@ -0,0 +1,18 @@ +--- +date: '2020-03-25' +sections: + bugs: + - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/5.yml b/translations/ru-RU/data/release-notes/2-20/5.yml new file mode 100644 index 0000000000..44115fdc71 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/5.yml @@ -0,0 +1,20 @@ +--- +date: '2020-04-07' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + bugs: + - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/6.yml b/translations/ru-RU/data/release-notes/2-20/6.yml new file mode 100644 index 0000000000..568f19954f --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/6.yml @@ -0,0 +1,27 @@ +--- +date: '2020-04-23' +sections: + security_fixes: + - '**HIGH**: OpenSSL has been updated to address [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 %}' + - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + bugs: + - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" + - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + changes: + - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% 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: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/7.yml b/translations/ru-RU/data/release-notes/2-20/7.yml new file mode 100644 index 0000000000..b377d90b66 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/7.yml @@ -0,0 +1,21 @@ +--- +date: '2020-05-05' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + bugs: + - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' + - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/8.yml b/translations/ru-RU/data/release-notes/2-20/8.yml new file mode 100644 index 0000000000..510bf779fb --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/8.yml @@ -0,0 +1,20 @@ +--- +date: '2020-05-19' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + bugs: + - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-20/9.yml b/translations/ru-RU/data/release-notes/2-20/9.yml new file mode 100644 index 0000000000..326818d711 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-20/9.yml @@ -0,0 +1,17 @@ +--- +date: '2020-06-02' +sections: + security_fixes: + - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + bugs: + - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/0.yml b/translations/ru-RU/data/release-notes/2-21/0.yml new file mode 100644 index 0000000000..cfd8a069f8 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/0.yml @@ -0,0 +1,72 @@ +--- +date: '2020-06-09' +sections: + features: + - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + security_fixes: + - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + bugs: + - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' + changes: + - 'The web notifications interface, including new [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - 'Admins can [enable security alerts](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' + - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/1.yml b/translations/ru-RU/data/release-notes/2-21/1.yml new file mode 100644 index 0000000000..9b802bd1f3 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/1.yml @@ -0,0 +1,20 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/10.yml b/translations/ru-RU/data/release-notes/2-21/10.yml new file mode 100644 index 0000000000..65b5d9c64c --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/10.yml @@ -0,0 +1,15 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/11.yml b/translations/ru-RU/data/release-notes/2-21/11.yml new file mode 100644 index 0000000000..ce20fbe36a --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/11.yml @@ -0,0 +1,18 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/12.yml b/translations/ru-RU/data/release-notes/2-21/12.yml new file mode 100644 index 0000000000..c347bb7aca --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/12.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/13.yml b/translations/ru-RU/data/release-notes/2-21/13.yml new file mode 100644 index 0000000000..06e910bb50 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/13.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/2.yml b/translations/ru-RU/data/release-notes/2-21/2.yml new file mode 100644 index 0000000000..bdac746dbc --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/2.yml @@ -0,0 +1,20 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/3.yml b/translations/ru-RU/data/release-notes/2-21/3.yml new file mode 100644 index 0000000000..dd4ccbbb5e --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/3.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% 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: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/4.yml b/translations/ru-RU/data/release-notes/2-21/4.yml new file mode 100644 index 0000000000..e90460c88e --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/4.yml @@ -0,0 +1,27 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" + - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/5.yml b/translations/ru-RU/data/release-notes/2-21/5.yml new file mode 100644 index 0000000000..444cf28527 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/5.yml @@ -0,0 +1,15 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/6.yml b/translations/ru-RU/data/release-notes/2-21/6.yml new file mode 100644 index 0000000000..d85f716f13 Binary files /dev/null and b/translations/ru-RU/data/release-notes/2-21/6.yml differ diff --git a/translations/ru-RU/data/release-notes/2-21/7.yml b/translations/ru-RU/data/release-notes/2-21/7.yml new file mode 100644 index 0000000000..69134720e7 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/7.yml @@ -0,0 +1,14 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/8.yml b/translations/ru-RU/data/release-notes/2-21/8.yml new file mode 100644 index 0000000000..b7bf410b13 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/8.yml @@ -0,0 +1,16 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + bugs: + - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-21/9.yml b/translations/ru-RU/data/release-notes/2-21/9.yml new file mode 100644 index 0000000000..46656c9e6b --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-21/9.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/ru-RU/data/release-notes/2-22/0.yml b/translations/ru-RU/data/release-notes/2-22/0.yml new file mode 100644 index 0000000000..2070890751 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-22/0.yml @@ -0,0 +1,130 @@ +--- +intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. +date: '2020-09-23' +sections: + features: + - + heading: GitHub Actions Beta + notes: + - | + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + + You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + - + heading: GitHub Packages Beta + notes: + - | + [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + - + heading: Advanced Security Code Scanning Beta + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. + + Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + - + heading: Pull Request Retargeting + notes: + - | + When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + - + heading: Suspend and Unsuspend an App Installation + notes: + - | + Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + - + heading: Improved Large Scale Performance + notes: + - | + We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% 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 %}'' + + Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + - + heading: View All of Your Users + notes: + - | + For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](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: Administration Changes + notes: + - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} + - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](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 %}' + - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% 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 %} + - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% 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: Security Changes + notes: + - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](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 %} + - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - + heading: Developer Changes + notes: + - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' + - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' + - + heading: Users and organizations can add Twitter usernames to their GitHub profiles + notes: + - '[Developers and organizations can now add their Twitter username to their profile](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: Изменения API + notes: + - | + #### Graduated Previews + + The following previews are now an official part of the API: + * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} + * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} + - | + #### GraphQL Schema Changes + + * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + bugs: + - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + deprecations: + - + heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020** That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + #- type: Backup and Disaster recovery + #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} + - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} + - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a 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 %}' + - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ru-RU/data/release-notes/2-22/1.yml b/translations/ru-RU/data/release-notes/2-22/1.yml new file mode 100644 index 0000000000..fbd3988c3d --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-22/1.yml @@ -0,0 +1,71 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - | + The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - | + Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + - | + Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + - | + System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + - | + The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + - | + `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + - | + Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + - | + Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + - | + Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + - | + When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + - | + The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + - | + OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + - | + Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + - | + On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + - | + When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + - | + When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + - | + Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + - | + Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + - | + The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + - | + Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + - | + A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + - | + When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + - | + [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + - | + GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management 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: + - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} + - GitHub App Manifests now include the `request_oauth_on_install` field. {% 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: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ru-RU/data/release-notes/2-22/2.yml b/translations/ru-RU/data/release-notes/2-22/2.yml new file mode 100644 index 0000000000..dc36b39e12 --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-22/2.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + bugs: + - | + If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + - | + A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} + - | + On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + - | + When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + - | + Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} + - | + The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + - | + On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ru-RU/data/release-notes/2-22/3.yml b/translations/ru-RU/data/release-notes/2-22/3.yml new file mode 100644 index 0000000000..45442a5d4b --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-22/3.yml @@ -0,0 +1,23 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - | + **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + - | + **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + - | + Packages have been updated to the latest security versions. {% 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: + - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/ru-RU/data/release-notes/2-22/4.yml b/translations/ru-RU/data/release-notes/2-22/4.yml new file mode 100644 index 0000000000..e97737ee0b --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-22/4.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + bugs: + - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} diff --git a/translations/ru-RU/data/release-notes/2-22/5.yml b/translations/ru-RU/data/release-notes/2-22/5.yml new file mode 100644 index 0000000000..0520df862f --- /dev/null +++ b/translations/ru-RU/data/release-notes/2-22/5.yml @@ -0,0 +1,22 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' + - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/ru-RU/data/reusables/accounts/create-account.md b/translations/ru-RU/data/reusables/accounts/create-account.md new file mode 100644 index 0000000000..dc817b083d --- /dev/null +++ b/translations/ru-RU/data/reusables/accounts/create-account.md @@ -0,0 +1,2 @@ +1. Go to {% data variables.product.product_name %}'s [Pricing]({% data variables.product.pricing_url %}) page. +2. Read the information about the different products and subscriptions that {% data variables.product.product_name %} offers, then click the upgrade button under the subscription you'd like to choose. diff --git a/translations/ru-RU/data/reusables/actions/actions-not-verified.md b/translations/ru-RU/data/reusables/actions/actions-not-verified.md index 2ab85ce6c1..3107e5a79f 100644 --- a/translations/ru-RU/data/reusables/actions/actions-not-verified.md +++ b/translations/ru-RU/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations, but unlike verified apps, {% data variables.product.prodname_dotcom %} does not review or verify individual actions listed in {% data variables.product.prodname_marketplace %}. +Anyone can publish an action in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/ru-RU/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/ru-RU/data/reusables/actions/actions-packages-set-spending-limit.md new file mode 100644 index 0000000000..e315a34bc8 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/actions-packages-set-spending-limit.md @@ -0,0 +1 @@ +You can set a specific spending limit or, for some accounts, allow unlimited spending. The spending limit applies to your combined overages for {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}. diff --git a/translations/ru-RU/data/reusables/actions/visualization-beta.md b/translations/ru-RU/data/reusables/actions/visualization-beta.md new file mode 100644 index 0000000000..ee3ad11ef4 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/visualization-beta.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** The workflow visualization graph for {% data variables.product.prodname_actions %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ru-RU/data/reusables/audit_log/audit-log-api-info.md b/translations/ru-RU/data/reusables/audit_log/audit-log-api-info.md new file mode 100644 index 0000000000..55728a1692 --- /dev/null +++ b/translations/ru-RU/data/reusables/audit_log/audit-log-api-info.md @@ -0,0 +1,5 @@ +* Access to your organization or repository settings +* Changes in permissions +* Added or removed users in an organization, repository, or team +* Users being promoted to admin +* Changes to permissions of a {% data variables.product.prodname_github_app %} diff --git a/translations/ru-RU/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/ru-RU/data/reusables/audit_log/audit-log-git-events-retention.md new file mode 100644 index 0000000000..3f1584bf91 --- /dev/null +++ b/translations/ru-RU/data/reusables/audit_log/audit-log-git-events-retention.md @@ -0,0 +1 @@ +The audit log retains Git events for 7 days. This is shorter than other audit log events, which can be retained for 90 days. diff --git a/translations/ru-RU/data/reusables/classroom/about-assignments.md b/translations/ru-RU/data/reusables/classroom/about-assignments.md new file mode 100644 index 0000000000..65a3506229 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/about-assignments.md @@ -0,0 +1 @@ +Each assignment has a title and an optional deadline. You can choose the visibility of repositories that {% data variables.product.prodname_classroom %} creates and choose access permissions. You can also automatically grade assignments and create a dedicated space to discuss the assignment with the student. diff --git a/translations/ru-RU/data/reusables/classroom/about-autograding.md b/translations/ru-RU/data/reusables/classroom/about-autograding.md new file mode 100644 index 0000000000..04ed2b067c --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/about-autograding.md @@ -0,0 +1 @@ +You can use autograding to automatically check a student's work for an assignment on {% data variables.product.prodname_classroom %}. You configure tests for an assignment, and the tests run immediately every time a student pushes to an assignment repository on {% data variables.product.product_location %}. The student can view the test results, make changes, and push to see new results. diff --git a/translations/ru-RU/data/reusables/classroom/about-classrooms.md b/translations/ru-RU/data/reusables/classroom/about-classrooms.md new file mode 100644 index 0000000000..5d19bbb44a --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/about-classrooms.md @@ -0,0 +1 @@ +A classroom in {% data variables.product.prodname_classroom %} is where teachers and students interact during a course. Teachers can create a student roster for the classroom, then create, assign, review, and grade assignments within the classroom. diff --git a/translations/ru-RU/data/reusables/classroom/about-online-ides.md b/translations/ru-RU/data/reusables/classroom/about-online-ides.md new file mode 100644 index 0000000000..43818e691f --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/about-online-ides.md @@ -0,0 +1 @@ +You can optionally configure an assignment to use an online integrated development environment (IDE). Online IDEs allow your students to write code, run programs, and collaborate in a browser, without installing Git and a full development toolchain on the student's computer. If you choose an online IDE for an assignment, students can still check out and run code locally on a computer with the necessary software. diff --git a/translations/ru-RU/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/ru-RU/data/reusables/classroom/assignments-classroom-prerequisite.md new file mode 100644 index 0000000000..06284dad51 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-classroom-prerequisite.md @@ -0,0 +1 @@ +You must create a classroom before you can create an assignment. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." diff --git a/translations/ru-RU/data/reusables/classroom/assignments-click-pencil.md b/translations/ru-RU/data/reusables/classroom/assignments-click-pencil.md new file mode 100644 index 0000000000..820afd5260 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-click-pencil.md @@ -0,0 +1 @@ +1. To the right of the assignment you want to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing assignment in list of assignments](/assets/images/help/classroom/assignments-click-pencil.png) diff --git a/translations/ru-RU/data/reusables/classroom/assignments-group-definition.md b/translations/ru-RU/data/reusables/classroom/assignments-group-definition.md new file mode 100644 index 0000000000..3143cddc70 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-group-definition.md @@ -0,0 +1 @@ +A group assignment is collaborative coursework for groups of students on {% data variables.product.prodname_classroom %}. diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-assign-a-deadline.md new file mode 100644 index 0000000000..6e8e29cc11 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-assign-a-deadline.md @@ -0,0 +1,5 @@ +Optionally, you can assign a deadline to the assignment. Under "Deadline (optional)", click in the text field, then use the date picker to assign a deadline. + +
      + Date picker for assignment deadline +
      diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-an-online-ide.md new file mode 100644 index 0000000000..54858178a5 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -0,0 +1,5 @@ +To choose an online IDE for the assignment, select the **Select an online IDE** drop-down menu, then click the IDE you'd like your students to use. + +
      + Using the 'Select an online IDE' drop-down menu to click an online IDE for the assignment +
      diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-template-repository.md new file mode 100644 index 0000000000..15bcb66cb5 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-template-repository.md @@ -0,0 +1,5 @@ +Under "Add a template repository to give students starter code", select the **Select a repository** drop-down, then type a search query. In the list of results, click the template repository you'd like to use for starter code. + +
      + Using the 'Select a repository' drop-down menu to find a template repository to use as starter code for an assignment +
      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 new file mode 100644 index 0000000000..3f4f17e1b2 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -0,0 +1,9 @@ +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)." + +Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. + +
      + Visibility options for assignment repositories +
      diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-click-continue-after-basics.md new file mode 100644 index 0000000000..b82d19fe8e --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-click-continue-after-basics.md @@ -0,0 +1,7 @@ +
      + +When you're done, click **Continue** to configure starter code and a development environment for the assignment. + +
      + 'Continue' button +
      diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md new file mode 100644 index 0000000000..4607b61065 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md @@ -0,0 +1,7 @@ +
      + +When you're done, click **Continue** to configure automatic grading and feedback for the project. + +
      + 'Continue' button +
      diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-click-create-assignment-button.md new file mode 100644 index 0000000000..935d73f5df --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-click-create-assignment-button.md @@ -0,0 +1,5 @@ +To create the assignment, click **Create assignment**. + +
      + 'Create assignment' button +
      diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-create-review-pull-request.md new file mode 100644 index 0000000000..5cc14ee9ff --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-create-review-pull-request.md @@ -0,0 +1,5 @@ +To create pull requests for the discussion of feedback, select **Enable feedback pull requests**. + +
      + Checkbox for 'Enable feedback pull requests' +
      diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-create-the-assignment.md new file mode 100644 index 0000000000..051e169c57 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -0,0 +1,5 @@ +To create an assignment, sign into {% data variables.product.prodname_classroom_with_url %} and navigate to a classroom. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click **New assignment**. + +
      + The 'New assignment' button +
      diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-intro-for-environment.md new file mode 100644 index 0000000000..bda2c39723 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-intro-for-environment.md @@ -0,0 +1 @@ +Optionally, decide whether to provide empty repositories or starter code, and preconfigure a development environment for your students. diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md new file mode 100644 index 0000000000..6290d808ad --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md @@ -0,0 +1,3 @@ +{% data reusables.classroom.classroom-enables-invitation-urls %} + +{% data reusables.classroom.invitation-url-warning %} diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-prevent-changes.md new file mode 100644 index 0000000000..9ef39a18b9 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-prevent-changes.md @@ -0,0 +1,7 @@ +You can prevent students from changing files that contain tests for autograding, or other important files in the assignment repository. + +Under "Protected file paths", type relative paths within the repository to protect. + +
      + Text field for typing protected file paths +
      \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/ru-RU/data/reusables/classroom/assignments-guide-using-autograding.md new file mode 100644 index 0000000000..5f50beec64 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-guide-using-autograding.md @@ -0,0 +1,23 @@ +{% data reusables.classroom.about-autograding %} For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." + +{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} For more information, see "[Grading methods](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)." + +
      + Using the 'Add test' drop-down menu to click a grading method +
      + +
      + +Define the parameters of your test case, like the name, commands, inputs, outputs, timeout, and points. When you're done, click **Save test case**. + +
      + 'Save test case' button for an autograding test +
      + +
      + +You can add more tests with the **Add test** drop-down menu, and you can edit or delete existing tests with {% octicon "pencil" aria-label="The pencil icon" %} or {% octicon "trash" aria-label="The trash icon" %}. + +
      + Pencil and trash icons to edit or delete an autograding test +
      \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/classroom/assignments-individual-definition.md b/translations/ru-RU/data/reusables/classroom/assignments-individual-definition.md new file mode 100644 index 0000000000..33425ae2c3 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-individual-definition.md @@ -0,0 +1 @@ +An individual assignment is coursework for each student who participates in a course on {% data variables.product.prodname_classroom %}. The student is intended to complete an individual assignment without help from other students. diff --git a/translations/ru-RU/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/ru-RU/data/reusables/classroom/assignments-to-prevent-submission.md new file mode 100644 index 0000000000..62bd9cc2da --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-to-prevent-submission.md @@ -0,0 +1 @@ +To prevent acceptance or submission of an assignment by students, deselect **Enable assignment invitation URL**. To edit the assignment, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment**. diff --git a/translations/ru-RU/data/reusables/classroom/assignments-type-a-title.md b/translations/ru-RU/data/reusables/classroom/assignments-type-a-title.md new file mode 100644 index 0000000000..20d32397ac --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/assignments-type-a-title.md @@ -0,0 +1,5 @@ +Type a title for the assignment. Optionally, click {% octicon "pencil" aria-label="The pencil icon" %} to edit the prefix. + +
      + Assignment title and prefix +
      diff --git a/translations/ru-RU/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/ru-RU/data/reusables/classroom/classroom-creates-group-repositories.md new file mode 100644 index 0000000000..10cdc5924a --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/classroom-creates-group-repositories.md @@ -0,0 +1 @@ +For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.product_name %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. diff --git a/translations/ru-RU/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/ru-RU/data/reusables/classroom/classroom-creates-individual-repositories.md new file mode 100644 index 0000000000..4108abf9ad --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -0,0 +1 @@ +When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.product_name %}. diff --git a/translations/ru-RU/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/ru-RU/data/reusables/classroom/classroom-enables-invitation-urls.md new file mode 100644 index 0000000000..1b357c3a2d --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/classroom-enables-invitation-urls.md @@ -0,0 +1 @@ +By default, {% data variables.product.prodname_classroom %} enables an invitation URL for each assignment you create. Students can accept and submit the assignment while the invitation URL is enabled. You can share the URL with your students on your LMS, course homepage, or wherever you post assignments. Students can also navigate to the assignment on {% data variables.product.prodname_classroom %} if the student has already accepted an assignment for the classroom. diff --git a/translations/ru-RU/data/reusables/classroom/click-assignment-in-list.md b/translations/ru-RU/data/reusables/classroom/click-assignment-in-list.md new file mode 100644 index 0000000000..347d0bc108 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/click-assignment-in-list.md @@ -0,0 +1 @@ +1. In the list of assignments, click the assignment you want to view. ![Assignment in list of assignments for an classroom](/assets/images/help/classroom/click-assignment-in-list.png) diff --git a/translations/ru-RU/data/reusables/classroom/click-classroom-in-list.md b/translations/ru-RU/data/reusables/classroom/click-classroom-in-list.md new file mode 100644 index 0000000000..fe7d091cdc --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/click-classroom-in-list.md @@ -0,0 +1 @@ +1. In the list of classrooms, click the classroom you want to view. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) diff --git a/translations/ru-RU/data/reusables/classroom/click-settings.md b/translations/ru-RU/data/reusables/classroom/click-settings.md new file mode 100644 index 0000000000..9fe6b33d6b --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/click-settings.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" tab for classroom](/assets/images/help/classroom/click-settings.png) diff --git a/translations/ru-RU/data/reusables/classroom/click-students.md b/translations/ru-RU/data/reusables/classroom/click-students.md new file mode 100644 index 0000000000..13df0b1e40 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/click-students.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**. !["Students" tab for classroom](/assets/images/help/classroom/click-students.png) diff --git a/translations/ru-RU/data/reusables/classroom/for-more-information-about-assignment-creation.md b/translations/ru-RU/data/reusables/classroom/for-more-information-about-assignment-creation.md new file mode 100644 index 0000000000..8fd113d763 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/for-more-information-about-assignment-creation.md @@ -0,0 +1 @@ +For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." 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 new file mode 100644 index 0000000000..e554d4b605 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/guide-create-new-classroom.md @@ -0,0 +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. 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/classroom/invitation-url-warning.md b/translations/ru-RU/data/reusables/classroom/invitation-url-warning.md new file mode 100644 index 0000000000..f85e808ddc --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/invitation-url-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning**: Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a user account on {% data variables.product.product_name %} with an identifier in your roster. + +{% endwarning %} diff --git a/translations/ru-RU/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/ru-RU/data/reusables/classroom/readme-contains-button-for-online-ide.md new file mode 100644 index 0000000000..fac85f79f1 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -0,0 +1 @@ +When a student accepts an assignment with an online IDE, the assignment repository will include a _README.md_ file with a special button at the top of the file. The button links the student directly to the workspace in the online IDE. diff --git a/translations/ru-RU/data/reusables/classroom/sign-into-github-classroom.md b/translations/ru-RU/data/reusables/classroom/sign-into-github-classroom.md new file mode 100644 index 0000000000..578bf7213e --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/sign-into-github-classroom.md @@ -0,0 +1 @@ +1. Sign into {% data variables.product.prodname_classroom_with_url %}. diff --git a/translations/ru-RU/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/ru-RU/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md new file mode 100644 index 0000000000..2486daf0a4 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md @@ -0,0 +1 @@ +Under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. diff --git a/translations/ru-RU/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/ru-RU/data/reusables/classroom/you-can-choose-a-template-repository.md new file mode 100644 index 0000000000..40eb9d273b --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -0,0 +1 @@ +You can optionally choose a template repository as starter code for the assignment. The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}. diff --git a/translations/ru-RU/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/ru-RU/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md new file mode 100644 index 0000000000..e9592fb832 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md @@ -0,0 +1 @@ +You can automatically create a pull request where you can provide feedback and answer a student's questions about an assignment. For more information about the review of changes in a pull request, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)." diff --git a/translations/ru-RU/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md b/translations/ru-RU/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md new file mode 100644 index 0000000000..af5be0c098 --- /dev/null +++ b/translations/ru-RU/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md @@ -0,0 +1 @@ +You may want to predefine the default settings for the assignment repositories that {% data variables.product.prodname_classroom %} creates from a template repository. For example, you may want to disable issues, define labels for pull requests, or protect a branch in some or all of the repositories. diff --git a/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md b/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md new file mode 100644 index 0000000000..b8d2b78cbc --- /dev/null +++ b/translations/ru-RU/data/reusables/dependabot/private-dependencies-note.md @@ -0,0 +1,3 @@ +When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)." + +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file 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 fc99299bc2..b36b0b6cb7 100644 --- a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md @@ -1,20 +1,23 @@ -| Package manager | Supports vendoring | -| -------------------------------- |:------------------:| -| Bundler: `bundler` | **X** | -| Cargo: `cargo` | | -| Composer: `composer` | | -| Docker: `docker` | | -| Elm: `elm` | | -| git submodule: `gitsubmodule` | | -| GitHub Actions: `github-actions` | | -| Go modules: `gomod` | **X** | -| Gradle: `gradle` | | -| Maven: `maven` | | -| Mix: `mix` | | -| npm: `npm` | | -| NuGet: `nuget` | | -| pip: `pip` | | -| Terraform: `terraform` | | +The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. + +| Package manager | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | +| -------------------------------- |:-----------------------------------------------------------------:|:---------:| +| Bundler: `bundler` | | **✓** | +| Cargo: `cargo` | **✓** | | +| Composer: `composer` | **✓** | | +| Docker: `docker` | **✓** | | +| Elixir: `hex` | | | +| Elm: `elm` | **✓** | | +| git submodule: `gitsubmodule` | **✓** | | +| GitHub Actions: `github-actions` | **✓** | | +| Go modules: `gomod` | **✓** | **✓** | +| Gradle: `gradle` | **✓** | | +| Maven: `maven` | **✓** | | +| Mix: `mix` | **✓** | | +| npm: `npm` | **✓** | | +| NuGet: `nuget` | **✓** | | +| pip: `pip` | | | +| Terraform: `terraform` | **✓** | | {% note %} diff --git a/translations/ru-RU/data/reusables/discussions/about-categories-and-formats.md b/translations/ru-RU/data/reusables/discussions/about-categories-and-formats.md new file mode 100644 index 0000000000..a17ca2ca53 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/about-categories-and-formats.md @@ -0,0 +1 @@ +All discussions must be created in a category, and repository administrators and maintainers define the categories for a repository. Categories can contain open-ended conversations, or conversations with a question/answer format. diff --git a/translations/ru-RU/data/reusables/discussions/about-discussions.md b/translations/ru-RU/data/reusables/discussions/about-discussions.md new file mode 100644 index 0000000000..c61b8b0f0a --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/about-discussions.md @@ -0,0 +1 @@ +Discussions are an open forum for conversation among maintainers and the community for a project on {% data variables.product.product_name %}. diff --git a/translations/ru-RU/data/reusables/discussions/beta.md b/translations/ru-RU/data/reusables/discussions/beta.md new file mode 100644 index 0000000000..8562a9025f --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_discussions %} is currently in beta and subject to change. + +{% endnote %} diff --git a/translations/ru-RU/data/reusables/discussions/click-discussion-in-list.md b/translations/ru-RU/data/reusables/discussions/click-discussion-in-list.md new file mode 100644 index 0000000000..8156c86331 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/click-discussion-in-list.md @@ -0,0 +1 @@ +1. In the list of discussions, click the discussion you want to view. ![Discussion in list of discussions for a repository](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/ru-RU/data/reusables/discussions/discussions-tab.md b/translations/ru-RU/data/reusables/discussions/discussions-tab.md new file mode 100644 index 0000000000..67795aa5ae --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/discussions-tab.md @@ -0,0 +1 @@ +1. Under your repository name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. !["Discussions" tab for a repository](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/translations/ru-RU/data/reusables/discussions/edit-categories.md b/translations/ru-RU/data/reusables/discussions/edit-categories.md new file mode 100644 index 0000000000..6f4f6af574 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/edit-categories.md @@ -0,0 +1 @@ +1. To the right of "Categories", click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing categories](/assets/images/help/discussions/click-edit-categories.png) diff --git a/translations/ru-RU/data/reusables/discussions/edit-category-details.md b/translations/ru-RU/data/reusables/discussions/edit-category-details.md new file mode 100644 index 0000000000..8004b70314 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/edit-category-details.md @@ -0,0 +1 @@ +Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." diff --git a/translations/ru-RU/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/ru-RU/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md new file mode 100644 index 0000000000..a43c0686b0 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -0,0 +1,5 @@ +You can enable or disable discussions for a repository. + +{% data reusables.repositories.navigate-to-repo %} +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. ![Repository settings button](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", select **Discussions**. ![Checkbox under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/ru-RU/data/reusables/discussions/github-recognizes-members.md b/translations/ru-RU/data/reusables/discussions/github-recognizes-members.md new file mode 100644 index 0000000000..b6874b910d --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/github-recognizes-members.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. diff --git a/translations/ru-RU/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/ru-RU/data/reusables/discussions/marking-a-comment-as-an-answer.md new file mode 100644 index 0000000000..bdefffdea0 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -0,0 +1,14 @@ +You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +When you mark a question as an answer, {% data variables.product.product_name %} will highlight the comment and replies to the comment to help visitors quickly find the answer. + +![Comment marked as answer to a discussion](/assets/images/help/discussions/comment-marked-as-answer.png) + +You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the unanswered discussion you want to mark as answered. ![Unanswered discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the discussion, find the comment you want to mark as the answer. +1. In the upper-right corner of the comment, click {% octicon "check-circle" aria-label="The circular check icon" %}. !["Mark as answer" circular check icon for marking comment as answer in a discussion](/assets/images/help/discussions/comment-mark-as-answer-button.png) +1. Optionally, to unmark a comment as the answer, click {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. diff --git a/translations/ru-RU/data/reusables/discussions/repository-category-limit.md b/translations/ru-RU/data/reusables/discussions/repository-category-limit.md new file mode 100644 index 0000000000..293d3632b5 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/repository-category-limit.md @@ -0,0 +1 @@ +Each repository can have up to 10 categories. diff --git a/translations/ru-RU/data/reusables/discussions/starting-a-discussion.md b/translations/ru-RU/data/reusables/discussions/starting-a-discussion.md new file mode 100644 index 0000000000..242e3abf9b --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/starting-a-discussion.md @@ -0,0 +1,6 @@ +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Click **New discussion**. !["New discussion" button within the "Discussions" tab for a repository](/assets/images/help/discussions/new-discussion-button.png) +1. Select the **Select Category** drop-down menu, and click a category for your discussion. !["Select Category" drop-down menu and list of available categories in a repository](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) +1. Type a title and body for your discussion. ![Text fields for new discussion's title and body](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) diff --git a/translations/ru-RU/data/reusables/discussions/you-can-categorize-discussions.md b/translations/ru-RU/data/reusables/discussions/you-can-categorize-discussions.md new file mode 100644 index 0000000000..bb05316d77 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/you-can-categorize-discussions.md @@ -0,0 +1 @@ +You can categorize discussions to help community members begin conversations in the right place, and to help community members find related discussions. diff --git a/translations/ru-RU/data/reusables/discussions/you-can-convert-an-issue.md b/translations/ru-RU/data/reusables/discussions/you-can-convert-an-issue.md new file mode 100644 index 0000000000..1421256e1f --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/you-can-convert-an-issue.md @@ -0,0 +1 @@ +If an issue turns out to be a question or open-ended conversation instead of a work item to track and prioritize, you can convert the issue to a discussion. diff --git a/translations/ru-RU/data/reusables/discussions/you-can-use-discussions.md b/translations/ru-RU/data/reusables/discussions/you-can-use-discussions.md new file mode 100644 index 0000000000..27c1ba7cb2 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/you-can-use-discussions.md @@ -0,0 +1 @@ +You can use discussions to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/discussions/you-cannot-convert-a-discussion.md b/translations/ru-RU/data/reusables/discussions/you-cannot-convert-a-discussion.md new file mode 100644 index 0000000000..9e9b687b67 --- /dev/null +++ b/translations/ru-RU/data/reusables/discussions/you-cannot-convert-a-discussion.md @@ -0,0 +1 @@ +You cannot convert a discussion to an issue. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/ru-RU/data/reusables/dotcom_billing/actions-packages-unpaid-account.md index cb9dac9ca3..dc87bcb5ee 100644 --- a/translations/ru-RU/data/reusables/dotcom_billing/actions-packages-unpaid-account.md +++ b/translations/ru-RU/data/reusables/dotcom_billing/actions-packages-unpaid-account.md @@ -2,4 +2,4 @@ If your account has outstanding unpaid charges: * The storage or minutes included in your account for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} will not be reset until the payment has been successfully processed. * For accounts with storage or minutes remaining for the current billing period, {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} will continue to be available until any included usage has been reached. -* For accounts that have reached the included usage for the current billing period for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} will be disabled to prevent any further overages. If you pay your account by invoice, you must [contact our account management team](https://enterprise.github.com/contact) to process payment and reset your usage. +* For accounts that have reached the included usage for the current billing period for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} will be disabled to prevent any further overages. 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 1d0ef762d6..67fa09ec6a 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 %}](https://education.github.com/partners/schools)." +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/teach-and-learn-with-github-education/about-github-education)." diff --git a/translations/ru-RU/data/reusables/education/apply-for-team.md b/translations/ru-RU/data/reusables/education/apply-for-team.md index afc1ef555d..88fdff7f90 100644 --- a/translations/ru-RU/data/reusables/education/apply-for-team.md +++ b/translations/ru-RU/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- Apply for free [{% data variables.product.prodname_team %}](/articles/github-s-products), which allows unlimited users and private repositories. For more information, see "[Applying for an educator or researcher discount](/articles/applying-for-an-educator-or-researcher-discount)." +- Apply for free [{% data variables.product.prodname_team %}](/articles/github-s-products), which allows unlimited users and private repositories. For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." diff --git a/translations/ru-RU/data/reusables/education/click-get-teacher-benefits.md b/translations/ru-RU/data/reusables/education/click-get-teacher-benefits.md new file mode 100644 index 0000000000..25bbacd747 --- /dev/null +++ b/translations/ru-RU/data/reusables/education/click-get-teacher-benefits.md @@ -0,0 +1 @@ +1. Under "Individuals", click **Get teacher benefits**. !["Get teacher benefits" on {% data variables.product.prodname_education %} homepage](/assets/images/help/education/click-get-teacher-benefits.png) diff --git a/translations/ru-RU/data/reusables/education/educator-requirements.md b/translations/ru-RU/data/reusables/education/educator-requirements.md new file mode 100644 index 0000000000..b7a004744d --- /dev/null +++ b/translations/ru-RU/data/reusables/education/educator-requirements.md @@ -0,0 +1,6 @@ +To apply for an educator or researcher discount, you must meet the following requirements. + +- Be an educator, faculty member, or researcher. +- Have a verifiable school-issued email address. +- Upload documents that prove your school affiliation. +- Have a user account on {% data variables.product.product_name %}. diff --git a/translations/ru-RU/data/reusables/gated-features/discussions.md b/translations/ru-RU/data/reusables/gated-features/discussions.md new file mode 100644 index 0000000000..5ada0a25ee --- /dev/null +++ b/translations/ru-RU/data/reusables/gated-features/discussions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_discussions %} is available in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/ru-RU/data/reusables/github-actions/actions-billing.md b/translations/ru-RU/data/reusables/github-actions/actions-billing.md index 947b31a56d..4e12946e9b 100644 --- a/translations/ru-RU/data/reusables/github-actions/actions-billing.md +++ b/translations/ru-RU/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account. +{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ru-RU/data/reusables/github-actions/actions-on-examples.md b/translations/ru-RU/data/reusables/github-actions/actions-on-examples.md index beea3062f5..06efe2e4ea 100644 --- a/translations/ru-RU/data/reusables/github-actions/actions-on-examples.md +++ b/translations/ru-RU/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -##### **Example using a single event** +##### Example using a single event ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -##### **Example using a list of events** +##### Example using a list of events ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -##### **Example using multiple events with activity types or configuration** +##### Example using multiple events with activity types or configuration If you need to specify activity types or configuration for an event, you must configure each event separately. You must append a colon (`:`) to all events, including events without configuration. diff --git a/translations/ru-RU/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/ru-RU/data/reusables/github-actions/actions-spending-limit-brief.md new file mode 100644 index 0000000000..20d912fb21 --- /dev/null +++ b/translations/ru-RU/data/reusables/github-actions/actions-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/ru-RU/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/ru-RU/data/reusables/github-actions/actions-spending-limit-detailed.md new file mode 100644 index 0000000000..062eef3c3f --- /dev/null +++ b/translations/ru-RU/data/reusables/github-actions/actions-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.github-actions.actions-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where a workflow is run. Any coupons on your account do not apply to {% data variables.product.prodname_actions %} overages. diff --git a/translations/ru-RU/data/reusables/github-actions/contacting-support.md b/translations/ru-RU/data/reusables/github-actions/contacting-support.md index c3d307a405..d4bcb7c776 100644 --- a/translations/ru-RU/data/reusables/github-actions/contacting-support.md +++ b/translations/ru-RU/data/reusables/github-actions/contacting-support.md @@ -1,4 +1,4 @@ -If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} board](https://github.community/c/github-actions). +If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). If you have feedback or feature requests for {% data variables.product.prodname_actions %}, share those in the {% data variables.contact.contact_feedback_actions %}. diff --git a/translations/ru-RU/data/reusables/github-actions/macos-runner-preview.md b/translations/ru-RU/data/reusables/github-actions/macos-runner-preview.md index 88a2d482c4..e6db4f8803 100644 --- a/translations/ru-RU/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/ru-RU/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The MacOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the MacOS 10.15 virtual environment. +**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/ru-RU/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/ru-RU/data/reusables/github-actions/publish-to-maven-workflow-step.md index 24292b0b12..fec15a1815 100644 --- a/translations/ru-RU/data/reusables/github-actions/publish-to-maven-workflow-step.md +++ b/translations/ru-RU/data/reusables/github-actions/publish-to-maven-workflow-step.md @@ -1 +1 @@ -Runs the `mvn -B deploy` command to publish to the `ossrh` repository. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. +Runs the `mvn --batch-mode deploy` command to publish to the `ossrh` repository. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. diff --git a/translations/ru-RU/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/ru-RU/data/reusables/github-actions/publish-to-packages-workflow-step.md index aa0c63eeea..743020588d 100644 --- a/translations/ru-RU/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ b/translations/ru-RU/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -Runs the `mvn -B deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret. +Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret. diff --git a/translations/ru-RU/data/reusables/github-insights/download-latest-release.md b/translations/ru-RU/data/reusables/github-insights/download-latest-release.md index 207d17df7f..9f144cfd30 100644 --- a/translations/ru-RU/data/reusables/github-insights/download-latest-release.md +++ b/translations/ru-RU/data/reusables/github-insights/download-latest-release.md @@ -1,3 +1,3 @@ -1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the [Releases page](https://github.com/github/insights-releases/releases/latest) for `github/insights-releases`. +1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the Releases page for `github/insights-releases`. 2. To download the latest release, under "Assets", click `insights-VERSION.tar.gz`. ![Installation assset](/assets/images/help/insights/installation-tgz.png) 3. Unzip the directory. diff --git a/translations/ru-RU/data/reusables/marketplace/app-transfer-to-org-for-verification.md b/translations/ru-RU/data/reusables/marketplace/app-transfer-to-org-for-verification.md new file mode 100644 index 0000000000..0621a9e6e9 --- /dev/null +++ b/translations/ru-RU/data/reusables/marketplace/app-transfer-to-org-for-verification.md @@ -0,0 +1 @@ +If you want to sell an app that's owned by your user account, first you'll need to transfer the app to an organization, and then request verification for a listing created by the organization. diff --git a/translations/ru-RU/data/reusables/marketplace/free-plan-note.md b/translations/ru-RU/data/reusables/marketplace/free-plan-note.md new file mode 100644 index 0000000000..bf63caa53d --- /dev/null +++ b/translations/ru-RU/data/reusables/marketplace/free-plan-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** If you're listing an app on {% data variables.product.prodname_marketplace %}, you can't list your app with a free pricing plan if you offer a paid service outside of {% data variables.product.prodname_marketplace %}. + +{% endnote %} diff --git a/translations/ru-RU/data/reusables/marketplace/launch-with-free.md b/translations/ru-RU/data/reusables/marketplace/launch-with-free.md index 15230e218b..2151c241cc 100644 --- a/translations/ru-RU/data/reusables/marketplace/launch-with-free.md +++ b/translations/ru-RU/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -You can submit both an unverified and verified app. This will allow you to launch with a free version of your app. Once GitHub verifies your app, your listing will change from unverified to verified in {% data variables.product.prodname_marketplace %} and GitHub will publish your new pricing plans. +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/ru-RU/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/ru-RU/data/reusables/marketplace/marketplace-billing-ui-requirements.md index 9c02badeae..5aa91ca839 100644 --- a/translations/ru-RU/data/reusables/marketplace/marketplace-billing-ui-requirements.md +++ b/translations/ru-RU/data/reusables/marketplace/marketplace-billing-ui-requirements.md @@ -1,7 +1,7 @@ -- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} must be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} It's highly recommended to allow customers to re-enable their previous plan. -- Customers must be able to upgrade from your app's UI if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` -- Customers must be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. -- Customers must be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: +- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} should be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} It's highly recommended to allow customers to re-enable their previous plan. +- Customers should be able to upgrade from your app's user interface if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` +- Customers should be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. +- Customers should be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: - Current plan and price. - New plans purchased. - Upgrades, downgrades, cancellations, and the number of remaining days in a free trial. diff --git a/translations/ru-RU/data/reusables/package_registry/authenticate-packages.md b/translations/ru-RU/data/reusables/package_registry/authenticate-packages.md index 89915a62e8..aee972b1ba 100644 --- a/translations/ru-RU/data/reusables/package_registry/authenticate-packages.md +++ b/translations/ru-RU/data/reusables/package_registry/authenticate-packages.md @@ -3,7 +3,7 @@ You need an access token to publish, install, and delete packages. You can use a {% if currentVersion == "free-pro-team@latest" %} To authenticate using a {% data variables.product.prodname_actions %} workflow: -- For package registries (`PACKAGE-REGISTRY.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`), you can use a `GITHUB_TOKEN`. +- 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. {% else %} To authenticate to diff --git a/translations/ru-RU/data/reusables/package_registry/billing-for-container-registry.md b/translations/ru-RU/data/reusables/package_registry/billing-for-container-registry.md index 7cf8e2459f..479e2d5b55 100644 --- a/translations/ru-RU/data/reusables/package_registry/billing-for-container-registry.md +++ b/translations/ru-RU/data/reusables/package_registry/billing-for-container-registry.md @@ -1,3 +1,3 @@ -During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." +During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/guides/configuring-docker-for-use-with-github-packages)." After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the container registry. 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)." diff --git a/translations/ru-RU/data/reusables/package_registry/container-registry-beta-billing-note.md b/translations/ru-RU/data/reusables/package_registry/container-registry-beta-billing-note.md index ccc4fc14f8..f588ab6f9b 100644 --- a/translations/ru-RU/data/reusables/package_registry/container-registry-beta-billing-note.md +++ b/translations/ru-RU/data/reusables/package_registry/container-registry-beta-billing-note.md @@ -1,5 +1,5 @@ {% note %} -**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." +**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)." {% endnote %} diff --git a/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md b/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md index 24313880ba..6bd738198e 100644 --- a/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md +++ b/translations/ru-RU/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" and "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} diff --git a/translations/ru-RU/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/ru-RU/data/reusables/package_registry/docker_registry_deprecation_status.md index 2df9364c31..a23fdc598b 100644 --- a/translations/ru-RU/data/reusables/package_registry/docker_registry_deprecation_status.md +++ b/translations/ru-RU/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -1,5 +1,5 @@ {% warning %} -**Note:** The {% data variables.product.prodname_registry %} Docker registry will be superseded by {% data variables.product.prodname_github_container_registry %}{% if enterpriseServerVersions contains currentVersion %} in a future {% data variables.product.product_name %} release{% endif %}.{% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" and "[Getting started with {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry)."{% endif %} +**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 %} {% endwarning %} diff --git a/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md index b0cddc8bcb..3b74dd6c78 100644 --- a/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md +++ b/translations/ru-RU/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/package_registry/packages-billing.md b/translations/ru-RU/data/reusables/package_registry/packages-billing.md index 7a93df94ba..adc9c87bed 100644 --- a/translations/ru-RU/data/reusables/package_registry/packages-billing.md +++ b/translations/ru-RU/data/reusables/package_registry/packages-billing.md @@ -1 +1 @@ -{% data variables.product.prodname_registry %} usage is free for public packages. For private packages, each {% data variables.product.product_name %} account receives a certain amount of free storage and data transfer, depending on the product used with the account. By default, your account will have a spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you increase your spending limit above the default of $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. Any coupons on your account do not apply to {% data variables.product.prodname_registry %} overages. +{% data variables.product.prodname_registry %} usage is free for public packages. For private packages, each {% data variables.product.product_name %} account receives a certain amount of free storage and data transfer, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/ru-RU/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/ru-RU/data/reusables/package_registry/packages-spending-limit-brief.md new file mode 100644 index 0000000000..ea07621d29 --- /dev/null +++ b/translations/ru-RU/data/reusables/package_registry/packages-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/ru-RU/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/ru-RU/data/reusables/package_registry/packages-spending-limit-detailed.md new file mode 100644 index 0000000000..2719322745 --- /dev/null +++ b/translations/ru-RU/data/reusables/package_registry/packages-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.package_registry.packages-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. Any coupons on your account do not apply to {% data variables.product.prodname_registry %} overages. diff --git a/translations/ru-RU/data/reusables/package_registry/required-scopes.md b/translations/ru-RU/data/reusables/package_registry/required-scopes.md index ec9748d65a..364cdccaef 100644 --- a/translations/ru-RU/data/reusables/package_registry/required-scopes.md +++ b/translations/ru-RU/data/reusables/package_registry/required-scopes.md @@ -1 +1 @@ -You must use a personal access token with the appropriate scopes to publish and install packages in {% data variables.product.prodname_registry %}. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +You must use a personal access token with the appropriate scopes to publish and install packages in {% data variables.product.prodname_registry %}. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)." diff --git a/translations/ru-RU/data/reusables/package_registry/viewing-packages.md b/translations/ru-RU/data/reusables/package_registry/viewing-packages.md index 7a16420a97..131b04989a 100644 --- a/translations/ru-RU/data/reusables/package_registry/viewing-packages.md +++ b/translations/ru-RU/data/reusables/package_registry/viewing-packages.md @@ -1 +1 @@ -After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/publishing-and-managing-packages/viewing-packages)." +After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)." diff --git a/translations/ru-RU/data/reusables/repositories/dependency-review.md b/translations/ru-RU/data/reusables/repositories/dependency-review.md new file mode 100644 index 0000000000..e780074c3c --- /dev/null +++ b/translations/ru-RU/data/reusables/repositories/dependency-review.md @@ -0,0 +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)." +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/repositories/navigate-to-job-superlinter.md b/translations/ru-RU/data/reusables/repositories/navigate-to-job-superlinter.md index 3c79e1a1a6..afa0402d6b 100644 --- a/translations/ru-RU/data/reusables/repositories/navigate-to-job-superlinter.md +++ b/translations/ru-RU/data/reusables/repositories/navigate-to-job-superlinter.md @@ -1,5 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. Under **Jobs** or in the visualization graph, click the job you want to see. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. In the left sidebar, click the job you want to see. ![Lint code base job](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% else %} 1. In the left sidebar, click the job you want to see. ![Select a workflow job](/assets/images/help/repository/workflow-job.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ru-RU/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/ru-RU/data/reusables/repositories/two-dot-diff-comparison-example-urls.md index 5dbca8831b..1a25944892 100644 --- a/translations/ru-RU/data/reusables/repositories/two-dot-diff-comparison-example-urls.md +++ b/translations/ru-RU/data/reusables/repositories/two-dot-diff-comparison-example-urls.md @@ -1 +1 @@ -For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f.` +For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`. diff --git a/translations/ru-RU/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/ru-RU/data/reusables/repositories/view-failed-job-results-superlinter.md index 434994a169..d436c99e66 100644 --- a/translations/ru-RU/data/reusables/repositories/view-failed-job-results-superlinter.md +++ b/translations/ru-RU/data/reusables/repositories/view-failed-job-results-superlinter.md @@ -1,5 +1,8 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Any failed steps are automatically expanded to display the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png) +1. Any failed steps are automatically expanded to display the results. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %} +![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png){% endif %} {% else %} 1. Expand the **Run Super-Linter** step to view the results. ![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results.png) {% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/repositories/view-specific-line-superlinter.md b/translations/ru-RU/data/reusables/repositories/view-specific-line-superlinter.md index ae70f1762f..5695e5746a 100644 --- a/translations/ru-RU/data/reusables/repositories/view-specific-line-superlinter.md +++ b/translations/ru-RU/data/reusables/repositories/view-specific-line-superlinter.md @@ -1,5 +1,10 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. Optionally, to get a link to a specific line in the logs, click on the step's line number. You can then copy the link from the address bar of your web browser. ![Button to copy link](/assets/images/help/repository/copy-link-button-updated.png) +1. Optionally, to get a link to a specific line in the logs, click on the step's line number. You can then copy the link from the address bar of your web browser. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Button to copy link](/assets/images/help/repository/copy-link-button-updated-2.png) + {% else %} + ![Button to copy link](/assets/images/help/repository/copy-link-button-updated.png) + {% endif %} {% else %} 1. Optionally, to get a link to a specific line in the logs, click on the step's line number. You can then copy the link from the address bar of your web browser. ![Button to copy link](/assets/images/help/repository/copy-link-button.png) {% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/search/date_gt_lt.md b/translations/ru-RU/data/reusables/search/date_gt_lt.md index 960f02127d..57a206f28c 100644 --- a/translations/ru-RU/data/reusables/search/date_gt_lt.md +++ b/translations/ru-RU/data/reusables/search/date_gt_lt.md @@ -1 +1 @@ -Dates support [greater than, less than, and range qualifiers](/articles/understanding-the-search-syntax). +When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." diff --git a/translations/ru-RU/data/reusables/secret-scanning/api-beta.md b/translations/ru-RU/data/reusables/secret-scanning/api-beta.md new file mode 100644 index 0000000000..510473ea8d --- /dev/null +++ b/translations/ru-RU/data/reusables/secret-scanning/api-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The {% data variables.product.prodname_secret_scanning %} API is currently in beta and subject to change. + +{% endnote %} diff --git a/translations/ru-RU/data/reusables/sponsors/billing-switcher.md b/translations/ru-RU/data/reusables/sponsors/billing-switcher.md new file mode 100644 index 0000000000..4831c34a3b --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/billing-switcher.md @@ -0,0 +1 @@ +1. Optionally, to manage your sponsorship on behalf of an organization, in the upper-left corner, use the **Personal settings** drop-down menu, and click the organization. ![Drop-down menu to switch accounts for settings](/assets/images/help/sponsors/billing-account-switcher.png) diff --git a/translations/ru-RU/data/reusables/sponsors/change-tier.md b/translations/ru-RU/data/reusables/sponsors/change-tier.md index 9770dfebd1..e805d6d08a 100644 --- a/translations/ru-RU/data/reusables/sponsors/change-tier.md +++ b/translations/ru-RU/data/reusables/sponsors/change-tier.md @@ -1 +1 @@ -1. 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 **Change tier**. ![Change tier button](/assets/images/help/billing/edit-sponsor-billing.png) +1. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored account, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your tier amount, then click **Change tier**. ![Change tier button](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/ru-RU/data/reusables/sponsors/choose-updates.md b/translations/ru-RU/data/reusables/sponsors/choose-updates.md new file mode 100644 index 0000000000..ade59cf05b --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/choose-updates.md @@ -0,0 +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) diff --git a/translations/ru-RU/data/reusables/sponsors/manage-sponsorship.md b/translations/ru-RU/data/reusables/sponsors/manage-sponsorship.md new file mode 100644 index 0000000000..fb0b480922 --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/manage-sponsorship.md @@ -0,0 +1 @@ +1. To the right of your current tier, click **Manage**. ![Manage your sponsorship button](/assets/images/help/sponsors/manage-your-sponsorship-button.png) \ No newline at end of file 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 new file mode 100644 index 0000000000..0cd08d5382 --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/manage-updates-for-orgs.md @@ -0,0 +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)." diff --git a/translations/ru-RU/data/reusables/sponsors/maximum-tier.md b/translations/ru-RU/data/reusables/sponsors/maximum-tier.md index a787f1dd0a..803658fba4 100644 --- a/translations/ru-RU/data/reusables/sponsors/maximum-tier.md +++ b/translations/ru-RU/data/reusables/sponsors/maximum-tier.md @@ -1 +1 @@ -The maximum price is US$6000 per month. +The maximum price is US$12,000 per month. diff --git a/translations/ru-RU/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/ru-RU/data/reusables/sponsors/navigate-to-sponsored-account.md new file mode 100644 index 0000000000..def70f43f1 --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/navigate-to-sponsored-account.md @@ -0,0 +1 @@ +1. On {% data variables.product.product_name %}, navigate to the sponsored account's profile. diff --git a/translations/ru-RU/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/ru-RU/data/reusables/sponsors/navigate-to-sponsors-dashboard.md new file mode 100644 index 0000000000..0185cfdeed --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/navigate-to-sponsors-dashboard.md @@ -0,0 +1,2 @@ +1. In the upper-right corner of any page, click your profile photo, then click **{% data variables.product.prodname_sponsors %}**. ![{% data variables.product.prodname_sponsors %} button](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) +2. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**. ![Developer sponsors dashboard button](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) diff --git a/translations/ru-RU/data/reusables/sponsors/no-fees.md b/translations/ru-RU/data/reusables/sponsors/no-fees.md index a122d94bbb..dd829bafdc 100644 --- a/translations/ru-RU/data/reusables/sponsors/no-fees.md +++ b/translations/ru-RU/data/reusables/sponsors/no-fees.md @@ -1 +1 @@ -{% data variables.product.prodname_sponsors %} does not charge any fees for sponsorships from user accounts, so 100% of these sponsorships go to the sponsored developer or organization. +{% data variables.product.prodname_sponsors %} does not charge any fees for sponsorships from user accounts, so 100% of these sponsorships go to the sponsored developer or organization. The 10% fee for sponsorships from organizations is waived during the beta. diff --git a/translations/ru-RU/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/ru-RU/data/reusables/sponsors/org-sponsors-release-phase.md new file mode 100644 index 0000000000..75983073a4 --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/org-sponsors-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Sponsoring on behalf of an organization is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/sponsors/pay-prorated-amount.md b/translations/ru-RU/data/reusables/sponsors/pay-prorated-amount.md new file mode 100644 index 0000000000..f201de957c --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/pay-prorated-amount.md @@ -0,0 +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 diff --git a/translations/ru-RU/data/reusables/sponsors/prorated-sponsorship.md b/translations/ru-RU/data/reusables/sponsors/prorated-sponsorship.md index f63d25e339..56a047d867 100644 --- a/translations/ru-RU/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/ru-RU/data/reusables/sponsors/prorated-sponsorship.md @@ -1 +1 @@ -You will immediately be charged a prorated amount for the time until your next regular billing date. +If you're sponsoring on behalf of your user account, you will immediately be charged a prorated amount for the time until your next regular billing date. If you're sponsoring on behalf of an organization, you can choose to pay the prorated amount or make the full monthly payment. diff --git a/translations/ru-RU/data/reusables/sponsors/sponsor-account.md b/translations/ru-RU/data/reusables/sponsors/sponsor-account.md new file mode 100644 index 0000000000..d2f8a2e73d --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/sponsor-account.md @@ -0,0 +1 @@ +1. Click **Sponsor _ACCOUNT_**. ![Sponsor button](/assets/images/help/sponsors/sponsor-developer-button.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/sponsors/sponsorship-dashboard.md b/translations/ru-RU/data/reusables/sponsors/sponsorship-dashboard.md new file mode 100644 index 0000000000..e76cb9b70c --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/sponsorship-dashboard.md @@ -0,0 +1,4 @@ +1. Navigate to your sponsorship dashboard for the account. + - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![Sponsoring button](/assets/images/help/profile/sponsoring-button.png) + - If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![Sponsoring button](/assets/images/help/sponsors/org-sponsoring-button.png) +1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/ru-RU/data/reusables/sponsors/sponsorship-details.md b/translations/ru-RU/data/reusables/sponsors/sponsorship-details.md index 55425b5c0a..6542580736 100644 --- a/translations/ru-RU/data/reusables/sponsors/sponsorship-details.md +++ b/translations/ru-RU/data/reusables/sponsors/sponsorship-details.md @@ -1 +1 @@ -Anyone with a {% data variables.product.product_name %} account can sponsor anyone with a sponsored developer profile or sponsored organization profile through a recurring monthly payment. You can choose from multiple sponsorship tiers, with monthly payment amounts and benefits that are set by the sponsored developer or organization. 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 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/webhooks/app_always_desc.md b/translations/ru-RU/data/reusables/webhooks/app_always_desc.md new file mode 100644 index 0000000000..d52aaebe58 --- /dev/null +++ b/translations/ru-RU/data/reusables/webhooks/app_always_desc.md @@ -0,0 +1 @@ +`installation` | `object` | The {% data variables.product.prodname_github_app %} installation. diff --git a/translations/ru-RU/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/ru-RU/data/reusables/webhooks/secret_scanning_alert_event_properties.md new file mode 100644 index 0000000000..e8778f6204 --- /dev/null +++ b/translations/ru-RU/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -0,0 +1,4 @@ +| Клавиша | Тип | Description | +| ------------ | -------- | --------------------------------------------------------------------------------------- | +| `действие` | `строка` | The action that was performed. This can be either `created`, `resolved`, or `reopened`. | +| `оповещение` | `объект` | The secret scanning alert involved in the event. | diff --git a/translations/ru-RU/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/ru-RU/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md new file mode 100644 index 0000000000..5da7e75271 --- /dev/null +++ b/translations/ru-RU/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -0,0 +1 @@ +Activity related to secret scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see “[About secret scanning](/github/administering-a-repository/about-secret-scanning).” diff --git a/translations/ru-RU/data/ui.yml b/translations/ru-RU/data/ui.yml index dbb583d01a..c144b9cb54 100644 --- a/translations/ru-RU/data/ui.yml +++ b/translations/ru-RU/data/ui.yml @@ -7,7 +7,7 @@ header: release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation. If there's a problem with translations on this page, please let us know. localization_in_progress: Hello, explorer! This page is under active development or still in translation. For the most up-to-date and accurate information, please visit our English documentation. - early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' + early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' search: need_help: Need help? placeholder: Search topics, products... @@ -56,6 +56,14 @@ contribution_cta: button: Make a contribution or: Or, to_guidelines: learn how to contribute. +enterprise_releases_list: + title: Enterprise Server Releases + currently_supported: Currently supported + currently_supported_message: See GitHub Enterprise for information about the latest release. + deprecated: Deprecated + deprecated_message: 'These docs remain available but are no longer maintained:' + deprecated_developer: Deprecated on developer.github.com + deprecated_developer_message: 'These docs remain available on the legacy developer site but are no longer maintained:' products: graphql: reference: @@ -123,3 +131,4 @@ footer: product_landing: quick_start: Quickstart reference_guides: Reference guides + overview: Обзор diff --git a/translations/ru-RU/data/variables/action_code_examples.yml b/translations/ru-RU/data/variables/action_code_examples.yml index 37602b4775..b4c356a4fd 100644 --- a/translations/ru-RU/data/variables/action_code_examples.yml +++ b/translations/ru-RU/data/variables/action_code_examples.yml @@ -1,12 +1,4 @@ --- -- - title: Starter workflows - description: Workflow files for helping people get started with GitHub Actions - languages: TypeScript - href: actions/starter-workflows - tags: - - official - - рабочий процесс - title: Example services description: Example workflows using service containers @@ -334,3 +326,10 @@ - monorepo - copybara - рабочий процесс +- + title: Deploy static files to GitHub Pages + description: GitHub Action to publish website to GitHub Pages automatically + languages: 'TypeScript, JavaScript' + href: peaceiris/actions-gh-pages + tags: + - publishing diff --git a/translations/ru-RU/data/variables/command_line.yml b/translations/ru-RU/data/variables/command_line.yml index 805c67903e..5d1f568716 100644 --- a/translations/ru-RU/data/variables/command_line.yml +++ b/translations/ru-RU/data/variables/command_line.yml @@ -1,5 +1,5 @@ --- -#Use this variable wherever backticks are necessary: https://github.com/github/docs-internal/pull/1176#discussion-diff-19853931 +#Use this variable wherever backticks are necessary backticks: >- {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} #Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!) diff --git a/translations/ru-RU/data/variables/discussions_community_examples.yml b/translations/ru-RU/data/variables/discussions_community_examples.yml new file mode 100644 index 0000000000..8b3594f2ec --- /dev/null +++ b/translations/ru-RU/data/variables/discussions_community_examples.yml @@ -0,0 +1,38 @@ +--- +- + #Images and descriptions are pulled directly from the repo + repo: vercel/next.js + description: The React Framework +- + repo: gatsbyjs/gatsby + description: Build blazing fast, modern apps and websites with React +- + repo: nodejs/node + description: Node.js JavaScript runtime ✨🐢🚀✨ +- + repo: tailwindlabs/tailwindcss + description: A utility-first CSS framework for rapid UI development. +- + repo: laravel/framework + description: Laravel is a web application framework with expressive, elegant syntax. +- + repo: prisma/prisma + description: Modern database access (ORM alternative) for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite +- + repo: dotnet/csharplang + description: 'The official repo for the design of the C# programming language' +- + repo: home-assistant/frontend + description: '🍭 Frontend for Home Assistant' +- + repo: jspsych/jsPsych + description: A JavaScript library for creating and running behavioral experiments in a web browser +- + repo: adonisjs/core + description: '🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence' +- + repo: ImageMagick/ImageMagick + description: '🧙‍♂️ ImageMagick 7' +- + repo: react-hook-form/react-hook-form + description: '📋 React Hooks for forms validation (Web + React Native)' diff --git a/translations/ru-RU/data/variables/product.yml b/translations/ru-RU/data/variables/product.yml index 9f7f04d407..d187b76b37 100644 --- a/translations/ru-RU/data/variables/product.yml +++ b/translations/ru-RU/data/variables/product.yml @@ -37,7 +37,10 @@ prodname_unified_search: 'унифицированный поиск' #GitHub Education prodname_education: 'GitHub Education' prodname_education_community: 'Education Community' +prodname_education_community_with_url: 'the [GitHub Education Community](https://education.github.community)' prodname_classroom: 'GitHub Classroom' +prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)' +prodname_campus_program: 'GitHub Campus Program' prodname_student_pack: 'GitHub Student Developer Pack' #GitHub CLI prodname_cli: 'GitHub CLI' @@ -69,6 +72,8 @@ ae_azure_ad_app_link: 'the [GitHub AE application](https://azuremarketplace.micr prodname_actions: 'GitHub Actions' #GitHub Debug prodname_debug: 'GitHub Debug' +#GitHub Discussions +prodname_discussions: 'GitHub Discussions' #GitHub Packages prodname_registry: 'GitHub Packages' prodname_github_container_registry: 'GitHub Container Registry' 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 b8d68ab601..27e403461a 100644 --- a/translations/zh-CN/content/actions/creating-actions/about-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/about-actions.md @@ -33,8 +33,8 @@ versions: | 类型 | 操作系统 | | ---------- | ------------------- | | Docker 容器 | Linux | -| JavaScript | Linux、MacOS、Windows | -| 组合运行步骤 | Linux、MacOS、Windows | +| JavaScript | Linux、macOS、Windows | +| 组合运行步骤 | Linux、macOS、Windows | #### Docker 容器操作 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 a29a724012..088e6e7dbe 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 @@ -226,6 +226,10 @@ jobs: ``` {% endraw %} -从您的仓库中，单击 **Actions（操作）**选项卡，然后选择最新的工作流程来运行。 您应看到 "Hello Mona the Octocat" 或您用于 `who-to-greet` 输入的姓名和时间戳在日志中打印。 +从您的仓库中，单击 **Actions（操作）**选项卡，然后选择最新的工作流程来运行。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}在 **Jobs（作业）**下或可视化图表中，单击 **A job to say hello（表示问候的作业）**。 {% endif %}您应看到 "Hello Mona the Octocat" 或您用于 `who-to-greet` 输入的姓名和时间戳在日志中打印。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![在工作流中使用操作的屏幕截图](/assets/images/help/repository/docker-action-workflow-run-updated.png) +{% else %} ![在工作流中使用操作的屏幕截图](/assets/images/help/repository/docker-action-workflow-run.png) +{% endif %} 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 f93c36204b..01b69c3100 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 @@ -176,7 +176,7 @@ git tag -a -m "My first action release" v1 git push --follow-tags ``` -作为检入 `node_modules` 目录的替代方法，您可以使用名为 [`@vercel/ncc`](https://github.com/vercel/ncc) 的工具将您的代码和模块编译到一个用于分发的文件中。 +Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution. 1. 通过在您的终端运行此命令来安装 `vercel/ncc`。 `npm i -g @vercel/ncc` @@ -256,9 +256,11 @@ jobs: ``` {% endraw %} -从您的仓库中，单击 **Actions（操作）**选项卡，然后选择最新的工作流程来运行。 您应看到 "Hello Mona the Octocat" 或您用于 `who-to-greet` 输入的姓名和时间戳在日志中打印。 +从您的仓库中，单击 **Actions（操作）**选项卡，然后选择最新的工作流程来运行。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}在 **Jobs（作业）**下或可视化图表中，单击 **A job to say hello（表示问候的作业）**。 {% endif %}您应看到 "Hello Mona the Octocat" 或您用于 `who-to-greet` 输入的姓名和时间戳在日志中打印。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![在工作流中使用操作的屏幕截图](/assets/images/help/repository/javascript-action-workflow-run-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} ![在工作流中使用操作的屏幕截图](/assets/images/help/repository/javascript-action-workflow-run-updated.png) {% else %} ![在工作流中使用操作的屏幕截图](/assets/images/help/repository/javascript-action-workflow-run.png) 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 f2c2d123e2..ce68767feb 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 @@ -22,19 +22,19 @@ Docker 和 JavaScript 操作需要元数据文件。 元数据文件名必须是 操作元数据文件使用 YAML 语法。 如果您是 YAML 的新用户，请参阅“[五分钟了解 YAML](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)”。 -### **`name`** +### `name` **必要** 操作的名称。 {% data variables.product.prodname_dotcom %} 在 **Actions（操作）**选项卡中显示 `name`，帮助从视觉上识别每项作业中的操作。 -### **`作者`** +### `作者` **可选** 操作的作者姓名。 -### **`说明`** +### `说明` **必要** 操作的简短描述。 -### **`inputs`** +### `inputs` **可选** 输入参数用于指定操作在运行时预期使用的数据。 {% data variables.product.prodname_dotcom %} 将输入参数存储为环境变量。 大写的输入 ID 在运行时转换为小写。 建议使用小写输入 ID。 @@ -57,23 +57,23 @@ inputs: 例如，如果工作流程定义了 numOctocats and octocatEyeColor 输入，操作代码可使用 `INPUT_NUMOCTOCATS` 和 `INPUT_OCTOCATEYECOLOR` 环境变量读取输入的值。 -#### **`inputs.`** +#### `inputs.` **必要** 要与输入关联的 `string` 识别符。 `` 的值是输入元数据的映射。 `` 必须是 `inputs` 对象中的唯一识别符。 `` 必须以字母或 `_` 开关，并且只能包含字母数字、`-` 或 `_`。 -#### **`inputs..description`** +#### `inputs..description` **必要** 输入参数的 `string` 描述。 -#### **`inputs..required`** +#### `inputs..required` **必要** 表示操作是否需要输入参数的 `boolean`。 当参数为必要时设置为 `true`。 -#### **`inputs..default`** +#### `inputs..default` **可选** 表示默认值的 `string`。 当工作流程文件中未指定输入参数时使用默认值。 -### **`outputs`** +### `outputs` **可选** 输出参数允许您声明操作所设置的数据。 稍后在工作流程中运行的操作可以使用以前运行操作中的输出数据集。 例如，如果有操作执行两个输入的相加 (x + y = z)，则该操作可能输出总和 (z)，用作其他操作的输入。 @@ -87,15 +87,15 @@ outputs: description: 'The sum of the inputs' ``` -#### **`outputs.`** +#### `outputs.` **必要** 要与输出关联的 `string` 识别符。 `` 的值是输出元数据的映射。 `` 必须是 `outputs` 对象中的唯一识别符。 `` 必须以字母或 `_` 开头，并且只能包含字母数字、`-` 或 `_`。 -#### **`outputs..description`** +#### `outputs..description` **必要** 输出参数的 `string` 描述。 -### 用于组合运行步骤操作的 **`outputs`** +### 用于组合运行步骤操作的 `outputs` **可选** `outputs` 使用与 `outputs.` 及 `outputs..description` 相同的参数（请参阅“用于 {% data variables.product.prodname_actions %} 的 @@ -126,7 +126,7 @@ runs: -#### **`outputs.`** +#### `outputs..value` **必要** 输出参数将会映射到的值。 您可以使用上下文将此设置为 `string` 或表达式。 例如，您可以使用 `steps` 上下文将输出的 `value` 设置为步骤的输出值。 @@ -134,7 +134,7 @@ runs: -### 用于 JavaScript 操作的 **`runs`** +### 用于 JavaScript 操作的 `runs` **必要** 配置操作代码的路径和用于执行代码的应用程序。 @@ -153,19 +153,19 @@ runs: -#### **`runs.using`** +#### `runs.using` **必要** 用于执行 [`main`](#runsmain) 中指定的代码的应用程序。 -#### **`runs.main`** +#### `runs.main` **必要** 包含操作代码的文件。 [`using`](#runsusing) 中指定的应用程序执行此文件。 -#### **`pre`** +#### `pre` **可选** 允许您在 `main:` 操作开始之前，在作业开始时运行脚本。 例如，您可以使用 `pre:` 运行基本要求设置脚本。 使用 [`using`](#runsusing) 语法指定的应用程序将执行此文件。 `pre:` 操作始终默认运行，但您可以使用 [`pre-if`](#pre-if) 覆盖该设置。 @@ -184,7 +184,7 @@ runs: -#### **`pre-if`** +#### `pre-if` **可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 请注意，`step` 上下文不可用，因为尚未运行任何步骤。 @@ -200,7 +200,7 @@ runs: -#### **`post`** +#### `post` **可选** 允许您在 `main:` 操作完成后，在作业结束时运行脚本。 例如，您可以使用 `post:` 终止某些进程或删除不需要的文件。 使用 [`using`](#runsusing) 语法指定的应用程序将执行此文件。 @@ -220,7 +220,7 @@ runs: -#### **`post-if`** +#### `post-if` **可选** 允许您定义 `post:` 操作执行的条件。 `post:` 操作仅在满足 `post-if` 中的条件后运行。 如果未设置，则 `post-if` 默认使用 `always()`。 @@ -236,25 +236,25 @@ runs: -### 用于组合运行步骤操作的 **`runs`** +### 用于组合运行步骤操作的 `runs` **必要** 配置组合操作的路径和用于执行代码的应用程序。 -#### **`runs.using`** +#### `runs.using` **必要** 要使用组合运行步骤操作，请将此设置为 `"composite"`。 -#### **`runs.steps`** +#### `runs.steps` **必要** 您计划在此操作中运行的步骤。 -##### **`runs.steps.run`** +##### `runs.steps.run` **必要** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： @@ -285,37 +285,37 @@ runs: -##### **`runs.steps.shell`** +##### `runs.steps.shell` **必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)列出的任何 shell。 -##### **`runs.steps.name`** +##### `runs.steps.name` **可选** 组合运行步骤的名称。 -##### **`runs.steps.id`** +##### `runs.steps.id` **可选** 步骤的唯一标识符。 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。 -##### **`runs.steps.env`** +##### `runs.steps.env` **可选** 设置环境变量的 `map` 仅用于该步骤。 如果要修改工作流程中存储的环境变量，请在复合运行步骤中使用 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %}。 -##### **`runs.steps.working-directory`** +##### `runs.steps.working-directory` **可选** 指定命令在其中运行的工作目录。 -### 用于 Docker 操作的 **`runs`** +### 用于 Docker 操作的 `runs` **必要** 配置用于 Docker 操作的图像。 @@ -347,13 +347,13 @@ runs: -#### **`runs.using`** +#### `runs.using` **必要** 必须将此值设置为 `'docker'`。 -#### **`pre-entrypoint`** +#### `pre-entrypoint` **可选** 允许您在 `entrypoint` 操作开始之前运行脚本。 例如，您可以使用 `pre-entrypoint:` 运行基本要求设置脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 启动此操作，并在使用同一基本映像的新容器中运行脚本。 这意味着运行时状态与主 `entrypoint` 容器不同，并且必须在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `pre-entrypoint:` 操作始终默认运行，但您可以使用 [`pre-if`](#pre-if) 覆盖该设置。 @@ -376,19 +376,19 @@ runs: -#### **`runs.image`** +#### `runs.image` **必要** 要用作容器来运行操作的 Docker 映像。 值可以是 Docker 基本映像名称、仓库中的本地 `Dockerfile`、Docker Hub 中的公共映像或另一个注册表。 要引用仓库本地的 `Dockerfile`，请使用操作元数据文件的相对路径。 `Docker` 应用程序将执行此文件。 -#### **`runs.env`** +#### `runs.env` **可选** 指定要在容器环境中设置的环境变量的键/值映射。 -#### **`runs.entrypoint`** +#### `runs.entrypoint` **可选** 覆盖 `Dockerfile` 中的 Docker `ENTRYPOINT`，或在未指定时设置它。 当 `Dockerfile` 未指定 `ENTRYPOINT` 或者您想要覆盖 `ENTRYPOINT` 指令时使用 `entrypoint`。 如果您省略 `entrypoint`，您在 Docker `ENTRYPOINT` 指令中指定的命令将执行。 Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPOINT` 文档建议使用 _exec_ 形式的 `ENTRYPOINT` 指令。 @@ -396,7 +396,7 @@ runs: -#### **`post-entrypoint`** +#### `post-entrypoint` **可选** 允许您在 `runs.entrypoint` 操作完成后运行清理脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 来启动此操作。 因为 {% data variables.product.prodname_actions %} 使用同一基本映像在新容器内运行脚本，所以运行时状态与主 `entrypoint` 容器不同。 您可以在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `post-entrypoint:` 操作始终默认运行，但您可以使用 [`post-if`](#post-if) 覆盖该设置。 @@ -415,7 +415,7 @@ runs: -#### **`runs.args`** +#### `runs.args` **可选** 定义 Docker 容器输入的字符串数组。 输入可包含硬编码的字符串。 {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。 @@ -449,7 +449,7 @@ runs: -### **`branding`** +### `branding` 您可以使用颜色和 [Feather](https://feathericons.com/) 图标创建徽章，以个性化和识别操作。 徽章显示在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中的操作名称旁边。 @@ -468,13 +468,13 @@ branding: -#### **`branding.color`** +#### `branding.color` 徽章的背景颜色。 可以是以下之一：`white`、`yellow`、`blue`、`green`、`orange`、`red`、`purple` 或 `gray-dark`。 -#### **`branding.icon`** +#### `branding.icon` 要使用的 [Feather](https://feathericons.com/) 图标的名称。 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 8dd8590b6e..f94d639aed 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 @@ -25,7 +25,11 @@ versions: 现在，在审查拉取请求时，您将能够查看工作流程运行并下载生成的构件。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down-updated.png) +{% else %} ![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png) +{% endif %} 这将允许您在计算机上运行拉取请求中的代码，有助于调试或测试拉取请求。 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 de8b19ee75..5ae46db35c 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-gradle.md @@ -91,7 +91,7 @@ steps: ### 缓存依赖项 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. 运行成功后，您的本地 Gradle 缓存将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程包仓库下载依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 +使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以缓存依赖项以加速工作流程运行。 运行成功后，您的本地 Gradle 缓存将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程包仓库下载依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} ```yaml diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/guides/building-and-testing-java-with-maven.md index 336882b1d1..1bb19a4044 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 @@ -53,7 +53,7 @@ jobs: with: java-version: 1.8 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -85,13 +85,13 @@ steps: with: java-version: 1.8 - name: Run the Maven verify phase - run: mvn -B verify --file pom-ci.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} ### 缓存依赖项 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache your dependencies to speed up your workflow runs. 运行成功后，您的本地 Maven 仓库将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程 Maven 仓库下载依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 +使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以缓存依赖项以加速工作流程运行。 运行成功后，您的本地 Maven 仓库将存储在 GitHub 操作基础架构中。 在未来的工作流程运行中，缓存将会恢复，因此不需要从远程 Maven 仓库下载依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} ```yaml @@ -108,7 +108,7 @@ steps: key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} restore-keys: ${{ runner.os }}-m2 - name: Build with Maven - run: mvn -B package --file pom.xml + run: mvn --batch-mode --update-snapshots verify ``` {% endraw %} @@ -125,7 +125,7 @@ Maven 通常会在 `target` 目录中创建 JAR、EAR 或 WAR 等输出文件。 steps: - uses: actions/checkout@v2 - uses: actions/setup-java@v1 - - run: mvn -B package --file pom.xml + - run: mvn --batch-mode --update-snapshots verify - run: mkdir staging && cp target/*.jar staging - uses: actions/upload-artifact@v2 with: 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 05b2fdecc9..76e8027a87 100644 --- a/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md +++ b/translations/zh-CN/content/actions/guides/building-and-testing-nodejs.md @@ -129,7 +129,7 @@ jobs: {% data variables.product.prodname_dotcom %} 托管的运行器安装了 npm 和 Yarn 依赖项管理器。 在构建和测试代码之前，可以使用 npm 和 Yarn 在工作流程中安装依赖项。 Windows 和 Linux {% data variables.product.prodname_dotcom %} 托管的运行器也安装了 Grunt、Gulp 和 Bower。 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 更多信息请参阅“缓存依赖项以加快工作流程”。 +使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您还可以缓存依赖项以加速工作流程。 更多信息请参阅“缓存依赖项以加快工作流程”。 #### 使用 npm 的示例 @@ -227,7 +227,7 @@ always-auth=true #### 缓存依赖项示例 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache dependencies using a unique key, and restore the dependencies when you run future workflows using the `cache` action. 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 +使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以使用唯一密钥缓存依赖项， 并在使用`缓存`操作运行未来的工作流程时恢复依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”和 [`cache` 操作](https://github.com/marketplace/actions/cache)。 {% raw %} ```yaml 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 9c238651b7..0af814dd33 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 @@ -60,7 +60,11 @@ jobs: * `run: Test-Path resultsfile.log` - 检查仓库的根目录中是否存在名为 `resultsfile.log` 的文件。 * `Should -Be $true` - 使用 Pester 定义预期结果。 如果结果是非预期的，则 {% data variables.product.prodname_actions %} 会将此标记为失败的测试。 例如： + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![失败的 Pester 测试](/assets/images/help/repository/actions-failed-pester-test-updated.png) + {% else %} ![失败的 Pester 测试](/assets/images/help/repository/actions-failed-pester-test.png) + {% endif %} * `Invoke-Pester Unit.Tests.ps1 -Passthru` - 使用 Pester 执行文件 `Unit.Tests.ps1` 中定义的测试。 例如，要执行上述相同的测试， `Unit.Tests.ps1` 将包含以下内容： ``` @@ -91,7 +95,7 @@ jobs: {% endnote %} -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 更多信息请参阅“缓存依赖项以加快工作流程”。 +使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您还可以缓存依赖项以加速工作流程。 更多信息请参阅“缓存依赖项以加快工作流程”。 例如，以下作业将安装 `SqlServer` 和 `PSScriptAnalyzer` 模块： @@ -119,7 +123,7 @@ jobs: #### 缓存依赖项 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. 更多信息请参阅“缓存依赖项以加快工作流程”。 +使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以使用唯一密钥缓存 PowerShell 依赖项， 这样在使用 [`cache`](https://github.com/marketplace/actions/cache) 操作运行未来的工作流程时可以恢复依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”。 PowerShell 根据运行器的操作系统将其依赖项缓存在不同的位置。 例如，以下 Ubuntu 示例中使用的 `path` 位置在 Windows 操作系统中是不同的。 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-python.md b/translations/zh-CN/content/actions/guides/building-and-testing-python.md index 4cb51e7352..c78fb903ff 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 @@ -217,7 +217,7 @@ jobs: {% data variables.product.prodname_dotcom %} 托管的运行器安装了 pip 软件包管理器。 在构建和测试代码之前，您可以使用 pip 从 PyPI 软件包注册表安装依赖项。 例如，下面的 YAML 安装或升级 `pip` 软件包安装程序以及 `setuptools` 和 `wheel` 软件包。 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can also cache dependencies to speed up your workflow. 更多信息请参阅“缓存依赖项以加快工作流程”。 +使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您还可以缓存依赖项以加速工作流程。 更多信息请参阅“缓存依赖项以加快工作流程”。 {% raw %} @@ -265,7 +265,7 @@ steps: #### 缓存依赖项 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache pip dependencies using a unique key, and restore the dependencies when you run future workflows using the [`cache`](https://github.com/marketplace/actions/cache) action. 更多信息请参阅“缓存依赖项以加快工作流程”。 +使用 {% data variables.product.prodname_dotcom %} 托管的运行器时，您可以使用唯一密钥缓存 pip 依赖项， 并在使用[`缓存`](https://github.com/marketplace/actions/cache)操作运行未来的工作流程时恢复依赖项。 更多信息请参阅“缓存依赖项以加快工作流程”。 Pip 根据运行器的操作系统将依赖项缓存在不同的位置。 您需要缓存的路径可能不同于下面的 Ubuntu 示例，具体取决于您使用的操作系统。 更多信息请参阅 [Python 缓存示例](https://github.com/actions/cache/blob/main/examples.md#python---pip)。 diff --git a/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md b/translations/zh-CN/content/actions/guides/building-and-testing-ruby.md index 7a9a51e67b..60267aff97 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 @@ -148,7 +148,7 @@ steps: #### 缓存依赖项 -If you are using {% data variables.product.prodname_dotcom %}-hosted runners, the `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. +如果您使用的是 {% data variables.product.prodname_dotcom %} 托管的运行器， `setup-ruby` 操作提供了在运行之间自动处理 gem 缓存的方法。 要启用缓存，请设置以下内容。 @@ -165,7 +165,7 @@ steps: **无 setup-ruby 的缓存** -For greater control over caching, if you are using {% data variables.product.prodname_dotcom %}-hosted runners, you can use the `actions/cache` Action directly. 更多信息请参阅“缓存依赖项以加快工作流程”。 +为了加强缓存控制，如果您使用的是 {% data variables.product.prodname_dotcom %} 托管的运行器，可以直接使用 `actions/cache` 操作。 更多信息请参阅“缓存依赖项以加快工作流程”。 {% raw %} ```yaml 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 c620377768..d1f30725d3 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 @@ -84,7 +84,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -143,7 +143,7 @@ jobs: with: java-version: 1.8 - name: Publish package - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` @@ -182,7 +182,7 @@ jobs: server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD - name: Publish to the Maven Central Repository - run: mvn -B deploy + run: mvn --batch-mode deploy env: MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }} MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }} @@ -191,7 +191,7 @@ jobs: with: java-version: 1.8 - name: Publish to GitHub Packages - run: mvn -B deploy + run: mvn --batch-mode deploy env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` 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 bb65fffb6e..2909e18a9e 100644 --- a/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md +++ b/translations/zh-CN/content/actions/guides/publishing-nodejs-packages.md @@ -8,8 +8,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md b/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md index 7e5a0986dc..e6e6040685 100644 --- a/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md +++ b/translations/zh-CN/content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md @@ -11,8 +11,6 @@ redirect_from: versions: free-pro-team: '*' enterprise-server: '>=2.22' -authors: - - GitHub --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md b/translations/zh-CN/content/actions/guides/storing-workflow-data-as-artifacts.md index 225976407a..d5e1ddc82b 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 @@ -108,8 +108,6 @@ jobs: path: output/test/code-coverage.html ``` -![工作流程上传构件工作流程运行的图像](/assets/images/help/repository/upload-build-test-artifact.png) - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### 配置自定义构件保留期 @@ -238,7 +236,12 @@ jobs: echo The result is $value ``` +工作流程运行运行将会存档它生成的任何构件。 有关下载存档的构件的更多信息，请参阅“[下载工作流程构件](/actions/managing-workflow-runs/downloading-workflow-artifacts)”。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +![要在作业之间传递数据以执行数学工作流程](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% else %} ![要在作业之间传递数据以执行数学工作流程](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +{% endif %} {% if currentVersion == "free-pro-team@latest" %} 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 57a5fd132b..3f1808fa47 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 @@ -87,7 +87,7 @@ versions: - Windows Server 2016 64 位 - Windows Server 2019 64 位 -#### MacOS +#### macOS - macOS 10.13 (High Sierra) 或更高版本 diff --git a/translations/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md index af2d6dd644..4b717ea2e5 100644 --- a/translations/zh-CN/content/actions/index.md +++ b/translations/zh-CN/content/actions/index.md @@ -41,6 +41,7 @@ changelog: title: 自托管运行器组访问权限更改 date: '2020-10-16' href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/ +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/ @@ -69,18 +70,18 @@ versions:

      代码示例

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

      抱歉，找不到结果

      +

      抱歉，找不到结果

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

      了解如何添加代码示例 {% octicon "arrow-right" %}
      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 21aecae1e7..06a2654ede 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 @@ -204,13 +204,18 @@ _操作_ 是独立命令，它们组合到_步骤_以创建_作业_。 操作是 ### 查看作业的活动 -作业开始运行后，您可以在 {% data variables.product.prodname_dotcom %} 上查看每个步骤的活动。 +作业开始运行后，您可以 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}查看运行进度的可视化图{% endif %}以及查看 {% data variables.product.prodname_dotcom %} 上每个步骤的活动。 {% data reusables.repositories.navigate-to-repo %} 1. 在仓库名称下，单击 **Actions（操作）**。 ![导航到仓库](/assets/images/help/images/learn-github-actions-repository.png) 1. 在左侧边栏中，单击您想要查看的工作流程。 ![工作流程结果的屏幕截图](/assets/images/help/images/learn-github-actions-workflow.png) 1. 在“Workflow runs（工作流程运行）”下，单击您想要查看的运行的名称。 ![工作流程运行的屏幕截图](/assets/images/help/images/learn-github-actions-run.png) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. 在 **Jobs（作业）**下或可视化图中，单击您要查看的作业。 ![选择作业](/assets/images/help/images/overview-actions-result-navigate.png) +{% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. 查看每个步骤的结果。 ![工作流程运行详细信息的屏幕截图](/assets/images/help/images/overview-actions-result-updated-2.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. 单击作业名称以查看每个步骤的结果。 ![工作流程运行详细信息的屏幕截图](/assets/images/help/images/overview-actions-result-updated.png) {% else %} 1. 单击作业名称以查看每个步骤的结果。 ![工作流程运行详细信息的屏幕截图](/assets/images/help/images/overview-actions-result.png) 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 c13b8837be..fd02f04ef2 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-circleci-to-github-actions.md @@ -101,7 +101,7 @@ GitHub Actions -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 更多信息请参阅“缓存依赖项以加快工作流程”。 +{% data variables.product.prodname_actions %} 缓存仅适用于 {% data variables.product.prodname_dotcom %} 托管的运行器。 更多信息请参阅“缓存依赖项以加快工作流程”。 {% data variables.product.prodname_actions %} 没有 CircleCI 的 Docker 层缓存（或 DLC）的等效项。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 456e291e95..51c89c8fa0 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 @@ -346,7 +346,7 @@ jobs: -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 更多信息请参阅“缓存依赖项以加快工作流程”。 +{% data variables.product.prodname_actions %} 缓存仅适用于 {% data variables.product.prodname_dotcom %} 托管的运行器。 更多信息请参阅“缓存依赖项以加快工作流程”。 ### 构件 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 9592224022..16af094413 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 @@ -165,9 +165,9 @@ git: #### 在矩阵中使用环境变量 -Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step. +Travis CI 和 {% data variables.product.prodname_actions %} 可以将自定义环境变量添加到测试矩阵，这可让您在后面的步骤中引用该变量。 -In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %} +在 {% data variables.product.prodname_actions %}中，您可以使用 `include` 键将自定义环境变量添加到矩阵中。 {% data reusables.github-actions.matrix-variable-example %} ### {% data variables.product.prodname_actions %} 中的关键功能 @@ -322,7 +322,7 @@ cache: npm -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. 更多信息请参阅“缓存依赖项以加快工作流程”。 +{% data variables.product.prodname_actions %} 缓存仅适用于 {% data variables.product.prodname_dotcom %} 托管的运行器。 更多信息请参阅“缓存依赖项以加快工作流程”。 ### 常见任务示例 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 e478426546..9539116600 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 @@ -54,6 +54,8 @@ versions: **警告** 提交 SHA 的简短版本不安全，绝不可用于指定操作的 Git 引用。 由于仓库网络的工作方式，任何用户都可以复刻仓库，将精心编写的提交推送到与短 SHA 冲突的仓库。 这会导致该 SHA 上的后续克隆失败，因为它成为不明确的提交。 因此，使用缩短的 SHA 的任何工作流程将立即失败。 {% endwarning %} + + * **审核操作的源代码** 确保操作按照预期处理仓库和密码的内容。 例如，确认密码未发送到非预期主机，或者没有被无意中记录。 @@ -92,10 +94,14 @@ versions: 因此，自托管的运行器几乎[永远不能用于 {% data variables.product.product_name %} 上的公共仓库](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)，因为任何用户都可以打开针对仓库的拉取请求并破坏环境。 同样，在私有仓库上使用自托管运行器时也要小心，因为任何可以复刻仓库并打开 PR 的人（通常是对仓库具有读取权限的人）都能够破坏自托管运行器环境，包括访问密码以及可授予仓库写入权限的特权 `GITHUB_TOKEN` 。 +在组织或企业级别定义自托管运行器时， {% data variables.product.product_name %} 可将多个仓库中的工作流程安排到同一个运行器中。 因此，这些环境的安全危害可能会导致广泛的影响。 为了帮助缩小损害范围，可以通过将自托管运行器组织到单独的组中来创建边界。 更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。 + 您还应考虑自托管运行器机器的环境： - 配置为自托管运行器的计算机上存储哪些敏感信息？ 例如，私有 SSH 密钥、API 访问令牌等。 - 计算机是否可通过网络访问敏感服务？ 例如，Azure 或 AWS 元数据服务。 此环境中的敏感信息量应保持在最低水平，您应该始终注意，任何能够调用工作流程的用户都有权访问此环境。 +某些客户可能会尝试通过实施在每次作业执行后自动销毁自托管运行器的系统来部分降低这些风险。 但是，此方法可能不如预期有效，因为无法保证自托管运行器只运行一个作业。 + ### 审核 {% data variables.product.prodname_actions %} 事件 您可以使用审核日志来监控组织中的管理任务。 审核日志记录操作类型、操作的运行时间以及执行操作的用户帐户。 @@ -130,5 +136,3 @@ versions: | `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` | 组织管理员从组中删除自托管运行器时触发。 | - - diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md index 1f77cb82a6..0c3426a74b 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -17,8 +17,13 @@ versions: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} -{% data reusables.repositories.view-run %} -1. 在工作流程右上角单击 **Cancel workflow（取消工作流程）**。 ![取消检查套件按钮](/assets/images/help/repository/cancel-check-suite.png) +1. 从工作流程运行列表中，单击您要取消的`已排队`或`进行中`运行的名称。 ![工作流程运行的名称](/assets/images/help/repository/in-progress-run.png) +1. 在工作流程右上角单击 **Cancel workflow（取消工作流程）**。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![取消检查套件按钮](/assets/images/help/repository/cancel-check-suite-updated.png) +{% else %} + ![取消检查套件按钮](/assets/images/help/repository/cancel-check-suite.png) +{% endif %} ### {% data variables.product.prodname_dotcom %} 取消工作流程运行所执行的步骤 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 8b37349eb3..f9cd8acb52 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -19,4 +19,9 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. 在**构件**下，单击您想要下载的构件。 ![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png) +1. 在**构件**下，单击您想要下载的构件。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down-updated.png) + {% else %} + ![下载构件下拉菜单](/assets/images/help/repository/artifact-drop-down.png) + {% endif %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/index.md b/translations/zh-CN/content/actions/managing-workflow-runs/index.md index f3f23f9854..97885e3e6a 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/index.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/index.md @@ -18,6 +18,7 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% link_in_list /using-the-visualization-graph %}{% endif %} {% link_in_list /viewing-workflow-run-history %} {% link_in_list /using-workflow-run-logs %} {% link_in_list /manually-running-a-workflow %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md index 58e6c9ea7f..ca1c9f5871 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -16,4 +16,4 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单，并选择 **Re-run all jobs（重新运行所有作业）**。 ![重新运行检查下拉菜单](/assets/images/help/repository/rerun-checks-drop-down.png) +1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单并选择 **Re-run all jobs（重新运行所有作业）**。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index e8331cd503..3bc38564a3 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -26,7 +26,13 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. 在 **Artifacts（构件）**下，单击您要删除的构件旁边的 {% octicon "trashcan" aria-label="The trashcan icon" %}。 ![删除构件下拉菜单](/assets/images/help/repository/actions-delete-artifact.png) +1. 在 **Artifacts（构件）**下，单击 +您要删除的构件旁边的 {% octicon "trashcan" aria-label="The trashcan icon" %}。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![删除构件下拉菜单](/assets/images/help/repository/actions-delete-artifact-updated.png) + {% else %} + ![删除构件下拉菜单](/assets/images/help/repository/actions-delete-artifact.png) + {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} ### 设置构件的保留期 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/using-the-visualization-graph.md b/translations/zh-CN/content/actions/managing-workflow-runs/using-the-visualization-graph.md new file mode 100644 index 0000000000..ed0ee746a5 --- /dev/null +++ b/translations/zh-CN/content/actions/managing-workflow-runs/using-the-visualization-graph.md @@ -0,0 +1,21 @@ +--- +title: 使用可视化图表 +intro: 每个工作流程运行都会生成一个实时图表，说明运行进度。 您可以使用此图表来监控和调试工作流程。 +product: '{% data reusables.gated-features.actions %}' +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.visualization-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} + +1. 图表显示每个工作流程中的作业。 作业名称左侧的图标指示作业的状态。 作业之间的线表示依赖项。 ![工作流程图表](/assets/images/help/images/workflow-graph.png) + +2. 单击作业可查看作业日志。 ![工作流程图表](/assets/images/help/images/workflow-graph-job.png) diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md index 533f006117..7e072af03d 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/using-workflow-run-logs.md @@ -44,7 +44,12 @@ versions: {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. 在日志输出的右上角，在 **Search logs（搜索日志）**搜索框中输入搜索查询。 ![搜索日志的搜索框](/assets/images/help/repository/search-log-box-updated.png) +1. 在日志输出的右上角，在 **Search logs（搜索日志）**搜索框中输入搜索查询。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![搜索日志的搜索框](/assets/images/help/repository/search-log-box-updated-2.png) +{% else %} + ![搜索日志的搜索框](/assets/images/help/repository/search-log-box-updated.png) +{% endif %} {% else %} 1. 要展开想包含在搜索中的每个步骤，请单击该步骤。 ![步骤名称](/assets/images/help/repository/failed-check-step.png) 1. 在日志输出的右上角，在 **Search logs（搜索日志）**搜索框中输入搜索查询。 ![搜索日志的搜索框](/assets/images/help/repository/search-log-box.png) @@ -61,8 +66,12 @@ versions: {% data reusables.repositories.navigate-to-job-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} 1. 在右上角单击 -{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 并选择 **Download log archive（下载日志存档）**。 +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} 并选择 **Download log archive（下载日志存档）**。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![下载日志下拉菜单](/assets/images/help/repository/download-logs-drop-down-updated-2.png) + {% else %} ![下载日志下拉菜单](/assets/images/help/repository/download-logs-drop-down-updated.png) + {% endif %} {% else %} 1. 在右上角单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 并选择 **Download log archive（下载日志存档）**。 @@ -78,8 +87,20 @@ versions: {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. 在右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。 ![烤肉串水平图标](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) -2. 要删除日志文件，单击 **Delete all logs（删除所有日志）**按钮并审查确认提示。 ![删除所有日志](/assets/images/help/repository/delete-all-logs-updated.png) 删除日志后，**Delete all logs（删除所有日志）**按钮将被删除，以表明工作流程运行中未剩下任何日志文件。 +1. 在右上角单击 +{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![烤肉串水平图标](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) + {% else %} + ![烤肉串水平图标](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated.png) + {% endif %} +2. 要删除日志文件，单击 **Delete all logs（删除所有日志）**按钮并审查确认提示。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![删除所有日志](/assets/images/help/repository/delete-all-logs-updated-2.png) + {% else %} + ![删除所有日志](/assets/images/help/repository/delete-all-logs-updated.png) + {% endif %} +删除日志后，**Delete all logs（删除所有日志）** 按钮将会移除，以表示在工作流程运行中没有日志文件。 {% else %} 1. 在右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。 ![烤肉串水平图标](/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png) 2. 要删除日志文件，单击 **Delete all logs（删除所有日志）**按钮并审查确认提示。 ![Delete all logs](/assets/images/help/repository/delete-all-logs.png) 删除日志后，**Delete all logs（删除所有日志）**按钮将被删除，以表明工作流程运行中未剩下任何日志文件。 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/viewing-job-execution-time.md b/translations/zh-CN/content/actions/managing-workflow-runs/viewing-job-execution-time.md index fabc3a7b50..c6280faab1 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/viewing-job-execution-time.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/viewing-job-execution-time.md @@ -15,7 +15,7 @@ versions: {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -1. 在作业摘要下，您可以查看作业的执行时间。 要查看可计费的作业执行时间，单击 **Run and billable time details（运行和可计费时间详细信息）**。 ![运行和可计费时间详细信息链接](/assets/images/help/repository/view-run-billable-time.png) +1. 在作业摘要下，您可以查看作业的执行时间。 要查看有关计费作业执行时间的详细信息，请单击 **Billable time（计费时间）**下的时间。 ![运行和可计费时间详细信息链接](/assets/images/help/repository/view-run-billable-time.png) {% note %} diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md index adcc9aa67d..d482db8316 100644 --- a/translations/zh-CN/content/actions/quickstart.md +++ b/translations/zh-CN/content/actions/quickstart.md @@ -59,7 +59,11 @@ versions: {% 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. 在 **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 %} ### 更多入门工作流程 @@ -101,7 +105,7 @@ versions: # When the event is triggered, GitHub Actions will run the jobs indicated jobs: say_hello: - # Uses a ubuntu-lates runner to complete the requested steps + # Uses a ubuntu-latest runner to complete the requested steps runs-on: ubuntu-latest steps: - run: | diff --git a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md index d7251d04f1..f94651bec6 100644 --- a/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/context-and-expression-syntax-for-github-actions.md @@ -75,7 +75,7 @@ env: - 以 `a-Z` 或 `_` 开头。 - 后跟 `a-Z` `0-9` `-` 或 `_`。 -#### **`github` 上下文** +#### `github` 上下文 `github` 上下文包含有关工作流程运行以及触发运行的事件相关信息。 您可以读取环境变量中的大多数 `github` 上下文数据。 有关环境变量的更多信息，请参阅“[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”。 @@ -103,7 +103,7 @@ env: | `github.workflow` | `字符串` | 工作流程的名称。 如果工作流程文件未指定 `name`，此属性的值将是仓库中工作流程文件的完整路径。 | | `github.workspace` | `字符串` | 使用 [`checkout`](https://github.com/actions/checkout) 操作时步骤的默认工作目录和仓库的默认位置。 | -#### **`env` 上下文** +#### `env` 上下文 `env` 上下文包含已在工作流程、作业或步骤中设置的环境变量。 有关在工作流程中设置环境变量的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)”。 @@ -117,7 +117,7 @@ env: | `env.` | `字符串` | 特定环境变量的值。 | -#### **`job` 上下文** +#### `job` 上下文 `job` 上下文包含当前正在运行的作业相关信息。 @@ -133,7 +133,7 @@ env: | `job.services..ports` | `对象` | 服务容器显露的端口。 | | `job.status` | `字符串` | 作业的当前状态。 可能的值包括 `success`、`failure` 或 `cancelled`。 | -#### **`steps` 上下文** +#### `steps` 上下文 `steps` 上下文包含当前作业中已经运行的步骤相关信息。 @@ -145,7 +145,7 @@ env: | `steps..outcome` | `字符串` | 在 [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) 应用之前完成的步骤的结果。 可能的值包括 `success`、`failure`、`cancelled` 或 `skipped`。 当 `continue-on-error` 步骤失败时，`outcome` 为 `failure`，但最终的 `conclusion` 为 `success`。 | | `steps..outputs.` | `字符串` | 特定输出的值。 | -#### **`runner` 上下文** +#### `runner` 上下文 `runner` 上下文包含正在执行当前作业的运行器相关信息。 @@ -155,7 +155,7 @@ env: | `runner.temp` | `字符串` | 运行器临时目录的路径。 此目录保证在每个作业开始时为空，即使在自托管的运行器上也是如此。 | | `runner.tool_cache` | `字符串` | 包含 {% data variables.product.prodname_dotcom %} 托管运行器一些预安装工具的目录路径。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 托管运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。 | -#### **`needs` 上下文** +#### `needs` 上下文 `needs` 上下文包含定义为当前作业依赖项的所有作业的输出。 有关定义作业依赖项的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)”。 diff --git a/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md index be7f0a266b..4c6f90dc67 100644 --- a/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md +++ b/translations/zh-CN/content/actions/reference/events-that-trigger-workflows.md @@ -137,9 +137,9 @@ jobs: #### `repository_dispatch` -| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------- | ---- | --------------------- | ------------ | -| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | `GITHUB_REF` 分支上的最新提交 | 收到了分发的分支 | +| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------------------------------------- | ---- | ------------ | ------------ | +| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | 默认分支上的最新提交 | 默认分支 | {% data reusables.github-actions.branch-requirement %} @@ -699,6 +699,8 @@ on: {% data reusables.webhooks.workflow_run_desc %} +{% data reusables.github-actions.branch-requirement %} + | Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | | -------------------------------------------------------- | ----- | ------------ | ------------ | | [`workflow_run`](/webhooks/event-payloads/#workflow_run) | - n/a | 默认分支上的最新提交 | 默认分支 | diff --git a/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md b/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md index 03a010a325..a6b25c5618 100644 --- a/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/reference/specifications-for-github-hosted-runners.md @@ -63,8 +63,8 @@ Windows 虚拟机配置为以禁用了用户帐户控制 (UAC) 的管理员身 * [Ubuntu 16.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1604-README.md) * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) * [Windows Server 2016](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2016-Readme.md) -* [MacOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) -* [MacOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) +* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [macOS 11.0](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11.0-Readme.md) {% data reusables.github-actions.ubuntu-runner-preview %} {% data reusables.github-actions.macos-runner-preview %} diff --git a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md index c8730aedf7..23eb826a1a 100644 --- a/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/reference/workflow-syntax-for-github-actions.md @@ -21,17 +21,17 @@ versions: 必须将工作流程文件存储在仓库的 `.github/workflows` 目录中。 -### **`name`** +### `name` 工作流程的名称。 {% data variables.product.prodname_dotcom %} 在仓库的操作页面上显示工作流程的名称。 如果省略 `name`，{% data variables.product.prodname_dotcom %} 将其设置为相对于仓库根目录的工作流程文件路径。 -### **`on`** +### `on` **必要** 触发工作流程的 {% data variables.product.prodname_dotcom %} 事件的名称。 您可以提供单一事件 `string`、事件的 `array`、事件 `types` 的 `array` 或事件配置 `map`，以安排工作流程的运行，或将工作流程的执行限于特定文件、标记或分支更改。 有关可用事件的列表，请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows)”。 {% data reusables.github-actions.actions-on-examples %} -### **`on..types`** +### `on..types` 选择将触发工作流程运行的活动类型。 大多数 GitHub 事件由多种活动触发。 例如，发布资源的事件在发行版 `published`、`unpublished`、`created`、`edited`、`deleted` 或 `prereleased` 时触发。 通过 `types` 关键词可缩小触发工作流程运行的活动类型的范围。 如果只有一种活动类型可触发 web 挂钩事件，就没有必要使用 `types` 关键词。 @@ -45,7 +45,7 @@ on: types: [published, created, edited] ``` -### **`on..`** +### `on..` 使用 `push` 和 `pull_request` 事件时，您可以将工作流配置为在特定分支或标记上运行。 对于 `pull_request` 事件，只评估基础上的分支和标签。 如果只定义 `tags` 或只定义 `branches`，则影响未定义 Git ref 的事件不会触发工作流程运行。 @@ -112,7 +112,7 @@ on: - '!releases/**-alpha' ``` -### **`on..paths`** +### `on..paths` 使用 `push` 和 `pull_request` 事件时，您可以将工作流程配置为在至少一个文件不匹配 `paths-ignore` 或至少一个修改的文件匹配配置的 `paths` 时运行。 路径过滤器不评估是否推送到标签。 @@ -179,13 +179,13 @@ on: 更多信息请参阅“[关于比较拉取请求中的分支](/articles/about-comparing-branches-in-pull-requests)”。 -### **`on.schedule`** +### `on.schedule` {% data reusables.repositories.actions-scheduled-workflow-example %} 有关计划任务语法的更多信息请参阅“[触发工作流程的事件](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)”。 -### **`env`** +### `env` 环境变量的 `map` 可用于工作流程中的所有作业和步骤。 您还可以设置仅适用于作业或步骤的环境变量。 更多信息请参阅 [`jobs..env`](#jobsjob_idenv) and [`jobs..steps.env`](#jobsjob_idstepsenv)。 @@ -198,13 +198,13 @@ env: SERVER: production ``` -### **`defaults`** +### `defaults` 将应用到工作流程中所有作业的默认设置的 `map`。 您也可以设置只可用于作业的默认设置。 更多信息请参阅 [`jobs..defaults`](#jobsjob_iddefaults)。 {% data reusables.github-actions.defaults-override %} -### **`defaults.run`** +### `defaults.run` 您可以为工作流程中的所有 [`run`](#jobsjob_idstepsrun) 步骤提供默认的 `shell` 和 `working-directory` 选项。 您也可以设置只可用于作业的 `run` 默认设置。 更多信息请参阅 [`jobs..defaults.run`](#jobsjob_iddefaultsrun)。 您不能在此关键词中使用上下文或表达式。 @@ -219,7 +219,7 @@ defaults: working-directory: scripts ``` -### **`jobs`** +### `jobs` 工作流程运行包括一项或多项作业。 作业默认是并行运行。 要按顺序运行作业，您可以使用 `needs` 关键词在其他作业上定义依赖项。 @@ -229,7 +229,7 @@ defaults: 如果需要查找在工作流程运行中运行的作业的唯一标识符，可以使用 {% data variables.product.prodname_dotcom %} ApI。 更多信息请参阅“[工作流程作业](/rest/reference/actions#workflow-jobs)”。 -### **`jobs.`** +### `jobs.` 每项作业必须关联一个 ID。 键值 `job_id` 是一个字符串，其值是作业配置数据的映像。 必须将 `` 替换为 `jobs` 对象唯一的字符串。 `` 必须以字母或 `_` 开头，并且只能包含字母数字字符、`-` 或 `_`。 @@ -243,15 +243,15 @@ jobs: name: My second job ``` -### **`jobs..name`** +### `jobs..name` 作业显示在 {% data variables.product.prodname_dotcom %} 上的名称。 -### **`jobs..needs`** +### `jobs..needs` -识别在此作业运行之前必须成功完成的任何作业。 它可以是一个字符串，也可以是字符串数组。 如果某个作业失败，则所有需要它的作业都会被跳过，除非这些作业使用让该作业继续的条件语句。 +识别在此作业运行之前必须成功完成的任何作业。 它可以是一个字符串，也可以是字符串数组。 If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. -#### 示例 +#### Example requiring dependent jobs to be successful ```yaml jobs: @@ -270,7 +270,21 @@ jobs: 2. `job2` 3. `job3` -### **`jobs..runs-on`** +#### Example not requiring dependent jobs to be successful + +```yaml +jobs: + job1: + job2: + needs: job1 + job3: + if: always() + 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)." + +### `jobs..runs-on` **必需**运行作业的机器类型。 机器可以是 {% data variables.product.prodname_dotcom %} 托管的运行器或自托管的运行器。 @@ -286,7 +300,7 @@ jobs: {% data reusables.github-actions.ubuntu-runner-preview %} -##### **示例** +##### 示例 ```yaml runs-on: ubuntu-latest @@ -298,7 +312,7 @@ runs-on: ubuntu-latest {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -##### **示例** +##### 示例 ```yaml runs-on: [self-hosted, linux] @@ -306,7 +320,7 @@ runs-on: [self-hosted, linux] 更多信息请参阅“[关于自托管的运行器](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)”和“[在工作流程中使用自托管的运行器](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)”。 -### **`jobs..outputs`** +### `jobs..outputs` 作业的输出 `map`。 作业输出可用于所有依赖此作业的下游作业。 有关定义作业依赖项的更多信息，请参阅 [`jobs..needs`](#jobsjob_idneeds)。 @@ -314,7 +328,7 @@ runs-on: [self-hosted, linux] 要在依赖的作业中使用作业输出, 您可以使用 `needs` 上下文。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)”。 -#### **示例** +#### 示例 {% raw %} ```yaml @@ -338,13 +352,13 @@ jobs: ``` {% endraw %} -### **`jobs..env`** +### `jobs..env` 环境变量的 `map` 可用于作业中的所有步骤。 您也可以设置整个工作流程或单个步骤的环境变量。 更多信息请参阅 [`env`](#env) 和 [`jobs..steps.env`](#jobsjob_idstepsenv)。 {% data reusables.repositories.actions-env-var-note %} -#### **示例** +#### 示例 ```yaml jobs: @@ -353,13 +367,13 @@ jobs: FIRST_NAME: Mona ``` -### **`jobs..defaults`** +### `jobs..defaults` 将应用到作业中所有步骤的默认设置的 `map`。 您也可以设置整个工作流程的默认设置。 更多信息请参阅 [`defaults`](#defaults)。 {% data reusables.github-actions.defaults-override %} -### **`jobs..defaults.run`** +### `jobs..defaults.run` 为作业中的所有 `run` 步骤提供默认的 `shell` 和 `working-directory`。 此部分不允许上下文和表达式。 @@ -379,13 +393,13 @@ jobs: working-directory: scripts ``` -### **`jobs..if`** +### `jobs..if` 您可以使用 `if` 条件阻止作业在条件得到满足之前运行。 您可以使用任何支持上下文和表达式来创建条件。 {% data reusables.github-actions.expression-syntax-if %} 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。 -### **`jobs..steps`** +### `jobs..steps` 作业包含一系列任务，称为 `steps`。 步骤可以运行命令、运行设置任务，或者运行您的仓库、公共仓库中的操作或 Docker 注册表中发布的操作。 并非所有步骤都会运行操作，但所有操作都会作为步骤运行。 每个步骤在运行器环境中以其自己的进程运行，且可以访问工作区和文件系统。 因为步骤以自己的进程运行，所以步骤之间不会保留环境变量的更改。 {% data variables.product.prodname_dotcom %} 提供内置的步骤来设置和完成作业。 @@ -415,17 +429,17 @@ jobs: ``` {% endraw %} -#### **`jobs..steps.id`** +### `jobs..steps.id` 步骤的唯一标识符。 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。 -#### **`jobs..steps.if`** +### `jobs..steps.if` 您可以使用 `if` 条件阻止步骤在条件得到满足之前运行。 您可以使用任何支持上下文和表达式来创建条件。 {% data reusables.github-actions.expression-syntax-if %} 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions)”。 -##### 使用上下文的示例 +#### 使用上下文的示例 此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。 @@ -436,7 +450,7 @@ steps: run: echo This event is a pull request that had an assignee removed. ``` -##### 使用状态检查功能的示例 +#### 使用状态检查功能的示例 `my backup step` 仅在作业的上一步失败时运行。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的上下文和表达式语法](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)”。 @@ -449,11 +463,11 @@ steps: uses: actions/heroku@1.0.0 ``` -#### **`jobs..steps.name`** +### `jobs..steps.name` 步骤显示在 {% data variables.product.prodname_dotcom %} 上的名称。 -#### **`jobs..steps.uses`** +### `jobs..steps.uses` 选择要作为作业中步骤的一部分运行的操作。 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。 @@ -466,7 +480,7 @@ steps: 操作为 JavaScript 文件或 Docker 容器。 如果您使用的操作是 Docker 容器，则必须在 Linux 环境中运行作业。 更多详情请参阅 [`runs-on`](#jobsjob_idruns-on)。 -##### 使用版本化操作的示例 +#### 使用版本化操作的示例 ```yaml steps: @@ -480,7 +494,7 @@ steps: - uses: actions/setup-node@main ``` -##### 使用公共操作的示例 +#### 使用公共操作的示例 `{owner}/{repo}@{ref}` @@ -498,7 +512,7 @@ jobs: uses: actions/aws@v2.0.1 ``` -##### 在子目录中使用公共操作的示例 +#### 在子目录中使用公共操作的示例 `{owner}/{repo}/{path}@{ref}` @@ -512,7 +526,7 @@ jobs: uses: actions/aws/ec2@main ``` -##### 使用工作流程所在仓库中操作的示例 +#### 使用工作流程所在仓库中操作的示例 `./path/to/dir` @@ -528,7 +542,7 @@ jobs: uses: ./.github/actions/my-action ``` -##### 使用 Docker 中枢操作的示例 +#### 使用 Docker 中枢操作的示例 `docker://{image}:{tag}` @@ -542,7 +556,7 @@ jobs: uses: docker://alpine:3.8 ``` -##### 使用 Docker 公共注册表操作的示例 +#### 使用 Docker 公共注册表操作的示例 `docker://{host}/{image}:{tag}` @@ -556,7 +570,7 @@ jobs: uses: docker://gcr.io/cloud-builders/gradle ``` -#### **`jobs..steps.run`** +### `jobs..steps.run` 使用操作系统 shell 运行命令行程序。 如果不提供 `name`，步骤名称将默认为 `run` 命令中指定的文本。 @@ -588,7 +602,7 @@ jobs: working-directory: ./temp ``` -##### 使用指定 shell +#### 使用指定 shell 您可以使用 `shell` 关键词覆盖运行器操作系统中默认的 shell 设置。 您可以使用内置的 `shell` 关键词，也可以自定义 shell 选项集。 @@ -601,7 +615,7 @@ jobs: | Windows | `cmd` | {% data variables.product.prodname_dotcom %} 将扩展名 `.cmd` 附加到您的脚本名称并替换 `{0}`。 | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | | Windows | `powershell` | 这是 Windows 上使用的默认 shell。 Desktop PowerShell。 {% data variables.product.prodname_dotcom %} 将扩展名 `.ps1` 附加到您的脚本名称。 | `powershell -command ". '{0}'"`. | -##### 使用 bash 运行脚本的示例 +#### 使用 bash 运行脚本的示例 ```yaml steps: @@ -610,7 +624,7 @@ steps: shell: bash ``` -##### 使用 Windows `cmd` 运行脚本的示例 +#### 使用 Windows `cmd` 运行脚本的示例 ```yaml steps: @@ -619,7 +633,7 @@ steps: shell: cmd ``` -##### 使用 PowerShell Core 运行脚本的示例 +#### 使用 PowerShell Core 运行脚本的示例 ```yaml steps: @@ -628,7 +642,7 @@ steps: shell: pwsh ``` -##### 运行 python 脚本的示例 +#### 运行 python 脚本的示例 ```yaml steps: @@ -639,11 +653,11 @@ steps: shell: python ``` -##### 自定义 shell +#### 自定义 shell 您可以使用 `command […options] {0} [..more_options]` 将 `shell` 值设置为模板字符串。 {% data variables.product.prodname_dotcom %} 将字符串的第一个用空格分隔的词解释为命令，并在 `{0}` 处插入临时脚本的文件名。 -##### 退出代码和错误操作首选项 +#### 退出代码和错误操作首选项 至于内置的 shell 关键词，我们提供由 {% data variables.product.prodname_dotcom %} 托管运行程序执行的以下默认值。 在运行 shell 脚本时，您应该使用这些指南。 @@ -661,11 +675,11 @@ steps: - 除了编写脚本来检查每个错误代码并相应地响应之外，似乎没有办法完全选择快速失败行为。 由于我们默认不能实际提供该行为，因此您需要将此行为写入脚本。 - `cmd.exe` 在退出时带有其执行的最后一个程序的错误等级，并且会将错误代码返回到运行程序。 此行为在内部与上一个 `sh` 和 `pwsh` 默认行为一致，是 `cmd.exe` 的默认值，所以此行为保持不变。 -#### **`jobs..steps.with`** +### `jobs..steps.with` 输入参数的 `map` 由操作定义。 每个输入参数都是一个键/值对。 输入参数被设置为环境变量。 该变量的前缀为 `INPUT_`，并转换为大写。 -##### 示例 +#### 示例 定义 `hello_world` 操作所定义的三个输入参数（`first_name`、`middle_name` 和 `last_name`）。 这些输入变量将被 `hello-world` 操作作为 `INPUT_FIRST_NAME`、`INPUT_MIDDLE_NAME` 和 `INPUT_LAST_NAME` 环境变量使用。 @@ -681,11 +695,11 @@ jobs: last_name: Octocat ``` -#### **`jobs..steps.with.args`** +### `jobs..steps.with.args` `string` 定义 Docker 容器的输入。 {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。 此参数不支持 `array of strings`。 -##### 示例 +#### 示例 {% raw %} ```yaml @@ -704,11 +718,11 @@ steps: 1. 使用默认值，允许不指定任何 `args` 即可使用操作。 1. 如果操作显示 `--help` 标记或类似项，请将其用作默认值，以便操作自行记录。 -#### **`jobs..steps.with.entrypoint`** +### `jobs..steps.with.entrypoint` 覆盖 `Dockerfile` 中的 Docker `ENTRYPOINT`，或在未指定时设置它。 与包含 shell 和 exec 表单的 Docker `ENTRYPOINT` 指令不同，`entrypoint` 关键词只接受定义要运行的可执行文件的单个字符串。 -##### 示例 +#### 示例 ```yaml steps: @@ -720,7 +734,7 @@ steps: `entrypoint` 关键词旨在用于 Docker 容器操作，但您也可以将其用于未定义任何输入的 JavaScript 操作。 -#### **`jobs..steps.env`** +### `jobs..steps.env` 设置供步骤用于运行器环境的环境变量。 您也可以设置整个工作流程或某个作业的环境变量。 更多信息请参阅 [`env`](#env) 和 [`jobs..env`](#jobsjob_idenv)。 @@ -728,7 +742,7 @@ steps: 公共操作可在自述文件中指定预期的环境变量。 如果要在环境变量中设置密码，必须使用 `secrets` 上下文进行设置。 更多信息请参阅“[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”和“[{% data variables.product.prodname_actions %} 的上下文和表达式](/actions/reference/context-and-expression-syntax-for-github-actions)”。 -##### 示例 +#### 示例 {% raw %} ```yaml @@ -741,23 +755,23 @@ steps: ``` {% endraw %} -#### **`jobs..steps.continue-on-error`** +### `jobs..steps.continue-on-error` 防止步骤失败时作业也会失败。 设置为 `true` 以允许在此步骤失败时作业能够通过。 -#### **`jobs..steps.timeout-minutes`** +### `jobs..steps.timeout-minutes` 终止进程之前运行该步骤的最大分钟数。 -### **`jobs..timeout-minutes`** +### `jobs..timeout-minutes` 在 {% data variables.product.prodname_dotcom %} 自动取消运行之前可让作业运行的最大分钟数。 默认值：360 -### **`jobs..strategy`** +### `jobs..strategy` 策略创建作业的构建矩阵。 您可以定义要在其中运行每项作业的环境的不同变种。 -#### **`jobs..strategy.matrix`** +### `jobs..strategy.matrix` 您可以定义不同作业配置的矩阵。 矩阵允许您通过在单个作业定义中执行变量替换来创建多个作业。 例如，可以使用矩阵为多个受支持的编程语言、操作系统或工具版本创建作业。 矩阵重新使用作业的配置，并为您配置的每个矩阵创建作业。 @@ -767,7 +781,7 @@ steps: 定义 `matrix` 事项的顺序。 定义的第一个选项将是工作流程中运行的第一个作业。 -##### 使用 Node.js 多个版本运行的示例 +#### 使用 Node.js 多个版本运行的示例 您可以提供配置选项阵列来指定矩阵。 例如，如果运行器支持 Node.js 版本 6、8 和 10，则您可以在 `matrix` 中指定这些版本的阵列。 @@ -789,7 +803,7 @@ steps: `setup-node` 操作是在使用 {% data variables.product.prodname_dotcom %} 托管的运行器时建议用于配置 Node.js 版本的方式。 更多信息请参阅 [`setup-node`](https://github.com/actions/setup-node) 操作。 -##### 使用多个操作系统的示例 +#### 使用多个操作系统的示例 您可以创建矩阵以在多个运行器操作系统上运行工作流程。 您也可以指定多个矩阵配置。 此示例创建包含 6 个作业的矩阵： @@ -814,7 +828,7 @@ steps: 要查找 {% data variables.product.prodname_dotcom %} 托管的运行器支持的配置选项，请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的虚拟环境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)”。 -##### 在组合中包含附加值的示例 +#### 在组合中包含附加值的示例 您可以将额外的配置选项添加到已经存在的构建矩阵作业中。 例如，如果要在作业使用 `windows-latest` 和 `node` 的版本 4 运行时使用 `npm` 的特定版本，您可以使用 `include` 指定该附加选项。 @@ -834,7 +848,7 @@ strategy: ``` {% endraw %} -##### 包括新组合的示例 +#### 包括新组合的示例 您可以使用 `include` 将新作业添加到构建矩阵中。 任何不匹配包含配置都会添加到矩阵中。 例如，如果您想要使用 `node` 版本 12 在多个操作系统上构建，但在 Ubuntu 上需要一个使用节点版本 13 的额外实验性作业，则可使用 `include` 指定该额外作业。 @@ -852,7 +866,7 @@ strategy: ``` {% endraw %} -##### 从矩阵中排除配置的示例 +#### 从矩阵中排除配置的示例 您可以使用 `exclude` 选项删除构建矩阵中定义的特定配置。 使用 `exclude` 删除由构建矩阵定义的作业。 作业数量是您提供的数组中所包括的操作系统 (`os`) 数量减去所有减项 (`exclude`) 后的叉积。 @@ -878,15 +892,15 @@ strategy: ##### 在矩阵中使用环境变量 -You can add custom environment variables for each test combination by using the `include` key. 然后，您可以在后面的步骤中引用自定义环境变量。 +您可以使用 `include` 键为每个测试组合添加自定义环境变量。 然后，您可以在后面的步骤中引用自定义环境变量。 {% data reusables.github-actions.matrix-variable-example %} -### **`jobs..strategy.fail-fast`** +### `jobs..strategy.fail-fast` 设置为 `true` 时，如果任何 `matrix` 作业失败，{% data variables.product.prodname_dotcom %} 将取消所有进行中的作业。 默认值：`true` -### **`jobs..strategy.max-parallel`** +### `jobs..strategy.max-parallel` 使用 `matrix` 作业策略时可同时运行的最大作业数。 默认情况下，{% data variables.product.prodname_dotcom %} 将最大化并发运行的作业数量，具体取决于 {% data variables.product.prodname_dotcom %} 托管虚拟机上可用的运行程序。 @@ -895,7 +909,7 @@ strategy: max-parallel: 2 ``` -### **`jobs..continue-on-error`** +### `jobs..continue-on-error` 防止工作流程运行在作业失败时失败。 设置为 `true` 以允许工作流程运行在此作业失败时通过。 @@ -920,7 +934,7 @@ strategy: ``` {% endraw %} -### **`jobs..container`** +### `jobs..container` 用于运行作业中尚未指定容器的任何步骤的容器。 如有步骤同时使用脚本和容器操作，则容器操作将运行为同一网络上使用相同卷挂载的同级容器。 @@ -950,16 +964,17 @@ jobs: container: node:10.16-jessie ``` -#### **`jobs..container.image`** +### `jobs..container.image` 要用作运行操作的容器的 Docker 图像。 值可以是 Docker Hub 映像名称或{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}公共{% endif %}注册表名称。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..container.credentials`** + +### `jobs..container.credentials` {% data reusables.actions.registry-credentials %} -##### 示例 +#### 示例 {% raw %} ```yaml @@ -972,15 +987,15 @@ container: {% endraw %} {% endif %} -#### **`jobs..container.env`** +### `jobs..container.env` 设置容器中环境变量的 `map`。 -#### **`jobs..container.ports`** +### `jobs..container.ports` 设置要在容器上显示的端口 `array`。 -#### **`jobs..container.volumes`** +### `jobs..container.volumes` 设置要使用的容器卷的 `array`。 您可以使用卷分享作业中服务或其他步骤之间的数据。 可以指定命名的 Docker 卷、匿名的 Docker 卷或主机上的绑定挂载。 @@ -990,7 +1005,7 @@ container: `` 是主机上的卷名称或绝对路径，`` 是容器中的绝对路径。 -##### 示例 +#### 示例 ```yaml volumes: @@ -999,11 +1014,11 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..container.options`** +### `jobs..container.options` 附加 Docker 容器资源选项。 有关选项列表，请参阅“[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)”。 -### **`jobs..services`** +### `jobs..services` {% data reusables.github-actions.docker-container-os-support %} @@ -1033,16 +1048,17 @@ services: - 6379/tcp ``` -#### **`jobs..services..image`** +### `jobs..services..image` 要用作运行操作的服务容器的 Docker 图像。 值可以是 Docker Hub 映像名称或{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}公共{% endif %}注册表名称。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -#### **`jobs..services..credentials`** + +### `jobs..services..credentials` {% data reusables.actions.registry-credentials %} -##### 示例 +#### 示例 {% raw %} ```yaml @@ -1061,15 +1077,15 @@ services: {% endraw %} {% endif %} -#### **`jobs..services..env`** +### `jobs..services..env` 在服务容器中设置环境变量的 `map`。 -#### **`jobs..services..ports`** +### `jobs..services..ports` 设置要在服务容器上显示的端口 `array`。 -#### **`jobs..services..volumes`** +### `jobs..services..volumes` 设置要使用的服务容器卷的 `array`。 您可以使用卷分享作业中服务或其他步骤之间的数据。 可以指定命名的 Docker 卷、匿名的 Docker 卷或主机上的绑定挂载。 @@ -1079,7 +1095,7 @@ services: `` 是主机上的卷名称或绝对路径，`` 是容器中的绝对路径。 -##### 示例 +#### 示例 ```yaml volumes: @@ -1088,7 +1104,7 @@ volumes: - /source/directory:/destination/directory ``` -#### **`jobs..services..options`** +### `jobs..services..options` 附加 Docker 容器资源选项。 有关选项列表，请参阅“[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)”。 diff --git a/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md b/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md index 6959f20c16..2734f09e1f 100644 --- a/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md +++ b/translations/zh-CN/content/admin/authentication/changing-authentication-methods.md @@ -10,7 +10,7 @@ versions: 在您更改身份验证方法时，{% data variables.product.product_location %} 上的用户帐户将保留，只要他们的用户名没有发生变化，用户就可以继续登录原来的帐户。 -如果新的身份验证方法更改了用户名，将创建新帐户。 As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). +如果新的身份验证方法更改了用户名，将创建新帐户。 作为管理员，您可以通过站点管理员设置或使用[用户管理 API](/rest/reference/enterprise-admin#update-the-username-for-a-user)重命名用户。 您应当考虑的其他问题包括： diff --git a/translations/zh-CN/content/admin/configuration/index.md b/translations/zh-CN/content/admin/configuration/index.md index 91bed98341..7e2e815484 100644 --- a/translations/zh-CN/content/admin/configuration/index.md +++ b/translations/zh-CN/content/admin/configuration/index.md @@ -31,9 +31,7 @@ versions: {% link_in_list /enabling-private-mode %} {% link_in_list /configuring-email-for-notifications %} {% link_in_list /configuring-rate-limits %} - {% link_in_list /configuring-applications %} - {% link_in_list /troubleshooting-ssl-errors %} {% link_in_list /configuring-time-synchronization %} {% link_in_list /command-line-utilities %} @@ -54,11 +52,7 @@ versions: {% link_in_list /connecting-github-enterprise-server-to-github-enterprise-cloud %} {% link_in_list /enabling-unified-search-between-github-enterprise-server-and-githubcom %} {% link_in_list /enabling-unified-contributions-between-github-enterprise-server-and-githubcom %} - {% link_in_list /enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server %} {% link_in_list /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud %} - - {% topic_link_in_list /configuring-advanced-security-features %} {% link_in_list /configuring-code-scanning-for-your-appliance %} - diff --git a/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md b/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md index 498c702d84..a5f139f936 100644 --- a/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/zh-CN/content/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance.md @@ -37,7 +37,7 @@ versions: ``` - 在新的主设备上，使用 `ghe-repl-teardown` 删除 UUID。 请将 *`UUID`* 替换为您在上一步中检索到的 UUID。 ```shell - $ ghe-repl-teardown -u UUNID + $ ghe-repl-teardown -u UUID ``` ### 延伸阅读 diff --git a/translations/zh-CN/content/admin/index.md b/translations/zh-CN/content/admin/index.md index d8f150d6b8..ec9bc6ac85 100644 --- a/translations/zh-CN/content/admin/index.md +++ b/translations/zh-CN/content/admin/index.md @@ -28,3 +28,5 @@ versions: {% link_with_intro /packages %} {% link_with_intro /enterprise-support %} + +{% link_with_intro /release-notes %} 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 02c92ad31d..26731d2fac 100644 --- a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md +++ b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md @@ -15,7 +15,7 @@ An enterprise account allows you to manage multiple organizations{% if enterpris - 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) +- 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 reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." diff --git a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-minio-storage.md b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-minio-storage.md index a14a0b63f0..2b9405a329 100644 --- a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-minio-storage.md +++ b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-minio-storage.md @@ -11,29 +11,29 @@ versions: MinIO 在企业上提供对象存储并支持 S3 API 和 {% data variables.product.prodname_registry %}。 -This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/). +此快速入门将演示如何使用 Docker 设置 MinIO 以与 {% data variables.product.prodname_registry %} 使用，但除了 Docker 之外，您还有其他用于管理 MinIO 的选项。 有关 MinIO 的更多信息，请参阅官方的 [MinIO 文档](https://docs.min.io/)。 -### 1. Choose a MinIO mode for your needs +### 1. 根据您的需求选择 MinIO 模式 -| MinIO mode | Optimized for | Storage infrastructure required | -| ----------------------------------------------- | ------------------------------ | ------------------------------------ | -| Standalone MinIO (on a single host) | Fast setup | 不适用 | -| MinIO as a NAS gateway | NAS (Network-attached storage) | NAS devices | -| Clustered MinIO (also called Distributed MinIO) | Data security | Storage servers running in a cluster | +| MinIO 模式 | 针对以下平台优化 | 需要存储基础架构 | +| ----------------------- | ----------- | ------------ | +| 独立 MinIO（在单个主机上） | 快速设置 | 不适用 | +| MinIO 作为 NAS 网关 | NAS（网络连接存储） | NAS 设备 | +| 群集式 MinIO（也称为分布式 MinIO） | 数据安全 | 在群集中运行的存储服务器 | -For more information about your options, see the official [MinIO docs](https://docs.min.io/). +有关您的选项的更多信息，请参阅官方的 [MinIO 文档](https://docs.min.io/)。 -### 2. Install, run, and sign in to MinIO +### 2. 安装、运行和登录到 MinIO -1. Set up your preferred environment variables for MinIO. +1. 为 MinIO 设置首选环境变量。 - These examples use `MINIO_DIR`: + 以下示例使用 `MINIO_DIR`： ```shell $ export MINIO_DIR=$(pwd)/minio $ mkdir -p $MINIO_DIR ``` -2. Install MinIO. +2. 安装 MinIO。 ```shell $ docker pull minio/minio @@ -81,7 +81,7 @@ For more information about your options, see the official [MinIO docs](https://d * 使用 Docker 作为 NAS 网关运行 MinIO： - This setup is useful for deployments where there is already a NAS you want to use as the backup storage for {% data variables.product.prodname_registry %}. + 此设置对于已经有 NAS 用作 {% data variables.product.prodname_registry %} 的备份存储的部署非常有用。 ```shell $ docker run -p 9000:9000 \ @@ -91,30 +91,30 @@ For more information about your options, see the official [MinIO docs](https://d minio/minio gateway nas /data ``` - For more information, see "[MinIO Gateway for NAS](https://docs.min.io/docs/minio-gateway-for-nas.html)." + 更多信息请参阅“[NAS 的 MinIO 网关](https://docs.min.io/docs/minio-gateway-for-nas.html)”。 - * Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the "[Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html). + * 使用 Docker 作为集群运行 MinIO： 此 MinIO 部署使用多个主机和 MinIO 的擦除编码来提供最强的数据保护。 要在群集模式下运行 MinIO，请参阅“[分布式 MinIO 快速入门指南](https://docs.min.io/docs/distributed-minio-quickstart-guide.html)”。 -### 3. Create your MinIO bucket for {% data variables.product.prodname_registry %} +### 3. 为 {% data variables.product.prodname_registry %} 创建 MinIO 存储桶 -1. Install the MinIO client. +1. 安装 MinIO 客户端。 ```shell $ docker pull minio/mc ``` -2. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access. +2. 使用 {% data variables.product.prodname_ghe_server %} 可以访问的主机 URL 创建存储桶。 - * Local deployments example: + * 本地部署示例： ```shell $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" $ docker run minio/mc BUCKET-NAME ``` - This example can be used for MinIO standalone or MinIO as a NAS gateway. + 此示例可用于 MinIO 单机版或作为 NAS 网关的 MinIO。 - * Clustered deployments example: + * 集群部署示例： ```shell $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" @@ -124,10 +124,10 @@ For more information about your options, see the official [MinIO docs](https://d ### 后续步骤 -To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL: +要完成 {% data variables.product.prodname_registry %} 的存储配置，您需要复制 MinIO 存储 URL： ``` echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" ``` -For the next steps, see "[Configuring third-party storage for packages](/admin/packages/configuring-third-party-storage-for-packages)." \ No newline at end of file +有关后续步骤，请参阅“[为包配置第三方存储](/admin/packages/configuring-third-party-storage-for-packages)”。 \ No newline at end of file diff --git a/translations/zh-CN/content/admin/release-notes.md b/translations/zh-CN/content/admin/release-notes.md index 435693295c..730d9f9e45 100644 --- a/translations/zh-CN/content/admin/release-notes.md +++ b/translations/zh-CN/content/admin/release-notes.md @@ -1,6 +1,6 @@ --- title: 发行说明 -intro: The release notes for {{ allVersions[currentVersion].versionTitle }}. +intro: '{{ allVersions[currentVersion].versionTitle }}的发行说明。' layout: release-notes versions: enterprise-server: '*' diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md index aea5e17284..a4167672f2 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-your-enterprise.md @@ -131,7 +131,7 @@ curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ #### 从 {% data variables.product.prodname_dotcom_the_website %} 上的组织中删除仓库 -After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/reference/repos/#delete-a-repository). 您需要身份验证的访问令牌： +在解锁 {% data variables.product.prodname_dotcom_the_website %} 组织的仓库后，您应当使用[仓库删除端点](/rest/reference/repos/#delete-a-repository)删除之前迁移的每一个仓库。 您需要身份验证的访问令牌： ```shell curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ https://api.github.com/repos/orgname/repo_name diff --git a/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md b/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md index 640650e6d5..eda8216eae 100644 --- a/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md +++ b/translations/zh-CN/content/admin/user-management/suspending-and-unsuspending-users.md @@ -83,4 +83,4 @@ fatal: The remote end hung up unexpectedly ``` ### 延伸阅读 -- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file +- "[暂停用户](/rest/reference/enterprise-admin#suspend-a-user)" \ No newline at end of file diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md index 756a72c2fd..c36df2f109 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project.md @@ -36,23 +36,23 @@ versions: #### 创建部分提交 -If one file contains multiple changes, but you only want some of those changes to be included in a commit, you can create a partial commit. 其余更改会保持不动，以便您进行其他修改和提交。 这允许您进行单独、有意义的提交，例如使提交中的换行符更改区别于代码或文字更改。 +如果一个文件包含多处更改，但只有部分更改要包含在提交中，则可创建部分提交。 其余更改会保持不动，以便您进行其他修改和提交。 这允许您进行单独、有意义的提交，例如使提交中的换行符更改区别于代码或文字更改。 {% note %} -**Note:** Split diff displays are currently in beta and subject to change. +**注意：**拆分差异显示当前处于测试阶段，可能会更改。 {% endnote %} -1. To choose how your changes are displayed, in the top-right corner of the changed file, use {% octicon "gear" aria-label="The Gear icon" %} to select **Unified** or **Split**. ![Gear icon with unified and split diffs](/assets/images/help/desktop/gear-diff-select.png) -2. To exclude changed lines from your commit, click one or more changed lines so the blue disappears. The lines that are still highlighted in blue will be included in the commit. ![文件中取消选择的行](/assets/images/help/desktop/partial-commit.png) +1. 要选择更改的显示方式，请在已更改文件的右上角使用 {% octicon "gear" aria-label="The Gear icon" %} 选择**统一**或**拆分**。 ![包含统一和拆分差异的齿轮图标](/assets/images/help/desktop/gear-diff-select.png) +2. 要从提交中排除更改的行，请单击一条或多条更改的行，以使蓝色消失。 仍以蓝色突出显示的行将包含在提交中。 ![文件中取消选择的行](/assets/images/help/desktop/partial-commit.png) ### 3. 放弃更改 -If you have uncommitted changes that you don't want to keep, you can discard the changes. This will remove the changes from the files on your computer. You can discard all uncommitted changes in one or more files, or you can discard specific lines you added. +如果您有不想保留的未提交更改，可以放弃这些更改。 这将从计算机上的文件中删除更改。 您可以放弃一个或多个文件中所有未提交的更改，也可以丢弃添加的特定行。 -Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied. +丢弃的更改保存在回收站中带日期的文件中。 在回收站清空之前，您可以恢复丢弃的更改。 -#### Discarding changes in one or more files +#### 丢弃一个或多个文件中的更改 {% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %} @@ -60,22 +60,22 @@ Discarded changes are saved in a dated file in the Trash. You can recover discar {% data reusables.desktop.confirm-discard-files %} ![确认对话框中的放弃更改按钮](/assets/images/help/desktop/discard-changes-confirm-mac.png) -#### Discarding changes in one or more lines -You can discard one or more changed lines that are uncommitted. +#### 丢弃一行或多行中的更改 +您可以丢弃一个或多个未提交的已更改行。 {% note %} -**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines. +**注意：**在添加和删除行的一组更改中不可丢弃单行。 {% endnote %} -To discard one added line, in the list of changed lines, right click on the line you want to discard and select **Discard added line**. +要丢弃一个添加的行，请在已更改的行列表中，右键单击要丢弃的行，然后选择 **Discard added line（丢弃添加的行）**。 - ![Discard single line in the confirmation dialog](/assets/images/help/desktop/discard-single-line.png) + ![在确认对话框中丢弃单行](/assets/images/help/desktop/discard-single-line.png) -To discard a group of changed lines, right click the vertical bar to the right of the line numbers for the lines you want to discard, then select **Discard added lines**. +要丢弃一组更改的行，请右键单击要丢弃的行编号右侧的垂直条，然后选择 **Discard added lines（丢弃添加的行）**。 - ![Discard a group of added lines in the confirmation dialog](/assets/images/help/desktop/discard-multiple-lines.png) + ![在确认对话框中丢弃一组添加的行](/assets/images/help/desktop/discard-multiple-lines.png) ### 4. 编写提交消息并推送更改 diff --git a/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md b/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md index edc5993b54..3bef2eeeed 100644 --- a/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md +++ b/translations/zh-CN/content/developers/apps/authenticating-with-github-apps.md @@ -28,7 +28,7 @@ versions: {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. 在“Private keys（私钥）”中，单击 **Generate a private key（生成私钥）**。 ![生成私钥](/assets/images/github-apps/github_apps_generate_private_keys.png) +5. In "Private keys", click **Generate a private key**. ![生成私钥](/assets/images/github-apps/github_apps_generate_private_keys.png) 6. 您将看到一个以 PEM 格式下载至您的计算机的私钥。 确保将此文件存储下来，因为 GitHub 仅存储密钥的公共部分。 {% note %} 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 c762436959..b940dbe7d1 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 @@ -49,37 +49,39 @@ versions: 您可以在查询字符串中选择权限：使用下表中的权限名称作为查询参数名称，使用权限类型作为查询值。 例如，要在用户界面中为 `contents` 选择 `Read & write` 权限，您的查询字符串将包括 `&contents=write`。 要在用户界面中为 `blocking` 选择 `Read-only` 权限，您的查询字符串将包括 `&blocking=read`。 要在用户界面中为 `checks` 选择 `no-access` ，您的查询字符串将包括 `checks` 权限。 -| 权限 | 描述 | -| -------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 权限 | 描述 | +| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`管理`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | 对用于组织和仓库管理的各种端点授予访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% if currentVersion == "free-pro-team@latest" %} | [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | 授予对[阻止用户 API](/rest/reference/users#blocking) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} -| [`检查`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | 授予对[检查 API](/rest/reference/checks) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| `content_references` | 授予对“[创建内容附件](/rest/reference/apps#create-a-content-attachment)”端点的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`内容`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | 对用于修改仓库内容的各种端点授予访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`检查`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | 授予对[检查 API](/rest/reference/checks) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| `content_references` | 授予对“[创建内容附件](/rest/reference/apps#create-a-content-attachment)”端点的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`内容`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | 对用于修改仓库内容的各种端点授予访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | | [`部署`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | 授予对[部署 API](/rest/reference/repos#deployments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | 授予对[电子邮件 API](/rest/reference/users#emails) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} -| [`关注者`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | 授予对[关注者 API](/rest/reference/users#followers) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | 授予对[GPG 密钥 API](/rest/reference/users#gpg-keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | 授予对[议题 API](/rest/reference/issues) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`键`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | 授予对[公钥 API](/rest/reference/users#keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`关注者`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | 授予对[关注者 API](/rest/reference/users#followers) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | 授予对[GPG 密钥 API](/rest/reference/users#gpg-keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | 授予对[议题 API](/rest/reference/issues) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`键`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | 授予对[公钥 API](/rest/reference/users#keys) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | | [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | 授予管理组织成员的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% if currentVersion == "free-pro-team@latest" %} -| [`元数据`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | 授予对不泄漏敏感数据的只读端点的访问权限。 可以是 `read` 或 `none`。 设置任何权限时，默认值为 `read`；没有为 {% data variables.product.prodname_github_app %} 指定任何权限时，默认值为 `none`。 | +| [`元数据`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | 授予对不泄漏敏感数据的只读端点的访问权限。 可以是 `read` 或 `none`。 设置任何权限时，默认值为 `read`；没有为 {% data variables.product.prodname_github_app %} 指定任何权限时，默认值为 `none`。 | | [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | 授予对“[更新组织](/rest/reference/orgs#update-an-organization)”端点和[组织交互限制 API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} -| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | 授予对[组织 web 挂钩 API](/rest/reference/orgs#webhooks/) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| `organization_plan` | 授予使用“[获取组织](/rest/reference/orgs#get-an-organization)”端点获取有关组织计划的信息的权限。 可以是以下项之一：`none` 或 `read`。 | +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | 授予对[组织 web 挂钩 API](/rest/reference/orgs#webhooks/) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| `organization_plan` | 授予使用“[获取组织](/rest/reference/orgs#get-an-organization)”端点获取有关组织计划的信息的权限。 可以是以下项之一：`none` 或 `read`。 | | [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | 授予对[项目 API](/rest/reference/projects) 的访问权限。 可以是以下项之一：`none`、`read`、`write` 或 `admin`。{% if currentVersion == "free-pro-team@latest" %} | [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | 授予对[阻止组织用户 API](/rest/reference/orgs#blocking) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} -| [`页面`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | 授予对[页面 API](/rest/reference/repos#pages) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| `plan` | 授予使用“[获取用户](/rest/reference/users#get-a-user)”端点获取有关用户 GitHub 计划的信息的权限。 可以是以下项之一：`none` 或 `read`。 | -| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | 授予对各种拉取请求端点的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | 授予对[仓库 web 挂钩 API](/rest/reference/repos#hooks) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | 授予对[项目 API](/rest/reference/projects) 的访问权限。 可以是以下项之一：`none`、`read`、`write` 或 `admin`。 | -| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | 授予对[内容 API](/rest/reference/repos#contents) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`标星`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | 授予对[标星 API](/rest/reference/activity#starring) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | 授予对[状态 API](/rest/reference/repos#statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | 授予对[团队讨论 API](/rest/reference/teams#discussions) 和[团队讨论注释 API](/rest/reference/teams#discussion-comments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | -| `vulnerability_alerts` | 授予接收仓库漏洞依赖项安全警报的权限。 更多信息请参阅“[关于漏洞依赖项安全警报](/articles/about-security-alerts-for-vulnerable-dependencies)”。 可以是以下项之一：`none` 或 `read`。 | -| `关注` | 授予列出和更改用户订阅的仓库的权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`页面`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | 授予对[页面 API](/rest/reference/repos#pages) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| `plan` | 授予使用“[获取用户](/rest/reference/users#get-a-user)”端点获取有关用户 GitHub 计划的信息的权限。 可以是以下项之一：`none` 或 `read`。 | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | 授予对各种拉取请求端点的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | 授予对[仓库 web 挂钩 API](/rest/reference/repos#hooks) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | 授予对[项目 API](/rest/reference/projects) 的访问权限。 Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Grants access to the [Code scanning API](/rest/reference/code-scanning/). 可以是以下项之一：`none`、`read` 或 `write`。{% endif %} +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | 授予对[内容 API](/rest/reference/repos#contents) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`标星`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | 授予对[标星 API](/rest/reference/activity#starring) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | 授予对[状态 API](/rest/reference/repos#statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | 授予对[团队讨论 API](/rest/reference/teams#discussions) 和[团队讨论注释 API](/rest/reference/teams#discussion-comments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 | +| `vulnerability_alerts` | 授予接收仓库漏洞依赖项安全警报的权限。 更多信息请参阅“[关于漏洞依赖项安全警报](/articles/about-security-alerts-for-vulnerable-dependencies)”。 可以是以下项之一：`none` 或 `read`。 | +| `关注` | 授予列出和更改用户订阅的仓库的权限。 可以是以下项之一：`none`、`read` 或 `write`。 | ### {% data variables.product.prodname_github_app %} web 挂钩事件 diff --git a/translations/zh-CN/content/developers/apps/creating-a-github-app.md b/translations/zh-CN/content/developers/apps/creating-a-github-app.md index 2acadca7d4..5db7f950e1 100644 --- a/translations/zh-CN/content/developers/apps/creating-a-github-app.md +++ b/translations/zh-CN/content/developers/apps/creating-a-github-app.md @@ -42,7 +42,7 @@ versions: {% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -9. 默认情况下，为了提高应用程序的安全性，应用程序将使用过期用户授权令牌。 要选择不使用过期用户令牌，您必须取消选中“Expire user authorization tokens（过期用户授权令牌）”。 要了解有关设置刷新令牌流程和过期用户令牌的好处，请参阅“[刷新用户到服务器的访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”。 ![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png) +9. 默认情况下，为了提高应用程序的安全性，应用程序将使用过期用户授权令牌。 要选择不使用过期用户令牌，您必须取消选中“Expire user authorization tokens（过期用户授权令牌）”。 要了解有关设置刷新令牌流程和过期用户令牌的好处，请参阅“[刷新用户到服务器的访问令牌](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)”。 ![在 GitHub 应用程序设置过程中选择加入过期用户令牌的选项](/assets/images/github-apps/expire-user-tokens-selection.png) {% endif %} 9. 如果应用程序授权用户使用 OAuth 流程，您可以选择**在安装过程中请求用户授权 (OAuth)**，以允许用户在安装应用程序时授权它，从而省去一个步骤。 如果您选择此选项，则“设置 URL”将不可用，用户在安装应用程序后将被重定向到您的“用户授权回调 URL”。 更多信息请参阅“[在安装过程中授权用户](/apps/installing-github-apps/#authorizing-users-during-installation)”。 ![安装过程中请求用户授权](/assets/images/github-apps/github_apps_request_auth_upon_install.png) 10. 如果安装后需要附加设置，请添加一个“设置 URL”以便在用户安装应用程序后重定向他们。 ![GitHub 应用程序的设置 URL 字段 ](/assets/images/github-apps/github_apps_setup_url.png) 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 90452b023a..a543940b63 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 @@ -831,7 +831,7 @@ end ### 疑难解答 -Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}. +以下是一些常见问题和一些建议的解决方案。 如果您遇到任何其他问题，可以在 {% data variables.product.prodname_support_forum_with_url %} 中寻求帮助或建议。 * **问：**我的应用程序没有将代码推送到 GitHub。 我没有看到 RuboCop 自动进行修复！ @@ -857,7 +857,7 @@ Here are a few common problems and some suggested solutions. If you run into any ### 结论 -完成本指南后，您已经学会了使用检查 API 创建 CI 服务器的基础知识！ To review, you: +完成本指南后，您已经学会了使用检查 API 创建 CI 服务器的基础知识！ 回顾一下： * 配置您的服务器来接收检查 API 事件并创建检查运行。 * 使用 RuboCop 来检查仓库中的代码并为错误创建注释。 @@ -865,7 +865,7 @@ Here are a few common problems and some suggested solutions. If you run into any ### 后续步骤 -Here are some ideas for what you can do next: +以下是有关接下来可以做什么的一些想法： * 目前，始终显示“Fix this（修复此问题）”按钮。 更新您编写的代码，仅在 RuboCop 发现错误时显示“Fix this（修复此问题）”按钮。 * 如果您不希望 RuboCop 将文件直接提交到头部分支，您可以更新代码，以使用基于头部分支的新分支[创建拉取请求](/rest/reference/pulls#create-a-pull-request)。 diff --git a/translations/zh-CN/content/developers/apps/installing-github-apps.md b/translations/zh-CN/content/developers/apps/installing-github-apps.md index ed8bc1e8af..2ec8cf17c4 100644 --- a/translations/zh-CN/content/developers/apps/installing-github-apps.md +++ b/translations/zh-CN/content/developers/apps/installing-github-apps.md @@ -22,42 +22,42 @@ versions: 1. 从 [GitHub 应用程序设置页面](https://github.com/settings/apps)，选择您的应用程序。 2. 在左边栏中，单击 **Install App（安装应用程序）**。 3. 单击包含适当仓库的组织或用户帐户旁边的 **Install（安装）**。 -4. 将应用程序安装在所有仓库或所选仓库中。 ![App installation permissions](/assets/images/install_permissions.png) +4. 将应用程序安装在所有仓库或所选仓库中。 ![应用程序安装权限](/assets/images/install_permissions.png) 5. 安装后，您将在所选帐户上看到应用程序的配置选项。 您可以在这里进行更改，或重复前面的步骤将应用程序安装到其他帐户上。 {% if currentVersion == "free-pro-team@latest" %} ### 在 GitHub Marketplace 中提供您的应用程序 -You can offer a paid or free version of your app in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), where people can search for and view details about your app. {% data variables.product.prodname_marketplace %} automatically installs a GitHub App when an order is complete. +您可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 中提供应用程序的付费或免费版本，用户可以在其中搜索您的应用程序并查看其详细信息。 {% data variables.product.prodname_marketplace %} 在订单完成后会自动安装 GitHub 应用程序。 -See "[Getting started with GitHub Marketplace](/marketplace/getting-started/)" to learn more about listing your app on {% data variables.product.prodname_marketplace %}. +要了解如何在 {% data variables.product.prodname_marketplace %} 中上架您的应用程序，请参阅“[GitHub Marketplace 使用入门](/marketplace/getting-started/)”。 -To learn more about how users can install your app from {% data variables.product.prodname_marketplace %}, see "[Purchasing and installing apps in GitHub Marketplace](/articles/purchasing-and-installing-apps-in-github-marketplace)". +要详细了解用户如何从 {% data variables.product.prodname_marketplace %} 安装您的应用程序，请参阅“[在 GitHub Marketplace 中购买和安装应用程序](/articles/purchasing-and-installing-apps-in-github-marketplace)”。 {% endif %} -### Allowing people to install your public app on their repository +### 允许用户在他们的仓库中安装您的公共应用程序 -You can enable others to install your public app by providing the installation URL in places like your app's homepage. You can then point to your app's homepage from the landing page on GitHub. +您可以通过在应用程序的主页等位置提供安装 URL，使其他人能够安装您的公共应用程序。 然后，您可以从 GitHub 的登陆页面指向您的应用程序主页。 - If you are migrating from an OAuth App to a GitHub App, you can use query parameters to preselect the repositories and account when installing the GitHub App. See "[Migrating OAuth Apps to GitHub Apps](/apps/migrating-oauth-apps-to-github-apps/)" to learn more. + 如果要从 OAuth 应用程序迁移到 GitHub 应用程序，您可以在安装 GitHub 应用程序时使用查询参数预先选择仓库和帐户。 更多信息请参阅“[将 OAuth 应用程序迁移到 GitHub 应用程序](/apps/migrating-oauth-apps-to-github-apps/)”。 -These steps assume you have [built a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/): +这些步骤假定您已[构建 {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)： -1. From the [GitHub Apps settings page](https://github.com/settings/apps), select the public app you want to configure for others to install. -2. In "Homepage URL," type the URL for your app's homepage and click **Save changes**. ![Homepage URL](/assets/images/github-apps/github_apps_homepageURL.png) -3. GitHub provides a landing page for your app that includes a link to your app's "Homepage URL." To visit the landing page on GitHub, copy the URL from "Public link" and paste it into a browser. ![Public link](/assets/images/github-apps/github_apps_public_link.png) -4. Create a homepage for your app that includes the app installation URL: `{% data variables.product.oauth_host_code %}/apps//installations/new`. +1. 从 [GitHub应用程序设置页面](https://github.com/settings/apps)，选择要配置以供他人安装的公共应用程序。 +2. 在“Homepage URL（主页 URL）”中，输入应用程序主页的 URL，然后单击 **Save changes（保存更改）**。 ![主页 URL](/assets/images/github-apps/github_apps_homepageURL.png) +3. GitHub 为您的应用程序提供一个登录页面，其中包含指向应用程序“Homepage URL（主页 URL）”的链接。 要访问 GitHub 上的登录页面，请从“Public link（公共链接）”复制 URL 并将其粘贴到浏览器中。 ![公共链接](/assets/images/github-apps/github_apps_public_link.png) +4. 为您的应用程序创建一个包含应用程序安装 URL 的主页：`{% data variables.product.oauth_host_code %}/apps//installations/new`。 -### Authorizing users during installation +### 在安装过程中授权用户 -You can simplify the authorization process by completing it during app installation. To do this, select **Request user authorization (OAuth) during installation** when creating or modifying your app in GitHub. See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" to learn more. +您可以通过在应用程序安装过程中完成授权过程来简化它。 为此，请在创建或修改应用程序时选择**在安装过程中请求用户授权 (OAuth)**。 更多信息请参阅“[创建 GitHub 应用程序](/apps/building-github-apps/creating-a-github-app/)”。 -Once someone has installed your app, you will need to get an access token for the user. See steps 2 and 3 in "[Identifying users on your site](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)" to learn more. -### Preserving an application state during installation +一旦有人安装了您的应用程序，您将需要为用户获取访问令牌。 更多信息请参阅“[识别站点上的用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)”中的步骤 2 和 3。 +### 在安装过程中保留应用程序状态 -You can provide a `state` parameter in an app's installation URL to preserve the state of the application page and return people back to that state after they install, authenticate, or accept updates to your GitHub App. For example, you could use the `state` to correlate an installation to a user or account. +您可以在应用程序的安装 URL 中提供 `state` 参数，以保留应用程序页面的状态，并在用户安装、身份验证或接受 GitHub 应用程序的更新后将用户返回到该状态。 例如，您可以使用 `state` 参数将安装关联到用户或帐户。 -To preserve a state, add it to the installation URL: +要保留状态，请将其添加到安装 URL： `{% data variables.product.oauth_host_code %}/apps//installations/new?state=AB12t` diff --git a/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md b/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md index 1262767482..6cabfa43e9 100644 --- a/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/zh-CN/content/developers/apps/migrating-oauth-apps-to-github-apps.md @@ -1,6 +1,6 @@ --- -title: Migrating OAuth Apps to GitHub Apps -intro: 'Learn about the advantages of migrating your {% data variables.product.prodname_oauth_app %} to a {% data variables.product.prodname_github_app %} and how to migrate an {% data variables.product.prodname_oauth_app %} that isn''t listed on {% data variables.product.prodname_marketplace %}.' +title: 将 OAuth 应用程序迁移到 GitHub 应用程序 +intro: '了解将 {% data variables.product.prodname_oauth_app %} 迁移到 {% data variables.product.prodname_github_app %} 的好处，以及如何迁移未在 {% data variables.product.prodname_marketplace %} 中上架的 {% data variables.product.prodname_oauth_app %}。' redirect_from: - /apps/migrating-oauth-apps-to-github-apps versions: @@ -10,92 +10,92 @@ versions: --- -This article provides guidelines for existing integrators who are considering migrating from an OAuth App to a GitHub App. +本文为考虑从 OAuth 应用程序迁移到 GitHub 应用程序的现有集成者提供指南。 -### Reasons for switching to GitHub Apps +### 切换到 GitHub 应用程序的原因 -[GitHub Apps](/apps/) are the officially recommended way to integrate with GitHub because they offer many advantages over a pure OAuth-based integration: +[GitHub 应用程序](/apps/)是官方推荐的与 GitHub 集成的方式，因为相比纯粹的基于 OAuth 的集成，它们可提供许多优势： -- [Fine-grained permissions](/apps/differences-between-apps/#requesting-permission-levels-for-resources) target the specific information a GitHub App can access, allowing the app to be more widely used by people and organizations with security policies than OAuth Apps, which cannot be limited by permissions. -- [Short-lived tokens](/apps/differences-between-apps/#token-based-identification) provide a more secure authentication method over OAuth tokens. An OAuth token does not expire until the person who authorized the OAuth App revokes the token. GitHub Apps use tokens that expire quickly, creating a much smaller window of time for compromised tokens to be in use. -- [Built-in, centralized webhooks](/apps/differences-between-apps/#webhooks) receive events for all repositories and organizations the app can access. Conversely, OAuth Apps require configuring a webhook for each repository and organization accessible to the user. -- [Bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts) don't consume a {% data variables.product.product_name %} seat and remain installed even when the person who initially installed the app leaves the organization. -- Built-in support for OAuth is still available to GitHub Apps using [user-to-server endpoints](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). -- Dedicated [API rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) for bot accounts scale with your integration. -- Repository owners can [install GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) on organization repositories. If a GitHub App's configuration has permissions that request an organization's resources, the org owner must approve the installation. -- Open Source community support is available through [Octokit libraries](/rest/overview/libraries) and other frameworks such as [Probot](https://probot.github.io/). -- Integrators building GitHub Apps have opportunities to adopt earlier access to APIs. +- [精细权限](/apps/differences-between-apps/#requesting-permission-levels-for-resources)控制 GitHub 应用程序可以访问的特定信息，这使其比 OAuth 应用程序更广地适用于具有安全策略的用户和组织，因为后者不受权限限制。 +- [短期令牌](/apps/differences-between-apps/#token-based-identification)提供比 OAuth 令牌更安全的身份验证方法。 在授权 OAuth 应用程序的人撤销令牌之前，OAuth 令牌不会过期。 GitHub 应用程序使用快速过期的令牌，将受损令牌的使用限制到更小的时限。 +- [内置的集中式 web 挂钩](/apps/differences-between-apps/#webhooks)接收应用程序可以访问的所有仓库和组织的事件。 相反，OAuth 应用程序需要为用户可访问的每个仓库和组织配置一个 web 挂钩。 +- [机器人帐户](/apps/differences-between-apps/#machine-vs-bot-accounts)不占用 {% data variables.product.product_name %} 席位，即使最初安装应用程序的人离开组织，它仍然保持安装状态， +- GitHub 应用程序仍然可以使用[用户到服务器端点](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)对 OAuth 进行内置支持。 +- 专用于机器人帐户的 [API 速率限制](/apps/building-github-apps/understanding-rate-limits-for-github-apps/)随集成而扩展。 +- 仓库所有者可以在组织仓库上[安装 GitHub 应用程序](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps)。 如果 GitHub 应用程序的配置具有请求组织资源的权限，则组织所有者必须批准安装。 +- 可通过 [Octokit 库](/rest/overview/libraries)和其他框架（例如 [Probot](https://probot.github.io/)）获得开源社区支持。 +- 构建 GitHub 应用程序的集成者有机会采用较早的 API 访问方式。 -### Converting an OAuth App to a GitHub App +### 将 OAuth 应用程序转换为 GitHub 应用程序 -These guidelines assume that you have a registered OAuth App{% if currentVersion == "free-pro-team@latest" %} that may or may not be listed in GitHub Marketplace{% endif %}. At a high level, you'll need to follow these steps: +这些指南假定您拥有一个注册的 OAuth 应用程序{% if currentVersion == "free-pro-team@latest" %}，它可能在 GitHub Marketplace 中上架，也可能没上架{% endif %}。 在较高级别，您需要执行以下步骤： -1. [Review the available API endpoints for GitHub Apps](#review-the-available-api-endpoints-for-github-apps) -1. [Design to stay within API rate limits](#design-to-stay-within-api-rate-limits) -1. [Register a new GitHub App](#register-a-new-github-app) -1. [Determine the permissions your app requires](#determine-the-permissions-your-app-requires) -1. [Subscribe to webhooks](#subscribe-to-webhooks) -1. [Understand the different methods of authentication](#understand-the-different-methods-of-authentication) -1. [Direct users to install your GitHub App on repositories](#direct-users-to-install-your-github-app-on-repositories) -1. [Remove any unnecessary repository hooks](#remove-any-unnecessary-repository-hooks) -1. [Encourage users to revoke access to your OAuth app](#encourage-users-to-revoke-access-to-your-oauth-app) +1. [查看 GitHub 应用程序可用的 API 端点](#review-the-available-api-endpoints-for-github-apps) +1. [设计保持在 API 速率限制内](#design-to-stay-within-api-rate-limits) +1. [注册新的 GitHub 应用程序](#register-a-new-github-app) +1. [确定应用程序所需的权限](#determine-the-permissions-your-app-requires) +1. [订阅 web 挂钩](#subscribe-to-webhooks) +1. [了解不同的身份验证方法](#understand-the-different-methods-of-authentication) +1. [指导用户在仓库中安装您的 GitHub 应用程序](#direct-users-to-install-your-github-app-on-repositories) +1. [删除任何不必要的仓库挂钩](#remove-any-unnecessary-repository-hooks) +1. [鼓励用户撤销 OAuth 应用程序的访问权限](#encourage-users-to-revoke-access-to-your-oauth-app) -#### Review the available API endpoints for GitHub Apps +#### 查看 GitHub 应用程序可用的 API 端点 -While the majority of [REST API](/rest) endpoints and [GraphQL](/graphql) queries are available to GitHub Apps today, we are still in the process of enabling some endpoints. Review the [available REST endpoints](/rest/overview/endpoints-available-for-github-apps) to ensure that the endpoints you need are compatible with GitHub Apps. Note that some of the API endpoints enabled for GitHub Apps allow the app to act on behalf of the user. See "[User-to-server requests](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" for a list of endpoints that allow a GitHub App to authenticate as a user. +尽管目前大多数 [REST API](/rest) 端点和 [GraphQL](/graphql) 查询都可用于 GitHub 应用程序，但我们仍在不断启用更多端点。 查看[可用的 REST 端点](/rest/overview/endpoints-available-for-github-apps)，确保您需要的端点与 GitHub 应用程序兼容。 请注意，为 GitHub 应用程序启用的某些 API 端点允许应用程序代表用户执行操作。 有关允许 GitHub 应用程序验证为用户的端点列表，请参阅“[用户到服务器请求](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)”。 -We recommend reviewing the list of API endpoints you need as early as possible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_app %}s. +我们建议您尽早查看所需的 API 端点列表。 如果尚未为 {% data variables.product.prodname_github_app %} 启用您需要的端点，请告知支持人员。 -#### Design to stay within API rate limits +#### 设计保持在 API 速率限制内 -GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), which can increase based on the number of repositories and users in the organization. A GitHub App can also make use of [conditional requests](/rest#conditional-requests) or consolidate requests by using the [GraphQL API V4](/graphql). +GitHub 应用程序使用[滑动速率限制规则](/apps/building-github-apps/understanding-rate-limits-for-github-apps/)，可根据组织中仓库和用户的数量而增加速率上限。 GitHub 应用程序还可以通过使用 [GraphQL API V4](/graphql) 来利用[条件请求](/rest#conditional-requests)或合并请求。 -#### Register a new GitHub App +#### 注册新的 GitHub 应用程序 -Once you've decided to make the switch to Github Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/). +一旦决定要切换到 Github 应用程序，就需要[创建新的 GitHub 应用程序](/apps/building-github-apps/)。 -#### Determine the permissions your app requires +#### 确定应用程序所需的权限 -When registering your GitHub App, you'll need to select the permissions required by each endpoint used in your app's code. See "[GitHub App permissions](/rest/reference/permissions-required-for-github-apps)" for a list of the permissions needed for each endpoint available to GitHub Apps. +注册 GitHub 应用程序时，您需要选择应用程序代码中使用的每个端点所需的权限。 有关 GitHub 应用程序可用的每个端点所需的权限列表，请参阅“[GitHub 应用程序权限](/rest/reference/permissions-required-for-github-apps)”。 -In your GitHub App's settings, you can specify whether your app needs `No Access`, `Read-only`, or `Read & Write` access for each permission type. The fine-grained permissions allow your app to gain targeted access to the subset of data you need. We recommend specifying the smallest set of permissions possible that provides the desired functionality. +在 GitHub 应用程序的设置中，您可以针对每种权限类型指定您的应用程序是否需要 `No Access`、`Read-only` 或 `Read & Write` 权限。 精细权限允许您的应用程序获得有针对性的权限以访问您需要的数据子集。 我们建议指定能够提供所需功能的最小权限集。 -#### Subscribe to webhooks +#### 订阅 web 挂钩 -After you've created a new GitHub App and selected its permissions, you can select the webhook events you wish to subscribe it to. See "[Editing a Github App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks. +创建新的 GitHub 应用程序并选择其权限后，您可以选择要它订阅的 web 挂钩事件。 有关如何订阅 web 挂钩，请参阅“[编辑 GitHub 应用程序的权限](/apps/managing-github-apps/editing-a-github-app-s-permissions/)”。 -#### Understand the different methods of authentication +#### 了解不同的身份验证方法 -GitHub Apps primarily use a token-based authentication that expires after a short amount of time, providing more security than an OAuth token that does not expire. It’s important to understand the different methods of authentication available to you and when you need to use them: +GitHub 应用程序主要使用在短时间后过期的基于令牌的身份验证，比不会过期的 OAuth 令牌更安全。 了解您可以使用的不同身份验证方法以及您何时需要使用它们，这非常重要： -* A **JSON Web Token (JWT)** [authenticates as the GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app). For example, you can authenticate with a **JWT** to fetch application installation details or exchange the **JWT** for an **installation access token**. -* An **installation access token** [authenticates as a specific installation of your GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) (also called server-to-server requests). For example, you can authenticate with an **installation access token** to open an issue or provide feedback on a pull request. -* An **OAuth access token** can [authenticate as a user of your GitHub App](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site) (also called user-to-server requests). For example, you can use an OAuth access token to authenticate as a user when a GitHub App needs to verify a user’s identity or act on a user’s behalf. +* **JSON Web 令牌 (JWT)** [验证为 GitHub 应用程序](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)。 例如，您可以使用 **JWT** 进行身份验证，以获取应用程序安装设施的详细信息或将 **JWT** 交换为**安装访问令牌**。 +* **安装访问令牌**[验证为 GitHub 应用程序的特定安装设施](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)（也称为服务器到服务器请求）。 例如，您可以使用**安装访问令牌**进行身份验证以打开议题或提供对拉取请求的反馈。 +* **OAuth 访问令牌**可以[验证为 GitHub 应用程序的用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)（也称为用户到服务器请求）。 例如， 当 GitHub 应用程序需要验证用户身份或代表用户执行操作时，您可以使用 OAuth 访问令牌验证为用户。 -The most common scenario is to authenticate as a specific installation using an **installation access token**. +最常见的情况是使用**安装访问令牌**验证为特定安装设施。 -#### Direct users to install your GitHub App on repositories +#### 指导用户在仓库中安装您的 GitHub 应用程序 -Once you've made the transition from an OAuth App to a GitHub App, you will need to let users know that the GitHub App is available to install. For example, you can include an installation link for the GitHub App in a call-to-action banner inside your application. To ease the transition, you can use query parameters to identify the user or organization account that is going through the installation flow for your GitHub App and pre-select any repositories your OAuth App had access to. This allows users to easily install your GitHub App on repositories you already have access to. +从 OAuth 应用程序过渡到 GitHub 应用程序后，您需要让用户知道 GitHub 应用程序可供安装。 例如，您可以在应用程序内的呼吁横幅中添加 GitHub 应用程序的安装链接。 为了简化过渡，您可以使用查询参数来识别将要完成 GitHub 应用程序安装流程的用户或组织帐户，并预先选择 OAuth 应用程序可以访问的任何仓库。 这使用户可以轻松地在您有权访问的仓库上安装 GitHub 应用程序。 -##### Query parameters +##### 查询参数 -| 名称 | 描述 | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `suggested_target_id` | **Required**: ID of the user or organization that is installing your GitHub App. | -| `repository_ids[]` | Array of repository IDs. If omitted, we select all repositories. The maximum number of repositories that can be pre-selected is 100. | +| 名称 | 描述 | +| --------------------- | ---------------------------------------------- | +| `suggested_target_id` | **必填**：要安装您的 GitHub 应用程序的用户或组织的 ID。 | +| `repository_ids[]` | 仓库 ID 的数组。 如果省略，我们将选择所有仓库。 可以预先选择的仓库最大数量为 100。 | -##### Example URL +##### 示例 URL ``` https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID ``` -You'll need to replace `YOUR_APP_NAME` with the name of your GitHub App, `ID_OF_USER_OR_ORG` with the ID of your target user or organization, and include up to 100 repository IDs (`REPO_A_ID` and `REPO_B_ID`). To get a list of repositories your OAuth App has access to, use the [List repositories for the authenticated user](/rest/reference/repos#list-repositories-for-the-authenticated-user) and [List organization repositories](/rest/reference/repos#list-organization-repositories) endpoints. +您需要将 `YOUR_APP_NAME` 替换为 GitHub 应用程序的名称，将 `ID_OF_USER_OR_ORG` 替换为目标用户或组织的 ID，并包含最多 100 个仓库 ID（`REPO_A_ID` 和 `REPO_B_ID`）。 要获取 OAuth 应用程序有权访问的仓库列表，请使用[列出经验证用户的仓库](/rest/reference/repos#list-repositories-for-the-authenticated-user)和[列出组织仓库](/rest/reference/repos#list-organization-repositories)端点。 -#### Remove any unnecessary repository hooks +#### 删除任何不必要的仓库挂钩 -Once your GitHub App has been installed on a repository, you should remove any unnecessary webhooks that were created by your legacy OAuth App. If both apps are installed on a repository, they may duplicate functionality for the user. To remove webhooks, you can listen for the [`installation_repositories` webhook](/webhooks/event-payloads/#installation_repositories) with the `repositories_added` action and [Delete a repository webhook](/rest/reference/repos#delete-a-repository-webhook) on those repositories that were created by your OAuth App. +在仓库中安装 GitHub 应用程序后，应删除由原有 OAuth 应用程序创建的任何不必要的 web 挂钩。 如果两个应用程序都安装在仓库中，它们可能会为用户重复执行功能。 要删除 web 挂钩，您可以使用 `repositories_added` 操作侦听 [`installation_repositories` web 挂钩](/webhooks/event-payloads/#installation_repositories)，并删除 OAuth 应用程序在这些仓库中创建的[仓库 web 挂钩](/rest/reference/repos#delete-a-repository-webhook)。 -#### Encourage users to revoke access to your OAuth app +#### 鼓励用户撤销 OAuth 应用程序的访问权限 -As your GitHub App installation base grows, consider encouraging your users to [revoke access](/articles/authorizing-oauth-apps/) to the legacy OAuth integration. +随着 GitHub 应用程序安装基础的增长，请考虑鼓励用户[撤销](/articles/authorizing-oauth-apps/)原有 OAuth 集成的访问权限。 diff --git a/translations/zh-CN/content/developers/apps/rate-limits-for-github-apps.md b/translations/zh-CN/content/developers/apps/rate-limits-for-github-apps.md index 27c41012e7..eb4e8a4ada 100644 --- a/translations/zh-CN/content/developers/apps/rate-limits-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/rate-limits-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: Rate limits for GitHub Apps +title: GitHub 应用程序的速率限制 intro: '{% data reusables.shortdesc.rate_limits_github_apps %}' redirect_from: - /early-access/integrations/rate-limits/ @@ -12,13 +12,13 @@ versions: github-ae: '*' --- -### Server-to-server requests +### 服务器到服务器请求 {% if currentVersion == "free-pro-team@latest" %} -Different server-to-server request rate limits apply to {% data variables.product.prodname_github_app %}s if the app is installed on organizations or repositories owned by a {% data variables.product.prodname_ghe_cloud %} account. +如果应用程序安装在 {% data variables.product.prodname_ghe_cloud %} 帐户拥有的组织或仓库上，则不同的服务器到服务器请求速率限制适用于 {% data variables.product.prodname_github_app %}。 -#### Normal server-to-server rate limits +#### 标准的服务器到服务器速率限制 {% endif %} @@ -26,32 +26,32 @@ Different server-to-server request rate limits apply to {% data variables.produc {% if currentVersion == "free-pro-team@latest" %} -#### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits +#### {% data variables.product.prodname_ghe_cloud %} 服务器到服务器速率限制 -{% data variables.product.prodname_github_app %}s that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +{% data variables.product.prodname_github_app %} 安装在 {% data variables.product.prodname_ghe_cloud %} 帐户拥有的组织或仓库上，发送服务器到服务器请求的速率限制为每小时 15,000 个请求。 {% endif %} ### 用户到服务器请求 -{% data variables.product.prodname_github_app %}s can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests. +{% data variables.product.prodname_github_app %} 还可以[代表用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps)发送用户到服务器的请求。 {% if currentVersion == "free-pro-team@latest" %} -Different user-to-server request rate limits apply to {% data variables.product.prodname_github_app %}s if the app is installed on organizations or repositories owned by a {% data variables.product.prodname_ghe_cloud %} account and the authenticated user also belongs to the same {% data variables.product.prodname_ghe_cloud %} account. +如果应用程序安装在 {% data variables.product.prodname_ghe_cloud %} 帐户拥有的组织或仓库上，并且经验证用户也属于同一个 {% data variables.product.prodname_ghe_cloud %} 帐户，则不同的用户到服务器请求速率限制适用于 {% data variables.product.prodname_github_app %}。 -#### Normal user-to-server rate limits +#### 标准的用户到服务器速率限制 {% endif %} -User-to-server requests are rate limited at 5,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's{% if currentVersion == "github-ae@latest" %} token{% else %} username and password{% endif %} share the same quota of 5,000 requests per hour for that user. +用户到服务器请求的速率限制为每个经验证的用户每小时最多发送 5,000 个请求。 该用户授权的所有 OAuth 应用程序、该用户拥有的个人访问令牌以及使用该用户的{% if currentVersion == "github-ae@latest" %}令牌{% else %} 用户名和密码{% endif %} 验证的请求，将共享该用户每小时 5,000 个请求的配额。 {% if currentVersion == "free-pro-team@latest" %} -#### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits +#### {% data variables.product.prodname_ghe_cloud %} 用户到服务器速率限制 -When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user. +如果用户属于 {% data variables.product.prodname_ghe_cloud %} 帐户，则对同一个 {% data variables.product.prodname_ghe_cloud %} 帐户拥有的资源发出的用户到服务器请求，速率限制为每个经验证用户每小时 15,000 个请求。 该用户授权的所有 OAuth 应用程序、该用户拥有的个人访问令牌以及使用该用户的用户名和密码验证的 {% data variables.product.prodname_ghe_cloud %} 请求，将共享该用户每小时 5,000 个请求的配额。 {% endif %} -For more detailed information about rate limits, see "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" for REST API and "[Resource limitations](/graphql/overview/resource-limitations)" for GraphQL API. +有关速率限制的更多信息，请参阅 REST API 的“[速率限制](/rest/overview/resources-in-the-rest-api#rate-limiting)”和 GraphQL API 的“[资源限制](/graphql/overview/resource-limitations)”。 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 6e392de83c..102819caf1 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 @@ -1,6 +1,6 @@ --- -title: Refreshing user-to-server access tokens -intro: 'To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens.' +title: 刷新用户到服务器访问令牌 +intro: '要实施定期令牌轮换并减少受威胁令牌的影响，您可以配置 {% data variables.product.prodname_github_app %} 以使用过期用户访问令牌。' redirect_from: - /apps/building-github-apps/refreshing-user-to-server-access-tokens versions: @@ -13,28 +13,28 @@ versions: {% data reusables.pre-release-program.expiring-user-access-tokens-beta %} -### About expiring user access tokens +### 关于过期用户访问令牌 -To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens. For more information on making user-to-server requests, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +要实施定期令牌轮换并减少受威胁令牌的影响，您可以配置 {% data variables.product.prodname_github_app %} 以使用过期用户访问令牌。 有关发出用户到服务器请求的更多信息，请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 -Expiring user tokens expire after 8 hours. When you receive a new user-to-server access token, the response will also contain a refresh token, which can be exchanged for a new user token and refresh token. Refresh tokens are valid for 6 months. +过期用户令牌在 8 小时后过期。 当您收到新的用户到服务器访问令牌时，响应还将包含刷新令牌，可以将其交换为新的用户令牌和刷新令牌。 刷新令牌的有效期为 6 个月。 -### Renewing a user token with a refresh token +### 使用刷新令牌续订用户令牌 -To renew an expiring user-to-server access token, you can exchange the `refresh_token` for a new access token and `refresh_token`. +要续订过期的用户到服务器访问令牌，您可以将 `refresh_token` 交换为新的访问令牌和 `refresh_token`。 `POST https://github.com/login/oauth/access_token` -This callback request will send you a new access token and a new refresh token. This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)." +此回调请求将向您发送新的访问令牌和新的刷新令牌。 此回调请求类似于用来将临时 `code` 交换为访问令牌的 OAuth 请求。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)”和“[身份验证基础知识](/rest/guides/basics-of-authentication#providing-a-callback)”。 #### 参数 -| 名称 | 类型 | 描述 | -| --------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `refresh_token` | `字符串` | **Required.** The token generated when the {% data variables.product.prodname_github_app %} owner enables expiring tokens and issues a new user access token. | -| `grant_type` | `字符串` | **Required.** Value must be `refresh_token` (required by the OAuth specification). | -| `client_id` | `字符串` | **Required.** The client ID for your {% data variables.product.prodname_github_app %}. | -| `client_secret` | `字符串` | **Required.** The client secret for your {% data variables.product.prodname_github_app %}. | +| 名称 | 类型 | 描述 | +| --------------- | ----- | --------------------------------------------------------------------------------------- | +| `refresh_token` | `字符串` | **必填。**当 {% data variables.product.prodname_github_app %} 所有者启用过期令牌并颁发新的用户访问令牌时生成的令牌。 | +| `grant_type` | `字符串` | **必填。**值必须为 `refresh_token`（OAuth 规范要求）。 | +| `client_id` | `字符串` | **必填。**{% data variables.product.prodname_github_app %} 的客户端 ID。 | +| `client_secret` | `字符串` | **必填。**{% data variables.product.prodname_github_app %} 的客户端密钥。 | #### 响应 @@ -48,25 +48,25 @@ This callback request will send you a new access token and a new refresh token. "token_type": "bearer" } ``` -### Configuring expiring user tokens for an existing GitHub App +### 为现有 GitHub 应用程序配置过期用户令牌 -You can enable or disable expiring user-to-server authorization tokens from your {% data variables.product.prodname_github_app %} settings. +您可以在 {% data variables.product.prodname_github_app %} 设置中启用或禁用过期用户到服务器授权令牌 {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -4. Click **Edit** next to your chosen {% data variables.product.prodname_github_app %}. ![Settings to edit a GitHub App](/assets/images/github-apps/edit-test-app.png) -5. In the left sidebar, click **Beta Features**. ![Beta Features menu option](/assets/images/github-apps/beta-features-option.png) -6. Next to "User-to-server token expiration", click **Opt-in** or **Opt-out**. This setting may take a couple of seconds to apply. +4. 单击所选 {% data variables.product.prodname_github_app %} 旁边的 **Edit（编辑）**。 ![编辑 GitHub 应用程序的设置](/assets/images/github-apps/edit-test-app.png) +5. 在左边栏中，单击 **Beta Features（测试版功能）**。 ![测试版功能菜单选项](/assets/images/github-apps/beta-features-option.png) +6. 在“User-to-server token expiration（用户到服务器令牌过期）”旁边，单击 **Opt-in（选择加入）**或 **Opt-out（选择退出）**。 应用此设置可能需要几秒钟的时间。 -### Opting out of expiring tokens for new GitHub Apps +### 为新的 GitHub 应用程序选择退出过期令牌 -When you create a new {% data variables.product.prodname_github_app %}, by default your app will use expiring user-to-server access tokens. +当您创建新的 {% data variables.product.prodname_github_app %} 时，默认情况下，您的应用程序将使用过期用户到服务器访问令牌。 -If you want your app to use non-expiring user-to-server access tokens, you can deselect "Expire user authorization tokens" on the app settings page. +如果希望应用程序使用不过期用户到服务器访问令牌，您可以在应用程序设置页面上取消选择“Expire user authorization tokens（过期用户授权令牌）”。 -![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png) +![在 GitHub 应用程序设置过程中选择加入过期用户令牌的选项](/assets/images/github-apps/expire-user-tokens-selection.png) -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. +仅当应用程序所有者为其应用程序启用了过期用户令牌时，使用用户到服务器授权令牌的现有 {% data variables.product.prodname_github_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. 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 +要为现有 {% data variables.product.prodname_github_app %} 启用过期用户令牌，需要通过 OAuth 流程发送用户以重新颁发将在 8 小时后过期的新用户令牌，并使用刷新令牌发出请求以获取新的访问令牌和刷新令牌。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 diff --git a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md index 1e0b15d4f3..fa4937a0cb 100644 --- a/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/scopes-for-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Scopes for OAuth Apps +title: OAuth 应用程序的作用域 intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps/ @@ -11,20 +11,20 @@ versions: github-ae: '*' --- -When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form. +在 GitHub 上设置 OAuth 应用程序时，请求的作用域会在授权表单上显示给用户。 {% note %} -**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +**注** ：如果您在构建 GitHub 应用程序，则不需要在授权请求中提供作用域。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 {% endnote %} {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -If your -{% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)." +如果您的 +{% data variables.product.prodname_oauth_app %} 无法访问浏览器（如 CLI 工具），则无需为用户指定向应用程序验证的作用域。 更多信息请参阅“[授权 OAuth 应用程序](/developers/apps/authorizing-oauth-apps#device-flow)”。 {% endif %} -Check headers to see what OAuth scopes you have, and what the API action accepts: +检查标头以查看您拥有哪些 OAuth 作用域，以及 API 操作接受什么： ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I @@ -33,51 +33,52 @@ X-OAuth-Scopes: repo, user X-Accepted-OAuth-Scopes: user ``` -* `X-OAuth-Scopes` lists the scopes your token has authorized. -* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for. +* `X-OAuth-Scopes` 列出令牌已授权的作用域。 +* `X-Accepted-OAuth-Scopes` 列出操作检查的作用域。 -### Available scopes +### 可用作用域 -| 名称 | 描述 | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -| **`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} -| **`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. | -|  `repo:status` | Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. | -|  `repo_deployment` | Grants access to [deployment statuses](/rest/reference/repos#deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. | -|  `public_repo` | Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. | -|  `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest"%} -|  `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning).{% endif %} -| **`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. | -|  `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. | -|  `read:repo_hook` | Grants read and ping access to hooks in public or private repositories. | -| **`admin:org`** | Fully manage the organization and its teams, projects, and memberships. | -|  `write:org` | Read and write access to organization membership, organization projects, and team membership. | -|  `read:org` | Read-only access to organization membership, organization projects, and team membership. | -| **`admin:public_key`** | Fully manage public keys. | -|  `write:public_key` | Create, list, and view details for public keys. | -|  `read:public_key` | List and view details for public keys. | -| **`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user. | -| **`gist`** | Grants write access to gists. | -| **`通知`** | Grants:
      * read access to a user's notifications
      * mark as read access to threads
      * watch and unwatch access to a repository, and
      * read, write, and delete access to thread subscriptions. | -| **`用户`** | Grants read/write access to profile info only. Note that this scope includes `user:email` and `user:follow`. | -|  `read:user` | Grants access to read a user's profile data. | -|  `user:email` | Grants read access to a user's email addresses. | -|  `user:follow` | Grants access to follow or unfollow other users. | -| **`delete_repo`** | Grants access to delete adminable repositories. | -| **`write:discussion`** | Allows read and write access for team discussions. | -|  `read:discussion` | Allows read access for team discussions.{% if currentVersion == "free-pro-team@latest" %} -| **`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)". | -| **`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)". | -| **`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "[Deleting packages](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} -| **`admin:gpg_key`** | Fully manage GPG keys. | -|  `write:gpg_key` | Create, list, and view details for GPG keys. | -|  `read:gpg_key` | List and view details for GPG keys.{% if currentVersion == "free-pro-team@latest" %} -| **`工作流程`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes, see https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token for details.{% endif %} +| 名称 | 描述 | +| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **`（无作用域）`** | 授予对公共信息的只读访问权限（包括公开的用户个人资料、公共仓库信息和 gist）{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} +| **`site_admin`** | 授予站点管理员对 [{% data variables.product.prodname_ghe_server %} 管理 API 端点](/rest/reference/enterprise-admin)的访问权限。{% endif %} +| **`repo`** | 授予对私有和公共仓库的完全访问权限。 这包括对公共和私有仓库及组织的代码、提交状态、仓库和组织项目、邀请、协作者、添加团队成员身份、部署状态以及仓库 web 挂钩的读取/写入权限。 还授予管理用户项目的权限。 | +|  `repo:status` | 授予对公共和私有仓库提交状态的读取/写入权限。 仅在授予其他用户或服务对私有仓库提交状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | +|  `repo_deployment` | 授予对公共和私有仓库[部署状态](/rest/reference/repos#deployments)的访问权限。 仅在授予其他用户或服务对部署状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 | +|  `public_repo` | 将访问权限限制为公共仓库。 这包括对公共仓库和组织的代码、提交状态、仓库项目、协作者以及部署状态的读取/写入权限。 标星公共仓库也需要此权限。 | +|  `repo:invite` | 授予接受/拒绝仓库协作邀请的权限。 仅在授予其他用户或服务对邀请的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +|  `security_events` | 授予：
      对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限。
      对 [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) 中安全事件的读取和写入权限。{% endif %}{% if currentVersion ver_gt "enterprise-server@2.21" and currentVersion ver_lt "enterprise-server@3.1" %} +|  `security_events` | 授予对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限。{% endif %} +| **`admin:repo_hook`** | 授予对公共和私有仓库中仓库挂钩的读取、写入、ping 和删除权限。 `repo` 和 `public_repo` 作用域授予对仓库（包括仓库挂钩）的完全访问权限。 使用 `admin:repo_hook` 作用域将访问权限限制为仅仓库挂钩。 | +|  `write:repo_hook` | 授予对公共或私有仓库中挂钩的读取、写入和 ping 权限。 | +|  `read:repo_hook` | 授予对公共或私有仓库中挂钩的读取和 ping 权限。 | +| **`admin:org`** | 全面管理组织及其团队、项目和成员。 | +|  `write:org` | 对组织成员身份、组织项目和团队成员身份的读取和写入权限。 | +|  `read:org` | 对组织成员身份、组织项目和团队成员身份的只读权限。 | +| **`admin:public_key`** | 全面管理公钥。 | +|  `write:public_key` | 创建、列出和查看公钥的详细信息。 | +|  `read:public_key` | 列出和查看公钥的详细信息。 | +| **`admin:org_hook`** | 授予对组织挂钩的读取、写入、ping 和删除权限。 **注：**OAuth 令牌只能对由 OAuth 应用程序创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。 | +| **`gist`** | 授予对 gist 的写入权限。 | +| **`通知`** | 授予：
      * 对用户通知的读取权限
      * 对线程的标记读取权限
      * 对仓库的关注和取消关注权限，以及
      * 对线程订阅的读取、写入和删除权限。 | +| **`用户`** | 仅授予对个人资料的读取/写入权限。 请注意，此作用域包括 `user:email` 和 `user:follow`。 | +|  `read:user` | 授予读取用户个人资料数据的权限。 | +|  `user:email` | 授予对用户电子邮件地址的读取权限。 | +|  `user:follow` | 授予关注或取消关注其他用户的权限。 | +| **`delete_repo`** | 授予删除可管理仓库的权限。 | +| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 | +|  `read:discussion` | 授予对团队讨论的读取权限。{% if currentVersion == "free-pro-team@latest" %} +| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 | +| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 | +| **`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 更多信息请参阅“[删除包](/github/managing-packages-with-github-packages/deleting-a-package)”。{% endif %} +| **`admin:gpg_key`** | 全面管理 GPG 密钥。 | +|  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 | +|  `read:gpg_key` | 列出和查看 GPG 密钥的详细信息。{% if currentVersion == "free-pro-team@latest" %} +| **`工作流程`** | 授予添加和更新 {% data variables.product.prodname_actions %} 工作流程文件的权限。 如果在同一仓库中的另一个分支上存在相同的文件(具有相同的路径和内容)，则工作流程文件可以在没有此作用域的情况下提交。 工作流程文件可能公开 `GITHUB_TOKEN`，它可能具有一组不同的作用域，更多信息请参阅 https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token。{% endif %} {% note %} -**Note:** Your OAuth App can request the scopes in the initial redirection. You can specify multiple scopes by separating them with a space: +**注：**您的 OAuth 应用程序可以在初始重定向中请求作用域。 您可以使用空格分隔多个作用域来指定它们： https://github.com/login/oauth/authorize? client_id=...& @@ -85,16 +86,16 @@ X-Accepted-OAuth-Scopes: user {% endnote %} -### Requested scopes and granted scopes +### 请求的作用域和授予的作用域 -The `scope` attribute lists scopes attached to the token that were granted by the user. Normally, these scopes will be identical to what you requested. However, users can edit their scopes, effectively granting your application less access than you originally requested. Also, users can edit token scopes after the OAuth flow is completed. You should be aware of this possibility and adjust your application's behavior accordingly. +`scope` 属性列出了用户授予的附加到令牌的作用域。 通常，这些作用域与您请求的作用域相同。 但是，用户可以编辑其作用域，实际上授予应用程序更少的权限（相比您最初请求的权限）。 此外，用户还可以在 OAuth 流程完成后编辑令牌作用域。 您应该意识到这种可能性，并相应地调整应用程序的行为。 -It's important to handle error cases where a user chooses to grant you less access than you originally requested. For example, applications can warn or otherwise communicate with their users that they will see reduced functionality or be unable to perform some actions. +如果用户选择授予更少的权限（相比您最初请求的权限），妥善处理这种错误情况非常重要。 例如，应用程序可以警告或以其他方式告诉用户，他们可用的功能会减少或者无法执行某些操作。 -Also, applications can always send users back through the flow again to get additional permission, but don’t forget that users can always say no. +此外，应用程序总是可以将用户送回流程以获取更多权限，但不要忘记，用户总是可以说不。 -Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which provides tips on handling modifiable token scopes. +请查看[身份验证基础知识指南](/guides/basics-of-authentication/)，其中提供了有关处理可修改令牌作用域的提示。 -### Normalized scopes +### 标准化作用域 -When requesting multiple scopes, the token is saved with a normalized list of scopes, discarding those that are implicitly included by another requested scope. For example, requesting `user,gist,user:email` will result in a token with `user` and `gist` scopes only since the access granted with `user:email` scope is included in the `user` scope. +请求多个作用域时，将用标准化的作用域列表保存令牌，而放弃其他请求的作用域隐式包含的那些作用域。 例如，请求 `user,gist,user:email` 将生成仅具有 `user` 和 `gist` 作用域的令牌，因为使用 `user:email` 作用域授予的权限包含在 `user` 作用域中。 diff --git a/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md index 8c71adf5db..871ae90521 100644 --- a/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md +++ b/translations/zh-CN/content/developers/apps/setting-up-your-development-environment-to-create-a-github-app.md @@ -1,6 +1,6 @@ --- -title: Setting up your development environment to create a GitHub App -intro: 'Learn the foundations for extending and building new {% data variables.product.prodname_github_apps %}.' +title: 设置开发环境以创建 GitHub 应用程序 +intro: '了解扩展和构建新 {% data variables.product.prodname_github_apps %} 的基础。' redirect_from: - /apps/quickstart-guides/setting-up-your-development-environment versions: @@ -12,142 +12,142 @@ versions: ### 简介 -This guide will walk through the steps needed to configure a GitHub App and run it on a server. GitHub Apps require some setup steps to manage webhook events and connect the app registration on GitHub to your code. The app in this guide serves as a foundation that you can use to extend and build new GitHub Apps. +本指南将演练配置 GitHub 应用程序并在服务器上运行它所需的步骤。 GitHub 应用程序需要一些设置步骤来管理 web 挂钩事件并将 GitHub 上的应用程序注册连接到您的代码。 本指南中的应用程序可用作扩展和构建新 GitHub 应用程序的基础。 -By the end of this guide you'll have registered a GitHub App and set up a web server to receive webhook events. You'll learn how to use a tool called Smee to capture webhook payloads and forward them to your local development environment. The template app you'll configure in this section won't do anything special yet, but it will serve as a framework you can use to start writing app code using the API or complete other [quickstart guides](/apps/quickstart-guides/). {% if currentVersion == "free-pro-team@latest" %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %} +在本指南结束之前，您将注册 GitHub 应用程序并设置 web 服务器以接收 web 挂钩事件。 您将学习如何使用名为 Smee 的工具捕获 web 挂钩有效负载，并将它们转发到本地开发环境。 您将在本节中配置的模板应用不会做任何特殊的事情，但它将作为一个框架，支持您使用 API 开始编写应用程序代码或完成其他[快速入门指南](/apps/quickstart-guides/)。 {% if currentVersion == "free-pro-team@latest" %}您可以在 [GitHub Marketplace](https://github.com/marketplace) 和[使用 GitHub](https://github.com/works-with) 中查看成功的应用程序示例。{% endif %} -After completing this project you will understand how to authenticate as a GitHub App and an installation, and how those authentication methods are different. +完成此项目后，您将了解如何验证为 GitHub 应用程序和安装设施，以及这些身份验证方法有何不同。 -Here are the steps you'll take to configure the template GitHub App: +以下是配置模板 GitHub 应用程序的步骤： -1. [Start a new Smee channel](#step-1-start-a-new-smee-channel) -1. [Register a new GitHub App](#step-2-register-a-new-github-app) -1. [Save your private key and App ID](#step-3-save-your-private-key-and-app-id) -1. [Prepare the runtime environment](#step-4-prepare-the-runtime-environment) -1. [Review the GitHub App template code](#step-5-review-the-github-app-template-code) -1. [Start the server](#step-6-start-the-server) -1. [Install the app on your account](#step-7-install-the-app-on-your-account) +1. [启动新的 Sme 通道](#step-1-start-a-new-smee-channel) +1. [注册新的 GitHub 应用程序](#step-2-register-a-new-github-app) +1. [保存私钥和应用程序 ID](#step-3-save-your-private-key-and-app-id) +1. [准备运行时环境](#step-4-prepare-the-runtime-environment) +1. [审查 GitHub 应用程序模板代码](#step-5-review-the-github-app-template-code) +1. [启动服务器](#step-6-start-the-server) +1. [在您的帐户上安装应用程序](#step-7-install-the-app-on-your-account) {% data reusables.apps.app-ruby-guides %} ### 基本要求 -You may find it helpful to have a basic understanding of the following: +您可能会发现对以下内容有基本的了解很有帮助： * [GitHub 应用程序](/apps/about-apps) * [Web 挂钩](/webhooks) -* [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/rest) +* [Ruby 编程语言](https://www.ruby-lang.org/en/) +* [REST API](/rest) * [Sinatra](http://sinatrarb.com/) -But you can follow along at any experience level. We'll link out to information you need along the way! +但是，任何经验水平都能跟上步伐。 我们会一路提供所需信息的链接。 -Before you begin, you'll need to clone the repository with the template code used in this quickstart. Open your Terminal app and find a directory where you'd like to store the code. Run this command to clone the [GitHub App template](https://github.com/github-developer/github-app-template) repository: +在开始之前，您需要使用本快速入门中所用的模板代码克隆仓库。 打开您的终端应用程序并找到要存储代码的目录。 运行此命令以克隆 [GitHub 应用程序模板](https://github.com/github-developer/github-app-template)仓库： ```shell $ git clone https://github.com/github-developer/github-app-template.git ``` -### 步骤 1. Start a new Smee channel +### 步骤 1. 启动新的 Sme 通道 -To help GitHub send webhooks to your local machine without exposing it to the internet, you can use a tool called Smee. First, go to https://smee.io and click **Start a new channel**. If you're already comfortable with other tools that expose your local machine to the internet like [ngrok](https://dashboard.ngrok.com/get-started) or [localtunnel](https://localtunnel.github.io/www/), feel free to use those. +为了帮助 GitHub 将 web 挂钩发送到您的本地计算机而不将其暴露在互联网上，您可以使用一个名为 Smee 的工具。 首先，转到 https://smee.io，然后单击 **Start a new channel（启动新通道）**。 如果您已经习惯使用将本地计算机暴露到互联网上的其他工具，例如 [ngrok](https://dashboard.ngrok.com/get-started) 或 [localtunnel](https://localtunnel.github.io/www/)，请随意使用。 -![The Smee new channel button](/assets/images/smee-new-channel.png) +![Smee 新通道按钮](/assets/images/smee-new-channel.png) -Starting a new Smee channel creates a unique domain where GitHub can send webhook payloads. You'll need to know this domain for the next step. Here is an example of a unique domain at `https://smee.io/qrfeVRbFbffd6vD`: +启动一个新的 Smee 通道并创建一个唯一的域，供 GitHub 发送 web 挂钩有效负载。 下一步需要了解此域。 以下是 `https://smee.io/qrfeVRbFbffd6vD` 上的唯一域示例： -![A Smee unique channel](/assets/images/smee-unique-domain.png) +![Smee 唯一通道](/assets/images/smee-unique-domain.png) -Next, go back to the Terminal and follow these steps to run the Smee command-line interface (CLI) client: +接下来，返回终端并按照以下步骤运行 Smee 命令行接口 (CLI) 客户端： {% note %} -**Note:** The following steps are slightly different than the "Use the CLI" instructions you'll see in your Smee channel page. You do **not** need to follow the "Use the Node.js client" or "Using Probot's built-in support" instructions. +**注：**以下步骤与您在 Smee 通道页面中看到的“使用 CLI”说明略有不同。 您**不**需要遵循“使用 Node.js 客户端”或“使用 Probot 的内置支持”说明。 {% endnote %} -1. Install the client: +1. 安装客户端： ```shell $ npm install --global smee-client ``` -2. Run the client (replacing `https://smee.io/qrfeVRbFbffd6vD` with your own domain): +2. 运行客户端（将 `https://smee.io/qrfeVRbFbffd6vD` 替换为自己的域）： ```shell $ smee --url https://smee.io/qrfeVRbFbffd6vD --path /event_handler --port 3000 ``` - You should see output like the following: + 您应该会看到如下输出： ```shell Forwarding https://smee.io/qrfeVRbFbffd6vD to http://127.0.0.1:3000/event_handler Connected https://smee.io/qrfeVRbFbffd6vD ``` -The `smee --url ` command tells Smee to forward all webhook events received by the Smee channel to the Smee client running on your computer. The `--path /event_handler` option forwards events to the `/event_handler` route, which we'll cover in a [later section](#step-5-review-the-github-app-template-code). The `--port 3000` option specifies port 3000, which is the port your server will be listening to. Using Smee, your machine does not need to be open to the public internet to receive webhooks from GitHub. You can also open that Smee URL in your browser to inspect webhook payloads as they come in. +`smee --url ` 命令指示 Smee 将 Smee 通道接收的所有 web 挂钩事件转发到计算机上运行的 Smee 客户端。 `--path /event_handler` 选项将事件转发到 `/event_handler` 路由，我们将在[后面的章节](#step-5-review-the-github-app-template-code)中介绍。 `--port 3000` 选项指定端口 3000，这是服务器将侦听的端口。 使用 Smee，您的计算机不需要向公共互联网开放即可从 GitHub 接收 web 挂钩。 您也可以在浏览器中打开 Smee URL 来检查 web 挂钩有效负载。 -We recommend leaving this Terminal window open and keeping Smee connected while you complete the rest of the steps in this guide. Although you _can_ disconnect and reconnect the Smee client without losing your unique domain (unlike ngrok), you may find it easier to leave it connected and do other command-line tasks in a different Terminal window. +我们建议您在完成本指南其余步骤时保持此终端窗口打开并保持 Smee 连接。 尽管您_可以_断开连接后重新连接 Smee 客户端而不会丢失唯一域（与 ngrok 不同），但您可能会发现，保持连接时在其他终端窗口中执行其他命令行任务更容易。 -### 步骤 2. Register a new GitHub App +### 步骤 2. 注册新的 GitHub 应用程序 -If you don't yet have a GitHub account, now is a [great time to join](https://github.com/join). Don't forget to verify your email before continuing! To register a new app, visit the [app settings page](https://github.com/settings/apps) in your GitHub profile, and click **New GitHub App**. +如果您还没有 GitHub 帐户，现在[是时候注册了](https://github.com/join)。 在继续之前，不要忘记验证您的电子邮件地址！ 要注册新应用程序，请访问您的 GitHub 个人资料中的[应用程序设置页面](https://github.com/settings/apps)，然后单击 **New GitHub App（新建 GitHub 应用程序）**。 -![GitHub website, showing the **New App**](/assets/images/new-app.png) +![GitHub 网站，显示 **新应用程序**](/assets/images/new-app.png) -You'll see a form where you can enter details about your app. See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" for general information about the fields on this page. For the purposes of this guide, you'll need to enter specific data in a few fields: +您将看到一个表单，您可以在其中输入有关应用程序的详细信息。 有关此页面上字段的一般信息，请参阅“[创建 GitHub 应用程序](/apps/building-github-apps/creating-a-github-app/)”。 在本指南中，您需要在几个字段中输入特定数据： {% note %} -**Note:** You can always update these settings later to point to a hosted server. +**注：**您以后可以随时更新这些设置以指向托管服务器。 {% endnote %} -* For the "Homepage URL", use the domain issued by Smee. 例如： +* 对于“主页 URL”，请使用 Smee 发布的域名。 例如： - ![Form with Smee domain filled in for homepage URL](/assets/images/homepage-url.png) + ![为主页 URL 填写 Smee 域的表单](/assets/images/homepage-url.png) -* For the "Webhook URL", again use the domain issued by Smee. 例如： +* 对于“web 挂钩 URL”，也请使用 Smee 发布的域名。 例如： - ![Form with Smee domain filled in for webhook URL](/assets/images/webhook-url.png) + ![为 web 挂钩 URL 填写 Smee 域的表单](/assets/images/webhook-url.png) -* For the "Webhook secret", create a password to secure your webhook endpoints. This should be something that only you (and GitHub, via this form) know. The secret is important because you will be receiving payloads from the public internet, and you'll use this secret to verify the webhook sender. Note that the GitHub App settings say the webhook secret is optional, which is true in most cases, but for the template app code to work, you must set a webhook secret. +* 对于“web 挂钩密钥”，请创建密码来保护您的 web 挂钩端点。 这应该是只有您（和 GitHub 通过此表单）知道的密码。 此密钥很重要，因为您将从公共互联网接收有效负载，并且您将使用此密钥来验证 web 挂钩发送者。 请注意，GitHub 应用程序设置表示 web 挂钩密钥是可选的，在大多数情况下确实如此，但要使模板应用程序代码正常工作，您必须设置 web 挂钩密钥。 - ![Form with webhook secret filled in](/assets/images/webhook-secret.png) + ![填写 web 挂钩密钥的表单](/assets/images/webhook-secret.png) -* On the Permissions & Webhooks page, you can specify a set of permissions for your app, which determines how much data your app has access to. Leave this page with its default values. If you decide to extend this template app, you can update these permissions later. +* 在 Permissions & Webhooks（权限和 web 挂钩）页面上，您可以为应用程序指定一组权限，这些权限决定了应用程序有权访问多少数据。 保留此页面的默认值。 如果您决定扩展此模板应用程序，可以在以后更新这些权限。 -* At the bottom of the Permissions & Webhooks page, specify whether this is a private app or a public app. This refers to who can install it: just you, or anyone in the world? For now, leave the app as private by selecting **Only on this account**. +* 在 Permissions & Webhooks（权限和 web 挂钩）页面的底部，指定这是私有应用程序还是公共应用程序。 这是指谁可以安装它：是只有您自己，还是世界上任何人？ 现在，选择 **Only on this account（仅在此帐户上）**将应用程序保留为私有应用程序。 - ![GitHub App privacy](/assets/images/create_app.png) + ![GitHub 应用程序隐私](/assets/images/create_app.png) -Click **Create GitHub App** to create your app! +单击 **Create GitHub App（创建 GitHub 应用程序）**以创建您的应用程序！ -### 步骤 3. Save your private key and App ID +### 步骤 3. 保存私钥和应用程序 ID -After you create your app, you'll be taken back to the [app settings page](https://github.com/settings/apps). You have two more things to do here: +创建应用程序后，您将被带回[应用程序设置页面](https://github.com/settings/apps)。 您还有两件事要做： -* **Generate a private key for your app.** This is necessary to authenticate your app later on. Scroll down on the page and click **Generate a private key**. Save the resulting PEM file (called something like _`app-name`_-_`date`_-private-key.pem) in a directory where you can find it again. +* **为应用程序生成私钥。**这是以后验证应用程序所必需的。 向下滚动页面，然后单击 **Generate a private key（生成私钥）**。 将生成的 PEM 文件（称为 _`app-name`_-_`date`_-private-key.pem 等）保存在可以再次找到的目录中。 - ![The private key generation dialog](/assets/images/private_key.png) + ![私钥生成对话框](/assets/images/private_key.png) -* **Note the app ID GitHub has assigned your app.** You'll need this to prepare your runtime environment. +* **请注意 GitHub 已为您的应用程序分配了应用程序 ID。**您需要使用它来准备运行时环境。 - Your app's ID number + 应用程序的 ID -### 步骤 4. Prepare the runtime environment +### 步骤 4. 准备运行时环境 -To keep your information secure, we recommend putting all your app-related secrets in your computer's memory where your app can find them, rather than putting them directly in your code. A handy development tool called [dotenv](https://github.com/bkeepers/dotenv) loads project-specific environment variables from a `.env` file to `ENV`. Never check your `.env` file into GitHub. This is a local file that stores sensitive information that you don't want on the public internet. The `.env` file is already included in the repository's [`.gitignore`](/articles/ignoring-files/) file to prevent that. +为了保证您的信息安全，我们建议将与应用程序相关的所有密钥放在应用程序可以找到的计算机内存中，而不是直接将它们放在代码中。 一种称为 [dotenv](https://github.com/bkeepers/dotenv) 的便捷开发工具将特定于项目的环境变量从 `.env` 文件加载到 `ENV`。 切勿将 `.env` 文件检入 GitHub。 这是一个本地文件，用于存储您不希望在公共互联网上公开的敏感信息。 为了防止这种情况，`.env` 文件已包含在仓库的 [`.gitignore`](/articles/ignoring-files/) 文件中。 -The template code you downloaded in the [Prerequisites section](#prerequisites) already has an example file called `.env-example`. Rename the example file from `.env-example` to `.env` or create a copy of the `.env-example` file called `.env`. You haven't installed dotenv yet, but you will install it later in this quickstart when you run `bundle install`. **Note:** Quickstarts that reference the steps in this guide may include additional environment variables in the `.env-example` file. Reference the quickstart guide for the project you've cloned on GitHub for guidance setting those additional environment variables. +您在[前提条件](#prerequisites)部分下载的模板代码已经有一个名为 `.env-example` 的示例文件。 将示例文件 `.env-example` 重命名为 `.env`，或者创建 `.env-example` 文件的副本，命名为 `.env`。 您尚未安装 dotenv，但您将在本快速入门后面运行 `bundle install` 时安装它。 **注：**引用本指南步骤的快速入门可能在 `.env-example` 文件中包含其他环境变量。 有关设置这些附加环境变量的指南，请参考 GitHub 上克隆的项目的快速入门指南。 -You need to add these variables to the `.env` file: +您需要将这些变量添加到 `.env` 文件： -* _`GITHUB_PRIVATE_KEY`_: Add the private key you [generated and saved previously](#step-3-save-your-private-key-and-app-id). Open the `.pem` file with a text editor or use the command line to display the contents of the file: `cat path/to/your/private-key.pem`. Copy the entire contents of the file as the value of `GITHUB_PRIVATE_KEY` in your `.env` file. **Note:** Because the PEM file is more than one line you'll need to add quotes around the value like the example below. -* _`GITHUB_APP_IDENTIFIER`_: Use the app ID you noted in the previous section. -* _`GITHUB_WEBHOOK_SECRET`_: Add your webhook secret. +* _`GITHUB_PRIVATE_KEY`_：添加您[之前生成并保存的](#step-3-save-your-private-key-and-app-id)私钥。 使用文本编辑器打开 `.pem` 文件，或使用命令行显示文件的内容：`cat path/to/your/private-key.pem`。 将文件的全部内容复制为 `.env` 文件中的 `GITHUB_PRIVATE_KEY` 值。 **注：**由于 PEM 文件不止一行，您需要像下面的示例那样在值的两边添加引号。 +* _`GITHUB_APP_IDENTIFIER`_：使用您在上一节中注意到的应用程序 ID。 +* _`GITHUB_WEBHOOK_SECRET`_：添加您的 web 挂钩密钥。 -Here is an example `.env` file: +以下是 `.env` 文件示例： ``` PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY----- @@ -159,26 +159,26 @@ GITHUB_APP_IDENTIFIER=12345 GITHUB_WEBHOOK_SECRET=your webhook secret ``` -### 步骤 5. Review the GitHub App template code +### 步骤 5. 审查 GitHub 应用程序模板代码 -The template app code already contains some code that every GitHub App will need. This sections walks you through the code that already exists in the GitHub App template. There aren't any steps that you need to complete in this section. If you're already familiar with the template code, you can skip ahead to "[Step 6. Start the server](#step-6-start-the-server)." +模板应用程序代码已经包含每个 GitHub 应用程序都需要的一些代码。 本节将引导您浏览 GitHub 应用程序模板中已经存在的代码。 在本节中，您不需要完成任何步骤。 如果您已经熟悉模板代码，则可以跳到“[步骤 6. 启动服务器](#step-6-start-the-server)”。 -Open up the `template_server.rb` file in your favorite text editor. You'll see comments throughout this file that provide additional context for the template code. We recommend reading those comments carefully and even adding your own comments to accompany new code you write. +在您喜欢的文本编辑器中打开 `template_server.rb` 文件。 您会在整个文件中看到为模板代码提供更多上下文信息的注释。 我们建议您仔细阅读这些注释，甚至为您编写的新代码添加自己的注释。 -At the top of the file you'll see `set :port 3000`, which sets the port used when starting the web server to match the port you redirected your webhook payloads to in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." +在文件顶部，您将看到 `set :port 3000`，它设置启动 Web 服务器时使用的端口，以匹配您在“[步骤 1. 启动新的 Sme 通道](#step-1-start-a-new-smee-channel)”中将 web 挂钩有效负载重定向到的端口。 -The next code you'll see is the `class GHApp < Sintra::Application` declaration. You'll write all of the code for your GitHub App inside this class. +您将刚看到的下一段代码是 `class GHApp < Sintra::Application` 声明。 您将在此类中编写 GitHub 应用程序的所有代码。 -Out of the box, the class in the template does the following things: -* [Read the environment variables](#read-the-environment-variables) -* [Turn on logging](#turn-on-logging) -* [Define a before filter](#define-a-before-filter) -* [Define the route handler](#define-a-route-handler) -* [Define the helper methods](#define-the-helper-methods) +模板中现成的类可执行以下操作： +* [读取环境变量](#read-the-environment-variables) +* [开启日志记录](#turn-on-logging) +* [定义前置过滤器](#define-a-before-filter) +* [定义路由处理程序](#define-a-route-handler) +* [定义辅助方法](#define-the-helper-methods) -#### Read the environment variables +#### 读取环境变量 -The first thing that this class does is read the three environment variables you set in "[Step 4. Prepare the runtime environment](#step-4-prepare-the-runtime-environment)" and store them in variables to use later: +该类要做的第一件事是读取您在“[步骤 4. 准备运行时环境](#step-4-prepare-the-runtime-environment)”中设置的三个环境变量，并将它们存储在变量中供以后使用： ``` ruby # Expects that the private key in PEM format. Converts the newlines @@ -192,9 +192,9 @@ WEBHOOK_SECRET = ENV['GITHUB_WEBHOOK_SECRET'] APP_IDENTIFIER = ENV['GITHUB_APP_IDENTIFIER'] ``` -#### Turn on logging +#### 开启日志记录 -Next is a code block that enables logging during development, which is the default environment in Sinatra. This code turns on logging at the `DEBUG` level to show useful output in the Terminal while you are developing the app: +接下来是一个在开发过程中启用日志记录的代码块，这是 Sinatra 中的默认环境。 开发应用程序时，此代码在 `DEBUG` 级别打开日志记录，以在终端中显示有用的输出： ``` ruby # Turn on Sinatra's verbose logging during development @@ -203,9 +203,9 @@ configure :development do end ``` -#### Define a before filter +#### 定义前置过滤器 -Sinatra uses [before filters](https://github.com/sinatra/sinatra#filters) that allow you to execute code before the route handler. The `before` block in the template calls four [helper methods](https://github.com/sinatra/sinatra#helpers). The template app defines those helper methods in a [later section](#define-the-helper-methods). +Sinatra 使用[前置过滤器](https://github.com/sinatra/sinatra#filters)允许您在路由处理程序之前执行代码。 模板中的 `before` 块调用四个[辅助方法](https://github.com/sinatra/sinatra#helpers)。 模板应用程序在[后面的部分](#define-the-helper-methods)定义这些辅助方法。 ``` ruby # Before each request to the `/event_handler` route @@ -218,9 +218,9 @@ before '/event_handler' do end ``` -#### Define a route handler +#### 定义路由处理程序 -An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app. +模板代码中包含空路由。 此代码处理对 `/event_handler` 路由的所有 `POST` 请求。 在本快速入门中，您将不会编写此事件处理程序，但请参阅其他[快速入门指南](/apps/quickstart-guides/)，了解有关如何扩展此模板应用程序的示例。 ``` ruby post '/event_handler' do @@ -228,35 +228,35 @@ post '/event_handler' do end ``` -#### Define the helper methods +#### 定义辅助方法 -The helper methods in this template do most of the heavy lifting. Four helper methods are defined in this section of the code. +此模板中的辅助方法可以完成大部分繁重的工作。 代码的这一部分中定义了四个辅助方法。 -##### Handling the webhook payload +##### 处理 web 挂钩有效负载 -The first method `get_payload_request` captures the webhook payload and converts it to JSON format, which makes accessing the payload's data much easier. +第一个方法 `get_payload_request` 捕获 web 挂钩有效负载并将其转换为 JSON 格式，使访问有效负载的数据变得更容易。 -##### Verifying the webhook signature +##### 验证 web 挂钩签名 -The second method `verify_webhook_signature` performs verification of the webhook signature to ensure that GitHub generated the event. To learn more about the code in the `verify_webhook_signature` helper method, see "[Securing your webhooks](/webhooks/securing/)." If the webhooks are secure, this method will log all incoming payloads to your Terminal. The logger code is helpful in verifying your web server is working but you can always remove it later. +第二个方法 `verify_webhook_signature` 对 web 挂钩签名进行验证，以确保 GitHub 生成了事件。 要详细了解 `verify_webhook_signature` 辅助方法中的代码，请参阅“[保护 web 挂钩](/webhooks/securing/)”。 如果 web 挂钩是安全的，则此方法会将所有传入的有效负载记录到您的终端。 记录器代码有助于验证 Web 服务器是否正常运行，但是您以后可以随时删除它。 -##### Authenticating as a GitHub App +##### 验证为 GitHub 应用程序 -To make API calls, you'll be using the [Octokit library](http://octokit.github.io/octokit.rb/). Doing anything interesting with this library will require you, or rather your app, to authenticate. GitHub Apps have two methods of authentication: +要进行 API 调用，您将使用 [Octokit 库](http://octokit.github.io/octokit.rb/)。 要对此库进行任何有意义的操作，都需要您（或者更确切地说是您的应用程序）进行身份验证。 GitHub 应用程序有两种身份验证方法： -- Authenticating as a GitHub App using a [JSON Web Token (JWT)](https://jwt.io/introduction). -- Authenticating as a specific installation of a GitHub App using an installation access token. +- 使用 [JSON Web 令牌 (JWT)](https://jwt.io/introduction) 验证为 GitHub 应用程序。 +- 使用安装访问令牌验证为 GitHub 应用程序的特定安装设施。 -You'll learn about authenticating as an installation in the [next section](#authenticating-as-an-installation). +您将在[下一节](#authenticating-as-an-installation)中了解验证为安装设施。 -[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) lets you do a couple of things: +[验证为 GitHub 应用程序](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)后可以做两件事： - * You can retrieve high-level management information about your GitHub App. + * 可以检索有关 GitHub 应用程序的高级别管理信息。 * 为应用程序安装申请访问令牌。 -For example, you would authenticate as a GitHub App to retrieve a list of the accounts (organization and personal) that have installed your app. But this authentication method doesn't allow you to do much with the API. To access a repository's data and perform operations on behalf of the installation, you need to authenticate as an installation. To do that, you'll need to authenticate as a GitHub App first to request an installation access token. +例如，通过验证为 GitHub 应用程序，您可以检索已安装您的应用程序的帐户（组织帐户和个人帐户）列表。 不过这种身份验证方法不允许您使用 API 做很多事情。 要访问仓库的数据并代表安装设施执行操作，您需要验证为安装设施。 为此，您需要先验证为 GitHub 应用程序才能请求安装设施访问令牌。 -Before you can use the Octokit.rb library to make API calls, you'll need to initialize an [Octokit client](http://octokit.github.io/octokit.rb/Octokit/Client.html) authenticated as a GitHub App. The `authenticate_app` helper method does just that! +在使用 Octokit.rb 库进行 API 调用之前，您需要初始化已验证为 GitHub 应用程序的 [Octokit 客户端](http://octokit.github.io/octokit.rb/Octokit/Client.html)。 `authenticate_app` 辅助方法就可以做到这一点！ ``` ruby # Instantiate an Octokit client authenticated as a GitHub App. @@ -284,11 +284,11 @@ def authenticate_app end ``` -The code above generates a [JSON Web Token (JWT)](https://jwt.io/introduction) and uses it (along with your app's private key) to initialize the Octokit client. GitHub checks a request's authentication by verifying the token with the app's stored public key. To learn more about how this code works, see "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)." +上面的代码生成 [JSON Web 令牌 (JWT)](https://jwt.io/introduction)并使用它（以及应用程序的私钥）来初始化 Octokit 客户端。 GitHub 通过使用应用程序存储的公钥验证令牌来检查请求的身份验证。 要了解有关此代码如何工作的更多信息，请参阅“[验证为 GitHub 应用程序](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)”。 ##### 验证为安装 -_安装设施_是指已安装该应用程序的任何用户或组织帐户。 Even if someone installs the app on more than one repository, it only counts as one installation because it's within the same account. The last helper method `authenticate_installation` initializes an [Octokit client](http://octokit.github.io/octokit.rb/Octokit/Client.html) authenticated as an installation. This Octokit client is what you'd use to make authenticated API calls. +_安装设施_是指已安装该应用程序的任何用户或组织帐户。 即使有人在多个仓库中安装应用程序，也只能算作一个安装设施，因为它们在同一个帐户内。 最后一个辅助方法 `authenticate_installation` 初始化已验证为安装设施的 [Octokit 客户端](http://octokit.github.io/octokit.rb/Octokit/Client.html)。 此 Octokit 客户端是您用来进行经验证 API 调用的客户端。 ``` ruby # Instantiate an Octokit client authenticated as an installation of a @@ -300,40 +300,40 @@ def authenticate_installation(payload) end ``` -The [`create_app_installation_access_token`](http://octokit.github.io/octokit.rb/Octokit/Client/Apps.html#create_app_installation_access_token-instance_method) Octokit method creates an installation token. This method accepts two arguments: +[`create_app_installation_access_token`](http://octokit.github.io/octokit.rb/Octokit/Client/Apps.html#create_app_installation_access_token-instance_method) Octokit 方法创建安装令牌。 此方法接受两个参数： -* Installation (integer): The ID of a GitHub App installation -* Options (hash, defaults to `{}`): A customizable set of options +* 安装 设施(整数)：GitHub 应用程序安装设施的 ID +* 选项（哈希，默认为 `{}`）： 一组可自定义的选项 -Any time a GitHub App receives a webhook, it includes an `installation` object with an `id`. Using the client authenticated as a GitHub App, you pass this ID to the `create_app_installation_access_token` method to generate an access token for each installation. Since you're not passing any options to the method, the options default to an empty hash. If you look back at [the docs](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation), you can see the response for `create_app_installation_access_token` includes two fields: `token` and `expired_at`. The template code selects the token in the response and initializes an installation client. +GitHub 应用程序收到的每个 web 挂钩都包含一个带有 `id` 的 `installation` 对象。 使用验证为 GitHub 应用程序的客户端，您将此 ID 传递给 `create_app_installation_access_token` 方法，为每个安装设施生成访问令牌。 由于您没有向该方法传递任何选项，因此这些选项默认为空哈希。 如果回顾一下[文档](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)，您可以看到 `create_app_installation_access_token` 的响应包含两个字段：`token` 和 `expired_at`。 模板代码选择响应中的令牌并初始化安装客户端。 -With this method in place, each time your app receives a new webhook payload, it creates a client for the installation that triggered the event. This authentication process enables your GitHub App to work for all installations on any account. +使用此方法，您的应用程序每次收到新的 web 挂钩有效负载时，都会为触发事件的安装设施创建一个客户端。 此身份验证过程使您的 GitHub 应用程序能够在任何帐户上的所有安装设施中正常工作。 -Now you're ready to start making API calls! +现在您可以开始进行 API 调用了！ -### 步骤 6. Start the server +### 步骤 6. 启动服务器 -Your app doesn't _do_ anything yet, but at this point, you can get it running on the server. +您的应用程序还没有_做_任何事情，但是现在您可以让它在服务器上运行。 -Keep Smee running in the current tab in your Terminal. Open a new tab and `cd` into the directory where you [cloned the template app code](#prerequisites). The Ruby code in this repository will start up a [Sinatra](http://sinatrarb.com/) web server. This code has a few dependencies. You can install these by running: +让 Smee 在您终端的当前选项卡中运行。 打开一个新选项卡并 `cd` 到您[克隆了模板应用程序代码](#prerequisites)的目录中。 此仓库中的 Ruby 代码将启动 [Sinatra](http://sinatrarb.com/) web 服务器。 此代码有一些依赖项。 可以通过运行以下命令安装它们： ```shell $ gem install bundler ``` -Followed by: +后接： ```shell $ bundle install ``` -With the dependencies installed, you can start the server: +安装依赖项后，您可以启动服务器： ```shell $ ruby template_server.rb ``` -You should see a response like: +您应该会看到如下响应： ```shell > == Sinatra (v2.0.3) has taken the stage on 3000 for development with backup from Puma @@ -345,25 +345,25 @@ You should see a response like: > Use Ctrl-C to stop ``` -If you see an error, make sure you've created the `.env` file in the directory that contains `template_server.rb`. +如果您看到错误，请确保在包含 `template_server.rb` 的目录中创建了 `.env` 文件。 -Once the server is running, you can test it by going to `http://localhost:3000` in your browser. If the app works as expected, you'll see a helpful error page: +服务器运行后，您可以在浏览器中转到 `http://localhost:3000` 来测试它。 如果应用程序按预期工作，您将看到一个有用的错误页面： -Sinatra's 404 error page +Sinatra 的 404 错误页面 -This is good! Even though it's an error page, it's a _Sinatra_ error page, which means your app is connected to the server as expected. You're seeing this message because you haven't given the app anything else to show. +很好！ 即使它是一个错误页面，它也是一个 _Sinatra_ 错误页面，这意味着您的应用程序已按预期连接到服务器。 之所以会看到此消息，是因为您还没有给应用程序提供任何要显示的内容。 -### 步骤 7. Install the app on your account +### 步骤 7. 在您的帐户上安装应用程序 -You can test that the server is listening to your app by triggering an event for it to receive. A simple event you can test is installing the app on your GitHub account, which should send the [`installation`](/webhooks/event-payloads/#installation) event. If the app receives it, you should see some output in the Terminal tab where you started `template_server.rb`. +您可以通过触发要接收的事件来测试服务器是否正在侦听您的应用程序。 您可以测试的一个简单事件是在您的 GitHub 帐户上安装应用程序，这应该会发送 [`installation`](/webhooks/event-payloads/#installation) 事件。 如果应用程序收到它，您应该会在启动了 `template_server.rb` 的终端选项卡中看到一些输出。 -To install the app, visit the [app settings page](https://github.com/settings/apps), choose your app, and click **Install App** in the sidebar. Next to your username, click **Install**. +要安装应用程序，请访问[应用程序设置页面](https://github.com/settings/apps)，选择您的应用程序，然后在边栏中单击 **Install App（安装应用程序）**。 在您的用户名旁边，单击 **Install（安装）**。 -You'll be asked whether to install the app on all repositories or selected repositories. If you don't want to install the app on _all_ of your repositories, that's okay! You may want to create a sandbox repository for testing purposes and install your app there. +系统会询问您是在所有仓库还是所选仓库上安装应用程序。 如果您不想在_所有_仓库上安装该应用程序，那没关系！ 您可能需要创建一个沙箱仓库用于测试，并在那里安装您的应用程序。 -App installation permissions +应用程序安装权限 -After you click **Install**, look at the output in your Terminal. You should see something like this: +单击 **Install（安装）**后，在终端中查看输出。 您应该会看到以下内容： ```shell > D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation @@ -374,31 +374,31 @@ After you click **Install**, look at the output in your Terminal. You should see > 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019 ``` -This is good news! It means your app received a notification that it was installed on your GitHub account. If you see something like this, your app is running on the server as expected. 🙌 +好消息！ 这意味着您的应用程序收到了它已安装在您的 GitHub 帐户上的通知。 如果您看到以下图标，则表明您的应用程序正在服务器上按预期运行。 🙌 -If you don't see the output, make sure Smee is running correctly in another Terminal tab. If you need to restart Smee, note that you'll also need to _uninstall_ and _reinstall_ the app to send the `installation` event to your app again and see the output in Terminal. If Smee isn't the problem, see the "[Troubleshooting](#troubleshooting)" section for other ideas. +如果看不到输出，请确保 Smee 能够在另一个终端选项卡中正常运行。 如果需要重新启动 Smee，请注意，您还需要_卸载_并_重新安装_该应用程序，以便再次向您的应用程序发送 `installation` 事件并在终端中查看输出。 如果 Smee 不是问题所在，请参阅“[疑难解答](#troubleshooting)”部分了解其他想法。 -If you're wondering where the Terminal output above is coming from, it's written in the [app template code](#prerequisites) in `template_server.rb`. +您可能想知道上面的终端输出来自哪里，它是在 `template_server.rb` 的[应用程序模板代码](#prerequisites)中写入的内容。 ### 疑难解答 -Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}. +以下是一些常见问题和一些建议的解决方案。 如果您遇到任何其他问题，可以在 {% data variables.product.prodname_support_forum_with_url %} 中寻求帮助或建议。 -* **Q:** When I try to install the Smee command-line client, I get the following error: +* **问：**我尝试安装 Smee 命令行客户端时，出现以下错误： ```shell > npm: command not found ``` - **A:** Looks like you don't have npm installed. The best way to install it is to download the Node.js package at https://nodejs.org and follow the installation instructions for your system. npm will be installed alongside Node.js. + **答**：看起来您没有安装 npm。 安装它的最佳方法是在 https://nodejs.org 下载 Node.js 包，然后按照适合您系统的安装说明进行安装。 npm 将随 Node.js 一起安装。 -* **Q:** When I run the server, I get the following error: +* **问：**我运行服务器时，出现以下错误： ```shell > server.rb:38:in `initialize': Neither PUB key nor PRIV key: header too long (OpenSSL::PKey::RSAError) ``` - **A:** You probably haven't set up your private key environment variable quite right. Your `GITHUB_PRIVATE_KEY` variable should look like this: + **答：**您可能还没有正确设置您的私钥环境变量。 您的 `GITHUB_PRIVATE_KEY` 变量应如下所示： ``` PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY----- @@ -408,26 +408,26 @@ Here are a few common problems and some suggested solutions. If you run into any -----END RSA PRIVATE KEY-----" ``` - Double-check that you've copied the correct public key into your `.env` file. + 再次检查是否已将正确的公钥复制到 `.env` 文件中。 -* **Q:** When I run the server, it crashes with this error: +* **问：**我运行服务器时，它崩溃并显示以下错误： ```shell > Octokit::Unauthorized ... 401 - Bad credentials` ``` - **A:** You may be authenticated as a GitHub App but not as an installation. Make sure you follow all the steps under "[Authenticate as an installation](#authenticating-as-an-installation)," and use the `@installation_client` instance variable (authenticated with an installation access token) for your API operations, not the `@app_client` instance variable (authenticated with a JWT). The `@app_client` can only retrieve high-level information about your app and obtain installation access tokens. It can't do much else in the API. + **答：**您可能被验证为 GitHub 应用程序而不是安装设施。 请确保遵循“[验证为安装设施](#authenticating-as-an-installation)”下的所有步骤，并使用 `@installation_client` 实例变量（使用安装访问令牌进行身份验证）进行 API 操作，而不是 `@app_client` 实例变量（使用 JWT 进行身份验证）。 `@app_client` 只能检索有关应用程序的高级别信息和获取安装访问令牌。 它在 API 中做不了太多其他事情。 -* **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm installing the app on a repository on GitHub, but I don't see any output in the Terminal window where I'm running the server. +* **问：**我的服务器没有侦听事件！ Smee 客户端在终端窗口中运行，我正在将应用程序安装到 GitHub 上的仓库中，但是在运行服务器的终端窗口中没有看到任何输出。 - **A:** You may not be running the Smee client, or you may not have the correct Smee domain in your GitHub App settings. First check to make sure the Smee client is running in a Terminal tab. If that's not the problem, visit your [app settings page](https://github.com/settings/apps) and check the fields shown in "[Step 2. Register a new GitHub App](#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u ` command in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." + **答：**您可能没有运行 Smee 客户端，或者您的 GitHub 应用程序设置中没有正确的 Smee 域。 首先检查以确保 Smee 客户端在终端选项卡中运行。 如果这不是问题所在，请访问您的[应用程序设置页面](https://github.com/settings/apps)并检查“[步骤 2. 注册新 GitHub 应用程序](#step-2-register-a-new-github-app)”中显示的字段。 确保这些字段中的域与您在“[步骤 1”的 `smee -u ` 命令中使用的域相匹配。 启动新的 Sme 通道](#step-1-start-a-new-smee-channel)”中将 web 挂钩有效负载重定向到的端口。 -* **Q:** I'm getting seeing an `Octokit::NotFound` 404 error in my debug output: +* **问：**我的调试输出中出现 `Octokit::NotFound` 404 错误： ``` 2018-12-06 15:00:56 - Octokit::NotFound - POST https://api.github.com/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token: ``` - **A:** Ensure the variables in your `.env` file are correct. Make sure that you have not set identical variables in any other environment variable files like `bash_profile`. You can check the environment variables your app is using by adding `puts` statements to your app code and re-running the code. For example, to ensure you have the correct private key set, you could add `puts PRIVATE_KEY` to your app code: + **答：**确保 `.env` 文件中的变量正确。 请确保您没有在任何其他环境变量文件（例如 `bash_profile`）中设置相同的变量。 您可以通过在应用程序代码中添加 `puts` 语句并重新运行代码来检查应用程序正在使用的环境变量。 例如，为了确保您有正确的私钥集，可以将 `puts PRIVATE_KEY` 添加到您的应用程序代码中： ``` PRIVATE_KEY = OpenSSL::PKey::RSA.new(ENV['GITHUB_PRIVATE_KEY'].gsub('\n', "\n")) @@ -436,14 +436,14 @@ Here are a few common problems and some suggested solutions. If you run into any ### 结论 -After walking through this guide, you've learned the basic building blocks for developing GitHub Apps! To review, you: +完成本指南后，您已了解开发 GitHub 应用程序的基本构建块！ 回顾一下： -* Registered a new GitHub App -* Used Smee to receive webhook payloads -* Ran a simple web server via Sinatra -* Authenticated as a GitHub App -* Authenticated as an installation +* 注册新的 GitHub 应用程序 +* 使用 Sme 接收 web 挂钩有效负载 +* 通过 Sinatra 运行一个简单的 Web 服务器 +* 验证为 GitHub 应用程序 +* 验证为安装设施 ### 后续步骤 -You now have a GitHub App running on a server. It doesn't do anything special yet, but check out some of the ways you can customize your GitHub App template in the other [quickstart guides](/apps/quickstart-guides/). +现在，您在服务器上运行了 GitHub 应用程序。 它还没有做任何特别的事情，但是您可以在其他[快速入门指南](/apps/quickstart-guides/)中了解一些自定义 GitHub 应用程序模板的方法。 diff --git a/translations/zh-CN/content/developers/apps/using-content-attachments.md b/translations/zh-CN/content/developers/apps/using-content-attachments.md index 664b642e52..d7582d7d86 100644 --- a/translations/zh-CN/content/developers/apps/using-content-attachments.md +++ b/translations/zh-CN/content/developers/apps/using-content-attachments.md @@ -1,6 +1,6 @@ --- -title: Using content attachments -intro: Content attachments allow a GitHub App to provide more information in GitHub for URLs that link to registered domains. GitHub renders the information provided by the app under the URL in the body or comment of an issue or pull request. +title: 使用内容附件 +intro: 内容附件允许 GitHub 应用程序在 GitHub 中为链接到注册域的 URL 提供更多信息。 GitHub 可渲染应用程序在正文或者议题或拉取请求注释中的 URL 下提供的信息。 redirect_from: - /apps/using-content-attachments versions: @@ -11,32 +11,32 @@ versions: {% data reusables.pre-release-program.content-attachments-public-beta %} -### About content attachments +### 关于内容附件 -A GitHub App can register domains that will trigger `content_reference` events. When someone includes a URL that links to a registered domain in the body or comment of an issue or pull request, the app receives the [`content_reference` webhook](/webhooks/event-payloads/#content_reference). You can use content attachments to visually provide more context or data for the URL added to an issue or pull request. The URL must be a fully-qualified URL, starting with either `http://` or `https://`. URLs that are part of a markdown link are ignored and don't trigger the `content_reference` event. +GitHub 应用程序可以注册将触发 `content_reference` 事件的域。 当有人在正文或者议题或拉取请求的注释中包含链接到注册域的 URL 时，应用程序会收到 [`content_reference` web 挂钩](/webhooks/event-payloads/#content_reference)。 您可以使用内容附件直观地为添加到议题或拉取请求的 URL 提供更多的上下文或数据。 URL 必须是完全合格的 URL，以 `http://` 或 `https://` 开头。 作为 Markdown 链接一部分的 URL 将被忽略，不会触发 `content_reference` 事件。 -Before you can use the {% data variables.product.prodname_unfurls %} API, you'll need to configure content references for your GitHub App: -* Give your app `Read & write` permissions for "Content references." -* Register up to 5 valid, publicly accessible domains when configuring the "Content references" permission. Do not use IP addresses when configuring content reference domains. You can register a domain name (example.com) or a subdomain (subdomain.example.com). -* Subscribe your app to the "Content reference" event. +在使用 {% data variables.product.prodname_unfurls %} API 之前，您需要为 GitHub 应用程序配置内容引用： +* 为应用程序提供对“内容引用”的 `Read & write` 权限。 +* 配置“内容引用”权限时，注册最多 5 个有效且可公开访问的域。 配置内容引用域时不要使用 IP 地址。 您可以注册域名 (example.com) 或子域 (subdomain.example.com)。 +* 让应用程序订阅“内容引用”事件。 -Once your app is installed on a repository, issue or pull request comments in the repository that contain URLs for your registered domains will generate a content reference event. 应用程序必须在发布内容引用 URL 后六小时内创建内容附件。 +将应用程序安装到仓库中后，仓库中包含注册域 URL 的议题或拉取请求注释将生成内容引用事件。 应用程序必须在发布内容引用 URL 后六小时内创建内容附件。 -Content attachments will not retroactively update URLs. It only works for URLs added to issues or pull requests after you configure the app using the requirements outlined above and then someone installs the app on their repository. +内容附件不会追溯更新 URL。 只有在您根据上述要求配置了应用程序，并且有人在其仓库中安装应用程序之后，它才会更新添加到议题或拉取请求中的 URL。 -See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" or "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" for the steps needed to configure GitHub App permissions and event subscriptions. +有关配置 GitHub 应用程序权限和事件订阅所需的步骤，请参阅“[创建 GitHub 应用程序](/apps/building-github-apps/creating-a-github-app/)”或“[编辑 GitHub 应用程序的权限](/apps/managing-github-apps/editing-a-github-app-s-permissions/)”。 -### Implementing the content attachment flow +### 实现内容附件流程 -The content attachment flow shows you the relationship between the URL in the issue or pull request, the `content_reference` webhook event, and the REST API endpoint you need to call to update the issue or pull request with additional information: +内容附件流程向您显示议题或拉取请求中的 URL、`content_reference` web 挂钩事件以及使用额外信息更新议题或拉取请求所需调用的 REST API 端点之间的关系。 -**Step 1.** Set up your app using the guidelines outlined in [About content attachments](#about-content-attachments). You can also use the [Probot App example](#example-using-probot-and-github-app-manifests) to get started with content attachments. +**步骤 1.** 使用[关于内容附件](#about-content-attachments)中的指南设置应用程序。 您也可以根据 [Probot 应用程序示例](#example-using-probot-and-github-app-manifests)开始使用内容附件。 -**Step 2.** Add the URL for the domain you registered to an issue or pull request. You must use a fully qualified URL that starts with `http://` or `https://`. +**步骤 2.** 将注册域的 URL 添加到议题或拉取请求。 必须使用以 `http://` 或 `https://` 开头的完全合格 URL。 -![URL added to an issue](/assets/images/github-apps/github_apps_content_reference.png) +![添加到议题的 URL](/assets/images/github-apps/github_apps_content_reference.png) -**Step 3.** Your app will receive the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) with the action `created`. +**步骤 3.**应用程序将收到带有操作 `created` 的 [`content_reference` web 挂钩](/webhooks/event-payloads/#content_reference)。 ``` json { @@ -55,12 +55,12 @@ The content attachment flow shows you the relationship between the URL in the is } ``` -**Step 4.** The app uses the `content_reference` `id`, to [Create a content attachment](/rest/reference/apps#create-a-content-attachment) using the REST API. You'll also need the `installation` `id` to authenticate as a [GitHub App installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +**步骤 4.** 应用程序使用 `content_reference` `id`，以使用 REST API [创建内容附件](/rest/reference/apps#create-a-content-attachment)。 您还需要 `installation` `id` 以验证为 [GitHub 应用程序安装设施](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)。 {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} -The `body` parameter can contain markdown: +`body` 参数可包含 Markdown： ```shell curl -X POST \ @@ -73,14 +73,14 @@ The `body` parameter can contain markdown: }' ``` -For more information about creating an installation token, see "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)." +有关创建和安装令牌的更多信息，请参阅“[验证为 GitHub 应用程序](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)”。 -**Step 5.** You'll see the new content attachment appear under the link in a pull request or issue comment: +**步骤 5.** 在拉取请求或议题注释中，您将看到新的内容附件显示在链接下： -![Content attached to a reference in an issue](/assets/images/github-apps/github_apps_content_reference_attachment.png) +![附加到议题引用的内容](/assets/images/github-apps/github_apps_content_reference_attachment.png) -### Using content attachments in GraphQL -We provide the `node_id` in the [`content_reference` webhook](/webhooks/event-payloads/#content_reference) event so you can refer to the `createContentAttachment` mutation in the GraphQL API. +### 在 GraphQL 中使用内容附件 +我们在 [`content_reference` web 挂钩](/webhooks/event-payloads/#content_reference)中提供 `node_id`，以便您可以在 GraphQL API 中引用 `createContentAttachment` 突变。 {% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %} @@ -104,7 +104,7 @@ mutation { } } ``` -Example cURL: +示例 cURL： ```shell curl -X "POST" "https://api.github.com/graphql" \ @@ -116,16 +116,16 @@ curl -X "POST" "https://api.github.com/graphql" \ }' ``` -For more information on `node_id`, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." +有关 `node_id` 的更多信息，请参阅“[使用全局节点 ID](/graphql/guides/using-global-node-ids)”。 -### Example using Probot and GitHub App Manifests +### 使用 Probot 和 GitHub 应用程序清单的示例 -To quickly setup a GitHub App that can use the {% data variables.product.prodname_unfurls %} API, you can use [Probot](https://probot.github.io/). See "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" to learn how Probot uses GitHub App Manifests. +要快速设置可使用 {% data variables.product.prodname_unfurls %} API 的 GitHub 应用程序，您可以使用 [Probot](https://probot.github.io/)。 要了解 Probot 如何使用 GitHub 应用程序清单，请参阅“[从清单创建 GitHub 应用程序](/apps/building-github-apps/creating-github-apps-from-a-manifest/)”。 -To create a Probot App, follow these steps: +要创建 Probot 应用程序，请按照以下步骤操作： 1. [生成新的 GitHub 应用程序](https://probot.github.io/docs/development/#generating-a-new-app)。 -2. 打开您创建的项目，自定义 `app.yml` 文件中的设置。 Subscribe to the `content_reference` event and enable `content_references` write permissions: +2. 打开您创建的项目，自定义 `app.yml` 文件中的设置。 订阅 `content_reference` 事件并启用 `content_references` 写入权限： ``` yml @@ -145,7 +145,7 @@ To create a Probot App, follow these steps: value: example.org ``` -3. Add this code to the `index.js` file to handle `content_reference` events and call the REST API: +3. 将此代码添加到 `index.js` 文件以处理 `content_reference` 事件并调用 REST API： ``` javascript module.exports = app => { @@ -166,13 +166,13 @@ To create a Probot App, follow these steps: } ``` -4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to [localhost:3000](http://localhost:3000), and click the **Register GitHub App** button: +4. [在本地运行 GitHub 应用程序](https://probot.github.io/docs/development/#running-the-app-locally)。 导航到 [localhost:3000](http://localhost:3000)， 然后单击 **Register GitHub App（注册 GitHub 应用程序）**按钮： ![注册 Probot GitHub 应用程序](/assets/images/github-apps/github_apps_probot-registration.png) -5. Install the app on a test repository. -6. Create an issue in your test repository. -7. Add a comment to the issue you opened that includes the URL you configured in the `app.yml` file. -8. Take a look at the issue comment and you'll see an update that looks like this: +5. 在测试仓库中安装应用程序。 +6. 在测试仓库中创建议题。 +7. 将注释添加到您打开的议题，包括您在 `app.yml` 文件中配置的 URL。 +8. 查看议题注释，您将看到如下所示的更新： - ![Content attached to a reference in an issue](/assets/images/github-apps/github_apps_content_reference_attachment.png) + ![附加到议题引用的内容](/assets/images/github-apps/github_apps_content_reference_attachment.png) diff --git a/translations/zh-CN/content/developers/apps/using-the-github-api-in-your-app.md b/translations/zh-CN/content/developers/apps/using-the-github-api-in-your-app.md index d969ac5d6b..6ee3aa87a7 100644 --- a/translations/zh-CN/content/developers/apps/using-the-github-api-in-your-app.md +++ b/translations/zh-CN/content/developers/apps/using-the-github-api-in-your-app.md @@ -1,6 +1,6 @@ --- -title: Using the GitHub API in your app -intro: Learn how to set up your app to listen for events and use the Octokit library to perform REST API operations. +title: 在应用程序中使用 GitHub API +intro: 了解如何设置应用程序以侦听事件，并使用 Octokit 库执行 REST API 操作。 redirect_from: - /apps/building-your-first-github-app/ - /apps/quickstart-guides/using-the-github-api-in-your-app @@ -13,83 +13,83 @@ versions: ### 简介 -This guide will help you build a GitHub App and run it on a server. The app you build will add a label to all new issues opened in the repository where the app is installed. +本指南将帮助您构建 GitHub 应用程序并在服务器上运行它。 您构建的应用程序将为在安装该应用程序的仓库中所有打开的新议题添加标签。 -This project will walk you through the following: +此项目将引导您完成以下工作： -* Programming your app to listen for events -* Using the Octokit.rb library to do REST API operations +* 编程应用程序以侦听事件 +* 使用 Octokit. rb 库执行 REST API 操作 {% data reusables.apps.app-ruby-guides %} -Once you've worked through the steps, you'll be ready to develop other kinds of integrations using the full suite of GitHub APIs. {% if currentVersion == "free-pro-team@latest" %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %} +一旦完成了这些步骤，您就可以使用整套 GitHub API 开发其他类型的集成。 {% if currentVersion == "free-pro-team@latest" %}您可以在 [GitHub Marketplace](https://github.com/marketplace) 和[使用 GitHub](https://github.com/works-with) 中查看成功的应用程序示例。{% endif %} ### 基本要求 -You may find it helpful to have a basic understanding of the following: +您可能会发现对以下内容有基本的了解很有帮助： * [GitHub 应用程序](/apps/about-apps) * [Web 挂钩](/webhooks) -* [The Ruby programming language](https://www.ruby-lang.org/en/) -* [REST APIs](/rest) +* [Ruby 编程语言](https://www.ruby-lang.org/en/) +* [REST API](/rest) * [Sinatra](http://sinatrarb.com/) -But you can follow along at any experience level. We'll link out to information you need along the way! +但是，任何经验水平都能跟上步伐。 我们会一路提供所需信息的链接。 -Before you begin, you'll need to do the following: +在开始之前，您需要执行以下操作： -1. Clone the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository. +1. 克隆[在应用程序中使用 GitHub API](https://github.com/github-developer/using-the-github-api-in-your-app) 仓库。 ```shell $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git ``` 在目录中，您将找到包含本快速入门将要使用的模板代码的 `template_server.rb` 文件以及包含已完成项目代码的 `server.rb` 文件。 -1. Follow the steps in the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart to configure and run the `template_server.rb` app server. If you've previously completed a GitHub App quickstart other than [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/), you should register a _new_ GitHub App and start a new Smee channel to use with this quickstart. +1. 按照“[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)”快速入门中的步骤来配置和运行 `template_server.rb` 应用程序服务器。 如果您以前完成了[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)以外的其他 GitHub 应用程序快速入门，您应该注册一个_新_ GitHub 应用程序并启动一个新 Smee 通道以用于本快速入门。 - This quickstart includes the same `template_server.rb` code as the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart. **Note:** As you follow along with the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart, make sure to use the project files included in the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository. + 本快速入门包含与[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)快速入门相同的 `template_server.rb` 代码。 **注：**遵循[设置开发环境](/apps/quickstart-guides/setting-up-your-development-environment/)快速入门的同时，请确保使用[在应用程序中使用 GitHub API](https://github.com/github-developer/using-the-github-api-in-your-app) 仓库中包含的项目文件。 - See the [Troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App. + 如果在设置模板 GitHub 应用程序时遇到问题，请参阅[疑难解答](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting)部分。 -### Building the app +### 构建应用程序 -Now that you're familiar with the `template_server.rb` code, you're going to create code that automatically adds the `needs-response` label to all issues opened in the repository where the app is installed. +现在您已经熟悉了 `template_server.rb` 代码，您将创建可将 `needs-response` 标签自动添加到安装该应用程序的仓库中所有已打开议题的代码。 -The `template_server.rb` file contains app template code that has not yet been customized. In this file, you'll see some placeholder code for handling webhook events and some other code for initializing an Octokit.rb client. +`template_server.rb` 文件包含尚未自定义的应用程序模板代码。 在本文件中，您将看到一些用于处理 web 挂钩事件的占位符代码，以及用于初始化 Octokit.rb 客户端的一些其他代码。 {% note %} -**Note:** `template_server.rb` contains many code comments that complement this guide and explain additional technical details. You may find it helpful to read through the comments in that file now, before continuing with this section, to get an overview of how the code works. +**注：**`template_server.rb` 包含许多代码注释，可补充本指南并解释其他技术细节。 您可能会发现，在继续本节之前通读该文件中的注释以概要了解代码的工作方式，将对您大有帮助。 -The final customized code that you'll create by the end of this guide is provided in [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Try waiting until the end to look at it, though! +您在本指南末尾创建的最终自定义代码存在于 [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb) 中。 不过，尽可能等到最后再查看它吧！ {% endnote %} -These are the steps you'll complete to create your first GitHub App: +以下是创建第一个 GitHub 应用程序要完成的步骤： -1. [Update app permissions](#step-1-update-app-permissions) -2. [Add event handling](#step-2-add-event-handling) -3. [Create a new label](#step-3-create-a-new-label) -4. [Add label handling](#step-4-add-label-handling) +1. [更新应用程序权限](#step-1-update-app-permissions) +2. [添加事件处理](#step-2-add-event-handling) +3. [创建新标签](#step-3-create-a-new-label) +4. [添加标签处理](#step-4-add-label-handling) -### 步骤 1. Update app permissions +### 步骤 1. 更新应用程序权限 -When you [first registered your app](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read issues and write labels. +如果您在[首次注册应用程序](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)时接受了默认权限，则意味着您的应用程序无法访问大多数资源。 对于此示例，您的应用程序将需要读取议题和写入标签的权限。 要更新应用程序的权限： 1. 从[应用程序设置页面](https://github.com/settings/apps)选择应用程序，然后单击边栏中的 **Permissions & Webhooks（权限和 web 挂钩）**。 -1. In the "Permissions" section, find "Issues," and select **Read & Write** in the "Access" dropdown next to it. The description says this option grants access to both issues and labels, which is just what you need. -1. In the "Subscribe to events" section, select **Issues** to subscribe to the event. +1. 在“Permissions（权限）”部分，找到“Issues（议题）”，然后在其旁边的“Access（访问权限）”下拉列表中选择 **Read & write（读取和写入）**。 说明中表示，此选项将授予对议题和标签的访问权限，而这正是您所需要的。 +1. 在“Subscribe to events（订阅事件）”部分，选择 **Issues（议题）**以订阅事件。 {% data reusables.apps.accept_new_permissions_steps %} -太好了！ 您的应用程序现在有权限执行所需的任务。 Now you can add the code to make it work. +太好了！ 您的应用程序现在有权限执行所需的任务。 现在，您可以添加代码使其正常工作。 -### 步骤 2. Add event handling +### 步骤 2. 添加事件处理 -The first thing your app needs to do is listen for new issues that are opened. Now that you've subscribed to the **Issues** event, you'll start receiving the [`issues`](/webhooks/event-payloads/#issues) webhook, which is triggered when certain issue-related actions occur. You can filter this event type for the specific action you want in your code. +应用程序需要做的第一件事是侦听打开的新议题。 现在您已订阅 **Issues（议题）**事件，您将开始接收 [`issues`](/webhooks/event-payloads/#issues) web 挂钩，它在某些与议题相关的操作发生时触发。 您可以根据要在代码中执行的特定操作来过滤此事件类型。 -GitHub 将 web 挂钩有效负载作为 `POST` 请求发送。 Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads in the `post '/event_handler'` route. +GitHub 将 web 挂钩有效负载作为 `POST` 请求发送。 因为您已将 Smee web 挂钩有效负载转发到 `http://localhost/event_handler:3000`，因此您的服务器将在 `post '/event_handler'` 路由中接收 `POST` 请求有效负载。 您在[前提条件](#prerequisites)部分中下载的 `template_server.rb` 文件中已包括空 `post '/event_handler'` 路由。 空路由如下所示： @@ -104,7 +104,7 @@ GitHub 将 web 挂钩有效负载作为 `POST` 请求发送。 Because you forwa end ``` -Use this route to handle the `issues` event by adding the following code: +通过添加以下代码，使用此路由来处理 `issues` 事件： ``` ruby case request.env['HTTP_X_GITHUB_EVENT'] @@ -115,9 +115,9 @@ when 'issues' end ``` -GitHub 发送的每个事件都包含一个名为 `HTTP_X_GITHUB_EVENT` 的请求标头，它指示 `POST` 请求中的事件类型。 Right now, you're only interested in `issues` event types. 每个事件都有一个附加的 `action` 字段，它指示触发事件的操作类型。 For `issues`, the `action` field can be `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, or `reopened`. +GitHub 发送的每个事件都包含一个名为 `HTTP_X_GITHUB_EVENT` 的请求标头，它指示 `POST` 请求中的事件类型。 现在，您只关注 `issues` 事件类型。 每个事件都有一个附加的 `action` 字段，它指示触发事件的操作类型。 对于 `issues`，`action` 字段可以是 `assigned`、`unassigned`、`labeled`、`unlabeled`、`opened`、`edited`、`milestoned`、`demilestoned`、`closed` 或 `reopened`。 -To test your event handler, try adding a temporary helper method. You'll update later when you [Add label handling](#step-4-add-label-handling). For now, add the following code inside the `helpers do` section of the code. You can put the new method above or below any of the other helper methods. Order doesn't matter. +要测试事件处理程序，请尝试添加临时辅助方法。 稍后将在[添加标签处理](#step-4-add-label-handling)时进行更新。 现在，在代码的 `helpers do` 部分添加以下代码。 您可以将新方法放在其他任何辅助方法的上方或下方。 顺序无关紧要。 ``` ruby def handle_issue_opened_event(payload) @@ -125,37 +125,37 @@ def handle_issue_opened_event(payload) end ``` -This method receives a JSON-formatted event payload as an argument. This means you can parse the payload in the method and drill down to any specific data you need. You may find it helpful to inspect the full payload at some point: try changing `logger.debug 'An issue was opened!` to `logger.debug payload`. The payload structure you see should match what's [shown in the `issues` webhook event docs](/webhooks/event-payloads/#issues). +此方法接收 JSON 格式的事件有效负载作为参数。 这意味着您可以解析方法中的有效负载并深入挖掘所需的任何特定数据。 您可能会发现在某个时候检查整个有效负载很有帮助：尝试将 `logger.debug 'An issue was opened!` 更改为 `logger.debug payload`。 您看到的有效负载结构应该与 [`issues` web 挂钩事件文档中显示的](/webhooks/event-payloads/#issues)结构相匹配。 -太好了！ It's time to test the changes. +太好了！ 是时候测试更改了。 {% data reusables.apps.sinatra_restart_instructions %} -In your browser, visit the repository where you installed your app. Open a new issue in this repository. The issue can say anything you like. It's just for testing. +在浏览器中，访问安装应用程序的仓库。 在此仓库中打开一个新议题。 此议题可以谈论您喜欢的任何事情。 它仅用于测试。 -When you look back at your Terminal, you should see a message in the output that says, `An issue was opened!` Congrats! You've added an event handler to your app. 💪 +回头查看终端时，您应该会在输出中看到一条消息：`An issue was opened!` 恭喜！ 您已将事件处理程序添加到应用程序中。 💪 -### 步骤 3. Create a new label +### 步骤 3. 创建新标签 -Okay, your app can tell when issues are opened. Now you want it to add the label `needs-response` to any newly opened issue in a repository the app is installed in. +好，您的应用程序在有议题被打开时会告诉您。 现在，您希望它将标签 `needs-response` 添加到安装该应用程序的仓库中任何新打开的议题。 -Before the label can be _added_ anywhere, you'll need to _create_ the custom label in your repository. You'll only need to do this one time. For the purposes of this guide, create the label manually on GitHub. In your repository, click **Issues**, then **Labels**, then click **New label**. Name the new label `needs-response`. +将标签_添加_到任何位置之前，您需要在仓库中_创建_自定义标签。 只需要这样做一次。 就本指南而言，请在 GitHub 上手动创建标签。 在仓库中，依次单击 **Issues（议题）**、**Labels（标签）**，然后单击 **New label（新建标签）**。 将新标签命名为 `needs-response`。 {% tip %} -**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. +**提示**：如果您的应用能够以编程方式创建标签，那岂不是很棒吗？ [它能](/rest/reference/issues#create-a-label)！ 完成本指南中的步骤后，请尝试添加代码，自行实现。 {% endtip %} -Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue). +现在，标签有了，您可以对应用程序进行编程，以使用 REST API [将标签添加到任何新打开的议题中](/rest/reference/issues#add-labels-to-an-issue)。 -### 步骤 4. Add label handling +### 步骤 4. 添加标签处理 -Congrats—you've made it to the final step: adding label handling to your app. For this task, you'll want to use the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/). +恭喜！您来到了最后一步：向应用程序添加标签处理。 要完成此任务，您需要使用 [Octokit.rb Ruby 库](http://octokit.github.io/octokit.rb/)。 -In the Octokit.rb docs, find the list of [label methods](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). The method you'll want to use is [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method). +在 Octokit.rb 文档中，找到[标签方法](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html)列表。 您要使用的方法是 [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method)。 -Back in `template_server.rb`, find the method you defined previously: +回到 `template_server.rb`，找到您以前定义的方法： ``` ruby def handle_issue_opened_event(payload) @@ -163,13 +163,13 @@ def handle_issue_opened_event(payload) end ``` -The [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) docs show you'll need to pass three arguments to this method: +[`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) 文档显示您需要向此方法传递三个参数： -* Repo (string in `"owner/name"` format) -* Issue number (integer) -* Labels (array) +* 仓库（`"owner/name"` 格式的字符串） +* 议题编号（整数） +* 标签（数组） -You can parse the payload to get both the repo and the issue number. Since the label name will always be the same (`needs-response`), you can pass it as a hardcoded string in the labels array. Putting these pieces together, your updated method might look like this: +您可以解析有效负载以获取仓库和议题编号。 由于标签名称始终相同 (`needs-response`)，因此可以在标签数组中作为硬编码字符串传递它。 将这些片段放在一起，更新后的方法可能如下所示： ``` ruby # When an issue is opened, add a label @@ -180,56 +180,56 @@ def handle_issue_opened_event(payload) end ``` -Try opening a new issue in your test repository and see what happens! If nothing happens right away, try refreshing. +尝试在测试仓库中打开一个新议题，看看会发生什么！ 如果没有任何反应，请尝试刷新。 -You won't see much in the Terminal, _but_ you should see that a bot user has added a label to the issue. +在终端中看不到太多信息，_但是_您应该看到机器人用户已向该议题添加了标签。 {% note %} -**Note:** When GitHub Apps take actions via the API, such as adding labels, GitHub shows these actions as being performed by _bot_ accounts. For more information, see "[Machine vs. bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts)." +**注：**当 GitHub 应用程序通过 API 执行操作（例如添加标签）时，GitHub 会显示这些操作由_机器人_帐户执行。 更多信息请参阅“[机器与机器人帐户](/apps/differences-between-apps/#machine-vs-bot-accounts)”。 {% endnote %} -If so, congrats! You've successfully built a working app! 🎉 +如果是，恭喜！ 您已成功构建了一个可正常工作的应用程序！ 🎉 -You can see the final code in `server.rb` in the [app template repository](https://github.com/github-developer/using-the-github-api-in-your-app). +您可以在[应用程序模板仓库](https://github.com/github-developer/using-the-github-api-in-your-app)的 `server.rb` 中查看最终代码。 -See "[Next steps](#next-steps)" for ideas about where you can go from here. +有关接下来可以做什么的想法，请参阅“[后续步骤](#next-steps)”。 ### 疑难解答 -Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}. +以下是一些常见问题和一些建议的解决方案。 如果您遇到任何其他问题，可以在 {% data variables.product.prodname_support_forum_with_url %} 中寻求帮助或建议。 -* **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm sending events on GitHub.com by opening new issues, but I don't see any output in the Terminal window where I'm running the server. +* **问：**我的服务器没有侦听事件！ Smee 客户端在终端窗口中运行，我通过打开新议题在 GitHub.com 上发送事件，但是在运行服务器的终端窗口中没有看到任何输出。 - **A:** You may not have the correct Smee domain in your app settings. Visit your [app settings page](https://github.com/settings/apps) and double-check the fields shown in "[Register a new app with GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u ` command in "[Start a new Smee channel](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)." + **答：**您的应用程序设置中可能没有正确的 Smee 域。 访问[应用程序设置页面](https://github.com/settings/apps)，然后双击“[使用 GitHub 注册新应用程序](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)”中显示的的字段。 确保这些字段中的域与您在“[启动新的 Smee 通道](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)”中的 `smee -u ` 命令中使用的域相匹配。 -* **Q:** My app doesn't work! I opened a new issue, but even after refreshing, no label has been added to it. +* **问：**我的应用程序无法正常工作！ 我打开了一个新议题，但是即使刷新后也没有给它添加标签。 - **A:** Make sure all of the following are true: + **答：**请确保满足以下所有条件： - * You [installed the app](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) on the repository where you're opening the issue. - * Your [Smee client is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) in a Terminal window. - * Your [web server is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) with no errors in another Terminal window. - * Your app has [read & write permissions on issues and is subscribed to issue events](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel). - * You [checked your email](#step-1-update-app-permissions) after updating the permissions and accepted the new permissions. + * 您在打开议题的仓库中[安装了应用程序](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account)。 + * 您的 [Smee 客户端正在终端窗口中运行](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)。 + * 您的 [web 服务器](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server)能够在其他终端窗口中无错误运行。 + * 您的应用程序具有[对议题的读取和写入权限并且订阅了议题事件](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)。 + * 您在更新权限后[检查了电子邮件](#step-1-update-app-permissions)并接受了新权限。 ### 结论 -After walking through this guide, you've learned the basic building blocks for developing GitHub Apps! To review, you: +完成本指南后，您已了解开发 GitHub 应用程序的基本构建块！ 回顾一下： -* Programmed your app to listen for events -* Used the Octokit.rb library to do REST API operations +* 编程应用程序以侦听事件 +* 使用 Octokit. rb 库执行 REST API 操作 ### 后续步骤 -Here are some ideas for what you can do next: +以下是有关接下来可以做什么的一些想法： -* [Rewrite your app using GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)! -* Rewrite your app in Node.js using [Probot](https://github.com/probot/probot)! -* Have the app check whether the `needs-response` label already exists on the issue, and if not, add it. -* When the bot successfully adds the label, show a message in the Terminal. (Hint: compare the `needs-response` label ID with the ID of the label in the payload as a condition for your message, so that the message only displays when the relevant label is added and not some other label.) -* Add a landing page to your app and hook up a [Sinatra route](https://github.com/sinatra/sinatra#routes) for it. -* Move your code to a hosted server (like Heroku). Don't forget to update your app settings with the new domain. -* Share your project or get advice in the {% data variables.product.prodname_support_forum_with_url %}{% if currentVersion == "free-pro-team@latest" %} -* Have you built a shiny new app you think others might find useful? [Add it to GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %} +* [使用 GraphQL 重写应用程序](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)！ +* 使用 [Probot](https://github.com/probot/probot) 在 Node.js 中重写应用程序！ +* 让应用程序检查议题上是否存在 `needs-response` 标签，如果否，则添加它。 +* 当机器人成功添加标签时，在终端中显示消息。 （提示：将 `needs-response` 标签 ID 与有效负载中的标签 ID 进行比较，以作为显示消息的条件，这样只有在添加相关标签时才显示消息。） +* 向应用程序添加登录页面并为它连接 [Sinatra 路由](https://github.com/sinatra/sinatra#routes)。 +* 将代码移动到托管服务器（如 Heroku）。 不要忘记使用新域更新应用程序设置。 +* 在 {% data variables.product.prodname_support_forum_with_url %}{% if currentVersion == "free-pro-team@latest" %} 中分享项目或寻求建议 +* 您是否构建了一款让人眼前一亮的新应用程序？您认为它可能对其他人有帮助？ [将其添加到 GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)！{% endif %} diff --git a/translations/zh-CN/content/developers/github-marketplace/about-github-marketplace.md b/translations/zh-CN/content/developers/github-marketplace/about-github-marketplace.md index a3fd3b9745..6b9a0d183d 100644 --- a/translations/zh-CN/content/developers/github-marketplace/about-github-marketplace.md +++ b/translations/zh-CN/content/developers/github-marketplace/about-github-marketplace.md @@ -1,6 +1,6 @@ --- title: 关于 GitHub Marketplace -intro: 'Learn the basics to prepare your app for review before joining {% data variables.product.prodname_marketplace %}.' +intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.' redirect_from: - /apps/marketplace/getting-started/ - /marketplace/getting-started @@ -8,58 +8,47 @@ versions: free-pro-team: '*' --- -[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) connects you to developers who want to extend and improve their {% data variables.product.prodname_dotcom %} workflows. You can list free and paid tools for developers to use in {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_marketplace %} offers developers two types of tools: {% data variables.product.prodname_actions %} and Apps, and each tool requires different steps for adding it to {% data variables.product.prodname_marketplace %}. +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 为您与希望扩展和改进其 {% data variables.product.prodname_dotcom %} 工作流程的开发者提供纽带。 您可以在 {% data variables.product.prodname_marketplace %} 中上架免费和付费的工具，供开发者使用。 {% data variables.product.prodname_marketplace %} 为开发者提供两种类型的工具：{% data variables.product.prodname_actions %} 和应用程序，每种工具都需要不同的步骤才能添加到 {% data variables.product.prodname_marketplace %} 中。 ### GitHub Actions {% data reusables.actions.actions-not-verified %} -To learn about publishing {% data variables.product.prodname_actions %} in the {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." +To learn about publishing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %}, see "[Publishing actions in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace)." ### 应用 -You can list verified and unverified apps in {% data variables.product.prodname_marketplace %}. Unverified apps do not go through the security, testing, and verification cycle {% data variables.product.prodname_dotcom %} requires for verified apps. +Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only listings that are verified by {% data variables.product.company_short %} can include paid plans. For more information, see "[About verified creators](/developers/github-marketplace/about-verified-creators)." -Verified apps have a green badge in {% data variables.product.prodname_marketplace %}. Unverified apps have a grey badge next to their listing and are only available as free apps. +If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_app %}s](/developers/apps/building-oauth-apps)." -![Green verified and grey unverified badge](/assets/images/marketplace/marketplace_verified_badges.png) +{% data reusables.marketplace.github_apps_preferred %}，尽管您可以在 {% data variables.product.prodname_marketplace %} 中上架 OAuth 和 {% data variables.product.prodname_github_app %}。 For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_app %}s to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." -If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s, see "[Building apps](/apps/)." +如果您对 {% data variables.product.prodname_marketplace %} 有疑问，请直接联系 {% data variables.contact.contact_support %}。 -{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_app %}s in {% data variables.product.prodname_marketplace %}. See "[Differences between GitHub and OAuth apps](/apps/differences-between-apps/)" for more details. To learn more about switching from OAuth to {% data variables.product.prodname_github_apps %}, see [Migrating OAuth Apps to {% data variables.product.prodname_github_app %}s](/apps/migrating-oauth-apps-to-github-apps/). +### Publishing an app to {% data variables.product.prodname_marketplace %} -If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly. +When you have finished creating your app, you can share it with other users by publishing it to {% data variables.product.prodname_marketplace %}. In summary, the process is: -#### Unverified Apps +1. Review your app carefully to ensure that it will behave as expected in other repositories and that it follows best practice guidelines. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)" and "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience)." -Unverified apps do not need to meet the "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)" or go through the "[Security review process](/marketplace/getting-started/security-review-process/)". +1. Add webhook events to the app to track user billing requests. For more information about the {% data variables.product.prodname_marketplace %} API, webhook events, and billing requests, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -{% data reusables.marketplace.unverified-apps %} Having a published paid plan will prevent you from being able to submit an unverified app. You must remove paid plans or keep them in draft mode before publishing an unverified app. +1. Create a draft {% data variables.product.prodname_marketplace %} listing. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)." -To list your unverified app in {% data variables.product.prodname_marketplace %}, you only need to create a "[Listing on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)" and submit it as an unverified listing. +1. Add a pricing plan. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -{% data reusables.marketplace.launch-with-free %} +1. Check whether your app meets the requirements for listing on {% data variables.product.prodname_marketplace %} as a free or a paid app. For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." -#### Verified Apps +1. Read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." -If you've already built an app and you're interested in submitting a verified listing in {% data variables.product.prodname_marketplace %}, start here: +1. Submit your listing for publication in {% data variables.product.prodname_marketplace %}, requesting verification if you want to sell the app. For more information, see "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication)." -1. [Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)
      Learn about requirements, guidelines, and the app submission process. +An onboarding expert will contact you with any questions or further steps. For example, if you have added a paid plan, you will need to complete the verification process and complete financial onboarding. As soon as your listing is approved the app is published to {% data variables.product.prodname_marketplace %}. -1. [Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)
      Before you can list your app on {% data variables.product.prodname_marketplace %}, you'll need to integrate billing flows using the {% data variables.product.prodname_marketplace %} API and webhook events. +### Seeing how your app is performing -1. [Listing on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)
      Create a draft {% data variables.product.prodname_marketplace %} listing, configure webhook settings, and set up pricing plans. +You can access metrics and transactions for your listing. 更多信息请参阅： -1. [Selling your app](/marketplace/selling-your-app/)
      Learn about pricing plans, billing cycles, and how to receive payment from {% data variables.product.prodname_dotcom %} for your app. - -1. [{% data variables.product.prodname_marketplace %} Insights](/marketplace/github-marketplace-insights/)
      See how your app is performing in {% data variables.product.prodname_marketplace %}. You can use metrics collected by {% data variables.product.prodname_dotcom %} to guide your marketing campaign and be successful in {% data variables.product.prodname_marketplace %}. - -1. [{% data variables.product.prodname_marketplace %} transactions](/marketplace/github-marketplace-transactions/)
      Download and view transaction data for your {% data variables.product.prodname_marketplace %} listing. - -### Reviewing your app - -We want to make sure that the apps offered on {% data variables.product.prodname_marketplace %} are safe, secure, and well tested. The {% data variables.product.prodname_marketplace %} onboarding specialists will review your app to ensure that it meets all requirements. Follow the guidelines in these articles before submitting your app: - - -* [Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) -* [Security review process](/marketplace/getting-started/security-review-process/) +- "[Viewing metrics for your listing](/developers/github-marketplace/viewing-metrics-for-your-listing)" +- "[Viewing transactions for your listing](/developers/github-marketplace/viewing-transactions-for-your-listing)" diff --git a/translations/zh-CN/content/developers/github-marketplace/about-verified-creators.md b/translations/zh-CN/content/developers/github-marketplace/about-verified-creators.md new file mode 100644 index 0000000000..f5141317c7 --- /dev/null +++ b/translations/zh-CN/content/developers/github-marketplace/about-verified-creators.md @@ -0,0 +1,43 @@ +--- +title: About verified creators +intro: 'Each organization that wants to sell apps on {% data variables.product.prodname_marketplace %} must follow a verification process. Their identity is checked and their billing process reviewed.' +versions: + free-pro-team: '*' +--- + +### About verified creators + +A verified creator is an organization that {% data variables.product.company_short %} has checked. Anyone can share their apps with other users on {% data variables.product.prodname_marketplace %} but only organizations that are verified by {% data variables.product.company_short %} can sell apps. For more information about organizations, see "[About organizations](/github/setting-up-and-managing-organizations-and-teams/about-organizations)." + +The verification process aims to protect users. For example, it verifies the seller's identity, checks that their {% data variables.product.product_name %} organization is set up securely, and that they can be contacted for support. + +After passing the verification checks, any apps that the organization lists on {% data variables.product.prodname_marketplace %} are shown with a verified creator badge {% octicon "verified" aria-label="Verified creator badge" %}. The organization can now add paid plans to any of their apps. Each app with a paid plan also goes through a financial onboarding process to check that it's set up to handle billing correctly. + +![verified creator badges](/assets/images/marketplace/marketplace_verified_creator_badges_apps.png) + +In addition to the verified creator badge, you'll also see badges for unverified and verified apps. These apps were published using the old method for verifying individual apps. + +![绿色的已验证和灰色的未验证徽章](/assets/images/marketplace/marketplace_verified_badges.png) + +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." + +### About the verification process + +The first time you request verification for a listing of one of your apps, you will enter the verification process. An onboarding expert will guide you through the process. This includes checking: + +- Profile information - The basic profile information is populated accurately and appropriately. +- Security - The organization has enabled two-factor authentication. +- Verified domain - The organization has verified the domain of the site URL. +- Purchase webhook event - The event is handled correctly by the app. + +When your organization is verified, all your apps are shown with a verified creator badge. You are now able to offer paid plans for any of your apps. + +For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何进行验证，请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)”。 + +{% note %} + +**Note:** This verification process for apps replaces the previous process where individual apps were verified. The current process is similar to the verification process for actions. If you have apps that were verified under the old process, these will not be affected by the changes. The {% data variables.product.prodname_marketplace %} team will contact you with details of how to migrate to organization-based verification. + +{% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/billing-customers.md b/translations/zh-CN/content/developers/github-marketplace/billing-customers.md index a3bffbc31b..47cfd0c030 100644 --- a/translations/zh-CN/content/developers/github-marketplace/billing-customers.md +++ b/translations/zh-CN/content/developers/github-marketplace/billing-customers.md @@ -1,6 +1,6 @@ --- -title: Billing customers -intro: 'Apps on {% data variables.product.prodname_marketplace %} should adhere to GitHub''s billing guidelines and support recommended services. Following our guidelines helps customers navigate the billing process without any surprises.' +title: 向客户计费 +intro: '{% data variables.product.prodname_marketplace %} 上的应用程序应遵守 GitHub 的计费指南并支持推荐的服务。 遵循我们的指南可帮助客户顺利完成帐单流程。' redirect_from: - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace/ - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace/ @@ -11,38 +11,38 @@ versions: -### Understanding the billing cycle +### 了解结算周期 -Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +客户在购买您的应用程序时可选择月度或年度结算周期、 客户对结算周期和计划选择所做的所有更改都将触发 `marketplace_purchase` 事件。 您可以参考 `marketplace_purchase` web 挂钩有效负载，以查看客户选择了哪个结算周期以及下一个计费日期 (`effective_date`) 何时开始 。 有关 web 挂钩有效负载的更多信息，请参阅“[{% data variables.product.prodname_marketplace %} API 的 web 挂钩事件](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)”。 -### Providing billing services in your app's UI +### 在应用程序 UI 中提供帐单服务 -Customers must be able to perform the following actions from your app's website: -- Customers must be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. +客户应该能够从您的应用程序网站执行以下操作： +- 客户应该能够单独修改或取消其个人和组织帐户的 {% data variables.product.prodname_marketplace %} 计划。 {% data reusables.marketplace.marketplace-billing-ui-requirements %} -### Billing services for upgrades, downgrades, and cancellations +### 升级、降级和取消的帐单服务 -Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)." +请遵循以下升级、降级和取消指南，以维护清晰一致的帐单流程。 有关 {% data variables.product.prodname_marketplace %} 购买事件的详细说明，请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 -You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). +您可以使用 `marketplace_purchase` web 挂钩的 `effective_date` 键来确定计划何时发生更改，并定期同步[列出计划的帐户](/rest/reference/apps#list-accounts-for-a-plan)。 #### 升级 -When a customer upgrades their pricing plan or changes their billing cycle from monthly to yearly, you should make the change effective for them immediately. You need to apply a pro-rated discount to the new plan and change the billing cycle. +当客户升级其定价计划或将其结算周期从每月更改为每年时，您应立即使更改对他们生效。 您需要对新计划应用按比例的折扣并更改结算周期。 {% data reusables.marketplace.marketplace-failed-purchase-event %} -For information about building upgrade and downgrade workflows into your app, see "[Upgrading and downgrading plans](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)." +有关为应用程序构建升级或降级工作流程的信息，请参阅“[处理计划更改](/developers/github-marketplace/handling-plan-changes)”。 -#### Downgrades and cancellations +#### 降级和取消 -Downgrades occur when a customer moves to a free plan from a paid plan, selects a plan with a lower cost than their current plan, or changes their billing cycle from yearly to monthly. When downgrades or cancellations occur, you don't need to provide a refund. Instead, the current plan will remain active until the last day of the current billing cycle. The `marketplace_purchase` event will be sent when the new plan takes effect at the beginning of the customer's next billing cycle. +当客户从付费计划转为免费计划、选择成本比其当前计划低的计划或将结算周期从每年更改为每月时，就会发生降级。 当降级或取消发生时，您不需要提供退款。 相反，当前计划将保持有效状态，直到当前结算周期的最后一天。 `marketplace-purpose` 事件将在客户的新计划生效，即下一个结算周期开始时发送。 -When a customer cancels a plan, you must: -- Automatically downgrade them to the free plan, if it exists. +当客户取消计划时，您必须： +- 自动降级到免费计划（如果有）。 {% data reusables.marketplace.cancellation-clarification %} -- Enable them to upgrade the plan through GitHub if they would like to continue the plan at a later time. +- 让他们能够通过 GitHub 升级计划（如果他们以后想要继续订阅计划）。 -For information about building cancellation workflows into your app, see "[Cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)." +有关为应用程序构建取消工作流程的信息，请参阅“[处理计划取消](/developers/github-marketplace/handling-plan-cancellations)”。 diff --git a/translations/zh-CN/content/developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/zh-CN/content/developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md index 300ab07e7c..6657d3ce0f 100644 --- a/translations/zh-CN/content/developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md +++ b/translations/zh-CN/content/developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md @@ -1,6 +1,6 @@ --- -title: Configuring a webhook to notify you of plan changes -intro: 'After [creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), you can configure a webhook that notifies you when changes to customer account plans occur. After you configure the webhook, you can [handle the `marketplace_purchase` event types](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) in your app.' +title: 配置 web 挂钩以通知您计划更改 +intro: '在[创建 {% data variables.product.prodname_marketplace %} 上架信息草稿](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) 后，您可以配置 web 挂钩，以便在客户帐户计划发生更改时通知您。 配置 web 挂钩后，您可以在应用程序中[处理 `marketplace_purchase` 事件类型](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)。' redirect_from: - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing/ - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing/ @@ -13,30 +13,30 @@ versions: -The {% data variables.product.prodname_marketplace %} event webhook can only be set up from your application's {% data variables.product.prodname_marketplace %} listing page. You can configure all other events from your [application's developer settings page](https://github.com/settings/developers). If you haven't created a {% data variables.product.prodname_marketplace %} listing, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how. +{% data variables.product.prodname_marketplace %} 事件 web 挂钩只能在应用程序的 {% data variables.product.prodname_marketplace %} 上架页面中进行设置。 您可以在[应用程序的开发者设置页面](https://github.com/settings/developers)中配置所有其他事件。 如果您尚未创建 {% data variables.product.prodname_marketplace %} 上架信息，请阅读“[创建 {% data variables.product.prodname_marketplace %} 上架信息](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)”了解方法。 -### Creating a webhook +### 创建 web 挂钩 -To create a webhook for your {% data variables.product.prodname_marketplace %} listing, click **Webhook** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). You'll see the following webhook configuration options needed to configure your webhook: +要为 {% data variables.product.prodname_marketplace %} 上架信息创建 web 挂钩，请在 [{% data variables.product.prodname_marketplace %} 上架页面](https://github.com/marketplace/manage)的左边栏中单击 **Webhook（web 挂钩）**。 您将看到配置 web 挂钩所需的以下 web 挂钩配置选项： -#### Payload URL +#### 有效负载 URL {% data reusables.webhooks.payload_url %} -#### Content type +#### 内容类型 -{% data reusables.webhooks.content_type %} GitHub recommends using the `application/json` content type. +{% data reusables.webhooks.content_type %} GitHub 建议使用 `application/json` 内容类型。 -#### Secret +#### 密钥 {% data reusables.webhooks.secret %} #### 已激活 -By default, webhook deliveries are "Active." You can choose to disable the delivery of webhook payloads during development by deselecting "Active." If you've disabled webhook deliveries, you will need to select "Active" before you submit your app for review. +默认情况下，web 挂钩交付为“Active（激活）”。 您可以通过取消选择“Active（激活）”来选择在开发过程中禁用 web 挂钩交付。 如果您禁用了 web 挂钩交付，则在提交应用程序以供审查之前需要选择“Active（激活）”。 -### Viewing webhook deliveries +### 查看 web 挂钩交付 -Once you've configured your {% data variables.product.prodname_marketplace %} webhook, you'll be able to inspect `POST` request payloads from the **Webhook** page of your application's [{% data variables.product.prodname_marketplace %} listing](https://github.com/marketplace/manage). GitHub 不会重新发送失败的递送尝试。 确保您的应用程序可以接收 GitHub 发送的所有 web 挂钩有效负载。 +配置 {% data variables.product.prodname_marketplace %} web 挂钩后，您可以在应用程序的 [{% data variables.product.prodname_marketplace %} 上架信息](https://github.com/marketplace/manage)的 **Webhook（web 挂钩）**页面中检查 `POST` 请求有效负载。 GitHub 不会重新发送失败的递送尝试。 确保您的应用程序可以接收 GitHub 发送的所有 web 挂钩有效负载。 -![Inspect recent {% data variables.product.prodname_marketplace %} webhook deliveries](/assets/images/marketplace/marketplace_webhook_deliveries.png) +![检查最近的 {% data variables.product.prodname_marketplace %} web 挂钩交付](/assets/images/marketplace/marketplace_webhook_deliveries.png) diff --git a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace.md b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace.md index 9252c41ece..6e9061cc66 100644 --- a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace.md +++ b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace.md @@ -1,6 +1,6 @@ --- title: Creating apps for GitHub Marketplace -intro: 'You can list free and paid tools for developers to use in {% data variables.product.prodname_marketplace %}.' +intro: '您可以在 {% data variables.product.prodname_marketplace %} 中上架免费和付费的工具，供开发者使用。' mapTopic: true versions: free-pro-team: '*' diff --git a/translations/zh-CN/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md b/translations/zh-CN/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md new file mode 100644 index 0000000000..4107fa4427 --- /dev/null +++ b/translations/zh-CN/content/developers/github-marketplace/customer-experience-best-practices-for-apps.md @@ -0,0 +1,20 @@ +--- +title: Customer experience best practices for apps +intro: 'Guidelines for creating an app that will be easy to use and understand.' +shortTitle: Customer experience best practice +versions: + free-pro-team: '*' +--- + +If you follow these best practices it will help you to provide a good customer experience. + +### Customer communication + +- Marketing materials for the app should accurately represent the app's behavior. +- Apps should include links to user-facing documentation that describe how to set up and use the app. +- Customers should be able to see what type of plan they have in the billing, profile, or account settings section of the app. +- Customers should be able to install and use your app on both a personal account and an organization account. They should be able to view and manage the app on those accounts separately. + +### Plan management + +{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/zh-CN/content/developers/github-marketplace/drafting-a-listing-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/drafting-a-listing-for-your-app.md index 7bc6b6e542..d8fc7aacee 100644 --- a/translations/zh-CN/content/developers/github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/drafting-a-listing-for-your-app.md @@ -1,6 +1,6 @@ --- -title: Drafting a listing for your app -intro: 'When you create a {% data variables.product.prodname_marketplace %} listing, GitHub saves it in draft mode until you submit the app for approval. Your listing shows customers how they can use your app.' +title: 起草应用程序上架信息 +intro: '当您创建 {% data variables.product.prodname_marketplace %} 上架信息时，GitHub 将其保存为草稿模式，直到您提交应用程序以供审批。 您的上架信息向客户显示如何使用您的应用程序。' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/ @@ -18,50 +18,50 @@ versions: -### Create a new draft {% data variables.product.prodname_marketplace %} listing +### 创建新的 {% data variables.product.prodname_marketplace %} 上架信息草稿 -You can only create draft listings for apps that are public. Before creating your draft listing, you can read the following guidelines for writing and configuring settings in your {% data variables.product.prodname_marketplace %} listing: +您只能为公共应用程序创建上架信息草稿。 在创建上架信息草稿之前，请阅读以下有关在 {% data variables.product.prodname_marketplace %} 上架信息中编写和配置设置的指南： -* [Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/) -* [Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/) -* [Configuring the {% data variables.product.prodname_marketplace %} Webhook](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/) +* [编写 {% data variables.product.prodname_marketplace %} 上架产品说明](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/) +* [设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/) +* [配置 {% data variables.product.prodname_marketplace %} web 挂钩](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/) -To create a {% data variables.product.prodname_marketplace %} listing: +要创建 {% data variables.product.prodname_marketplace %} 上架信息： {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} -3. In the left sidebar, click either **OAuth Apps** or **GitHub Apps** depending on the app you're adding to {% data variables.product.prodname_marketplace %}. +3. 在左边栏中，单击 **OAuth Apps（OAuth 应用程序）**或 **GitHub Apps（GitHub 应用程序）**，具体取决于您要添加到 {% data variables.product.prodname_marketplace %} 的应用程序。 {% note %} - **Note**: You can also add a listing by navigating to https://github.com/marketplace/new, viewing your available apps, and clicking **Create draft listing**. + **注**：您也可以通过以下方法添加上架信息：导航到 https://github.com/marketplace/new，查看可用的应用程序，然后单击 **Create draft listing（创建上架信息草稿）**。 {% endnote %} - ![App type selection](/assets/images/settings/apps_choose_app.png) + ![应用程序类型选择](/assets/images/settings/apps_choose_app.png) -4. Select the app you'd like to add to +4. 选择要添加到的应用程序 {% data variables.product.prodname_marketplace %}. -![App selection for {% data variables.product.prodname_marketplace %} listing](/assets/images/github-apps/github_apps_select-app.png) +![选择在 {% data variables.product.prodname_marketplace %} 中上架的应用程序](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.edit_marketplace_listing %} -5. Once you've created a new draft listing, you'll see an overview of the sections that you'll need to visit before your {% data variables.product.prodname_marketplace %} listing will be complete. ![GitHub Marketplace listing](/assets/images/marketplace/marketplace_listing_overview.png) +5. 创建新的上架草稿后，您将看到在完成 {% data variables.product.prodname_marketplace %} 上架信息之前需要访问的部分的概览。 ![GitHub Marketplace 上架信息](/assets/images/marketplace/marketplace_listing_overview.png) {% note %} -**Note:** In the "Contact info" section of your listing, we recommend using individual email addresses, rather than group emails addresses like support@domain.com. GitHub will use these email addresses to contact you about updates to {% data variables.product.prodname_marketplace %} that might affect your listing, new feature releases, marketing opportunities, payouts, and information on conferences and sponsorships. +**注：**在上架信息的“联系信息”部分，我们建议您使用个人电子邮件地址，而不是像 support@domain.com 这样的团体电子邮件地址。 GitHub 将使用这些电子邮件地址与您联系，以告知可能影响您的上架产品的 {% data variables.product.prodname_marketplace %} 更新、新功能发布、营销机会、付款以及会议和赞助信息。 {% endnote %} -### Editing your listing +### 编辑您的上架信息 -Once you've created a {% data variables.product.prodname_marketplace %} draft listing, you can come back to modify information in your listing anytime. If your app is already approved and in {% data variables.product.prodname_marketplace %}, you can edit the information and images in your listing, but you will not be able to change existing published pricing plans. See "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." +创建 {% data variables.product.prodname_marketplace %} 上架信息草稿后，您可以随时回来修改上架信息。 如果您的应用程序已获批准并且在 {% data variables.product.prodname_marketplace %} 中，您可以编辑上架产品的信息和图像，但无法更改现有的已发布定价计划。 请参阅“[设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)”。 -### Submitting your app +### 提交应用程序 -Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, the {% data variables.product.prodname_marketplace %} onboarding team will contact you with additional information about the onboarding process. You can learn more about the onboarding and security review process in "[Getting started with {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)." +完成 {% data variables.product.prodname_marketplace %} 上架信息后，您可以在 **Overview（概览）**页面中提交您的上架信息以供审查。 您需要阅读并接收“[{% data variables.product.prodname_marketplace %} 开发者协议](/articles/github-marketplace-developer-agreement/)”，然后才可以单击 **Submit for review（提交审查）**。 提交应用程序以供审查后，上架专家将与您联系，提供有关上架流程的其他信息。 有关上架和安全审查流程的更多信息，请参阅“[{% data variables.product.prodname_marketplace %} 入门指南](/marketplace/getting-started/)”。 -### Removing a {% data variables.product.prodname_marketplace %} listing +### 删除 {% data variables.product.prodname_marketplace %} 上架信息 -If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact [marketplace@github.com](mailto:marketplace@github.com) to remove your listing. +如果您不想再在 {% data variables.product.prodname_marketplace %} 中上架应用程序，请联系 {% data variables.contact.contact_support %} 删除您的上架信息。 diff --git a/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md b/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md index 13c59a79b6..0f495b88fc 100644 --- a/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md +++ b/translations/zh-CN/content/developers/github-marketplace/handling-new-purchases-and-free-trials.md @@ -1,6 +1,6 @@ --- -title: Handling new purchases and free trials -intro: 'When a customer purchases a paid plan, free trial, or the free version of your {% data variables.product.prodname_marketplace %} app, you''ll receive the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhook with the `purchased` action, which kicks off the purchasing flow.' +title: 处理新购买和免费试用 +intro: '当客户购买您的 {% data variables.product.prodname_marketplace %} 应用程序的付费计划、免费试用版或免费版本时，您将收到 [`marketplace_purchase` 事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) web 挂钩，挂钩中带有可启动购买流程的 `purchased` 操作。' redirect_from: - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps/ - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps/ @@ -14,68 +14,68 @@ versions: {% warning %} -If you offer a GitHub App in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate OAuth App to support this flow. 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 +如果在 {% data variables.product.prodname_marketplace %} 中提供 GitHub 应用程序，您的应用程序必须按照 OAuth 授权流程来识别用户。 您不需要设置单独的 OAuth 应用程序来支持此流程。 更多信息请参阅“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 {% endwarning %} -### 步骤 1. Initial purchase and webhook event +### 步骤 1. 首次购买和 web 挂钩事件 -Before a customer purchases your {% data variables.product.prodname_marketplace %} app, they select a [listing plan](/marketplace/selling-your-app/github-marketplace-pricing-plans/). They also choose whether to purchase the app from their personal account or an organization account. +客户在购买 {% data variables.product.prodname_marketplace %} 应用程序之前，需要选择[上架产品计划](/marketplace/selling-your-app/github-marketplace-pricing-plans/)。 他们还要选择是从个人帐户还是从组织帐户购买应用程序。 -The customer completes the purchase by clicking **Complete order and begin installation**. +客户通过单击 **Complete order and begin installation（完成订单并开始安装）**来完成购买。 -GitHub then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. +然后，GitHub 将带有 `purchased` 操作的 [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) web 挂钩发送到您的应用程序。 -Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins. +从 `marketplace_purchase` web 挂钩读取 `effective_date` 和 `marketplace_purchase` 对象，以确定客户购买了哪个计划、何时开始结算周期以及何时开始下一个结算周期。 -If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)." See "[Upgrading and downgrading plans](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)" to find out how to transition a free trial to a paid plan when a free trial expires. +如果您的应用程序提供免费试用版，则从 web 挂钩读取 `marketplace_purchase[on_free_trial]` 属性。 如果该值为 `true`，则应用程序需要跟踪免费试用开始日期 (`effective_date`) 和免费试用结束日期 (`free_trial_ends_on`)。 使用 `free_trial_ends_on` 日期在应用程序的 UI 中显示免费试用剩余天数。 您可以在横幅或[帐单 UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui) 中显示它。 要了解如何在免费试用结束前处理取消，请参阅“[处理计划取消](/developers/github-marketplace/handling-plan-cancellations)”。 请参阅“[处理计划更改](/developers/github-marketplace/handling-plan-changes)”，了解在免费试用期满后如何从免费试用版过渡到付费计划。 -See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload. +有关 `marketplace_purchase` 事件有效负载的示例，请参阅“[{% data variables.product.prodname_marketplace %} web 挂钩事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)”。 ### 步骤 2. 安装 -If your app is a GitHub App, GitHub prompts the customer to select which repositories the app can access when they purchase it. GitHub then installs the app on the account the customer selected and grants access to the selected repositories. +如果您的应用程序是 GitHub 应用程序，GitHub 会在客户购买时提示客户选择应用程序可以访问的仓库。 然后，GitHub 将应用程序安装在客户选择的帐户上，并授予对所选仓库的访问权限。 -At this point, if you specified a **Setup URL** in your GitHub App settings, Github will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your GitHub App. +如果您在 GitHub 应用程序设置中指定了**设置 URL**，此时 GitHub 会将客户重定向到该 URL。 如果未指定设置 URL，您将无法处理 GitHub 应用程序的购买。 {% note %} -**Note:** The **Setup URL** is described as optional in GitHub App settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. +**注：****设置 URL** 在 GitHub 应用程序设置中被描述为可选项，但如果您要在 {% data variables.product.prodname_marketplace %} 中提供应用程序，则它为必填字段。 {% endnote %} -If your app is an OAuth App, GitHub does not install it anywhere. Instead, GitHub redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). +如果您的应用程序是 OAuth 应用程序，GitHub 不会在任何地方安装它。 GitHub 会将客户重定向到您在 [{% data variables.product.prodname_marketplace %} 上架信息](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls)中指定的**安装 URL**。 -When a customer purchases an OAuth App, GitHub redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. +当客户购买 OAuth 应用程序时，GitHub 会将客户重定向到您选择的 URL（设置 URL 或安装 URL），并且该 URL 将客户选择的定价计划包含为查询参数：`marketplace_listing_plan_id`。 ### 步骤 3. 授权 -When a customer purchases your app, you must send the customer through the OAuth authorization flow: +当客户购买您的应用程序时，您必须通过 OAuth 授权流程发送客户： -* If your app is a GitHub App, begin the authorization flow as soon as GitHub redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." +* 如果您的应用程序是 GitHub 应用程序，则在 GitHub 将客户重定向到**设置 URL** 时开始授权流程。 请遵循“[识别和授权 GitHub 应用程序用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”中的步骤。 -* If your app is an OAuth App, begin the authorization flow as soon as GitHub redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/)." +* 如果您的应用程序是 OAuth 应用程序，则在 GitHub 将客户重定向到**安装 URL** 时开始授权流程。 请遵循“[授权 OAuth 应用程序](/apps/building-oauth-apps/authorizing-oauth-apps/)”中的步骤。 -For either type of app, the first step is to redirect the customer to https://github.com/login/oauth/authorize. +对于任一类型的应用程序，第一步都是将客户重定向到 https://github.com/login/oauth/authorize。 -After the customer completes the authorization, your app receives an OAuth access token for the customer. You'll need this token for the next step. +客户完成授权后，您的应用程序将收到客户的 OAuth 访问令牌。 下一步将需要使用此令牌。 {% note %} -**Note:** When authorizing a customer on a free trial, grant them the same access they would have on the paid plan. You'll move them to the paid plan after the trial period ends. +**注：**授权客户免费试用时，请授予他们与付费计划相同的访问权限。 试用期结束后，将其移至付费计划。 {% endnote %} -### 步骤 4. Provisioning customer accounts +### 步骤 4. 预配客户帐户 -Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. +您的应用程序必须为所有新购买预配客户帐户。 使用在[步骤 3. 授权](#step-3-authorization)中收到的客户访问令牌，调用“[列出经验证用户的订阅](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)”端点。 响应将包括客户的 `account` 信息，并显示他们是否在使用免费试用版 (`on_free_trial`)。 使用此信息完成设置和预配。 {% data reusables.marketplace.marketplace-double-purchases %} -If the purchase is for an organization and per-user, you can prompt the customer to choose which organization members will have access to the purchased app. +如果客户是为组织按用户购买应用程序，您可以提示客户选择哪些组织成员将有权访问所购买的应用程序。 -You can customize the way that organization members receive access to your app. Here are a few suggestions: +您可以自定义组织成员获取应用程序访问权限的方式。 以下是一些建议： -**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/rest/reference/orgs#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. +**统一定价：**如果客户是使用统一定价为组织购买应用程序，您的应用程序可以通过 API [获取组织的所有成员](/rest/reference/orgs#list-organization-members)，并提示组织管理员选择哪些成员作为集成者一方的付费用户。 -**Per-unit pricing:** One method of provisioning per-unit seats is to allow users to occupy a seat as they log in to the app. Once the customer hits the seat count threshold, your app can alert the user that they need to upgrade through {% data variables.product.prodname_marketplace %}. +**每单位定价：**一种预配每单位席位的方法，允许用户在登录应用程序时占用一个席位。 一旦客户达到席位数阈值，您的应用程序就可以提醒用户他们需要通过 {% data variables.product.prodname_marketplace %} 进行升级。 diff --git a/translations/zh-CN/content/developers/github-marketplace/handling-plan-cancellations.md b/translations/zh-CN/content/developers/github-marketplace/handling-plan-cancellations.md index 0237b09988..49fc0e14e1 100644 --- a/translations/zh-CN/content/developers/github-marketplace/handling-plan-cancellations.md +++ b/translations/zh-CN/content/developers/github-marketplace/handling-plan-cancellations.md @@ -1,6 +1,6 @@ --- -title: Handling plan cancellations -intro: 'Cancelling a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhook with the `cancelled` action, which kicks off the cancellation flow.' +title: 处理计划取消 +intro: '取消 {% data variables.product.prodname_marketplace %} 应用程序将触发 [`marketplace_purchase` 事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) web 挂钩，挂钩中带有可启动取消流程的 `cancelled` 操作。' redirect_from: - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans/ - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/ @@ -11,23 +11,23 @@ versions: -For more information about cancelling as it relates to billing, see "[Billing customers in {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)." +有关与计费相关之取消的更多信息，请参阅“[在 {% data variables.product.prodname_marketplace %} 中向客户计费](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)”。 -### 步骤 1. Cancellation event +### 步骤 1. 取消事件 -If a customer chooses to cancel a {% data variables.product.prodname_marketplace %} order, GitHub sends a [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the action `cancelled` to your app when the cancellation takes effect. If the customer cancels during a free trial, your app will receive the event immediately. When a customer cancels a paid plan, the cancellation will occur at the end of the customer's billing cycle. +如果客户选择取消 {% data variables.product.prodname_marketplace %}，则在取消生效时，GitHub 会向您的应用程序发送带有操作 `cancelled` 的 [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) web 挂钩。 如果客户在免费试用期间取消，您的应用程序将立即收到此事件。 如果客户取消付费计划，则取消将在客户结算周期结束时生效。 -### 步骤 2. Deactivating customer accounts +### 步骤 2. 停用客户帐户 -When a customer cancels a free or paid plan, your app must perform these steps to complete cancellation: +当客户取消免费或付费计划时，您的应用程序必须执行以下步骤才能完成取消： -1. Deactivate the account of the customer who cancelled their plan. -1. Revoke the OAuth token your app received for the customer. -1. If your app is an OAuth App, remove all webhooks your app created for repositories. -1. Remove all customer data within 30 days of receiving the `cancelled` event. +1. 停用取消计划的客户的帐户。 +1. 撤消您的应用程序为客户接收的 OAuth 令牌。 +1. 如果您的应用程序是 OAuth 应用程序，则删除应用程序为仓库创建的所有 web 挂钩。 +1. 在收到 `cancelled` 事件后的 30 天内删除所有客户数据。 {% note %} -**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." +**注：**我们建议使用 [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) web 挂钩的 `effective_date` 来确定计划更改何时生效，并定期同步[列出计划的帐户](/rest/reference/apps#list-accounts-for-a-plan)。 有关 web 挂钩的更多信息，请参阅“[{% data variables.product.prodname_marketplace %} web 挂钩事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)”。 {% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/handling-plan-changes.md b/translations/zh-CN/content/developers/github-marketplace/handling-plan-changes.md index 89841d8db0..a123910af5 100644 --- a/translations/zh-CN/content/developers/github-marketplace/handling-plan-changes.md +++ b/translations/zh-CN/content/developers/github-marketplace/handling-plan-changes.md @@ -1,6 +1,6 @@ --- -title: Handling plan changes -intro: 'Upgrading or downgrading a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the `changed` action, which kicks off the upgrade or downgrade flow.' +title: 处理计划更改 +intro: '升级或降级 {% data variables.product.prodname_marketplace %} 应用程序将触发 [`marketplace_purchase` 事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) web 挂钩，挂钩中带有可启动升级或降级流程的 `changed` 操作。' redirect_from: - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans/ - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/ @@ -11,54 +11,54 @@ versions: -For more information about upgrading and downgrading as it relates to billing, see "[Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)." +有关与计费相关之升级和降级的更多信息，请参阅“[与 {% data variables.product.prodname_marketplace %} API 集成](/marketplace/integrating-with-the-github-marketplace-api/)”。 -### 步骤 1. Pricing plan change event +### 步骤 1. 定价计划更改事件 -GitHub send the `marketplace_purchase` webhook with the `changed` action to your app, when a customer makes any of these changes to their {% data variables.product.prodname_marketplace %} order: -* Upgrades to a more expensive pricing plan or downgrades to a lower priced plan. -* Adds or removes seats to their existing plan. -* Changes the billing cycle. +当客户对其 {% data variables.product.prodname_marketplace %} 订单进行以下任何更改时，GitHub 会将带有 `changed` 操作的 `marketplace_purchase` web 挂钩发送到您的应用程序： +* 升级到更昂贵的定价计划或降级到价格较低的计划。 +* 在其现有计划中增加或删除席位。 +* 更改结算周期。 -GitHub will send the webhook when the change takes effect. For example, when a customer downgrades a plan, GitHub sends the webhook at the end of the customer's billing cycle. GitHub sends a webhook to your app immediately when a customer upgrades their plan to allow them access to the new service right away. If a customer switches from a monthly to a yearly billing cycle, it's considered an upgrade. See "[Billing customers in {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" to learn more about what actions are considered an upgrade or downgrade. +更改生效时，GitHub 将发送 web 挂钩。 例如，当客户降级计划时，GitHub 会在客户的结算周期结束时发送 web 挂钩。 当客户升级其计划以便立即访问新服务时，GitHub 会立即向您的应用程序发送 web 挂钩。 如果客户从月度结算周期切换到年度结算周期，则视为升级。 有关哪些操作被视为升级或降级，请参阅“[在 {% data variables.product.prodname_marketplace %} 中向客户计费](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)”。 -Read the `effective_date`, `marketplace_purchase`, and `previous_marketplace_purchase` from the `marketplace_purchase` webhook to update the plan's start date and make changes to the customer's billing cycle and pricing plan. See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload. +从 `marketplace_purchase` web 挂钩读取 `effective_date`、`marketplace_purchase` 和 `previous_marketplace_purchase`，以更新计划的开始日期，并更改客户的结算周期和定价计划。 有关 `marketplace_purchase` 事件有效负载的示例，请参阅“[{% data variables.product.prodname_marketplace %} web 挂钩事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)”。 -If your app offers free trials, you'll receive the `marketplace_purchase` webhook with the `changed` action when the free trial expires. If the customer's free trial expires, upgrade the customer to the paid version of the free-trial plan. +如果您的应用程序提供免费试用，则在免费试用到期时您将收到带有 `changed` 操作的 `marketplace_purchase` web 挂钩。 如果客户的免费试用到期，则将客户升级到免费试用计划的付费版本。 -### 步骤 2. Updating customer accounts +### 步骤 2. 更新客户账户 -You'll need to update the customer's account information to reflect the billing cycle and pricing plan changes the customer made to their {% data variables.product.prodname_marketplace %} order. Display upgrades to the pricing plan, `seat_count` (for per-unit pricing plans), and billing cycle on your Marketplace app's website or your app's UI when you receive the `changed` action webhook. +您需要更新客户的帐户信息，以反映客户对其 {% data variables.product.prodname_marketplace %} 订单所做的结算周期和定价计划更改。 当您收到 `changed` 操作 web 挂钩时，您的 Marketplace 应用程序的网站或应用程序的 UI 上会显示定价计划、`seat_count`（对于每单位定价计划）和结算周期的升级。 -When a customer downgrades a plan, it's recommended to review whether a customer has exceeded their plan limits and engage with them directly in your UI or by reaching out to them by phone or email. +当客户降级计划时，建议查看客户是否超出了计划限制，然后直接在您的 UI 中与他们互动，或者通过电话或电子邮件与他们联系。 -To encourage people to upgrade you can display an upgrade URL in your app's UI. See "[About upgrade URLs](#about-upgrade-urls)" for more details. +要鼓励用户升级，您可以在应用程序的 UI 中显示升级 URL。 更多信息请参阅“[关于升级 URL](#about-upgrade-urls)”。 {% note %} -**Note:** We recommend performing a periodic synchronization using `GET /marketplace_listing/plans/:id/accounts` to ensure your app has the correct plan, billing cycle information, and unit count (for per-unit pricing) for each account. +**注：**建议您使用 `GET /marketplace_listing/plans/:id/accounts` 进行定期同步，以确保您的应用程序具有每个帐户的正确计划、结算周期信息和单位计数（对于每单位定价）。 {% endnote %} -### Failed upgrade payments +### 升级付款失败 {% data reusables.marketplace.marketplace-failed-purchase-event %} -### About upgrade URLs +### 关于升级 URL -You can redirect users from your app's UI to upgrade on GitHub using an upgrade URL: +您可以使用升级 URL 将用户从应用程序的 UI 重定向到 GitHub 上的升级页面： ``` https://www.github.com/marketplace//upgrade// ``` -For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page. +例如，如果您发现某个客户需要从 5 人计划转换到 10 人计划，您可以在应用程序 UI 中显示一个“升级指南”按钮，或者显示包含升级 URL 链接的横幅。 升级 URL 可将客户带到您的上架产品计划的升级确认页面。 -Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. +对客户想要购买的计划使用 `LISTING_PLAN_NUMBER`。 当您创建新的定价计划时，他们会收到 `LISTING_PLAN_NUMBER`（对于您的上架产品中每个计划而言是唯一的）和 `LISTING_PLAN_ID`（对于 {% data variables.product.prodname_marketplace %} 中每个计划而言是唯一的）。 当您[列出计划](/rest/reference/apps#list-plans)时，可以找到这些编号，它们用于标识上架产品的定价计划。 使用 `LISTING_PLAN_ID` 和“[列出计划的帐户](/rest/reference/apps#list-accounts-for-a-plan)”端点获取 `CUSTOMER_ACCOUNT_ID`。 {% note %} -**Note:** If your customer upgrades to additional units (such as seats), you can still send them to the appropriate plan for their purchase, but we are unable to support `unit_count` parameters at this time. +**注：**如果您的客户升级到更多单位（例如席位），您仍然可以将他们送到适合其购买的计划中，但我们目前无法支持 `unit_count` 参数。 {% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/index.md b/translations/zh-CN/content/developers/github-marketplace/index.md index 34b9741c61..d31b78bf1e 100644 --- a/translations/zh-CN/content/developers/github-marketplace/index.md +++ b/translations/zh-CN/content/developers/github-marketplace/index.md @@ -1,6 +1,6 @@ --- title: GitHub Marketplace -intro: 'List your tools in {% data variables.product.prodname_dotcom %} Marketplace for developers to use or purchase.' +intro: '在 {% data variables.product.prodname_dotcom %} Marketplace 中上架您的工具，供开发者使用或购买。' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace/ - /apps/marketplace/ @@ -11,8 +11,10 @@ versions: {% topic_link_in_list /creating-apps-for-github-marketplace %} {% link_in_list /about-github-marketplace %} + {% link_in_list /about-verified-creators %} {% link_in_list /requirements-for-listing-an-app %} - {% link_in_list /security-review-process-for-submitted-apps %} + {% link_in_list /security-best-practices-for-apps %} + {% link_in_list /customer-experience-best-practices-for-apps %} {% link_in_list /viewing-metrics-for-your-listing %} {% link_in_list /viewing-transactions-for-your-listing %} {% topic_link_in_list /using-the-github-marketplace-api-in-your-app %} @@ -27,7 +29,7 @@ versions: {% link_in_list /writing-a-listing-description-for-your-app %} {% link_in_list /setting-pricing-plans-for-your-listing %} {% link_in_list /configuring-a-webhook-to-notify-you-of-plan-changes %} - {% link_in_list /submitting-your-listing-for-review %} + {% link_in_list /submitting-your-listing-for-publication %} {% topic_link_in_list /selling-your-app-on-github-marketplace %} {% link_in_list /pricing-plans-for-github-marketplace-apps %} {% link_in_list /billing-customers %} diff --git a/translations/zh-CN/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/zh-CN/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md index bb33fe004f..7ac1291fd0 100644 --- a/translations/zh-CN/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/zh-CN/content/developers/github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -1,6 +1,6 @@ --- -title: Pricing plans for GitHub Marketplace apps -intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.' +title: GitHub Marketplace 应用程序的定价计划 +intro: '定价计划允许您为应用程序提供不同级别的服务或资源。 您可以在 {% data variables.product.prodname_marketplace %} 上架信息中提供最多 10 个定价计划。' redirect_from: - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans/ - /marketplace/selling-your-app/github-marketplace-pricing-plans @@ -10,38 +10,48 @@ versions: -{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit, and GitHub lists the price in US dollars. Customers purchase your app using a payment method attached to their {% data variables.product.product_name %} account, without having to leave GitHub.com. You don't have to write code to perform billing transactions, but you will have to handle [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) for purchase events. +{% data variables.product.prodname_marketplace %} 定价计划可以是免费、统一定价或每单位定价。 价格以美元设置、显示和处理。 付费计划仅限于已验证的上架产品。 -If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed. +客户使用附加到其 {% data variables.product.product_name %} 帐户的付款方式购买您的应用程序，而不必离开 {% data variables.product.prodname_dotcom_the_website %}。 您不必编写代码来执行结算交易，但必须处理来自 {% data variables.product.prodname_marketplace %} API 的事件。 更多信息请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 -For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." +如果您在 {% data variables.product.prodname_marketplace %} 中上架的应用程序有多个计划选项，您可以设置相应的定价计划。 例如，如果您的应用程序有两个计划选项：开源计划和专业计划，您可以为开源计划设置一个免费定价计划，为专业计划设置一个统一定价计划。 每个 {% data variables.product.prodname_marketplace %} 上架产品必须为列出的每个计划提供年度和月度价格。 + +有关如何创建定价计划的更多信息，请参阅“[设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)”。 + +{% data reusables.marketplace.free-plan-note %} + +### 定价计划的类型 + +#### 免费定价计划 + +{% data reusables.marketplace.free-apps-encouraged %} + +免费计划对用户完全免费。 如果您设置免费定价计划，则无法向选择免费定价计划的用户收取使用应用程序的费用。 您可以为上架产品同时创建免费和付费计划。 + +所有应用程序都需要处理新购买和取消事件。 仅含免费计划的应用程序无需处理免费试用、升级和降级事件。 更多信息请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 + +如果您向已作为免费服务在 {% data variables.product.prodname_marketplace %} 中上架的应用程序添加付费计划，则需要请求验证应用程序并完成财务手续。 + +#### 付费定价计划 + +有两种类型的付费定价计划： + +- 统一定价计划按月和按年收取固定费用。 + +- 每单位定价计划按月或按年向您指定的单位收取固定费用。 “单位”可以是您愿意指定的任何对象（例如用户、席位或人员）。 + +您可能还希望提供免费试用。 这些选项为客户提供为期 14 天免费试用 OAuth 或 GitHub 应用程序的机会。 设置 Marketplace 定价计划时，您可以选择为统一定价或每单位定价计划提供免费试用选项。 + +### 免费试用 + +客户可以免费试用 Marketplace 上架产品中包含免费试用选项的任何付费计划。 但是，客户不能对一个 Marketplace 产品使用多次免费试用机会。 + +免费试用的固定期限为 14 天。 客户在试用期结束前 4 天（免费试用期第 11 天）收到通知，他们的计划将升级。 在免费试用结束时，如果客户不取消，他们将自动注册到他们正在试用的计划中。 + +更多信息请参阅“[处理新购买和免费试用](/developers/github-marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)”。 {% note %} -**Note:** If you're listing an app on {% data variables.product.prodname_marketplace %}, you can't list your app with a free pricing plan if you offer a paid service outside of {% data variables.product.prodname_marketplace %}. - -{% endnote %} - -### Types of pricing plans - -**Free pricing plans** are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. Unverified free apps do not need to implement any billing flows. Free apps that are verified by Github need to implement billing flows for new purchases and cancellations, but do not need to implement billing flows for free trials, upgrades, and downgrades. If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to resubmit the app for review. - -**Flat rate pricing plans** charge a set fee on a monthly and yearly basis. - -**Per-unit pricing plans** charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). - -**Marketplace free trials** provide 14-day free trials of OAuth or GitHub Apps to customers. When you [set up a Marketplace pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/), you can select the option to provide a free trial for flat-rate or per-unit pricing plans. - -### Free trials - -Customers can start a free trial for any available paid plan on a Marketplace listing, but will not be able to create more than one free trial for a Marketplace product. - -Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel. - -See "[New purchases and free trials](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for details on how to handle free trials in your app. - -{% note %} - -**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event. +**注：**GitHub 希望您在取消试用后 30 天（从收到取消事件开始算起）内删除任何私人客户数据。 。 {% endnote %} diff --git a/translations/zh-CN/content/developers/github-marketplace/requirements-for-listing-an-app.md b/translations/zh-CN/content/developers/github-marketplace/requirements-for-listing-an-app.md index cb3cbe9336..750bf5b37b 100644 --- a/translations/zh-CN/content/developers/github-marketplace/requirements-for-listing-an-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- -title: Requirements for listing an app -intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before our {% data variables.product.prodname_marketplace %} onboarding specialists will approve the listing.' +title: 上架应用程序的要求 +intro: '{% data variables.product.prodname_marketplace %} 上的应用程序必须满足本页列出的要求才能发布上架。' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ @@ -12,49 +12,62 @@ versions: free-pro-team: '*' --- + +在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求取决于您是要提供免费应用程序还是付费应用程序。 -Before you submit your app for review, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/articles/github-marketplace-developer-agreement/)." You'll accept the terms within your [draft listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) on {% data variables.product.product_name %}. Once you've submitted your app, one of the {% data variables.product.prodname_marketplace %} onboarding specialists will reach out to you with more information about the onboarding process, and review your app to ensure it meets these requirements: +### 对所有 {% data variables.product.prodname_marketplace %} 上架产品的要求 -### User experience +{% data variables.product.prodname_marketplace %} 中的所有上架产品应该是能够为 {% data variables.product.product_name %} 社区提供价值的工具。 提交要发布的上架信息时，您必须阅读并接受“[{% data variables.product.prodname_marketplace %} 开发者协议](/articles/github-marketplace-developer-agreement/)”的条款。 -- {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations. -- {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users. -- Apps must provide value to customers and integrate with the platform in some way beyond authentication. -- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only. -- Apps cannot actively persuade users away from {% data variables.product.product_name %}. -- Marketing materials for the app must accurately represent the app's behavior. -- Apps must include links to user-facing documentation that describe how to set up and use the app. -- When a customer purchases an app and GitHub redirects them to the app's installation URL, the app must begin the OAuth flow immediately. For details, see "[Handling new purchases and free trials](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/#step-3-authorization)." +#### 所有应用程序的用户体验要求 -- Customers must be able to install your app and select repositories on both a personal and organization account. They should be able to view and manage those accounts separately. +所有上架产品应满足以下要求，无论它们是免费应用程序还是付费应用程序。 -### Brand and listing +- 上架信息不得主动诱导用户离开 {% data variables.product.product_name %}。 +- 上架信息必须包含发布者的有效联系信息。 +- 上架信息必须包含应用程序的相关说明。 +- 上架信息必须指定定价计划。 +- 应用程序必须为客户提供价值，并通过身份验证以外的其他方式与平台集成。 +- 应用程序必须在 {% data variables.product.prodname_marketplace %} 中公开可用，并且不能是测试版或只能通过邀请获取。 +- 应用程序必须设置 web 挂钩事件，以便在发生计划更改或取消时通过 {% data variables.product.prodname_marketplace %} API 通知发布者。 更多信息请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 -- Apps that use GitHub logos must follow the "[{% data variables.product.product_name %} Logos and Usage](https://github.com/logos)" guidelines. -- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." -- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." +有关提供良好客户体验的更多信息，请参阅“[应用程序的客户体验最佳实践](/developers/github-marketplace/customer-experience-best-practices-for-apps)”。 -### 安全 +#### 所有应用程序的品牌和上架要求 -Apps will go through a security review before being listed on {% data variables.product.prodname_marketplace %}. A successful review will meet the requirements and follow the security best practices listed in "[Security review process](/marketplace/getting-started/security-review-process/)." For information on the review process, contact [marketplace@github.com](mailto:marketplace@github.com). +- 使用 GitHub 徽标的应用程序必须遵循 {% data variables.product.company_short %} 指南。 更多信息请参阅“[{% data variables.product.company_short %} 徽标和用法](https://github.com/logos)”。 +- 应用程序必须具有徽标、功能卡和屏幕截图，并且这些内容必须遵循“[编写 {% data variables.product.prodname_marketplace %} 上架说明](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)”中提供的建议。 +- 上架信息必须包含认真编写并且没有语法错误的说明。 有关编写上架信息的指南，请参阅“[编写 {% data variables.product.prodname_marketplace %} 上架说明](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)”。 -### Billing flows +为了保护您的客户，我们建议您还要遵循安全最佳实践。 更多信息请参阅“[应用程序的安全最佳实践](/developers/github-marketplace/security-best-practices-for-apps)”。 -Your app must integrate [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) using the [{% data variables.product.prodname_marketplace %} webhook event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). +### 免费应用程序注意事项 -#### Free apps +{% data reusables.marketplace.free-apps-encouraged %} -{% data reusables.marketplace.free-apps-encouraged %} If you are listing a free app, you'll need to meet these requirements: +### 付费应用程序的要求 -- Customers must be able to see that they have a free plan in the billing, profile, or account settings section of the app. -- When a customer cancels your app, you must follow the flow for [cancelling plans](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/). +除了上述对所有应用程序的要求之外，作为付费服务在 {% data variables.product.prodname_marketplace %} 上提供的每个应用程序还必须满足以下要求： -#### Paid apps +- {% data variables.product.prodname_github_app %} 应至少有 100 个安装设施。 +- {% data variables.product.prodname_oauth_app %} 应至少有 200 个用户。 +- 所有付费应用程序必须处理关于新购买、升级、降级、取消和免费试用的 {% data variables.product.prodname_marketplace %} 购买事件。 更多信息请参阅下面的“[付费应用程序的计费要求](#billing-requirements-for-paid-apps)”。 +- 发布组织必须具有经过验证的域，并且必须启用双重身份验证。 更多信息请参阅“[在组织中要求双重身份验证](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.")”。 -To offer your app as a paid service, you'll need to meet these requirements to list your app on {% data variables.product.prodname_marketplace %}: +当您准备在 {% data variables.product.prodname_marketplace %} 上发布应用程序时，您必须请求验证上架信息。 -- To sell your app in {% data variables.product.prodname_marketplace %}, it must use GitHub's billing system. Your app does not need to handle payments but does need to use "[{% data variables.product.prodname_marketplace %} purchase events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" to manage new purchases, upgrades, downgrades, cancellations, and free trials. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" to learn about how to integrate these events into your app. Using GitHub's billing system allows customers to purchase an app without leaving GitHub and pay for the service with the payment method already attached to their {% data variables.product.product_name %} account. -- Apps must support both monthly and annual billing for paid subscriptions purchases. -- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." -{% data reusables.marketplace.marketplace-billing-ui-requirements %} +{% note %} + +验证过程对组织开放。 {% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何进行验证，请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)”。 + +{% endnote %} + +### 付费应用程序的计费要求 + +您的应用程序无需处理付款，但需要使用 {% data variables.product.prodname_marketplace %} 购买事件来管理新购买、升级、降级、取消和免费试用。 有关如何将这些事件集成到您的应用程序中，请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 + +GitHub 的计费 API 允许客户在不离开 GitHub 的情况下购买应用程序，并使用已附加到其 {% data variables.product.product_name %} 帐户的付款方式来支付服务费用。 + +- 应用程序必须在付费订阅计划中支持月度和年度计费。 +- 上架产品可提供免费和付费计划的任何组合。 免费计划是可选项，但建议提供。 更多信息请参阅“[设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)”。 diff --git a/translations/zh-CN/content/developers/github-marketplace/security-best-practices-for-apps.md b/translations/zh-CN/content/developers/github-marketplace/security-best-practices-for-apps.md new file mode 100644 index 0000000000..8311680fb2 --- /dev/null +++ b/translations/zh-CN/content/developers/github-marketplace/security-best-practices-for-apps.md @@ -0,0 +1,59 @@ +--- +title: 应用程序的安全最佳实践 +intro: '准备在 {% data variables.product.prodname_marketplace %} 上分享安全应用程序的指南。' +redirect_from: + - /apps/marketplace/getting-started/security-review-process/ + - /marketplace/getting-started/security-review-process + - /developers/github-marketplace/security-review-process-for-submitted-apps +shortTitle: 安全最佳实践 +versions: + free-pro-team: '*' +--- + +遵循这些最佳实践将有助于您提供安全的用户体验。 + +### 授权、身份验证和访问控制 + +我们建议创建 GitHub 应用程序，而不是 OAuth 应用程序。 {% data reusables.marketplace.github_apps_preferred %}. 更多信息请参阅“[GitHub 应用程序和 OAuth 应用程序之间的差异](/apps/differences-between-apps/)”。 +- 应用程序应使用最小权限原则，只请求应用程序执行其预期功能所需的 OAuth 作用域和 GitHub 应用程序权限。 更多信息请参阅维基百科中的[最小权限原则](https://en.wikipedia.org/wiki/Principle_of_least_privilege)。 +- 应用程序应为客户提供删除其帐户的方法，而无需发送电子邮件或呼叫支持人员。 +- 应用程序不应在应用程序的不同实现之间共享令牌。 例如，桌面应用程序应该使用与基于 Web 的应用程序不同的令牌。 单个令牌允许每个应用程序单独请求 GitHub 资源所需的访问权限。 +- 根据每种用户类型所需的功能，针对不同的用户角色设计应用程序。 例如，标准用户不应有权访问管理功能，帐单管理员可能不需要仓库代码推送权限。 +- 应用程序不应共享服务帐户（如电子邮件或数据库服务）来管理 SaaS 服务。 +- 应用程序中使用的所有服务都应具有唯一的登录名和密码凭据。 +- 对生产托管基础架构的管理员权限只能授予担当管理职责的工程师和员工。 +- 应用程序不应使用个人访问令牌进行身份验证，应验证为 [OAuth 应用程序](/apps/about-apps/#about-oauth-apps)或 [GitHub 应用程序](/apps/about-apps/#about-github-apps)： + - OAuth 应用程序应使用 [OAuth 令牌](/apps/building-oauth-apps/authorizing-oauth-apps/)进行身份验证。 + - GitHub 应用程序应使用 [JSON Web 令牌 (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)、[OAuth 令牌](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)或[安装访问令牌](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)进行身份验证。 + +### 数据保护 + +- 应用程序应使用带有有效 TLS 证书或 SSH for Git 的 HTTPS 对通过公共互联网传输的数据进行加密。 +- 应用程序应安全地存储客户端 ID 和客户端密钥。 我们建议将它们存储为[环境变量](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables)。 +- 应用程序应在收到用户请求后 30 天内或在用户与 GitHub 的法律关系终止后 30 天内删除所有 GitHub 用户数据。 +- 应用程序不应要求用户提供其 GitHub 密码。 +- 应用程序应该对令牌、客户端 ID 和客户端密钥进行加密。 + +### 日志记录和监视 + +应用程序应具有日志记录和监视功能。 应用程序日志应保留至少 30 天，并存档至少一年。 安全日志应包括： + +- 身份验证和授权事件 +- 服务配置更改 +- 对象读取和写入 +- 所有用户和组权限更改 +- 角色提升到管理员 +- 每个事件的一致时间戳 +- 所有记录操作的源用户、IP 地址和/或主机名 + +### 事件响应工作流程 + +要为用户提供安全体验，应在上架应用程序之前制定明确的事件响应计划。 我们建议您在自己的公司内成立安全和运营事件响应团队，而不是使用第三方供应商。 您应该能够在确认事件后 24 小时内通知 {% data variables.product.product_name %}。 + +有关事件响应工作流程的示例，请参阅 [SANS 研究所网站](https://www.sans.org/information-security-policy/)上的“数据泄露响应策略”。 包含明确的事件响应措施的简短文档比冗长的策略模板更有价值。 + +### 漏洞管理和补丁工作流程 + +您应该定期对生产基础架构进行漏洞扫描。 您应该对漏洞扫描的结果进行分类，并定义您同意修复漏洞的时间段。 + +如果您还没有准备好设置完整的漏洞管理程序，最好先创建一个修补流程。 有关创建补丁管理策略的指南，请参阅这篇 TechRepublic 文章“[建立补丁管理策略](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)”。 diff --git a/translations/zh-CN/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md index 5c09876b29..b625589a71 100644 --- a/translations/zh-CN/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/zh-CN/content/developers/github-marketplace/setting-pricing-plans-for-your-listing.md @@ -1,6 +1,6 @@ --- -title: Setting pricing plans for your listing -intro: 'When [listing your app on {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/), you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' +title: 为上架产品设置定价计划 +intro: '在 {% data variables.product.prodname_marketplace %} 中上架应用程序时，您可以选择免费提供或有偿出售您的应用程序。 如果打算出售应用程序，您可以为不同的功能等级创建不同的定价计划。' redirect_from: - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ @@ -17,66 +17,61 @@ versions: free-pro-team: '*' --- +### 关于设置定价计划 +如果要在 {% data variables.product.prodname_marketplace %} 上出售应用程序，则需要在发布应用程序上架信息时请求验证。 在验证过程中，上架专家会检查组织的身份和安全设置。 上架专家还将引导组织完成财务手续。 更多信息请参阅“[在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)”。 -### Creating pricing plans +{% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何进行验证，请参阅“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)”。 -To learn about the types of pricing plans that {% data variables.product.prodname_marketplace %} offers, see "[{% data variables.product.prodname_marketplace %} Pricing Plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." You'll also find helpful billing guidelines in "[Selling your app](/marketplace/selling-your-app/)." +{% data variables.product.prodname_marketplace %} 提供几种不同类型的定价计划。 更多信息请参阅“[{% data variables.product.prodname_marketplace %} 的定价计划](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)”。 -Pricing plans can be in the draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published listing will function the same way as draft listings until your app is approved and listed on {% data variables.product.prodname_marketplace %}. Draft listings allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish the pricing plan, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. +### 关于保存定价计划 -To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). If you haven't created a {% data variables.product.prodname_marketplace %} listing yet, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how. +您可以将定价计划保存为草稿或已发布状态。 如果尚未提交 {% data variables.product.prodname_marketplace %} 上架信息以供审批，则已发布的计划与计划草案的运作方式相同，直到您的上架信息得到批准并显示在 {% data variables.product.prodname_marketplace %} 上。 计划草案允许您创建和保存新的定价计划，而无需在您的 {% data variables.product.prodname_marketplace %} 上架页面上提供它们。 一旦您在已发布的上架信息中发布定价计划，它就可以立即供客户购买。 您最多可以发布 10 个定价计划。 -When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan: +有关向客户计费的指南，请参阅“[向客户计费](/developers/github-marketplace/billing-customers)”。 -#### Plan name +### 创建定价计划 -Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align to the plan's resources, the size of the company that will use the plan, or anything you'd like. +要为 {% data variables.product.prodname_marketplace %} 上架信息创建定价计划，请在 [{% data variables.product.prodname_marketplace %} 上架页面](https://github.com/marketplace/manage)的左边栏中单击 **Plans and pricing（计划和定价）**。 更多信息请参阅“[创建 {% data variables.product.prodname_marketplace %} 上架信息草稿](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)”。 -#### Pricing models +单击 **New draft plan（新建计划草稿）**时，您将会看到一个用于自定义定价计划的表单。 您需要配置以下字段以创建定价计划： -##### Free plans +- **Plan name（计划名称）** - 定价计划的名称将显示在 {% data variables.product.prodname_marketplace %} 应用程序的登录页面上。 您可以自定义定价计划的名称，使其与计划的资源、将使用该计划的公司规模或任何您想要的内容保持一致。 -{% data reusables.marketplace.free-apps-encouraged %} A free plan still requires you to handle [new purchase](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/) and [cancellation](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/) billing flows. See "[Billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" for more details. +- **Pricing models（定价模式）** - 有三种类型的定价计划：免费、统一定价和每单位定价。 所有计划都要求通过 Marketplace API 处理新购买和取消事件。 此外，对于付费计划： -##### Flat-rate plans + - 您必须以美元设置每月和每年订阅价格。 + - 您的应用程序必须处理计划更改事件。 + - 您必须请求验证才能发布包含付费计划的上架产品。 + - {% data reusables.marketplace.marketplace-pricing-free-trials %} -Flat-rate pricing plans allow you to offer your service to customers for a flat-rate fee. {% data reusables.marketplace.marketplace-pricing-free-trials %} + 更多信息请参阅“[{% data variables.product.prodname_marketplace %} 应用程序的定价计划](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)”和“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 -You must set a price for both monthly and yearly subscriptions in U.S. Dollars for flat-rate plans. Dollars for flat-rate plans. +- **Available for（适用对象）** - {% data variables.product.prodname_marketplace %} 定价计划可以适用于 **Personal and organization accounts（个人和组织帐户）**、**Personal accounts only（仅个人帐户）**或 **Organization accounts only（仅组织帐户）**。 例如，如果您的定价计划为每单位定价并提供多个席位，则您将选择 **Organization accounts only（仅组织帐户）**，因为无法从个人帐户为组织中的人员分配席位。 -##### Per-unit plans +- **Short description（简要说明）** - 编写有关定价计划细节的简短摘要。 说明可包括计划的目标客户类型或所包含的资源。 -Per-unit pricing allows you to offer your app in units. For example, a unit can be a person, seat, or user. You'll need to provide a name for the unit and set a price for both monthly and yearly subscriptions, in U.S. Dollars. +- **Bullets（项目符号）** - 您最多可以编写四个项目符号，其中包括有关定价计划的更多细节。 项目符号可包括应用程序的用例，或列出有关计划中包含的资源或功能的更多详细信息。 -#### Available for +{% data reusables.marketplace.free-plan-note %} -{% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. +### 创建 {% data variables.product.prodname_marketplace %} 上架产品的定价计划 -#### Short description +如果不再需要 {% data variables.product.prodname_marketplace %} 上架产品的定价计划，或者需要调整定价细节，您可以删除它。 -Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. +![删除定价计划的按钮](/assets/images/marketplace/marketplace_remove_this_plan.png) -#### Bullets +为 {% data variables.product.prodname_marketplace %} 中已上架的应用程序发布定价计划后，就无法对该计划进行更改。 您需要删除该定价计划，然后创建一个新计划。 已经购买已删除定价计划的客户将继续使用它，直到他们选择退出并转到新的定价计划。 有关定价计划的更多信息，请参阅“[{% data variables.product.prodname_marketplace %} 定价计划](/marketplace/selling-your-app/github-marketplace-pricing-plans/)”。 -You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. - -### Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan - -If a pricing plan for your {% data variables.product.prodname_marketplace %} plan is no longer needed or if you need to adjust pricing details, you can remove it. - -![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png) - -Once you publish a pricing plan for an app already listed in the {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." - -Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription. +您删除定价计划后，用户将无法使用该计划购买您的应用程序。 使用已删除定价计划的现有用户将继续使用该计划，直到他们取消其计划订阅。 {% note %} -**Note:** {% data variables.product.product_name %} can't remove users from a removed pricing plan. You can run a campaign to encourage users to upgrade or downgrade from the removed pricing plan onto a new pricing plan. +**注：**{% data variables.product.product_name %} 不能从已删除的定价计划中删除用户。 您可以推出一个活动，鼓励用户从已删除的定价计划升级或降级到新的定价计划。 {% endnote %} -You can disable GitHub Marketplace free trials without retiring the pricing plan, but this prevents you from initiating future free trials for that plan. If you choose to disable free trials for a pricing plan, users already signed up can complete their free trial. +您可以禁用 GitHub Marketplace 免费试用而不撤销定价计划，但这会阻止您在未来为该计划启动免费试用。 如果您选择禁用定价计划的免费试用，则已注册的用户仍可以完成其免费试用。 -After retiring a pricing plan, you can create a new pricing plan with the same name as the removed pricing plan. For instance, if you have a "Pro" pricing plan but need to change the flat rate price, you can remove the "Pro" pricing plan and create a new "Pro" pricing plan with an updated price. Users will be able to purchase the new pricing plan immediately. +撤销定价计划后，您可以创建与已删除的定价计划同名的新定价计划。 例如，如果您有一个 "Pro" 定价计划，但需要更改统一价格，您可以删除该 "Pro" 定价计划，然后使用更新后的价格创建新的 "Pro" 定价计划。 用户将能够立即购买新的定价计划。 diff --git a/translations/zh-CN/content/developers/github-marketplace/submitting-your-listing-for-publication.md b/translations/zh-CN/content/developers/github-marketplace/submitting-your-listing-for-publication.md new file mode 100644 index 0000000000..be3e6cdccd --- /dev/null +++ b/translations/zh-CN/content/developers/github-marketplace/submitting-your-listing-for-publication.md @@ -0,0 +1,37 @@ +--- +title: 提交要发布的上架信息 +intro: '您可以提交上架产品以供 {% data variables.product.prodname_dotcom %} 社区使用。' +redirect_from: + - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review + - /developers/github-marketplace/submitting-your-listing-for-review +versions: + free-pro-team: '*' +--- + + + +完成应用程序的上架信息后，您将会看到两个按钮，允许您请求在验证或不验证的情况下发布上架产品。 如果您在上架信息中发布了任何付费定价计划，则“发布而不验证”的 **Request（请求）**按钮将被禁用。 + +![Unverified and verified request button](/assets/images/marketplace/marketplace-request-button.png) + +{% data reusables.marketplace.launch-with-free %} + +提交上架信息以供审查后，上架专家将联系您，要求您提供更多信息。 + +有关创建和提交上架信息的流程概述，请参阅“[关于 {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/about-github-marketplace#publishing-an-app-to-github-marketplace)”。 + +### 请求验证发布的前提条件 + +请求验证上架信息之前，您需要将 {% data variables.product.prodname_marketplace %} 帐单流程和 web 挂钩集成到应用程序中。 更多信息请参阅“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 + +如果已满足上架要求并且已集成 {% data variables.product.prodname_marketplace %} API，请继续提交您的上架信息。 For more information, see "[Requirements for listing an app](/developers/github-marketplace/requirements-for-listing-an-app)." + +{% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何执行此操作的信息，请参阅下面的“[在提交之前将应用程序转让给组织](#transferring-an-app-to-an-organization-before-you-submit)”。 + +### 在提交之前将应用程序转让给组织 + +无法出售由用户帐户拥有的应用程序。 您需要将应用程序转让给已成为经验证创建者的组织，或者可请求验证应用程序上架信息的组织。 更多信息请参阅： + +1. “[从头开始创建组织](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)” + +1. “[转让 GitHub 应用程序的所有权](/developers/apps/transferring-ownership-of-a-github-app)”或“[转让 OAuth 应用程序的所有权](/developers/apps/transferring-ownership-of-an-oauth-app)” diff --git a/translations/zh-CN/content/developers/github-marketplace/testing-your-app.md b/translations/zh-CN/content/developers/github-marketplace/testing-your-app.md index 09e79b1a7a..bd37d5368c 100644 --- a/translations/zh-CN/content/developers/github-marketplace/testing-your-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/testing-your-app.md @@ -1,6 +1,6 @@ --- -title: Testing your app -intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before the {% data variables.product.prodname_marketplace %} onboarding team approves your app, it must adequately handle the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows).' +title: 测试应用程序 +intro: 'GitHub 建议在将上架信息提交到 {% data variables.product.prodname_marketplace %} 之前，先使用 API 和 web 挂钩测试您的应用，以便为客户提供理想的体验。 在上架专家批准您的应用程序之前，它必须能够完全处理帐单流程。' redirect_from: - /apps/marketplace/testing-apps-apis-and-webhooks/ - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ @@ -11,34 +11,34 @@ versions: -### Testing apps +### 测试应用程序 -You can use a [draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) to simulate each of the [billing flows](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows). A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. +您可以使用 {% data variables.product.prodname_marketplace %} 上架草稿来模拟每个帐单流程。 上架信息处于草稿状态意味着它尚未提交以供审批。 使用 {% data variables.product.prodname_marketplace %} 上架草稿进行的任何购买都_不会_产生真正的交易，GitHub 不会从您的信用卡中扣款。 更多信息请参阅“[起草应用程序上架信息](/developers/github-marketplace/drafting-a-listing-for-your-app)”和“[在应用程序中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 -#### Using a development app with a draft listing to test changes +#### 使用带有上架草稿的开发应用程序来测试更改 -A {% data variables.product.prodname_marketplace %} listing can only be associated with a single app registration, and each app can only access its own {% data variables.product.prodname_marketplace %} listing. For these reasons, we recommend configuring a separate development app, with the same configuration as your production app, and creating a _draft_ {% data variables.product.prodname_marketplace %} listing that you can use for testing. The draft {% data variables.product.prodname_marketplace %} listing allows you to test changes without affecting the active users of your production app. You will never have to submit your development {% data variables.product.prodname_marketplace %} listing, since you will only use it for testing. +{% data variables.product.prodname_marketplace %} 上架信息只能与单个应用程序注册相关联，并且每个应用程序只能访问它自己的 {% data variables.product.prodname_marketplace %} 上架信息。 出于这些原因，我们建议配置一个与生产应用程序配置相同的单独开发应用程序，并创建可用于测试的 {% data variables.product.prodname_marketplace %} 上架_草稿_。 {% data variables.product.prodname_marketplace %} 草稿允许您测试更改而不影响生产应用程序的活动用户。 您无需提交开发 {% data variables.product.prodname_marketplace %} 上架信息，因为它仅用于测试。 -Because you can only create draft {% data variables.product.prodname_marketplace %} listings for public apps, you must make your development app public. Public apps are not discoverable outside of published {% data variables.product.prodname_marketplace %} listings as long as you don't share the app's URL. A Marketplace listing in the draft state is only visible to the app's owner. +由于只能为公共应用程序创建 {% data variables.product.prodname_marketplace %} 上架草稿，因此您必须将开发应用程序设为公共。 公共应用程序不会在已发布的 {% data variables.product.prodname_marketplace %} 上架信息之外被发现，只要您不分享该应用程序的 URL。 处于草稿状态的 Marketplace 上架信息仅对应用程序的所有者可见。 -Once you have a development app with a draft listing, you can use it to test changes you make to your app while integrating with the {% data variables.product.prodname_marketplace %} API and webhooks. +一旦有了带有上架草稿的开发应用程序，就可以在与 {% data variables.product.prodname_marketplace %} API 和 web 挂钩集成的同时，使用它来测试您对应用程序所做的更改。 {% warning %} -Do not make test purchases with an app that is live in {% data variables.product.prodname_marketplace %}. +不要使用 {% data variables.product.prodname_marketplace %} 中上线的应用程序来测试购买。 {% endwarning %} -#### Simulating Marketplace purchase events +#### 模拟 Marketplace 购买事件 -Your testing scenarios may require setting up listing plans that offer free trials and switching between free and paid subscriptions. Because downgrades and cancellations don't take effect until the next billing cycle, GitHub provides a developer-only feature to "Apply Pending Change" to force `changed` and `cancelled` plan actions to take effect immediately. You can access **Apply Pending Change** for apps with _draft_ Marketplace listings in https://github.com/settings/billing#pending-cycle: +您的测试场景可能需要设置可提供免费试用并且可在免费和付费订阅之间切换的上架计划。 由于降级和取消要到下一个结算周期才会生效，因此 GitHub 提供一个开发者专用功能“应用待处理更改”，以强制 `changed` 和 `cancelled` 计划操作立即生效。 您可以在 https://github.com/settings/billing#pending-cycle 中对带有 Marketplace 上架_草稿_的应用程序使用 **Apply Pending Change（应用待处理更改）**： -![Apply pending change](/assets/images/github-apps/github-apps-apply-pending-changes.png) +![应用待处理更改](/assets/images/github-apps/github-apps-apply-pending-changes.png) -### Testing APIs +### 测试 API -For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace). +对于大多数 {% data variables.product.prodname_marketplace %} API 端点，我们还提供存根 API 端点，它们返回可用于测试的硬编码假数据。 要接收存根数据，您必须指定存根 URL，其路由中包括 `/stubbed`（例如，`/user/marketplace_purchases/stubbed`）。 有关支持此存根数据方法的端点列表，请参阅 [{% data variables.product.prodname_marketplace %} 端点](/rest/reference/apps#github-marketplace)。 -### Testing webhooks +### 测试 web 挂钩 -GitHub provides tools for testing your deployed payloads. For more information, see "[Testing webhooks](/webhooks/testing/)." +GitHub 提供用于测试已部署有效负载的工具。 更多信息请参阅“[测试 web 挂钩](/webhooks/testing/)”。 diff --git a/translations/zh-CN/content/developers/github-marketplace/viewing-metrics-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/viewing-metrics-for-your-listing.md index 50d90f1cb1..0b7d781bca 100644 --- a/translations/zh-CN/content/developers/github-marketplace/viewing-metrics-for-your-listing.md +++ b/translations/zh-CN/content/developers/github-marketplace/viewing-metrics-for-your-listing.md @@ -1,6 +1,6 @@ --- -title: Viewing metrics for your listing -intro: 'The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}''s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns.' +title: 查看上架产品的指标 +intro: '{% data variables.product.prodname_marketplace %} Insights 页面显示 {% data variables.product.prodname_github_app %} 的指标。 您可以使用这些指标来跟踪 {% data variables.product.prodname_github_app %} 的表现，并就价格、计划、免费试用以及如何看待营销活动的效果做出更明智的决定。' redirect_from: - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing/ - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing/ @@ -12,43 +12,43 @@ versions: -You can view metrics for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed. +您可以查看 {% data variables.product.prodname_github_app %} 在过去一天（24 小时）、一周、一月或整个上架期间的指标。 {% note %} -**Note:** Because it takes time to aggregate data, you'll notice a slight delay in the dates shown. When you select a time period, you can see exact dates for the metrics at the top of the page. +**注：**由于聚合数据需要时间，因此您会注意到显示的日期略有延迟。 选择时间段时，可以在页面顶部看到指标的确切日期。 {% endnote %} -### Performance metrics +### 性能指标 -The Insights page displays these performance metrics, for the selected time period: +Insights 页面显示选定时段的以下性能指标： -* **Subscription value:** Total possible revenue (in US dollars) for subscriptions. This value represents the possible revenue if no plans or free trials are cancelled and all credit transactions are successful. The subscription value includes the full value for plans that begin with a free trial in the selected time period, even when there are no financial transactions in that time period. The subscription value also includes the full value of upgraded plans in the selected time period but does not include the prorated amount. To see and download individual transactions, see "[GitHub Marketplace transactions](/marketplace/github-marketplace-transactions/)." -* **Visitors:** Number of people that have viewed a page in your GitHub Apps listing. This number includes both logged in and logged out visitors. -* **Pageviews:** Number of views the pages in your GitHub App's listing received. A single visitor can generate more than one pageview. +* **Subscription value（订阅价值）：**订阅的可能总收入（美元）。 此值表示在没有计划或免费试用被取消并且所有信用交易都成功的情况下的可能收入。 订阅价值包括计划在选定时段内的全部价值，从免费试用开始计算，即使在该时段内没有任何财务交易。 订阅价值还包括选定时段内升级计划的全部价值，但不包括按比例分配的金额。 要查看和下载单个交易，请参阅“[GitHub Marketplace 交易](/marketplace/github-marketplace-transactions/)”。 +* **Visitors（访客数）：**查看过 GitHub 应用程序上架页面的人数。 此数字包括已登录和已注销的访客。 +* **Pageviews（网页浏览量）：**GitHub 应用程序上架页面获得的浏览次数。 单个访客可以产生多个网页浏览量。 {% note %} -**Note:** Your estimated subscription value could be much higher than the transactions processed for this period. +**注：**您估计的订阅价值可能远远高于此期间处理的交易。 {% endnote %} -#### Conversion performance +#### 转化性能 -* **Unique visitors to landing page:** Number of people who viewed your GitHub App's landing page. -* **Unique visitors to checkout page:** Number of people who viewed one of your GitHub App's checkout pages. -* **Checkout page to new subscriptions:** Total number of paid subscriptions, free trials, and free subscriptions. See the "Breakdown of total subscriptions" for the specific number of each type of subscription. +* **Unique visitors to landing page（登录页面的绝对访客数）：**查看过 GitHub 应用程序登录页面的人数。 +* **Unique visitors to checkout page（结账页面的绝对访客数）：**查看过 GitHub 应用程序结账页面的人数。 +* **Checkout page to new subscriptions（结账页面产生的新订阅数）：**付费订阅、免费试用和免费订阅的总数。 有关每种类型订阅的具体数量，请参阅“订阅总数的细分”。 ![Marketplace insights](/assets/images/marketplace/marketplace_insights.png) -To access {% data variables.product.prodname_marketplace %} Insights: +要访问 {% data variables.product.prodname_marketplace %} Insights： {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.marketplace_apps %} 4. 选择 -{% data variables.product.prodname_github_app %} that you'd like to view Insights for. +您要查看其 Insights 的 {% data variables.product.prodname_github_app %}。 {% data reusables.user-settings.edit_marketplace_listing %} -6. Click the **Insights** tab. -7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Insights page. ![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png) +6. 单击 **Insights** 选项卡。 +7. （可选）通过单击 Insights 页面右上角的 Period（时段）下拉列表选择不同的时间段。 ![Marketplace 时段](/assets/images/marketplace/marketplace_insights_time_period.png) diff --git a/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md b/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md index ce64f0ae76..c211742c78 100644 --- a/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/zh-CN/content/developers/github-marketplace/viewing-transactions-for-your-listing.md @@ -1,6 +1,6 @@ --- -title: Viewing transactions for your listing -intro: 'The {% data variables.product.prodname_marketplace %} transactions page allows you to download and view all transactions for your {% data variables.product.prodname_marketplace %} listing. You can view transations for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.' +title: 查看上架产品的交易 +intro: '{% data variables.product.prodname_marketplace %} 交易页面允许您下载和查看 {% data variables.product.prodname_marketplace %} 上架产品的所有交易。 您可以查看 {% data variables.product.prodname_github_app %} 在过去一天（24 小时）、一周、一月或整个上架期间的交易。' redirect_from: - /marketplace/github-marketplace-transactions versions: @@ -11,36 +11,36 @@ versions: {% note %} -**Note:** Because it takes time to aggregate data, you'll notice a slight delay in the dates shown. When you select a time period, you can see exact dates for the metrics at the top of the page. +**注：**由于聚合数据需要时间，因此您会注意到显示的日期略有延迟。 选择时间段时，可以在页面顶部看到指标的确切日期。 {% endnote %} -You can view or download the transaction data to keep track of your subscription activity. Click the **Export CSV** button to download a `.csv` file. You can also select a period of time to view and search within the transaction page. +您可以查看或下载交易数据来跟踪订阅活动。 单击 **Export CSV（导出 CSV）**按钮以下载 `.csv` 文件。 您还可以选择一个时间段在交易页面中查看和搜索。 -### Transaction data fields +### 交易数据字段 -* **date:** The date of the transaction in `yyyy-mm-dd` format. -* **app_name:** The app name. -* **user_login:** The login of the user with the subscription. -* **user_id:** The id of the user with the subscription. -* **user_type:** The type of GitHub account, either `User` or `Organization`. -* **country:** The three letter country code. -* **amount_in_cents:** The amount of the transaction in cents. When a value is less the plan amount, the user upgraded and the new plan is prorated. A value of zero indicates the user cancelled their plan. -* **renewal_frequency:** The subscription renewal frequency, either `Monthly` or `Yearly`. -* **marketplace_listing_plan_id:** The `id` of the subscription plan. +* **date（日期）：**交易的日期，格式为 `yyyy-mm-dd`。 +* **app_name：**应用程序的名称。 +* **user_login：**订阅用户的登录名。 +* **user_id：**订阅用户的 ID。 +* **user_type：**GitHub 帐户的类型，即 `User` 或 `Organization`。 +* **country（国家/地区）：**三个字母的国家代码。 +* **amount_in_cents：**交易金额，以美分为单位。 如果该值小于计划金额，则表示用户已升级并按比例分配给新计划。 值为零表示用户已取消其计划。 +* **renewal_frequency：**续订频率，即 `Monthly` 或 `Yearly`。 +* **marketplace_listing_plan_id：**订阅计划的 `id`。 ![Marketplace insights](/assets/images/marketplace/marketplace_transactions.png) -### Accessing {% data variables.product.prodname_marketplace %} transactions +### 访问 {% data variables.product.prodname_marketplace %} 交易 -To access {% data variables.product.prodname_marketplace %} transactions: +要访问 {% data variables.product.prodname_marketplace %} 交易： {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.marketplace_apps %} 4. 选择 -{% data variables.product.prodname_github_app %} that you'd like to view transactions for. +您要查看其交易的 {% data variables.product.prodname_github_app %}。 {% data reusables.user-settings.edit_marketplace_listing %} -6. Click the **Transactions** tab. -7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Transactions page. ![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png) +6. 单击 **Transactions（交易）**选项卡。 +7. （可选）通过单击 Transactions（交易）页面右上角的 Period（时段）下拉列表选择不同的时间段。 ![Marketplace 时段](/assets/images/marketplace/marketplace_insights_time_period.png) diff --git a/translations/zh-CN/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md b/translations/zh-CN/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md index 3254c9670c..0d41f00b42 100644 --- a/translations/zh-CN/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md +++ b/translations/zh-CN/content/developers/github-marketplace/webhook-events-for-the-github-marketplace-api.md @@ -1,6 +1,6 @@ --- title: GitHub Marketplace API 的 web 挂钩事件 -intro: '{% data variables.product.prodname_marketplace %} app 从 Marketplace 购买事件 web 挂钩接收有关用户计划更改的信息。 当用户购买、取消或更改其付款计划时，就会触发 Marketplace 购买事件。 有关如何响应每类事件的详细信息，请参阅“[帐单流程](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)”。' +intro: '{% data variables.product.prodname_marketplace %} app 从 Marketplace 购买事件 web 挂钩接收有关用户计划更改的信息。 当用户购买、取消或更改其付款计划时，就会触发 Marketplace 购买事件。' redirect_from: - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ diff --git a/translations/zh-CN/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md index d3a3dd3818..7ad59b6d68 100644 --- a/translations/zh-CN/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/writing-a-listing-description-for-your-app.md @@ -1,6 +1,6 @@ --- -title: Writing a listing description for your app -intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.' +title: 编写应用程序的上架说明 +intro: '要在 {% data variables.product.prodname_marketplace %} 中[上架应用程序](/marketplace/listing-on-github-marketplace/)，您需要根据 GitHub 的指南编写应用程序的说明并提供图像。' redirect_from: - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions/ - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions/ @@ -16,180 +16,180 @@ versions: -Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing. +以下是有关您在上架信息草稿的 **Listing description（上架说明）**部分中需要填写字段的指南。 -### Naming and links +### 命名和链接 -#### Listing name +#### 上架产品名称 -Your app's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters. +应用程序的名称将显示在 [{% data variables.product.prodname_marketplace %} 主页](https://github.com/marketplace)上。 名称限制为 255 个字符。 -#### Very short description +#### 简短说明 -The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). +在 [{% data variables.product.prodname_marketplace %} 主页](https://github.com/marketplace)上，社区将会看到应用程序名称下面“非常简短”的说明。 -![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png) +![{% data variables.product.prodname_marketplace %} 应用程序简短说明](/assets/images/marketplace/marketplace_short_description.png) -##### Length +##### 长度 -We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly. +我们建议将简短说明控制在 40-80 个字符。 尽管可以使用更多字符，但简洁的描述使客户更容易快速阅读和理解。 -##### Content +##### 内容 -- Describe the app’s functionality. Don't use this space for a call to action. 例如： +- 介绍应用程序的功能。 不要在此空间使用呼吁用语。 例如： - **DO:** Lightweight project management for GitHub issues + **宜：**GitHub 议题的轻量级项目管理 - **DON'T:** Manage your projects and issues on GitHub + **不宜：**Manage your projects and issues on GitHub（在 GitHub 上管理项目和议题） - **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_ + **提示：**在呼吁用语中动词的末尾加上 "s" 可转变为可接受的说明：_Manages your projects and issues on GitHub_ -- Don’t repeat the app’s name in the description. +- 不要在说明中重复应用程序的名称。 - **DO:** A container-native continuous integration tool + **宜：**容器原生持续集成工具 - **DON'T:** Skycap is a container-native continuous integration tool + **不宜：**Skycap 是一个容器原生持续集成工具 -##### Formatting +##### 格式 -- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns. +- 始终使用句子大小写规则。 只大写第一个字母和专有名词。 -- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence. +- 在简短说明的末尾不要使用标点符号。 简短说明不应包含完整的句子，并且绝对不能包含一个以上的句子。 -- Only capitalize proper nouns. 例如： +- 仅大写专有名词。 例如： - **DO:** One-click delivery automation for web developers + **宜：**One-click delivery automation for web developers - **DON'T:** One-click delivery automation for Web Developers + **不宜：**One-click delivery automation for Web Developers -- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. +- 在列表中始终使用[连续逗号](https://en.wikipedia.org/wiki/Serial_comma)。 -- Avoid referring to the GitHub community as "users." +- 避免将 GitHub 社区称为“用户”。 - **DO:** Create issues automatically for people in your organization + **宜：**为组织中的人员自动创建议题 - **DON'T:** Create issues automatically for an organization's users + **不宜：**为组织的用户自动创建议题 -- Avoid acronyms unless they’re well established (such as API). 例如： +- 避免使用首字母缩写词，除非是约定俗成的缩写（如 API）。 例如： - **DO:** Agile task boards, estimates, and reports without leaving GitHub + **宜：**Agile task boards, estimates, and reports without leaving GitHub - **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI + **不宜：** Agile task boards, estimates, and reports without leaving GitHub’s UI #### 分类 -Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app. +{% data variables.product.prodname_marketplace %} 中的应用程序可以按类别显示。 在 **Primary category（主要类别）**下拉列表中选择最适合描述应用程序主要功能的类别，（可选）然后选择适合应用程序的 **Secondary category（次要类别）**。 #### 支持的语言 -If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional. +如果您的应用程序仅适用于特定语言，请选择它支持的最多 10 种编程语言。 这些语言显示在应用程序的 {% data variables.product.prodname_marketplace %} 上架信息页面上。 此字段是可选的。 -#### Listing URLs +#### 上架信息中的 URL -**Required URLs** -* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries. -* **Privacy policy URL:** The web page that displays your app's privacy policy. -* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App. +**必需的 URL** +* **Customer support URL（客户支持 URL）：**客户寻求技术支持、产品或帐户查询时前往的网页 URL。 +* **Privacy policy URL（隐私政策 URL）：**显示应用程序隐私政策的网页。 +* **Installation URL（安装 URL）：**此字段仅对 OAuth 应用程序显示。 （GitHub 应用程序不使用此 URL，因为它们使用 GitHub 应用程序设置页面中可选的设置 URL。） 当客户购买您的 OAuth 应用程序时，GitHub 将在客户安装应用程序后将其重定向到安装 URL。 您需要将客户重定向到 `https://github.com/login/oauth/authorize` 以开始 OAuth 授权流程。 更多信息请参阅“[新购买 OAuth 应用程序](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)”。 如果您要上架 GitHub 应用程序，请跳过此字段。 -**Optional URLs** -* **Company URL:** A link to your company's website. -* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance. -* **Documentation URL:** A link to documentation that teaches customers how to use your app. +**可选的 URL** +* **Company URL（公司 URL）：**指向公司网站的链接。 +* **Status URL（状态 URL）：**显示应用程序状态的网页链接。 状态页面可以包括当前和历史事件报告、Web 应用程序正常运行时间状态以及预定维护。 +* **Documentation URL（文档 URL）：**指导客户如何使用应用程序的文档链接。 -### Logo and feature card +### 徽标和特征卡 -{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps. +{% data variables.product.prodname_marketplace %} 使用圆形徽章内的方形徽标图像显示所有上架产品，以便从视觉上区分应用程序。 -![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png) +![GitHub Marketplace 徽标和徽章图像](/assets/images/marketplace/marketplace-logo-and-badge.png) -A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card. +特征卡由应用程序的徽标、名称和自定义背景图像组成，可体现您的品牌个性。 如果您的应用程序是[主页](https://github.com/marketplace)顶部的四个随机精选应用程序之一，{% data variables.product.prodname_marketplace %} 将显示此卡。 每个应用程序的简短说明显示在其特征卡的下方。 -![Feature card](/assets/images/marketplace/marketplace_feature_card.png) +![特征卡](/assets/images/marketplace/marketplace_feature_card.png) -As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card. +当您上传图像和选择颜色时，{% data variables.product.prodname_marketplace %} 上架草稿将显示徽标和特征卡的预览。 -##### Guidelines for logos +##### 徽标指南 -You must upload a custom image for the logo. For the badge, choose a background color. +您必须上传徽标的自定义图像。 对于徽章，请选择背景颜色。 -- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published. -- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center. -- For best results, upload a logo image with a transparent background. -- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image. -- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens. +- 上传至少为 200 像素 x 200 像素的徽标图像，这样在发布上架信息时就不必放大徽标。 +- 徽标将被裁剪为正方形。 建议上传徽标居中的正方形图像文件。 +- 为获得最佳效果，请上传透明背景的徽标图像。 +- 要显示无缝徽章的外观，请选择与徽标图像的背景颜色（或透明度）匹配的徽章背景颜色。 +- 避免使用带有文字的徽标图像。 带有文字的徽标在小屏幕上缩放效果不佳。 -##### Guidelines for feature cards +##### 特征卡指南 -You must upload a custom background image for the feature card. For the app's name, choose a text color. +您必须上传特征卡的自定义背景图像。 对于应用程序的名称，请选择文本颜色。 -- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality. -- Background image measures 965 pixels x 482 pixels (width x height). -- Choose a text color for your app's name that shows up clearly over the background image. +- 在背景图像中使用图案或纹理赋予卡片视觉特征，使其在 {% data variables.product.prodname_marketplace %} 主页的深色背景下引人注目。 特征卡应体现应用程序的品牌个性。 +- 背景图像尺寸为 965 像素 x 482 像素（宽 x 高）。 +- 为应用程序的名称选择文本颜色，使其清晰地显示在背景图像上。 -### Listing details +### 上架详细信息 -To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description." +要获取应用程序的登录页面，请在 {% data variables.product.prodname_marketplace %} 主页或类别页面上单击应用程序的名称。 登录页面显示应用程序的较长说明，包括两个部分：“Introductory description（简介）”和“Detailed description（详细说明）”。 -Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page. +“Introductory description（简介）”显示在应用程序 {% data variables.product.prodname_marketplace %} 登录页面的顶部。 -![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png) +![{% data variables.product.prodname_marketplace %} 简介](/assets/images/marketplace/marketplace_intro_description.png) -Clicking **Read more...**, displays the "Detailed description." +单击 **Read more（阅读更多）...**，显示“Detailed description（详细说明）”。 -![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png) +![{% data variables.product.prodname_marketplace %} 详细说明](/assets/images/marketplace/marketplace_detailed_description.png) -Follow these guidelines for writing these descriptions. +请遵循以下指南编写这些说明。 -#### Length +#### 长度 -We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly. +我们建议您[上架应用程序](/marketplace/listing-on-github-marketplace/)时，在必填字段“Introductory description（简介）”中写 1-2 句高度概述的说明，长度控制在 150-250 个字符。 尽管可以使用更多字符，但简洁的概述使客户更容易快速阅读和理解。 -You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description. +您可以在可选的“Detailed description（详细说明）”字段中添加更多信息。 在应用程序登录页面中“Introductory description（简介）”的下方单击 **Read more（阅读更多）...** 将会看到此说明。 详细说明包括 3-5 个[价值主张](https://en.wikipedia.org/wiki/Value_proposition)，每个价值主张用 1-2 个句子阐明。 此说明最多可以使用 1,000 个字符。 -#### Content +#### 内容 -- Always begin introductory descriptions with your app's name. +- 始终用应用程序的名称开始简介。 -- Always write descriptions and value propositions using the active voice. +- 始终用主动语态编写说明和价值主张。 -#### Formatting +#### 格式 -- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns. +- 始终在价值主张标题中使用句子大小写规则。 只大写第一个字母和专有名词。 -- Use periods in your descriptions. Avoid exclamation marks. +- 在说明中使用句点。 避免使用感叹号。 -- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence. +- 在价值主张标题的末尾不要使用标点符号。 价值主张标题不应包含完整的句子，并且不能包含一个以上的句子。 -- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. 例如： +- 对于每个价值主张，请在其标题后加上一段说明。 使用 Markdown 将标题格式设置为[三级标题](/articles/basic-writing-and-formatting-syntax/#headings)。 例如： - ### Learn the skills you need + ### 学习所需的技能 - GitHub Learning Lab can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more. + GitHub Learning Lab 可以帮助您学习如何使用 GitHub、如何使用 Markdown 更有效地沟通以及如何处理合并冲突等。 -- Only capitalize proper nouns. +- 仅大写专有名词。 -- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. +- 在列表中始终使用[连续逗号](https://en.wikipedia.org/wiki/Serial_comma)。 -- Avoid referring to the GitHub community as "users." +- 避免将 GitHub 社区称为“用户”。 - **DO:** Create issues automatically for people in your organization + **宜：**为组织中的人员自动创建议题 - **DON'T:** Create issues automatically for an organization's users + **不宜：**为组织的用户自动创建议题 -- Avoid acronyms unless they’re well established (such as API). +- 避免使用首字母缩写词，除非是约定俗成的缩写（如 API）。 -### Product screenshots +### 产品屏幕截图 -You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page. +您可以上传应用程序的最多五张屏幕截图，以显示在应用程序的登录页面上。 向每个屏幕截图添加可选标题以提供上下文。 上传屏幕截图后，您将其拖动到希望它们在登录页面上显示的位置。 -#### Guidelines for screenshots +#### 屏幕截图指南 -- Images must be of high resolution (at least 1200px wide). -- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next. -- Show as much of the user interface as possible so people can see what your app does. -- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes. -- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots. -- Captions are most effective when they are short and snappy. +- 图像必须具有高分辨率(至少 1200 像素宽)。 +- 所有图像必须具有相同的高度和宽度（宽高比），以避免用户切换图像时出现页面跳跃。 +- 显示尽可能多的用户界面，以便用户看到应用程序执行的操作。 +- 在浏览器中截取应用程序的屏幕时，仅包括显示窗口中的内容。 避免包括地址栏、标题栏或工具栏图标，它们不能很好地适应较小的屏幕尺寸。 +- GitHub 在应用程序登录页面的图框中显示您上传的屏幕截图，因此您无需在屏幕截图周围添加图框或边框。 +- 简短明快的字幕效果最好。 -![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png) +![GitHub Marketplace 屏幕截图](/assets/images/marketplace/marketplace-screenshots.png) diff --git a/translations/zh-CN/content/developers/overview/about-githubs-apis.md b/translations/zh-CN/content/developers/overview/about-githubs-apis.md index 3ffd0aa908..5eb45b8247 100644 --- a/translations/zh-CN/content/developers/overview/about-githubs-apis.md +++ b/translations/zh-CN/content/developers/overview/about-githubs-apis.md @@ -9,11 +9,7 @@ versions: github-ae: '*' --- -There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). - -When using the REST API, we encourage you to [request v3 via the `Accept` header](/rest/overview/media-types#request-specific-version). - -For information on using the GraphQL API, see the [v4 docs](/graphql). +There are two stable versions of the GitHub API: the [REST API](/rest) and the [GraphQL API](/graphql). When using the REST API, we encourage you to [request v3 via the `Accept` header](/v3/media/#request-specific-version). For information on using the GraphQL API, see the [v4 docs](/graphql). ## Deprecated versions diff --git a/translations/zh-CN/content/developers/overview/github-developer-program.md b/translations/zh-CN/content/developers/overview/github-developer-program.md index 4cd982af16..1497ee957d 100644 --- a/translations/zh-CN/content/developers/overview/github-developer-program.md +++ b/translations/zh-CN/content/developers/overview/github-developer-program.md @@ -1,37 +1,37 @@ --- -title: GitHub Developer Program -intro: 'If you build tools that integrate with {% data variables.product.prodname_dotcom %}, you can join the {% data variables.product.prodname_dotcom %} Developer Program.' +title: GitHub 开发者计划 +intro: '要构建与 {% data variables.product.prodname_dotcom %} 集成的工具，您可以加入 {% data variables.product.prodname_dotcom %} 开发者计划。' redirect_from: - /计划 versions: free-pro-team: '*' --- -Building an application that integrates with GitHub? Register for our Developer Program! The possibilities are endless, and you enjoy the kudos. [Register now](https://github.com/developer/register) +要构建与 GitHub 集成的应用程序？ 请注册我们的开发者计划！ 无尽可能，享受点赞。 [立即注册](https://github.com/developer/register) -## Stay in the know +## 信息灵通 -Be the first to know about API changes and try out new features before they launch in the [Developer blog](https://developer.github.com/changes/). +第一时间了解 API 变更，在[开发者博客](https://developer.github.com/changes/)中发布新功能之前抢先体验。 -## Scratch an itch +## 大显身手 -Build your own tools that seamlessly integrate with the place you push code every day. +构建自己的工具，与每天推送代码的平台无缝集成。 -## Take on the enterprise +## 纳入企业 -[Obtain developer licenses](http://github.com/contact?form%5Bsubject%5D=Development+licenses) to build and test your application against {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}. +[取得开发者许可](http://github.com/contact?form%5Bsubject%5D=Development+licenses)，根据 {% data variables.product.prodname_ghe_server %} 或 {% data variables.product.prodname_ghe_managed %} 构建和测试您的应用程序。 -## Have an integration that works with GitHub? +## 有适用于 GitHub 的集成？ -Awesome! We'd love to have you be part of the program. Here’s how you can spread the word:

      -* [Let us know about your integration](https://github.com/contact?form[subject]=New+GitHub+Integration) -* Use the [Octocat or GitHub logo](https://github.com/logos) to identify that your product works with GitHub -* Post a video or a blog on your website about your integration +太棒了！ 我们希望您加入计划。 以下是您可以使用的推广方式：

      +* [让我们知道您的集成](https://github.com/contact?form[subject]=New+GitHub+Integration) +* 使用 [Octocat 或 GitHub 徽标](https://github.com/logos)来标识您的产品适用于 GitHub +* 在您的网站上发布有关您的集成的视频或博客 -## Ready to join the GitHub Developer Program? +## 准备加入 GitHub 开发者计划吗？ -Membership is open to individual developers and companies who have: +成员资格向满足以下条件的个人开发者和公司开放： -* An integration in production or development using the GitHub API. -* An email address where GitHub users can contact you for support. +* 使用 GitHub API 进行生产或开发中的集成。 +* 提供 GitHub 用户可以联系您以获取支持的电子邮件地址。 diff --git a/translations/zh-CN/content/developers/overview/index.md b/translations/zh-CN/content/developers/overview/index.md index 61dc77d7d8..71ddca7f42 100644 --- a/translations/zh-CN/content/developers/overview/index.md +++ b/translations/zh-CN/content/developers/overview/index.md @@ -1,6 +1,6 @@ --- title: 概览 -intro: 'Learn about {% data variables.product.prodname_dotcom %}''s APIs{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} and secure your deployments.{% else %}, secure your deployments, and join {% data variables.product.prodname_dotcom %}''s Developer Program.{% endif %}' +intro: '了解 {% data variables.product.prodname_dotcom %} 的 API{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 并保护您的部署。{% else %}、保护您的部署并加入 {% data variables.product.prodname_dotcom %} 开发者计划。{% endif %}' versions: free-pro-team: '*' enterprise-server: '*' 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 750d6a3f05..1aeaf49469 100644 --- a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md +++ b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md @@ -1,6 +1,6 @@ --- -title: Managing deploy keys -intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you. +title: 管理部署密钥 +intro: 了解在自动化部署脚本时管理服务器上的 SSH 密钥的不同方法，以及哪种方法最适合您。 redirect_from: - /guides/managing-deploy-keys/ - /v3/guides/managing-deploy-keys @@ -11,48 +11,48 @@ versions: --- -You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users. +在自动执行部署脚本时，您可以使用 SSH 代理转发、HTTPS 结合 OAuth 令牌、部署密钥或机器用户来管理服务器上的 SSH 密钥。 -### SSH agent forwarding +### SSH 代理转发 -In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses. +在许多情况下，尤其是在项目开始时，SSH 代理转发是最快和最简单的方法。 代理转发与本地开发计算机使用相同的 SSH 密钥。 -##### Pros +##### 优点 -* You do not have to generate or keep track of any new keys. -* There is no key management; users have the same permissions on the server that they do locally. -* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys. +* 无需生成或跟踪任何新密钥。 +* 没有密钥管理；用户在服务器上具有与本地相同的权限。 +* 服务器上没有存储密钥，因此，万一服务器受到破坏，您不需要搜索并删除泄露的密钥。 -##### Cons +##### 缺点 -* Users **must** SSH in to deploy; automated deploy processes can't be used. -* SSH agent forwarding can be troublesome to run for Windows users. +* 用户**必须**通过 SSH 进行部署；不能使用自动部署过程。 +* 对于 Windows 用户来说，使用 SSH 代理转发可能比较麻烦。 ##### 设置 -1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information. -2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this: `ssh -A serverA 'bash -s' < deploy.sh` +1. 在本地开启代理转发。 更多信息请参阅[我们的 SSH 代理转发指南][ssh-agent-forwarding]。 +2. 将部署脚本设置为使用代理转发。 例如，在 bash 脚本中，启用代理转发如下所示：`ssh -A serverA 'bash -s' < deploy.sh` -### HTTPS cloning with OAuth tokens +### 使用 OAuth 令牌进行 HTTPS 克隆 -If you don't want to use SSH keys, you can use [HTTPS with OAuth tokens][git-automation]. +如果不想使用 SSH 密钥，您可以使用 [HTTPS 结合 OAuth 令牌][git-automation]。 -##### Pros +##### 优点 -* Anyone with access to the server can deploy the repository. -* Users don't have to change their local SSH settings. -* Multiple tokens (one for each user) are not needed; one token per server is enough. -* A token can be revoked at any time, turning it essentially into a one-use password. -* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization). +* 有权访问服务器的任何人都可以部署仓库。 +* 用户不必更改其本地 SSH 设置。 +* 不需要多个令牌（每个用户一个）；每个服务器一个令牌就足够了。 +* 令牌可随时撤销，本质上变成一次性密码。 +* 可以使用 [OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization) 轻松编写生成新令牌的脚本。 -##### Cons +##### 缺点 -* You must make sure that you configure your token with the correct access scopes. -* Tokens are essentially passwords, and must be protected the same way. +* 必须确保使用正确的访问范围配置令牌。 +* 令牌本质上是密码，必须以同样的方式进行保护。 ##### 设置 -See [our guide on Git automation with tokens][git-automation]. +请参阅[使用令牌的 Git 自动化指南][git-automation]。 ### 部署密钥 @@ -60,33 +60,33 @@ See [our guide on Git automation with tokens][git-automation]. {% data reusables.repositories.deploy-keys-write-access %} -##### Pros +##### 优点 -* Anyone with access to the repository and server has the ability to deploy the project. -* Users don't have to change their local SSH settings. -* Deploy keys are read-only by default, but you can give them write access when adding them to a repository. +* 有权访问仓库和服务器的任何人都能够部署项目。 +* 用户不必更改其本地 SSH 设置。 +* 默认情况下，部署密钥是只读的，但在将它们添加到仓库时，您可以授予其写入权限。 -##### Cons +##### 缺点 -* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server. -* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised. +* 部署密钥只授予对单个仓库的访问权限。 较复杂的项目可能要将多个仓库拉取到同一服务器。 +* 部署密钥通常不受密码保护，因此在服务器遭到破坏时可轻松访问密钥。 ##### 设置 -1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public/private rsa key pair. -2. In the upper-right corner of any {% data variables.product.product_name %} page, click your profile photo, then click **Your profile**. ![Navigation to profile](/assets/images/profile-page.png) -3. On your profile page, click **Repositories**, then click the name of your repository. ![Repositories link](/assets/images/repos.png) -4. From your repository, click **Settings**. ![Repository settings](/assets/images/repo-settings.png) -5. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. ![Add Deploy Keys link](/assets/images/add-deploy-key.png) -6. Provide a title, paste in your public key. ![Deploy Key page](/assets/images/deploy-key.png) -7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository. -8. Click **Add key**. +1. 在服务器上[运行 `ssh-keygen` 进程][generating-ssh-keys]，并记住保存生成的公共/私有 RSA 密钥对的位置。 +2. 在 {% data variables.product.product_name %} 的右上角，单击您的个人资料照片，然后单击 **Your profile（您的个人资料）**。 ![个人资料导航](/assets/images/profile-page.png) +3. 在个人资料页面上，单击 **Repositories（仓库）**，然后单击仓库的名称。 ![仓库链接](/assets/images/repos.png) +4. 在仓库中，单击 **Settings（设置）**。 ![仓库设置](/assets/images/repo-settings.png) +5. 在边栏中，单击 **Deploy Keys（部署密钥）**，然后单击 **Add deploy key（添加部署密钥）**。 ![添加部署密钥链接](/assets/images/add-deploy-key.png) +6. 提供标题，粘贴到公钥中。 ![部署密钥页面](/assets/images/deploy-key.png) +7. 如果希望此密钥拥有对仓库的写入权限，请选择 **Allow write access（允许写入权限）**。 具有写入权限的部署密钥允许将部署推送到仓库。 +8. 单击 **Add key（添加密钥）**。 -##### Using multiple repositories on one server +##### 在一台服务器上使用多个仓库 -If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories. +如果在一台服务器上使用多个仓库，则需要为每个仓库生成专用密钥对。 不能对多个仓库重复使用一个部署密钥。 -In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. 例如： +在服务器的 SSH 配置文件（通常为 `~/.ssh/config`）中，为每个仓库添加一个别名条目。 例如： ```bash Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0 @@ -102,45 +102,45 @@ Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE * `Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias. * `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias. -You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. 例如： +然后可以使用主机名的别名通过 SSH 与仓库进行交互，SSH 将使用分配给该别名的唯一部署密钥。 例如： ```bash $ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git ``` -### Machine users +### 机器用户 -If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). +如果您的服务器需要访问多个仓库，您可以创建一个新的 {% data variables.product.product_name %} 帐户并附加一个专用于自动化的 SSH 密钥。 由于此 {% data variables.product.product_name %} 帐户不会被人类使用，因此称为_机器用户_。 您可以将机器用户添加为个人仓库上的[协作者][collaborator]（授予读取和写入权限）、添加为组织仓库上的[外部协作者][outside-collaborator]（授予读取、写入或管理员权限）或添加到对需要自动化的仓库具有访问权限的[团队][team]（授予团队权限）。 {% if currentVersion == "free-pro-team@latest" %} {% tip %} -**Tip:** Our [terms of service][tos] state: +**提示：**我们的[服务条款][tos]规定： > *不允许通过“自动程序”或其他自动方法注册帐户。* -This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool. +这意味着您不能自动创建帐户。 但是，如果要创建一个机器用户来自动化任务（例如在项目或组织中部署脚本），那就太酷了。 {% endtip %} {% endif %} -##### Pros +##### 优点 -* Anyone with access to the repository and server has the ability to deploy the project. -* No (human) users need to change their local SSH settings. -* Multiple keys are not needed; one per server is adequate. +* 有权访问仓库和服务器的任何人都能够部署项目。 +* 没有（人类）用户需要更改其本地 SSH 设置。 +* 不需要多个密钥；每台服务器一个就足够了。 -##### Cons +##### 缺点 -* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access. -* Machine user keys, like deploy keys, are usually not protected by a passphrase. +* 只有组织才能将机器用户限制为只读访问。 个人仓库始终授予协作者读取/写入权限。 +* 机器用户密钥（如部署密钥）通常不受密码保护。 ##### 设置 -1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account. -2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization. +1. 在服务器上[运行 `ssh-keygen` 进程][generating-ssh-keys]，并将公钥附加到机器用户帐户。 +2. 授予机器用户帐户访问要自动化的仓库的权限。 为此，您可以将帐户添加为[协作者][collaborator]、添加为[外部协作者][outside-collaborator]或添加到组织中的[团队][team]。 [ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/ [generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key diff --git a/translations/zh-CN/content/developers/overview/replacing-github-services.md b/translations/zh-CN/content/developers/overview/replacing-github-services.md index 878a316bd5..987c51456f 100644 --- a/translations/zh-CN/content/developers/overview/replacing-github-services.md +++ b/translations/zh-CN/content/developers/overview/replacing-github-services.md @@ -1,6 +1,6 @@ --- -title: Replacing GitHub Services -intro: 'If you''re still relying on the deprecated {% data variables.product.prodname_dotcom %} Services, learn how to migrate your service hooks to webhooks.' +title: 替换 GitHub 服务 +intro: '如果您仍然依赖已弃用的 {% data variables.product.prodname_dotcom %} 服务，请了解如何将服务挂钩迁移到 web 挂钩。' redirect_from: - /guides/replacing-github-services/ - /v3/guides/automating-deployments-to-integrators/ @@ -11,61 +11,61 @@ versions: --- -We have deprecated GitHub Services in favor of integrating with webhooks. This guide helps you transition to webhooks from GitHub Services. For more information on this announcement, see the [blog post](https://developer.github.com/changes/2018-10-01-denying-new-github-services). +我们弃用了 GitHub 服务，转而支持与 web 挂钩集成。 本指南可帮助您从 GitHub 服务过渡到 web 挂钩。 有关此公告的更多信息，请参阅[博客文章](https://developer.github.com/changes/2018-10-01-denying-new-github-services)。 {% note %} -As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications. +作为电子邮件服务的替代方法，您现在可以开始使用推送到仓库的电子邮件通知。 有关如何配置提交电子邮件通知，请参阅“[关于推送到仓库的电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)”。 {% endnote %} -### Deprecation timeline +### 弃用时间表 -- **October 1, 2018**: GitHub discontinued allowing users to install services. We removed GitHub Services from the GitHub.com user interface. -- **January 29, 2019**: As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications. -- **January 31, 2019**: GitHub will stop delivering installed services' events on GitHub.com. +- **2018 年 10 月 1 日**：GitHub 停止允许用户安装服务。 我们从 GitHub.com 用户界面中删除了 GitHub 服务。 +- **2019 年 1 月 29 日**：作为电子邮件服务的替代方法，您现在可以开始使用推送到仓库的电子邮件通知。 有关如何配置提交电子邮件通知，请参阅“[关于推送到仓库的电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)”。 +- **2019 年 1 月 31 日**：GitHub 将停止在 GitHub.com 上交付已安装服务的事件。 -### GitHub Services background +### GitHub 服务背景信息 -GitHub Services (sometimes referred to as Service Hooks) is the legacy method of integrating where GitHub hosted a portion of our integrator’s services via [the `github-services` repository](https://github.com/github/github-services). Actions performed on GitHub trigger these services, and you can use these services to trigger actions outside of GitHub. +GitHub 服务（有时称为服务挂钩）是传统的集成方法，其中 GitHub 通过[ `github-services` 仓库](https://github.com/github/github-services)托管集成者的部分服务。 在 GitHub 上执行的操作会触发这些服务，您可以使用这些服务在 GitHub 之外触发操作。 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -### Finding repositories that use GitHub Services -We provide a command-line script that helps you identify which repositories on your appliance use GitHub Services. For more information, see [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %} +### 查找使用 GitHub 服务的仓库 +我们提供命令行脚本，帮助您识别设备上哪些仓库使用 GitHub 服务。 更多信息请参阅 [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report)。{% endif %} -### GitHub Services vs. webhooks +### GitHub 服务与 web 挂钩 -The key differences between GitHub Services and webhooks: -- **Configuration**: GitHub Services have service-specific configuration options, while webhooks are simply configured by specifying a URL and a set of events. -- **Custom logic**: GitHub Services can have custom logic to respond with multiple actions as part of processing a single event, while webhooks have no custom logic. -- **Types of requests**: GitHub Services can make HTTP and non-HTTP requests, while webhooks can make HTTP requests only. +GitHub 服务与 web 挂钩之间的主要区别： +- **配置**：GitHub 服务具有特定于服务的配置选项，而 web 挂钩只需指定 URL 和一组事件即可进行配置。 +- **自定义逻辑**：GitHub 服务可以具有自定义逻辑，在处理单个事件时使用多个操作进行响应，而 web 挂钩没有自定义逻辑。 +- **服务类型**：GitHub 服务可以发出 HTTP 和非 HTTP 请求，而 web 挂钩只能发出 HTTP 请求。 -### Replacing Services with webhooks +### 用 web 挂钩替换服务 -To replace GitHub Services with Webhooks: +要用 web 挂钩替换 GitHub 服务: -1. Identify the relevant webhook events you’ll need to subscribe to from [this list](/webhooks/#events). +1. 从[此列表](/webhooks/#events)确定您需要订阅的相关 web 挂钩事件。 -2. Change your configuration depending on how you currently use GitHub Services: +2. 根据您当前如何使用 GitHub 服务更改您的配置： - - **GitHub Apps**: Update your app's permissions and subscribed events to configure your app to receive the relevant webhook events. - - **OAuth Apps**: Request either the `repo_hook` and/or `org_hook` scope(s) to manage the relevant events on behalf of users. - - **GitHub Service providers**: Request that users manually configure a webhook with the relevant events sent to you, or take this opportunity to build an app to manage this functionality. For more information, see "[About apps](/apps/about-apps/)." + - **GitHub 应用程序**：更新应用程序的权限和订阅的事件，以配置应用程序接收相关的 web 挂钩事件。 + - **OAuth 应用程序**：请求 `repo_hook` 和/或 `org_hook` 作用域以代表用户管理相关事件。 + - **GitHub 服务提供商**：请求用户手动配置包含发送给您的相关事件的 web 挂钩，或者借此机会构建一个应用程序来管理此功能。 更多信息请参阅“[关于应用程序](/apps/about-apps/)”。 -3. Move additional configuration from outside of GitHub. Some GitHub Services require additional, custom configuration on the configuration page within GitHub. If your service does this, you will need to move this functionality into your application or rely on GitHub or OAuth Apps where applicable. +3. 从 GitHub 外部移动额外配置。 某些 GitHub 服务需要在 GitHub 中的配置页面上进行额外的自定义配置。 如果您的服务这样做，则需要将此功能移动到应用程序中，或在适用的情况下依赖 GitHub 或 OAuth 应用程序。 -### Supporting {% data variables.product.prodname_ghe_server %} +### 支持 {% data variables.product.prodname_ghe_server %} -- **{% data variables.product.prodname_ghe_server %} 2.17**: {% data variables.product.prodname_ghe_server %} release 2.17 and higher will discontinue allowing admins to install services. Admins will continue to be able to modify existing service hooks and receive service hooks in {% data variables.product.prodname_ghe_server %} release 2.17 through 2.19. As an alternative to the email service, you will be able to use email notifications for pushes to your repository in {% data variables.product.prodname_ghe_server %} 2.17 and higher. See [this blog post](https://developer.github.com/changes/2019-01-29-life-after-github-services) to learn more. -- **{% data variables.product.prodname_ghe_server %} 2.20**: {% data variables.product.prodname_ghe_server %} release 2.20 and higher will stop delivering all installed services' events. +- **{% data variables.product.prodname_ghe_server %} 2.17**：{% data variables.product.prodname_ghe_server %} 2.17 及更高版本将停止允许管理员安装服务。 在 {% data variables.product.prodname_ghe_server %} 2.17 至 2.19 版本中，管理员仍然能够修改现有服务挂钩和接收服务挂钩。 在 {% data variables.product.prodname_ghe_server %} 2.17 及更高版本中，作为电子邮件服务的替代方法，您将能够使用推送到仓库的电子邮件通知。 更多信息请参阅[这篇博客文章](https://developer.github.com/changes/2019-01-29-life-after-github-services)。 +- **{% data variables.product.prodname_ghe_server %} 2.20**：{% data variables.product.prodname_ghe_server %} 2.20 及更高版本将停止交付所有已安装服务的事件。 -The {% data variables.product.prodname_ghe_server %} 2.17 release will be the first release that does not allow admins to install GitHub Services. We will only support existing GitHub Services until the {% data variables.product.prodname_ghe_server %} 2.20 release. We will also accept any critical patches for your GitHub Service running on {% data variables.product.prodname_ghe_server %} until October 1, 2019. +{% data variables.product.prodname_ghe_server %} 2.17 版将是不允许管理员安装 GitHub 服务的第一个版本。 我们将仅支持现有的 GitHub 服务，直到 {% data variables.product.prodname_ghe_server %} 2.20 版本。 我们还将接受 {% data variables.product.prodname_ghe_server %} 上运行的 GitHub 服务的任何重要补丁，直到 2019 年 10 月 1 日。 -### Migrating with our help +### 在我们的帮助下迁移 -Please [contact us](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) with any questions. +如有任何问题，请[联系我们](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation)。 -As a high-level overview, the process of migration typically involves: - - Identifying how and where your product is using GitHub Services. - - Identifying the corresponding webhook events you need to configure in order to move to plain webhooks. - - Implementing the design using either [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/) or [{% data variables.product.prodname_github_app %}s. {% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) are preferred. To learn more about why {% data variables.product.prodname_github_app %}s are preferred, see "[Reasons for switching to {% data variables.product.prodname_github_app %}s](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)." +作为高度概述，迁移过程通常涉及： + - 确定产品使用 GitHub 服务的方式和位置。 + - 确定需要配置的相应 web 挂钩事件，以便移动到普通 web 挂钩。 + - 使用 [{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/) 或 [{% data variables.product.prodname_github_app %} 实现设计。 {% data variables.product.prodname_github_app %}](/apps/building-github-apps/) 优先。 要了解为什么优先使用 {% data variables.product.prodname_github_app %}，请参阅“[切换到 {% data variables.product.prodname_github_app %} 的原因](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)”。 diff --git a/translations/zh-CN/content/developers/overview/secret-scanning.md b/translations/zh-CN/content/developers/overview/secret-scanning.md index 3b4eeaec1c..eb3e2161cf 100644 --- a/translations/zh-CN/content/developers/overview/secret-scanning.md +++ b/translations/zh-CN/content/developers/overview/secret-scanning.md @@ -1,6 +1,6 @@ --- title: 秘密扫描 -intro: 'As a service provider, you can partner with {% data variables.product.prodname_dotcom %} to have your secret token formats secured through secret scanning, which searches for accidental commits of your secret format and can be sent to a service provider''s verify endpoint.' +intro: '作为服务提供者，您可以与 {% data variables.product.prodname_dotcom %} 合作，通过密码扫描保护您的密码令牌格式，该扫描将搜索意外提交的密码格式，并且可以发送到服务提供者的验证端点。' redirect_from: - /partnerships/token-scanning/ - /partnerships/secret-scanning @@ -9,57 +9,57 @@ versions: --- -{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. Secret scanning happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our secret scanning. +{% data variables.product.prodname_dotcom %} 扫描仓库查找已知的密码格式，以防止欺诈性使用意外提交的凭据。 默认情况下，密码扫描发生在公共仓库上，但仓库管理员或组织所有者可以在私有仓库上启用它。 作为服务提供者，您可以与 {% data variables.product.prodname_dotcom %} 合作，让您的密码格式包含在我们的密码扫描中。 -When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice. +在公共仓库中找到密码格式的匹配项时，将发送有效负载到您选择的 HTTP 端点。 -When a match of your secret format is found in a private repository configured for secret scanning, then repository admins are alerted and can view and manage the secret scanning results on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from secret scanning](/github/administering-a-repository/managing-alerts-from-secret-scanning)". +在配置为密码扫描的私有仓库中找到密码格式的匹配项时，仓库管理员将收到警报，并且可以查看和管理 {% data variables.product.prodname_dotcom %} 上的密码扫描结果。 更多信息请参阅“[管理来自密码扫描的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)”。 {% note %} -**Note:** Secret scanning 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 secret scanning program. +本文介绍作为服务提供者如何与 {% data variables.product.prodname_dotcom %} 合作并加入密码扫描计划。 -### The secret scanning process +### 密码扫描流程 -##### How secret scanning works in a public repository +##### 密码扫描在公共仓库中的工作方式 -The following diagram summarizes the secret scanning process for public repositories, with any matches sent to a service provider's verify endpoint. +下图总结了在公共仓库中进行密码扫描并将任何匹配项发送到服务提供者的验证端点的流程。 -![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "Secret scanning flow") +![显示扫描密码并向服务提供者的验证端点发送匹配项的流程图](/assets/images/secret-scanning-flow.png "密码扫描流程") -### Joining the secret scanning program on {% data variables.product.prodname_dotcom %} +### 在 {% data variables.product.prodname_dotcom %} 上加入密码扫描计划 -1. Contact {% data variables.product.prodname_dotcom %} to get the process started. -1. Identify the relevant secrets you want to scan for and create regular expressions to capture them. -1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the secret scanning message payload. -1. Implement signature verification in your secret alert service. -1. Implement secret revocation and user notification in your secret alert service. +1. 联系 {% data variables.product.prodname_dotcom %} 以启动流程。 +1. 识别要扫描的相关密码，并创建正则表达式来捕获它们。 +1. 针对在公共仓库中发现的密码匹配项，创建一个密码警报服务，以便从 {% data variables.product.prodname_dotcom %} 接受包含密码扫描消息有效负载的 web 挂钩。 +1. 在密码警报服务中实施签名验证。 +1. 在密码警报服务中实施密码撤销和用户通知。 -#### Contact {% data variables.product.prodname_dotcom %} to get the process started +#### 联系 {% data variables.product.prodname_dotcom %} 以启动流程 -To get the enrollment process started, email secret-scanning@github.com. +要启动注册流程，请发送电子邮件至 secret-scanning@github.com。 -You will receive details on the secret scanning program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. +您将收到有关密码扫描计划的详细信息，您需要同意 {% data variables.product.prodname_dotcom %} 的参与条款才能继续。 -#### Identify your secrets and create regular expressions +#### 识别您的密码并创建正则表达式 -To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the secret scanning program: +要扫描您的密码，{% data variables.product.prodname_dotcom %} 需要您要包含在密码扫描计划中的每个密码的以下信息： -* A unique, human readable name for the secret type. We'll use this to generate the `Type` value in the message payload later. -* A regular expression which finds the secret type. Be as precise as possible, because this will reduce the number of false positives. -* The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. This does not have to be unique for each secret type. +* 密码类型的唯一、人类可读的名称。 稍后我们将使用它来生成消息有效负载中的 `Type` 值。 +* 查找密码类型的正则表达式。 尽可能精确，因为这样可以减少误报的数量。 +* 从 {% data variables.product.prodname_dotcom %} 接收消息的端点的 URL。 对于每个密码类型，这不必是唯一的。 -Send this information to secret-scanning@github.com. +将此信息发送到 secret-scanning@github.com。 -#### Create a secret alert service +#### 创建密码警报服务 -Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send a HTTP `POST` message to your endpoint. +在您提供给我们的 URL 上创建一个可访问互联网的公共 HTTP 端点。 在公共仓库中找到正则表达式的匹配项时，{% data variables.product.prodname_dotcom %} 将发送 HTTP `POST` 消息到您的端点。 -##### Example POST sent to your endpoint +##### 发送到端点的 POST 示例 ``` POST / HTTP/1.1 @@ -79,21 +79,21 @@ Content-Length: 0123 ] ``` -The message body is a JSON array that contains one or more objects with the following contents. When multiple matches are found, {% data variables.product.prodname_dotcom %} may send a single message with more than one secret match. Your endpoint should be able to handle requests with a large number of matches without timing out. +消息正文是一个 JSON 数组，其中包含一个或多个具有以下内容的对象。 找到多个匹配项时，{% data variables.product.prodname_dotcom %} 可能发送一条包含多个密码匹配项的消息。 您的端点应该能够在不超时的情况下处理包含大量匹配项的请求。 -* **Token**: The value of the secret match. -* **Type**: The unique name you provided to identify your regular expression. -* **URL**: The public commit URL where the match was found. +* **令牌**：密码匹配项的值。 +* **类型**：您提供的用于识别正则表达式的唯一名称。 +* **URL**：在其中找到匹配项的公共提交 URL。 -#### Implement signature verification in your secret alert service +#### 在密码警报服务中实施签名验证 -We strongly recommend you implement signature validation in your secret alert service to ensure that the messages you receive are genuinely from {% data variables.product.prodname_dotcom %} and not malicious. +我们强烈建议您在密码警报服务中实施签名验证，以确保您收到的消息确实来自 {% data variables.product.prodname_dotcom %}，而不是恶意消息。 -You can retrieve the {% data variables.product.prodname_dotcom %} secret scanning public key from https://api.github.com/meta/public_keys/secret_scanning and validate the message using the `ECDSA-NIST-P256V1-SHA256` algorithm. +您可以从 https://api.github.com/meta/public_keys/secret_scanning 检索 {% data variables.product.prodname_dotcom %} 密码扫描公钥，并使用 `ECDSA-NIST-P256V1-SHA256` 算法验证消息。 -Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. The code also assumes you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens). The token does not need any permissions set. +假设您收到以下消息，下面的代码段演示如何执行签名验证。 该代码还假设您已经使用生成的 PAT 设置了一个名为 `GITHUB_PRODUCTION_TOKEN` 的环境变量 (https://github.com/settings/tokens)。 该令牌不需要设置任何权限。 -**Sample message sent to verify endpoint** +**发送到验证端点的消息示例** ``` POST / HTTP/1.1 Host: HOST @@ -106,7 +106,7 @@ Content-Length: 0000 [{"token": "some_token", "type": "some_type", "url": "some_url"}] ``` -**Validation sample in Go** +**Go 中的验证示例** ```golang package main @@ -277,7 +277,7 @@ type asn1Signature struct { } ``` -**Validation sample in Ruby** +**Ruby 中的验证示例** ```ruby require 'openssl' require 'net/http' @@ -317,6 +317,6 @@ openssl_key = OpenSSL::PKey::EC.new(current_key) puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), payload.chomp) ``` -#### Implement secret revocation and user notification in your secret alert service +#### 在密码警报服务中实施密码撤销和用户通知 -For secret scanning in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. +对于公共仓库中的密码扫描，您可以增强密码警报服务，以撤销泄露的密码并通知受影响的用户。 如何在密码警报服务中实现此功能取决于您，但我们建议您考虑 {% data variables.product.prodname_dotcom %}向您发送的公开和泄露示警消息所涉及的任何密码。 diff --git a/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md b/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md index 349ab10e0d..ed6a7a2af6 100644 --- a/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md +++ b/translations/zh-CN/content/developers/overview/using-ssh-agent-forwarding.md @@ -1,6 +1,6 @@ --- -title: Using SSH agent forwarding -intro: 'To simplify deploying to a server, you can set up SSH agent forwarding to securely use local SSH keys.' +title: 使用 SSH 代理转发 +intro: '为简化向服务器的部署，您可以设置 SSH 代理转发以安全地使用本地 SSH 密钥。' redirect_from: - /guides/using-ssh-agent-forwarding/ - /v3/guides/using-ssh-agent-forwarding @@ -12,17 +12,17 @@ versions: -SSH agent forwarding can be used to make deploying to a server simple. It allows you to use your local SSH keys instead of leaving keys (without passphrases!) sitting on your server. +SSH 代理转发可用于简化向服务器的部署。 它允许您使用本地 SSH 密钥，而不是将密钥（不带密码！）放在服务器上。 -If you've already set up an SSH key to interact with {% data variables.product.product_name %}, you're probably familiar with `ssh-agent`. It's a program that runs in the background and keeps your key loaded into memory, so that you don't need to enter your passphrase every time you need to use the key. The nifty thing is, you can choose to let servers access your local `ssh-agent` as if they were already running on the server. This is sort of like asking a friend to enter their password so that you can use their computer. +如果已设置 SSH 密钥 来与 {% data variables.product.product_name %} 交互，您可能已经熟悉了 `ssh-agent`。 这是一个在后台运行的程序，它将密钥加载到内存中，因此您不需要每次使用密钥时都输入密码。 最妙的是，您可以选择让服务器访问您的本地 `ssh-agent`，就像它们已经在服务器上运行一样。 这有点像要求朋友输入他们的密码，以便您可以使用他们的计算机。 -Check out [Steve Friedl's Tech Tips guide][tech-tips] for a more detailed explanation of SSH agent forwarding. +有关 SSH 代理转发的更详细说明，请参阅 [Steve Friedl 的技术提示指南][tech-tips]。 -### Setting up SSH agent forwarding +### 设置 SSH 代理转发 -Ensure that your own SSH key is set up and working. You can use [our guide on generating SSH keys][generating-keys] if you've not done this yet. +确保您自己的 SSH 密钥已设置并正常运行。 如果您还没有 SSH 密钥，请使用[我们的 SSH 密钥生成指南][generating-keys]。 -You can test that your local key works by entering `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}` in the terminal: +您可以在终端输入 `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}主机名{% else %}github.com{% endif %}` 来测试您的本地密钥是否有效： ```shell $ ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %} @@ -31,26 +31,26 @@ $ ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVe > shell access. ``` -We're off to a great start. Let's set up SSH to allow agent forwarding to your server. +开局不错。 让我们设置 SSH 以允许代理转发到您的服务器。 -1. Using your favorite text editor, open up the file at `~/.ssh/config`. If this file doesn't exist, you can create it by entering `touch ~/.ssh/config` in the terminal. +1. 使用您喜欢的文本编辑器打开位于 `~/.ssh/config` 的文件。 如果此文件不存在，您可以通过在终端输入 `touch ~/.ssh/config` 来创建它。 -2. Enter the following text into the file, replacing `example.com` with your server's domain name or IP: +2. 在文件中输入以下文本，将 `example.com` 替换为服务器的域名或 IP： Host example.com ForwardAgent yes {% warning %} -**Warning:** You may be tempted to use a wildcard like `Host *` to just apply this setting to all SSH connections. That's not really a good idea, as you'd be sharing your local SSH keys with *every* server you SSH into. They won't have direct access to the keys, but they will be able to use them *as you* while the connection is established. **You should only add servers you trust and that you intend to use with agent forwarding.** +**警告：**您可能想使用 `Host *` 这样的通配符将此设置应用于所有 SSH 连接。 但这并不是一个好主意，因为您将与 SSH 到的*每台*服务器共享您的本地 SSH 密钥。 它们无法直接访问密钥，但是在建立连接后，它们可以*像您一样*使用这些密钥。 **您应该只添加您信任的服务器以及打算用于代理转发的服务器。** {% endwarning %} -### Testing SSH agent forwarding +### 测试 SSH 代理转发 -To test that agent forwarding is working with your server, you can SSH into your server and run `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}hostname{% else %}github.com{% endif %}` once more. If all is well, you'll get back the same prompt as you did locally. +要测试代理转发是否对您的服务器有效，您可以 SSH 到服务器，然后再次运行 `ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}主机名{% else %}github.com{% endif %}`。 如果一切正常，您将收到与本地使用相同的提示。 -If you're unsure if your local key is being used, you can also inspect the `SSH_AUTH_SOCK` variable on your server: +如果不确定是否在使用本地密钥，您还可以检查服务器上的 `SSH_AUTH_SOCK` 变量： ```shell $ echo "$SSH_AUTH_SOCK" @@ -58,7 +58,7 @@ $ echo "$SSH_AUTH_SOCK" > /tmp/ssh-4hNGMk8AZX/agent.79453 ``` -If the variable is not set, it means that agent forwarding is not working: +如果未设置变量，则表示代理转发不起作用： ```shell $ echo "$SSH_AUTH_SOCK" @@ -69,13 +69,13 @@ $ ssh -T git@{% if enterpriseServerVersions contains currentVersion or currentVe > Permission denied (publickey). ``` -### Troubleshooting SSH agent forwarding +### SSH 代理转发疑难解答 -Here are some things to look out for when troubleshooting SSH agent forwarding. +以下是排查 SSH 代理转发时需要注意的一些事项。 -#### You must be using an SSH URL to check out code +#### 您必须使用 SSH URL 检出代码 -SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/config* file on your server and ensure the URL is an SSH-style URL like below: +SSH 转发仅适用于 SSH URL，而不是 HTTP(s) URL。 检查服务器上的 *.git/config* 文件，并确保 URL 是 SSH 样式的 URL，如下所示： ```shell [remote "origin"] @@ -83,13 +83,13 @@ SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/confi fetch = +refs/heads/*:refs/remotes/origin/* ``` -#### Your SSH keys must work locally +#### 您的 SSH 密钥必须在本地有效 -Before you can make your keys work through agent forwarding, they must work locally first. [Our guide on generating SSH keys][generating-keys] can help you set up your SSH keys locally. +在通过代理转发使密钥起作用之前，它们必须首先在本地有效。 [我们的 SSH 密钥生成指南][generating-keys]可帮助您在本地设置 SSH 密钥。 -#### Your system must allow SSH agent forwarding +#### 您的系统必须允许 SSH 代理转发 -Sometimes, system configurations disallow SSH agent forwarding. You can check if a system configuration file is being used by entering the following command in the terminal: +有时，系统配置不允许 SSH 代理转发。 您可以通过在终端中输入以下命令来检查是否正在使用系统配置文件： ```shell $ ssh -v example.com @@ -103,7 +103,7 @@ $ exit # Returns to your local command prompt ``` -In the example above, the file *~/.ssh/config* is loaded first, then */etc/ssh_config* is read. We can inspect that file to see if it's overriding our options by running the following commands: +在上面的示例中，先加载 *~/.ssh/config* 文件，然后读取 */etc/ssh_config* 文件。 通过运行以下命令，我们可以检查该文件以查看它是否覆盖了我们的选项： ```shell $ cat /etc/ssh_config @@ -113,17 +113,17 @@ $ cat /etc/ssh_config > ForwardAgent no ``` -In this example, our */etc/ssh_config* file specifically says `ForwardAgent no`, which is a way to block agent forwarding. Deleting this line from the file should get agent forwarding working once more. +在此示例中，我们的 */etc/ssh_config* 文件特别表示 `ForwardAgent no`，这是一种阻止代理转发的方式。 从文件中删除此行应该会使代理转发再次起作用。 -#### Your server must allow SSH agent forwarding on inbound connections +#### 您的服务器必须允许入站连接上的 SSH 代理转发 -Agent forwarding may also be blocked on your server. You can check that agent forwarding is permitted by SSHing into the server and running `sshd_config`. The output from this command should indicate that `AllowAgentForwarding` is set. +代理转发也可能在您的服务器上被阻止。 您可以通过 SSH 到服务器并运行 `sshd_config` 来检查是否允许代理转发。 此命令的输出应指示 `AllowAgentForwarding` 已设置。 -#### Your local `ssh-agent` must be running +#### 您的本地 `ssh-agent` 必须正在运行 -On most computers, the operating system automatically launches `ssh-agent` for you. On Windows, however, you need to do this manually. We have [a guide on how to start `ssh-agent` whenever you open Git Bash][autolaunch-ssh-agent]. +在大多数计算机上，操作系统会自动为您启动 `ssh-agent`。 但是在 Windows 上，您需要手动执行此操作。 我们提供了[在每次打开 Git Bash 时如何启动 `ssh-agent` 的指南][autolaunch-ssh-agent]。 -To verify that `ssh-agent` is running on your computer, type the following command in the terminal: +要验证 `ssh-agent` 是否正在您的计算机上运行，请在终端中键入以下命令： ```shell $ echo "$SSH_AUTH_SOCK" @@ -131,15 +131,15 @@ $ echo "$SSH_AUTH_SOCK" > /tmp/launch-kNSlgU/Listeners ``` -#### Your key must be available to `ssh-agent` +#### 您的密钥必须可用于 `ssh-agent` -You can check that your key is visible to `ssh-agent` by running the following command: +您可以通过运行以下命令来检查您的密钥是否对 `ssh-agent` 可见： ```shell ssh-add -L ``` -If the command says that no identity is available, you'll need to add your key: +如果命令说没有身份可用，则需要添加密钥： ```shell $ ssh-add yourkey @@ -147,7 +147,7 @@ $ ssh-add yourkey {% tip %} -On Mac OS X, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command: +在 Mac OS X 上，一旦在重新引导过程中重新启动 `ssh-agent`，它将“忘记”该密钥。 但是，您可以使用此命令将 SSH 密钥导入密钥链： ```shell $ ssh-add -K yourkey @@ -157,5 +157,4 @@ $ ssh-add -K yourkey [tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html [generating-keys]: /articles/generating-ssh-keys -[generating-keys]: /articles/generating-ssh-keys [autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows diff --git a/translations/zh-CN/content/developers/webhooks-and-events/about-webhooks.md b/translations/zh-CN/content/developers/webhooks-and-events/about-webhooks.md index 8856911048..c0f571fe2a 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/about-webhooks.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/about-webhooks.md @@ -1,6 +1,6 @@ --- title: 关于 web 挂钩 -intro: Learn the basics of how webhooks work to help you build and set up integrations. +intro: 了解 Webhook 如何帮助您构建和设置集成的基础知识。 redirect_from: - /webhooks versions: @@ -10,25 +10,25 @@ versions: --- -Webhooks allow you to build or set up integrations, such as [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), which subscribe to certain events on GitHub.com. When one of those events is triggered, we'll send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. You're only limited by your imagination. +Web 挂钩允许您构建或设置集成，例如 [{% data variables.product.prodname_github_app %}](/apps/building-github-apps/) 或 [{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/)，以订阅 GitHub.com 上的某些事件。 当触发其中某个事件时，我们将向 web 挂钩的配置 URL 发送 HTTP POST 有效负载。 Web 挂钩可用于更新外部议题跟踪器、触发 CI 构建、更新备份镜像，甚至部署到生产服务器。 您只受想象力的限制。 -Webhooks can be installed on{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} an [organization][org-hooks], a specific [repository][repo-hooks], or a {% data variables.product.prodname_github_app %}. Once installed, the webhook will be sent each time one or more subscribed events occurs. +Web 挂钩可以安装在{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/)、{% endif %}[组织][org-hooks]、特定[仓库][repo-hooks]或 {% data variables.product.prodname_github_app %} 上。 安装后，每当发生一个或多个订阅事件时，都会发送 web 挂钩。 -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 %} +您可以为每个安装目标{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}（{% data variables.product.prodname_ghe_server %}实例、特定组织或特定仓库）{% else %}（特定组织或特定仓库）{% endif %}上的每个事件创建最多 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}250{% else %}20{% endif %} 个 web 挂钩。 ### 事件 {% 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. +每个事件对应于您的组织和/或仓库可能发生的一组特定操作。 例如，如果您订阅了 `issues`，则每当议题被打开、关闭、标记等操作时，您都会收到详细的有效负载。 -See "[Webhook event payloads](/webhooks/event-payloads)" for the list of available webhook events and their payloads. +有关可用的 web 挂钩事件及其有效负载的列表，请参阅“[web 挂钩事件有效负载](/webhooks/event-payloads)”。 -### Ping event +### Ping 事件 {% data reusables.webhooks.ping_short_desc %} -For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. +有关 `ping` 事件 web 挂钩有效负载的更多信息，请参阅 [`ping`](/webhooks/event-payloads/#ping) 事件。 [org-hooks]: /rest/reference/orgs#webhooks/ [repo-hooks]: /rest/reference/repos#hooks diff --git a/translations/zh-CN/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md index 63a28f53f1..8be52ff367 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/configuring-your-server-to-receive-payloads.md @@ -1,6 +1,6 @@ --- -title: Configuring your server to receive payloads -intro: Learn to set up a server to manage incoming webhook payloads. +title: 配置服务器以接收有效负载 +intro: 了解如何设置服务器来管理传入的 web 挂钩有效负载。 redirect_from: - /webhooks/configuring versions: @@ -11,31 +11,31 @@ versions: -Now that our webhook is ready to deliver messages, we'll set up a basic Sinatra server to handle incoming payloads. +现在，我们的 web 挂钩已准备好传递消息，我们将设置一个基本的 Sinatra 服务器 来处理传入的有效负载。 -Recall that we specifically set our webhook URL to `http://localhost:4567/payload`. Since we're developing locally, we'll need to expose our local development environment to the Internet, so that GitHub can send out messages, and our local server can process them. +回想一下，我们专门将 web 挂钩 URL 设置为 `http://localhost:4567/payload`。 由于我们在本地进行开发，因此我们需要将本地开发环境暴露给互联网，以便 GitHub 可以发送消息，而我们的本地服务器可以处理它们。 注：您可以[从平台样本仓库][platform samples]下载此项目的完整源代码。 -### Using ngrok +### 使用 ngrok -First, we'll install a program to expose our local host to the Internet. We'll use ngrok to do this. [ngrok is a free download](https://ngrok.com/download) available for all major operating systems. +首先，我们将安装一个程序，将本地主机暴露给互联网。 我们将使用 ngrok 实现此目的。 [ngrok 可免费下载](https://ngrok.com/download)，适用于所有主流操作系统。 -When you're done with that, you can expose your localhost by running `./ngrok http 4567` on the command line. You should see a line that looks something like this: +完成此工作后，您可以在命令行上运行 `./ngrok http 4567` 以暴露本地主机。 您应该会看到如下所示的行： ```shell $ Forwarding http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567 ``` -Copy that funky `*.ngrok.io` URL! We're now going to go *back* to the Payload URL and pasting this server into that field. It should look something like `http://7e9ea9dc.ngrok.io/payload`. +复制那个不寻常的 `*.ngrok.io` URL！ 现在，我们将*回到*有效负载 URL，并将此服务器粘贴到该字段中。 它应该如下所示：`http://7e9ea9dc.ngrok.io/payload`。 -By doing this, we've set ourselves up to expose our localhost at path `/payload` to the Internet. +通过这些设置，我们就将路径 `/payload` 上的本地主机暴露给了互联网。 -### Writing the server +### 编写服务器 -Now comes the fun part! We want our server to listen to `POST` requests, at `/payload`, because that's where we told GitHub our webhook URL was. Since ngrok is exposing our local environment, we don't need to set up a real server somewhere online, and can happily test out our code locally. +有趣的来了！ 我们希望服务器在 `/payload` 处侦听 `POST` 请求，因为这是我们告诉 GitHub 我们的 web 挂钩 URL 所在位置。 由于 ngrok 在暴露我们的本地环境，因此我们无需在线上某个位置设置真正的服务器，就可以在本地愉快地测试我们的代码。 -Let's set up a little Sinatra app to do something with the information. Our initial setup might look something like this: +让我们设置一个小 Sinatra 应用程序来处理信息。 我们的初始设置可能如下所示： ``` ruby require 'sinatra' @@ -51,7 +51,7 @@ end 启动此服务器。 -Since we set up our webhook to listen to events dealing with `Issues`, go ahead and create a new Issue on the repository you're testing with. Once you create it, switch back to your terminal. You should see something like this in your output: +我们已经设置了 web 挂钩来侦听涉及 `Issues` 的事件，现在，我们在要测试的仓库上创建一个新议题。 创建后，切换回终端。 您应该会在输出中看到以下内容： ```shell $ ~/Developer/platform-samples/hooks/ruby/configuring-your-server $ ruby server.rb @@ -62,9 +62,9 @@ $ ~/Developer/platform-samples/hooks/ruby/configuring-your-server $ ruby server. > I got some JSON: {"action"=>"opened", "issue"=>{"url"=>"... ``` -Success! You've successfully configured your server to listen to webhooks. Your server can now process this information any way you see fit. For example, if you were setting up a "real" web application, you might want to log some of the JSON output to a database. +成功！ 您已成功配置服务器以侦听 web 挂钩。 您的服务器现在可以按照您认为合适的任何方式处理此信息。 例如，如果要设置“真实的” Web 应用程序，则可能需要将一些 JSON 输出记录到数据库中。 -For additional information on working with webhooks for fun and profit, head on over to the [Testing Webhooks](/webhooks/testing) guide. +有关使用 web 挂钩的乐趣和好处的更多信息，请参阅[测试 web 挂钩](/webhooks/testing)指南。 [platform samples]: https://github.com/github/platform-samples/tree/master/hooks/ruby/configuring-your-server [Sinatra]: http://www.sinatrarb.com/ diff --git a/translations/zh-CN/content/developers/webhooks-and-events/creating-webhooks.md b/translations/zh-CN/content/developers/webhooks-and-events/creating-webhooks.md index b52573e1b7..faf0cd5e46 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/creating-webhooks.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/creating-webhooks.md @@ -1,6 +1,6 @@ --- -title: Creating webhooks -intro: 'Learn to build a webhook, choosing the events your webhook will listen for on {% data variables.product.prodname_dotcom %} and how to set up a server to receive and manage the webhook payload.' +title: 创建 web 挂钩 +intro: '了解如何构建 web 挂钩，选择 web 挂钩将在 {% data variables.product.prodname_dotcom %} 上侦听的事件，以及如何设置服务器以接收和管理 web 挂钩负载。' redirect_from: - /webhooks/creating versions: @@ -11,48 +11,48 @@ versions: -Now that we understand [the basics of webhooks][webhooks-overview], let's go through the process of building out our own webhook powered integration. In this tutorial, we'll create a repository webhook that will be responsible for listing out how popular our repository is, based on the number of Issues it receives per day. +我们已了解 [web 挂钩的基础知识][webhooks-overview]，现在我们来构建自己的 web 挂钩支持的集成。 在本教程中，我们将创建一个仓库 web 挂钩，它将负责根据仓库每天收到的议题数量列出仓库的受欢迎程度。 -Creating a webhook is a two-step process. You'll first need to set up how you want your webhook to behave through {% data variables.product.product_name %}--what events should it listen to. After that, you'll set up your server to receive and manage the payload. +创建 web 挂钩是一个两步过程。 首先需要设置 web 挂钩通过 {% data variables.product.product_name %} 实施的行为 - 它应该侦听哪些事件。 之后，您将设置服务器以接收和管理有效负载。 {% data reusables.webhooks.webhooks-rest-api-links %} -### Setting up a Webhook +### 设置 web 挂钩 -You can install webhooks on an organization or on a specific repository. +您可以在组织或特定仓库上安装 web 挂钩。 -To set up a webhook, go to the settings page of your repository or organization. From there, click **Webhooks**, then **Add webhook**. +要设置 web 挂钩，请转到仓库或组织的设置页面。 在那里，单击 **Webhooks（web 挂钩）**，然后单击 **Add webhook（添加 web 挂钩）**。 -Alternatively, you can choose to build and manage a webhook [through the Webhooks API][webhook-api]. +或者，您可以选择[通过 web 挂钩 API][webhook-api] 来构建和管理 web 挂钩。 -Webhooks require a few configuration options before you can make use of them. We'll go through each of these settings below. +Web 挂钩需要设置几个配置选项才能使用。 我们将在下面介绍所有这些设置。 -### Payload URL +### 有效负载 URL {% data reusables.webhooks.payload_url %} -Since we're developing locally for our tutorial, let's set it to `http://localhost:4567/payload`. We'll explain why in the [Configuring Your Server](/webhooks/configuring/) docs. +由于在本教程中，我们将在本地开发，因此将其设置为 `http://localhost:4567/payload`。 我们将在[配置服务器](/webhooks/configuring/)文档中解释原因。 -### Content Type +### 内容类型 -{% data reusables.webhooks.content_type %} For this tutorial, the default content type of `application/json` is fine. +{% data reusables.webhooks.content_type %} 在本教程中，可以使用默认内容类型 `application/json`。 -### Secret +### 密钥 {% data reusables.webhooks.secret %} -### SSL Verification +### SSL 验证 {% data reusables.webhooks.webhooks_ssl %} ### 已激活 -By default, webhook deliveries are "Active." You can choose to disable the delivery of webhook payloads by deselecting "Active." +默认情况下，web 挂钩交付为“Active（激活）”。 您可以通过取消选择“Active（激活）”来选择禁用 web 挂钩交付。 ### 事件 -Events are at the core of webhooks. These webhooks fire whenever a certain action is taken on the repository, which your server's payload URL intercepts and acts upon. +事件是 web 挂钩的核心。 当仓库上发生特定操作时，就会触发这些 web 挂钩，而服务器的有效负载 URL 会截获它们并采取行动。 A full list of webhook events, and when they execute, can be found in [the webhooks API][hooks-api] reference. diff --git a/translations/zh-CN/content/developers/webhooks-and-events/testing-webhooks.md b/translations/zh-CN/content/developers/webhooks-and-events/testing-webhooks.md index b130829f53..2d26d9d764 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/testing-webhooks.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/testing-webhooks.md @@ -1,5 +1,5 @@ --- -title: Testing webhooks +title: 测试 web 挂钩 intro: 'Review your webhook deliveries on {% data variables.product.prodname_dotcom %}, including the HTTP Request and payload as well as the response.' redirect_from: - /webhooks/testing diff --git a/translations/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 ccd933fa4d..b9628c6a08 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 @@ -145,7 +145,7 @@ The unique properties for a webhook event are the same properties you'll find in {{ webhookPayloadsForCurrentVersion.check_suite.completed }} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### code_scanning_alert {% data reusables.webhooks.code_scanning_alert_event_short_desc %} @@ -445,7 +445,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 #### Web 挂钩有效负载对象 {% data reusables.webhooks.installation_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Web 挂钩有效负载示例 @@ -469,7 +469,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 #### Web 挂钩有效负载对象 {% data reusables.webhooks.installation_repositories_properties %} -{% data reusables.webhooks.app_desc %} +{% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} #### Web 挂钩有效负载示例 @@ -1047,7 +1047,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends | 键 | 类型 | 描述 | | -------- | ----- | -------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
      • `created` - 创建了仓库。
      • `deleted` - 仓库被删除。 This event type is only available to [organization hooks](/rest/reference/orgs#webhooks/)
      • `archived` - 仓库被存档。
      • `unarchived` - 仓库被取消存档。
        • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
      • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
        • {% endif %}
      • `edited` - 仓库的信息被编辑。
      • `renamed` - 仓库被重命名。
      • `transferred` - 仓库被转让。
      • `publicized` - 仓库被设为公共。
      • `privatized` - 仓库被设为私有。
      | +| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
      • `created` - 创建了仓库。
      • `deleted` - 仓库被删除。
      • `archived` - 仓库被存档。
      • `unarchived` - 仓库被取消存档。
        • {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
      • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/rest/overview/api-previews#anonymous-git-access-to-repositories)
        • {% endif %}
      • `edited` - 仓库的信息被编辑。
      • `renamed` - 仓库被重命名。
      • `transferred` - 仓库被转让。
      • `publicized` - 仓库被设为公共。
      • `privatized` - 仓库被设为私有。
      | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1100,6 +1100,31 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% endif %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + +### secret_scanning_alert + +{% data reusables.webhooks.secret_scanning_alert_event_short_desc %} + +#### 可用性 + +- 仓库 web 挂钩 +- 组织 web 挂钩 +- {% data variables.product.prodname_github_app %}s with the `secret_scanning_alerts:read` permission + +#### Web 挂钩有效负载对象 + +{% 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. + +#### Web 挂钩有效负载示例 + +{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} +{% endif %} + ### security_advisory 与安全通告相关的活动。 安全通告提供有关 GitHub 软件中安全漏洞的信息。 安全通告数据集还支持 GitHub 安全警报，请参阅“[关于漏洞依赖项的安全警报](/articles/about-security-alerts-for-vulnerable-dependencies/)”。 @@ -1237,9 +1262,9 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends #### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| ---- | ---- | -------------------------------------------------------------------------------- | -| `团队` | `对象` | The [team](/rest/reference/teams) that was modified. **注：**较旧的事件可能不会在有效负载中包括此值。 | +| 键 | 类型 | 描述 | +| ---- | ---- | ------------------------------------------------------------ | +| `团队` | `对象` | 被修改的[团队](/rest/reference/teams)。 **注：**较旧的事件可能不会在有效负载中包括此值。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1268,7 +1293,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends {% 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. +事件的执行者是标星仓库的[用户](/rest/reference/users)，并且事件的仓库是被标星的[仓库](/rest/reference/repos)。 #### 可用性 @@ -1305,7 +1330,7 @@ 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)." +When a {% data variables.product.prodname_actions %} workflow run is requested or completed. 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#workflow_run)”。 #### 可用性 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 new file mode 100644 index 0000000000..f348234d87 --- /dev/null +++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -0,0 +1,54 @@ +--- +title: About discussions +intro: Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About discussions + +With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools. + +- Share announcements and information, gather feedback, plan, and make decisions +- Ask questions, discuss and answer the questions, and mark the discussions as answered +- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows + +![Discussions tab for a repository](/assets/images/help/discussions/hero.png) + +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. 更多信息请参阅“[组织的仓库权限级别](/github/setting-up-and-managing-organizations-and-teams/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)." + +### About categories and formats for discussions + +{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %} + +For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %} + +For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +### Best practices for discussions + +As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)." + +Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." + +### 分享反馈 + +You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). + +### 延伸阅读 + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" +- "[调解评论和对话](/github/building-a-strong-community/moderating-comments-and-conversations)" +- “[在 {% data variables.product.prodname_dotcom %} 上维护您的安全](/github/building-a-strong-community/maintaining-your-safety-on-github)” diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md new file mode 100644 index 0000000000..be12ce18c7 --- /dev/null +++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -0,0 +1,48 @@ +--- +title: Collaborating with maintainers using discussions +shortTitle: Collaborating with maintainers +intro: You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion. +permissions: People with read permissions to a repository can start and participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About collaboration with maintainers using discussions + +{% data reusables.discussions.about-discussions %} If you use or contribute to a project, you can start a discussion to make suggestions and engage with maintainers and community members about your plans, questions, ideas, and feedback. For more information, see "[‎About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +{% data reusables.discussions.about-categories-and-formats %} Repository administrators and project maintainers can delete a discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)." + +{% data reusables.discussions.github-recognizes-members %} These members appear in a list of the most helpful contributors to the project's discussions. As your project grows, you can grant higher access permissions to active members of your community. For more information, see "[Granting higher permissions to top contributors](/discussions/guides/granting-higher-permissions-to-top-contributors)" + +![Most helpful contributors to discussions for a project](/assets/images/help/discussions/most-helpful.png) + +For more information about participation in discussions, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." + +### 基本要求 + +To collaborate with maintainers using discussions, a repository administrator or project maintainer must enable discussions for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Starting a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Filtering the list of discussions + +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the **Search all discussions** field, type a search query. Optionally, to the right of the search field, click a button to further filter the results. ![Search bar and buttons for filtering discussions](/assets/images/help/discussions/search-and-filter-controls.png) +1. In the list of discussions, click the discussion you want to view. ![Discussion search results](/assets/images/help/discussions/search-result.png) + +### Converting an issue to a discussion + +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)." + +### 延伸阅读 + +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- “[在 {% data variables.product.prodname_dotcom %} 上维护您的安全](/github/building-a-strong-community/maintaining-your-safety-on-github)” diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/index.md new file mode 100644 index 0000000000..44aed03c8b --- /dev/null +++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/index.md @@ -0,0 +1,14 @@ +--- +title: Collaborating with your community using discussions +shortTitle: Collaborating using discussions +intro: Gather and discuss your project with community members and other maintainers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /about-discussions %} +{% link_in_list /participating-in-a-discussion %} +{% link_in_list /collaborating-with-maintainers-using-discussions %} + diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md new file mode 100644 index 0000000000..c16fa4f3a7 --- /dev/null +++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -0,0 +1,31 @@ +--- +title: Participating in a discussion +intro: You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}. +permissions: People with read permissions to a repository can participate in discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About participation in a discussion + +{% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." + +In addition to starting or viewing a discussion, you can comment in response to the original comment from the author of the discussion. You can also create a comment thread by replying to an individual comment that another community member made within the discussion, and react to comments with emoji. For more information about reactions, see "[About conversations on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github#reacting-to-ideas-in-comments)." + +You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)." + +### 基本要求 + +Discussions must be enabled for the repository for you to participate in a discussion in the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Creating a discussion + +{% data reusables.discussions.starting-a-discussion %} + +### Marking a comment as an answer + +Discussion authors and users with the triage role or greater for a repository can mark a comment as the answer to a discussion in the repository. + +{% data reusables.discussions.marking-a-comment-as-an-answer %} 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 new file mode 100644 index 0000000000..ec1a20ae29 --- /dev/null +++ b/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -0,0 +1,49 @@ +--- +title: Best practices for community conversations on GitHub +shortTitle: Best practices for community conversations +intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to a discussion when you are ready to scope out the work.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Community conversations in {% data variables.product.prodname_discussions %} + +Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository and gather diverse feedback and ideas more quickly. You can help drive a productive conversation by: + +- Asking pointed questions and follow-up questions to garner specific feedback +- Capture a diverse experience and distill it down to main points +- Open an issue to take action based on the conversation, where applicable + +For more information about opening an issue and cross-referencing a discussion, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)." + +### Learning about conversations on GitHub + +You can create and participate in discussions, issues, and pull requests, depending on the type of conversation you'd like to have. + +You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and spike out a project's specific details before committing it to an issue, which can then be scoped. Discussions are useful for teams if: +- You are in the discovery phase of a project and are still learning which director your team wants to go in +- You want to collect feedback from a wider community about a project +- You want to keep bug fixes, feature requests, and general conversations separate + +议题适用于讨论项目的具体细节，如漏洞修复和计划的改进。 更多信息请参阅“[关于议题](/articles/about-issues)”。 拉取请求允许您直接评论提议的更改。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests)”和“[评论拉取请求](/articles/commenting-on-a-pull-request)”。 + +{% data reusables.organizations.team-discussions-purpose %} 更多信息请参阅“[关于团队讨论](/articles/about-team-discussions)”。 + +### Following contributing guidelines + +Before you open a discussion, check to see if the repository has contributing guidelines. The CONTRIBUTING file includes information about how the repository maintainer would like you to contribute ideas to the project. + +更多信息请参阅“[设置健康参与的项目](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)”。 + +### 后续步骤 + +To continue learning about {% data variables.product.prodname_discussions %} and quickly create a discussion for your community, see "[Quickstart for {% data variables.product.prodname_discussions %}](/discussions/quickstart)." + +### 延伸阅读 + +- "[设置健康参与的项目](/articles/setting-up-your-project-for-healthy-contributions)" +- "[使用模板鼓励有用的议题和拉取请求](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" +- "[调解评论和对话](/articles/moderating-comments-and-conversations)" +- "[在 {% data variables.product.prodname_dotcom %} 上编写](/articles/writing-on-github)" diff --git a/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md new file mode 100644 index 0000000000..dddf07b20a --- /dev/null +++ b/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -0,0 +1,20 @@ +--- +title: Finding discussions across multiple repositories +intro: 'You can easily access every discussion you''ve created or participated in across multiple repositories.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Finding discussions + +1. 导航至 {% data variables.product.prodname_dotcom_the_website %}。 +1. In the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your discussions**. !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. + +### 延伸阅读 + +- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" 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 new file mode 100644 index 0000000000..906d7feb0a --- /dev/null +++ b/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -0,0 +1,32 @@ +--- +title: Granting higher permissions to top contributors +intro: 'Repository administrators can promote any community member to a moderator and maintainer.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### 简介 + +The most helpful contributors for the past 30 days are highlighted on the {% data variables.product.prodname_discussions %} dashboard, based on how many comments were marked as answers by other community members. Helpful contributors can help drive a healthy community and moderate and guide the community space in addition to maintainers. + +### Step 1: Audit your discussions top contributors + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Compare the list of contributors with their access permissions to see who qualifies to moderate the discussion. + +### Step 2: Review permission levels for discussions + +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)." + +### Step 3: Change permissions levels for top contributors + +You can change a contributor's permission levels to give them more access to the tooling they need to moderate GitHub Discussions. To change a person's or team's permission levels, see "[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)." + +### Step 4: Notify community members of elevated access + +When you change a collaborators permission level, they will receive a notification for the change. diff --git a/translations/zh-CN/content/discussions/guides/index.md b/translations/zh-CN/content/discussions/guides/index.md new file mode 100644 index 0000000000..1f16f60479 --- /dev/null +++ b/translations/zh-CN/content/discussions/guides/index.md @@ -0,0 +1,31 @@ +--- +title: Discussions guides +shortTitle: 指南 +intro: 'Discover pathways to get started or learn best practices for participating or monitoring your community''s discussions.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Getting started with discussions + +{% link_in_list /about-discussions %} +{% link_in_list /best-practices-for-community-conversations-on-github %} +{% link_in_list /finding-discussions-across-multiple-repositories %} + +### Administering discussions + +{% link_in_list /granting-higher-permissions-to-top-contributors %} + + + + + diff --git a/translations/zh-CN/content/discussions/index.md b/translations/zh-CN/content/discussions/index.md new file mode 100644 index 0000000000..bfbd387225 --- /dev/null +++ b/translations/zh-CN/content/discussions/index.md @@ -0,0 +1,55 @@ +--- +title: GitHub Discussions Documentation +beta_product: true +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.' +introLinks: + quickstart: /discussions/quickstart +featuredLinks: + guides: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + gettingStarted: + - /discussions/quickstart + guideCards: + - /discussions/collaborating-with-your-community-using-discussions/about-discussions + - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion + - /discussions/managing-discussions-for-your-community/moderating-discussions + popular: + - /discussions/guides/granting-higher-permissions-to-top-contributors + - /discussions/guides/best-practices-for-community-conversations-on-github + - /discussions/guides/finding-discussions-across-multiple-repositories + - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions + - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository +product_video: https://www.youtube-nocookie.com/embed/DbTWBP3_RbM +layout: product-landing +versions: + free-pro-team: '*' +--- + + + + + + + +{% assign discussionsCommunityExamples = site.data.variables.discussions_community_examples %} +{% if discussionsCommunityExamples %} +
      +

      Communities using discussions

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

      抱歉，找不到结果

      +

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

      + Add your community {% octicon "arrow-right" %} +
      +
      +{% endif %} diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md new file mode 100644 index 0000000000..8ccb2875b2 --- /dev/null +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md @@ -0,0 +1,13 @@ +--- +title: Managing discussions for your community +shortTitle: Managing discussions +intro: 'You can enable and configure discussions for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +{% link_in_list /managing-discussions-in-your-repository %} +{% link_in_list /managing-categories-for-discussions-in-your-repository %} +{% link_in_list /moderating-discussions %} diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md new file mode 100644 index 0000000000..fe2bfbd824 --- /dev/null +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md @@ -0,0 +1,56 @@ +--- +title: Managing categories for discussions in your repository +intro: You can categorize the discussions in your repository to organize conversations for your community members, and you can choose a format for each category. +permissions: Repository administrators and people with write or greater access to a repository can enable discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About categories for discussions + +{% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} + +Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations.{% data reusables.discussions.repository-category-limit %} + +For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +### Default categories + +| 分类 | Purpose | 类型 | +|:--------------- |:-------------------------------------------------------------------- |:--------------------- | +| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion | +| 💡Ideas | Ideas to change or improve the project | Open-ended discussion | +| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer | +| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion | + +### Creating a category + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.edit-categories %} +1. Click **New category**. !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png) +1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png) +1. 单击 **Create（创建）**。 !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png) + +### Editing a category + +You can edit a category to change the category's emoji, title, description, and discussion format. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} +![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png) +1. 单击 **Save changes（保存更改）**。 !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +### Deleting a category + +When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png) +1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png) +1. Click **Delete & Move**. ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png) 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 new file mode 100644 index 0000000000..07f315e23b --- /dev/null +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -0,0 +1,94 @@ +--- +title: Managing discussions in your repository +intro: You can categorize, spotlight, transfer, or delete the discussions in a repository. +permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About management of discussions + +{% 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)." + +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](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)," and "[Setting guidelines for repository contributors](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)." + +For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/github/building-a-strong-community/moderating-comments-and-conversations)." + +### 基本要求 + +To manage discussions in a repository, discussions must be enabled for the repository. For more information, see "[Enabling or disabling discussions for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." + +### Changing the category for a discussion + +You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" article. + +You can also move a discussion to a different category. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) + +### Pinning a discussion + +You can pin up to four important discussions above the list of discussions for the repository. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png) +1. Optionally, customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Editing a pinned discussion + +Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Customize the look of the pinned discussion. ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) + +### Unpinning a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) +1. Read the warning, then click **Unpin discussion**. !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png) + +### Transferring a discussion + +To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png) +1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Click **Transfer discussion**. !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png) + +### Deleting a discussion + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png) +1. Read the warning, then click **Delete this discussion**. !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) + +### Converting issues based on labels + +You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Next to the label you want to convert to issues, click **Convert issues**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md new file mode 100644 index 0000000000..2c91d32d89 --- /dev/null +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -0,0 +1,39 @@ +--- +title: Moderating discussions +intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, and converting issues to discussions. and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct to discussions.' +permissions: People with triage access to a repository can moderate discussions in the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About moderating discussions + +{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you 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. + +### Marking a comment as an answer + +{% data reusables.discussions.marking-a-comment-as-an-answer %} + +### Locking discussions + +It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository will still be able to comment on the discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the discussion you want to lock. ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the right margin of a discussion, click **Lock conversation**. +1. Read the information about locking conversations and click **Lock conversation on this discussion**. +1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**. + +### Converting an issue to a discussion + +When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository can bulk convert issues based on labels. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to convert. +1. In the right margin of an issue, click **Convert to discussion**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/zh-CN/content/discussions/quickstart.md b/translations/zh-CN/content/discussions/quickstart.md new file mode 100644 index 0000000000..2a288ec201 --- /dev/null +++ b/translations/zh-CN/content/discussions/quickstart.md @@ -0,0 +1,58 @@ +--- +title: Quickstart for GitHub Discussions +intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository and start conversations with your community.' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### 简介 + +{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike issues. Discussions enable fluid, open conversation in a public forum. + +Discussions give a space for more collaborative conversations by connecting and giving a more centralized area to connect and find information. + +### Enabling {% data variables.product.prodname_discussions %} on your repository + +Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public repositories. + +When you first enable a {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. + +{% data reusables.repositories.navigate-to-repo %} +1. 在仓库名称下，单击 {% octicon "gear" aria-label="The gear icon" %} **Settings（设置）**。 ![Public settings button](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", click **Set up discussions**. ![Set up a discussion button under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png) +1. Under "Start a new discussion," edit the template to align with the resources and tone you want to set for your community. +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) + +### Welcoming contributions to your discussions + +You can welcome your community and introduce a new way to communicate in a repository by creating a welcome post and pin the post to your {% data variables.product.prodname_discussions %} page. Pinning and locking discussions helps people know that a post is meant as an announcement. You can use announcements as a way to link people to more resources and offer guidance for opening discussions in your community. For more information about pinning a discussion, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." + + +### Setting up community guidelines for contributors + +You can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. You can also update the repository's README to communicate expectations on when collaborators should open an issue or discussion. + +For more information about providing guidelines for your project, see "[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and "[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." + +### Creating a new discussion + +Anyone with access to a repository can create a discussion. + +{% data reusables.discussions.starting-a-discussion %} + +### Organizing discussions into relevant categories + +Repository owners and people with write access can create new categories to keep discussions organized. Collaborators participating and creating new discussions can group discussions into the most relevant existing categories. Discussions can also be recategorized after they are created. For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)" + +### Promoting healthy conversations + +People with write permissions for a repository can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." + +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)." + +### 后续步骤 + +Once there is a clear path to scope work out and move an idea from concept to reality, you can create an issue and start tracking your progress. For more information on creating an issue from a discussion, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)." diff --git a/translations/zh-CN/content/education/guides.md b/translations/zh-CN/content/education/guides.md new file mode 100644 index 0000000000..6f4d797ba7 --- /dev/null +++ b/translations/zh-CN/content/education/guides.md @@ -0,0 +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 +versions: + free-pro-team: '*' +--- + +### Get started with {% 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. + +- [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/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount) +- [Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack) + +### Run a software development course with {% 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 %}. + +- [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) + +### Learn to develop software + +Incorporate {% data variables.product.prodname_dotcom %} into your education, and use the same tools as the professionals. + +- [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/teach-and-learn-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) + +### Contribute to the community + +Participate in the community, get training from {% data variables.product.company_short %}, and learn or teach new skills. + +- [{% data variables.product.prodname_education_community %}](https://education.github.community) +- [关于 Campus Experts](/education/teach-and-learn-with-github-education/about-campus-experts) +- [关于 Campus Advisors](/education/teach-and-learn-with-github-education/about-campus-advisors) diff --git a/translations/zh-CN/content/education/index.md b/translations/zh-CN/content/education/index.md new file mode 100644 index 0000000000..c3827df288 --- /dev/null +++ b/translations/zh-CN/content/education/index.md @@ -0,0 +1,45 @@ +--- +title: GitHub Education Documentation +shortTitle: Education +intro: "{% data variables.product.prodname_education %} helps you teach or learn software development with the tools and support of {% data variables.product.company_short %}'s platform and community." +introLinks: + quickstart: /education/quickstart +featuredLinks: + guides: + - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack + - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount + - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution + guideCards: + - /github/getting-started-with-github/signing-up-for-a-new-github-account + - /github/getting-started-with-github/git-and-github-learning-resources + - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom + popular: + - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork + - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research + - /desktop + - /github/getting-started-with-github/github-cli + - /education/manage-coursework-with-github-classroom/teach-with-github-classroom +changelog: + - + title: 'Try something new at Local Hack Day: Learn' + date: '2020-10-15' + href: https://github.blog/2020-10-15-try-something-new-at-local-hack-day-learn/ + - + title: 'Remote Education: Creating community through shared experiences' + date: '2020-09-24' + href: https://github.blog/2020-09-24-remote-education-creating-community-through-shared-experiences/ + - + title: 'Remote Education: A series of best practices for online campus communities' + date: '2020-09-10' + href: https://github.blog/2020-09-10-remote-education-a-series-of-best-practices-for-online-campus-communities/ + - + title: Welcome to the inaugural class of MLH Fellows + date: '2020-06-24' + href: https://github.blog/2020-06-24-welcome-to-the-inaugural-class-of-mlh-fellows/ +layout: product-landing +versions: + free-pro-team: '*' +--- + + + diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md new file mode 100644 index 0000000000..f00b2f90ed --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom.md @@ -0,0 +1,31 @@ +--- +title: About using MakeCode Arcade with GitHub Classroom +shortTitle: About using MakeCode Arcade +intro: You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-makecode +--- + +### About MakeCode Arcade + +MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade. + +For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. + +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. + +### About submission of assignments with MakeCode Arcade + +By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.product.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen. + +![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) + +### 延伸阅读 + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md new file mode 100644 index 0000000000..ad440d799a --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: About using Repl.it with GitHub Classroom +shortTitle: About using Repl.it +intro: You can configure Repl.it as the online integrated development environment (IDE) for assignments in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/student-experience-replit +--- + +### About Repl.it + +Repl.it is an online integrated development environment (IDE) that supports multiple programming languages. Students can write, edit, run, test, and debug code in a browser with Repl.it. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +{% data reusables.classroom.readme-contains-button-for-online-ide %} + +The first time the student clicks the button to visit Repl.it, the student must sign into Repl.it with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on Repl.it. + +For more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/misc/quick-start#the-repl-environment). + +For group assignments, students can use Repl.it Multiplayer to work collaboratively. For more information, see the [Repl.it Multiplayer](https://repl.it/site/multiplayer) website. + +### About submission of assignments with Repl.it + +By default, Repl.it is configured to push to the assignment repository on {% data variables.product.product_location %}. After making progress on an assignment with Repl.it, students should push changes to {% data variables.product.product_location %} using the version control functionality in the left sidebar. + +![Repl.it version control functionality](/assets/images/help/classroom/ide-replit-version-control-button.png) + +For more information about using Git on Repl.it, see the [Repl.it + Git Tutorial](https://repl.it/talk/learn/Replit-Git-Tutorial/23331) on the Repl.it website. + +### 延伸阅读 + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md new file mode 100644 index 0000000000..1ee1e1b5a1 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom.md @@ -0,0 +1,33 @@ +--- +title: Basics of setting up GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %} basics' +intro: Learn how to set up your classroom, manage assignments, and configure time-saving automation. +versions: + free-pro-team: '*' +--- + +### Videos about {% data variables.product.prodname_classroom %} + +You can watch a series of short video tutorials about the configuration and use of {% data variables.product.prodname_classroom %}. To watch all videos as part of a continuous playlist, see the [{% data variables.product.prodname_classroom %} Getting Started Guide](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) on YouTube. + +For more information about terminology for {% data variables.product.prodname_classroom %}, see "[Glossary](/education/manage-coursework-with-github-classroom/glossary)". + +1. Getting started {% octicon "link-external" aria-label="The external link icon" %} +2. Adding your student roster {% octicon "link-external" aria-label="The external link icon" %} +3. Creating assignments + - Creating an assignment using a {% data variables.product.prodname_dotcom %} repository {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Microsoft MakeCode as your online IDE {% octicon "link-external" aria-label="The external link icon" %} + - Creating an assignment using Repl.it as your online IDE {% octicon "link-external" aria-label="The external link icon" %} +4. How students complete assignments {% octicon "link-external" aria-label="The external link icon" %} +5. How teachers review assignments {% octicon "link-external" aria-label="The external link icon" %} +6. Creating group assignments {% octicon "link-external" aria-label="The external link icon" %} +7. Next steps to get started {% octicon "link-external" aria-label="The external link icon" %} +8. {% data variables.product.prodname_dotcom %} Teacher Toolbox {% octicon "link-external" aria-label="The external link icon" %} + +### 后续步骤 + +For more information about teaching with {% data variables.product.prodname_classroom %}, see "[Teach with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom)." + +### 延伸阅读 + +- "[Teach and learn with {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md new file mode 100644 index 0000000000..b53f88c097 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories.md @@ -0,0 +1,50 @@ +--- +title: Configure default settings for assignment repositories +shortTitle: Configure defaults for assignment repositories +intro: You can use the Probot Settings app to configure the default settings for repositories that {% data variables.product.prodname_classroom %} creates for an assignment. +permissions: Organization owners can configure default settings for assignment repositories by installing a {% data variables.product.prodname_github_app %} for the organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/probot-settings +--- + +### About configuration of defaults for assignment repositories + +{% data variables.product.prodname_classroom %} creates a repository that belongs for each student or team that accepts an assignment. The repository belongs to the organization that you use for {% data variables.product.prodname_classroom %}. Assignment repositories can be empty, or you can use a template repository. For more information, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} + +With the Probot Settings app, you can create a file named _.github/settings.yml_ in a repository that contains a list of settings for the repository, and then install a {% data variables.product.prodname_github_app %} for your organization that automatically applies the settings to the repository. + +You can include _.github/settings.yml_ in a template repository that you use for an assignment in {% data variables.product.prodname_classroom %}. When an individual or team accepts the assignment, {% data variables.product.prodname_classroom %} creates the assignment repository, and the Settings app automatically applies the settings from _.github/settings.yml_. + +Probot is a a project, framework, and collection of free apps to automate {% data variables.product.product_name %}. A Probot app can listen to repository events, like the creation of new commits, comments, and issues, and automatically respond to the event. + +For more information, see the [Probot website](https://probot.github.io) and the [Settings app website](https://probot.github.io/apps/settings/). For more information about {% data variables.product.prodname_github_apps %}, see "[About apps](/developers/apps/about-apps)." + +### Adding the Settings app to your organization + +After you install the Probot Settings app for your organization, the app will apply the settings that you define in _.github/settings.yml_ for any repository in your organization, including new assignment repositories that {% data variables.product.prodname_classroom %} creates. + +1. Navigate to the [Settings app page](https://github.com/apps/settings). +1. Click **Install**, then click the organization that you use for {% data variables.product.prodname_classroom %}. Provide the app full access to all repositories owned by the organization. ![Installing the Probot Settings app](/assets/images/help/classroom/probot-settings.gif) + +### Configuring default settings for an assignment repository + +1. Create a template repository that contains a _.github/settings.yml_ file. For a complete list of settings, see the [README](https://github.com/probot/settings#github-settings) for the `probot/settings` repository. For more information about using a template repository for starter code in {% data variables.product.prodname_classroom %}, see "[Create an assignment from a template repository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)." + + {% warning %} + + **Warning:** Do not define `collaborators` in the _.github/settings.yml_ file for your template repository. {% data variables.product.prodname_classroom %} automatically grants teachers and teaching assistants access to assignment repositories. + + {% endwarning %} + +1. Create an assignment using the template repository containing _.github/settings.yml_ as the starter code. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +The Probot Settings app for your organization will now apply the settings you define in _.github/settings.yml_ within the template repository to every assignment repository that {% data reusables.classroom.you-may-want-to-predefine-repository-settings %} creates for a student or team. + +### 延伸阅读 + +- [Probot apps](https://probot.github.io/apps/) +- [Probot documentation](https://probot.github.io/docs/) diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md new file mode 100644 index 0000000000..accb5a7fb4 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md @@ -0,0 +1,138 @@ +--- +title: Connect a learning management system to GitHub Classroom +intro: You can configure an LTI-compliant learning management system (LMS) to connect to {% data variables.product.prodname_classroom %} so that you can import a roster for your classroom. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/configuring-a-learning-management-system-for-github-classroom + - /education/manage-coursework-with-github-classroom/connect-to-lms + - /education/manage-coursework-with-github-classroom/generate-lms-credentials + - /education/manage-coursework-with-github-classroom/setup-canvas + - /education/manage-coursework-with-github-classroom/setup-generic-lms + - /education/manage-coursework-with-github-classroom/setup-moodle +--- + +### About configuration of your LMS + +You can connect a learning management system (LMS) to {% data variables.product.prodname_classroom %}, and {% data variables.product.prodname_classroom %} can import a roster of student identifiers from the LMS. To connect your LMS to {% data variables.product.prodname_classroom %}, you must enter configuration credentials for {% data variables.product.prodname_classroom %} in your LMS. + +### 基本要求 + +To configure an LMS to connect to {% data variables.product.prodname_classroom %}, you must first create a classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-classroom)." + +### Supported LMSes + +{% data variables.product.prodname_classroom %} supports import of roster data from LMSes that implement Learning Tools Interoperability (LTI) standards. + +- LTI version 1.0 and/or 1.1 +- LTI Names and Roles Provisioning 1.X + +Using LTI helps keep your information safe and secure. LTI is an industry-standard protocol and GitHub Classroom's use of LTI is certified by the Instructional Management System (IMS) Global Learning Consortium. For more information, see [Learning Tools Interoperability](https://www.imsglobal.org/activity/learning-tools-interoperability) and [About IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) on the IMS Global Learning Consortium website. + +{% data variables.product.company_short %} has tested import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. + +- Canvas +- Google Classroom +- Moodle +- Sakai + +Currently, {% data variables.product.prodname_classroom %} doesn't support import of roster data from Blackboard or Brightspace + +### Generating configuration credentials for your classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. If your classroom already has a roster, you can either update the roster or delete the roster and create a new roster. + - For more information about deleting and creating a roster, see "[Deleting a roster for a classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#deleting-a-roster-for-a-classroom)" and "[Creating a roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + - For more information about updating a roster, see "[Adding students to the roster for your classroom](/education/manage-coursework-with-github-classroom/manage-classrooms#adding-students-to-the-roster-for-your-classroom)." +1. In the list of LMSes, click your LMS. If your LMS is not supported, click **Other LMS**. ![List of LMSes](/assets/images/help/classroom/classroom-settings-click-lms.png) +1. Read about connecting your LMS, then click **Connect to _LMS_**. +1. Copy the "Consumer Key", "Shared Secret", and "Launch URL" for the connection to the classroom. ![Copy credentials](/assets/images/help/classroom/classroom-copy-credentials.png) + +### Configuring a generic LMS + +You must configure the privacy settings for your LMS to allow external tools to receive roster information. + +1. Navigate to your LMS. +1. Configure an external tool. +1. Provide the configuration credentials you generated in {% data variables.product.prodname_classroom %}. + - Consumer key + - 共享机密 + - Launch URL (sometimes called "tool URL" or similar) + +### Configuring Canvas + +You can configure {% data variables.product.prodname_classroom %} as an external app for Canvas to import roster data into your classroom. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). + +1. Sign into [Canvas](https://www.instructure.com/canvas/#login). +1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}. +1. 在左边栏中，单击 **Settings（设置）**。 +1. Click the **Apps** tab. +1. Click **View app configurations**. +1. Click **+App**. +1. Select the **Configuration Type** drop-down menu, and click **By URL**. +1. Paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Canvas app configuration | Value or setting | + |:------------------------------------------------------------------------- |:------------------------------------------------------------------ | + | **Consumer Key** | Consumer key from {% data variables.product.prodname_classroom %} + | **Shared Secret** | Shared secret from {% data variables.product.prodname_classroom %} + | **Allow this tool to access the IMS Names and Role Provisioning Service** | Enabled | + | **Configuration URL** | Launch URL from {% data variables.product.prodname_classroom %} + + {% note %} + + **Note**: If you don't see a checkbox in Canvas labeled "Allow this tool to access the IMS Names and Role Provisioning Service", then your Canvas administrator must contact Canvas support to enable membership service configuration for your Canvas account. Without enabling this feature, you won't be able to sync the roster from Canvas. For more information, see [How do I contact Canvas Support?](https://community.canvaslms.com/t5/Canvas-Basics-Guide/How-do-I-contact-Canvas-Support/ta-p/389767) on the Canvas website. + + {% endnote %} + +1. 单击 **Submit（提交）**。 +1. In the left sidebar, click **Home**. +1. To prompt Canvas to send a confirmation email, in the left sidebar, click **GitHub Classroom**. Follow the instructions in the email to finish linking {% data variables.product.prodname_classroom %}. + +### Configuring Moodle + +You can configure {% data variables.product.prodname_classroom %} as an activity for Moodle to import roster data into your classroom. For more information about Moodle, see the [Moodle website](https://moodle.org). + +You must be using Moodle version 3.0 or greater. + +1. Sign into [Moodle](https://moodle.org/login/index.php). +1. Select the Moodle course to integrate with {% data variables.product.prodname_classroom %}. +1. Click **Turn editing on**. +1. Wherever you'd like {% data variables.product.prodname_classroom %} to be available in Moodle, click **Add an activity or resource**. +1. Choose **External tool** and click **Add**. +1. In the "Activity name" field, type "GitHub Classroom". +1. In the **Preconfigured tool** field, to the right of the drop-down menu, click **+**. +1. Under "External tool configuration", paste the configuration credentials from {% data variables.product.prodname_classroom %}. For more information, see "[Generating configuration credentials for your classroom](#generating-configuration-credentials-for-your-classroom)." + + | Field in Moodle app configuration | Value or setting | + |:--------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | **Tool name** | {% data variables.product.prodname_classroom %} - _YOUR CLASSROOM NAME_

      **Note**: You can use any name, but we suggest this value for clarity. | + | **Tool URL** | Launch URL from {% data variables.product.prodname_classroom %} + | **LTI version** | LTI 1.0/1.1 | + | **Default launch container** | New window | + | **Consumer key** | Consumer key from {% data variables.product.prodname_classroom %} + | **共享机密** | Shared secret from {% data variables.product.prodname_classroom %} + +1. Scroll to and click **Services**. +1. To the right of "IMS LTI Names and Role Provisioning", select the drop-down menu and click **Use this service to retrieve members' information as per privacy settings**. +1. Scroll to and click **Privacy**. +1. To the right of **Share launcher's name with tool** and **Share launcher's email with tool**, select the drop-down menus to click **Always**. +1. 在页面底部，单击 **Save changes（保存更改）**。 +1. In the **Preconfigure tool** menu, click **GitHub Classroom - _YOUR CLASSROOM NAME_**. +1. Under "Common module settings", to the right of "Availability", select the drop-down menu and click **Hide from students**. +1. At the bottom of the page, click **Save and return to course**. +1. Navigate to anywhere you chose to display {% data variables.product.prodname_classroom %}, and click the {% data variables.product.prodname_classroom %} activity. + +### Importing a roster from your LMS + +For more information about importing the roster from your LMS into {% data variables.product.prodname_classroom %}, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms#creating-a-roster-for-your-classroom)." + +### Disconnecting your LMS + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Connect to a learning management system (LMS)", click **Connection Settings**. !["Connection settings" link in classroom settings](/assets/images/help/classroom/classroom-settings-click-connection-settings.png) +1. Under "Delete Connection to your learning management system", click **Disconnect from your learning management system**. !["Disconnect from your learning management system" button in connection settings for classroom](/assets/images/help/classroom/classroom-settings-click-disconnect-from-your-lms-button.png) 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 new file mode 100644 index 0000000000..842e4c79d2 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-a-group-assignment.md @@ -0,0 +1,145 @@ +--- +title: Create a group assignment +intro: 'You can create a collaborative assignment for teams of students who participate in your course.' +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/create-group-assignments +--- + +### About group assignments + +{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers. + +When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment. + +{% data reusables.classroom.classroom-creates-group-repositories %} + +{% data reusables.classroom.about-assignments %} + +You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. 更多信息请参阅“[关于团队](/github/setting-up-and-managing-organizations-and-teams/about-teams)”。 + +For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### 基本要求 + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Defining teams for an assignment](#defining-teams-for-an-assignment) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +#### Defining teams for an assignment + +If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams. + +{% tip %} + +**提示**： + +- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course. + +- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members. + +{% endtip %} + +![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png) + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +### Providing feedback + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the team. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
      + Group assignment +
      + +### 后续步骤 + +- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. + +- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### 延伸阅读 + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" +- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md new file mode 100644 index 0000000000..f882ddabd6 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository.md @@ -0,0 +1,19 @@ +--- +title: Create an assignment from a template repository +intro: You can create an assignment from a template repository to provide starter code, documentation, and other resources to your students. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments +--- + +You can use a template repository on {% data variables.product.product_name %} as starter code for an assignment on {% data variables.product.prodname_classroom %}. Your template repository can contain boilerplate code, documentation, and other resources for your students. 更多信息请参阅“[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)”。 + +To use the template repository for your assignment, the template repository must be owned by your organization, or the visibility of the template repository must be public. + +{% data reusables.classroom.you-may-want-to-predefine-repository-settings %} For more information, see "[Configure default settings for assignment repositories](/education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories)." + +### 延伸阅读 + +- "[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)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md new file mode 100644 index 0000000000..20bd5c14ef --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/create-an-individual-assignment.md @@ -0,0 +1,124 @@ +--- +title: Create an individual assignment +intro: You can create an assignment for students in your course to complete individually. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment + - /education/manage-coursework-with-github-classroom/create-an-individual-assignment +--- + +### About individual assignments + +{% data reusables.classroom.assignments-individual-definition %} + +{% data reusables.classroom.classroom-creates-individual-repositories %} + +{% data reusables.classroom.about-assignments %} + +For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." + +### 基本要求 + +{% data reusables.classroom.assignments-classroom-prerequisite %} + +### Creating an assignment + +{% data reusables.classroom.assignments-guide-create-the-assignment %} + +### Setting up the basics for an assignment + +Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories. + +- [Naming an assignment](#naming-an-assignment) +- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment) +- [Choosing an assignment type](#choosing-an-assignment-type) +- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories) + +#### Naming an assignment + +For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`. + +{% data reusables.classroom.assignments-type-a-title %} + +#### Assigning a deadline for an assignment + +{% data reusables.classroom.assignments-guide-assign-a-deadline %} + +#### Choosing an assignment type + +Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +#### Choosing a visibility for assignment repositories + +{% data reusables.classroom.assignments-guide-choose-visibility %} + +{% data reusables.classroom.assignments-guide-click-continue-after-basics %} + +### Adding starter code and configuring a development environment + +{% data reusables.classroom.assignments-guide-intro-for-environment %} + +- [Choosing a template repository](#choosing-a-template-repository) +- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide) + +#### Choosing a template repository + +By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %} For more information about template repositories, see "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)." + +{% data reusables.classroom.assignments-guide-choose-template-repository %} + +{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} + +#### Choosing an online integrated development environment (IDE) + +{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." + +{% data reusables.classroom.assignments-guide-choose-an-online-ide %} + +### Providing feedback for an assignment + +Optionally, you can automatically grade assignments and create a space for discussing each submission with the student. + +- [Testing assignments automatically](#testing-assignments-automatically) +- [Preventing changes to important files](#preventing-changes-to-important-files) +- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback) + +#### Testing assignments automatically + +{% data reusables.classroom.assignments-guide-using-autograding %} + +#### Preventing changes to important files + +{% data reusables.classroom.assignments-guide-prevent-changes %} + +#### Creating a pull request for feedback + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +{% data reusables.classroom.assignments-guide-create-review-pull-request %} + +{% data reusables.classroom.assignments-guide-click-create-assignment-button %} + +### Inviting students to an assignment + +{% data reusables.classroom.assignments-guide-invite-students-to-assignment %} + +You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %} + +
      + Individual assignment +
      + +### 后续步骤 + +- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Creating, cloning, and archiving repositories](/github/creating-cloning-and-archiving-repositories)," "[Using Git](/github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." + +- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)." + +- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)." + +### 延伸阅读 + +- "[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)" +- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md new file mode 100644 index 0000000000..44e2a0103f --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom.md @@ -0,0 +1,9 @@ +--- +title: Get started with GitHub Classroom +shortTitle: 入门 +intro: Learn how to configure and use {% data variables.product.prodname_classroom %} to administer your course. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/glossary.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/glossary.md new file mode 100644 index 0000000000..3facfc7ba8 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/glossary.md @@ -0,0 +1,52 @@ +--- +title: 词汇表 +intro: You can review explanations of terminology for {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +--- + +### 转让 + +An assignment is coursework in {% data variables.product.prodname_classroom %}. A teacher can assign an assignment to an individual student or a group of students. Teachers can import starter code for the assignment, assign students, and create a deadline for each assignment. For more information, see the definitions for "[individual assignment](#individual-assignment)" and "[group assignment](#group-assignment)." + +--- + +### classroom + +A classroom is the basic unit of {% data variables.product.prodname_classroom %}. Teachers can use a classroom to organize and manage students, teaching assistants, and assignments for a single course. A classroom belongs to an organization on {% data variables.product.prodname_dotcom_the_website %}. To administer a classroom, you must be an organization owner for the organization on {% data variables.product.prodname_dotcom %}. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." + +--- + +### {% data variables.product.prodname_classroom %} + +{% data variables.product.prodname_classroom %} is a web application for educators that provides course administration tools integrated with {% data variables.product.prodname_dotcom %}. For more information, see the [{% data variables.product.prodname_classroom %}](https://classroom.github.com/) website. + +--- + +### group assignment + +{% data reusables.classroom.assignments-group-definition %} For more information, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +--- + +### identifier + +An identifier in {% data variables.product.prodname_classroom %} is a unique ID for a student participating in a course. For example, an identifier can be a student name, alphanumeric ID, or email address. + +--- + +### individual assignment + +{% data reusables.classroom.assignments-individual-definition %} For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)." + +--- + +### roster + +A roster allows a teacher to manage students and assignment submissions in a classroom on {% data variables.product.prodname_classroom %}. Teachers can create a roster by entering a list of student identifiers, or by connecting {% data variables.product.prodname_classroom %} to a learning management system (LMS). For more information about identifiers, see the definition of "[identifier](#identifier)." For more information about connecting {% data variables.product.prodname_classroom %} to an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + +--- + +### 延伸阅读 + +- "[{% data variables.product.prodname_dotcom %} 词汇](/github/getting-started-with-github/github-glossary)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/index.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/index.md new file mode 100644 index 0000000000..e568c09a16 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/index.md @@ -0,0 +1,32 @@ +--- +title: Manage coursework with GitHub Classroom +shortTitle: '{% data variables.product.prodname_classroom %}' +intro: With {% data variables.product.prodname_classroom %}, you can use {% data variables.product.product_name %} to administer or participate in a course about software development. +versions: + free-pro-team: '*' +--- + +### 目录 + +{% topic_link_in_list /get-started-with-github-classroom %} + {% link_in_list /basics-of-setting-up-github-classroom %} + {% link_in_list /glossary %} + +{% topic_link_in_list /teach-with-github-classroom %} + {% link_in_list /manage-classrooms %} + {% link_in_list /create-an-individual-assignment %} + {% link_in_list /create-a-group-assignment %} + {% link_in_list /create-an-assignment-from-a-template-repository %} + {% link_in_list /leave-feedback-with-pull-requests %} + {% link_in_list /use-autograding %} + {% link_in_list /configure-default-settings-for-assignment-repositories %} + {% link_in_list /connect-a-learning-management-system-to-github-classroom %} + +{% topic_link_in_list /integrate-github-classroom-with-an-ide %} + {% link_in_list /integrate-github-classroom-with-an-online-ide %} + {% link_in_list /about-using-makecode-arcade-with-github-classroom %} + {% link_in_list /about-using-replit-with-github-classroom %} + {% link_in_list /run-student-code-in-an-online-ide %} + +{% topic_link_in_list /learn-with-github-classroom %} + {% link_in_list /view-autograding-results %} diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md new file mode 100644 index 0000000000..f4245ea672 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide.md @@ -0,0 +1,9 @@ +--- +title: Integrate GitHub Classroom with an IDE +shortTitle: Integrate with an IDE +intro: You can help your students write, test, and debug code by preconfiguring a development environment for assignment repositories on {% data variables.product.prodname_classroom %}. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md new file mode 100644 index 0000000000..9a2b16772a --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide.md @@ -0,0 +1,42 @@ +--- +title: Integrate GitHub Classroom with an online IDE +shortTitle: Integrate with an online IDE +intro: You can preconfigure a supported online integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/online-ide-integrations +--- + +### About integration with an online IDE + +{% data reusables.classroom.about-online-ides %} + +After a student accepts an assignment with an online IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary. + +![Button for online IDE in README.md for assignment repository](/assets/images/help/classroom/assignment-repository-ide-button-in-readme.png) + +### Supported online IDEs + +{% data variables.product.prodname_classroom %} supports the following online IDEs. You can learn more about the student experience for each IDE. + +| IDE | 更多信息 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | +| Repl.it | "[About using Repl.it with GitHub Classroom](/education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom)" | + +### Configuring an online IDE for an assignment + +You can choose the online IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an online IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Authorizing the OAuth app for an online IDE + +The first time you configure an assignment with an online IDE, you must authorize the OAuth app for the online IDE for your organization. + +!["Go grant access" button in popover for authorizing OAuth app for online IDE](/assets/images/help/classroom/assignment-ide-go-grant-access-button.png) + +For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. 更多信息请参阅“[授权 OAuth 应用程序](/github/authenticating-to-github/authorizing-oauth-apps)”。 + +### 延伸阅读 + +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md new file mode 100644 index 0000000000..bca1150346 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Learn with GitHub Classroom +intro: You can participate in coursework in {% data variables.product.prodname_classroom %} and see results from your teacher. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md new file mode 100644 index 0000000000..c51d2b43d3 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests.md @@ -0,0 +1,31 @@ +--- +title: Leave feedback with pull requests +intro: You can leave feedback for your students in a special pull request within the repository for each assignment. +permissions: People with read permissions to a repository can leave feedback in a pull request for the repository. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github +--- + +### About feedback pull requests for assignments + +{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %} + +When you enable the pull request for feedback for an assignment, {% data variables.product.prodname_classroom %} will create a special pull request titled **Feedback** in the assignment repository for each student or team. The pull request automatically shows every commit that a student pushed to the assignment repository's default branch. + +### 基本要求 + +To create and access the feedback pull request, you must enable the feedback pull request when you create the assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +### Leaving feedback in a pull request for an assignment + +{% data reusables.classroom.sign-into-github-classroom %} +1. In the list of classrooms, click the classroom with the assignment you want to review. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **Review**. ![Review button for assignment in list of submissions for an assignment](/assets/images/help/classroom/assignments-click-review-button.png) +1. Review the pull request. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)." + +### 延伸阅读 + +- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](http://localhost:4000/en/free-pro-team@latest/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)" 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 new file mode 100644 index 0000000000..8b75539d56 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/manage-classrooms.md @@ -0,0 +1,106 @@ +--- +title: Manage classrooms +intro: You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}. +permissions: Organization owners can manage a classroom for an organization. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/archive-a-classroom +--- + +### About classrooms + +{% data reusables.classroom.about-classrooms %} + +![Classroom](/assets/images/help/classroom/classroom-hero.png) + +### About management of classrooms + +{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms. + +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 classrom. 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)." + +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. + +### About classroom rosters + +Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course. + +When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a user account to link the user account to an identifier for the classroom. After the student links a user account, you can see the associated user account in the roster. You can also see when the student accepts or submits an assignment. + +![Classroom roster](/assets/images/help/classroom/roster-hero.png) + +### 基本要求 + +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 authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. 更多信息请参阅“[授权 OAuth 应用程序](/github/authenticating-to-github/authorizing-oauth-apps)”。 + +### Creating a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **New classroom**. !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png) +{% data reusables.classroom.guide-create-new-classroom %} + +After you create a classroom, you can begin creating assignments for students. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." + +### Creating a roster for your classroom + +You can create a roster of the students who participate in your course. + +If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, click {% octicon "mortar-board" aria-label="The mortar board icon" %} **Import from a learning management system** and follow the instructions. For more information, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." !["Import from a learning management system" button](/assets/images/help/classroom/click-import-from-a-learning-management-system-button.png) +1. To create a roster manually, type your student identifiers. Optionally, click **Upload a CSV or text file** to upload a file containing the identifiers. ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png) +1. Click **Create roster**. !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png) + +### Adding students to the roster for your classroom + +Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classrom](#creating-a-roster-for-your-classroom)." + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. To the right of "Classroom roster", click **Update students**. !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png) +1. Follow the instructions to add students to the roster. + - To import students from an LMS, click **Sync from a learning management system**. For more information about importing a roster from an LMS, see "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)." + - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**. ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png) + +### Renaming a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. Under "Classroom name", type a new name for the classroom. ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png) +1. Click **Rename classroom**. !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png) + +### Archiving or unarchiving a classroom + +You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**. ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png) +1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**. ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png) + +### Deleting a roster for a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-students %} +1. Under "Delete this roster", click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png) +1. Read the warnings, then click **Delete roster**. !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png) + +### Deleting a classroom + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-settings %} +1. To the right of "Delete this classroom", click **Delete classroom**. !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png) +1. **阅读警告**。 +1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete. ![Modal for deleting a classrom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png) +1. Click **Delete classroom**. !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png) diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md new file mode 100644 index 0000000000..57e3f1e824 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide.md @@ -0,0 +1,21 @@ +--- +title: Run student code in an online IDE +intro: You can run the code from a student assignment within the online integrated development environment (IDE) that you configured for the assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/running-student-code +--- + +### About student code and online IDEs + +If you configure an online integrated development environment (IDE) for an assignment, you can run the code within the online IDE. You don't need to clone the assignment repository to your computer. + +For more information about online IDEs, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)." + +### Running student code in the online IDE + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of the submission, click **View IDE**. !["View IDE" button for submission using an online IDE](/assets/images/help/classroom/assignments-click-view-ide.png) diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md new file mode 100644 index 0000000000..6e051e9d2d --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom.md @@ -0,0 +1,8 @@ +--- +title: Teach with GitHub Classroom +intro: Learn how to set up your classroom and assignments. +mapTopic: true +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/use-autograding.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/use-autograding.md new file mode 100644 index 0000000000..986bda5a56 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/use-autograding.md @@ -0,0 +1,83 @@ +--- +title: Use autograding +intro: You can automatically provide feedback on code submissions from your students by configuring tests to run in the assignment repository. +miniTocMaxHeadingLevel: 4 +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers +--- + +### About autograding + +{% data reusables.classroom.about-autograding %} + +After a student accepts an assignment, on every push to the assignment repository, {% data variables.product.prodname_actions %} runs the commands for your autograding test in a Linux environment containing the student's newest code. {% data variables.product.prodname_classroom %} creates the necessary workflows for {% data variables.product.prodname_actions %}. You don't need experience with {% data variables.product.prodname_actions %} to use autograding. + +You can use a testing framework, run a custom command, write input/output tests, or combine different testing methods. The Linux environment for autograding contains many popular software tools. For more information, see the details for the latest version of Ubuntu in "[Specifications for {% data variables.product.company_short %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)." + +You can see an overview of which students are passing autograding tests by navigating to the assignment in {% data variables.product.prodname_classroom %}. A green checkmark means that all tests are passing for the student, and a red X means that some or all tests are failing for the student. If you award points for one or more tests, then a bubble shows the score for the tests out of the maximum possible score for the assignment. + +![Overview for an assignment with autograding results](/assets/images/help/classroom/autograding-hero.png) + +### Grading methods + +There are two grading methods: input/output tests and run command tests. + +#### Input/output test + +An input/output test optionally runs a setup command, then provides standard input to a test command. {% data variables.product.prodname_classroom %} evaluates the test command's output against an expected result. + +| 设置 | 描述 | +|:------------------- |:------------------------------------------------------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate standard output for evaluation | +| **Inputs** | Standard input for run command | +| **Expected output** | The output that you want to see as standard output from the run command | +| **Comparison** | The type of comparison between the run command's output and the expected output

      • **Included**: Passes when the expected output appears
        anywhere in the standard output from the run command
      • **Exact**: Passes when the expected output is completely identical
        to the standard output from the run command
      • **Regex**: Passes if the regular expression in expected
        output matches against the standard output from the run command
      | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +#### Run command test + +A run command test runs a setup command, then runs a test command. {% data variables.product.prodname_classroom %} checks the exit status of the test command. An exit code of `0` results in success, and any other exit code results in failure. + +{% data variables.product.prodname_classroom %} provides presets for language-specific run command tests for a variety of programming languages. For example, the **Run node** test prefills the setup command with `npm install` and the test command with `npm test`. + +| 设置 | 描述 | +|:----------------- |:------------------------------------------------------------------------------ | +| **Test name** | The name of the test, to identify the test in logs | +| **Setup command** | _Optional_. A command to run before tests, such as compilation or installation | +| **Run command** | The command to run the test and generate an exit code for evaluation | +| **Timeout** | In minutes, how long a test should run before resulting in failure | +| **Points** | _Optional_. The number of points the test is worth toward a total score | + +### Configuring autograding tests for an assignment + +You can add autograding tests during the creation of a new assignment. {% data reusables.classroom.for-more-information-about-assignment-creation %} + +You can add, edit, or delete autograding tests for an existing assignment. If you change the autograding tests for an existing assignment, existing assignment repositories will not be affected. A student or team must accept the assignment and create a new assignment repository to use the new tests. + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.assignments-click-pencil %} +1. In the left sidebar, click **Grading and feedback**. !["Grading and feedback" to the left of assignment's basics](/assets/images/help/classroom/assignments-click-grading-and-feedback.png) +1. Add, edit, or delete an autograding test. + - To add a test, under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. ![Using the "Add test" drop-down menu to click a grading method](/assets/images/help/classroom/autograding-click-grading-method.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To edit a test, to the right of the test name, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing an autograding test](/assets/images/help/classroom/autograding-click-pencil.png) Configure the test, then click **Save test case**. !["Save test case" button for an autograding test](/assets/images/help/classroom/assignments-click-save-test-case-button.png) + - To delete a test, to the right of the test name, click {% octicon "trash" aria-label="The trash icon" %}. ![Trash icon for deleting an autograding test](/assets/images/help/classroom/autograding-click-trash.png) +1. At the bottom of the page, click **Update assignment**. !["Update assignment" button at the bottom of the page](/assets/images/help/classroom/assignments-click-update-assignment.png) + +### Viewing logs from autograding tests + +{% data reusables.classroom.sign-into-github-classroom %} +{% data reusables.classroom.click-classroom-in-list %} +{% data reusables.classroom.click-assignment-in-list %} +1. To the right of a submission, click **View test**. !["View test" button for an assignment submission](/assets/images/help/classroom/assignments-click-view-test.png) +1. Review the test output. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)." + +### 延伸阅读 + +- [{% data variables.product.prodname_actions %} documentation](/actions) diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/view-autograding-results.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/view-autograding-results.md new file mode 100644 index 0000000000..533f4ddcc8 --- /dev/null +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/view-autograding-results.md @@ -0,0 +1,30 @@ +--- +title: View autograding results +intro: You can see results from autograding within the repository for your assignment. +versions: + free-pro-team: '*' +redirect_from: + - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students +--- + +### About autograding + +Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.product.product_location %}. + +If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X. + +### Viewing autograding results for an assignment repository + +{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." + +The **Actions** tab shows the full history of test runs. + +!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png) + +You can click a specific test run to review log output, like compilation errors and test failures. + +![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) + +### 延伸阅读 + +- "[关于状态检查](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/zh-CN/content/education/quickstart.md b/translations/zh-CN/content/education/quickstart.md new file mode 100644 index 0000000000..3a5c526108 --- /dev/null +++ b/translations/zh-CN/content/education/quickstart.md @@ -0,0 +1,87 @@ +--- +title: Quickstart for GitHub Educators +intro: In about 15 minutes, teachers can get started with discounts, training, and tools for {% data variables.product.company_short %}, then create a classroom for the students in a software development course using {% data variables.product.prodname_classroom %}. +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' +--- + +### 简介 + +Educators who teach a course on software development can use discounts, partnerships, training, and tools from {% data variables.product.prodname_education %} to effectively teach relevant skills to students. + +In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}. + +{% tip %} + +**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Applying for a student developer pack](/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack)." + +{% endtip %} + +### Creating accounts on {% data variables.product.product_name %} + +First, you'll need to create a free user account on {% data variables.product.product_name %}. + +{% data reusables.accounts.create-account %} +1. Follow the prompts to create your free user account. + +After you create your user account, create a free organization account. You'll use this organization account to create and manage classrooms {% data variables.product.prodname_classroom %}. + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.organizations %} +{% data reusables.organizations.new-organization %} +4. Follow the prompts to create a free organization. + +For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." + +### Applying for an educator discount + +Next, you'll sign up for discounts on services from {% data variables.product.company_short %}. {% data reusables.education.educator-requirements %} + +{% tip %} + +**Tip** In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website. + +{% endtip %} + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### Set up {% data variables.product.prodname_classroom %} + +With your user account and organization account, you're ready to get started with {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %} is free to use. You can track and manage assignments, grade work automatically, and provide feedback to your students. + +{% data reusables.classroom.sign-into-github-classroom %} +1. To authorize {% data variables.product.prodname_classroom %} to access your user account on {% data variables.product.prodname_dotcom %}, review the information, then click **Authorize {% data variables.product.prodname_classroom %}**. !["Authorize {% data variables.product.prodname_classroom %}" button for user account](/assets/images/help/classroom/setup-click-authorize-github-classroom.png) +1. Review the information. To authorize {% data variables.product.prodname_classroom %} to access your organization account on {% data variables.product.prodname_dotcom %}, click **Grant**. !["Grant" button for organization](/assets/images/help/classroom/setup-click-grant.png) + + {% tip %} + + **Tip**: If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. 更多信息请参阅“[授权 OAuth 应用程序](/github/authenticating-to-github/authorizing-oauth-apps#oauth-apps-and-organizations)”。 + + {% endtip %} + +1. Click **Authorize github**. ![Click "Authorize" button for organization](/assets/images/help/classroom/setup-click-authorize-github.png) + +### Create your classroom + +{% data reusables.classroom.about-classrooms %} + +{% data reusables.classroom.sign-into-github-classroom %} +1. Click **Create your first classroom** or **New classroom**. +{% data reusables.classroom.guide-create-new-classroom %} + +### 后续步骤 + +You've created a classroom, and you're ready to enrich your course with {% data variables.product.product_name %} and {% data variables.product.prodname_classroom %}! 🎉 + +- Watch some videos about {% data variables.product.prodname_classroom %}. For more information, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)." +- Manage your classrooms and classroom admins, and create a roster of students for your classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." +- Create an assignment for individual students or teams. {% data reusables.classroom.for-more-information-about-assignment-creation %} +- Write and implement automated tests to provide immediate feedback to students directly in assignment repositories. For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." +- Participate in {% data variables.product.prodname_education_community_with_url %}. diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-campus-advisors.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-campus-advisors.md new file mode 100644 index 0000000000..762f38822a --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-campus-advisors.md @@ -0,0 +1,17 @@ +--- +title: 关于 Campus Advisors +intro: '作为讲师或辅导员，可在您的学校通过 Campus Advisors 培训和支持学习使用 {% data variables.product.prodname_dotcom %}。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-advisors + - /articles/about-campus-advisors +versions: + free-pro-team: '*' +--- + +教授、教师和辅导员可使用 Campus Advisors 在线培训掌握 Git 和 {% data variables.product.prodname_dotcom %}，通过 {% data variables.product.prodname_dotcom %} 学习最佳教学方法。 更多信息请参阅 "[Campus Advisors](https://education.github.com/teachers/advisors)"。 + +{% note %} + +**注：**作为讲师，无法为学生创建 {% data variables.product.prodname_dotcom %} 帐户。 学生必须创建自己的 {% data variables.product.prodname_dotcom %} 帐户。 + +{% endnote %} diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-campus-experts.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-campus-experts.md new file mode 100644 index 0000000000..a181cc9664 --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-campus-experts.md @@ -0,0 +1,11 @@ +--- +title: 关于 Campus Experts +intro: '作为学生，可通过 {% data variables.product.prodname_dotcom %} Campus Experts 培训学习必要的技能来构建学校的技术社区和实际作品集。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-campus-experts + - /articles/about-campus-experts +versions: + free-pro-team: '*' +--- + +作为 {% data variables.product.prodname_dotcom %} Campus Expert，学习公共演讲技能、技术写作、社区领导和软件开发技能。 更多信息请参阅 "[Campus Experts](https://education.github.com/students/experts)"。 diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md new file mode 100644 index 0000000000..823af9d33a --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers.md @@ -0,0 +1,31 @@ +--- +title: 关于适用于教育者和研究人员的 GitHub Education +intro: '{% data variables.product.prodname_education %} 提供各种工具帮助教育者和研究人员在课堂内外更有效地工作。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers + - /articles/about-github-education-for-educators-and-researchers +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 适用于教育者的 {% data variables.product.prodname_education %} + +利用 {% data variables.product.prodname_education %} 适用于各级教育者的工具和服务，您可以： + - 使用 [{% data variables.product.prodname_classroom %}](https://classroom.github.com) 分发代码、向学生提供反馈以及收集 {% data variables.product.prodname_dotcom %} 中的作业。 + - 加入我们的 [{% data variables.product.prodname_education_community %}](https://education.github.com/forum)，以与全球各地的同行讨论技术教育的当前趋势。 + - 访问和调整我们用于教授 Git 和 {% data variables.product.prodname_dotcom %} 的[开源课程计划](https://education.github.community/t/open-source-lesson-plans/1591)。 + - [申请 {% data variables.product.prodname_dotcom %} swag 包](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33)，其中包括学生用教育资料和重要工具。 + {% data reusables.education.apply-for-team %} + +### 适用于研究人员的 {% data variables.product.prodname_education %} + +利用 {% data variables.product.prodname_education %} 适用于研究人员的工具和服务，您可以： + - 在 {% data variables.product.prodname_dotcom %} 上与世界各地的其他人协作处理研究工作。 + - [了解](https://education.github.com/stories)全球各地的学术机构如何使用 {% data variables.product.prodname_dotcom %} 进行研究。 + {% data reusables.education.apply-for-team %} + +### 延伸阅读 + +- "[关于学生版 {% data variables.product.prodname_education %}](/articles/about-github-education-for-students)" diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md new file mode 100644 index 0000000000..f587517629 --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education-for-students.md @@ -0,0 +1,21 @@ +--- +title: 关于学生版 GitHub Education +intro: '{% data variables.product.prodname_education %} 让学生免费使用 {% data variables.product.prodname_dotcom %} 合作伙伴的各种开发工具，为他们提供真实的体验。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education-for-students + - /articles/about-github-education-for-students +versions: + free-pro-team: '*' +--- + +将 {% data variables.product.prodname_dotcom %} 用于学校项目是一种与别人协作的实用方式，可创建展示真实世界的作品集。 + +{% data reusables.education.about-github-education-link %} + +拥有 {% data variables.product.prodname_dotcom %} 帐户的每个人都可通过 {% data variables.product.prodname_free_user %} 在无限的公共和私有仓库中协作。 作为学生，您也可以申请 {% data variables.product.prodname_student_pack %}，以免费使用专业开发者使用的工具和服务。 For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" and [{% data variables.product.prodname_education %}](https://education.github.com/pack). + +如果您是 FIRST 机器人俱乐部的成员，您的辅导员可以申请教育者折扣，这样您的团队可以免费使用 {% data variables.product.prodname_team %}（允许无限的用户和私有仓库） 进行协作。 For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." + +### 延伸阅读 + +- "[关于教育者和研究人员版 {% data variables.product.prodname_education %}](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education.md new file mode 100644 index 0000000000..59dfc4219c --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/about-github-education.md @@ -0,0 +1,23 @@ +--- +title: 关于 GitHub Education +intro: '{% data variables.product.prodname_education %} 为希望为其社区最大利用 {% data variables.product.prodname_dotcom %} 并且同意特定计划要求的学校提供特殊的免费产品。' +redirect_from: + - /github/teaching-and-learning-with-github-education/about-github-education + - /articles/about-github-education +versions: + free-pro-team: '*' +--- + +如果您的学校同意遵守特定要求，则您的中学、大学或训练营可获得 {% data variables.product.prodname_education %}，其中免费提供最佳 {% data variables.product.prodname_dotcom %}，包括： +- {% data variables.product.prodname_ghe_cloud %} 和/或 {% data variables.product.prodname_ghe_server %} +- 通过 Campus Advisor 计划为教师提供 Git 和 {% data variables.product.prodname_dotcom %} 培训 +- 自动访问高级 {% data variables.product.prodname_education %} 功能，如 {% data variables.product.prodname_student_pack %} +- 通过 Campus Experts 计划为学生提供领导力发展和技术培训 + +更多信息请参阅[官方 {% data variables.product.prodname_education %}](https://education.github.com/partners/schools) 网页。 + +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)." + +要详细了解学生领导者和教师的培训计划，请参阅 "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)" 和 "[Campus Advisors](https://education.github.com/teachers/advisors)"。 + +如果您是学生或教师并且您的学校未作为 {% data variables.product.prodname_education %} 学校与 {% data variables.product.prodname_dotcom %} 合作，您也可以个人申请使用 {% 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/zh-CN/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md new file mode 100644 index 0000000000..0f13be8acf --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack.md @@ -0,0 +1,53 @@ +--- +title: Apply for a student developer pack +intro: '作为学生，可以申请 {% data variables.product.prodname_student_pack %}，其中包括 {% data variables.product.prodname_dotcom %} 合作伙伴的特惠和福利。' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack + - /articles/applying-for-a-student-developer-pack +versions: + free-pro-team: '*' +--- + +{% data reusables.education.about-github-education-link %} + +### 要求 + +要获得申请 {% data variables.product.prodname_student_pack %} 的资格，必须： +- 现正攻读学位或文凭授予课程，如高中、初中、大专、大学、自主学习或类似教育机构 +- 具有学校发放的可验证电子邮件地址，或者上传能证明您目前学生身份的文档 +- 拥有 [{% data variables.product.prodname_dotcom %} 用户帐户](/articles/signing-up-for-a-new-github-account) +- 至少年满 13 岁 + +证明您现任学生身份的文件包括学校 ID 照看、班级课程表、成绩单和归属或入学签到函。 + +在作为学生期间，可能会提示您定期重新验证目前的学业身份。 + +{% note %} + +**注：**不能在不同帐户之间转让学生折扣。 如有多个帐户想申请折扣，请考虑[合并](/articles/merging-multiple-user-accounts)您的用户帐户并根据需要[重命名](/articles/changing-your-github-username)保留的帐户。 + +{% endnote %} + +有关续订 {% data variables.product.prodname_student_pack %} 的信息，请参阅“[到期和续订](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)”。 + +### 申请 {% data variables.product.prodname_student_pack %} + +{% data reusables.education.benefits-page %} +3. 在 "Which best describes your academic status?"（哪一项最准确描述了您的学业身份？）下，选择 **Student（学生）**。 ![选择学籍](/assets/images/help/education/academic-status-student.png) +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### 到期和续订 + +在您的 {% data variables.product.prodname_student_pack %} 访问权限到期后，如果您仍有资格，您可以重新申请，但有些合作伙伴可能不提供续订服务。 合作伙伴的大多数计时特惠在您设置后便开始。 更多信息请参阅 [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) 页面。 + +要查看您对 {% data variables.product.prodname_student_pack %} 的免费访问何时到期，请访问您帐户的[帐单设置](https://github.com/settings/billing)。 + +### 延伸阅读 + +- "[我的 {% data variables.product.prodname_student_pack %} 申请为什么未获得批准？](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" +- "[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)" +- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md new file mode 100644 index 0000000000..1e5adc727d --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount.md @@ -0,0 +1,57 @@ +--- +title: Apply for an educator or researcher discount +intro: '如果您是教育者或研究人员，可以为组织申请免费获取 {% data variables.product.prodname_team %}。' +redirect_from: + - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount + - /articles/applying-for-a-classroom-discount/ + - /articles/applying-for-a-discount-for-your-school-club/ + - /articles/applying-for-an-academic-research-discount/ + - /articles/applying-for-a-discount-for-your-first-robotics-team/ + - /articles/applying-for-an-educator-or-researcher-discount +versions: + free-pro-team: '*' +--- + +### 关于教育者和研究人员折扣 + +{% data reusables.education.about-github-education-link %} + +{% data reusables.education.educator-requirements %} + +For more information about user accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)." + +### 申请教育者或研究人员折扣 + +{% data reusables.education.benefits-page %} +{% data reusables.education.click-get-teacher-benefits %} +{% data reusables.education.select-email-address %} +{% data reusables.education.upload-proof-status %} +{% data reusables.education.school-name %} +{% data reusables.education.plan-to-use-github %} +{% data reusables.education.submit-application %} + +### 升级组织 + +在教育者或研究人员折扣申请获得批准后，您可以将用于学习社区的组织升级到 {% data variables.product.prodname_team %}，以便免费访问无限的用户和具有完全功能的私有仓库。 您可以升级现有组织或创建新组织进行升级。 + +#### 升级现有组织 + +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +#### 升级新组织 + +{% data reusables.education.upgrade-page %} +1. 单击 {% octicon "plus" aria-label="The plus symbol" %} **Create an organization（创建组织）**。 ![创建组织按钮](/assets/images/help/education/create-org-button.png) +3. 阅读信息，然后单击 **Create organization（创建组织）**。 ![创建组织按钮](/assets/images/help/education/create-organization-button.png) +4. 在“Choose a plan（选择计划）”下，单击 **选择 {% data variables.product.prodname_free_team %}**。 +5. 按照提示创建组织。 +{% data reusables.education.upgrade-page %} +{% data reusables.education.upgrade-organization %} + +### 延伸阅读 + +- "[为什么我的教育者或研究人员折扣申请未获得批准？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" +- [{% data variables.product.prodname_education %}](https://education.github.com) +- [{% data variables.product.prodname_classroom %} 视频](https://classroom.github.com/videos) +- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/index.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/index.md new file mode 100644 index 0000000000..5f1195a3a8 --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/index.md @@ -0,0 +1,26 @@ +--- +title: Explore the benefits of teaching and learning with GitHub Education +shortTitle: Teach and learn +intro: Learn how {% data variables.product.prodname_education %} can benefit your classroom, schoolwork, or research and how to apply for free access to various developer tools from {% data variables.product.company_short %}'s partners. +redirect_from: + - /education/teach-and-learn-with-github-education + - /github/teaching-and-learning-with-github-education + - /categories/teaching-and-learning-with-github-education +versions: + free-pro-team: '*' +--- + +### 目录 + +{% topic_link_in_list /use-github-at-your-educational-institution %} + {% link_in_list /about-github-education %} + {% link_in_list /about-campus-experts %} + {% link_in_list /about-campus-advisors %} +{% topic_link_in_list /use-github-for-your-schoolwork %} + {% link_in_list /about-github-education-for-students %} + {% link_in_list /apply-for-a-student-developer-pack %} + {% link_in_list /why-wasnt-my-application-for-a-student-developer-pack-approved %} +{% topic_link_in_list /use-github-in-your-classroom-and-research %} + {% link_in_list /about-github-education-for-educators-and-researchers %} + {% link_in_list /apply-for-an-educator-or-researcher-discount %} + {% link_in_list /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved %} diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md new file mode 100644 index 0000000000..4bb3204f8f --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-at-your-educational-institution.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub at your educational institution +intro: '通过 {% data variables.product.prodname_education %} 以及我们针对学生和讲师的各种培训计划，利用 {% data variables.product.prodname_dotcom %} 使您机构的学生、讲师和 IT 员工最大限度地获益。' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution + - /articles/using-github-at-your-educational-institution +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md new file mode 100644 index 0000000000..ab86a34b17 --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub for your schoolwork +intro: '作为学生，使用 {% data variables.product.prodname_dotcom %} 在您的学校项目上协作，并构建真实世界的体验。' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork + - /articles/using-github-for-your-schoolwork +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md new file mode 100644 index 0000000000..a6428c6922 --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research.md @@ -0,0 +1,11 @@ +--- +title: Use GitHub in your classroom and research +intro: '作为教育工作者或研究人员，使用 {% data variables.product.prodname_dotcom %} 在课堂上、学生或研究小组中协作完成您的工作等等。' +mapTopic: true +redirect_from: + - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research + - /articles/using-github-in-your-classroom-and-research +versions: + free-pro-team: '*' +--- + diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md new file mode 100644 index 0000000000..eeb5d45ca8 --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved.md @@ -0,0 +1,67 @@ +--- +title: 为什么我的学生开发包申请未获得批准？ +intro: '查看申请 {% data variables.product.prodname_student_pack %}未获批准的常见原因，并了解成功重新申请的窍门。' +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved + - /articles/why-was-my-application-for-a-student-developer-pack-denied/ + - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved + - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**提示：** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### 学术关联文档不明确 + +如果您上传的图像没有明确地确定您当前的学术地位，则我们需要您的学术地位的进一步证明。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### 使用具有未经验证域的学术电子邮件 + +如果您的学术电子邮件地址有未经验证的域，则我们需要您的学术地位的进一步证明。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +### 使用来自电子邮件政策宽松的学校的学术电子邮件 + +如果您的学校在付费学生注册之前发出电子邮件地址，则我们需要您的学术地位的进一步证明。 {% data reusables.education.upload-proof-reapply %} + +{% data reusables.education.pdf-support %} + +如果您有关于学校域的其他疑问或问题，请让学校的 IT 人员联系我们。 + +### 学术电子邮件地址已占用 + +如果您的学术电子邮件地址已用于为其他 {% data variables.product.prodname_dotcom %} 帐户申请 {% data variables.product.prodname_student_pack %}，则该折扣到期之前，您无法重复使用该学术电子邮件地址成功申请其他 {% data variables.product.prodname_student_pack %}。 + +{% note %} + +**注：**维护多个个人帐户违反了 {% data variables.product.prodname_dotcom %} [服务条款](/articles/github-terms-of-service/#3-account-requirements)。 + +{% endnote %} + +如果您有多个个人用户帐户，则必须合并您的帐户。 要保留折扣，请保留已授予折扣的帐户。 您可以通过将所有电子邮件地址添加到保留的帐户来重命名保留的帐户，并保留您的贡献历史记录。 + +更多信息请参阅： +- “[合并多个用户帐户](/articles/merging-multiple-user-accounts)” +- “[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username)” +- “[添加电子邮件地址到 {% data variables.product.prodname_dotcom %} 帐户](/articles/adding-an-email-address-to-your-github-account)” + +### 学生身份不合格 + +以下情况时，您没有资格获得 {% data variables.product.prodname_student_pack %}： +- 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. +- 您未满 13 岁。 + +您的讲师仍可申请 {% data variables.product.prodname_education %} 折扣供课堂使用。 如果您是编程学校或训练营的学生，并且您的学校参加 [{% data variables.product.prodname_dotcom %} 校园计划](https://education.github.com/schools)，您将有资格获得 {% data variables.product.prodname_student_pack %}。 + +### 延伸阅读 + +- “[申请学生开发包](/articles/applying-for-a-student-developer-pack)” +- "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)" diff --git a/translations/zh-CN/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/zh-CN/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md new file mode 100644 index 0000000000..4bc4faeaa9 --- /dev/null +++ b/translations/zh-CN/content/education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md @@ -0,0 +1,45 @@ +--- +title: 为什么我的教育工作者或研究人员折扣申请未获得批准？ +intro: 查看申请教育工作者或研究人员折扣未获批准的常见原因，并了解成功重新申请的窍门。 +redirect_from: + - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ + - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved + - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved +versions: + free-pro-team: '*' +--- + +{% tip %} + +**提示：** {% data reusables.education.about-github-education-link %} + +{% endtip %} + +### 关联文档证明不明确 + +如果您上传的图像无法明确地确定您目前在学校或大学工作，则必须重新申请并上传您的教职员 ID 或雇主证明信的其他图像，其中须含有明确信息。 + +{% data reusables.education.pdf-support %} + +### 使用具有未经验证域的学术电子邮件 + +如果您的学术电子邮件地址有未经验证的域，则我们可能需要您的学术地位的进一步证明。 {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +### 使用来自电子邮件政策宽松的学校的学术电子邮件 + +如果您学校的校友和退休教师终身可以访问学校发出的电子邮件地址，则我们可能需要您的学术地位的进一步证明。 {% data reusables.education.upload-different-image %} + +{% data reusables.education.pdf-support %} + +如果您有关于学校域的其他疑问或问题，请让学校的 IT 人员联系我们。 + +### 非学生申请学生开发包 + +教育工作者或研究人员没有资格获得 [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)随附的合作伙伴优惠。 当您重新申请时，确保选择 **Faculty（教职工）**来描述您的学术地位。 + +### 延伸阅读 + +- "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)" diff --git a/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md b/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md index 655b5b28f8..ced5a30049 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-dependabot-version-updates.md @@ -32,14 +32,14 @@ versions: ### 支持的仓库和生态系统 +您可以为包含其中一个受支持包管理器的依赖项清单或锁定文件的仓库配置版本更新。 对于某些软件包管理器，您也可以配置依赖项的供应。 更多信息请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)。” + {% note %} -{% data reusables.dependabot.private-dependencies %} +{% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 See the details in the table below. {% endnote %} -您可以为包含其中一个受支持包管理器的依赖项清单或锁定文件的仓库配置版本更新。 对于某些软件包管理器，您也可以配置依赖项的供应。 更多信息请参阅“[依赖项更新的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#vendor)。” - {% data reusables.dependabot.supported-package-managers %} 如果您的仓库已使用集成进行依赖项管理，则在启用 {% data variables.product.prodname_dependabot %} 前需要禁用此集成。 更多信息请参阅“[关于集成](/github/customizing-your-github-workflow/about-integrations)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md b/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md index ffc5d7f779..625ff2a2c4 100644 --- a/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md +++ b/translations/zh-CN/content/github/administering-a-repository/about-secret-scanning.md @@ -18,7 +18,7 @@ versions: ### 关于公共仓库的 {% data variables.product.prodname_secret_scanning %} - {% data variables.product.prodname_secret_scanning_caps %} is automatically enabled on public repositories, where it scans code for secrets, to check for known secret formats. When a match of your secret format is found in a public repository, {% data variables.product.company_short %} doesn't publicly disclose the information as an alert, but instead sends a payload to an HTTP endpoint of your choice. For an overview of how secret scanning works on public repositories, see "[Secret scanning](/developers/overview/secret-scanning)." + {% data variables.product.prodname_secret_scanning_caps %} 在公共仓库上自动启用，在其中会扫描密钥代码来检查已知的密码格式。 当在公共仓库中找到您的密码格式的匹配项时，{% data variables.product.company_short %} 不将信息作为警报公开，而是将有效负载发送到您选择的 HTTP 端点。 有关密码扫描如何在公共仓库上运行的概述，请参阅“[密码扫描](/developers/overview/secret-scanning)”。 当您推送到公共仓库时，{% data variables.product.product_name %} 会扫描提交的内容中是否有密码。 如果将私有仓库切换到公共仓库，{% data variables.product.product_name %} 会扫描整个仓库中的密码。 @@ -36,6 +36,7 @@ versions: - Databricks - Datadog - Discord +- Doppler - Dropbox - Dynatrace - Finicity @@ -67,7 +68,7 @@ versions: {% data reusables.secret-scanning.beta %} -If you're a repository administrator or an organization owner, you can enable {% data variables.product.prodname_secret_scanning %} for private repositories that are owned by organizations. You can enable {% data variables.product.prodname_secret_scanning %} for all your repositories, or for all new repositories within your organization. {% data variables.product.prodname_secret_scanning_caps %} is not available for user account-owned private repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." +如果您是仓库管理员或组织所有者，您可以为组织拥有的私有仓库启用 {% data variables.product.prodname_secret_scanning %}。 您可以启用对您所有的仓库或者您组织中的所有新仓库启用 {% data variables.product.prodname_secret_scanning %}。 {% data variables.product.prodname_secret_scanning_caps %} 不适用于用户帐户拥有的私有仓库。 更多信息请参阅“[管理仓库的安全性和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”或“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”。 将提交推送到启用了 {% data variables.product.prodname_secret_scanning %} 的私有仓库时，{% data variables.product.product_name %} 会扫描提交的内容中是否有密码： @@ -77,7 +78,9 @@ If you're a repository administrator or an organization owner, you can enable {% - {% data variables.product.prodname_dotcom %} 在仓库中显示警报。 更多信息请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/github/administering-a-repository/managing-alerts-from-secret-scanning)”。 -Repository administrators and organization owners can grant users and team access to {% data variables.product.prodname_secret_scanning %} alerts. 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 +仓库管理员和组织所有者可以授予用户和团队访问 {% data variables.product.prodname_secret_scanning %} 警报。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 + +要监控来自私有仓库或组织中的 {% data variables.product.prodname_secret_scanning %} 的结果，可以使用 {% data variables.product.prodname_secret_scanning %} API。 有关 API 端点的更多信息，请参阅“[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)”。 {% data variables.product.product_name %} 当前会扫描私有仓库，查找以下服务提供商发布的密码。 @@ -90,6 +93,7 @@ Repository administrators and organization owners can grant users and team acces - CloudBees CodeShip - Databricks - Discord +- Doppler - Dropbox - Dynatrace - Finicity diff --git a/translations/zh-CN/content/github/administering-a-repository/classifying-your-repository-with-topics.md b/translations/zh-CN/content/github/administering-a-repository/classifying-your-repository-with-topics.md index 4ed3cde0bc..9deddeefe4 100644 --- a/translations/zh-CN/content/github/administering-a-repository/classifying-your-repository-with-topics.md +++ b/translations/zh-CN/content/github/administering-a-repository/classifying-your-repository-with-topics.md @@ -22,7 +22,7 @@ versions: 仓库管理员可以添加他们喜欢的任何主题到仓库。 适用于对仓库分类的主题包括仓库的预期目的、主题领域、社区或语言。{% if currentVersion == "free-pro-team@latest" %}此外，{% data variables.product.product_name %} 也会分析公共仓库内容，生成建议的主题，仓库管理员可以接受或拒绝。 私有仓库内容不可分析，也不会收到主题建议。{% endif %} -{% if currentVersion == "github-ae@latest" %}Internal {% else %}Public, internal, {% endif %}and private repositories can have topics, although you will only see private repositories that you have access to in topic search results. +{% if currentVersion == "github-ae@latest" %}Internal {% else %}公共、内部{% endif %}和私有仓库可拥有主题，虽然您在主题搜索结果中只会看到您有权访问的私有仓库。 您可以搜索与公共仓库关联的仓库。 更多信息请参阅“[搜索仓库](/articles/searching-for-repositories#search-by-topic)”。 您也可以搜索 {% data variables.product.product_name %} 中的主题列表。 更多信息请参阅“[搜索主题](/articles/searching-topics)”。 diff --git a/translations/zh-CN/content/github/administering-a-repository/configuration-options-for-dependency-updates.md b/translations/zh-CN/content/github/administering-a-repository/configuration-options-for-dependency-updates.md index 3766bf752f..ce303e9375 100644 --- a/translations/zh-CN/content/github/administering-a-repository/configuration-options-for-dependency-updates.md +++ b/translations/zh-CN/content/github/administering-a-repository/configuration-options-for-dependency-updates.md @@ -302,13 +302,14 @@ updates: - dependency-name: "express" # For Express, ignore all updates for version 4 and 5 versions: ["4.x", "5.x"] - # For Loadash, ignore all updates - - dependency-name: "loadash" + # For Lodash, ignore all updates + - dependency-name: "lodash" ``` {% note %} -**注**：{% data variables.product.prodname_dependabot_version_updates %} 无法为包含私有 git 依赖项或私有 git 注册表的清单中的任何依赖项运行版本更新，即使您将私有依赖项添加到配置文件的 `ignore` 选项。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot#supported-repositories-and-ecosystems)”。 +**注意**：即使您将不可访问的依赖项添加到配置文件的`忽略`选项，{% 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-repositories)”和“[排除 {% 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/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md b/translations/zh-CN/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md index 48f764aef7..a6dbc17daa 100644 --- a/translations/zh-CN/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md +++ b/translations/zh-CN/content/github/administering-a-repository/customizing-your-repositorys-social-media-preview.md @@ -11,7 +11,7 @@ versions: 在添加图像之前，请展开仓库链接以显示关于仓库和所有者头像的基本信息。 为仓库添加图像有助于在各种社交平台上识别您的项目。 -{% if currentVersion != "github-ae@latest" %}You can upload an image to a private repository, but your image can only be shared from a public repository.{% endif %} +{% if currentversion != "github-ae@latest" %}您可以将映像上传到私有仓库，但您的映像只能从公共仓库分享。{% endif %} {% tip %} 提示：您的图像应为大小在 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获取质量最佳的渲染，建议图像的像素保持在 640 x 320 像素。 diff --git a/translations/zh-CN/content/github/administering-a-repository/deleting-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/deleting-a-repository.md index a921d075b7..38c99ef5c1 100644 --- a/translations/zh-CN/content/github/administering-a-repository/deleting-a-repository.md +++ b/translations/zh-CN/content/github/administering-a-repository/deleting-a-repository.md @@ -13,14 +13,14 @@ versions: {% data reusables.organizations.owners-and-admins-can %} 删除组织仓库。 如果已禁用 **Allow members to delete or transfer repositories for this organization（允许成员删除或转让此组织的仓库）**，仅组织所有者可删除组织仓库。 {% data reusables.organizations.new-repo-permissions-more-info %} -{% if currentVersion != "github-ae@latest" %}Deleting a public repository will not delete any forks of the repository.{% endif %} +{% if currentversion != "github-ae@latest" %}删除公共仓库不会删除该仓库的任何复刻。{% endif %} {% warning %} **警告**： -- Deleting a repository will **permanently** delete release attachments and team permissions. 此操作**必须**完成。 -- Deleting a private {% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}or internal {% endif %}repository will delete all forks of the repository. +- 删除仓库将**永久**删除发行版附件和团队权限。 此操作**必须**完成。 +- 删除私有 {% if currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}或内部{% endif %}仓库将会删除该仓库的所有复刻。 {% endwarning %} diff --git a/translations/zh-CN/content/github/administering-a-repository/enabling-and-disabling-version-updates.md b/translations/zh-CN/content/github/administering-a-repository/enabling-and-disabling-version-updates.md index 7a66ca0747..fef6b36c2d 100644 --- a/translations/zh-CN/content/github/administering-a-repository/enabling-and-disabling-version-updates.md +++ b/translations/zh-CN/content/github/administering-a-repository/enabling-and-disabling-version-updates.md @@ -14,14 +14,10 @@ versions: {% data reusables.dependabot.initial-updates %} 更多信息请参阅“[自定义依赖项更新](/github/administering-a-repository/customizing-dependency-updates)。” +{% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 更多信息请参阅“[关于 Dependabot 版本更新](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)”。 + ### 启用 {% data variables.product.prodname_dependabot_version_updates %} -{% note %} - -{% data reusables.dependabot.private-dependencies %} - -{% endnote %} - {% data reusables.dependabot.create-dependabot-yml %} 1. 使用 `package-ecosystem` 指定要监视的包管理器。 1. 对于每个包管理器，可使用： diff --git a/translations/zh-CN/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/zh-CN/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md new file mode 100644 index 0000000000..070048507f --- /dev/null +++ b/translations/zh-CN/content/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -0,0 +1,20 @@ +--- +title: Enabling or disabling GitHub Discussions for a repository +intro: 'You can use discussions in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.' +product: '{% data reusables.gated-features.discussions %}' +permissions: People with admin permissions to a repository can enable discussions for the repository. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Enabling or disabling discussions for your repository + +{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} +1. To disable discussions, under "Features", unselect **Discussions**. + +### 延伸阅读 + +- "[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/zh-CN/content/github/administering-a-repository/index.md b/translations/zh-CN/content/github/administering-a-repository/index.md index a9a7a59aee..1d43ba47ec 100644 --- a/translations/zh-CN/content/github/administering-a-repository/index.md +++ b/translations/zh-CN/content/github/administering-a-repository/index.md @@ -12,36 +12,25 @@ versions: ### 目录 {% topic_link_in_list /managing-repository-settings %} - {% link_in_list /setting-repository-visibility %}{% if currentVersion == "free-pro-team@latest" %} - {% link_in_list /managing-teams-and-people-with-access-to-your-repository %}{% endif %} + {% link_in_list /setting-repository-visibility %} + {% link_in_list /managing-teams-and-people-with-access-to-your-repository %} {% link_in_list /classifying-your-repository-with-topics %} {% link_in_list /customizing-how-changed-files-appear-on-github %} {% link_in_list /about-email-notifications-for-pushes-to-your-repository %} - {% link_in_list /displaying-a-sponsor-button-in-your-repository %} - - {% link_in_list /customizing-your-repositorys-social-media-preview %} - - {% link_in_list /viewing-deployment-activity-for-your-repository %} - {% link_in_list /managing-the-forking-policy-for-your-repository %} - {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository %} - {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %} + {% link_in_list /disabling-or-limiting-github-actions-for-a-repository %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /enabling-or-disabling-github-discussions-for-a-repository %}{% endif %} {% link_in_list /managing-git-lfs-objects-in-archives-of-your-repository %} {% link_in_list /enabling-anonymous-git-read-access-for-a-repository %} - - {% link_in_list /configuring-autolinks-to-reference-external-resources %} - {% link_in_list /renaming-a-repository %} {% link_in_list /transferring-a-repository %} {% link_in_list /deleting-a-repository %} - {% link_in_list /restoring-a-deleted-repository %} - {% topic_link_in_list /managing-branches-in-your-repository %} {% link_in_list /viewing-branches-in-your-repository %} {% link_in_list /changing-the-default-branch %} @@ -50,9 +39,7 @@ versions: {% link_in_list /about-merge-methods-on-github %} {% link_in_list /configuring-commit-squashing-for-pull-requests %} {% link_in_list /configuring-commit-rebasing-for-pull-requests %} - {% link_in_list /managing-the-automatic-deletion-of-branches %} - {% topic_link_in_list /defining-the-mergeability-of-pull-requests %} {% link_in_list /about-protected-branches %} {% link_in_list /configuring-protected-branches %} @@ -65,31 +52,22 @@ versions: {% link_in_list /enabling-required-reviews-for-pull-requests %} {% link_in_list /about-required-commit-signing %} {% link_in_list /enabling-required-commit-signing %} - {% link_in_list /requiring-a-linear-commit-history %} {% link_in_list /enabling-force-pushes-to-a-protected-branch %} {% link_in_list /enabling-deletion-of-a-protected-branch %} - {% topic_link_in_list /releasing-projects-on-github %} {% link_in_list /about-releases %} {% link_in_list /managing-releases-in-a-repository %} {% link_in_list /viewing-your-repositorys-releases-and-tags %} {% link_in_list /linking-to-releases %} - {% link_in_list /comparing-releases %} - - {% link_in_list /automation-for-release-forms-with-query-parameters %} - - {% topic_link_in_list /securing-your-repository %} {% link_in_list /about-securing-your-repository %} {% link_in_list /about-secret-scanning %} {% link_in_list /configuring-secret-scanning-for-private-repositories %} {% link_in_list /managing-alerts-from-secret-scanning %} {% link_in_list /managing-security-and-analysis-settings-for-your-repository %} - - {% topic_link_in_list /keeping-your-dependencies-updated-automatically %} {% link_in_list /about-dependabot-version-updates %} {% link_in_list /enabling-and-disabling-version-updates %} @@ -98,4 +76,3 @@ versions: {% link_in_list /customizing-dependency-updates %} {% link_in_list /configuration-options-for-dependency-updates %} {% link_in_list /keeping-your-actions-up-to-date-with-dependabot %} - diff --git a/translations/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 6d833ad48f..5b94165d24 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 @@ -19,8 +19,8 @@ versions: ### 关于发行版管理 -{% if currentVersion == "free-pro-team@latest" %} -You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. 更多信息请参阅“在 {% data variables.product.prodname_marketplace %} 中发布操作”。 +{% if currentversion == "free proteam@latest" %} +您也可以在 {% data variables.product.prodname_marketplace %} 中发布特定版本的操作。 更多信息请参阅“在 {% data variables.product.prodname_marketplace %} 中发布操作”。 {% endif %} 您可以选择是否 diff --git a/translations/zh-CN/content/github/administering-a-repository/managing-repository-settings.md b/translations/zh-CN/content/github/administering-a-repository/managing-repository-settings.md index 818e46ede9..2006116c9f 100644 --- a/translations/zh-CN/content/github/administering-a-repository/managing-repository-settings.md +++ b/translations/zh-CN/content/github/administering-a-repository/managing-repository-settings.md @@ -1,6 +1,6 @@ --- title: 管理仓库设置 -intro: 'Repository administrators and organization owners can change settings for a repository, like the name, ownership, and visibility, or delete the repository.' +intro: '仓库管理员和组织所有者可以更改仓库的设置，如名称、所有权和可见性，或删除该仓库。' mapTopic: true redirect_from: - /articles/managing-repository-settings 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 f8c7b40976..36a21fff9c 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 @@ -24,18 +24,18 @@ versions: ### 授予对安全警报的访问权限 -After you enable {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_secret_scanning %} alerts for a repository in an organization, organization owners and repository administrators can view the alerts by default. 您可以授予其他团队和人员访问仓库的警报。 +为组织中的仓库启用 {% data variables.product.prodname_dependabot %} 或 {% data variables.product.prodname_secret_scanning %} 后，组织所有者和仓库管理员默认可以查看警报。 您可以授予其他团队和人员访问仓库的警报。 {% note %} -Organization owners and repository administrators can only grant access to view security alerts, such as {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_secret_scanning %} alerts, to people or teams who have write access to the repo. +组织所有者和仓库管理员只能向具有仓库写入权限的人员授予安全警报的查看权限，如 {% data variables.product.prodname_dependabot %} 和 {% data variables.product.prodname_secret_scanning %} 警报。 {% endnote %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches. ![用于授予人员或团队访问安全警报的搜索字段](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) +4. 在“Access to alerts（访问警报）”下，在搜索字段中开始键入您要查找的个人或团队的名称，然后单击匹配列表中的名称。 ![用于授予人员或团队访问安全警报的搜索字段](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) 5. 单击 **Save changes（保存更改）**。 ![用于更改安全警报设置的"Save changes（保存更改）"按钮](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) ### 删除对安全警报的访问权限 @@ -43,7 +43,7 @@ Organization owners and repository administrators can only grant access to view {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}. ![用于删除某人对您仓库的安全警报访问权限的 "x" 按钮](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) +4. 在“Access to alerts（访问警报）”下，在要删除其访问权限的个人或团队的右侧，单击 {% octicon "x" aria-label="X symbol" %}。 ![用于删除某人对您仓库的安全警报访问权限的 "x" 按钮](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) ### 延伸阅读 diff --git a/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md b/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md index 529b7772c0..b373dbd6cd 100644 --- a/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md +++ b/translations/zh-CN/content/github/administering-a-repository/setting-repository-visibility.md @@ -20,12 +20,12 @@ versions: #### 将仓库设为私有 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -* {% data variables.product.product_name %} 将会分离公共仓库的公共复刻并将其放入新的网络中。 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 %} 不再在 {% data variables.product.prodname_archive %} 中包含该仓库。 For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if enterpriseServerVersions contains currentVersion %} -* Anonymous Git read access is no longer available. 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)”。{% endif %} +* {% data variables.product.product_name %} 将会分离公共仓库的公共复刻并将其放入新的网络中。 公共复刻无法设为私有。{% endif %} +* 如果您将仓库的可见性从内部更改为私有， {% data variables.product.prodname_dotcom %} 将删除属于任何没有新私有仓库访问权限的用户的复刻。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}任何复刻的可见性也将更改为私有。{% elsif currentVersion == "github-ae@latest" %}如果内部仓库有任何复刻，则复刻的可见性已经是私有的。{% endif %}更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)”{% if currentversion == "free proteam@latest" %} +* 如果对用户帐户或组织使用 {% data variables.product.prodname_free_user %}，有些功能在您将可见性更改为私有后不可用于仓库。 {% data reusables.gated-features.more-info %}{% endif %} +* 任何已发布的 {% data variables.product.prodname_pages %} 站点将自动取消发布。{% if currentVersion == "free-pro-team@latest" %} 如果将自定义域添加到 {% data variables.product.prodname_pages %} 站点，应先删除或更新 DNS 记录后再将仓库设为私有，以避免域接管的风险。 更多信息请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %}{% if currentVersion == "free-pro-team@latest" %} +* {% data variables.product.prodname_dotcom %} 不再在 {% data variables.product.prodname_archive %} 中包含该仓库。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program) 上存档内容和数据”。{% endif %}{% if enterpriseServerVersions contains currentVersion %} +* 匿名 Git 读取权限不再可用。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)”。{% endif %} {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} @@ -37,7 +37,7 @@ versions: {% 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)" +* 仓库的任何复刻都将保留在仓库网络中， {% data variables.product.product_name %} 维护根仓库与复刻之间的关系。 更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)” {% endif %} @@ -45,8 +45,8 @@ versions: #### 将仓库设为公共 -* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% if currentVersion == "free-pro-team@latest" %} -* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). 您的仓库设为公共后，您还可以查看仓库的社区资料以了解项目是否符合支持贡献者的最佳做法。 更多信息请参阅“[查看您的社区资料](/articles/viewing-your-community-profile)”。{% endif %} +* {% data variables.product.product_name %} 将会分离私有复刻并将它们变成独立的私有仓库。 更多信息请参阅“[删除仓库或更改其可见性时，复刻会发生什么变化？](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)”{% if currentVersion == "free-pro-team@latest" %} +* 如果在创建开源项目时将私有仓库转换为公共仓库，请参阅[开放源码指南](http://opensource.guide)以了解有用的提示和指南。 您还可以通过 [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) 免费学习管理开源项目的课程。 您的仓库设为公共后，您还可以查看仓库的社区资料以了解项目是否符合支持贡献者的最佳做法。 更多信息请参阅“[查看您的社区资料](/articles/viewing-your-community-profile)”。{% endif %} {% endif %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/about-anonymized-image-urls.md b/translations/zh-CN/content/github/authenticating-to-github/about-anonymized-image-urls.md index 5f862793ab..f0df9e6c65 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/about-anonymized-image-urls.md +++ b/translations/zh-CN/content/github/authenticating-to-github/about-anonymized-image-urls.md @@ -8,7 +8,7 @@ versions: free-pro-team: '*' --- -为托管您的图像，{% data variables.product.product_name %} 使用 [开源项目 Camo](https://github.com/atmos/camo)。 Camo generates an anonymous URL proxy for each image which hides your browser details and related information from other users. The URL starts `https://.githubusercontent.com/`, with different subdomains depending on how you uploaded the image. +为托管您的图像，{% data variables.product.product_name %} 使用 [开源项目 Camo](https://github.com/atmos/camo)。 Camo 为每个映像生成匿名 URL 代理，以隐藏您的浏览器详细信息和来自其他用户的相关信息。 URL 以 `https:///.githubusercontent.com/` 开头，并且根据您如何上传映像而有不同的子域。 直接或间接收到您的匿名化图像 URL 的任何人都可查看您的图像。 为对敏感图像保密，将它们限于私人网络或需要身份验证的服务器，而不使用 Camo。 diff --git a/translations/zh-CN/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md b/translations/zh-CN/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md index ee48dd78e5..3171482bdf 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/zh-CN/content/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account.md @@ -19,9 +19,9 @@ versions: {% mac %} -1. 将 SSH 密钥复制到剪贴板。 +1. 将 SSH 公钥复制到剪贴板。 - 如果您的 SSH 密钥文件与示例代码不同，请修改文件名以匹配您当前的设置。 在复制密钥时，请勿添加任何新行或空格。 + 如果您的 SSH 公钥文件与示例代码不同，请修改文件名以匹配您当前的设置。 在复制密钥时，请勿添加任何新行或空格。 ```shell $ pbcopy < ~/.ssh/id_ed25519.pub @@ -46,9 +46,9 @@ versions: {% windows %} -1. 将 SSH 密钥复制到剪贴板。 +1. 将 SSH 公钥复制到剪贴板。 - 如果您的 SSH 密钥文件与示例代码不同，请修改文件名以匹配您当前的设置。 在复制密钥时，请勿添加任何新行或空格。 + 如果您的 SSH 公钥文件与示例代码不同，请修改文件名以匹配您当前的设置。 在复制密钥时，请勿添加任何新行或空格。 ```shell $ clip < ~/.ssh/id_ed25519.pub @@ -73,9 +73,9 @@ versions: {% linux %} -1. 将 SSH 密钥复制到剪贴板。 +1. 将 SSH 公钥复制到剪贴板。 - 如果您的 SSH 密钥文件与示例代码不同，请修改文件名以匹配您当前的设置。 在复制密钥时，请勿添加任何新行或空格。 + 如果您的 SSH 公钥文件与示例代码不同，请修改文件名以匹配您当前的设置。 在复制密钥时，请勿添加任何新行或空格。 ```shell $ sudo apt-get install xclip 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 91420f0bd8..b5c995c3fd 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 @@ -9,7 +9,7 @@ versions: enterprise-server: '*' --- -您必须为 {% data variables.product.product_name %} 帐户选择或生成密码，密码应满足以下条件： +您必须为 {% data variables.product.product_name %} 帐户选择或生成密码，密码至少应满足以下条件： - 至少 8 个字符，包含数字和小写字母；或者 - 至少 16 个字符，任意字符组合 diff --git a/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index d29629f2d2..27ef9367e9 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/zh-CN/content/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -100,7 +100,7 @@ versions: {% note %} - **Note:** If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line. + **注意：** 如果您选择不向密钥添加密码，应该省略 `UseKeychain` 行。 {% endnote %} @@ -110,7 +110,7 @@ versions: ``` {% note %} - **注：**`-K` 选项位于 Apple 的 `ssh-add` 标准版本中，当您将 ssh 密钥添加到 ssh-agent 时，它会将密码存储在您的密钥链中。 If you chose not to add a passphrase to your key, run the command without the `-K` option. + **注：**`-K` 选项位于 Apple 的 `ssh-add` 标准版本中，当您将 ssh 密钥添加到 ssh-agent 时，它会将密码存储在您的密钥链中。 如果选择不向密钥添加密码，请运行命令，而不使用 `-K` 选项。 如果您没有安装 Apple 的标准版本，可能会收到错误消息。 有关解决此错误的详细信息，请参阅“[错误：ssh-add：非法选项 -- K](/articles/error-ssh-add-illegal-option-k)”。 diff --git a/translations/zh-CN/content/github/authenticating-to-github/index.md b/translations/zh-CN/content/github/authenticating-to-github/index.md index 6cceee5010..625a1793b4 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/index.md +++ b/translations/zh-CN/content/github/authenticating-to-github/index.md @@ -35,11 +35,9 @@ versions: {% link_in_list /reviewing-your-authorized-applications-oauth %} {% link_in_list /reviewing-your-security-log %} {% link_in_list /removing-sensitive-data-from-a-repository %} - {% link_in_list /about-anonymized-image-urls %} {% link_in_list /about-githubs-ip-addresses %} {% link_in_list /githubs-ssh-key-fingerprints %} - {% link_in_list /sudo-mode %} {% link_in_list /preventing-unauthorized-access %} {% topic_link_in_list /securing-your-account-with-two-factor-authentication-2fa %} @@ -48,18 +46,14 @@ versions: {% link_in_list /configuring-two-factor-authentication-recovery-methods %} {% link_in_list /accessing-github-using-two-factor-authentication %} {% link_in_list /recovering-your-account-if-you-lose-your-2fa-credentials %} - {% link_in_list /changing-two-factor-authentication-delivery-methods-for-your-mobile-device %} {% link_in_list /countries-where-sms-authentication-is-supported %} - {% link_in_list /disabling-two-factor-authentication-for-your-personal-account %} - {% topic_link_in_list /authenticating-with-saml-single-sign-on %} {% link_in_list /about-authentication-with-saml-single-sign-on %} {% link_in_list /authorizing-an-ssh-key-for-use-with-saml-single-sign-on %} {% link_in_list /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-your-active-saml-sessions %} - {% topic_link_in_list /connecting-to-github-with-ssh %} {% link_in_list /about-ssh %} {% link_in_list /checking-for-existing-ssh-keys %} @@ -68,13 +62,9 @@ versions: {% link_in_list /testing-your-ssh-connection %} {% link_in_list /working-with-ssh-key-passphrases %} {% topic_link_in_list /troubleshooting-ssh %} - {% link_in_list /using-ssh-over-the-https-port %} - {% link_in_list /recovering-your-ssh-key-passphrase %} - {% link_in_list /deleted-or-missing-ssh-keys %} - {% link_in_list /error-permission-denied-publickey %} {% link_in_list /error-bad-file-number %} {% link_in_list /error-key-already-in-use %} @@ -82,9 +72,7 @@ versions: {% link_in_list /error-permission-to-userrepo-denied-to-userother-repo %} {% link_in_list /error-agent-admitted-failure-to-sign %} {% link_in_list /error-ssh-add-illegal-option----k %} - {% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %} - {% link_in_list /error-were-doing-an-ssh-key-audit %} {% topic_link_in_list /managing-commit-signature-verification %} {% link_in_list /about-commit-signature-verification %} diff --git a/translations/zh-CN/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md b/translations/zh-CN/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md index 519b06f54d..181d3ac5b1 100644 --- a/translations/zh-CN/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md +++ b/translations/zh-CN/content/github/authenticating-to-github/removing-sensitive-data-from-a-repository.md @@ -40,6 +40,12 @@ $ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA $ bfg --replace-text passwords.txt ``` +删除敏感数据后，必须强制将更改推送到 {% data variables.product.product_name %}。 + +```shell +$ git push --force +``` + 有关完整的使用和下载说明，请参阅 [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) 的文档。 #### 使用 filter-branch 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 bbf9ce37bc..8b098a1529 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 @@ -33,7 +33,7 @@ versions: ### 了解安全日志中的事件 {% endif %} -The events listed in your security log are triggered by your actions. Actions are grouped into the following categories: +安全日志中列出的事件由您的操作触发。 操作分为以下几类： | 类别名称 | 描述 | | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% if currentVersion == "free-pro-team@latest" %} @@ -61,13 +61,13 @@ The events listed in your security log are triggered by your actions. Actions ar {% endif %} -### Security log actions +### 安全日志操作 -An overview of some of the most common actions that are recorded as events in the security log. +安全日志中记录为事件的一些最常见操作的概述。 {% if currentVersion == "free-pro-team@latest" %} -#### `account_recovery_token` category actions +#### `account_recovery_token` 类操作 | 操作 | 描述 | | --------------- | ----------------------------------------------------------------------------------------- | @@ -75,20 +75,20 @@ An overview of some of the most common actions that are recorded as events in th | `recover` | 当您成功[取回帐户恢复令牌](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)时触发。 | | `recover_error` | 当 {% data variables.product.prodname_dotcom %} 无法验证所使用的令牌时触发。 | -#### `billing` category actions +#### `billing` 类操作 | 操作 | 描述 | | --------------------- | ----------------------------------------------------------------------------------------------------------- | | `change_billing_type` | 当您[更改 {% data variables.product.prodname_dotcom %} 的支付方式](/articles/adding-or-editing-a-payment-method)时触发。 | | `change_email` | 当您[更改您的电子邮件地址](/articles/changing-your-primary-email-address)时触发。 | -#### `marketplace_agreement_signature` category actions +#### `marketplace_agreement_signature` 类操作 | 操作 | 描述 | | -------- | --------------------------------------------------------------- | | `create` | 在签署 {% data variables.product.prodname_marketplace %} 开发者协议时触发。 | -#### `marketplace_listing` category actions +#### `marketplace_listing` 类操作 | 操作 | 描述 | | --------- | -------------------------------------------------------------------- | @@ -100,7 +100,7 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} -#### `oauth_access` category actions +#### `oauth_access` 类操作 | 操作 | 描述 | | --------- | ------------------------------------------------------------------------------------------------------------------------ | @@ -109,7 +109,7 @@ An overview of some of the most common actions that are recorded as events in th {% if currentVersion == "free-pro-team@latest" %} -#### `payment_method` category actions +#### `payment_method` 类操作 | 操作 | 描述 | | -------- | ------------------------------------------------------ | @@ -119,13 +119,13 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} -#### `profile_picture` category actions +#### `profile_picture` 类操作 | 操作 | 描述 | | -------- | ------------------------------------------------------------ | | `update` | 当您[设置或更新个人资料图片](/articles/setting-your-profile-picture/)时触发。 | -#### `project` category actions +#### `project` 类操作 | 操作 | 描述 | | ------------------------ | --------------------------------- | @@ -138,14 +138,14 @@ An overview of some of the most common actions that are recorded as events in th | `unlink` | 当仓库从项目板解除链接时触发。 | | `update_user_permission` | 在项目板中添加或删除外部协作者时，或者他们的权限级别被更改时触发。 | -#### `public_key` category actions +#### `public_key` 类操作 | 操作 | 描述 | | -------- | ------------------------------------------------------------------------------------------------------------------------- | | `create` | 当您[为 {% data variables.product.product_name %} 帐户添加新公共 SSH 密钥](/articles/adding-a-new-ssh-key-to-your-github-account)时触发。 | | `delete` | 当您[删除 {% data variables.product.product_name %} 帐户的公共 SSH 密钥](/articles/reviewing-your-ssh-keys)时触发。 | -#### `repo` category actions +#### `repo` 类操作 | 操作 | 描述 | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -169,14 +169,14 @@ An overview of some of the most common actions that are recorded as events in th | `unarchived` | 当仓库所有者取消存档仓库时触发。 | {% if currentVersion == "free-pro-team@latest" %} -#### `sponsors` category actions +#### `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#sponsoring-a-developer)”） | +| `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` | 当您更改是否接收被赞助开发者的电子邮件更新时触发（请参阅“[管理赞助](/articles/managing-your-sponsorship)”） | | `sponsor_sponsorship_tier_change` | 当您升级或降级赞助时触发（请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”） | | `sponsored_developer_approve` | 当您的 {% data variables.product.prodname_sponsors %} 帐户被批准时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） | @@ -190,7 +190,7 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} {% if currentVersion == "free-pro-team@latest" %} -#### `successor_invitation` category actions +#### `successor_invitation` 类操作 | 操作 | 描述 | | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -203,7 +203,7 @@ An overview of some of the most common actions that are recorded as events in th {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -#### `team` category actions +#### `team` 类操作 | 操作 | 描述 | | ------------------- | ------------------------------------------------------------------------ | @@ -217,7 +217,7 @@ An overview of some of the most common actions that are recorded as events in th {% endif %} {% if currentVersion != "github-ae@latest" %} -#### `two_factor_authentication` category actions +#### `two_factor_authentication` 类操作 | 操作 | 描述 | | ---------- | ----------------------------------------------------------------------------------- | @@ -225,24 +225,24 @@ An overview of some of the most common actions that are recorded as events in th | `disabled` | 在禁用双重身份验证时触发。 | {% endif %} -#### `user` category actions +#### `user` 类操作 -| 操作 | 描述 | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_email` | 在您{% if currentVersion != "github-ae@latest" %}[新增电子邮件地址](/articles/changing-your-primary-email-address){% else %}新增电子邮件地址{% endif %}时触发。 | -| `create` | Triggered when you create a new user account.{% if currentVersion != "github-ae@latest" %} -| `change_password` | 当您更改密码时触发。 | +| 操作 | 描述 | +| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| `add_email` | 在您{% if currentVersion != "github-ae@latest" %}[新增电子邮件地址](/articles/changing-your-primary-email-address){% else %}新增电子邮件地址{% endif %}时触发。 | +| `create` | 在创建新帐户时触发。{% if currentVersion != "github-ae@latest" %} +| `change_password` | 当您更改密码时触发。 | | `forgot_password` | 在您要求[重置密码](/articles/how-can-i-reset-my-password)时触发。{% endif %} -| `hide_private_contributions_count` | 当您[在个人资料中隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。 | -| `login` | 当您登录 {% data variables.product.product_location %} 时触发。 | -| `failed_login` | 当您未能成功登录时触发。 | -| `remove_email` | 当您删除电子邮件地址时触发。 | -| `rename` | Triggered when you rename your account.{% if currentVersion == "free-pro-team@latest" %} +| `hide_private_contributions_count` | 当您[在个人资料中隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。 | +| `login` | 当您登录 {% data variables.product.product_location %} 时触发。 | +| `failed_login` | 当您未能成功登录时触发。 | +| `remove_email` | 当您删除电子邮件地址时触发。 | +| `rename` | 在重命名帐户时触发。{% if currentVersion == "free-pro-team@latest" %} | `report_content` | 当您[举报议题或拉取请求，或者举报对议题、拉取请求或提交的评论](/articles/reporting-abuse-or-spam)时触发。{% endif %} -| `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion != "github-ae@latest" %} +| `show_private_contributions_count` | 当您[在个人资料中公开私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。{% if currentVersion != "github-ae@latest" %} | `two_factor_requested` | 当 {% data variables.product.product_name %} 要求您提供[双重身份验证代码](/articles/accessing-github-using-two-factor-authentication)时触发。{% endif %} -#### `user_status` category actions +#### `user_status` 类操作 | 操作 | 描述 | | --------- | -------------------------------------------------------------------------------------------- | diff --git a/translations/zh-CN/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md b/translations/zh-CN/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md index c3e3530ccd..c8ff60023c 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md +++ b/translations/zh-CN/content/github/building-a-strong-community/about-issue-and-pull-request-templates.md @@ -13,7 +13,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -You can create default issue and pull request templates for your organization or user account. 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 +您可以为组织或用户帐户创建议题和拉取请求模板。 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 {% endif %} diff --git a/translations/zh-CN/content/github/building-a-strong-community/about-wikis.md b/translations/zh-CN/content/github/building-a-strong-community/about-wikis.md index ee109b9c7e..159957050d 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/about-wikis.md +++ b/translations/zh-CN/content/github/building-a-strong-community/about-wikis.md @@ -15,9 +15,9 @@ versions: 使用 wiki，可以像在 {% data variables.product.product_name %} 的任何其他位置一样编写内容。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/articles/getting-started-with-writing-and-formatting-on-github)”。 我们使用[开源标记库](https://github.com/github/markup)将不同的格式转换为 HTML，以便选择使用 Markdown 或任何其他支持的格式编写。 -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}If you create a wiki in a public repository, the wiki is available to {% if enterpriseServerVersions contains currentVersion %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in an internal or private repository, {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}people{% elsif currentVersion == "github-ae@latest" %}enterprise members{% endif %} with access to the repository can also access the wiki. 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。 +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}如果您在公共仓库中创建 wiki，则该 wiki 可供{% if enterpriseServerVersions contains currentVersion %}具有 {% data variables.product.product_location %} 访问权限的任何人{% else %}公共{% endif %}访问。 {% endif %}如果您在内部或私有仓库中创建 wiki，对该仓库具有访问权限的{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}人员{% elsif currentVersion == "github-ae@latest" %}企业成员{% endif %}也可以访问该 wiki。 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。 -您可以直接在 {% data variables.product.product_name %} 上编辑 wikis，也可在本地编辑 wiki 文件。 By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.product.product_location %} to contribute to a wiki in {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} repository. 更多信息请参阅“[更改 wikis 的访问权限](/articles/changing-access-permissions-for-wikis)”。 +您可以直接在 {% data variables.product.product_name %} 上编辑 wikis，也可在本地编辑 wiki 文件。 默认情况下，只有能够写入仓库的人才可更改 wikis，但您可以允许 {% data variables.product.product_location %} 上的每个人参与{% if currentVersion == "github-ae@latest" %}内部{% else %}公共{% endif %}仓库中的 wiki。 更多信息请参阅“[更改 wikis 的访问权限](/articles/changing-access-permissions-for-wikis)”。 ### 延伸阅读 diff --git a/translations/zh-CN/content/github/building-a-strong-community/adding-support-resources-to-your-project.md b/translations/zh-CN/content/github/building-a-strong-community/adding-support-resources-to-your-project.md index 5532cee13d..13f4ad83fd 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/adding-support-resources-to-your-project.md +++ b/translations/zh-CN/content/github/building-a-strong-community/adding-support-resources-to-your-project.md @@ -15,7 +15,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -You can create default support resources for your organization or user account. 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 +您可以为组织或用户帐户创建默认支持资源。 更多信息请参阅“[创建默认社区健康文件](/github/building-a-strong-community/creating-a-default-community-health-file)”。 {% endif %} diff --git a/translations/zh-CN/content/github/building-a-strong-community/index.md b/translations/zh-CN/content/github/building-a-strong-community/index.md index d5a722a3f2..2784d54c00 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/index.md +++ b/translations/zh-CN/content/github/building-a-strong-community/index.md @@ -13,21 +13,15 @@ versions: ### 目录 {% topic_link_in_list /setting-up-your-project-for-healthy-contributions %} - {% link_in_list /about-community-management-and-moderation %} {% link_in_list /about-community-profiles-for-public-repositories %} {% link_in_list /accessing-a-projects-community-profile %} {% link_in_list /adding-a-code-of-conduct-to-your-project %} - {% link_in_list /setting-guidelines-for-repository-contributors %} {% link_in_list /adding-a-license-to-a-repository %} {% link_in_list /adding-support-resources-to-your-project %} - {% link_in_list /creating-a-default-community-health-file %} - - {% link_in_list /encouraging-helpful-contributions-to-your-project-with-labels %} - {% topic_link_in_list /using-templates-to-encourage-useful-issues-and-pull-requests %} {% link_in_list /about-issue-and-pull-request-templates %} {% link_in_list /configuring-issue-templates-for-your-repository %} @@ -42,7 +36,6 @@ versions: {% link_in_list /tracking-changes-in-a-comment %} {% link_in_list /managing-how-contributors-report-abuse-in-your-organizations-repository %} {% link_in_list /managing-reported-content-in-your-organizations-repository %} - {% topic_link_in_list /maintaining-your-safety-on-github %} {% link_in_list /blocking-a-user-from-your-personal-account %} {% link_in_list /viewing-users-youve-blocked-from-your-personal-account %} @@ -51,7 +44,6 @@ versions: {% link_in_list /viewing-users-who-are-blocked-from-your-organization %} {% link_in_list /unblocking-a-user-from-your-organization %} {% link_in_list /reporting-abuse-or-spam %} - {% topic_link_in_list /documenting-your-project-with-wikis %} {% link_in_list /about-wikis %} {% link_in_list /adding-or-editing-wiki-pages %} @@ -60,10 +52,8 @@ versions: {% link_in_list /viewing-a-wikis-history-of-changes %} {% link_in_list /changing-access-permissions-for-wikis %} {% link_in_list /disabling-wikis %} - {% topic_link_in_list /collaborating-with-your-team %} {% link_in_list /about-team-discussions %} {% link_in_list /creating-a-team-discussion %} {% link_in_list /editing-or-deleting-a-team-discussion %} {% link_in_list /pinning-a-team-discussion %} - diff --git a/translations/zh-CN/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md b/translations/zh-CN/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md index 954ca4085e..05d1ba750c 100644 --- a/translations/zh-CN/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md +++ b/translations/zh-CN/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md @@ -58,4 +58,4 @@ versions: ### 延伸阅读 - 开源指南的“[启动开源项目](https://opensource.guide/starting-a-project/)”部分{% if currentVersion == "free-pro-team@latest" %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %} +- "[添加许可到仓库](/articles/adding-a-license-to-a-repository)"{% endif %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-branches.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-branches.md index 5d9001a375..92a6dba43e 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-branches.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/about-branches.md @@ -23,7 +23,7 @@ versions: ### 关于默认分支 -{% data reusables.branches.new-repo-default-branch %} 默认分支是任何人访问您的仓库时 {% data variables.product.prodname_dotcom %} 显示的分支。 The default branch is also the initial branch that Git checks out locally when someone clones the repository. {% data reusables.branches.default-branch-automatically-base-branch %} +{% data reusables.branches.new-repo-default-branch %} 默认分支是任何人访问您的仓库时 {% data variables.product.prodname_dotcom %} 显示的分支。 默认分支也是初始分支，当有人克隆存储库时，Git 会在本地检出该分支。 {% data reusables.branches.default-branch-automatically-base-branch %} 默认情况下，{% data variables.product.product_name %} 将任何新仓库中的默认分支命名为{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}`main`{% else %}`master`{% endif %}。 @@ -75,7 +75,7 @@ versions: - 如果对分支启用了必需拉取请求审查，则在满足拉取请求审查策略中的所有要求之前，无法将更改合并到分支。 更多信息请参阅“[合并拉取请求](/articles/merging-a-pull-request)”。 - 如果对分支启用了代码所有者的必需审查，并且拉取请求修改具有所有者的代码，则代码所有者必须批准拉取请求后才可合并。 更多信息请参阅“[关于代码所有者](/articles/about-code-owners)”。 - 如果对分支启用了必需提交签名，则无法将任何提交推送到未签名和验证的分支。 更多信息请参阅“[关于提交签名验证](/articles/about-commit-signature-verification)”和“[关于必需提交签名](/articles/about-required-commit-signing)”。{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -- If you use {% data variables.product.prodname_dotcom %}'s conflict editor to fix conflicts for a pull request that you created from a protected branch, {% data variables.product.prodname_dotcom %} helps you to create an alternative branch for the pull request, so that your resolution of the conflicts can be merged. 更多信息请参阅“[解决 {% data variables.product.prodname_dotcom %} 上的合并冲突](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)”。{% endif %} +- 如果您使用 {% data variables.product.prodname_dotcom %} 的冲突编辑器来解决从受保护分支创建拉取请求的冲突，{% data variables.product.prodname_dotcom %} 可帮助您为拉取请求创建一个备用分支，以解决合并冲突。 更多信息请参阅“[解决 {% data variables.product.prodname_dotcom %} 上的合并冲突](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)”。{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md index 1bae4fa4c7..dfd60e1f9c 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -22,7 +22,11 @@ versions: {% data reusables.pull_requests.automatically-delete-branches %} -如果要删除的分支是仓库的默认分支，则在删除该分支之前必须选择新的默认分支。 更多信息请参阅“[更改默认分支](/github/administering-a-repository/changing-the-default-branch)”。 +{% note %} + +**注意：**如果要删除的分支是仓库的默认分支，则在删除该分支之前必须选择新的默认分支。 更多信息请参阅“[更改默认分支](/github/administering-a-repository/changing-the-default-branch)”。 + +{% endnote %} 如果要删除的分支与打开的拉取请求关联，则在删除该分支之前必须合并或关闭拉取请求。 更多信息请参阅“[合并拉取请求](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)”和“[关闭拉取请求](/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request)”。 diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/index.md index 1203e34a47..02c1e31e27 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/index.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/index.md @@ -29,9 +29,7 @@ versions: {% link_in_list /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility %} {% topic_link_in_list /collaborating-on-repositories-with-code-quality-features %} {% link_in_list /about-status-checks %} - {% link_in_list /working-with-pre-receive-hooks %} - {% topic_link_in_list /proposing-changes-to-your-work-with-pull-requests %} {% link_in_list /about-branches %} {% link_in_list /creating-and-deleting-branches-within-your-repository %} @@ -39,9 +37,7 @@ versions: {% link_in_list /about-comparing-branches-in-pull-requests %} {% link_in_list /creating-a-pull-request %} {% link_in_list /creating-a-pull-request-from-a-fork %} - {% link_in_list /changing-the-stage-of-a-pull-request %} - {% link_in_list /requesting-a-pull-request-review %} {% link_in_list /changing-the-base-branch-of-a-pull-request %} {% link_in_list /committing-changes-to-a-pull-request-branch-created-from-a-fork %} @@ -52,15 +48,12 @@ versions: {% topic_link_in_list /reviewing-changes-in-pull-requests %} {% link_in_list /about-pull-request-reviews %} {% link_in_list /reviewing-proposed-changes-in-a-pull-request %} - {% link_in_list /filtering-files-in-a-pull-request %} - {% link_in_list /finding-changed-methods-and-functions-in-a-pull-request %} {% link_in_list /commenting-on-a-pull-request %} {% link_in_list /viewing-a-pull-request-review %} - + {% link_in_list /reviewing-dependency-changes-in-a-pull-request %} {% link_in_list /incorporating-feedback-in-your-pull-request %} - {% link_in_list /approving-a-pull-request-with-required-reviews %} {% link_in_list /dismissing-a-pull-request-review %} {% link_in_list /checking-out-pull-requests-locally %} diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md new file mode 100644 index 0000000000..20744e85be --- /dev/null +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -0,0 +1,74 @@ +--- +title: Reviewing dependency changes in a pull request +intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Dependency review is currently in beta and subject to change. + +{% endnote %} + +### About dependency review + +If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. + +Dependency review is available in: + +* All public repositories. +* Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. 更多信息请参阅“[探索仓库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)”。 + +Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. + +By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. {% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix them at some later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)." + +Dependency review supports the same languages and package management ecosystems as the dependency graph. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。 + +### Reviewing dependencies in a pull request + +{% data reusables.repositories.sidebar-pr %} +{% data reusables.repositories.choose-pr-review %} +{% data reusables.repositories.changed-files %} + +1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. + + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) + + {% note %} + + **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% endnote %} + +1. Check the dependencies listed in the dependency review. + + ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) + + Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name. + + The icon beside each dependency indicates whether the dependency has been added ({% octicon "diff-added" aria-label="Dependency added icon" %}), updated ({% octicon "diff-modified" aria-label="Dependency modified icon" %}), or removed ({% octicon "diff-removed" aria-label="Dependency removed icon" %}) in this pull request. + + Other information includes: + + * The version, or version range, of the new, updated, or deleted dependency. + * For a specific version of a dependency: + * The age of that release of the dependency. + * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency. + * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project. + + Where a dependency has a known vulnerability, the warning message includes: + + * A brief description of the vulnerability. + * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability. + * The severity of the vulnerability. + * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release. + +1. You can return to the original view of the file by clicking the source diff button. + + ![The source diff button](/assets/images/help/pull_requests/dependency-review-source-diff.png) diff --git a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 0d0b0aee3e..907fa03d11 100644 --- a/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -29,6 +29,18 @@ versions: ![取消审查按钮](/assets/images/help/pull_requests/cancel-review-button.png) +{% 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)." + +{% data reusables.repositories.changed-files %} + +1. On the right of the header for a manifest or lock file, display the dependency review by clicking the rich diff button. + + ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) +{% endif %} + ### 将文件标记为已查看 在完成审查文件后，您可以将文件标记为已查看，该文件将会收起。 如果查看过的文件有更改，将会取消已查看的标记。 @@ -53,8 +65,5 @@ versions: ### 延伸阅读 -- “[关于拉取请求审查](/articles/about-pull-request-reviews)” -- "[关于拉取请求的必要审查](/articles/about-required-reviews-for-pull-requests)" -- “[批准需要审查的拉取请求](/articles/approving-a-pull-request-with-required-reviews)” -- "[评论拉取请求](/articles/commenting-on-a-pull-request)" -- "[按审查状态过滤拉取请求](/articles/filtering-pull-requests-by-review-status)" +- "[关于拉取请求的必要审查](/github/administering-a-repository/about-required-reviews-for-pull-requests)" +- "[按审查状态过滤拉取请求](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)" 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 8d1d9c21df..b65476a885 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 @@ -56,7 +56,7 @@ versions: {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -#### Changing the visibility of an internal repository +#### 更改内部仓库的可见性 {% note %} @@ -64,11 +64,11 @@ versions: {% endnote %} -If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or user account will remain private. +如果企业策略允许复刻，则内部仓库的任何复刻都将是私有的。 如果您更改内部仓库的可见性，组织或用户帐户拥有的任何复刻都将保持私有。 -##### Deleting the internal repository +##### 删除内部仓库 -If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network. +如果您更改了内部仓库的可见性，然后删除仓库，复刻将继续存在于单独的网络中。 {% endif %} @@ -78,4 +78,4 @@ If you change the visibility of an internal repository and then delete the repos - "[关于复刻](/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)" -- "{% 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 %}" +- "{% 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/committing-changes-to-your-project/index.md b/translations/zh-CN/content/github/committing-changes-to-your-project/index.md index d78c163565..e59de39090 100644 --- a/translations/zh-CN/content/github/committing-changes-to-your-project/index.md +++ b/translations/zh-CN/content/github/committing-changes-to-your-project/index.md @@ -16,9 +16,7 @@ versions: {% topic_link_in_list /creating-and-editing-commits %} {% link_in_list /about-commits %} {% link_in_list /creating-a-commit-with-multiple-authors %} - {% link_in_list /creating-a-commit-on-behalf-of-an-organization %} - {% link_in_list /changing-a-commit-message %} {% topic_link_in_list /viewing-and-comparing-commits %} {% link_in_list /commit-branch-and-tag-labels %} 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 a7ae9d0d05..f478fec023 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 @@ -40,9 +40,9 @@ versions: ### CODEOWNERS 语法 -CODEOWNERS 文件使用遵循 [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) 文件中所用规则的模式。 模式后接一个或多个使用标准 `@username` 或 `@org/team-name` 格式的 {% data variables.product.prodname_dotcom %} 用户名或团队名称。 您也可以通过已经添加到其 {% data variables.product.product_name %} 帐户的电子邮件地址来指代用户，如 `user@example.com`。 +CODEOWNERS 文件使用遵循 [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) 文件中所用大多数规则的模式，但有[一些例外](#syntax-exceptions)。 模式后接一个或多个使用标准 `@username` 或 `@org/team-name` 格式的 {% data variables.product.prodname_dotcom %} 用户名或团队名称。 您也可以通过已经添加到其 {% data variables.product.product_name %} 帐户的电子邮件地址来指代用户，如 `user@example.com`。 -如果 CODEOWNERS 文件中的任何行包含无效语法，则该文件将不会被检测并且不会用于请求审查。 无效语法包括 {% data variables.product.product_name %} 上不存在的内联注释和用户或团队名称。 +如果 CODEOWNERS 文件中的任何行包含无效语法，则该文件将不会被检测并且不会用于请求审查。 #### CODEOWNERS 文件示例 ``` # This is a comment. @@ -84,6 +84,13 @@ apps/ @octocat # subdirectories. /docs/ @doctocat ``` +#### 语法例外 +gitignore 文件有一些语法规则在 CODEOWNERS 文件中不起作用： +- 使用 `\` 对以 `#` 开头的模式转义，使其被当作模式而不是注释 +- 使用 `!` 否定模式 +- 使用 `[ ]` 定义字符范围 + + ### 延伸阅读 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-readmes.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-readmes.md index 90a03a1166..8a6ac34427 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-readmes.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-readmes.md @@ -13,9 +13,9 @@ versions: ### 关于自述文件 -You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% if currentVersion == "free-pro-team@latest" %}, contribution guidelines, and a code of conduct{% elsif enterpriseServerVersions contains currentVersion %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions. +您可以将 README 文件添加到仓库来交流有关您项目的重要信息。 README 连同仓库许可{% if currentVersion == "free-pro-team@latest" %}、参与指南以及行为准则{% elsif enterpriseServerVersions contains currentVersion %} 和参与指南{% endif %}，用于传达项目的要求，并且帮助您管理参与。 -For more information about providing guidelines for your project, see {% if currentVersion == "free-pro-team@latest" %}"[Adding a code of conduct to your project](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." +有关为项目提供指南的更多信息，请参阅 {% if currentVersion == "free-pro-team@latest" %}“[为项目添加行为准则](/github/building-a-strong-community/adding-a-code-of-conduct-to-your-project)”和{% endif %}“[设置健康参与的项目](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)”。 自述文件通常是访问者在访问仓库时看到的第一个项目。 自述文件通常包含以下信息： - 项目做什么 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repositories.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repositories.md index 11d8bb60f2..ec769955be 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repositories.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/about-repositories.md @@ -1,6 +1,6 @@ --- title: 关于仓库 -intro: 仓库就像项目的文件夹。 项目的仓库包含项目的所有文件，并存储每个文件的修订记录。 您也可以在仓库中讨论并管理项目的工作。 +intro: 仓库包含项目的所有文件，并存储每个文件的修订记录。 您可以在仓库中讨论并管理项目的工作。 redirect_from: - /articles/about-repositories versions: @@ -22,9 +22,11 @@ versions: 每个人和组织都可拥有无限的仓库，并且可以邀请无限的协作者参与所有仓库。 {% endif %} -您可以使用仓库议题、拉取请求及项目板与其他人协作处理您的项目。 - -![octocat/Hello-World 仓库的主页面](/assets/images/help/repository/repo-main-page.png) +您可以使用仓库管理您的工作并与他人合作。 +- 您可以使用议题来收集用户反馈，报告软件缺陷，并组织您想要完成的任务。 更多信息请参阅“[关于议题](/github/managing-your-work-on-github/about-issues)”。 +- {% data reusables.discussions.you-can-use-discussions %} +- 您可以使用拉取请求来建议对仓库的更改。 更多信息请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)”。 +- 您可以使用项目板来组织议题和拉取请求并排定优先级。 更多信息请参阅“[关于项目板](/github/managing-your-work-on-github/about-project-boards)”。 {% data reusables.repositories.repo-size-limit %} 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 f467ee2463..6135c03ecd 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 @@ -12,7 +12,7 @@ versions: {% if currentversion == "github-ae@latest" %}当您创建由您的用户帐户拥有的仓库时，仓库始终是私有的。 创建组织拥有的仓库时，可以选择将仓库设为私有或内部。{% else %}创建仓库时，可以选择使仓库成为公共或私有。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} 如果要在组织中创建{% if currentVersion == "free-pro-team@latest" %} 由企业帐户拥有的仓库{% endif %}，也可以选择将仓库设为内部。{% endif %}{% endif %} {% if enterpriseServerVersions contains currentVersion %} -If +如果 {% data variables.product.product_location %} 不是私人模式或在防火墙后面，所有人都可以在互联网上访问公共仓库。 或者，使用 {% data variables.product.product_location %} 的每个人都可以使用公共仓库，包括外部协作者。 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 {% if currentversion ver_gt "enterprise-server@2.19" %} 内部仓库可供企业成员访问。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。{% endif %} {% elsif currentVersion == "github-ae@latest" %} 私有仓库仅可供您、您明确与其共享访问权限的人访问，而对于组织仓库，只有某些组织成员可以访问。 所有企业成员均可访问内部仓库。 更多信息请参阅“[关于内部仓库](#about-internal-repositories)”。 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md index 452b673e21..55d66fca44 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/https-cloning-errors.md @@ -45,16 +45,16 @@ versions: ```shell $ git remote -v # View existing remotes -> origin https://github.com/github/reactivecocoa.git (fetch) -> origin https://github.com/github/reactivecocoa.git (push) +> origin https://github.com/ghost/reactivecocoa.git (fetch) +> origin https://github.com/ghost/reactivecocoa.git (push) -$ git remote set-url origin https://github.com/github/ReactiveCocoa.git +$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git # Change the 'origin' remote's URL $ git remote -v # Verify new remote URL -> origin https://github.com/github/ReactiveCocoa.git (fetch) -> origin https://github.com/github/ReactiveCocoa.git (push) +> origin https://github.com/ghost/ReactiveCocoa.git (fetch) +> origin https://github.com/ghost/ReactiveCocoa.git (push) ``` 也可通过 [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) 应用程序更改 URL。 diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/index.md index 4bfa680bc0..461f85adcb 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/index.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repositories %} {% link_in_list /about-repository-visibility %} {% link_in_list /creating-a-new-repository %} - {% link_in_list /creating-a-repository-from-a-template %} - {% link_in_list /about-readmes %} {% link_in_list /about-code-owners %} {% link_in_list /about-repository-languages %} {% link_in_list /licensing-a-repository %} - {% link_in_list /creating-a-template-repository %} - {% link_in_list /creating-an-issues-only-repository %} {% link_in_list /limits-for-viewing-content-and-diffs-in-a-repository %} {% link_in_list /duplicating-a-repository %} @@ -39,8 +35,6 @@ versions: {% topic_link_in_list /archiving-a-github-repository %} {% link_in_list /about-archiving-repositories %} {% link_in_list /archiving-repositories %} - {% link_in_list /about-archiving-content-and-data-on-github %} {% link_in_list /referencing-and-citing-content %} - {% link_in_list /backing-up-a-repository %} diff --git a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md index 1a98d4c8ca..17c0ae58b6 100644 --- a/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md +++ b/translations/zh-CN/content/github/creating-cloning-and-archiving-repositories/licensing-a-repository.md @@ -17,7 +17,7 @@ versions: {% 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. 更多信息请参阅“[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)”。 +**注：**如果您在 {% data variables.product.product_name %} 的公共仓库中发布源代码，{% if currentVersion == "free-pro-team@latest" %}根据[服务条款](/articles/github-terms-of-service)，{% endif %}其他 {% data variables.product.product_location %} 用户有权利查看您的仓库并对其复刻。 如果您已创建仓库，并且不再希望用户访问它，便可将仓库设为私有。 在将仓库的可见性变为私有时，其他用户创建的现有复刻或本地副本仍将存在。 更多信息请参阅“[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)”。 {% endnote %} diff --git a/translations/zh-CN/content/github/customizing-your-github-workflow/about-github-marketplace.md b/translations/zh-CN/content/github/customizing-your-github-workflow/about-github-marketplace.md index 4aa96f35a0..5830a1483b 100644 --- a/translations/zh-CN/content/github/customizing-your-github-workflow/about-github-marketplace.md +++ b/translations/zh-CN/content/github/customizing-your-github-workflow/about-github-marketplace.md @@ -7,26 +7,27 @@ versions: free-pro-team: '*' --- -在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 中，您可以发现、浏览和安装免费及付费工具，包括 [{% data variables.product.prodname_github_app %}、{% data variables.product.prodname_oauth_app %}](/apps/differences-between-apps/) 和 {% data variables.product.prodname_actions %}。 +在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 中，您可以发现、浏览和安装免费及付费工具，包括 {% data variables.product.prodname_github_app %}、{% data variables.product.prodname_oauth_app %} 和 {% data variables.product.prodname_actions %}。 如果您购买付费工具，将使用支付 {% data variables.product.product_name %} 订阅的帐单信息来支付工具订阅，并且在常规帐单日期会收到一张帐单。 更多信息请参阅“[关于 {% data variables.product.prodname_marketplace %} 的计费](/articles/about-billing-for-github-marketplace)”。 -您也可以选择对所选工具免费试用 14 天。 在试用期间可随时取消，您无需付费，但会自动失去对工具的使用权限。 您付费的订阅将在 14 天试用结束时开始。 更多信息请参阅“[关于 {% data variables.product.prodname_marketplace %} 的计费](/articles/about-billing-for-github-marketplace)”。 +您也可以选择对某些工具免费试用 14 天。 在试用期间可随时取消，您无需付费，但会自动失去对工具的使用权限。 您付费的订阅将在 14 天试用结束时开始。 更多信息请参阅“[关于 {% data variables.product.prodname_marketplace %} 的计费](/articles/about-billing-for-github-marketplace)”。 -{% data variables.product.prodname_github_app %} 和 {% data variables.product.prodname_oauth_app %} 可以验证或取消验证。 验证的应用程序符合 {% data variables.product.prodname_dotcom %} 设置的特定要求，经过安全性审查后列在 {% data variables.product.prodname_marketplace %} 上。 更多信息请参阅的“[在 GitHub Marketplace 上列出应用程序需满足的要求](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)”。 +### 在 {% data variables.product.prodname_marketplace %} 上查找工具 -### {% data variables.product.prodname_marketplace %} 上的 {% data variables.product.prodname_actions %} +您可以发现、浏览和安装其他人在 {% data variables.product.prodname_marketplace %} 上创建的 应用程序和操作，请参阅“[搜索 {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)”。 -您可以发现、浏览和安装其他人在 {% data variables.product.prodname_marketplace %} 上创建的 {% data variables.product.prodname_actions %}，请参阅“[搜索 {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)”。 +{% data reusables.actions.actions-not-verified %} -任何人都可在 {% data variables.product.prodname_marketplace %} 上列出操作。 与某些应用程序不同， 在 {% data variables.product.prodname_marketplace %} 上列出的 {% data variables.product.prodname_actions %} 从来不会经过 {% data variables.product.prodname_dotcom %} 验证。 +任何人都可以在 {% data variables.product.prodname_marketplace %} 上列出免费的 {% data variables.product.prodname_github_app %} 或 {% data variables.product.prodname_oauth_app %}。 付费应用程序的发布者由 {% data variables.product.company_short %} 验证，这些应用程序的列表显示有认证的创建者徽章 {% octicon "verified" aria-label="Verified creator badge" %}。 您还将看到未验证和已验证应用程序的徽章。 这些应用程序是使用以前个别应用程序验证方法来发布的。 关于当前流程的更多信息，请参阅“[关于已验证的创建者](/developers/github-marketplace/about-verified-creators)”和“[列出应用程序的要求](/developers/github-marketplace/requirements-for-listing-an-app)”。 ### 在 {% data variables.product.prodname_marketplace %} 上创建和列出工具 -有关创建要在 {% data variables.product.prodname_marketplace %} 上列出的工具的更多信息，请参阅“[应用程序](/apps)”和“[{% data variables.product.prodname_actions %}](/actions)”。 +有关创建要在 {% data variables.product.prodname_marketplace %} 上列出的工具的更多信息，请参阅“[应用程序](/developers/apps)”和“[{% data variables.product.prodname_actions %}](/actions)”。 ### 延伸阅读 - "[在 {% data variables.product.prodname_marketplace %} 中购买和安装应用程序](/articles/purchasing-and-installing-apps-in-github-marketplace)" - "[管理 {% data variables.product.prodname_marketplace %} 应用程序的计费](/articles/managing-billing-for-github-marketplace-apps)" - "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)" +- "[GitHub 应用程序和 OAuth 应用程序之间的差异](/developers/apps/differences-between-github-apps-and-oauth-apps)" diff --git a/translations/zh-CN/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/zh-CN/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md index c6b82da343..6f31e24d9b 100644 --- a/translations/zh-CN/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/zh-CN/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md @@ -15,7 +15,7 @@ versions: {% data reusables.codespaces.about-configuration %} -如果您没有在仓库中定义配置，{% data variables.product.prodname_dotcom %} 将创建一个具有基本 Linux 映像的代码空间。 基本 Linux 映像包括适用于 Node.js、JavaScript、TypeScript、Python、C++、Java、C#、.NET Core、PHP 和 PowerShell 的工具。 有关基本 Linux 映像的更多信息，请参阅 [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) 仓库。 +如果您没有在仓库中定义配置，{% data variables.product.prodname_dotcom %} 将创建一个具有基本 Linux 映像的代码空间。 基本 Linux 映像包括适用于 Python、Node.js、JavaScript、TypeScript、C++、Java、C#、F#、.NET Core、PHP、PowerShell、Go、Ruby 和 Rust 的工具。 有关基本 Linux 映像的更多信息，请参阅 [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux) 仓库。 {% data reusables.codespaces.about-personalization %} {% data reusables.codespaces.codespace-config-order %} 更多信息请参阅“[个性化您帐户的 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account)”。 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 f929ac5fc4..c276e19fea 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning.md @@ -20,7 +20,7 @@ versions: 如果 {% data variables.product.prodname_code_scanning %} 发现您的代码中可能存在漏洞或错误，{% data variables.product.prodname_dotcom %} 会在仓库中显示警报。 在修复触发警报的代码之后，{% data variables.product.prodname_dotcom %} 将关闭警报。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 -{% data variables.product.prodname_code_scanning_capc %} 使用 {% data variables.product.prodname_actions %}。 For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)." +{% data variables.product.prodname_code_scanning_capc %} 使用 {% data variables.product.prodname_actions %}。 有关 API 端点的更多信息，请参阅“[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)”。 要开始 {% data variables.product.prodname_code_scanning %}，请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”。 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md index 878369e4a0..309effd0a6 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 @@ -44,11 +44,11 @@ Scanning code when someone pushes a change, and whenever a pull request is creat #### 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)." +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)." #### 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. 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 %} 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)." @@ -148,14 +148,14 @@ jobs: matrix: language: ['javascript', 'python'] ``` - + If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. ```yaml - uses: github/codeql-action/init@v1 with: languages: cpp, csharp, python -``` +``` {% if currentVersion == "free-pro-team@latest" %} ### Analyzing Python dependencies @@ -183,20 +183,20 @@ jobs: - name: Install dependencies run: | python -m pip install --upgrade pip - if [ -f requirements.txt ]; + if [ -f requirements.txt ]; then pip install -r requirements.txt; fi # Set the `CODEQL-PYTHON` environment variable to the Python executable # that includes the dependencies - echo "::set-env name=CODEQL_PYTHON::$(which python)" + echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV - name: Initialize CodeQL uses: github/codeql-action/init@v1 with: languages: python - # Override the default behavior so that the action doesn't attempt + # Override the default behavior so that the action doesn't attempt # to auto-install Python dependencies setup-python-dependencies: false -``` +``` {% endif %} ### Running additional queries @@ -239,7 +239,7 @@ In the workflow file, use the `config-file` parameter of the `init` action to sp ``` The configuration file can be located within the local repository, or in a public, remote repository. For remote repositories, you can use the _owner/repository/file.yml@branch_ syntax. The settings in the file are written in YAML format. - + #### Specifying additional queries 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. @@ -265,15 +265,15 @@ For the interpreted languages that {% data variables.product.prodname_codeql %} ``` yaml paths: - - src -paths-ignore: + - src +paths-ignore: - src/node_modules - '**/*.test.js' ``` {% note %} -**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. @@ -298,7 +298,7 @@ You can quickly analyze small portions of a monorepo when you modify code in spe 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 `github/foo`, `github/bar`, and `github/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. +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 @@ -307,9 +307,9 @@ steps: env: TOKEN: ${{ secrets.ACCESS_TOKEN }} run: | - git config --global url."https://${TOKEN}@github.com/github/foo".insteadOf "https://github.com/github/foo" - git config --global url."https://${TOKEN}@github.com/github/bar".insteadOf "https://github.com/github/bar" - git config --global url."https://${TOKEN}@github.com/github/baz".insteadOf "https://github.com/github/baz" + 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 %} diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md index 85a1cce98e..b355df593c 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md @@ -3,7 +3,7 @@ title: 为仓库启用代码扫描 shortTitle: 启用代码扫描 intro: '您可以对项目的仓库启用 {% data variables.product.prodname_code_scanning %}。' product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'If you have write permissions to a repository, you can enable {% data variables.product.prodname_code_scanning %} for that repository.' +permissions: '如果您拥有仓库的写入权限，便可对该仓库启用 {% data variables.product.prodname_code_scanning %}。' redirect_from: - /github/managing-security-vulnerabilities/configuring-automated-code-scanning - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning @@ -23,7 +23,7 @@ versions: ### 使用操作启用 {% data variables.product.prodname_code_scanning %} -{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. 更多信息请参阅“[关于 {% 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" %}使用操作运行 {% data variables.product.prodname_code_scanning %} 需时数分钟。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).”{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -31,14 +31,14 @@ versions: 4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with code scanning" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png) 5. Optionally, to customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." - Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing. + 一般来说，您可以提交 {% data variables.product.prodname_codeql_workflow %} 而不对其做任何更改。 但是，许多第三方工作流程需要额外的配置，因此在提交之前请阅读工作流程中的注释。 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)。” 6. 使用 **Start commit（开始提交）**下拉菜单，并键入提交消息。 ![开始提交](/assets/images/help/repository/start-commit-commit-new-file.png) 7. 选择您是想直接提交到默认分支，还是创建新分支并启动拉取请求。 ![选择提交位置](/assets/images/help/repository/start-commit-choose-where-to-commit.png) 8. 单击 **Commit new file（提交新文件）**或 **Propose new file（提议新文件）**。 -In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence. +在默认 {% data variables.product.prodname_codeql_workflow %} 中，{% data variables.product.prodname_code_scanning %} 配置为在每次将更改推送到默认分支或任何受保护分支或者对默认分支提出拉取请求时分析代码。 因此，{% data variables.product.prodname_code_scanning %} 将立即开始。 ### You decide how you generate {% data variables.product.prodname_code_scanning %} alerts, and which tools you use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. For more information, see "[About {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)." @@ -50,64 +50,64 @@ After you enable {% data variables.product.prodname_code_scanning %}, you can mo ![After you commit the workflow file or create a pull request, {% data variables.product.prodname_code_scanning %} will analyze your code according to the frequency you specified in your workflow file. If you created a pull request, {% data variables.product.prodname_code_scanning %} will only analyze the code on the pull request's topic branch until you merge the pull request into the default branch of the repository.](/assets/images/help/repository/code-scanning-actions-list.png) -1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. +1. 单击 {% data variables.product.prodname_code_scanning %} 工作流程的项目。 -1. Click the job name on the left. For example, **Analyze (LANGUAGE)**. +1. 单击左侧的作业名称。 例如 **Analyze (LANGUAGE)**。 - ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + ![{% 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. 查看此工作流运行时操作的日志记录输出。 -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. 在所有作业完成后，您可以查看已识别的任何 {% data variables.product.prodname_code_scanning %} 警报的详细信息。 For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." {% 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. +**注意：** 如果您提出拉取请求以将 {% data variables.product.prodname_code_scanning %} 工作流程添加到仓库，则在合并拉取请求之前，来自该拉取请求的警报不会直接显示在 {% data variables.product.prodname_code_scanning_capc %} 页面上。 如果发现任何警报，您可以在合并拉取请求之前查看这些警报，方法是在 {% data variables.product.prodname_code_scanning_capc %} 页面上的横幅中点击**发现的 _n_ 条警报**链接。 - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) + ![点击"发现的 n 条警报"链接](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% endnote %} -### Understanding the pull request checks +### 了解拉取请求检查 -Each {% data variables.product.prodname_code_scanning %} workflow you enable to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis. +用于对拉取请求运行的每个 {% data variables.product.prodname_code_scanning %} 工作流始终有至少两个条目列在拉取请求的检查部分中。 工作流程中每个分析作业有一个条目，最后还有一个对应于分析结果的条目。 -The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code. +{% data variables.product.prodname_code_scanning %} 分析检查的名称采用形式："TOOL NAME / JOB NAME (TRIGGER)"。 例如，对于 {% data variables.product.prodname_codeql %}，C++ 代码的分析有条目 "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)"。 您可以单击 {% data variables.product.prodname_code_scanning %} 分析条目上的**Details（详细信息）**来查看日志记录数据。 这允许您在分析作业失败时调试问题。 例如，对于编译的语言的 {% data variables.product.prodname_code_scanning %} 分析，如果操作无法生成代码，则可能会发生这种情况。 ![After a scan completes, you can view alerts from a completed scan. For more information, see "Managing alerts from {% data variables.product.prodname_code_scanning %}."](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see a "Missing analysis" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +当 {% data variables.product.prodname_code_scanning %} 作业完成后， {% data variables.product.prodname_dotcom %} 检查拉取请求是否添加了任何警报，并将“{% data variables.product.prodname_code_scanning_capc %} 结果/工具名称”条目添加到检查列表中。 在执行至少一次 {% data variables.product.prodname_code_scanning %} 后，您可以单击 **Details（详细信息）**查看分析结果。 如果使用拉取请求将 {% data variables.product.prodname_code_scanning %} 添加到存储库，则当您单击“{% data variables.product.prodname_code_scanning_capc %} 结果/工具名称”检查中的 **Details（详细信息）**时，您最初会看到“Missing analysis（缺少分析）”的消息。 - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) + ![缺少提交消息的分析](/assets/images/help/repository/code-scanning-missing-analysis.png) -#### Reasons for the "missing analysis" message +#### “缺少分析”消息的原因 -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. +在 {% data variables.product.prodname_code_scanning %} 分析拉取请求中的代码后，它需要将主题分支（用于创建拉取请求的分支）的分析与基本分支（要合并拉取请求的分支）的分析进行比较。 这允许 {% data variables.product.prodname_code_scanning %} 计算哪些警报是拉取请求新近引入的，哪些是基础分支中已经存在的，以及是否有任何现有的警报通过拉取请求中的更改来修复。 最初，如果使用拉取请求将 {% data variables.product.prodname_code_scanning %} 添加到仓库，则尚未分析基础分支，因此无法计算这些详细信息。 在这种情况下，当您从拉取请求的结果检查中点进时，将看到“Missing analysis for base commit SHA-HASH（缺少基础提交 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: +在其他情况下，可能没有分析对拉取请求的基础分支的最新提交。 这些包括： -* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed. +* 已针对默认分支以外的分支提出拉取请求，并且尚未分析此分支。 - 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. + 要检查是否扫描了分支，请转到 {% data variables.product.prodname_code_scanning_capc %} 页面，单击 **Branch<（分支）**下拉菜单并选择相关分支。 - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) + ![从 Branch（分支）下拉菜单中选择一个分支](/assets/images/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 %} -* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available. +* 目前正在分析拉取请求的基础分支上的最新提交，分析尚未提供。 - Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. + 等待几分钟，然后将更改推送到拉取请求以重新触发 {% 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. +* 在分析基础分支上的最新提交时发生了错误，且该提交的分析不可用。 - 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 %}. + 将一个微小的更改合并到基础分支以触发此最新提交的 {% data variables.product.prodname_code_scanning %}，然后将更改推送到拉取请求以重新触发 {% data variables.product.prodname_code_scanning %}。 ### 后续步骤 -After enabling {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: +启用 {% data variables.product.prodname_code_scanning %} 并允许其操作完成后，您可以： -- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 -- View any alerts generated for a pull request submitted after you enabled {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." -- Set up notifications for completed runs. 更多信息请参阅“[配置通知](/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. 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)。” +- 查看为此仓库生成的所有 {% data variables.product.prodname_code_scanning %} 警报。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 +- 查看在启用 {% data variables.product.prodname_code_scanning %} 后提交的拉取请求生成的任何警报。 更多信息请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”。 +- 为已完成的运行设置通知。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)”。 +- 调查初始设置 {% 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/troubleshooting-the-codeql-workflow)”。 +- 自定义 {% data variables.product.prodname_code_scanning %} 如何扫描您的仓库中的代码。 更多信息请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)。” diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md index d16e99fca4..3181219cee 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md @@ -1,6 +1,6 @@ --- title: 查找代码中的安全漏洞和错误 -shortTitle: Finding vulnerabilities and coding errors +shortTitle: 查找漏洞和编码错误 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/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md index 9e4ac5a93d..f8afb17582 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md @@ -1,7 +1,7 @@ --- title: 与代码扫描集成 shortTitle: 集成 -intro: 'You can integrate third-party code analysis tools with {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_code_scanning %} by uploading data as SARIF files.' +intro: '您可以通过将数据上传为 SARIF 文件来集成第三方代码分析工具与 {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_code_scanning %}。' mapTopic: true product: '{% data reusables.gated-features.code-scanning %}' redirect_from: 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 d5464a4067..4a9e665f1f 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 @@ -32,7 +32,7 @@ By default, {% data variables.product.prodname_code_scanning %} analyzes your co ### Viewing the alerts for a repository -Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. 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)." +Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. 更多信息请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)”。 You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch. diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md index 4e88037c49..04564d1fff 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md @@ -21,7 +21,7 @@ You must run {% data variables.product.prodname_codeql %} in the same container You may have difficulty running {% data variables.product.prodname_code_scanning %} if the container you're using is missing certain dependencies (for example, Git must be installed and added to the PATH variable). If you encounter dependency issues, review the list of software typically included on {% data variables.product.prodname_dotcom %}'s virtual environments. For more information, see the version-specific `readme` files in these locations: * Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* MacOS: https://github.com/actions/virtual-environments/tree/main/images/macos +* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos * Windows: https://github.com/actions/virtual-environments/tree/main/images/win ### Example workflow diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md index 72a38a8e45..8877def3a2 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md @@ -16,7 +16,7 @@ versions: {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -### Using {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI system +### 将 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 与现有的 CI 系统一起使用 If you use a continuous integration or continuous delivery/deployment (CI/CD) system other than {% data variables.product.prodname_actions %}, you can use your existing system to run {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql %} analysis and upload the results to {% data variables.product.prodname_dotcom %}. To do this, use the {% data variables.product.prodname_codeql_runner %}. @@ -40,7 +40,7 @@ If you use a continuous integration or continuous delivery/deployment (CI/CD) sy chmod +x codeql-runner-linux ``` -在 MacOS 上： +在 macOS 中: ```shell chmod +x codeql-runner-macos @@ -72,7 +72,7 @@ $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 提供 {% data variables.product.prodname_codeql %} 包访问权限的选项： 1. 允许 CI 服务器访问 {% data variables.product.prodname_dotcom_the_website %}，以便 {% data variables.product.prodname_codeql_runner %} 可以自动下载包。 -1. Manually download/extract the bundle, store it with other central resources, and use the `--codeql-path` flag to specify the location of the bundle in calls to initialize the +1. 手动下载/提取包，将其与其他中心资源一起存储，然后使用 `--codeql-path` 标志指定包在调用中的位置以初始化 。 {% data variables.product.prodname_codeql_runner %}. {% if enterpriseServerVersions contains currentVersion %} 1. 您可以在 {% data variables.product.product_location %} 上镜像 `github/codeql-action` 仓库。 除非您指定 `--codeql-path` 标志，否则运行器将在此位置和 {% data variables.product.prodname_dotcom_the_website %}上自动检查包。{% endif %} @@ -122,7 +122,7 @@ $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 #### 编译语言示例 -此示例与前面的示例相似，但此例中的仓库含有用 C/C++、C# 或 Java 编写的代码。 To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. 在初始化过程结束时，运行器会报告您需要在构建代码之前设置环境的命令。 您需要在调用正常的 CI 构建进程之前运行此命令，然后运行 `analyze` 命令。 +此示例与前面的示例相似，但此例中的仓库含有用 C/C++、C# 或 Java 编写的代码。 要为这些语言创建 {% data variables.product.prodname_codeql %} 数据库，CLI 需要监控构建。 在初始化过程结束时，运行器会报告您需要在构建代码之前设置环境的命令。 您需要在调用正常的 CI 构建进程之前运行此命令，然后运行 `analyze` 命令。 1. 检出要分析的仓库。 1. 移至检出仓库的目录。 @@ -139,7 +139,7 @@ $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". ``` -1. Run the script generated by the `init` action to set up the environment to monitor the build. +1. 运行通过 `init` 操作生成的脚本，以设置监控构建的环境。 ```shell $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md index 4b45193c67..6492795d3d 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md @@ -1,7 +1,7 @@ --- title: 对代码扫描的 SARIF 支持 shortTitle: SARIF 支持 -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 %}. 如果使用默认 {% data variables.product.prodname_codeql %} 静态分析引擎，结果将自动显示于您在 {% data variables.product.prodname_dotcom %} 上的仓库中。' +intro: '要在 {% data variables.product.prodname_dotcom %} 上的仓库中显示第三方静态分析工具的结果，您需要将结果存储在 SARIF 文件中，以支持用于 {% data variables.product.prodname_code_scanning %} 的 SARIF 2.1.0 JSON 架构的特定子集。 如果使用默认 {% data variables.product.prodname_codeql %} 静态分析引擎，结果将自动显示于您在 {% 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 @@ -16,9 +16,9 @@ versions: SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 标准](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html)。 SARIF 标准用于简化静态分析工具分享其结果的方式。 {% data variables.product.prodname_code_scanning_capc %} 支持 SARIF 2.1.0 JSON 架构的子集。 -要从第三方静态代码分析引擎上传 SARIF 文件，需确保上传的文件使用 SARIF 2.1.0 版本。 {% 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. 更多信息请参阅“[将 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)”。 有关 SARIF 2.1.0 JSON 架构的更多信息，请参阅 [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json)。 +要从第三方静态代码分析引擎上传 SARIF 文件，需确保上传的文件使用 SARIF 2.1.0 版本。 {% data variables.product.prodname_dotcom %} 将剖析 SARIF 文件，并在 {% data variables.product.prodname_code_scanning %} 过程中使用仓库中的结果显示警报。 更多信息请参阅“[将 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)”。 有关 SARIF 2.1.0 JSON 架构的更多信息，请参阅 [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json)。 -如果您结合使用 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_codeql_workflow %}，或者使用 {% data variables.product.prodname_codeql_runner %}，则 {% data variables.product.prodname_code_scanning %} 结果将自动使用受支持的 SARIF 2.1.0 子集。 For more information, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)" or "[Running {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." +如果您结合使用 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_codeql_workflow %}，或者使用 {% data variables.product.prodname_codeql_runner %}，则 {% data variables.product.prodname_code_scanning %} 结果将自动使用受支持的 SARIF 2.1.0 子集。 更多信息请参阅“[启用 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)”或“[在 CI 系统中运行 {% data variables.product.prodname_codeql %}{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”。 {% data variables.product.prodname_dotcom %} 使用 SARIF 文件中的属性来显示警报。 例如，`shortDescription` 和 `fullDescription` 出现在 {% data variables.product.prodname_code_scanning %} 警报的顶部。 `location` 允许 {% data variables.product.prodname_dotcom %} 在代码文件中显示注释。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)”。 @@ -26,19 +26,19 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS ### 使用指纹防止重复警报 -每次上传新的代码扫描结果时，都会处理结果并将警报添加到仓库中。 为防止出现针对同一问题的重复警报，{% data variables.product.prodname_code_scanning %} 使用指纹匹配各个运行的结果，使它们只会出现在所选分支的最新运行中出现一次。 This makes it possible to match alerts to the right line of code when files are edited. +每次上传新的代码扫描结果时，都会处理结果并将警报添加到仓库中。 为防止出现针对同一问题的重复警报，{% data variables.product.prodname_code_scanning %} 使用指纹匹配各个运行的结果，使它们只会出现在所选分支的最新运行中出现一次。 这样可以在编辑文件时将警报与正确的代码行匹配。 {% data variables.product.prodname_dotcom %} 使用 OASIS 标准中的 `partialFingerprints` 属性来检测两个结果在逻辑上是否相同。 更多信息请参阅 OASIS 文档中的 "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" 条目。 -通过 {% data variables.product.prodname_codeql_workflow %} 或 {% data variables.product.prodname_codeql_runner %} 创建的 SARIF 文件包含指纹数据。 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)." +通过 {% data variables.product.prodname_codeql_workflow %} 或 {% data variables.product.prodname_codeql_runner %} 创建的 SARIF 文件包含指纹数据。 如果使用 `upload-sarif` 操作上传 SARIF 文件且此数据缺少，则 {% data variables.product.prodname_dotcom %} 会尝试从源文件填充 `partialFingerprints` 字段。 有关上传结果的更多信息，请参阅“[将 SARIF 文件上传到 {% 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)." +如果您使用 `/code-scaning/sarifs` API 端点上传无指纹数据的 SARIF 文件，{% data variables.product.prodname_code_scanning %} 警报将被处理并显示，但用户可能会看到重复的警报。 为了避免看到重复的警报，您应该在上传 SARIF 文件之前计算指纹数据并填充 `partialFingerprints` 属性。 您可能发现 `upload-sarif` 操作的脚本使用一个有用的起点：https://github.com/github/codeql-action/blob/main/src/fingprints。 有关 API 的更多信息，请参阅“[上传 SARIF 文件](/rest/reference/code-scanning#upload-a-sarif-file)”。 -### Validating your SARIF file +### 验证 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/). +您可以根据 {% data variables.product.prodname_dotcom %} 引入规则测试 SARIF 文件是否兼容 {% data variables.product.prodname_code_scanning %}。 有关更多信息，请访问 [Microsoft SARIF 验证程序](https://sarifweb.azurewebsites.net/)。 ### 支持的 SARIF 输出文件属性 @@ -107,13 +107,13 @@ You can check a SARIF file is compatible with {% data variables.product.prodname #### `physicalLocation` 对象 -| 名称 | 描述 | -| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `artifactLocation.uri` | **必选。**表示构件位置的 URI，通常是仓库中或在构建期间生成的文件。 如果 URI 是相对的，它应相对于正在分析的 {% data variables.product.prodname_dotcom %} 仓库的根目录。 例如，main.js 或 src/script.js 相对于仓库的根目录。 如果 URI 是绝对的，则 {% data variables.product.prodname_code_scanning %} 可使用 URI 检出构件并匹配仓库中的文件。 例如，`https://github.com/github/example/blob/00/src/promiseUtils.js`。 | -| `region.startLine` | **必选。**区域中第一个字符的行号。 | -| `region.startColumn` | **必选。**区域中第一个字符的列编号。 | -| `region.endLine` | **必选。**区域中最后一个字符的行号。 | -| `region.endColumn` | **必选。**区域结束后字符的列编号。 | +| 名称 | 描述 | +| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `artifactLocation.uri` | **必选。**表示构件位置的 URI，通常是仓库中或在构建期间生成的文件。 如果 URI 是相对的，它应相对于正在分析的 {% data variables.product.prodname_dotcom %} 仓库的根目录。 例如，main.js 或 src/script.js 相对于仓库的根目录。 如果 URI 是绝对的，则 {% data variables.product.prodname_code_scanning %} 可使用 URI 检出构件并匹配仓库中的文件。 例如，`https://github.com/ghost/example/blob/00/src/promiseUtils.js`。 | +| `region.startLine` | **必选。**区域中第一个字符的行号。 | +| `region.startColumn` | **必选。**区域中第一个字符的列编号。 | +| `region.endLine` | **必选。**区域中最后一个字符的行号。 | +| `region.endColumn` | **必选。**区域结束后字符的列编号。 | ### SARIF 输出文件示例 diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md index 3a0587753c..5f9f57a2ff 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md @@ -20,16 +20,16 @@ versions: 您可以使用许多静态分析安全测试工具来生成 SARIF 文件，包括 {% data variables.product.prodname_codeql %}。 结果必须使用 SARIF 版本 2.1.0。 更多信息请参阅“[关于代码扫描的 SARIF 支持](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning)”。 -You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. 最佳上传方法将取决于您如何生成 SARIF 文件，例如，如果您使用： +您可以使用 {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} （如果您的组织正在参与测试计划，则可以使用）{% endif %}、{% data variables.product.prodname_code_scanning %} API 或 {% data variables.product.prodname_codeql_runner %} 上传结果。 最佳上传方法将取决于您如何生成 SARIF 文件，例如，如果您使用： - {% data variables.product.prodname_actions %} 来运行 {% data variables.product.prodname_codeql %} 操作，则无需进一步操作。 {% data variables.product.prodname_codeql %} 操作在完成分析后自动上传 SARIF 文件。 - "[管理工作流程运行](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)" -- {% data variables.product.prodname_dotcom %} 将在仓库中显示来自上传的 SARIF 文件的 {% data variables.product.prodname_code_scanning %} 警报。 If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)"). +- {% data variables.product.prodname_dotcom %} 将在仓库中显示来自上传的 SARIF 文件的 {% data variables.product.prodname_code_scanning %} 警报。 如果您阻止自动上传，在准备上传结果时可以使用 `upload` 命令（更多信息请参阅“[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)”）。 - 作为仓库外部构件生成结果的工具，您可以使用 {% data variables.product.prodname_code_scanning %} API 上传文件（更多信息请参阅“[上传 SARIF 文件](/rest/reference/code-scanning#upload-a-sarif-file)”）。 ### 通过 {% data variables.product.prodname_actions %} 上传 {% data variables.product.prodname_code_scanning %} 分析 -要将第三方 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}，需要 {% data variables.product.prodname_actions %} 工作流程。 For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +要将第三方 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}，需要 {% data variables.product.prodname_actions %} 工作流程。 更多信息请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)”和“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 您的工作流需要使用 `upload-sarif` 操作，该操作包含可用于配置上传的输入参数。 它包含可用于配置上传的输入参数。 您将要使用的主要输入参数是 `sarif-file`，它会配置要上传的文件或 SARIF 文件的目录。 目录或文件路径相对于仓库的根目录。 更多信息请参阅 [`upload-sarif` 操作](https://github.com/github/codeql-action/tree/HEAD/upload-sarif)。 @@ -43,7 +43,7 @@ You can upload the results using {% data variables.product.prodname_actions %}{% 只要提交被推送到仓库，此示例工作流程就会运行。 该操作使用 `partialFingerprints` 属性来确定是否发生了更改。 除了推送提交时运行之外，工作流程还预定每周运行一次。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。 -此工作流上传位于仓库根目录中的 `results.sarif` 文件。 For more information about creating a workflow file, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +此工作流上传位于仓库根目录中的 `results.sarif` 文件。 有关创建工作流程文件的更多信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 或者，您也可以修改此工作流程以上传 SARIF 文件的目录。 例如，您可以将所有 SARIF 文件放在仓库根目录中的 `sarif-output` 目录中，并将操作的输入参数 `sarif_file` 设置为 `sarif-output`。 @@ -77,7 +77,7 @@ jobs: 只要提交被推送到仓库，此示例工作流程就会运行。 该操作使用 `partialFingerprints` 属性来确定是否发生了更改。 除了推送提交时运行之外，工作流程还预定每周运行一次。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。 -工作流程显示了将 ESLint 静态分析工具作为工作流程中一个步骤运行的示例。 `Run ESLint` 步骤运行 ESLint 工具，输出 `results.sarif` 文件。 然后，工作流程使用 `upload-sarif` 操作将 `results.sarif` 文件上传到 {% data variables.product.prodname_dotcom %}。 For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)." +工作流程显示了将 ESLint 静态分析工具作为工作流程中一个步骤运行的示例。 `Run ESLint` 步骤运行 ESLint 工具，输出 `results.sarif` 文件。 然后，工作流程使用 `upload-sarif` 操作将 `results.sarif` 文件上传到 {% data variables.product.prodname_dotcom %}。 有关创建工作流程文件的更多信息，请参阅“[GitHub Actions 简介](/actions/learn-github-actions/introduction-to-github-actions)”。 ```yml name: "ESLint analysis" @@ -110,5 +110,5 @@ jobs: - "[{% data variables.product.prodname_actions %} 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions)" - "[查看工作流程历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)" -- "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)" +- "[在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)" - "[上传 SARIF 文件](/rest/reference/code-scanning#upload-a-sarif-file)" diff --git a/translations/zh-CN/content/github/getting-started-with-github/access-permissions-on-github.md b/translations/zh-CN/content/github/getting-started-with-github/access-permissions-on-github.md index de6a3b6aff..a50076f7b8 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/access-permissions-on-github.md +++ b/translations/zh-CN/content/github/getting-started-with-github/access-permissions-on-github.md @@ -18,7 +18,7 @@ versions: ### 组织帐户 -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{% if currentVersion == "free-pro-team@latest" %}, while billing managers can manage billing settings{% endif %}. 成员是其他每个人的默认角色。 您可以通过团队一次管理多个成员的访问权限。 更多信息请参阅： +组织成员可以是*所有者*{% if currentVersion == "free-pro-team@latest" %}、*帐单管理员*{% endif %} 或*成员*角色。 所有者对组织具有完全管理权限{% if currentVersion == "free-pro-team@latest" %}，而帐单管理员负责管理帐单设置{% endif %}。 成员是其他每个人的默认角色。 您可以通过团队一次管理多个成员的访问权限。 更多信息请参阅： - "[组织的权限级别](/articles/permission-levels-for-an-organization)" - "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)" - "[组织的仓库权限级别](/articles/repository-permission-levels-for-an-organization)" @@ -28,7 +28,7 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late ### 企业帐户 -*企业所有者*对企业帐户拥有最终权力，可在企业帐户中执行任何操作。 *帐单管理员*可以管理企业帐户的帐单设置。 企业帐户拥有的组织的成员和外部协作者自动成为企业帐户的成员，但他们对企业帐户本身或其设置没有访问权限。 For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +*企业所有者*对企业帐户拥有最终权力，可在企业帐户中执行任何操作。 *帐单管理员*可以管理企业帐户的帐单设置。 企业帐户拥有的组织的成员和外部协作者自动成为企业帐户的成员，但他们对企业帐户本身或其设置没有访问权限。 更多信息请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)”。 {% data reusables.gated-features.enterprise-accounts %} diff --git a/translations/zh-CN/content/github/getting-started-with-github/be-social.md b/translations/zh-CN/content/github/getting-started-with-github/be-social.md index 154d2f0233..62f8644016 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/be-social.md +++ b/translations/zh-CN/content/github/getting-started-with-github/be-social.md @@ -22,7 +22,7 @@ versions: ### 关注仓库 -您可以关注仓库以接收有关新拉取请求和议题的通知。 当所有者更新仓库时，您将在个人仪表板中看到其更改。 For more information see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}." +您可以关注仓库以接收有关新拉取请求和议题的通知。 当所有者更新仓库时，您将在个人仪表板中看到其更改。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}”[关注和取消关注仓库](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}”。 在仓库顶部单击 **Watch（关注）**可关注它。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/create-a-repo.md b/translations/zh-CN/content/github/getting-started-with-github/create-a-repo.md index e3e39f8746..b654ccdde5 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/create-a-repo.md +++ b/translations/zh-CN/content/github/getting-started-with-github/create-a-repo.md @@ -16,7 +16,7 @@ versions: {% elsif enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} -You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." +您可以在 {% data variables.product.product_name %} 仓库中存储各种项目，包括内部来源项目。 通过内部源代码，您可以分享代码来获取更好、更可靠的软件。 有关内部资源的更多信息，请参阅 {% data variables.product.company_short %} 的白皮书“[内部资源简介](https://resources.github.com/whitepapers/introduction-to-innersource/)”。 {% endif %} @@ -32,7 +32,7 @@ You can store a variety of projects in {% data variables.product.product_name %} {% data reusables.repositories.create_new %} 2. 为仓库键入简短、令人难忘的名称。 例如 "hello-world"。 ![用于输入仓库名称的字段](/assets/images/help/repository/create-repository-name.png) -3. （可选）添加仓库的说明。 For example, "My first repository on +3. （可选）添加仓库的说明。 例如“我在 {% data variables.product.product_name %}。" ![用于输入仓库说明的字段](/assets/images/help/repository/create-repository-desc.png) {% data reusables.repositories.choose-repo-visibility %} diff --git a/translations/zh-CN/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/zh-CN/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md index 8ef707e2fb..c5b0fa807f 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/zh-CN/content/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -32,14 +32,14 @@ versions: 以下是 {% data variables.product.prodname_dotcom_the_website %} 上镜像的几个主要仓库： -- [Android Open Source Project](https://github.com/aosp-mirror) +- [Android 开源项目](https://github.com/aosp-mirror) - [The Apache Software Foundation](https://github.com/apache) - [The Chromium Project](https://github.com/chromium) - [Eclipse Foundation](https://github.com/eclipse) - [The FreeBSD Project](https://github.com/freebsd) - [Glasgow Haskell Compiler](https://github.com/ghc) - [GNOME](https://github.com/GNOME) -- [Linux kernel source tree](https://github.com/torvalds/linux) +- [Linux 内核源树](https://github.com/torvalds/linux) - [Qt](https://github.com/qt) 为创建您自己的镜像，可在您的正式项目仓库中配置[接收后挂钩](https://git-scm.com/book/en/Customizing-Git-Git-Hooks)，以自动将提交推送到 {% data variables.product.product_name %} 上的镜像仓库。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/following-people.md b/translations/zh-CN/content/github/getting-started-with-github/following-people.md index 793a632c4c..42a3295eba 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/following-people.md +++ b/translations/zh-CN/content/github/getting-started-with-github/following-people.md @@ -1,6 +1,6 @@ --- title: 关注他人 -intro: 'You can follow people on {% data variables.product.product_name %} to receive notifications about their activity{% if currentVersion == "free-pro-team@latest" %} and discover projects in their communities{% endif %}.' +intro: '您可以在 {% data variables.product.product_name %} 上关注他人，以接收有关其活动的通知{% if currentVersion == "free-pro-team@latest" %}和发现其社区中的项目{% endif %}。' redirect_from: - /articles/following-people versions: @@ -9,7 +9,7 @@ versions: github-ae: '*' --- -When you follow people, you'll see their public activity in the activity view of your news feed.{% if currentVersion == "free-pro-team@latest" %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you in the discovery view of your news feed.{% endif %} To follow someone, visit their profile page and click **Follow** under their profile image. +关注他人后，您将在消息馈送的活动视图中看到其公开活动。{% if currentVersion == "free-pro-team@latest" %}如果您关注的人标注了某个公共仓库，{% data variables.product.product_name %} 可能会在您的消息馈送发现视图中向您推荐该仓库。{% endif %}要关注某人，请访问其个人资料页面，然后在其个人资料图像下面单击 **Follow（关注）**。 ![关注用户按钮](/assets/images/help/profile/follow-user-button.png) diff --git a/translations/zh-CN/content/github/getting-started-with-github/fork-a-repo.md b/translations/zh-CN/content/github/getting-started-with-github/fork-a-repo.md index 9f0346537a..dd515b4238 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/fork-a-repo.md +++ b/translations/zh-CN/content/github/getting-started-with-github/fork-a-repo.md @@ -25,7 +25,7 @@ versions: 开源软件的理念是通过共享代码，可以开发出更好、更可靠的软件。 更多信息请参阅 Open Source Initiative（开源倡议）上的“[关于开源倡议](http://opensource.org/about)”。 -For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." +有关将开源原则应用于组织在 {% data variables.product.product_location %} 上的开发工作的详细信息，请参阅 {% data variables.product.prodname_dotcom %} 的白皮书“[内部来源](https://resources.github.com/whitepapers/introduction-to-innersource/)”。 {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} @@ -70,7 +70,7 @@ For more information about applying open source principles to your organization' 1. 在 -{% data variables.product.product_name %}, navigate to **your fork** of the Spoon-Knife repository. +{% data variables.product.product_name %} 上，导航到 Spoon-Knife 仓库的**复刻**。 {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} @@ -97,7 +97,7 @@ For more information about applying open source principles to your organization' 1. 在 -{% data variables.product.product_name %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. +{% data variables.product.product_name %} 上，导航到 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 仓库。 {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} 4. 将目录更改为您在[第 2 步：创建复刻的本地克隆](#step-2-create-a-local-clone-of-your-fork)中克隆复刻的位置。 @@ -139,7 +139,7 @@ For more information about applying open source principles to your organization' 复刻仓库，开始参与项目。 {% data reusables.repositories.you-can-fork %} -{% if currentVersion == "free-pro-team@latest" %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。 +{% if currentVersion == "free-pro-team@latest" %}您可以浏览 [Explore](https://github.com/explore) 以查找项目并开始参与开源仓库。 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。 {% endif %} diff --git a/translations/zh-CN/content/github/getting-started-with-github/git-and-github-learning-resources.md b/translations/zh-CN/content/github/getting-started-with-github/git-and-github-learning-resources.md index 40bdb175d7..b7284d81a8 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/git-and-github-learning-resources.md +++ b/translations/zh-CN/content/github/getting-started-with-github/git-and-github-learning-resources.md @@ -9,6 +9,8 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +authors: + - GitHub --- ### 使用 Git @@ -55,6 +57,6 @@ versions: [Code School](http://codeschool.com) 的互动式[在线 Git 课程](http://www.codeschool.com/courses/git-real)有七个等级，以有趣的游戏形式提供数十个练习。 您可以自由调整 [.gitignore 模板](https://github.com/github/gitignore)以满足您的需求。 -Extend your {% data variables.product.prodname_dotcom %} reach through {% if currentVersion == "free-pro-team@latest" %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [Atom](https://atom.io) text editor. +通过{% if currentVersion == "free-pro-team@latest" %}[集成](/articles/about-integrations){% else %}集成{% endif %}或通过安装 [{% data variables.product.prodname_desktop %}](https://desktop.github.com) 和强大的 [Atom](https://atom.io) 文本编辑器来扩展您的 {% data variables.product.prodname_dotcom %} 的作用范围。 通过[开源指南](https://opensource.guide/)了解如何启动和发展您的开源项目。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md b/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md index 6434ec2217..b3407415d2 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md +++ b/translations/zh-CN/content/github/getting-started-with-github/github-for-mobile.md @@ -23,15 +23,15 @@ versions: 要安装 Android 或 iOS 版 {% data variables.product.prodname_mobile %}，请参阅 [{% data variables.product.prodname_mobile %}](https://github.com/mobile)。 -### Supported languages for {% data variables.product.prodname_mobile %} +### {% data variables.product.prodname_mobile %} 支持的语言 -{% data variables.product.prodname_mobile %} is available in the following languages. +{% data variables.product.prodname_mobile %} 支持以下语言。 - 日语 -- Brazilian Portuguese +- 巴西葡萄牙语 - 西班牙语 -If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. +如果将设备上的语言配置为受支持的语言，则 {% data variables.product.prodname_mobile %} 默认为该语言。 您可以在 {% data variables.product.prodname_mobile %} 的 **Settings（设置）**菜单中更改 {% data variables.product.prodname_mobile %} 的语言。 ### 管理 iOS 上 {% data variables.product.prodname_mobile %} 的通用链接 @@ -43,9 +43,9 @@ If you configure the language on your device to a supported language, {% data va ### 分享反馈 -If you find a bug in {% data variables.product.prodname_mobile %}, you can email us at mobilefeedback@github.com. +如果您发现 {% data variables.product.prodname_mobile %} 中的漏洞，可以发送电子邮件到 mobilefeedback@github.com 联系我们。 -You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} [on GitHub Discussions](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). +您可以在 [GitHub Discussions](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22) 上提交对 {% data variables.product.prodname_mobile %} 的功能要求或其他反馈。 ### 选择退出 iOS 的测试版 diff --git a/translations/zh-CN/content/github/getting-started-with-github/github-glossary.md b/translations/zh-CN/content/github/getting-started-with-github/github-glossary.md index 03a46d6dfd..8b0bb6c571 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/github-glossary.md +++ b/translations/zh-CN/content/github/getting-started-with-github/github-glossary.md @@ -10,8 +10,8 @@ versions: --- {% for term in site.data.glossaries.external %} - ### {{term.term}} - {{term.description}} + ### {% data glossaries.external[forloop.index0].term %} + {% data glossaries.external[forloop.index0].description %} --- {% endfor %} 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 b6681e18a3..495cf930ce 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 @@ -97,7 +97,7 @@ versions: - {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} - {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" and "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning) (beta)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) (beta)."{% endif %} +- {% data variables.product.prodname_advanced_security %}{% if currentVersion == "free-pro-team@latest" %}. 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)”和“[关于 {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)（测试版）”。{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %}。 更多信息请参阅“[关于 {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)（测试版）“。{% endif %} - [组织的 {% data variables.product.prodname_learning %}](https://lab.github.com/organizations) 有关注册 {% data variables.product.prodname_ghe_one %} 的更多信息，请联系 [{% data variables.product.product_name %} 的销售团队](https://enterprise.github.com/contact)。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/index.md b/translations/zh-CN/content/github/getting-started-with-github/index.md index 68eabcd3ab..45a93b67f4 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/index.md +++ b/translations/zh-CN/content/github/getting-started-with-github/index.md @@ -27,37 +27,27 @@ versions: {% link_in_list /fork-a-repo %} {% link_in_list /be-social %} {% topic_link_in_list /learning-about-github %} - {% link_in_list /githubs-products %} {% link_in_list /exploring-early-access-releases-with-feature-preview %} - {% link_in_list /types-of-github-accounts %} - {% link_in_list /faq-about-changes-to-githubs-plans %} {% link_in_list /github-cli %} {% link_in_list /github-desktop %} {% link_in_list /github-for-mobile %} - {% link_in_list /access-permissions-on-github %} {% link_in_list /github-glossary %} {% link_in_list /git-cheatsheet %} {% link_in_list /git-and-github-learning-resources %} {% topic_link_in_list /signing-up-for-github %} - % link_in_list /signing-up-for-a-new-github-account %} {% link_in_list /verifying-your-email-address %} - {% link_in_list /setting-up-a-trial-of-github-enterprise-cloud %} {% link_in_list /setting-up-a-trial-of-github-enterprise-server %} {% topic_link_in_list /exploring-projects-on-github %} - {% link_in_list /finding-ways-to-contribute-to-open-source-on-github %} - {% link_in_list /saving-repositories-with-stars %} {% link_in_list /following-people %} {% topic_link_in_list /using-github %} {% link_in_list /supported-browsers %} - {% link_in_list /troubleshooting-connectivity-problems %} - {% link_in_list /keyboard-shortcuts %} diff --git a/translations/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 aabb773f35..dd3cf27deb 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 @@ -21,22 +21,22 @@ versions: ### 站点快捷键 -| 键盘快捷键 | 描述 | -| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s 或 / | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/articles/about-searching-on-github)”。 | -| g n | 转到您的通知。 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 | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素 | +| 键盘快捷键 | 描述 | +| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| s 或 / | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/articles/about-searching-on-github)”。 | +| g n | 转到您的通知。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。 | +| esc | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素 | ### 仓库 -| 键盘快捷键 | 描述 | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | 转到 **Code（代码）**选项卡 | -| g i | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。 | -| g p | 转到 **Pull requests（拉取请求）**选项卡。 For more information, see "[About pull requests](/articles/about-pull-requests)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -| g a | 转到 **Actions（操作）**选项卡。 For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %} -| g b | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 | -| g w | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wikis](/articles/about-wikis)”。 | +| 键盘快捷键 | 描述 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| g c | 转到 **Code（代码）**选项卡 | +| g i | 转到 **Issues（议题）**选项卡。 更多信息请参阅“[关于议题](/articles/about-issues)”。 | +| g p | 转到 **Pull requests（拉取请求）**选项卡。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests)”。{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +| g a | 转到 **Actions（操作）**选项卡。 更多信息请参阅“[关于 Actions](/actions/getting-started-with-github-actions/about-github-actions)”。{% endif %} +| g b | 转到 **Projects（项目）**选项卡。 更多信息请参阅“[关于项目板](/articles/about-project-boards)”。 | +| g w | 转到 **Wiki** 选项卡。 更多信息请参阅“[关于 wikis](/articles/about-wikis)”。 | ### 源代码编辑 @@ -68,16 +68,16 @@ versions: ### 评论 -| 键盘快捷键 | 描述 | -| ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| control b 或 command b | 插入 Markdown 格式用于粗体文本 | -| control i 或 command i | 插入 Markdown 格式用于斜体文本 | -| control k 或 command k | 插入 Markdown 格式用于创建链接 | -| control shift p 或 command shift p | 在 **Write（撰写）**和 **Preview（预览）**评论选项卡之间切换 | -| control enter | 提交评论 | -| control .，然后 control [已保存回复编号] | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} +| 键盘快捷键 | 描述 | +| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | +| control b 或 command b | 插入 Markdown 格式用于粗体文本 | +| control i 或 command i | 插入 Markdown 格式用于斜体文本 | +| control k 或 command k | 插入 Markdown 格式用于创建链接 | +| control shift p 或 command shift p | 在 **Write（撰写）**和 **Preview（预览）**评论选项卡之间切换 | +| control enter | 提交评论 | +| control .，然后 control [已保存回复编号] | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% if currentVersion == "free-pro-team@latest" %} | control g 或 command g | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/articles/reviewing-proposed-changes-in-a-pull-request)”。 |{% endif %} -| r | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。 | +| r | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。 | ### 议题和拉取请求列表 @@ -103,49 +103,49 @@ versions: ### 拉取请求中的更改 -| 键盘快捷键 | 描述 | -| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | 在拉取请求中打开提交列表 | -| t | 在拉取请求中打开已更改文件列表 | -| j | 将所选内容在列表中向下移动 | -| k | 将所选内容在列表中向上移动 | -| cmd + shift + enter | 添加一条有关拉取请求差异的评论 | -| alt 并单击 | 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" %} +| 键盘快捷键 | 描述 | +| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| c | 在拉取请求中打开提交列表 | +| t | 在拉取请求中打开已更改文件列表 | +| j | 将所选内容在列表中向下移动 | +| k | 将所选内容在列表中向上移动 | +| cmd + shift + enter | 添加一条有关拉取请求差异的评论 | +| alt 并单击 | 通过按下 `alt` 并单击 **Show outdated（显示已过期）**或 **Hide outdated（隐藏已过期）**，在折叠和展开拉取请求中所有过期的审查评论之间切换。|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} | 单击，然后按住 shift 并单击 | 单击一个行号，按住 shift，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)。”|{% endif %} ### 项目板 #### 移动列 -| 键盘快捷键 | 描述 | -| ------------------------------------------------------------------------------------- | ----------- | -| enter 或 space | 开始移动聚焦的列 | -| escape | 取消正在进行的移动 | -| enter | 完成正在进行的移动 | -| ← 或 h | 向左移动列 | -| command ←、command h、control ← 或 control h | 将列移动到最左侧的位置 | -| → 或 l | 向右移动列 | -| command →、command l、control → 或 control l | 将列移动到最右侧的位置 | +| 键盘快捷键 | 描述 | +| ------------------------------------------------------------------------------------------------- | ----------- | +| enter 或 space | 开始移动聚焦的列 | +| escape | 取消正在进行的移动 | +| enter | 完成正在进行的移动 | +| ← 或 h | 向左移动列 | +| command + ← 或 command + h 或 control + ← 或 control + h | 将列移动到最左侧的位置 | +| → 或 l | 向右移动列 | +| command + → 或 command + l 或 control + → 或 control + l | 将列移动到最右侧的位置 | #### 移动卡片 -| 键盘快捷键 | 描述 | -| ------------------------------------------------------------------------------------------------------------- | ------------- | -| enter 或 space | 开始移动聚焦的卡片 | -| escape | 取消正在进行的移动 | -| enter | 完成正在进行的移动 | -| ↓ 或 j | 向下移动卡片 | -| command ↓、command j、control ↓ 或 control j | 将卡片移动到该列的底部 | -| ↑ 或 k | 向上移动卡片 | -| command ↑、command k、control ↑ 或 control k | 将卡片移动到该列的顶部 | -| ← 或 h | 将卡片移动到左侧列的底部 | -| shift ← 或 shift h | 将卡片移动到左侧列的顶部 | -| command ←、command h、control ← 或 control h | 将卡片移动到最左侧列的底部 | -| command shift ←、command shift h、control shift ← 或 control shift h | 将卡片移动到最左侧列的顶部 | -| → | 将卡片移动到右侧列的底部 | -| shift → 或 shift l | 将卡片移动到右侧列的顶部 | -| command →、command l、control → 或 control l | 将卡片移动到最右侧列的底部 | -| command shift →、command shift l、control shift → 或 control shift l | 将卡片移动到最右侧列的底部 | +| 键盘快捷键 | 描述 | +| --------------------------------------------------------------------------------------------------------------------------------- | ------------- | +| enter 或 space | 开始移动聚焦的卡片 | +| escape | 取消正在进行的移动 | +| enter | 完成正在进行的移动 | +| ↓ 或 j | 向下移动卡片 | +| command + ↓ 或 command + j 或 control + ↓ 或 control + j | 将卡片移动到该列的底部 | +| ↑ 或 k | 向上移动卡片 | +| command + ↑ 或 command + k 或 control + ↑ 或 control + k | 将卡片移动到该列的顶部 | +| ← 或 h | 将卡片移动到左侧列的底部 | +| shift + ← 或 shift + h | 将卡片移动到左侧列的顶部 | +| command + ← 或 command + h 或 control + ← 或 control + h | 将卡片移动到最左侧列的底部 | +| command + shift + ← 或 command + shift + h 或 control + shift + ← 或 control + shift + h | 将卡片移动到最左侧列的顶部 | +| → | 将卡片移动到右侧列的底部 | +| shift + → 或 shift + l | 将卡片移动到右侧列的顶部 | +| command + → 或 command + l 或 control + → 或 control + l | 将卡片移动到最右侧列的底部 | +| command + shift + → 或 command + shift + l 或 control + shift + → 或 control + shift + l | 将卡片移动到最右侧列的底部 | #### 预览卡片 @@ -156,38 +156,38 @@ versions: {% if currentVersion == "free-pro-team@latest" %} ### {% data variables.product.prodname_actions %} -| 键盘快捷键 | 描述 | -| ---------------------------------------------------- | ----------------------- | -| command space 或 control space | 在工作流程编辑器中，获取对工作流程文件的建议。 | +| 键盘快捷键 | 描述 | +| -------------------------------------------------------- | ----------------------- | +| command + space 或 control + space | 在工作流程编辑器中，获取对工作流程文件的建议。 | {% endif %} ### 通知 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} -| 键盘快捷键 | 描述 | -| ------------------ | ----- | -| e | 标记为完成 | -| shift u | 标记为未读 | -| shift i | 标记为已读 | -| shift m | 取消订阅 | +| 键盘快捷键 | 描述 | +| -------------------- | ----- | +| e | 标记为完成 | +| shift + u | 标记为未读 | +| shift + i | 标记为已读 | +| shift + m | 取消订阅 | {% else %} | 键盘快捷键 | 描述 | | ---------------------------------------- | ----- | | e、I 或 y | 标记为已读 | -| shift m | 静音线程 | +| shift + m | 静音线程 | {% endif %} ### 网络图 -| 键盘快捷键 | 描述 | -| --------------------------------------- | ------ | -| ← 或 h | 向左滚动 | -| → 或 l | 向右滚动 | -| ↑ 或 k | 向上滚动 | -| ↓ 或 j | 向下滚动 | -| shift ← 或 shift h | 一直向左滚动 | -| shift → 或 shift l | 一直向右滚动 | -| shift ↑ 或 shift k | 一直向上滚动 | -| shift ↓ 或 shift j | 一直向下滚动 | +| 键盘快捷键 | 描述 | +| ------------------------------------------- | ------ | +| ← 或 h | 向左滚动 | +| → 或 l | 向右滚动 | +| ↑ 或 k | 向上滚动 | +| ↓ 或 j | 向下滚动 | +| shift + ← 或 shift + h | 一直向左滚动 | +| shift + → 或 shift + l | 一直向右滚动 | +| shift + ↑ 或 shift + k | 一直向上滚动 | +| shift + ↓ 或 shift + j | 一直向下滚动 | diff --git a/translations/zh-CN/content/github/getting-started-with-github/saving-repositories-with-stars.md b/translations/zh-CN/content/github/getting-started-with-github/saving-repositories-with-stars.md index ac80b8b9a6..154dc151ce 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/saving-repositories-with-stars.md +++ b/translations/zh-CN/content/github/getting-started-with-github/saving-repositories-with-stars.md @@ -1,6 +1,6 @@ --- title: 使用星标保存仓库 -intro: 'You can star repositories and topics to keep track of projects you find interesting{% if currentVersion == "free-pro-team@latest" %} and discover related content in your news feed{% endif %}.' +intro: '您可以对仓库和主题标星以跟踪您感兴趣的项目{% if currentVersion == "free-pro-team@latest" %} and discover related content in your news feed{% endif %}。' redirect_from: - /articles/stars/ - /articles/about-stars/ @@ -20,7 +20,7 @@ versions: 标星操作便于以后再次找到仓库或主题。 您可以到 {% data variables.explore.your_stars_page %} 查看已经加星标的所有仓库和主题。 {% if currentVersion == "free-pro-team@latest" %} -You can star repositories and topics to discover similar projects on +您可以对仓库和主题标星以发现类似项目 {% data variables.product.product_name %} 上的企业设置来设置公告横幅。 对仓库或主题加星标时，{% data variables.product.product_name %} 可能会在消息馈送的发现视图中推荐相关内容。 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。 {% endif %} diff --git a/translations/zh-CN/content/github/getting-started-with-github/set-up-git.md b/translations/zh-CN/content/github/getting-started-with-github/set-up-git.md index 077d89f609..d94c4ababe 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/set-up-git.md +++ b/translations/zh-CN/content/github/getting-started-with-github/set-up-git.md @@ -17,7 +17,7 @@ versions: github-ae: '*' --- -要在命令行中使用 Git，您将需要在计算机上下载、安装和配置 Git。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. 有关 {% data variables.product.prodname_cli %} 的更多信息，请参阅 [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) 文档。{% endif %} +要在命令行中使用 Git，您将需要在计算机上下载、安装和配置 Git。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} 您也可以从命令行安装 {% data variables.product.prodname_cli %} 以使用 {% data variables.product.product_name %}。 有关 {% data variables.product.prodname_cli %} 的更多信息，请参阅 [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) 文档。{% endif %} 如果要在本地使用 Git，但不想使用命令行，您可以下载并安装 [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}) 客户端。 更多信息请参阅“[安装和配置 {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)”。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/zh-CN/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md index 7dd422d93e..50ee91ceac 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/zh-CN/content/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server.md @@ -13,7 +13,7 @@ versions: 您可以申请 45 天试用版来试用 {% data variables.product.prodname_ghe_server %}。 您的试用版将作为虚拟设备安装，带有内部或云部署选项。 有关支持的可视化平台列表，请参阅“[设置 GitHub Enterprise Server 实例](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)”。 -{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. 要获取这些功能的演示，请联系 {% data variables.contact.contact_enterprise_sales %}。 有关这些功能的更多信息，请参阅“[关于对有漏洞的依赖项发出警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”和“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。 +{% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报和 {% data variables.product.prodname_github_connect %} 目前在 {% data variables.product.prodname_ghe_server %} 试用版中不可用。 要获取这些功能的演示，请联系 {% data variables.contact.contact_enterprise_sales %}。 有关这些功能的更多信息，请参阅“[关于对有漏洞的依赖项发出警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”和“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。 试用版也可用于 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_cloud %} 的试用](/articles/setting-up-a-trial-of-github-enterprise-cloud)”。 @@ -36,7 +36,7 @@ versions: - [{% data variables.product.prodname_dotcom %} 快速入门指南](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/)网络直播 - {% data variables.product.prodname_dotcom %} 指南中的[了解 {% data variables.product.prodname_dotcom %} 流程](https://guides.github.com/introduction/flow/) - {% data variables.product.prodname_dotcom %} 指南中的 [Hello World](https://guides.github.com/activities/hello-world/) -3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise/admin/configuration/configuring-your-enterprise)." +3. 要配置实例以满足组织的需求，请参阅“[配置企业](/enterprise/admin/configuration/configuring-your-enterprise)”。 4. 要将 {% data variables.product.prodname_ghe_server %} 与您的身份提供程序集成，请参阅“[使用 SAML](/enterprise/admin/user-management/using-saml)”和“[使用 LDAP](/enterprise/admin/authentication/using-ldap)”。 5. 邀请不限数量的人员加入您的试用版。 - 使用内置身份验证或配置的身份提供程序将用户添加到 {% data variables.product.prodname_ghe_server %} 实例。 更多信息请参阅“[使用内置身份验证](/enterprise/admin/user-management/using-built-in-authentication)”。 diff --git a/translations/zh-CN/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md b/translations/zh-CN/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md index 0d85da2186..e28f556658 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md +++ b/translations/zh-CN/content/github/getting-started-with-github/signing-up-for-a-new-github-account.md @@ -1,5 +1,6 @@ --- title: 注册新 GitHub 帐户 +shortTitle: 注册新 GitHub 帐户 intro: '{% data variables.product.product_name %} 为一起工作的人员团队提供个人和组织的用户帐户。' redirect_from: - /articles/signing-up-for-a-new-github-account @@ -9,9 +10,8 @@ versions: 有关帐户类型和产品的更多信息，请参阅“[{% data variables.product.prodname_dotcom %} 帐户的类型](/articles/types-of-github-accounts)”和“[{% data variables.product.product_name %} 的产品](/articles/github-s-products)”。 -1. 转到 {% data variables.product.product_name %} 的 [Pricing（定价）]({% data variables.product.pricing_url %})页面。 -2. 阅读关于 {% data variables.product.product_name %} 提供的不同产品和订阅的信息，然后单击您想要选择的订阅下的升级按钮。 -3. 按照提示操作，创建您的个人帐户或组织。 +{% data reusables.accounts.create-account %} +1. 按照提示操作，创建您的个人帐户或组织。 ### 后续步骤 diff --git a/translations/zh-CN/content/github/getting-started-with-github/supported-browsers.md b/translations/zh-CN/content/github/getting-started-with-github/supported-browsers.md index 7a77d7a282..f90b088f15 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/supported-browsers.md +++ b/translations/zh-CN/content/github/getting-started-with-github/supported-browsers.md @@ -4,7 +4,7 @@ redirect_from: - /articles/why-doesn-t-graphs-work-with-ie-8/ - /articles/why-don-t-graphs-work-with-ie8/ - /articles/supported-browsers -intro: '我们将 {% data variables.product.product_name %} 设计为支持最新的 Web 浏览器。 We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).' +intro: '我们将 {% data variables.product.product_name %} 设计为支持最新的 Web 浏览器。 我们支持最新版本的 [Chrome](https://www.google.com/chrome/)、[Firefox](http://www.mozilla.org/firefox/)、[Safari](http://www.apple.com/safari/) 和 [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge)。' versions: free-pro-team: '*' enterprise-server: '*' diff --git a/translations/zh-CN/content/github/getting-started-with-github/types-of-github-accounts.md b/translations/zh-CN/content/github/getting-started-with-github/types-of-github-accounts.md index a1fc5bf7a3..1119838201 100644 --- a/translations/zh-CN/content/github/getting-started-with-github/types-of-github-accounts.md +++ b/translations/zh-CN/content/github/getting-started-with-github/types-of-github-accounts.md @@ -1,6 +1,6 @@ --- title: GitHub 帐户的类型 -intro: '您的用户帐户是您在 {% data variables.product.product_location %} 中的身份。 Your user account can be a member of any number of organizations.{% if currentVersion == "free-pro-team@latest" %} Organizations can belong to enterprise accounts.{% endif %}' +intro: '您的用户帐户是您在 {% data variables.product.product_location %} 中的身份。 您的用户帐户可以是任意数量组织的成员。{% if currentVersion == "free-pro-team@latest" %} 组织可属于企业帐户。{% endif %}' redirect_from: - /manage-multiple-clients/ - /managing-clients/ @@ -14,8 +14,8 @@ versions: --- {% if currentVersion == "free-pro-team@latest" %} -For a full list of features for each -{% data variables.product.product_name %} product, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)." +有关每个 +{% data variables.product.product_name %} 产品功能的完整列表，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/github/getting-started-with-github/githubs-products)”。 {% endif %} ### 个人用户帐户 @@ -73,6 +73,6 @@ For a full list of features for each ### 延伸阅读 -{% if currentVersion == "free-pro-team@latest" %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)" +{% if currentVersion == "free-pro-team@latest" %}- "[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)" - “[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”{% endif %} - “[创建新组织帐户](/articles/creating-a-new-organization-account)” diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/zh-CN/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md index f9cd79ed8d..8a3398259d 100644 --- a/translations/zh-CN/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/zh-CN/content/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -22,7 +22,7 @@ versions: {% mac %} -1. [Create a new repository](/articles/creating-a-new-repository) on +1. [创建新仓库](/articles/creating-a-new-repository) {% data variables.product.product_location %}. 为避免错误，请勿使用*自述文件*、许可或 `gitignore` 文件初始化新仓库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 ![创建新仓库下拉列表](/assets/images/help/repository/repo-create.png) @@ -60,7 +60,7 @@ versions: {% windows %} -1. [Create a new repository](/articles/creating-a-new-repository) on +1. [创建新仓库](/articles/creating-a-new-repository) {% data variables.product.product_location %}. 为避免错误，请勿使用*自述文件*、许可或 `gitignore` 文件初始化新仓库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 ![创建新仓库下拉列表](/assets/images/help/repository/repo-create.png) @@ -98,7 +98,7 @@ versions: {% linux %} -1. [Create a new repository](/articles/creating-a-new-repository) on +1. [创建新仓库](/articles/creating-a-new-repository) {% data variables.product.product_location %}. 为避免错误，请勿使用*自述文件*、许可或 `gitignore` 文件初始化新仓库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 ![创建新仓库下拉列表](/assets/images/help/repository/repo-create.png) diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md index 11a2bc2493..72c36fdf28 100644 --- a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md +++ b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line.md @@ -1,6 +1,6 @@ --- title: 使用命令行导入 Git 仓库 -intro: '{% if currentVersion == "free-pro-team@latest" %}If [GitHub Importer](/articles/importing-a-repository-with-github-importer) is not suitable for your purposes, such as if your existing code is hosted on a private network, then we recommend importing using the command line.{% else %}Importing Git projects using the command line is suitable when your existing code is hosted on a private network.{% endif %}' +intro: '{% if currentVersion == "free-pro-team@latest" %}如果 [GitHub Importer](/articles/importing-a-repository-with-github-importer) 不适用于您的目的，例如，如果您现有的代码托管在私有网络上，则我们建议使用命令行导入。{% else %}当您现有的代码托管在私有网络上时，适合使用命令行导入 Git 项目。{% endif %}' redirect_from: - /articles/importing-a-git-repository-using-the-command-line versions: diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github.md b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github.md index eb0f930863..40accb0382 100644 --- a/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github.md +++ b/translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github.md @@ -1,6 +1,6 @@ --- title: 将源代码导入到 GitHub -intro: 'You can import repositories to GitHub using {% if currentVersion == "free-pro-team@latest" %}GitHub Importer, the command line,{% else %}the command line{% endif %} or external migration tools.' +intro: '您可以使用 {% if currentVersion == "free-pro-team@latest" %}GitHub 导入工具、命令行、{% else %}命令行{% endif %}或外部迁移工具将仓库导入到 GitHub。' redirect_from: - /articles/importing-an-external-git-repository/ - /articles/importing-from-bitbucket/ diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/index.md b/translations/zh-CN/content/github/importing-your-projects-to-github/index.md index 126e13f568..bb43f88fcf 100644 --- a/translations/zh-CN/content/github/importing-your-projects-to-github/index.md +++ b/translations/zh-CN/content/github/importing-your-projects-to-github/index.md @@ -15,11 +15,9 @@ versions: ### 目录 {% topic_link_in_list /importing-source-code-to-github %} - {% link_in_list /about-github-importer %} {% link_in_list /importing-a-repository-with-github-importer %} {% link_in_list /updating-commit-author-attribution-with-github-importer %} - {% link_in_list /importing-a-git-repository-using-the-command-line %} {% link_in_list /adding-an-existing-project-to-github-using-the-command-line %} {% link_in_list /source-code-migration-tools %} diff --git a/translations/zh-CN/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md b/translations/zh-CN/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md index e85088c427..0049b510b7 100644 --- a/translations/zh-CN/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md +++ b/translations/zh-CN/content/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git.md @@ -35,9 +35,9 @@ Git 项目也存储在一个目录中。 不过，Git 通过将其引用存储 Git 工作流程可能类似如下： * Git 仓库在 *.git* 目录中存储所有其分支和标记的完整历史记录。 -* The latest stable release is contained within the default branch. +* 最新稳定发行版包含在默认分支中。 * 活动功能工作在单独的分支中进行开发。 -* When a feature is finished, the feature branch is merged into the default branch and deleted. +* 功能完成后，该功能分支将合并到默认分支中并删除。 与 SVN 不同的是，使用 Git 时目录结构保持不变，但文件内容会根据您的分支而变化。 diff --git a/translations/zh-CN/content/github/index.md b/translations/zh-CN/content/github/index.md index 7a23b91c11..e9bbd4f9ed 100644 --- a/translations/zh-CN/content/github/index.md +++ b/translations/zh-CN/content/github/index.md @@ -20,24 +20,14 @@ versions: {% link_in_list /authenticating-to-github %} - {% link_in_list /managing-subscriptions-and-notifications-on-github %} - - {% link_in_list /receiving-notifications-about-activity-on-github %} - {% link_in_list /setting-up-and-managing-organizations-and-teams %} - - {% link_in_list /setting-up-and-managing-your-enterprise %} - - - {% link_in_list /setting-up-and-managing-billing-and-payments-on-github %} - {% link_in_list /writing-on-github %} @@ -50,10 +40,7 @@ versions: {% link_in_list /collaborating-with-issues-and-pull-requests %} {% link_in_list /managing-your-work-on-github %} - - {% link_in_list /developing-online-with-codespaces %} - {% link_in_list /building-a-strong-community %} @@ -64,45 +51,20 @@ versions: {% link_in_list /administering-a-repository %} {% link_in_list /visualizing-repository-data-with-graphs %} - - {% link_in_list /managing-security-vulnerabilities %} - {% link_in_list /finding-security-vulnerabilities-and-errors-in-your-code %} {% link_in_list /managing-files-in-a-repository %} {% link_in_list /managing-large-files %} - - {% link_in_list /customizing-your-github-workflow %} - {% link_in_list /extending-github %} {% link_in_list /working-with-github-pages %} - - {% link_in_list /supporting-the-open-source-community-with-github-sponsors %} - - - -{% link_in_list /teaching-and-learning-with-github-education %} - - - {% link_in_list /finding-talent-with-github-jobs %} - - - {% link_in_list /working-with-github-support %} - - - {% link_in_list /understanding-how-github-uses-and-protects-your-data %} - - - {% link_in_list /site-policy %} - diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md b/translations/zh-CN/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md index eb3ff9d31b..c65a478914 100644 --- a/translations/zh-CN/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md +++ b/translations/zh-CN/content/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line.md @@ -20,9 +20,9 @@ versions: {% data reusables.repositories.sensitive-info-warning %} -1. On your computer, move the file you'd like to upload to +1. 在计算机上，将您上传到 -{% data variables.product.product_name %} into the local directory that was created when you cloned the repository. +{% data variables.product.product_name %} 的文件移入克隆仓库时创建的本地目录。 {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} {% data reusables.git.stage_for_commit %} diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md b/translations/zh-CN/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md index eafb1341b4..3d10eccec5 100644 --- a/translations/zh-CN/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md +++ b/translations/zh-CN/content/github/managing-files-in-a-repository/getting-permanent-links-to-files.md @@ -23,17 +23,17 @@ versions: * [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md) -refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file. +引用 GitHub 的 `codeql` 仓库，并显示 `main` 分支中 `README.md` 文件的当前版本。 分支头部的文件版本可能会随着新的提交而改变，因此如果您复制常规的 URL，当以后有人查看时，文件内容可能会不同。 ### 按 y 键可永久链接到特定提交中的文件 -For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id. 这将永久链接到该提交中文件的精确版本。 例如： +要创建所查看文件特定版本的永久链接，不要在 URL 中使用分支名称（例如上例中的 `main` 部分），而是输入提交 id。 这将永久链接到该提交中文件的精确版本。 例如： * [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) -replaces `main` with a specific commit id and the file content will not change. +将 `main` 替换为特定提交 id，文件内容将不会改变。 但是，手动查找提交 SHA 比较麻烦，因此您可以采用便捷方式，通过键入 y 将 URL 自动更新为永久链接版本。 然后，您可以复制该 URL，以后访问它的任何人都将看到与您所见完全一致的内容。 diff --git a/translations/zh-CN/content/github/managing-files-in-a-repository/index.md b/translations/zh-CN/content/github/managing-files-in-a-repository/index.md index 8f896ab9ed..a12db97706 100644 --- a/translations/zh-CN/content/github/managing-files-in-a-repository/index.md +++ b/translations/zh-CN/content/github/managing-files-in-a-repository/index.md @@ -14,9 +14,7 @@ versions: ### 目录 {% topic_link_in_list /managing-files-on-github %} - {% link_in_list /navigating-code-on-github %} - {% link_in_list /creating-new-files %} {% link_in_list /adding-a-file-to-a-repository %} {% link_in_list /moving-a-file-to-a-new-location %} diff --git a/translations/zh-CN/content/github/managing-large-files/about-git-large-file-storage.md b/translations/zh-CN/content/github/managing-large-files/about-git-large-file-storage.md index c5e191fadf..c5488fa2cd 100644 --- a/translations/zh-CN/content/github/managing-large-files/about-git-large-file-storage.md +++ b/translations/zh-CN/content/github/managing-large-files/about-git-large-file-storage.md @@ -13,8 +13,8 @@ versions: {% data variables.large_files.product_name_short %} 处理大文件的方式是存储对仓库中文件的引用，而不实际文件本身。 为满足 Git 的架构要求，{% data variables.large_files.product_name_short %} 创建了指针文件，用于对实际文件（存储在其他位置）的引用。 {% data variables.product.product_name %} 在仓库中管理此指针文件。 克隆仓库时，{% data variables.product.product_name %} 使用指针文件作为映射来查找大文件。 {% if currentVersion == "free-pro-team@latest" %} -Using -{% data variables.large_files.product_name_short %}, you can store files up to: +使用 +{% data variables.large_files.product_name_short %}，可以将文件存储到： | 产品 | 最大文件大小 | | ------------------------------------------------- | ---------------- | @@ -22,8 +22,8 @@ Using | {% data variables.product.prodname_pro %} | 2 GB | | {% data variables.product.prodname_team %} | 4 GB | | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %} - Using -{% data variables.large_files.product_name_short %}, you can store files up to {% if currentVersion ver_lt "enterprise-server@2.21" %}{% data variables.large_files.max_lfs_size %}{% else %}5 GB{% endif %} in your repository. + 使用 +{% data variables.large_files.product_name_short %}，可在仓库中存储最多 {% if currentVersion ver_lt "enterprise-server@2.21" %}{% data variables.large_files.max_lfs_size %}{% else %}5 GB{% endif %} 的文件。 {% endif %} 您也可以将 {% data variables.large_files.product_name_short %} 与 {% data variables.product.prodname_desktop %} 结合使用。 有关在 {% data variables.product.prodname_desktop %} 中克隆 Git LFS 仓库的更多信息，请参阅"[将仓库从 GitHub 克隆到 GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)"。 @@ -45,8 +45,8 @@ size 84977953 {% note %} **注意**： -- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites. -- {% data variables.large_files.product_name_short %} cannot be used with template repositories. +- {% data variables.large_files.product_name_short %} 不能用于 {% data variables.product.prodname_pages %} 站点。 +- {% data variables.large_files.product_name_short %} 不能用于模板仓库。 {% endnote %} diff --git a/translations/zh-CN/content/github/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/zh-CN/content/github/managing-large-files/about-storage-and-bandwidth-usage.md index 7c60f43695..79bb57c236 100644 --- a/translations/zh-CN/content/github/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/zh-CN/content/github/managing-large-files/about-storage-and-bandwidth-usage.md @@ -20,8 +20,8 @@ versions: - 如果下载一个使用 LFS 跟踪的 500 MB 文件，您将使用仓库所有者分配的 500 MB 带宽。 如果协作者推送文件更改并将新版本拉取到本地仓库，您将使用另外 500 MB 的带宽，所以两次下载的总使用量是 1 GB 带宽。 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -If -{% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in source code archives for your repository, downloads of those archives will count towards bandwidth usage for the repository. 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。 +如果 +{% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在仓库的源代码存档中，则下载这些存档将会计入仓库的带宽使用量。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。 {% endif %} {% tip %} 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 e5b1994a9a..b04c985005 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: 大文件的条件 -intro: '{% data variables.product.product_name %} 限制了仓库允许的文件大小，如果文件大于最大文件限制，将会阻止推送到仓库。' +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.' redirect_from: - /articles/conditions-for-large-files versions: @@ -11,10 +11,10 @@ versions: {% data reusables.large_files.use_lfs_tip %} -### 文件大于 {% data variables.large_files.warning_size %} 时的警告 +### Warning for files larger than {% data variables.large_files.warning_size %} -如果尝试添加或更新大于 {% data variables.large_files.warning_size %} 的文件，您将从 Git 收到警告。 更改仍将成功推送到仓库，但您可以考虑删除提交，以尽量减少对性能的影响。 更多信息请参阅“[从仓库的历史记录中删除文件](/github/managing-large-files/removing-files-from-a-repositorys-history)”。 +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)." -### 阻止大文件的推送 +### 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 %}. 更多信息请参阅“[设置 Git 推送限制](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)”。{% endif %} +{% 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 %} diff --git a/translations/zh-CN/content/github/managing-large-files/configuring-git-large-file-storage.md b/translations/zh-CN/content/github/managing-large-files/configuring-git-large-file-storage.md index e3487cd669..179b2e6497 100644 --- a/translations/zh-CN/content/github/managing-large-files/configuring-git-large-file-storage.md +++ b/translations/zh-CN/content/github/managing-large-files/configuring-git-large-file-storage.md @@ -18,7 +18,7 @@ versions: {% tip %} -**Note:** Before trying to push a large file to {% data variables.product.product_name %}, make sure that you've enabled {% data variables.large_files.product_name_short %} on your enterprise. 更多信息请参阅“[在 GitHub Enterprise Server 上配置 Git Large File Storage](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)”。 +**注：**尝试向 {% data variables.product.product_name %} 推送大文件之前，请确保在您的企业上启用了 {% data variables.large_files.product_name_short %}。 更多信息请参阅“[在 GitHub Enterprise Server 上配置 Git Large File Storage](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)”。 {% endtip %} @@ -59,5 +59,5 @@ versions: ### 延伸阅读 -- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +- "[与 {% data variables.large_files.product_name_long %} 协作](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} - "[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)"{% endif %} diff --git a/translations/zh-CN/content/github/managing-large-files/index.md b/translations/zh-CN/content/github/managing-large-files/index.md index bad4c6a34f..3b7a69f857 100644 --- a/translations/zh-CN/content/github/managing-large-files/index.md +++ b/translations/zh-CN/content/github/managing-large-files/index.md @@ -15,16 +15,12 @@ versions: {% link_in_list /conditions-for-large-files %} {% link_in_list /removing-files-from-a-repositorys-history %} {% link_in_list /distributing-large-binaries %} - {% link_in_list /what-is-my-disk-quota %} - {% topic_link_in_list /versioning-large-files %} {% link_in_list /about-git-large-file-storage %} {% link_in_list /installing-git-large-file-storage %} {% link_in_list /configuring-git-large-file-storage %} - {% link_in_list /about-storage-and-bandwidth-usage %} - {% link_in_list /collaboration-with-git-large-file-storage %} {% link_in_list /moving-a-file-in-your-repository-to-git-large-file-storage %} {% link_in_list /removing-files-from-git-large-file-storage %} diff --git a/translations/zh-CN/content/github/managing-large-files/installing-git-large-file-storage.md b/translations/zh-CN/content/github/managing-large-files/installing-git-large-file-storage.md index 82091a39c4..8cab311a71 100644 --- a/translations/zh-CN/content/github/managing-large-files/installing-git-large-file-storage.md +++ b/translations/zh-CN/content/github/managing-large-files/installing-git-large-file-storage.md @@ -58,7 +58,7 @@ versions: {% endtip %} 2. 在计算机上，找到下载的文件。 -3. 双击文件 *git-lfs-windows-1.X.X.exe*，其中 1.X.X 替换为您下载的 Git LFS 版本。 When you open this file Windows will run a setup wizard to install +3. 双击文件 *git-lfs-windows-1.X.X.exe*，其中 1.X.X 替换为您下载的 Git LFS 版本。 当您打开此文件时，Windows 将运行安装向导以安装 {% data variables.large_files.product_name_short %}. {% data reusables.command_line.open_the_multi_os_terminal %} 5. 验证安装成功： diff --git a/translations/zh-CN/content/github/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/zh-CN/content/github/managing-large-files/removing-files-from-git-large-file-storage.md index edcfb882d2..36789be6e5 100644 --- a/translations/zh-CN/content/github/managing-large-files/removing-files-from-git-large-file-storage.md +++ b/translations/zh-CN/content/github/managing-large-files/removing-files-from-git-large-file-storage.md @@ -36,9 +36,9 @@ versions: ### 仓库中的 {% data variables.large_files.product_name_short %} 对象 -After you remove files from {% data variables.large_files.product_name_short %}, the {% data variables.large_files.product_name_short %} objects still exist on the remote storage{% if currentVersion == "free-pro-team@latest" %} and will continue to count toward your {% data variables.large_files.product_name_short %} storage quota{% endif %}. +从 {% data variables.large_files.product_name_short %} 中删除文件后，{% data variables.large_files.product_name_short %} 对象仍存在于远程存储中{% if currentVersion == "free-pro-team@latest" %} 并将继续计入您的 {% data variables.large_files.product_name_short %} 存储配额{% endif %}。 -To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. 删除仓库时，所有关联的议题、星标和复刻也会被删除。 更多信息请参阅“[删除仓库](/github/administering-a-repository/deleting-a-repository)”。{% else %}请联系 {% data variables.product.prodname_enterprise %} 管理员以存档对象。 存档的对象将在三个月后清除。{% endif %} +要从仓库中删除 {% data variables.large_files.product_name_short %} 对象，请{% if currentVersion == "free-pro-team@latest" %}删除并重新创建仓库。 删除仓库时，所有关联的议题、星标和复刻也会被删除。 更多信息请参阅“[删除仓库](/github/administering-a-repository/deleting-a-repository)”。{% else %}请联系 {% data variables.product.prodname_enterprise %} 管理员以存档对象。 存档的对象将在三个月后清除。{% endif %} {% note %} 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 a628b146fd..67f9613edb 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 @@ -25,6 +25,8 @@ When your code depends on a package that has a security vulnerability, this vuln - 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 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)." {% note %} diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md new file mode 100644 index 0000000000..03831496b1 --- /dev/null +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies.md @@ -0,0 +1,24 @@ +--- +title: About managing vulnerable dependencies +intro: '{% data variables.product.prodname_dotcom %} helps you to avoid using third-party software that contains known vulnerabilities.' +versions: + free-pro-team: '*' +--- + +{% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies. + +#### Dependency graph +依赖项图是存储在仓库中的清单和锁定文件的摘要。 It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 + +#### Dependency review +By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + +#### {% data variables.product.prodname_dependabot_alerts %} +{% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 + +#### {% data variables.product.prodname_dependabot_security_updates %} +When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." + + +#### {% data variables.product.prodname_dependabot_version_updates %} +Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." 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 2b32234811..f85505ecaf 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 @@ -12,7 +12,7 @@ versions: {% 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-features-for-new-repositories)." +{% 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)." {% endif %} {% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %} diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/index.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/index.md index daad20f062..d09faff0b8 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/index.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/index.md @@ -9,8 +9,6 @@ versions: ### 目录 - - {% topic_link_in_list /managing-security-vulnerabilities-in-your-project %} {% link_in_list /adding-a-security-policy-to-your-repository %} {% link_in_list /about-github-security-advisories %} @@ -22,17 +20,13 @@ versions: {% link_in_list /publishing-a-security-advisory %} {% link_in_list /editing-a-security-advisory %} {% link_in_list /withdrawing-a-security-advisory %} - {% topic_link_in_list /managing-vulnerabilities-in-your-projects-dependencies %} - + {% link_in_list /about-managing-vulnerable-dependencies %} {% link_in_list /browsing-security-vulnerabilities-in-the-github-advisory-database %} - {% link_in_list /about-alerts-for-vulnerable-dependencies %} {% link_in_list /configuring-notifications-for-vulnerable-dependencies %} - {% link_in_list /about-dependabot-security-updates %} {% link_in_list /configuring-dependabot-security-updates %} {% link_in_list /viewing-and-updating-vulnerable-dependencies-in-your-repository %} {% link_in_list /troubleshooting-the-detection-of-vulnerable-dependencies %} {% link_in_list /troubleshooting-dependabot-errors %} - diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md index fa185001d2..36367d556c 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors.md @@ -76,6 +76,12 @@ There are separate limits for security and version update pull requests, so that 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 %} can't resolve your dependency files + +**Version updates only.** If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, you will see the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files". + +{% 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 If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request. diff --git a/translations/zh-CN/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/zh-CN/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index a000713180..eb9553f27e 100644 --- a/translations/zh-CN/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/translations/zh-CN/content/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -13,9 +13,11 @@ versions: 您可以为使用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图的任何仓库启用自动安全更新。 For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +{% data reusables.repositories.dependency-review %} + ### 关于仓库中有漏洞的依赖项的更新 -{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect vulnerabilities affecting your repository. 对于启用了 {% data variables.product.prodname_dependabot_security_updates %} 的仓库，当 {% data variables.product.product_name %} 检测到有漏洞的依赖项时，{% data variables.product.prodname_dependabot %} 会创建拉取请求来修复它。 拉取请求会将依赖项升级到避免漏洞所需的最低安全版本。 +{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known vulnerabilities. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. 拉取请求会将依赖项升级到避免漏洞所需的最低安全版本。 ### 查看和更新有漏洞的依赖项 diff --git a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md index 30ec7199c8..96f4efcb9e 100644 --- a/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md +++ b/translations/zh-CN/content/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox.md @@ -124,7 +124,8 @@ versions: - `is:repository-invitation`{% if currentVersion != "github-ae@latest" %} - `is:repository-vulnerability-alert` - `is:repository-advisory`{% endif %} -- `is:team-discussion` +- `is:team-discussion`{% if currentVersion == "free-pro-team@latest" %} +- `is:discussions`{% endif %} {% if currentVersion != "github-ae@latest" %} For information about reducing noise from notifications for diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/about-issues.md b/translations/zh-CN/content/github/managing-your-work-on-github/about-issues.md index 4089f51441..1c14a9bbb2 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/about-issues.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/about-issues.md @@ -10,11 +10,17 @@ versions: github-ae: '*' --- +### 关于议题 + 您可以在仓库中使用议题收集用户反馈，报告软件漏洞，并且组织要完成的任务。 议题不只是一个报告软件漏洞的地方。 +Other conversations are more suitable for discussions. {% data reusables.discussions.you-can-use-discussions %} + +{% data reusables.discussions.you-cannot-convert-a-discussion %} + {% data reusables.pull_requests.close-issues-using-keywords %} -为保持更新议题中的最新评论，您可以监控问题以接收关于最新评论的通知。 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 %}." +为保持更新议题中的最新评论，您可以监控问题以接收关于最新评论的通知。 更多信息请参阅{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。 要快速查找指向您订阅的最新议题的链接，请访问仪表板。 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。 @@ -26,7 +32,7 @@ versions: - 创建议题模板可帮助贡献者打开有意义的议题。 更多信息请参阅“[关于议题和拉取请求模板](/articles/about-issue-and-pull-request-templates)”。 - 将打开的议题传输到其他仓库。 更多信息请参阅“[将议题传输到其他仓库](/articles/transferring-an-issue-to-another-repository)”。 - 固定重要议题以使其更易于查找，防止重复的议题，减少干扰。 更多信息请参阅“[将议题固定到仓库](/articles/pinning-an-issue-to-your-repository)”。 -- 使用保存的回复跟踪重复的议题。 For more information, see "[About saved replies](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} +- 使用保存的回复跟踪重复的议题。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% if currentVersion == "free-pro-team@latest" %} - 报告违反{% data variables.product.prodname_dotcom %}'s [社区指导方针](/articles/github-community-guidelines)的评论。 更多信息请参阅“[报告滥用或垃圾邮件](/articles/reporting-abuse-or-spam)”。{% endif %} 议题也可以[分配到其他用户](/articles/assigning-issues-and-pull-requests-to-other-github-users)，[用标签标记](/articles/applying-labels-to-issues-and-pull-requests)以便快速搜索，以及[与里程碑组合](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)。 diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/index.md b/translations/zh-CN/content/github/managing-your-work-on-github/index.md index e1a17afdf5..1632261edd 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/index.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/index.md @@ -17,15 +17,11 @@ versions: {% topic_link_in_list /managing-your-work-with-issues-and-pull-requests %} {% link_in_list /about-issues %} {% link_in_list /creating-an-issue %} - {% link_in_list /deleting-an-issue %} - {% link_in_list /opening-an-issue-from-a-comment %} {% link_in_list /opening-an-issue-from-code %} - {% link_in_list /transferring-an-issue-to-another-repository %} {% link_in_list /pinning-an-issue-to-your-repository %} - {% link_in_list /creating-a-permanent-link-to-a-code-snippet %} {% link_in_list /managing-labels %} {% link_in_list /about-task-lists %} @@ -43,9 +39,7 @@ versions: {% link_in_list /linking-a-repository-to-a-project-board %} {% link_in_list /about-automation-for-project-boards %} {% link_in_list /configuring-automation-for-project-boards %} - {% link_in_list /copying-a-project-board %} - {% link_in_list /closing-a-project-board %} {% link_in_list /reopening-a-closed-project-board %} {% link_in_list /deleting-a-project-board %} diff --git a/translations/zh-CN/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md b/translations/zh-CN/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md index 986be98602..761d7a9b19 100644 --- a/translations/zh-CN/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md +++ b/translations/zh-CN/content/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests.md @@ -25,6 +25,7 @@ versions: - 过滤涉及但不一定[**@提及**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)的特定人员的议题和拉取请求：`state:open type:issue involves:octocat` - 按受理人过滤议题和拉取请求：`state:open type:issue assignee:octocat` - 按标签过滤议题和拉取请求：`state:open type:issue label:"bug"` +- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat` {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} 对于议题，您还可以使用搜索来： diff --git a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/index.md b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/index.md index aafa9e0795..2d27a5b427 100644 --- a/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/index.md +++ b/translations/zh-CN/content/github/receiving-notifications-about-activity-on-github/index.md @@ -14,16 +14,10 @@ versions: {% link_in_list /choosing-the-delivery-method-for-your-notifications %} {% topic_link_in_list /managing-your-notifications %} {% link_in_list /marking-notifications-as-read %} - {% link_in_list /saving-notifications-for-later %} - {% link_in_list /subscribing-to-and-unsubscribing-from-notifications %} - {% link_in_list /listing-the-issues-and-pull-requests-youre-subscribed-to %} - {% link_in_list /watching-and-unwatching-repositories %} - {% link_in_list /watching-and-unwatching-releases-for-a-repository %} - {% link_in_list /watching-and-unwatching-team-discussions %} {% link_in_list /listing-the-repositories-youre-watching %} diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/about-searching-on-github.md b/translations/zh-CN/content/github/searching-for-information-on-github/about-searching-on-github.md index eaf6392f07..a3f6133f88 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/about-searching-on-github.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/about-searching-on-github.md @@ -41,7 +41,8 @@ You can search for the following information across all repositories you can acc - [仓库](/articles/searching-for-repositories) - [主题](/articles/searching-topics) -- [议题和拉取请求](/articles/searching-issues-and-pull-requests) +- [Issues and pull requests](/articles/searching-issues-and-pull-requests){% if currentVersion == "free-pro-team@latest" %} +- [Discussions](/github/searching-for-information-on-github/searching-discussions){% endif %} - [代码](/articles/searching-code) - [提交](/articles/searching-commits) - [Users](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/index.md b/translations/zh-CN/content/github/searching-for-information-on-github/index.md index 0f064e8ce6..401fc80b23 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/index.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/index.md @@ -26,6 +26,7 @@ versions: {% link_in_list /searching-code %} {% link_in_list /searching-commits %} {% link_in_list /searching-issues-and-pull-requests %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /searching-discussions %} {% link_in_list /searching-github-marketplace %}{% endif %} {% link_in_list /searching-users %} {% link_in_list /searching-for-packages %} diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-discussions.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-discussions.md new file mode 100644 index 0000000000..190b2a11c0 --- /dev/null +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-discussions.md @@ -0,0 +1,110 @@ +--- +title: Searching discussions +intro: You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。 + +{% data reusables.search.syntax_tips %} + +### 按标题、正文或评论搜索 + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| 限定符 | 示例 | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +### 在用户或组织的仓库内搜索 + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| 限定符 | 示例 | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +### Filter by repository visibility + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. 更多信息请参阅“[关于仓库可见性](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)”。 + +| Qualifier | Example | :- | :- |{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +### 按作者搜索 + +The `author` qualifier finds discussions created by a certain user. + +| 限定符 | 示例 | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +### 按评论者搜索 + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +### Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +### 按评论数量搜索 + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| 限定符 | 示例 | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +### 按交互数量搜索 + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| 限定符 | 示例 | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +### 按反应数量搜索 + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +### Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +### 延伸阅读 + +- “[排序搜索结果](/articles/sorting-search-results/)” diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md index 3dc814a4cb..3fde5351e1 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-issues-and-pull-requests.md @@ -203,7 +203,7 @@ You can filter by the visibility of the repository containing the issues and pul | 限定符 | 示例 | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3C100&type=Issues) 匹配具有超过 100 条评论的已关闭议题。 | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) 匹配具有超过 100 条评论的已关闭议题。 | | | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) 匹配具有 500 到 1,000 条评论的议题。 | ### 按交互数量搜索 diff --git a/translations/zh-CN/content/github/searching-for-information-on-github/searching-topics.md b/translations/zh-CN/content/github/searching-for-information-on-github/searching-topics.md index 1fa02750c1..b7bf79e14b 100644 --- a/translations/zh-CN/content/github/searching-for-information-on-github/searching-topics.md +++ b/translations/zh-CN/content/github/searching-for-information-on-github/searching-topics.md @@ -26,7 +26,7 @@ versions: `is:featured` 搜索限定符会将搜索结果范围缩小为 {% data variables.product.product_name %} 上具有最多仓库的主题。 这些主题还会在 https://github.com/topics/ 上提供。 -`is:curated` 搜索限定符可将搜索结果范围缩小到社区成员已向其添加额外信息的主题。 更多信息请参阅位于 https://github.com/github/explore 的探索仓库。 +`is:curated` 搜索限定符可将搜索结果范围缩小到社区成员已向其添加额外信息的主题。 For more information, see the [explore repository](https://github.com/github/explore). 您可以使用日期参数和 `created:` 根据创建时间过滤主题，也可以使用 `repositories:n` 根据与此主题关联的仓库数量过滤主题。 这两个限定符都可以使用[大于和小于范围限定符](/articles/understanding-the-search-syntax)。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md index 9f205d0951..f2a41cafb4 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions.md @@ -8,7 +8,9 @@ versions: ### 关于 {% data variables.product.prodname_actions %} 的计费 -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} + +{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." 分钟数每月都会重置，而存储使用量不重置。 @@ -69,8 +71,8 @@ versions: ### 关于支出限制 -默认情况下，您的帐户对 {% data variables.product.prodname_actions %} 使用的支出限额为 0 美元。 要为私有仓库启用超过帐户自带量使用分钟数和存储空间，您可以增加支出限额或允许无限制支出。 更多信息请参阅“[管理 {% data variables.product.prodname_actions %} 的支出限制](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)”。 +{% data reusables.github-actions.actions-spending-limit-detailed %} -{% data reusables.github-actions.spending-limit-enterprise-account %} +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 reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md index 3272ffef6e..e8c42362b5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages.md @@ -10,6 +10,8 @@ versions: {% data reusables.package_registry.packages-billing %} +{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." + {% data reusables.package_registry.container-registry-beta-billing-note %} 数据传输每月都会重置，而存储使用量不重置。 @@ -50,8 +52,8 @@ versions: ### 关于支出限制 -默认情况下，您的帐户对 {% data variables.product.prodname_registry %} 使用的支出限额为 0 美元。 要对超出帐户所含金额的私人软件包启用存储和数据传输，您可以增加支出限额或允许无限制支出。 更多信息请参阅“[管理 {% data variables.product.prodname_registry %} 的支出限制](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)”。 +{% data reusables.package_registry.packages-spending-limit-detailed %} -{% data reusables.package_registry.spending-limit-enterprise-account %} +For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)." {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md index 03fbc9aee7..b12446b110 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors.md @@ -9,6 +9,8 @@ versions: {% data reusables.sponsors.sponsorship-details %} +{% data reusables.sponsors.no-fees %} + {% data reusables.dotcom_billing.view-all-subscriptions %} ### 延伸阅读 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 1235ca02f7..84e699acfb 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts.md @@ -18,11 +18,11 @@ versions: ### 个人帐户折扣 -拥有 {% data variables.product.prodname_free_user %} 的学生和教职工除了可使用无限公共和私有仓库外，经验证的学生还可以申请 {% data variables.product.prodname_student_pack %}，以便从 {% data variables.product.prodname_dotcom %} 合作伙伴处获得其他好处。 更多信息请参阅“[申请学生开发包](/articles/applying-for-a-student-developer-pack)”。 +拥有 {% data variables.product.prodname_free_user %} 的学生和教职工除了可使用无限公共和私有仓库外，经验证的学生还可以申请 {% data variables.product.prodname_student_pack %}，以便从 {% data variables.product.prodname_dotcom %} 合作伙伴处获得其他好处。 For more information, see "[Apply for a student developer pack](/education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack)." ### 学校和大学折扣 -经验证的教师可出于教学和学术研究目的申请 {% data variables.product.prodname_team %}。 经验证的教师可出于教学和学术研究目的申请 {% data variables.product.prodname_team %}。 更多信息请参阅“[在课堂和研究中使用 {{ 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 %}。 For more information, see "[Use {% data variables.product.prodname_dotcom %} in your classroom and research](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research)." 更多信息请参阅“[在课堂和研究中使用 {{ site.data.variables.product.prodname_dotcom }}](/articles/using-github-in-your-classroom-and-research)”。 更多信息请访问 [{% data variables.product.prodname_education %}](https://education.github.com/)。 ### 非赢利组织和图书馆折扣 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 1eeb5127d8..6a0aecc2d9 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 @@ -7,24 +7,24 @@ versions: free-pro-team: '*' --- +{% 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.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. 在页面右侧，靠近所选等级的位置，单击 **Edit（编辑）**。 ![编辑等级按钮](/assets/images/help/billing/edit-tier-button.png) +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %} ### 取消赞助 -取消赞助后，更改将在下一个结算日期生效。 {% data reusables.sponsors.no-refunds %} - {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.billing %} +{% 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/managing-your-spending-limit-for-github-actions.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md index 8010fa334d..37c851edcd 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions.md @@ -8,13 +8,15 @@ versions: ### 关于 {% data variables.product.prodname_actions %} 的支出限额 -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} +{% data reusables.github-actions.actions-billing %} -您可以设置更高的支出限额，或者对某些帐户允许无限制的支出。 如果您按发票为组织或企业帐户付款，可以预付超额费用以设置更高的支出限额。 支出限额适用于 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 的总超支额。 有关 {% 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)”。 +{% data reusables.github-actions.actions-spending-limit-brief %} -只要您将支出限额设定在 0 美元以上，您就要对过去发生的任何超额情况负责。 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且创建将当月存储使用量从 1.9GB 增加到 2.1GB 的工作流程工件，那么您使用的存储空间将比产品包含的 2GB 稍高。 +{% 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)." -由于您尚未启用超额，因此下次尝试发布包版本将失败。 您不会收到该月 0.1GB 超额费用的帐单。 但是，如果您在下个月启用超额，您的第一份帐单将包括过去的 0.1GB 超额，以及当前计费周期的任何超额。 +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且创建将当月存储使用量从 1.9GB 增加到 2.1GB 的工作流程工件，那么您使用的存储空间将比产品包含的 2GB 稍高。 + +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. ### 管理您用户帐户的 {% data variables.product.prodname_actions %} 支出限额 @@ -30,8 +32,6 @@ versions: 组织所有者和帐单管理员可管理组织的 {% data variables.product.prodname_actions %} 支出限额。 -如果通过发票支付组织帐户，您无法在 {% data variables.product.product_name %} 上管理企业帐户的支出限额。 如果想允许组织拥有的仓库对 {% data variables.product.prodname_actions %} 的使用超出各仓库包含的存储或数据传输量，您可以预付超限费用。 由于超限必须预付，因此不能对按发票付费的帐户启用无限制支出。 您的支出限额将是您预付金额的 150%。 如有任何问题，请[联系我们的客户管理团队](https://enterprise.github.com/contact)。 - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ versions: 企业所有者和帐单管理员可管理企业帐户的 {% data variables.product.prodname_actions %} 支出限额。 -{% data reusables.github-actions.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md index 3ef5ed1362..4785921f31 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages.md @@ -10,11 +10,13 @@ versions: {% data reusables.package_registry.packages-billing %} -您可以设置更高的支出限额，或者对某些帐户允许无限制的支出。 如果您按发票为组织或企业帐户付款，可以预付超额费用以设置更高的支出限额。 支出限额适用于 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 的总超支额。 有关 {% 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)”。 +{% data reusables.package_registry.packages-spending-limit-brief %} -只要您将支出限额设定在 0 美元以上，您就要对过去发生的任何超额情况负责。 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且发布新版私有包，将当月存储使用量从 1.9GB 增加到 2.1GB，那么发布该版本使用的存储空间将比产品包含的 2GB 稍高。 +{% 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)." -由于您尚未启用超额，因此下次尝试发布包版本将失败。 您不会收到该月 0.1GB 超额费用的帐单。 但是，如果您在下个月启用超额，您的第一份帐单将包括过去的 0.1GB 超额，以及当前计费周期的任何超额。 +As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. 例如，如果您的组织使用 {% data variables.product.prodname_team %}，不允许超额，并且发布新版私有包，将当月存储使用量从 1.9GB 增加到 2.1GB，那么发布该版本使用的存储空间将比产品包含的 2GB 稍高。 + +由于您尚未启用超额，因此下次尝试发布包版本将失败。 您不会收到该月 0.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. ### 管理您用户帐户的 {% data variables.product.prodname_registry %} 支出限额 @@ -30,8 +32,6 @@ versions: 组织所有者和帐单管理员可管理组织的 {% data variables.product.prodname_registry %} 支出限额。 -如果通过发票支付组织帐户，您无法在 {% data variables.product.product_name %} 上管理企业帐户的支出限额。 如果想允许组织拥有的仓库对 {% data variables.product.prodname_registry %} 的使用超出各仓库包含的存储或数据传输量，您可以预付超限费用。 由于超限必须预付，因此不能对按发票付费的帐户启用无限制支出。 您的支出限额将是您预付金额的 150%。 如有任何问题，请[联系我们的客户管理团队](https://enterprise.github.com/contact)。 - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} @@ -44,8 +44,6 @@ versions: 企业所有者和帐单管理员可管理企业帐户的 {% data variables.product.prodname_registry %} 支出限额。 -{% data reusables.package_registry.spending-limit-enterprise-account %} - {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} 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 cf0927e9ee..6239dd115e 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 @@ -7,12 +7,15 @@ versions: free-pro-team: '*' --- +{% data reusables.sponsors.org-sponsors-release-phase %} + +### About sponsorship upgrades + 当您升级赞助等级后，更改将立即生效。 {% data reusables.sponsors.prorated-sponsorship %} -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. 在页面右侧，靠近所选等级的位置，单击 **Edit（编辑）**。 ![编辑等级按钮](/assets/images/help/billing/edit-tier-button.png) +### 升级赞助 + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.update-sponsorship %} +{% data reusables.sponsors.update-sponsorship %} \ No newline at end of file diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md index 1dc75f3d02..aabc49714d 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account.md @@ -20,7 +20,7 @@ versions: ### 1. 备份组织内容 -删除组织后，GitHub **无法恢复内容**。 因此，在删除组织之前，请确保您拥有该帐户中所有仓库、wiki 和议题的副本。 +删除组织后，GitHub **无法恢复内容**。 Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. ### 2. 删除组织 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md index 5787a0d0db..44b8e80bc2 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -19,4 +19,4 @@ versions: {% data reusables.organizations.org_settings %} {% data reusables.organizations.oauth_app_access %} 5. 单击 **Remove restrictions（删除限制）**。 ![删除限制按钮](/assets/images/help/settings/settings-third-party-remove-restrictions.png) -6. 审查有关禁用第三方应用程序限制的信息后，请单击 **Yes, remove application restrictions（是，删除应用程序限制）**。 ![删除确认按钮按钮](/assets/images/help/settings/settings-third-party-confirm-disable.png) +6. 审查有关禁用第三方应用程序限制的信息后，请单击 **Yes, remove application restrictions（是，删除应用程序限制）**。 ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md index 3f91f87c84..52d7297490 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/index.md @@ -20,42 +20,30 @@ versions: {% link_in_list /creating-a-new-organization-from-scratch %} {% link_in_list /accessing-your-organizations-settings %} {% link_in_list /about-your-organizations-news-feed %} - {% link_in_list /viewing-insights-for-your-organization %} - {% topic_link_in_list /managing-membership-in-your-organization %} - {% link_in_list /inviting-users-to-join-your-organization %} {% link_in_list /canceling-or-editing-an-invitation-to-join-your-organization %} {% link_in_list /adding-people-to-your-organization %} - {% link_in_list /removing-a-member-from-your-organization %} {% link_in_list /reinstating-a-former-member-of-your-organization %} - {% link_in_list /can-i-create-accounts-for-people-in-my-organization %} - {% topic_link_in_list /managing-peoples-access-to-your-organization-with-roles %} {% link_in_list /permission-levels-for-an-organization %} {% link_in_list /maintaining-ownership-continuity-for-your-organization %} {% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %} - {% link_in_list /adding-a-billing-manager-to-your-organization %} {% link_in_list /removing-a-billing-manager-from-your-organization %} - {% topic_link_in_list /organizing-members-into-teams %} {% link_in_list /about-teams %} {% link_in_list /creating-a-team %} {% link_in_list /setting-your-teams-profile-picture %} {% link_in_list /adding-organization-members-to-a-team %} - {% link_in_list /managing-code-review-assignment-for-your-team %} - {% link_in_list /renaming-a-team %} {% link_in_list /changing-team-visibility %} - {% link_in_list /synchronizing-a-team-with-an-identity-provider-group %} - {% link_in_list /moving-a-team-in-your-organizations-hierarchy %} {% link_in_list /requesting-to-add-a-child-team %} {% link_in_list /requesting-to-add-or-change-a-parent-team %} @@ -66,9 +54,7 @@ versions: {% topic_link_in_list /managing-access-to-your-organizations-repositories %} {% link_in_list /repository-permission-levels-for-an-organization %} {% link_in_list /setting-base-permissions-for-an-organization %} - {% link_in_list /viewing-people-with-access-to-your-repository %} - {% link_in_list /managing-an-individuals-access-to-an-organization-repository %} {% link_in_list /managing-team-access-to-an-organization-repository %} {% link_in_list /adding-outside-collaborators-to-repositories-in-your-organization %} @@ -84,83 +70,54 @@ versions: {% link_in_list /managing-an-individuals-access-to-an-organization-project-board %} {% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %} {% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %} - {% topic_link_in_list /managing-access-to-your-organizations-apps %} {% link_in_list /adding-github-app-managers-in-your-organization %} {% link_in_list /removing-github-app-managers-from-your-organization %} - {% topic_link_in_list /managing-organization-settings %} - {% link_in_list /verifying-your-organizations-domain %} - {% link_in_list /renaming-an-organization %} {% link_in_list /transferring-organization-ownership %} {% link_in_list /restricting-repository-creation-in-your-organization %} {% link_in_list /setting-permissions-for-deleting-or-transferring-repositories %} {% link_in_list /restricting-repository-visibility-changes-in-your-organization %} {% link_in_list /managing-the-forking-policy-for-your-organization %} - {% link_in_list /disabling-or-limiting-github-actions-for-your-organization %} {% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization %} - - {% link_in_list /setting-permissions-for-adding-outside-collaborators %} - {% link_in_list /allowing-people-to-delete-issues-in-your-organization %} - - + {% link_in_list /allowing-people-to-delete-issues-in-your-organization %}{% if currentVersion == "free-pro-team@latest" %} + {% link_in_list /managing-discussion-creation-for-repositories-in-your-organization %}{% endif %} {% link_in_list /setting-team-creation-permissions-in-your-organization %} - - {% link_in_list /managing-scheduled-reminders-for-your-organization %} - - {% link_in_list /managing-the-default-branch-name-for-repositories-in-your-organization %} - - {% link_in_list /managing-default-labels-for-repositories-in-your-organization %} - - {% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %} - - {% link_in_list /managing-the-display-of-member-names-in-your-organization %} - + {% link_in_list /managing-updates-from-accounts-your-organization-sponsors %} {% link_in_list /disabling-publication-of-github-pages-sites-for-your-organization %} {% link_in_list /deleting-an-organization-account %} {% link_in_list /converting-an-organization-into-a-user %} - {% link_in_list /integrating-jira-with-your-organization-project-board %} - - {% link_in_list /upgrading-to-the-corporate-terms-of-service %} - {% topic_link_in_list /migrating-to-improved-organization-permissions %} {% link_in_list /converting-an-owners-team-to-improved-organization-permissions %} {% link_in_list /converting-an-admin-team-to-improved-organization-permissions %} {% link_in_list /migrating-admin-teams-to-improved-organization-permissions %} - {% topic_link_in_list /restricting-access-to-your-organizations-data %} {% link_in_list /about-oauth-app-access-restrictions %} {% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %} {% link_in_list /approving-oauth-apps-for-your-organization %} {% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %} - {% topic_link_in_list /keeping-your-organization-secure %} {% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %} {% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %} {% link_in_list /requiring-two-factor-authentication-in-your-organization %} - {% link_in_list /managing-security-and-analysis-settings-for-your-organization %} {% link_in_list /managing-secret-scanning-for-your-organization %} - {% link_in_list /managing-allowed-ip-addresses-for-your-organization %} - {% link_in_list /restricting-email-notifications-to-an-approved-domain %} - {% link_in_list /reviewing-the-audit-log-for-your-organization %} {% link_in_list /reviewing-your-organizations-installed-integrations %} - {% topic_link_in_list /managing-saml-single-sign-on-for-your-organization %} {% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %} {% link_in_list /about-scim %} @@ -170,17 +127,12 @@ versions: {% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %} {% link_in_list /enforcing-saml-single-sign-on-for-your-organization %} {% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %} - {% link_in_list /managing-team-synchronization-for-your-organization %} - {% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %} {% topic_link_in_list /granting-access-to-your-organization-with-saml-single-sign-on %} {% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %} {% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %} {% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %} - - {% topic_link_in_list /managing-git-access-to-your-organizations-repositories %} {% link_in_list /about-ssh-certificate-authorities %} {% link_in_list /managing-your-organizations-ssh-certificate-authorities %} - diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md new file mode 100644 index 0000000000..4bd9e0620a --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization.md @@ -0,0 +1,25 @@ +--- +title: Managing discussion creation for repositories in your organization +intro: You can choose the permission levels that members require to create discussions in repositories owned by your organization. +permissions: Organization owners can manage discussion creation for repositories owned by the organization. +versions: + free-pro-team: '*' +--- + +{% data reusables.discussions.beta %} + +### Allowing or disallowing users with read access to create discussions + +By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization. + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.member-privileges %} +5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**. ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png) +6. 单击 **Save（保存）**。 !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png) + +### 延伸阅读 + +- "[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/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md index c3ee4eb24e..7c41cc549a 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization.md @@ -9,29 +9,39 @@ versions: ### 关于安全性和分析设置的管理 {% data variables.product.prodname_dotcom %} 可帮助保护组织中的仓库。 您可以管理成员在组织中创建的所有现有或新仓库的安全性和分析功能。 - {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} +{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% endif %} - -### 启用或禁用现有仓库的功能 +### 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 %} -5. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -6. （可选）为组织中的新仓库默认启用该功能。 ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -7. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。 ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) -### 对新仓库启用或禁用功能 +The page that's displayed allows you to enable or disable security and analysis features for the repositories in your organization. + +### Enabling or disabling a feature for all existing repositories + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. 在“Configure security and analysis features（配置安全性和分析功能）”下，单击功能右侧的 **Disable all（全部禁用）**或 **Enable all（全部启用）**。 !["Configure security and analysis（配置安全性和分析）"功能的"Enable all（全部启用）"或"Disable all（全部禁用）"按钮](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) +1. （可选）为组织中的新仓库默认启用该功能。 ![新仓库的"Enable by default（默认启用）"选项](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) +1. 单击 **Disable FEATURE（禁用功能）**或 **Enable FEATURE（启用功能）**以禁用或启用组织中所有仓库的功能。 ![用于禁用或启用功能的按钮](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) + +### Enabling or disabling a feature for all new repositories when they are added + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. 在功能右侧的“Configure security and analysis features（配置安全和分析功能）”下，默认对组织中的新仓库启用或禁用该功能。 ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) + +### Allowing Dependabot to access private repositories + +{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to the targeted dependency files. By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository. For more information, including details of limitations to private dependency support, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." + +1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." +1. In the "{% data variables.product.prodname_dependabot %} repository access" section, click the settings button **{% octicon "gear" aria-label="The Gear icon" %}**. ![Repository access setting button](/assets/images/help/organizations/repository-access-cog-button.png) A list is displayed showing all of the private repositories in your organization. ![The Repositories list](/assets/images/help/organizations/repositories-dialog.png) +1. Select the repositories that {% data variables.product.prodname_dependabot %} can access. +1. Click **Select repositories**. -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. 在功能右侧的“Configure security and analysis features（配置安全和分析功能）”下，默认对组织中的新仓库启用或禁用该功能。 ![用于对新仓库启用或禁用功能的复选框](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md new file mode 100644 index 0000000000..0e42e82682 --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors.md @@ -0,0 +1,23 @@ +--- +title: Managing updates from accounts your organization sponsors +intro: You can manage the email address that receives updates from accounts your organization sponsors. +versions: + free-pro-team: '*' +permissions: Organization owners can manage updates from accounts the organization sponsors. +--- + +{% 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. 更多信息请参阅“[管理您的赞助](/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. 单击 **Update profile（更新个人资料）**。 ![更新个人资料按钮](/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)" \ No newline at end of file diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md index 71b489dbed..ba9ba67bc1 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization.md @@ -55,6 +55,9 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late | 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”） | **X** | | |{% if currentVersion == "free-pro-team@latest" %} | 管理组织依赖项洞见的显示（详细信息请参阅“[更改组织依赖项洞见的可见性](/articles/changing-the-visibility-of-your-organizations-dependency-insights)”） | **X** | | |{% endif %} | 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”） | **X** | | | +| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | | +| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | | +| Attribute your sponsorships to another organization (see "[Attributing sponsorships to your organization](/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization)" for details ) | **X** | | | | 禁止从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[为组织禁止发布 {% data variables.product.prodname_pages %} 站点](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** | | | | 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)”） | **X** | | | | 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md index 1d1b15004b..409dd31a02 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization.md @@ -114,7 +114,19 @@ versions: | [删除仓库或将仓库转让到组织外部](/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** | +| 创建到外部资源的自动链接引用，如 JIRA 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} +| 创建[安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** |{% endif %} ### 延伸阅读 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md index 1c3a69af50..fcb5bd5ba7 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization.md @@ -81,7 +81,9 @@ Each category has a set of associated actions that you can filter on. For exampl Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} -{% data reusables.search.date_gt_lt %} For example: +{% data reusables.search.date_gt_lt %} + +For example: * `created:2014-07-08` finds all events that occurred on July 8th, 2014. * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. @@ -105,25 +107,53 @@ Using the qualifier `country`, you can filter events in the audit log based on t {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -### Using the Audit log API +### 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 API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} +**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 API to keep copies of your audit log data and monitor: -* Access to your organization or repository settings. -* Changes in permissions. -* Added or removed users in an organization, repository, or team. -* Users being promoted to admin. -* Changes to permissions of a GitHub App. +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. +{% 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 as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +{% 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)" in the REST API documentation. + +{% endif %} + ### Audit log actions An overview of some of the most common actions that are recorded as events in the audit log. @@ -213,6 +243,28 @@ An overview of some of the most common actions that are recorded as events in th | `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). | `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). +{% 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. This functionality is available as a limited beta for users of {% data variables.product.prodname_ghe_cloud %} only. To join the beta, talk to your services or sales contact at {% data variables.product.company_short %}. + +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)" in the REST API documentation. + +{% endnote %} + +{% data reusables.audit_log.audit-log-git-events-retention %} + +| Action | Description +|---------|---------------------------- +| `clone` | Triggered when a repository is cloned. +| `fetch` | Triggered when changes are fetched from a repository. +| `push` | Triggered when changes are pushed to a repository. + +{% endif %} + #### `hook` category actions | Action | Description @@ -500,8 +552,20 @@ For more information, see "[Restricting publication of {% data variables.product | 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)") +| `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 organizaion](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") +| 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 %} {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md index 2a8099631b..906c318ffe 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile.md @@ -11,7 +11,7 @@ versions: github-ae: '*' --- -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}both public and{% endif %}private repositories, with specific details of your activity in private repositories anonymized. 更多信息请参阅“[在个人资料中公开或隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。 +{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}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)”。 {% note %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/index.md index b86f061e98..057c0f2993 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/index.md @@ -14,41 +14,28 @@ versions: {% topic_link_in_list /managing-user-account-settings %} {% link_in_list /about-your-personal-dashboard %} + {% link_in_list /managing-your-theme-settings %} {% link_in_list /changing-your-github-username %} - {% link_in_list /merging-multiple-user-accounts %} {% link_in_list /converting-a-user-into-an-organization %} - {% link_in_list /deleting-your-user-account %} {% link_in_list /permission-levels-for-a-user-account-repository %} {% link_in_list /permission-levels-for-user-owned-project-boards %} {% link_in_list /managing-the-default-branch-name-for-your-repositories %} {% link_in_list /managing-security-and-analysis-settings-for-your-user-account %} - {% link_in_list /managing-access-to-your-user-accounts-project-boards %} - + {% link_in_list /managing-access-to-your-user-accounts-project-boards %} {% link_in_list /integrating-jira-with-your-personal-projects %} - - {% link_in_list /best-practices-for-leaving-your-company %} - - {% link_in_list /what-does-the-available-for-hire-checkbox-do %} - {% topic_link_in_list /managing-email-preferences %} {% link_in_list /adding-an-email-address-to-your-github-account %} {% link_in_list /changing-your-primary-email-address %} {% link_in_list /setting-a-backup-email-address %} {% link_in_list /setting-your-commit-email-address %} - {% link_in_list /blocking-command-line-pushes-that-expose-your-personal-email-address %} - {% link_in_list /remembering-your-github-username-or-email %} - {% link_in_list /types-of-emails-github-sends %} - - {% link_in_list /managing-marketing-emails-from-github %} - {% topic_link_in_list /managing-access-to-your-personal-repositories %} {% link_in_list /inviting-collaborators-to-a-personal-repository %} {% link_in_list /removing-a-collaborator-from-a-personal-repository %} @@ -58,9 +45,7 @@ versions: {% link_in_list /about-organization-membership %} {% link_in_list /accessing-an-organization %} {% link_in_list /viewing-peoples-roles-in-an-organization %} - {% link_in_list /requesting-organization-approval-for-oauth-apps %} - {% link_in_list /publicizing-or-hiding-organization-membership %} {% link_in_list /managing-your-scheduled-reminders %} {% link_in_list /removing-yourself-from-an-organization %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md new file mode 100644 index 0000000000..9d0358aadc --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings.md @@ -0,0 +1,22 @@ +--- +title: Managing your theme settings +intro: You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses light mode or dark mode. +versions: + free-pro-team: '*' +--- + +{% note %} + +**Note:** Theme settings is currently in beta and subject to change. + +{% endnote %} + +For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from two themes, light and dark, or you can configure {% data variables.product.product_name %} to follow your system settings. Some developers use dark theme for personal preference, to reduce power consumption on certain devices, or to reduce eye strain in low-light conditions. + +{% data reusables.user_settings.access_settings %} +1. In the user settings sidebar, click **Appearance**. !["Apperance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +1. Under "Theme", select a theme preference. ![Radio buttons for theme settings](/assets/images/help/settings/theme-settings-radio-buttons.png) + +### 延伸阅读 + +- "[设置 {% data variables.product.prodname_desktop %} 的主题](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md b/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md index 316e412cae..22e1655cdc 100644 --- a/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md +++ b/translations/zh-CN/content/github/site-policy/github-additional-product-terms.md @@ -4,7 +4,7 @@ versions: free-pro-team: '*' --- -版本生效日期：2020 年 11 月 13 日 +Version Effective Date: December 14, 2020 创建帐户后，您有权访问许多不同的功能和产品，它们都是服务的一部分。 由于其中许多功能和产品具有不同的功能，因此可能需要特定于该功能或产品的附加条款和条件。 Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them. @@ -46,13 +46,11 @@ GitHub Pages 受某些特定带宽和使用限制的约束，可能不适用于 ### 5. Actions 和 Packages #### a. Actions 的使用 -GitHub Actions 使您能够直接在您的 GitHub 仓库中创建自定义软件开发生命周期工作流程。 Each Account comes with included compute and storage quantities for use with Actions, depending on your Account plan, which can be found in the [Actions documentation](/actions). Your Actions compute usage is displayed within [your account settings](https://github.com/settings/billing), and you will be notified by email in advance of reaching the limit of your included quantities. 如果要超出自带空间使用 Actions，您可以[启用超限](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)。 +GitHub Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. -自带和付费空间的计算用量以分钟为单位计算，具体取决于您执行的 Actions 类型（例如 Linux、Windows、macOS）。 每个 Action 的作业或任务所用的时间将取整到最接近的分钟数。 要判断自带空间是否充足，可以用倍数乘以执行每个作业或任务所用的时间量（取整之前），具体取决于 Action 的类型。 超限分钟数按[规定的每分钟价格](https://github.com/features/actions)收费，具体取决于您执行的 Actions 类型。 Actions 和 Packages 共用存储空间，您的存储空间用量显示在您的[帐户设置](https://github.com/settings/billing)中。 For additional details about included quantity usage calculations, see the [Actions documentation](/actions). - -对 Actions 和任何 Action 服务元素的使用，不得违反协议、[可接受使用政策](/github/site-policy/github-acceptable-use-policies)或 GitHub Actions [服务限制](/actions/reference/usage-limits-billing-and-administration/#usage-limits)。 此外，Actions 不得用于： +Actions and any elements of the Actions service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions). 此外，Actions 不得用于： - 密码破解; -- 使用我们的服务器破坏、非授权访问或尝试非授权访问任何服务、设备、数据、帐户或网络（[GitHub 漏洞赏金计划](https://bounty.github.com)授权的活动除外）； +- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); - 出于商业目的，提供兜售 Actions 或任何 Actions 元素的独立或集成应用程序或服务； - 任何给我们的服务器带来负担的活动，如果这种负担与提供给用户的收益不成比例（例如，不要将 Action 用作内容交付网络或作为无服务器应用程序的一部分，但收益低负担也低的 Action 可能没问题）；或 - 与使用 GitHub Actions 的仓库相关的软件项目创建、测试、部署或发布无关的任何其他活动。 @@ -60,16 +58,7 @@ GitHub Actions 使您能够直接在您的 GitHub 仓库中创建自定义软件 为防止违反这些限制和滥用 GitHub Actions，GitHub 可能会监视您对 GitHub Actions 的使用。 滥用 GitHub Actions 可能会导致作业终止，或者您使用 GitHub Actions 的权限受限。 #### b. Packages 的使用 -GitHub Packages 可用于下载、发布和管理内容包。 每个帐户计划都自带可用于 Packages 的带宽和存储空间，具体数量可查阅 [Packages 文档](/github/managing-packages-with-github-package-registry/about-github-package-registry)。 Actions 和 Packages 共用这两个服务功能之间的存储空间。 存储和带宽用量显示在您的[帐户设置](https://github.com/settings/billing)中，在达到自带空间的上限之前您会收到电子邮件通知。 如果要超出自带的带宽和存储空间使用 Packages，您可以[启用超限](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)。 - -带宽用量根据仓库中通过 Packages 传出的数据量计算，但是通过 Actions 的包传输不会计入您的自带或付费数量。 Packages bandwidth usage is limited by the [Acceptable Use Policy](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use), and included bandwidth quantities are determined by your [account plan](https://github.com/pricing). - -Actions 和 Packages 存储用量是这两个服务功能之间的共用量。 存储用量按一个月的加权平均数计算，不会每月重置。 Public and private repositories have different included storage quantities, and the included quantities for private repositories depend on your [account plan](https://github.com/pricing). - -#### c. Actions 和 Packages 的付款与计费 -Actions 和 Packages 根据用量计费。 不能单独购买额外的 Actions 或 Packages 数量。 对于按月计费的客户，必须有记录在档的付款方式才能选择支付这些服务功能的额外数量。 除非您是按发票计费的客户，否则将根据您上个月的用量每月定期向您收费。 对于发票客户，必须在 GitHub 发票日期后的三十 (30) 天内支付费用。 对于预付服务功能超限费用的客户，未使用的预付分钟数不会结转到下一个计费期，也不会退款。 - -您可以在[帐户设置](https://github.com/settings/billing/cost_management)中设置每月支出限额。 在达到自带空间上限和指定的付费额外数量支出限额之前，您会收到电子邮件通知。 +GitHub Packages is billed on a usage basis. The [Packages documentation](/packages) includes details, including bandwidth and storage quantities (depending on your Account plan), and how to monitor your Packages usage and set usage limits. Packages bandwidth usage is limited by the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies). ### 6. Learning Lab @@ -108,3 +97,13 @@ GitHub Advanced Security is licensed on a "Unique Committer" basis. A "Unique Co #### b. GitHub Advisory Database 的许可 GitHub Advisory Database 的许可采用[知识共享署名 4.0 许可](https://creativecommons.org/licenses/by/4.0/)原则。 有关署名条款，请参阅 上的 GitHub Advisory Database，或者所使用的单独 GitHub Advisory Database 记录（以 为前缀）。 + +### 13. GitHub Enterprise Server + +#### a. SQL Server Images + +You may download Microsoft SQL Server Standard Edition container image for Linux files ("SQL Server Images"). You must uninstall the SQL Server Images when your right to use the Software ends. Microsoft Corporation 可随时禁用 SQL Server 映像。 + +#### b. Third-party components + +软件包含第三方许可给 GitHub 的组件，其中包括其许可证需要 GitHub 为可用组件提供源代码的软件。 这些组件的源代码将在请求时提供。 diff --git a/translations/zh-CN/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/zh-CN/content/github/site-policy/github-enterprise-service-level-agreement.md index 1a7b518ddd..718c2cda01 100644 --- a/translations/zh-CN/content/github/site-policy/github-enterprise-service-level-agreement.md +++ b/translations/zh-CN/content/github/site-policy/github-enterprise-service-level-agreement.md @@ -8,22 +8,22 @@ versions: free-pro-team: '*' --- -**概述：**GitHub 保证 GitHub Enterprise Cloud 服务的季度正常运行时间达到 99.9%（“**服务等级**”或“**SLA**”）。 如果 GitHub 不符合 SLA，则客户将有权获得客户帐户的服务积分（“**服务积分**”）。 +**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the applicable GitHub service (the “**Service Level**” or “**SLA**”). 如果 GitHub 不符合 SLA，则客户将有权获得客户帐户的服务积分（“**服务积分**”）。 -有关每个服务功能（“**服务功能**”）的定义以及历史和当前正常运行时间的信息，请访问 [GitHub 状态页面](https://www.githubstatus.com/)。 本 SLA 中使用但未定义的大写术语采用客户适用协议中赋予的含义。 +For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). 本 SLA 中使用但未定义的大写术语采用客户适用协议中赋予的含义。 ## 正常运行时间保证 -“**正常运行时间**”是在给定的日历季度内，服务可用总分钟数的百分比。 GitHub 承诺至少保持 99.9% 的服务正常运行时间。 每个服务功能的正常运行时间计算如下所述（“**正常运行时间计算**”）。 如果 GitHub 不符合 SLA，客户将有权根据以下计算（“**服务积分计算**”）获得服务积分。 请注意，停机时间不会同时或以同样的方式影响每个客户。 +“**Uptime**” is the percentage of total possible minutes the applicable GitHub service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service. The Uptime calculation for each Service Feature that may be included with the applicable GitHub service is described below (“**Uptime Calculation**”). 如果 GitHub 不符合 SLA，客户将有权根据以下计算（“**服务积分计算**”）获得服务积分。 请注意，停机时间不会同时或以同样的方式影响每个客户。 -| **服务功能** | **正常运行时间计算** | **定义** | **服务积分计算** | -| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| **服务**包含以下服务功能：
      • 议题
      • 拉取请求
      • Git 操作
      • API 请求
      • Web 挂钩
      • 页面
      • 操作
      • 包
      | （日历季度的总分钟数 - 停机时间）/日历季度的总分钟数 | “**停机时间**”是指发生以下任一情况的时间段 (a) 在给定分钟内任何服务功能的错误率超过百分之五 (5%)；或 (b) 经 GitHub 的内部和外部监控系统组合确定，服务不可用。 | 服务积分索赔可能基于以下计算方法中的一种（而非两种）：
      • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than or equal to 99.9%, but greater than 99.0%.

        或

      • 如果在一个日历季度内，服务功能的正常运行时间低于 99.0%，则结果为客户为该服务功能所支付金额的 25%。
      | | -| **操作** | （总触发执行数 - 不可用执行数）/（总触发执行数）x 100 | “**总触发执行数**”是客户在一个日历季度内触发的所有操作的执行总数。

      “**不可用执行数**”是指在一个日历季度内，总触发执行数中未能运行的执行总数。 在触发器被成功触发五 (5) 分钟后，如果操作历史记录日志未捕获任何输出，则执行失败。 | 同上 | -| **包** | 传输正常运行时间 = 同“操作”

      存储正常运行时间 = 100% - 平均错误率*

      *正常运行时间计算不包括不计入总存储事务或失败存储事务的公共使用和存储事务（包括预身份验证失败；身份验证失败；存储帐户的尝试事务超过其指定配额）。 | “**错误率**”是在设定的时间间隔（当前设置为一小时）内，失败的存储事务总数除以总存储事务数。 如果在给定的一小时间隔内总存储事务数为零，则该间隔的错误率为 0％。

      “**平均错误率**”是日历季度内每个小时的错误率之和除以日历季度的总小时数。 | 同上 | +| **服务功能** | **正常运行时间计算** | **定义** | **服务积分计算** | +| -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | +| **Issues**,
      **Pull Requests**,
      **Git Operations**,
      **API Requests**,
      **Webhooks**,
      **Pages** | （日历季度的总分钟数 - 停机时间）/日历季度的总分钟数 | “**停机时间**”是指发生以下任一情况的时间段 (a) 在给定分钟内任何服务功能的错误率超过百分之五 (5%)；或 (b) 经 GitHub 的内部和外部监控系统组合确定，服务不可用。 | 服务积分索赔可能基于以下计算方法中的一种（而非两种）：
      • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than or equal to 99.9%, but greater than 99.0%.

        或

      • 如果在一个日历季度内，服务功能的正常运行时间低于 99.0%，则结果为客户为该服务功能所支付金额的 25%。
      | | +| **操作** | （总触发执行数 - 不可用执行数）/（总触发执行数）x 100 | “**总触发执行数**”是客户在一个日历季度内触发的所有操作的执行总数。

      “**不可用执行数**”是指在一个日历季度内，总触发执行数中未能运行的执行总数。 在触发器被成功触发五 (5) 分钟后，如果操作历史记录日志未捕获任何输出，则执行失败。 | 同上 | +| **包** | 传输正常运行时间 = 同“操作”

      存储正常运行时间 = 100% - 平均错误率*

      *正常运行时间计算不包括不计入总存储事务或失败存储事务的公共使用和存储事务（包括预身份验证失败；身份验证失败；存储帐户的尝试事务超过其指定配额）。 | “**错误率**”是在设定的时间间隔（当前设置为一小时）内，失败的存储事务总数除以总存储事务数。 如果在给定的一小时间隔内总存储事务数为零，则该间隔的错误率为 0％。

      “**平均错误率**”是日历季度内每个小时的错误率之和除以日历季度的总小时数。 | 同上 | ## 排除 -正常运行时间计算不包括因以下原因导致的服务功能故障：(i) 客户的行为、疏忽或滥用服务，包括违反协议；(ii) 客户的网络连接故障；(iii) 超出 GitHub 合理控制范围的因素，包括不可抗力事件；或 (iv) 客户的设备、服务或其他技术。 +Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the applicable GitHub service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. ## 服务积分兑换 如果 GitHub 不符合此 SLA，则客户必须在该日历季度结束后的三十 (30) 天内向 GitHub 提出书面申请才能兑换服务积分。 Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact). diff --git a/translations/zh-CN/content/github/site-policy/github-registered-developer-agreement.md b/translations/zh-CN/content/github/site-policy/github-registered-developer-agreement.md index 15c1a461f9..12fb2225c8 100644 --- a/translations/zh-CN/content/github/site-policy/github-registered-developer-agreement.md +++ b/translations/zh-CN/content/github/site-policy/github-registered-developer-agreement.md @@ -86,7 +86,7 @@ GitHub 很荣幸看到众多开发者融入我们的平台。 我们受宠若惊 13. **专有权利** - 您同意，GitHub 及其许可人拥有以下内容的所有权利、所有权和权益：API、预发布材料以及所有其他 GitHub 产品和服务；有关其配置和组合的所有信息和数据；以及对上述任何内容的所有修改和派生作品。 您同意，不得删除、更改、覆盖或混淆我们在 API、预发布材料或任何其他 GitHub 产品和服务上放置或嵌入的任何版权或其他专有权声明。 + 您同意，GitHub 及其许可人拥有以下内容的所有权利、所有权和权益：API、预发布材料以及所有其他 GitHub 产品和服务；有关其配置和组合的所有信息和数据；以及对上述任何内容的所有修改和派生作品。 You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services. 14. **政府用户** 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 4638b7ce34..52e15a6e1d 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 @@ -9,7 +9,9 @@ versions: ### 关于 {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.sponsorship-details %} {% data reusables.sponsors.no-fees %} 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %} 的计费](/articles/about-billing-for-github-sponsors)”。 +{% data reusables.sponsors.sponsorship-details %} + +{% data reusables.sponsors.no-fees %} 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %} 的计费](/articles/about-billing-for-github-sponsors)”。 {% data reusables.sponsors.you-can-be-a-sponsored-developer %} 更多信息请参阅“[关于开源贡献者的 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)”和“[为用户帐户设置 {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)”。 @@ -21,11 +23,11 @@ versions: {% note %} -**注：**{% data reusables.sponsors.matching-fund-eligible %} +**Note:** {% data reusables.sponsors.matching-fund-eligible %} {% endnote %} -{% data variables.product.prodname_matching_fund %} 旨在使 {% data variables.product.prodname_dotcom %} 社区开发开源软件的成员获益，宣传 [{% data variables.product.prodname_dotcom %} 社区指导方针](/github/site-policy/github-community-guidelines)。 被赞助组织没有资格获得 {% data variables.product.prodname_matching_fund %}。 +{% data variables.product.prodname_matching_fund %} 旨在使 {% data variables.product.prodname_dotcom %} 社区开发开源软件的成员获益，宣传 [{% data variables.product.prodname_dotcom %} 社区指导方针](/github/site-policy/github-community-guidelines)。 Payments to sponsored organizations and payments from organizations are not eligible for {% data variables.product.prodname_matching_fund %}. 若要符合 {% data variables.product.prodname_matching_fund %} 的资格，您必须创建吸引社区长期维持您发展的个人资料。 有关创建有吸引力的个人资料的更多信息，请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)”。 @@ -35,8 +37,6 @@ versions: 这只是开始 - 我们欢迎大家提供意见，确保 {% data variables.product.prodname_sponsors %} 满足您未来的需求。 请联系 [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors)，向我们发送您的反馈或建议。 -目前只有个人用户可以赞助开发者和组织。 如果您的组织有兴趣赞助开发者，请联系 [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors)。 - ### 延伸阅读 - "[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" - "[通过 {% data variables.product.prodname_sponsors %} 接受赞助](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)" diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md new file mode 100644 index 0000000000..57b1b5a4d6 --- /dev/null +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization.md @@ -0,0 +1,13 @@ +--- +title: Attributing sponsorships to your organization +intro: 'You can attribute the sponsorships paid by one of your organizations to another organization.' +versions: + free-pro-team: '*' +permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization. +--- + +1. Navigate to the organization whose sponsorships you want to attribute to another organization. +1. Under your organization name, click {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**. !["Sponsoring" tab](/assets/images/help/sponsors/sponsoring-tab.png) +1. In the upper-right corner, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" button](/assets/images/help/sponsors/sponsoring-settings-button.png) +1. Under "Link sponsorships to another account", use the drop-down menu, then click the organization you want this organization's sponsorships to be attributed to. ![Drop-down menu to select account](/assets/images/help/sponsors/select-an-account-drop-down.png) +1. Click **Link account**. !["Link account" button](/assets/images/help/sponsors/link-account-button.png) \ No newline at end of file diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md index bbe04958b6..12392039c0 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers.md @@ -13,38 +13,20 @@ versions: {% data reusables.sponsors.maximum-tier %} -### 为被赞助开发者配置文件添加层级 +### 添加等级 -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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-org-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-dev-sponsors-dashboard %} +{% 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 %} - -### 编辑或取消被赞助组织配置文件的层级 - -{% data reusables.sponsors.navigate-to-org-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 %} +{% data reusables.sponsors.retire-tier %} \ No newline at end of file diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md index d949f4b438..5aa3adde70 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md @@ -5,11 +5,13 @@ versions: free-pro-team: '*' --- -要监视赞助变更，例如在付款期结束时取消，您可以为被赞助的用户或组织帐户创建 web 挂钩。 为被赞助的用户或组织帐户创建 web 挂钩后，在创建、编辑或删除赞助时您将会收到更新消息。 更多信息请参阅 [`sponsorship` web 挂钩事件](/webhooks/event-payloads/#sponsorship)。 +### About webhooks for events in your sponsored account -### 管理被赞助用户帐户的 web 挂钩 +要监视赞助变更，例如在付款期结束时取消，您可以为被赞助的用户或组织帐户创建 web 挂钩。 When you set up a webhook for your sponsored account, you'll receive updates when sponsorships are created, edited, or deleted. 更多信息请参阅 [`sponsorship` web 挂钩事件](/webhooks/event-payloads/#sponsorship)。 -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +### Managing webhooks for events in your sponsored account + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-webhooks-tab %} {% data reusables.sponsors.add-webhook %} {% data reusables.sponsors.add-payload-url %} @@ -17,18 +19,4 @@ versions: {% data reusables.sponsors.webhook-secret-token %} {% data reusables.sponsors.add-active-triggers %} {% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} - -### 管理被赞助组织的 web 挂钩 - -组织所有者可以为被赞助组织配置 web 挂钩。 - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-webhooks-tab %} -{% data reusables.sponsors.add-webhook %} -{% data reusables.sponsors.add-payload-url %} -{% data reusables.sponsors.webhook-content-formatting %} -{% data reusables.sponsors.webhook-secret-token %} -{% data reusables.sponsors.add-active-triggers %} -{% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} +{% data reusables.sponsors.manage-existing-webhooks %} \ No newline at end of file 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 9d3c641d55..dd150b65ed 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors.md @@ -7,22 +7,15 @@ versions: free-pro-team: '*' --- +### About sponsorship updates + 您的赞助者可选择是否接收有关您工作更新的电子邮件。 更多信息请参阅“[管理您的赞助](/articles/managing-your-sponsorship)”。 -更新邮件将从用户帐户的主电子邮件地址或组织帐户的 `noreply@github.com` 电子邮件地址发出。 如果您对用户帐户启用了电子邮件地址保密，则更新邮件将从 `noreply@github.com` 发出。 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。 +For sponsored developer accounts, the update will come from your user account's primary email address. 如果您对用户帐户启用了电子邮件地址保密，则更新邮件将从 `noreply@github.com` 发出。 For sponsored organizations, the update will come from the organization's `noreply@github.com` email address. 更多信息请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。 -### 联系您的用户帐户的赞助者 +### 联系赞助者 -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.sponsors-updates-tab %} -{% data reusables.sponsors.draft-new-update %} -{% data reusables.sponsors.send-update-to-sponsors %} -{% data reusables.sponsors.write-sponsor-update %} -{% data reusables.sponsors.publish-sponsor-update %} - -### 联系您的组织的赞助者 - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.sponsors-updates-tab %} {% data reusables.sponsors.draft-new-update %} {% data reusables.sponsors.send-update-to-sponsors %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md index d49a907552..bec0740f5b 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors.md @@ -10,30 +10,17 @@ versions: ### 关于赞助者个人资料 -您的 {% data variables.product.prodname_sponsors %} 个人资料会告诉潜在的赞助者，他们为什么应该支持您。 人们点击您的个人资料或组织资料上的 **Sponsor（赞助）** 按钮，就会看到您的赞助个人资料。 我们建议个人资料中包括以下信息。 +您的 {% data variables.product.prodname_sponsors %} 个人资料会告诉潜在的赞助者，他们为什么应该支持您。 People see your sponsor profile when they click the **Sponsor** button on your profile. 我们建议个人资料中包括以下信息。 -- 您参与的开源工作。 -- 您为什么致力于开源开发。 +- Open source work that you contribute to +- Why you are committed to open source development -您还可以设定目标来解释不同的赞助级别允许您为社区做些什么。 +### Editing your profile details -### 编辑您的被赞助的开发者个人资料 - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### 编辑被赞助组织资料 - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.meet-the-team %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} +{% data reusables.sponsors.save-profile %} \ No newline at end of file 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 10838749ac..4f7261d474 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 @@ -16,6 +16,7 @@ versions: {% topic_link_in_list /sponsoring-open-source-contributors %} {% link_in_list /sponsoring-an-open-source-contributor %} {% link_in_list /managing-your-sponsorship %} + {% link_in_list /attributing-sponsorships-to-your-organization %} {% topic_link_in_list /receiving-sponsorships-through-github-sponsors %} {% link_in_list /about-github-sponsors-for-open-source-contributors %} {% link_in_list /setting-up-github-sponsors-for-your-user-account %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md index 217ebf4c09..1ed66eadaf 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors.md @@ -13,14 +13,8 @@ versions: {% data reusables.sponsors.payout-info %} -### 查看和编辑赞助用户帐户的付款信息 +### Viewing and editing payout information -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} - -### 查看和编辑赞助组织的付款信息 - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} +{% data reusables.sponsors.edit-bank-information %} \ No newline at end of file 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 055ad3c280..58aa3533f6 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal.md @@ -1,27 +1,19 @@ --- title: 管理您的赞助目标 -intro: 您可以为被赞助开发者或被赞助组织配置文件设置目标，以帮助社区了解赞助您的影响。 +intro: You can set a goal for your sponsored developer or sponsored organization account to help the community understand the impact of sponsoring you. versions: free-pro-team: '*' --- ### 关于赞助目标 -您可以为被赞助开发者或组织配置文件设置一个融资目标，并与您的社区共享该目标。 目标可帮助您了解您在开源社区中的影响，并扩大您在 {% data variables.product.prodname_sponsors %} 计划中的影响力。 +You can set a funding goal for your sponsored account and share the goal with your community. 目标可帮助您了解您在开源社区中的影响，并扩大您在 {% data variables.product.prodname_sponsors %} 计划中的影响力。 您的目标可设为您想要的赞助者数量或您希望每月赚取的金额。 每次只能设置一个目标。 一个目标达成后，可以设置另一个目标。 -### 为被赞助组织设置目标 +### Setting a goal -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.set-a-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### 为被赞助开发者设置目标 - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.set-a-goal %} {% data reusables.sponsors.select-goal-type %} @@ -31,6 +23,7 @@ versions: 编辑目标时，无法选择已实现的目标。 例如，如果您已经有 5 个赞助者，您无法将目标编辑为针对 4 个赞助者。 +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.select-goal-type %} @@ -40,6 +33,7 @@ versions: 取消的目标无法重新激活， 而必须创建新目标。 +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.retire-goal %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md index 6343cb48b3..4ab3b130a1 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship.md @@ -1,42 +1,35 @@ --- title: 管理赞助 -intro: 您可以管理谁能看到您的赞助，以及您是否要从赞助的开源贡献者接收电子邮件更新。 +intro: You can manage who can see your sponsorship and whether you receive email updates from the sponsored account. redirect_from: - /articles/managing-your-sponsorship versions: free-pro-team: '*' --- -有关更改赞助的信息，请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”。 +{% data reusables.sponsors.org-sponsors-release-phase %} -### 管理开发者赞助的隐私设置 +### 管理赞助的隐私设置 -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} {% data reusables.sponsors.who-can-see-your-sponsorship %} {% data reusables.sponsors.update-sponsorship %} -### 管理组织赞助的隐私设置 +### Managing email updates for your sponsorship -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.who-can-see-your-sponsorship %} +You can choose whether an account you sponsor can send you email updates about their work. The sponsored account will not have access to your email address. + +{% data reusables.sponsors.manage-updates-for-orgs %} + +{% data reusables.sponsors.navigate-to-sponsored-account %} +{% data reusables.sponsors.sponsorship-dashboard %} +{% data reusables.sponsors.manage-sponsorship %} +{% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.update-sponsorship %} -### 管理被赞助开发者的电子邮件更新 +### 延伸阅读 -您可以选择被赞助开发者能否以电子邮件向您发送其工作的更新。 被赞助开发者无法访问您的电子邮件地址。 - -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} -{% data reusables.sponsors.developer-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} - -### 管理被赞助组织的电子邮件更新 - -您可以选择被赞助组织能否以电子邮件向您发送其工作的更新。 被赞助组织无法访问您的电子邮件地址。 - -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.org-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} +- "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" +- "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)" \ No newline at end of file diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/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 e1cfbcec83..18ecfc6b9a 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 @@ -25,7 +25,7 @@ versions: ### 填写被赞助组织资料 -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ versions: {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% 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 %} @@ -54,7 +54,7 @@ versions: {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} 有关使用 Open Collective 设置 Stripe Connect 的更多信息，请参阅 Open Collective 文档中的[设置 {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors)。 @@ -63,7 +63,7 @@ versions: {% data reusables.sponsors.tax-form-information-org %} -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -75,7 +75,7 @@ versions: ### 向 {% data variables.product.prodname_dotcom %} 提交申请以请求批准 -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %} {% data reusables.sponsors.github-review-app %} 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 09c1271145..79f7ddb100 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 @@ -26,7 +26,7 @@ versions: 在 {% data variables.product.prodname_dotcom %} 审核您的申请后，您可以设置您的被赞助开发者个人资料，以便人们可以开始赞助您。 -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} @@ -40,7 +40,7 @@ versions: {% data reusables.sponsors.maximum-tier %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% 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 %} @@ -54,14 +54,14 @@ versions: {% data reusables.sponsors.double-check-stripe-info %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %} ### 提交您的税务信息 {% data reusables.sponsors.tax-form-information-dev %} -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %} {% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} @@ -73,7 +73,7 @@ versions: ### 向 {% data variables.product.prodname_dotcom %} 提交申请以请求批准 -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 4. 单击 **Request approval（请求批准）**。 ![请求批准按钮](/assets/images/help/sponsors/request-approval-button.png) {% data reusables.sponsors.github-review-app %} 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 16552a350f..4521f3c7ef 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md @@ -7,17 +7,32 @@ redirect_from: - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer versions: free-pro-team: '*' +permissions: Anyone can sponsor accounts on behalf of their own user account. Organization owners and billing managers can sponsor accounts on behalf of their organization. --- -### 关于赞助开发者和组织 +{% data reusables.sponsors.org-sponsors-release-phase %} -{% data reusables.sponsors.sponsorship-details %} {% data reusables.sponsors.no-fees %} 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %} 的计费](/articles/about-billing-for-github-sponsors)”。 +### About sponsorships -当您赞助开源贡献者后，更改将立即生效。 {% data reusables.sponsors.prorated-sponsorship %} +{% data reusables.sponsors.sponsorship-details %} -如果您赞助的开源贡献者退出您的等级，则您仍保留在该等级，直到您选择其他等级或取消订阅。 更多信息请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”。 +You can sponsor an account on behalf of your user account to invest in projects that you personally benefit from. You can sponsor an account on behalf of your organization for many reasons. +- Sustaining specific libraries that your organization's work depends on +- Investing in the ecosystem you rely on as a organization (such as blockchain) +- Developing brand awareness as an organization that values open source +- Thanking open source developers for building libraries that complement the product your organization offers -如果您想要赞助的开源贡献者没有被赞助开发者或组织资料，您可以鼓励该贡献者创建被赞助开发者或组织资料。 For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data variables.product.prodname_dotcom %} will send you the appropriate forms, notify you when they are due, and give you a reasonable amount of time to complete and send in the forms. +You can use a credit card to sponsor an account on {% data variables.product.product_name %}. If your organization wants to be invoiced, [contact us](https://support.github.com/contact/org-sponsors-waitlist). + +{% data reusables.sponsors.no-fees %} 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %} 的计费](/articles/about-billing-for-github-sponsors)”。 + +When you sponsor an account using a credit card, the change will become effective immediately. {% data reusables.sponsors.prorated-sponsorship %} + +{% data reusables.sponsors.manage-updates-for-orgs %} + +If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. 更多信息请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”。 + +If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data variables.product.prodname_dotcom %} will send you the appropriate forms, notify you when they are due, and give you a reasonable amount of time to complete and send in the forms. {% data reusables.sponsors.sponsorships-not-tax-deductible %} @@ -27,30 +42,20 @@ versions: {% endnote %} -### 赞助开发者 +### Sponsoring an account -在赞助开发者之前，您必须拥有经过验证的电子邮件地址。 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)”。 +Before you can sponsor an account, you must have a verified email address. 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)”。 -1. 在 {% data variables.product.product_name %} 上，导航到您要赞助的人员的个人资料。 -2. 在开发者的姓名下方，单击 **Sponsor（赞助）**。 ![赞助按钮](/assets/images/help/profile/sponsor-button.png) +1. On {% data variables.product.product_name %}, navigate to the profile of the user or organization you want to sponsor. +1. Navigate to your sponsorship dashboard for the account. + - To sponsor a developer, under the developer's name, click **Sponsor**. ![赞助按钮](/assets/images/help/profile/sponsor-button.png) + - To sponsor an organization, to the right of the the organization's name, click **Sponsor**. ![赞助按钮](/assets/images/help/sponsors/sponsor-org-button.png) +1. Optionally, on the right side of the page, to sponsor the account on behalf of your organization, use the **Sponsor as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you'll sponsor as](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) {% data reusables.sponsors.select-a-tier %} +{% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} ![编辑付款按钮](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) {% data reusables.sponsors.who-can-see-your-sponsorship %} ![用于选择谁可以查看您的赞助的单选按钮](/assets/images/help/sponsors/who-can-see-sponsorship.png) -{% data reusables.sponsors.developer-sponsored-choose-updates %} -7. 单击 **Sponsor _DEVELOPER_（赞助 *DEVELOPER*）**。 ![赞助开发者按钮](/assets/images/help/sponsors/sponsor-developer-button.png) - -### 赞助组织 - -在赞助组织之前，您必须拥有经过验证的电子邮件地址。 更多信息请参阅“[验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)”。 - -1. 在 {% data variables.product.product_name %} 上，导航到您要赞助的组织的页面。 -2. 在组织名称旁边，单击 **Sponsor（赞助）**。 ![赞助按钮](/assets/images/help/sponsors/sponsor-org-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.select-sponsorship-billing %} - ![编辑付款按钮](/assets/images/help/sponsors/edit-org-sponsorship-payment-button.png) -{% data reusables.sponsors.who-can-see-your-sponsorship %} - ![用于选择谁可以查看您的赞助的单选按钮](/assets/images/help/sponsors/who-can-see-org-sponsorship.png) -{% data reusables.sponsors.org-sponsored-choose-updates %} -7. 单击 **Sponsor _ORGANIZATION_（赞助组织）**。 ![赞助组织按钮](/assets/images/help/sponsors/sponsor-org-confirm-button.png) +{% data reusables.sponsors.choose-updates %} +{% data reusables.sponsors.sponsor-account %} diff --git a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md index 96b4cfa5e1..659890d902 100644 --- a/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ b/translations/zh-CN/content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md @@ -7,34 +7,25 @@ versions: free-pro-team: '*' --- +### About sponsors and sponsorships + 您可以查看有关您当前和过去的赞助、从赞助者收到的付款以及事件（例如赞助取消和赞助等级变更）的分析。 您还可以查看新的赞助、赞助变更和赞助取消等活动。 您可以按日期过滤活动列表。 您还可以导出帐户的赞助数据以 CSV 或 JSON 格式查看。 -您可以从赞助者仪表板获取所有这些信息。 - -### 查看赞助者仪表板 - -1. 在任何页面的右上角，单击您的个人资料照片，然后单击 **{% data variables.product.prodname_sponsors %}**。 ![{% data variables.product.prodname_sponsors %} 按钮](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. 在显示的列表中，在要查看其赞助者的帐户或组织的右侧，单击 **Dashboard（仪表板）**。 ![开发者赞助者仪表板按钮](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) - ### 查看您的赞助者和赞助 -1. 转到您的赞助者仪表板，参阅[查看您的赞助者仪表板](#viewing-your-sponsors-dashboard)。 -{% data reusables.sponsors.navigate-to-sponsors-tab %} +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. （可选）要按等级过滤赞助者，请使用 **Filter（过滤）**下拉菜单，单击 **Active tiers（活动等级）**或 **Retired tiers（已撤销等级）**，然后选择一个等级。 ![按等级过滤的下拉菜单](/assets/images/help/sponsors/filter-drop-down.png) ### 查看最近的赞助活动 -1. 转到您的赞助者仪表板，参阅[查看您的赞助者仪表板](#viewing-your-sponsors-dashboard)。 +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} 1. 在左侧边栏中，单击 **Activity（活动）**。 ![活动选项卡](/assets/images/help/sponsors/activity-tab.png) ### 导出赞助数据 -1. 转到您的赞助者仪表板，参阅[查看您的赞助者仪表板](#viewing-your-sponsors-dashboard)。 +If you have sponsors, you can export your sponsorship data. {% data variables.product.prodname_dotcom %} will send you an email with export data for all of your sponsors for the month you select. After the export is complete, you can export another month of data. You can export up to 10 sets of data per hour for any of your sponsored accounts. + +{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsors-tab %} 1. 单击 **Export all（全部导出）**。 ![全部导出按钮](/assets/images/help/sponsors/export-all.png) - - 如果您没有任何赞助者，此按钮将不显示。 - -1. 选择您想导出的数据的时间范围和格式，然后单击 **Start export（开始导出）**。 ![数据导出选项](/assets/images/help/sponsors/export-your-sponsors.png) - - {% data variables.product.prodname_dotcom %} 开始导出您选择的月份的所有赞助者的数据。 您很快就会收到一封电子邮件，其附件中包含这些数据。 导出完成后，您可以导出另一个月的数据。 您可以为您赞助的任何组织或用户帐户每小时导出多达 10 组数据。 +1. 选择您想导出的数据的时间范围和格式，然后单击 **Start export（开始导出）**。 ![数据导出选项](/assets/images/help/sponsors/export-your-sponsors.png) \ No newline at end of file diff --git a/translations/zh-CN/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/zh-CN/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 87783c72f4..7d1da8c393 100644 --- a/translations/zh-CN/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/zh-CN/content/github/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -36,7 +36,7 @@ versions: {% endwindows %} - `BRANCH-NAME`: The default branch for your current project, for example, `main` or `gh-pages`. ```shell - $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME + $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME # Filter the specified branch in your directory and remove empty commits > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) > Ref 'refs/heads/BRANCH-NAME' was rewritten 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 ee6e10f5bc..1a66878f1a 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 @@ -21,6 +21,10 @@ 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)." +{% 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: @@ -41,7 +45,8 @@ 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. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +- 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 diff --git a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/index.md b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/index.md index d09d04e748..a81e01db5e 100644 --- a/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/index.md +++ b/translations/zh-CN/content/github/visualizing-repository-data-with-graphs/index.md @@ -18,16 +18,12 @@ versions: {% link_in_list /about-repository-graphs %} {% link_in_list /viewing-a-summary-of-repository-activity %} {% link_in_list /viewing-a-projects-contributors %} - {% link_in_list /viewing-traffic-to-a-repository %} - {% topic_link_in_list /analyzing-changes-to-a-repositorys-content %} {% link_in_list /visualizing-commits-in-a-repository %} {% link_in_list /visualizing-additions-and-deletions-to-content-in-a-repository %} {% topic_link_in_list /understanding-connections-between-repositories %} {% link_in_list /viewing-a-repositorys-network %} {% link_in_list /listing-the-forks-of-a-repository %} - {% link_in_list /about-the-dependency-graph %} {% link_in_list /exploring-the-dependencies-of-a-repository %} - diff --git a/translations/zh-CN/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md index dce597fe73..9505554e5f 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md +++ b/translations/zh-CN/content/github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll.md @@ -51,7 +51,7 @@ Jekyll 站点中内容的主要类型是页面和帖子。 页面是指与某个 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: page + layout: post title: "POST TITLE" date: YYYY-MM-DD hh:mm:ss -0000 categories: CATEGORY-1 CATEGORY-2 diff --git a/translations/zh-CN/content/github/working-with-github-pages/index.md b/translations/zh-CN/content/github/working-with-github-pages/index.md index cd7e1cb677..cab57a854a 100644 --- a/translations/zh-CN/content/github/working-with-github-pages/index.md +++ b/translations/zh-CN/content/github/working-with-github-pages/index.md @@ -23,15 +23,11 @@ versions: {% topic_link_in_list /getting-started-with-github-pages %} {% link_in_list /about-github-pages %} {% link_in_list /creating-a-github-pages-site %} - {% link_in_list /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser %} - {% link_in_list /configuring-a-publishing-source-for-your-github-pages-site %} {% link_in_list /creating-a-custom-404-page-for-your-github-pages-site %} - {% link_in_list /securing-your-github-pages-site-with-https %} {% link_in_list /using-submodules-with-github-pages %} - {% link_in_list /unpublishing-a-github-pages-site %} {% topic_link_in_list /setting-up-a-github-pages-site-with-jekyll %} {% link_in_list /about-github-pages-and-jekyll %} @@ -42,9 +38,7 @@ versions: {% link_in_list /adding-a-theme-to-your-github-pages-site-using-jekyll %} {% link_in_list /about-jekyll-build-errors-for-github-pages-sites %} {% link_in_list /troubleshooting-jekyll-build-errors-for-github-pages-sites %} - {% topic_link_in_list /configuring-a-custom-domain-for-your-github-pages-site %} {% link_in_list /about-custom-domains-and-github-pages %} {% link_in_list /managing-a-custom-domain-for-your-github-pages-site %} {% link_in_list /troubleshooting-custom-domains-and-github-pages %} - diff --git a/translations/zh-CN/content/github/working-with-github-support/index.md b/translations/zh-CN/content/github/working-with-github-support/index.md index d832ade781..77d2c2293c 100644 --- a/translations/zh-CN/content/github/working-with-github-support/index.md +++ b/translations/zh-CN/content/github/working-with-github-support/index.md @@ -2,6 +2,7 @@ title: 使用 GitHub 支持 redirect_from: - /categories/working-with-github-support + - /forum versions: free-pro-team: '*' --- diff --git a/translations/zh-CN/content/graphql/README.md b/translations/zh-CN/content/graphql/README.md new file mode 100644 index 0000000000..78de2871d2 --- /dev/null +++ b/translations/zh-CN/content/graphql/README.md @@ -0,0 +1,10 @@ +# GraphQL + +`/content/graphql` 目录是 GitHub GraphQL API 文档所在的位置！ + +* `/content/graphql/guide` and `/content/graphql/overview` 目录中包含可以编辑的项目。 +* `/content/graphql/references` 目录对 GitHub GraphQL API 中使用的每个GraphQL 数据类型包含一个项目。 此目录中的大多数内容都使用 `include` 呈现。 + + `include` 标记呈现的内容来自 `/lib/graphql/static` 目录，由 GitHub 内部的 API 源代码自动生成，不应人工编辑。 更多信息请参阅 [`/lib/graphql/README.md`](/lib/graphql/README.md)。 + + **因此，我们不能接受参与此仓库中的 GraphQL API 参考内容。** diff --git a/translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md index e9305fbb73..7df359aa0d 100644 --- a/translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md +++ b/translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md @@ -14,12 +14,12 @@ versions: 从 REST 迁移到 GraphQL 代表了 API 逻辑的一次重大转变。 作为样式的 REST 与作为规范的 GraphQL 之间的差异使得很难—且通常不可取—以一对一方式将 REST API 调用替换为 GraphQL API 查询。 我们在下面提供了具体的迁移示例。 -To migrate your code from the [REST API](/rest) to the GraphQL API: +要将代码从 [REST API](/rest) 迁移到 GraphQL API： - 查看 [GraphQL 规范](https://graphql.github.io/graphql-spec/June2018/) -- Review GitHub's [GraphQL schema](/graphql/reference) +- 查看 GitHub 的 [GraphQL 架构](/graphql/reference) - 考虑您当前的现有代码如何与 GitHub REST API 交互 -- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions +- 使用[全局节点 ID](/graphql/guides/using-global-node-ids) 引用 API 版本之间的对象 GraphQL 的重要优势包括： @@ -53,12 +53,12 @@ query { } ``` -考虑另一个示例：检索拉取请求列表并检查每个请求是否可合并。 A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations): +考虑另一个示例：检索拉取请求列表并检查每个请求是否可合并。 对 REST API 的调用可检索拉取请求列表及其[摘要陈述](/rest#summary-representations)： ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls ``` -Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false: +确定拉取请求是否可合并需要分别检索每个拉取请求，查看其[详细陈述](/rest#detailed-representations)（大型有效负载），并检查它的 `mergeable` 属性是真还是假： ```shell curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number ``` @@ -128,13 +128,13 @@ curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:numbe } ``` -You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number. +您也可以通过[用变量替换](/graphql/guides/forming-calls-with-graphql#working-with-variables)拉取请求编号扩大此查询的能力。 ## 示例：强类型化 GraphQL 架构属于强类型化架构，可使数据处理更加安全。 -Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment): +考虑一个利用 GraphQL [突变](/graphql/reference/mutations)向议题或拉取请求添加注释，并错误地将 [`clientMutationId`](/graphql/reference/mutations#addcomment) 值指定为整数而非字符串的示例： ```graphql mutation { diff --git a/translations/zh-CN/content/graphql/guides/using-global-node-ids.md b/translations/zh-CN/content/graphql/guides/using-global-node-ids.md index f62c178e2c..bdb37f46af 100644 --- a/translations/zh-CN/content/graphql/guides/using-global-node-ids.md +++ b/translations/zh-CN/content/graphql/guides/using-global-node-ids.md @@ -13,7 +13,7 @@ versions: {% note %} -**注：**在 REST 中，全局节点 ID 字段被命名为 `node_id`。 在 GraphQL 中，此字段为 `node` 接口上的 `id` 字段。 For a refresher on what "node" means in GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql#node)." +**注：**在 REST 中，全局节点 ID 字段被命名为 `node_id`。 在 GraphQL 中，此字段为 `node` 接口上的 `id` 字段。 若要重温“节点”在 GraphQL 中的含义，请参阅“[GraphQL 简介](/graphql/guides/introduction-to-graphql#node)。” {% endnote %} @@ -29,7 +29,7 @@ versions: ### 1. 调用可返回对象节点 ID 的 REST 端点 -If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user): +如果您[请求经过身份验证的用户](/rest/reference/users#get-the-authenticated-user)： ```shell $ curl -i -u username:token {% data variables.product.api_url_pre %}/user @@ -101,7 +101,7 @@ query { 此查询类型—即按 ID 查找节点—被称为“直接节点查找。” -When you run this query, you'll see that the `__typename` is [`User`](/graphql/reference/objects#user). +当您运行此查询时，将发现 `__typename` 为 [`User`](/graphql/reference/objects#user)。 ### 3. 在 GraphQL 中执行直接节点查找 @@ -122,4 +122,4 @@ query { ### 在迁移中使用全局节点 ID -构建使用 REST API 或 GraphQL API 的集成时，最佳做法是保留全局节点 ID，以便轻松引用不同 API 版本的对象。 For more information on handling the transition between REST and GraphQL, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." +构建使用 REST API 或 GraphQL API 的集成时，最佳做法是保留全局节点 ID，以便轻松引用不同 API 版本的对象。 有关处理 REST 与 GraphQL 之间的转换的更多信息，请参阅“[从 REST 迁移到 GraphQL](/graphql/guides/migrating-from-rest-to-graphql)。” diff --git a/translations/zh-CN/content/graphql/overview/explorer.md b/translations/zh-CN/content/graphql/overview/explorer.md index 59c1bfaa4a..74540b78a4 100644 --- a/translations/zh-CN/content/graphql/overview/explorer.md +++ b/translations/zh-CN/content/graphql/overview/explorer.md @@ -7,6 +7,6 @@ versions: free-pro-team: '*' enterprise-server: '*' github-ae: '*' +layout: graphql-explorer --- -您可以转到 https://developer.github.com/v4/explorer 访问 GitHub 的 GraphQL Explorer。 diff --git a/translations/zh-CN/content/graphql/overview/resource-limitations.md b/translations/zh-CN/content/graphql/overview/resource-limitations.md index 8351e51eff..6c0fafa512 100644 --- a/translations/zh-CN/content/graphql/overview/resource-limitations.md +++ b/translations/zh-CN/content/graphql/overview/resource-limitations.md @@ -11,11 +11,11 @@ versions: ## 节点限制 -To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 [calls](/graphql/guides/forming-calls-with-graphql) must meet these standards: +要通过[架构](/graphql/guides/introduction-to-graphql#schema)验证，所有 GraphQL API v4 [调用](/graphql/guides/forming-calls-with-graphql)都必须满足这些标准： -* Clients must supply a `first` or `last` argument on any [connection](/graphql/guides/introduction-to-graphql#connection). +* 客户端必须提供任何[连接](/graphql/guides/introduction-to-graphql#connection)上的 `first` 或 `last` 参数。 * `first` 和 `last` 的值必须在 1 至 100 之间。 -* Individual calls cannot request more than 500,000 total [nodes](/graphql/guides/introduction-to-graphql#node). +* 单个调用请求的[节点](/graphql/guides/introduction-to-graphql#node)总数不能超过 500,000。 #### 计算调用中的节点 @@ -121,7 +121,7 @@ To pass [schema](/graphql/guides/introduction-to-graphql#schema) validation, all GraphQL API v4 限制不同于 REST API v3 的 [速率限制](/rest/overview/resources-in-the-rest-api#rate-limiting)。 -API 速率限制为什么不同？ With [GraphQL](/graphql), one GraphQL call can replace [multiple REST calls](/graphql/guides/migrating-from-rest-to-graphql). 单个复杂 GraphQL 调用可能相当于数千个 REST 请求。 虽然单个 GraphQL 调用远远低于 REST API v3 速率限制，但对 GitHub 的服务器来说，查询的计算成本可能同样高昂。 +API 速率限制为什么不同？ 使用 [GraphQL](/graphql)，一个 GraphQL 调用可替换[多个 REST 调用](/graphql/guides/migrating-from-rest-to-graphql)。 单个复杂 GraphQL 调用可能相当于数千个 REST 请求。 虽然单个 GraphQL 调用远远低于 REST API v3 速率限制，但对 GitHub 的服务器来说，查询的计算成本可能同样高昂。 要准确表示查询的服务器成本，GraphQL API v4 可根据标准分数量表计算调用的 **rate limit score（速率限制分数）**。 查询分数计入了父连接及其子连接上的第一个和最后一个参数。 diff --git a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md index c10ee1f002..76ac03cc7b 100644 --- a/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md +++ b/translations/zh-CN/content/insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise.md @@ -1,6 +1,6 @@ --- title: 启用 GitHub Insights 与 GitHub Enterprise 之间的链接 -intro: 'You can enable a link that will allow users to navigate from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_insights %}.' +intro: '您可以启用一个允许用户从 {% data variables.product.prodname_ghe_server %} 导航到 {% data variables.product.prodname_insights %} 的链接。' product: '{% data reusables.gated-features.github-insights %}' permissions: '{% data variables.product.prodname_ghe_server %} 的站点管理员可启用 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_insights %} 之间的链接。' redirect_from: diff --git a/translations/zh-CN/content/packages/guides/about-github-container-registry.md b/translations/zh-CN/content/packages/guides/about-github-container-registry.md new file mode 100644 index 0000000000..da47f0287b --- /dev/null +++ b/translations/zh-CN/content/packages/guides/about-github-container-registry.md @@ -0,0 +1,94 @@ +--- +title: 关于 GitHub Container Registration +intro: '您可以使用 {% data variables.product.prodname_github_container_registry %} 在 {% data variables.product.prodname_dotcom %} 上的组织或个人用户帐户中无缝托管和管理 Docker 容器映像。 {% data variables.product.prodname_github_container_registry %} 允许您配置谁可以使用细粒度权限管理和访问包。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/about-github-container-registry + - /packages/managing-container-images-with-github-container-registry +versions: + free-pro-team: '*' +--- + +{% note %} + +**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 要使用 {% data variables.product.prodname_github_container_registry %}，您必须为您的帐户启用该功能。 更多信息请参阅“[启用改进的容器支持](/packages/guides/enabling-improved-container-support)”。 + +{% endnote %} + +### 关于 {% data variables.product.prodname_github_container_registry %} + +{% data reusables.package_registry.container-registry-feature-highlights %} + +要共享有关包使用的上下文，可以将仓库链接到 {% data variables.product.prodname_dotcom %} 上的容器映像。 更多信息请参阅“[将仓库连接到容器映像](/packages/guides/connecting-a-repository-to-a-container-image)”。 + +{% data variables.product.prodname_github_container_registry %} 与其他包注册表具有不同的托管位置、权限和可见性。 + +| | 包注册表 | {% data variables.product.prodname_github_container_registry %} +| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | +| 托管位置 | 您可以在一个仓库中托管多个包。 | 您可以在一个组织或用户帐户中托管多个容器映像。 | +| 权限 | {% data reusables.package_registry.public-or-private-packages %} 您可以使用 {% data variables.product.prodname_dotcom %} 角色和团队来限制谁可以安装或发布每个包，因为包会继承仓库的权限。 对仓库有读取权限的任何人都可以将包安装为项目中的依赖项，有写入权限的任何人都可以发布新的包版本。 | 对于每个容器映像，您可以选择其他人具有的访问权限级别。 容器映像访问的权限与组织和仓库权限不同。 | + 可见性 | {% data reusables.package_registry.public-or-private-packages %} | 您可以设置每个容器映像的可见性。 私有容器映像仅对组织内被授予访问权限的人员或团队可见。 公共容器映像对任何人都可见。 | 匿名访问 | N/A| 您可以匿名访问公共容器映像。 + +更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %} 的范围和权限](#about-scopes-and-permissions-for-github-container-registry)”。 + +### 支持的格式 + +{% data variables.product.prodname_container_registry %} 目前支持以下容器映像格式： + +* [Docker 映像清单 V2，架构 2](https://docs.docker.com/registry/spec/manifest-v2-2/) +* [Open Container Initiative (OCI) 规格](https://github.com/opencontainers/image-spec) + +{% data variables.product.prodname_github_container_registry %} 在 `ghcr.io/OWNER/IMAGE-NAME` 托管容器。 + +| 包客户端 | 语言 | 包格式 | 描述 | +| ------ | --- | ------------ | ------ | +| docker | 不适用 | `Dockerfile` | 节点包管理器 | + + +#### 清单列表/映像索引 + +{% data variables.product.prodname_github_container_registry %} 也支持 Docker V2、Schema 2 和 OCI 映像规格中定义的 [Docker 清单列表](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI 映像索引](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md)格式。 + +### 容器映像的可见性和访问权限 + +如果您对容器映像具有管理员权限，可以将容器映像设置为私有或公有。 公有映像允许匿名访问，无需身份验证或通过 CLI 登录即可进行拉取。 + +作为管理员，您还可以授予容器映像的访问权限，该权限与在组织和仓库级别设置的权限不同。 + +对于由用户帐户发布和拥有的容器映像，您可以向任何人授予访问角色。 对于组织发布和拥有的容器映像，您可以为组织中的任何人或团队授予访问角色。 + +| 权限角色 | 访问描述 | +| ---- | ------------------------------------------------------------ | +| 读取 | 可以下载包。
      可以读取包元数据。 | +| 写入 | 可以上传和下载此包。
      可以读取和写入包元数据。 | +| 管理员 | 可以上传、下载、删除和管理此包。
      可以读取和写入包元数据。
      可以授予包权限。 | + +更多信息请参阅“[配置容器映像的访问控制和可见性](/packages/guides/configuring-access-control-and-visibility-for-container-images)”。 + +### 关于令牌 + +要安装或发布包，您必须使用具有适当作用域的令牌，并且您的用户帐户必须对该仓库具有适当的权限。 + +| 作用域 | 描述 | +| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| `read:packages` | 从 {% data variables.product.prodname_github_container_registry %} 下载和安装容器映像 | +| `write:packages` | 上传和发布容器映像到 {% data variables.product.prodname_github_container_registry %} +| `delete:packages` | 从 {% data variables.product.prodname_github_container_registry %} 删除私有或公共容器映像的特定版本。 更多信息请参阅“[删除容器映像](/packages/guides/deleting-a-container-image)”。 | + +要了解容器映像的可用范围和权限，请参阅“[配置容器映像的访问控制和可见性](/packages/guides/configuring-access-control-and-visibility-for-container-images)”。 + +更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token/)”和“[可用作用域](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)”。 + +### 关于 {% data variables.product.prodname_github_container_registry %} 的计费 + +{% data reusables.package_registry.billing-for-container-registry %} + +### 联系支持 + +如果您对 {% data variables.product.prodname_github_container_registry %} 有反馈或功能请求，请使用[反馈表](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages)。 + +如果在 {% data variables.product.prodname_github_container_registry %} 方面遇到以下问题，请使用[我们的联系表](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages)联系 {% data variables.contact.github_support %}： + +* 遇到任何与文档相矛盾的事情. +* 遇到模糊或不清楚的错误. +* 发布的包中含有敏感数据，例如违反 GDPR、API 密钥或个人身份信息. diff --git a/translations/zh-CN/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md b/translations/zh-CN/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md new file mode 100644 index 0000000000..dc1fc9d84f --- /dev/null +++ b/translations/zh-CN/content/packages/guides/configuring-access-control-and-visibility-for-container-images.md @@ -0,0 +1,69 @@ +--- +title: 配置容器映像的访问控制和可见性 +intro: '选择谁对容器映像具有读取、写入或管理员访问权限，以及容器映像在 {% data variables.product.prodname_dotcom %} 上的可见性。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### 为个人帐户配置对容器映像的访问 + +如果您对用户帐户拥有的容器映像具有管理员权限，您可以向其他用户分配读取、写入或管理员角色。 有关这些权限角色的更多信息，请参阅“[容器映像的可见性和访问权限](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)”。 + +{% data reusables.package_registry.package-settings-from-user-level %} +1. 在软件包设置页面上，单击 **Invite teams or people（邀请团队或人员）**，然后输入名称、用户名或您想要授予访问权限的人员的电子邮件地址。 不能授予团队访问用户帐户拥有的容器映像。 ![容器访问邀请按钮](/assets/images/help/package-registry/container-access-invite.png) +1. 在用户名或团队名称旁边，使用“Role（角色）”下拉菜单选择所需的权限级别。 ![容器访问选项](/assets/images/help/package-registry/container-access-control-options.png) + +所选用户将自动被授予访问权限，不需要先接受邀请。 + +### 为企业配置对容器映像的访问 + +如果您对组织拥有的容器映像具有管理员权限，您可以向其他用户和团队分配读取、写入或管理员角色。 有关这些权限角色的更多信息，请参阅“[容器映像的可见性和访问权限](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)”。 + +如果您的软件包由组织和私人拥有，则您只能向其他组织成员或团队授予访问。 + +对于组织映像容器，组织管理员必须先启用包，然后才能将可见性设置为公共。 更多信息请参阅“[启用改进的容器支持](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)”。 + +{% data reusables.package_registry.package-settings-from-org-level %} +1. 在软件包设置页面上，单击 **Invite teams or people（邀请团队或人员）**，然后输入名称、用户名或您想要授予访问权限的人员的电子邮件地址。 您还可以从组织输入团队名称，以允许所有团队成员访问。 ![容器访问邀请按钮](/assets/images/help/package-registry/container-access-invite.png) +1. 在用户名或团队名称旁边，使用“Role（角色）”下拉菜单选择所需的权限级别。 ![容器访问选项](/assets/images/help/package-registry/container-access-control-options.png) + +所选用户或团队将自动被授予访问权限，不需要先接受邀请。 + +### 为个人帐户配置容器映像的可见性 + +首次发布包时，默认可见性是私有的，只有您才能看到包。 您可以通过更改访问设置来修改私有或公共容器映像的访问权限。 + +公共包可以匿名访问，无需身份验证。 包一旦被设为公共，便无法再次将其设为私有。 + +{% data reusables.package_registry.package-settings-from-user-level %} +5. 在“Danger Zone（危险区域）”下，选择可见性设置： + - 要使容器映像对任何人都可见，请单击“**Make public（设为公共）**”。 + {% warning %} + + **警告：**包一旦被设为公共，便无法再次将其设为私有。 + + {% endwarning %} + - 要使容器映像只对选择的人员可见，请单击“**Make private（设为私有）**”。 ![容器可见性选项](/assets/images/help/package-registry/container-visibility-option.png) + +### 为组织配置容器映像的可见性 + +首次发布包时，默认可见性是私有的，只有您才能看到包。 您可以通过访问设置授予用户或团队对容器映像的不同访问角色。 + +公共包可以匿名访问，无需身份验证。 包一旦被设为公共，便无法再次将其设为私有。 + +对于组织映像容器，组织管理员必须先启用公共包，然后才能将可见性设置为公共。 更多信息请参阅“[启用改进的容器支持](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)”。 + +{% data reusables.package_registry.package-settings-from-org-level %} +5. 在“Danger Zone（危险区域）”下，选择可见性设置： + - 要使容器映像对任何人都可见，请单击“**Make public（设为公共）**”。 + {% warning %} + + **警告：**包一旦被设为公共，便无法再次将其设为私有。 + + {% endwarning %} + - 要使容器映像只对选择的人员可见，请单击“**Make private（设为私有）**”。 ![容器可见性选项](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/zh-CN/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md new file mode 100644 index 0000000000..a4b907c82f --- /dev/null +++ b/translations/zh-CN/content/packages/guides/configuring-apache-maven-for-use-with-github-packages.md @@ -0,0 +1,195 @@ +--- +title: 配置 Apache Maven 用于 GitHub 包 +intro: '您可以配置 Apache Maven 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 Java 项目中的依赖项。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。 + +### 向 {% data variables.product.prodname_registry %} 验证 + +{% data reusables.package_registry.authenticate-packages %} + +#### 使用个人访问令牌进行身份验证 + +{% data reusables.package_registry.required-scopes %} + +通过编辑 *~/.m2/settings.xml* 文件以包含个人访问令牌，您可以使用 Apache Maven 向 {% data variables.product.prodname_registry %} 验证。 如果 *~/.m2/settings.xml* 文件不存在，请新建该文件。 + +在 `servers` 标记中，添加带 `id` 的子 `server` 标记，将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌。 + +在 `repositories` 标记中，通过将仓库的 `id` 映射到您在包含凭据的 `server` 标记中添加的 `id` 来配置仓库。 将 {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名称，{% endif %}将 *REPOSITORY* 替换为您要向其发布包或从中安装包的仓库的名称，并将 *OWNER* 替换为拥有仓库的用户或组织帐户的名称。 由于不支持大写字母，因此，即使您的 {% data variables.product.prodname_dotcom %} 用户或组织名称中包含大写字母，也必须对仓库所有者使用小写字母。 + +如果要与多个仓库交互，您可以将每个仓库添加到 `repository` 标记中独立的子 `repositories`，将每个仓库的 `id` 映射到 `servers` 标记中的凭据。 + +{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} + +{% if enterpriseServerVersions contains currentVersion %} +有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 +{% endif %} + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + +``` + + + + github + + + + + github + + + central + https://repo1.maven.org/maven2 + true + true + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + + + + + + github + USERNAME + TOKEN + + + +``` +{% endif %} + +#### 使用 `GITHUB_TOKEN` 进行身份验证 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### 发布包 + +{% data reusables.package_registry.default-name %} 例如，{% data variables.product.prodname_dotcom %} 将名为 `com.example:test` 的包发布到名为 `OWNER/test` 的仓库中。 + +如果要将多个包发布到同一个仓库，您可以在 `pom.xml` 文件的 `` 元素中包含该仓库的 URL。 {% data variables.product.prodname_dotcom %} 将根据该字段匹配仓库。 由于仓库名称也是 `distributionManagement` 元素的一部分，因此将多个包发布到同一个仓库无需额外步骤、 + +有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 + +1. 编辑包目录中 *pom.xml* 文件的 `distributionManagement` 元素，将 `OWNER` 替换为拥有该仓库的用户或组织帐户的名称，将 `REPOSITORY` 替换为包含项目的仓库的名称。 + +{% if enterpriseServerVersions contains currentVersion %}将 *HOSTNAME* 替换为您的 {% data variables.product.prodname_ghe_server %} 实例的主机名称， {% endif %}将 `OWNER` 替换为拥有仓库的用户或组织帐户的名称，并将 `REPOSITORY` 替换为包含您项目的仓库的名称。 + {% if enterpriseServerVersions contains currentVersion %} + 有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 + {% endif %} + ``` + + + github + GitHub OWNER Apache Maven Packages + https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY + + + ``` + {% if enterpriseServerVersions contains currentVersion %} + 例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + ``` + + + github + GitHub OWNER Apache Maven Packages + https://HOSTNAME/_registry/maven/OWNER/REPOSITORY + + + ``` + {% endif %} +2. 发布包。 + + ```shell + $ mvn deploy + ``` + +{% data reusables.package_registry.viewing-packages %} + +### 安装包 + +要从 {% data variables.product.prodname_registry %} 安装 Apache Maven 包，请编辑 *pom.xml* 文件以包含该包作为依赖项。 如果要从多个仓库安装包，请为每个仓库添加 `repository` 标记。 有关在项目中使用 *pom.xml* 文件的更多信息，请参阅 Apache Maven 文档中的“[POM 简介](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)”。 + +{% data reusables.package_registry.authenticate-step %} +2. 将包依赖项添加到项目 *pom.xml* 文件的 `dependencies` 元素，将 `com.example:test` 替换为您的包。 + + ``` + + + com.example + test + 1.0.0-SNAPSHOT + + + ``` +3. 安装包。 + + ```shell + $ mvn install + ``` + +### 延伸阅读 + +- "[配置 Gradle 用于 {% data variables.product.prodname_registry %}](/packages/guides/configuring-gradle-for-use-with-github-packages)" +- “[删除包](/packages/manage-packages/deleting-a-package/)” diff --git a/translations/zh-CN/content/packages/guides/configuring-docker-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-docker-for-use-with-github-packages.md new file mode 100644 index 0000000000..798453372e --- /dev/null +++ b/translations/zh-CN/content/packages/guides/configuring-docker-for-use-with-github-packages.md @@ -0,0 +1,213 @@ +--- +title: 配置 Docker 用于 GitHub 包 +intro: '您可以配置 Docker 客户端以使用 {% data variables.product.prodname_registry %} 发布和检索 docker 镜像。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。 + +### 向 {% data variables.product.prodname_registry %} 验证 + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +您可以使用 `docker` 登录命令，通过 Docker 向 {% data variables.product.prodname_registry %} 验证。 + +{% if enterpriseServerVersions contains currentVersion %} + +必须在 {% data variables.product.product_location %} 的网站管理员为您的实例启用 Docker 支持和子域隔离后，您才可在 {% data variables.product.prodname_registry %} 上使用 Docker 注册表。 更多信息请参阅“[为企业管理 GitHub Packages](/enterprise/admin/packages)”。 + +{% endif %} + +### 向 {% data variables.product.prodname_registry %} 验证 + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% data reusables.package_registry.authenticate-packages %} + +#### 使用个人访问令牌进行身份验证 + +{% data reusables.package_registry.required-scopes %} + +您可以使用 `docker` 登录命令，通过 Docker 向 {% data variables.product.prodname_registry %} 验证。 + +为确保凭据安全，我们建议您将个人访问令牌保存在您计算机上的本地文件中，然后使用 Docker 的 `--password-stdin` 标志从本地文件读取您的令牌。 + +{% if currentVersion == "free-pro-team@latest" %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + ``` +{% endraw %} +{% endif %} + +{% if enterpriseServerVersions contains currentVersion %} +{% raw %} + ```shell + $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin +``` +{% endraw %} +{% endif %} + +要使用此示例登录命令，请将 `USERNAME` 替换为您的 {% data variables.product.product_name %} 用户名{% if enterpriseServerVersions contains currentVersion %}，将 `HOSTNAME` 替换为 {% data variables.product.product_location %},{% endif %} 的 URL，并将 `~/TOKEN.txt` 替换为您用于 {% data variables.product.product_name %} 的个人访问令牌的文件路径。 + +更多信息请参阅“[Docker 登录](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)”。 + +#### 使用 `GITHUB_TOKEN` 进行身份验证 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### 发布映像 + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +{% note %} + +**注：**映像名称只能使用小写字母。 + +{% endnote %} + +{% data variables.product.prodname_registry %} 支持每个仓库的多个顶层 Docker 镜像。 仓库可以拥有任意数量的映像标记。 在发布或安装大于 10GB 的 Docker 映像（每个图层上限为 5GB）时，可能会遇到服务降级的情况。 更多信息请参阅 Docker 文档中的“[Docker 标记](https://docs.docker.com/engine/reference/commandline/tag/)”。 + +{% data reusables.package_registry.viewing-packages %} + +1. 使用 `docker images` 确定 docker 映像的名称和 ID。 + ```shell + $ docker images + > < > + > REPOSITORY TAG IMAGE ID CREATED SIZE + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + ``` +2. 使用 Docker 映像 ID 标记 docker 映像，将 *OWNER* 替换为拥有仓库的用户或组织帐户的名称，将 *REPOSITORY* 替换为包含项目的仓库的名称，将 *IMAGE_NAME* 替换为包或映像的名称，将 *VERSION* 替换为构建时的包版本。 +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* 使用 {% data variables.product.product_location %} 的主机名，{% endif %}而 *VERSION* 使用构建时的软件包版本。 + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + 如果尚未为包构建 docker 映像，请构建映像，将 OWNER 替换为拥有仓库的用户或组织帐户的名称，将 REPOSITORY 替换为包含项目的仓库的名称，将 IMAGE_NAME 替换为包或映像的名称，将 VERSION 替换为构建时的包版本，将 PATH 替换为映像路径（如果映像未在当前工作目录中）。 + ``` + {% endif %} +3. 您可能首次发布新的 Docker 映像并将其命名为 `monalisa`。 +{% if enterpriseServerVersions contains currentVersion %} *HOSTNAME* 使用 {% data variables.product.product_location %} 的主机名，{% endif %}以及映像的 *PATH*（如果不在当前工作目录中）。 + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% else %} + ```shell + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + ``` + {% endif %} +4. 将映像发布到 +{% data variables.product.prodname_registry %}. + {% if currentVersion == "free-pro-team@latest" %} + ```shell + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% else %} + ```shell + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + {% endif %} + {% note %} + + **注：**必须使用 `IMAGE_NAME:VERSION` 推送映像，而不能使用 `IMAGE_NAME:SHA`。 + + {% endnote %} + +#### 发布 Docker 映像的示例 + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +您可以使用映像 ID 将 `monalisa` 映像的 1.0 版本发布到 `octocat/octo-app` 仓库。 + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} + +```shell +$ docker images + +> REPOSITORY TAG IMAGE ID CREATED SIZE +> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB + +# Tag the image with OWNER/REPO/IMAGE_NAME +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` + +{% endif %} + +您可能首次发布新的 Docker 映像并将其命名为 `monalisa`。 + +{% if currentVersion == "free-pro-team@latest" %} +```shell +# Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 +``` + +{% else %} +```shell +# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION +# Assumes Dockerfile resides in the current working directory (.) +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . + +# Push the image to {% data variables.product.prodname_registry %} +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +``` +{% endif %} + +### 下载映像 + +{% data reusables.package_registry.docker_registry_deprecation_status %} + +您可以使用 `docker pull` 命令从 {% data variables.product.prodname_registry %} 安装 Docker 映像，将 *OWNER* 替换为拥有仓库的用户或组织帐户的名称，将 *REPOSITORY* 替换为包含项目的仓库的名称，将 *IMAGE_NAME* 替换为包或映像的名称，{% if enterpriseServerVersions contains currentVersion %}将 *HOSTNAME* 替换为您 {% data variables.product.prodname_ghe_server %} 实例的主机名称，{% endif %}并将 *TAG_NAME* 替换为要安装的映像的标记。 + +{% if currentVersion == "free-pro-team@latest" %} +```shell +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% else %} +```shell +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +``` +{% endif %} + +{% note %} + +**注：**必须使用 `IMAGE_NAME:VERSION` 推送映像，而不能使用 `IMAGE_NAME:SHA`。 + +{% endnote %} + +### 延伸阅读 + +- “[删除包](/packages/publishing-and-managing-packages/deleting-a-package/)” diff --git a/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md new file mode 100644 index 0000000000..0c3df3fcd3 --- /dev/null +++ b/translations/zh-CN/content/packages/guides/configuring-dotnet-cli-for-use-with-github-packages.md @@ -0,0 +1,197 @@ +--- +title: 配置 `dotnet` CLI 用于 GitHub 包 +intro: '您可以配置 `dotnet` 命令行接口 (CLI) 以将 NuGet 包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 .NET 项目中的依赖项。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages + - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。 + +### 向 {% data variables.product.prodname_registry %} 验证 + +{% data reusables.package_registry.authenticate-packages %} + +#### 使用个人访问令牌进行身份验证 + +{% data reusables.package_registry.required-scopes %} + +要使用 `dotnet` 命令行接口 (CLI) 向 {% data variables.product.prodname_registry %} 验证，请在项目目录中创建一个 *nuget.config* 文件，将 {% data variables.product.prodname_registry %} 指定为 `dotnet` CLI 客户端的 `packageSources` 下的源。 + +必须： +- 将 `USERNAME` 替换为您在 {% data variables.product.prodname_dotcom %} 上的用户帐户的名称。 +- 将 `TOKEN` 替换为您的个人访问令牌。 +- 将 `OWNER` 替换为拥有项目所在仓库的用户或组织帐户的名称。{% if enterpriseServerVersions contains currentVersion %} +- 拥有 {% data variables.product.prodname_ghe_server %} 实例主机名称的 `HOSTNAME`。 + +有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 +{% endif %} + +```xml + + + + + + + + + + + + + +``` + +{% if enterpriseServerVersions contains currentVersion %} +例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + +```xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://github.com/octo-org/octo-cats-and-dogs + + + +``` +{% endif %} + +#### 使用 `GITHUB_TOKEN` 进行身份验证 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### 发布包 + +您可以使用 *nuget.config* 文件进行身份验证，将包发布到 {% data variables.product.prodname_registry %}。 发布时，您需要将 *csproj* 文件中的 `OWNER` 值用于您的 *nuget.config* 身份验证文件。 在 *.csproj* 文件中指定或增加版本号，然后使用 `dotnet pack` 命令创建该版本的 *.nuspec* 文件。 有关创建包的更多信息，请参阅 Microsoft 文档中的“[创建和发布包](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)”。 + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. 创建一个新项目。 + ```shell + dotnet new console --name OctocatApp + ``` +3. 将项目的特定信息添加到以 *.csproj* 结尾的项目文件中。 必须： + - 将 `OWNER` 替换为拥有项目所在仓库的用户或组织帐户的名称。 + - 将 `REPOSITORY` 替换为要发布的包所在仓库的名称。 + - 将 `1.0.0` 替换为包的版本号。{% if enterpriseServerVersions contains currentVersion %} + - 拥有 {% data variables.product.prodname_ghe_server %} 实例主机名称的 `HOSTNAME`。{% endif %} + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + ``` +4. 打包项目。 + ```shell + dotnet pack --configuration Release + ``` + +5. 使用您在 *nuget.config* 文件中指定的 `key` 发布包。 + ```shell + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" + ``` + +### 将多个包发布到同一个仓库 + +要将多个包发布到同一个仓库，您可以在所有 *.csproj* 项目文件的 `RepositoryURL` 字段中包含相同的 {% data variables.product.prodname_dotcom %} 仓库 URL。 {% data variables.product.prodname_dotcom %} 根据该字段匹配仓库。 + +例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + +``` xml + + + + Exe + netcoreapp3.0 + OctodogApp + 1.0.0 + Octodog + GitHub + This package adds an Octodog! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs + + + +``` + +### 安装包 + +在项目中使用来自 {% data variables.product.prodname_dotcom %} 的包类似于使用来自 *nuget.org* 的包。 将包依赖项添加到 *.csproj* 文件以指定包名称和版本。 有关在项目中使用 *.csproj* 文件的更多信息，请参阅 Microsoft 文档中的“[使用 NuGet 包](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)”。 + +{% data reusables.package_registry.authenticate-step %} + +2. 要使用包，请添加 `ItemGroup` 并配置 *.csproj* 项目文件中的 `PackageReference` 字段，将 `OctokittenApp` 包替换为您的包依赖项，将 `1.0.0` 替换为您要使用的版本： + ``` xml + + + + Exe + netcoreapp3.0 + OctocatApp + 1.0.0 + Octocat + GitHub + This package adds an Octocat! + https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY + + + + + + + + ``` + +3. 使用 `restore` 命令安装包。 + ```shell + dotnet restore + ``` + +### 延伸阅读 + +- “[删除包](/packages/publishing-and-managing-packages/deleting-a-package/)” diff --git a/translations/zh-CN/content/packages/guides/configuring-gradle-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-gradle-for-use-with-github-packages.md new file mode 100644 index 0000000000..31bf25df6f --- /dev/null +++ b/translations/zh-CN/content/packages/guides/configuring-gradle-for-use-with-github-packages.md @@ -0,0 +1,215 @@ +--- +title: 配置 Gradle 用于 GitHub 包 +intro: '您可以配置 Gradle 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 Java 项目中的依赖项。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。 + +### 向 {% data variables.product.prodname_registry %} 验证 + +{% data reusables.package_registry.authenticate-packages %} + +#### 使用个人访问令牌进行身份验证 + +{% data reusables.package_registry.required-scopes %} + +您可以使用 Gradle Groovy 或 Kotlin DSL，通过 Gradle 向 {% data variables.product.prodname_registry %} 验证，方法是编辑 *build.gradle* 文件 (Gradle Groovy) 或 *build.gradle.kts* 文件 (Kotlin DSL) 以包含您的个人访问令牌。 您还可以配置 Gradle Groovy 和 Kotlin DSL 以识别仓库中的一个或多个包。 + +{% if enterpriseServerVersions contains currentVersion %} +将 *REGISTRY-URL* 替换为您实例的 Maven 注册表的 URL。 如果您的实例启用了子域隔离，请使用 `maven.HOSTNAME`。 如果您的实例禁用了子域隔离，请使用 `HOSTNAME/_registry/maven`。 无论是哪种情况，都要将 *HOSTNAME* 替换为 +{% data variables.product.prodname_ghe_server %} 实例的主机名。 +{% endif %} + +将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌，将 *REPOSITORY* 替换为要发布的包所在仓库的名称，将 *OWNER* 替换为 {% data variables.product.prodname_dotcom %} 上拥有该仓库的用户或组织帐户的名称。 由于不支持大写字母，因此，即使您的 {% data variables.product.prodname_dotcom %} 用户或组织名称中包含大写字母，也必须对仓库所有者使用小写字母。 + +{% note %} + +**注：**{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} 关于示例，请参阅“[配置 Apache Maven 用于 {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)”。 + +{% endnote %} + +##### 将 Gradle Groovy 用于一个仓库中单个包的示例 + +```shell +plugins { + id("maven-publish") +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } +} +``` + +##### 将 Gradle Groovy 用于同一个仓库中多个包的示例 + +```shell +plugins { + id("maven-publish") apply false +} + +subprojects { + apply plugin: "maven-publish" + publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + } + } + } + publications { + gpr(MavenPublication) { + from(components.java) + } + } + } +} +``` + +##### 将 Kotlin DSL 用于同一个仓库中单个包的示例 + +```shell +plugins { + `maven-publish` +} + +publishing { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } +} +``` + +##### 将 Kotlin DSL 用于同一个仓库中多个包的示例 + +```shell +plugins { + `maven-publish` apply false +} + +subprojects { + apply(plugin = "maven-publish") + configure { + repositories { + maven { + name = "GitHubPackages" + url = uri("https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + credentials { + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + } + } + } + publications { + register("gpr") { + from(components["java"]) + } + } + } +} +``` + + #### 使用 `GITHUB_TOKEN` 进行身份验证 + + {% data reusables.package_registry.package-registry-with-github-tokens %} + + 有关将 `GITHUB_TOKEN` 用于 Maven 的更多信息，请参阅“[使用 Maven 发布 Java 包](/actions/language-and-framework-guides/publishing-java-packages-with-maven#publishing-packages-to-github-packages)”。 + + ### 发布包 + + {% data reusables.package_registry.default-name %} 例如，{% data variables.product.prodname_dotcom %} 将名为 `com.example.test` 的包发布到 `OWNER/test` {% data variables.product.prodname_registry %} 仓库中。 + + {% data reusables.package_registry.viewing-packages %} + + {% data reusables.package_registry.authenticate-step %} + 2. 创建包后，您可以发布包。 + + ```shell + $ gradle publish + ``` + +### 安装包 + +通过添加包作为您项目中的依赖项，您可以安装包。 更多信息请参阅 Gradle 文档中的“[声明依赖项](https://docs.gradle.org/current/userguide/declaring_dependencies.html)”。 + +{% data reusables.package_registry.authenticate-step %} +2. 将包依赖项添加到您的 *build.gradle* 文件 (Gradle Groovy) 或 *build.gradle.kts* 文件 (Kotlin DSL)。 + + 使用 Gradle Groovy 的示例： + ```shell + dependencies { + implementation 'com.example:package' + } + ``` + 使用 Kotlin DSL 的示例： + ```shell + dependencies { + implementation("com.example:package") + } + ``` + +3. 将 maven 插件添加到您的 *build.gradle* 文件 (Gradle Groovy) 或 *build.gradle.kts* 文件 (Kotlin DSL)。 + + 使用 Gradle Groovy 的示例： + ```shell + plugins { + id 'maven' + } + ``` + 使用 Kotlin DSL 的示例： + ```shell + plugins { + `maven` + } + ``` + + 3. 安装包。 + + ```shell + $ gradle install + ``` + +### 延伸阅读 + +- "[配置 Apache Maven 用于 {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)" +- “[删除包](/packages/publishing-and-managing-packages/deleting-a-package/)” diff --git a/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md b/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md new file mode 100644 index 0000000000..105d242f90 --- /dev/null +++ b/translations/zh-CN/content/packages/guides/configuring-npm-for-use-with-github-packages.md @@ -0,0 +1,203 @@ +--- +title: 配置 npm 用于 GitHub 包 +intro: '您可以配置 npm 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 npm 项目中的依赖项。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +**注：**安装或发布 Docker 映像时，{% data variables.product.prodname_registry %} 当前不支持外部图层，如 Windows 映像。 + +### 向 {% data variables.product.prodname_registry %} 验证 + +{% data reusables.package_registry.authenticate-packages %} + +#### 使用个人访问令牌进行身份验证 + +{% data reusables.package_registry.required-scopes %} + +通过编辑您的每用户 *~/.npmrc* 文件以包含个人访问令牌，或者在命令行上使用用户名和个人访问令牌登录 npm，您可以使用 npm 向 {% data variables.product.prodname_registry %} 验证。 + +要通过将个人访问令牌添加到 *~/.npmrc* 文件进行身份验证，请编辑项目的 *~/.npmrc* 文件以包含以下行，将{% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名，并{% endif %}将 *TOKEN* 替换为您的个人访问令牌。 如果 *~/.npmrc* 文件不存在，请新建该文件。 + +{% if enterpriseServerVersions contains currentVersion %} +有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 +{% endif %} + +```shell +//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN +``` + +{% if enterpriseServerVersions contains currentVersion %} +例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + +```shell +$ npm login --registry=https://npm.pkg.github.com +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +要通过登录到 npm 进行身份验证，请使用 `npm login` 命令，将 *USERNAME* 替换为您的 {% data variables.product.prodname_dotcom %} 用户名，将 *TOKEN* 替换为您的个人访问令牌，将 *PUBLIC-EMAIL-ADDRESS* 替换为您的电子邮件地址。 + +如果 {% data variables.product.prodname_registry %} 不是使用 npm 的默认包注册表，并且您要使用 `npm audit` 命令，我们建议您在对 {% data variables.product.prodname_registry %} 进行身份验证时，将 `--scope` 标志与包的所有者一起使用。 + +{% if enterpriseServerVersions contains currentVersion %} +有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 +{% endif %} + +```shell +$ npm login --scope=@OWNER --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} + +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` + +{% if enterpriseServerVersions contains currentVersion %} +例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + +```shell +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS +``` +{% endif %} + +#### 使用 `GITHUB_TOKEN` 进行身份验证 + +{% data reusables.package_registry.package-registry-with-github-tokens %} + +### 发布包 + +{% note %} + +**注：**包名称和作用域只能使用小写字母。 + +{% endnote %} + +默认情况下，{% data variables.product.prodname_registry %} 将包发布到您在 *package.json* 文件的名称字段中指定的 {% data variables.product.prodname_dotcom %} 仓库。 例如，您要发布一个名为 `@my-org/test` 的包到 `my-org/test` {% data variables.product.prodname_dotcom %} 仓库。 通过在包目录中包含 *README.md* 文件，您可以添加包列表页面的摘要。 更多信息请参阅 npm 文档中的“[使用 package.json](https://docs.npmjs.com/getting-started/using-a-package.json)”和“[如何创建 Node.js 模块](https://docs.npmjs.com/getting-started/creating-node-modules)”。 + +通过在 *package.json* 文件中包含 `URL` 字段，您可以将多个包发布到同一个 {% data variables.product.prodname_dotcom %} 仓库。 更多信息请参阅“[将多个包发布到同一个仓库](#publishing-multiple-packages-to-the-same-repository)”。 + +您可以使用项目中的本地 *.npmrc* 文件或使用 *package.json* 中的 `publishConfig` 选项来设置项目的作用域映射。 {% data variables.product.prodname_registry %} 只支持作用域内的 npm 包。 作用域内的包具有名称格式 `@owner/name`。 作用域内的包总是以 `@` 符号开头。 您可能需要更新 *package.json* 中的名称以使用作用域内的名称。 例如，`"name": "@codertocat/hello-world-npm"`。 + +{% data reusables.package_registry.viewing-packages %} + +#### 使用本地 *.npmrc* 文件发布包 + +您可以使用 *.npmrc* 文件来配置项目的作用域映射。 在 *.npmrc* 文件中，使用 {% data variables.product.prodname_registry %} URL 和帐户所有者，使 account owner so {% data variables.product.prodname_registry %} 知道将包请求路由到何处。 使用 *.npmrc* 文件防止其他开发者意外地将包发布到 npmjs.org 而不是 {% data variables.product.prodname_registry %}。 + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +1. 验证项目的 *package.json* 中包的名称。 `name` 字段必须包含包的作用域和名称。 例如，如果您的包名称为“test”，要发布到“My-org” +{% data variables.product.prodname_dotcom %} 组织，则 *package.json* 中的 `name` 字段应为 `@my-org/test`。 +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +#### 使用 *package.json* 文件中的 `publishConfig` 发布包 + +您可以使用 *package.json* 文件中的 `publishConfig` 元素来指定要发布包的注册表。 更多信息请参阅 npm 文档中的“[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)”。 + +1. 编辑包的 *package.json* 文件并包含 `publishConfig` 条目。 + {% if enterpriseServerVersions contains currentVersion %} + 有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 + {% endif %} + ```shell + "publishConfig": { + "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + }, + ``` + {% if enterpriseServerVersions contains currentVersion %} + 例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + ```shell + "publishConfig": { + "registry":"https://HOSTNAME/_registry/npm/" + }, + ``` + {% endif %} +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} + +### 将多个包发布到同一个仓库 + +要将多个包发布到同一个仓库，您可以在每个包的 *package.json* 文件的 `repository` 字段中包含 {% data variables.product.prodname_dotcom %} 仓库的 URL。 + +为确保仓库的 URL 正确，请将 REPOSITORY 替换为要发布的包所在仓库的名称，将 OWNER 替换为拥有该仓库的 {% data variables.product.prodname_dotcom %} 用户或组织帐户的名称。 + +{% data variables.product.prodname_registry %} 将根据该 URL 匹配仓库，而不是根据包名称。 + +```shell +"repository":"https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", +``` + +### 安装包 + +通过在项目的 *package.json* 文件中将包添加为依赖项，您可以从 {% data variables.product.prodname_registry %} 安装包。 有关在项目中使用 *package.json* 的更多信息，请参阅 npm 文档中的“[使用 package.json](https://docs.npmjs.com/getting-started/using-a-package.json)”。 + +默认情况下，您可以从一个组织添加包。 更多信息请参阅“[从其他组织安装包](#installing-packages-from-other-organizations)”。 + +还需要将 *.npmrc* 文件添加到项目，使所有安装包的请求都会通过 {% data variables.product.prodname_registry %}。 通过 {% data variables.product.prodname_registry %} 路由所有包请求时，您可以使用 *npmjs.com* 作用域内和作用域外的包。 更多信息请参阅 npm 文档中的“[npm 作用域](https://docs.npmjs.com/misc/scope)”。 + +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +4. 配置项目中的 *package.json* 使用要安装的包。 要将包依赖项添加到 {% data variables.product.prodname_registry %} 的 *package.json* 文件，请指定完整的作用域内包名称，例如 `@my-org/server`。 对于来自 *npmjs.com* 的包，请指定全名，例如 `@babel/core` 或 `@lodash`。 例如，以下 *package.json* 将 `@octo-org/octo-app` 包用作依赖项。 + + ``` + { + "name": "@my-org/server", + "version": "1.0.0", + "description": "Server app that uses the @octo-org/octo-app package", + "main": "index.js", + "author": "", + "license": "MIT", + "dependencies": { + "@octo-org/octo-app": "1.0.0" + } + } + ``` +5. 安装包。 + + ```shell + $ npm install + ``` + +#### 从其他组织安装包 + +默认情况下，您只能使用来自一个组织的 {% data variables.product.prodname_registry %} 包。 如果想将包请求传送到多个组织和用户，您可以添加额外行到 *.npmrc* 文件，将 {% if enterpriseServerVersions contains currentVersion %}*HOSTNAME* 替换为您的 {% data variables.product.prodname_ghe_server %} 实例的主机名，并{% endif %}将 *OWNER* 替换为拥有项目所在仓库的用户或组织帐户的名称。 + +{% if enterpriseServerVersions contains currentVersion %} +有关创建包的更多信息，请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 +{% endif %} + +```shell +registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}/OWNER +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +@OWNER:registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +``` + +{% if enterpriseServerVersions contains currentVersion %} +例如，*OctodogApp* 和 *OctocatApp* 项目将发布到同一个仓库： + +```shell +registry=https://HOSTNAME/_registry/npm/OWNER +@OWNER:registry=https://HOSTNAME/_registry/npm/ +@OWNER:registry=https://HOSTNAME/_registry/npm/ +``` +{% endif %} + +### 延伸阅读 + +- “[删除包](/packages/publishing-and-managing-packages/deleting-a-package/)” 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 new file mode 100644 index 0000000000..98ab1d6cb9 --- /dev/null +++ b/translations/zh-CN/content/packages/guides/configuring-rubygems-for-use-with-github-packages.md @@ -0,0 +1,149 @@ +--- +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.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry + - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages + - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% data reusables.package_registry.admins-can-configure-package-types %} + +### Prerequisites + +- You must have rubygems 2.4.1 or higher. To find your rubygems version: + + ```shell + $ gem --version + ``` + + - You must have bundler 1.6.4 or higher. To find your Bundler version: + ```shell + $ bundle --version + Bundler version 1.13.7 + ``` + + - Install keycutter to manage multiple credentials. To install keycutter: + ```shell + $ gem install keycutter + ``` + +### Authenticating to {% 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. + +```shell +--- +:github: Bearer TOKEN +``` + +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. + +```shell +--- +:backtrace: false +:bulk_threshold: 1000 +:sources: +- https://rubygems.org/ +- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ +:update_sources: true +:verbose: true + +``` + +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 %} + +```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. + +{% data reusables.package_registry.viewing-packages %} + +{% data reusables.package_registry.authenticate-step %} +2. Build the package from the *gemspec* to create the *.gem* package. + ```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 %} + + ```shell + $ gem push --key github \ + --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem + ``` + +### 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.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 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 %} + + ``` + source "https://rubygems.org" + + gem "rails" + + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do + gem "GEM NAME" + end + ``` + +3. 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). + + ``` + source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" + source "https://rubygems.org" + + gem "rails" + gem "GEM NAME" + ``` + +4. Install the package: + ```shell + $ gem install octo-gem --version "0.1.1" + ``` + +### Further reading + +- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/zh-CN/content/packages/guides/connecting-a-repository-to-a-container-image.md b/translations/zh-CN/content/packages/guides/connecting-a-repository-to-a-container-image.md new file mode 100644 index 0000000000..5280f0a2bb --- /dev/null +++ b/translations/zh-CN/content/packages/guides/connecting-a-repository-to-a-container-image.md @@ -0,0 +1,83 @@ +--- +title: 将仓库连接到容器映像 +intro: '您可以在本地以及 {% data variables.product.prodname_dotcom %} 上链接仓库与容器映像。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image +versions: + free-pro-team: '*' +--- + +在链接容器映像与仓库时，软件包登录页面将显示来自仓库的信息和链接，例如 README。 + +要在 {% data variables.product.prodname_dotcom %} 上连接仓库和容器映像，它们必须在 {% data variables.product.prodname_dotcom %} 上共用同一个所有者。 例如，`my_repo` 和 `hello_docker` 都归用户 `monalisa` 所有： +```shell +https://github.com/monalisa/my_repo +https://github.com/monalisa/hello_docker +``` + +### 将仓库连接到 {% data variables.product.prodname_dotcom %} 上用户拥有的容器映像 + +{% data reusables.package_registry.package-settings-from-user-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### 将仓库连接到 {% data variables.product.prodname_dotcom %} 上组织拥有的容器映像 + +{% data reusables.package_registry.package-settings-from-org-level %} + +{% data reusables.package_registry.repository_connection_steps %} + +### 将仓库连接到命令行上的容器映像 + +1. 在 Dockerfile 中添加此行，将 `OWNER` 和 `REPO` 替换为您的详细信息： + + ```shell + LABEL org.opencontainers.image.source https://github.com/OWNER/REPO + ``` + 例如，如果您是用户 `monalisa` 并且拥有 `my-repo`，您会将此行添加到 Dockerfile： + ```shell + LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo + ``` + 更多信息请参阅官方 Docker 文档中的“[LABEL](https://docs.docker.com/engine/reference/builder/#label)”，以及 `opencontainers/image-spec` 仓库中的“[预定义的标注键](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)”。 + +2. 构建容器映像。 此示例从当前目录的 Dockerfile 构建映像，并分配映像名称 `hello_docker`。 + + ```shell + $ docker build -t hello_docker . + ``` +3. （可选）查看您想要标记的 Docker 映像的详细信息。 + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +4. 使用所需的映像名称和托管目标标记 Docker 映像。 + ```shell + $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG + ``` + 例如： + ```shell + $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest + ``` + +5. 如果尚未进行身份验证，请 + +{% data variables.product.prodname_github_container_registry %}. 更多信息请参阅“[向 GitHub Container Registry 验证](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-github-container-registry)”。 + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + > Login Succeeded + ``` + {% endraw %} +6. 推送容器映像到 {% data variables.product.prodname_github_container_registry %}。 + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG + ``` + 例如： + ```shell + $ docker push ghcr.io/monalisa/hello_docker:latest + ``` diff --git a/translations/zh-CN/content/packages/guides/container-guides-for-github-packages.md b/translations/zh-CN/content/packages/guides/container-guides-for-github-packages.md new file mode 100644 index 0000000000..b9d74bf0b4 --- /dev/null +++ b/translations/zh-CN/content/packages/guides/container-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: GitHub Packages 的容器指南 +shortTitle: GitHub Packages 的容器指南 +intro: '您可以使用 {% data variables.product.prodname_registry %} 发布和检索 Docker 映像。' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/zh-CN/content/packages/guides/deleting-a-container-image.md b/translations/zh-CN/content/packages/guides/deleting-a-container-image.md new file mode 100644 index 0000000000..2130feae9b --- /dev/null +++ b/translations/zh-CN/content/packages/guides/deleting-a-container-image.md @@ -0,0 +1,33 @@ +--- +title: 删除容器映像 +intro: '您可以使用 GraphQL 或在 {% data variables.product.prodname_dotcom %} 上删除私有容器映像的版本。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/deleting-a-container-image +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +### 关于包删除 + +您可以在 {% data variables.product.prodname_dotcom %} 上删除整个容器映像或特定版本。 要删除容器映像，必须使用 UI。 目前不支持使用 GraphQL 来删除容器映像。 + +要删除容器映像，您必须具有容器映像的管理员权限。 + +删除公共包时，请注意，您可能会破坏依赖于包的项目。 + +### 删除 {% data variables.product.prodname_dotcom %} 上用户拥有的容器映像版本 + +{% data reusables.package_registry.package-settings-from-user-level %} +5. 在左侧单击 **Manage versions（管理版本）**。 +5. 在要删除的版本的右侧，单击 **Delete（删除）**。 ![删除包按钮](/assets/images/help/package-registry/delete-package-button.png) +6. 要确认删除，请输入包名称，然后单击 **I understand the consequences, delete this version（我明白后果，删除此版本）**。 ![确认包删除按钮](/assets/images/help/package-registry/confirm-package-deletion.png) + +### 删除 {% data variables.product.prodname_dotcom %} 上组织拥有的容器映像版本 + +{% data reusables.package_registry.package-settings-from-org-level %} +5. 在左侧单击 **Manage versions（管理版本）**。 +5. 在要删除的版本的右侧，单击 **Delete（删除）**。 ![删除包按钮](/assets/images/help/package-registry/delete-package-button.png) +6. 要确认删除，请输入包名称，然后单击 **I understand the consequences, delete this version（我明白后果，删除此版本）**。 ![确认包删除按钮](/assets/images/help/package-registry/confirm-package-deletion.png) diff --git a/translations/zh-CN/content/packages/guides/enabling-improved-container-support.md b/translations/zh-CN/content/packages/guides/enabling-improved-container-support.md new file mode 100644 index 0000000000..d50c341356 --- /dev/null +++ b/translations/zh-CN/content/packages/guides/enabling-improved-container-support.md @@ -0,0 +1,39 @@ +--- +title: 启用改进的容器支持 +intro: '要使用 {% data variables.product.prodname_github_container_registry %}，您必须为您的用户或组织帐户启用它。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/enabling-improved-container-support +versions: + free-pro-team: '*' +--- + +{% note %} + +**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)”。 + +{% endnote %} + +### 为您的个人帐户启用 {% data variables.product.prodname_github_container_registry %} + +一旦您的个人用户帐户启用 {% data variables.product.prodname_github_container_registry %}，您就可以发布容器到您的用户帐户所拥有的 {% data variables.product.prodname_github_container_registry %}。 + +要在组织内使用 {% data variables.product.prodname_github_container_registry %}，组织所有者必须为组织成员启用该功能。 + +{% data reusables.feature-preview.feature-preview-setting %} +2. 在左侧，选择“Improved container support（改进的容器支持）”，然后单击 **Enable（启用）**。 ![改进的容器支持](/assets/images/help/settings/improved-container-support.png) + +### 为您的组织帐户启用 {% data variables.product.prodname_github_container_registry %} + +在组织所有者或成员将容器映像发布到 {% data variables.product.prodname_github_container_registry %} 之前，组织管理员必须为组织启用功能预览。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +4. 在左侧，单击 **Packages（包）**。 +5. 在“Improved container support（改进的容器支持）”下，选择“Enable improved container support（启用改进的容器支持）”，然后单击 **Save（保存）**。 ![启用容器注册表支持选项和保存按钮](/assets/images/help/package-registry/enable-improved-container-support-for-orgs.png) +6. 在“Container creation（容器创建）”下，选择是要启用公共容器映像和/或私有容器映像。 + - 要让组织成员创建公共容器映像，请单击 **Public（公共）**。 + - 要让组织成员创建只对其他组织成员可见的私有容器映像，请单击 **Private（私有）**。 您可以进一步自定义私有容器映像的可见性。 更多信息请参阅“[配置容器映像的访问控制和可见性](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)”。 + + ![用于启用公共或私有包的选项 ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/zh-CN/content/packages/guides/index.md b/translations/zh-CN/content/packages/guides/index.md new file mode 100644 index 0000000000..afaeff6f10 --- /dev/null +++ b/translations/zh-CN/content/packages/guides/index.md @@ -0,0 +1,33 @@ +--- +title: 指南 +shortTitle: 指南 +intro: '这些指南帮助您配置 {% data variables.product.prodname_actions %} 或您的包客户端以支持 {% data variables.product.prodname_registry %}。' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem + - /packages/using-github-packages-with-your-projects-ecosystem +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### 目录 + +{% topic_link_in_list /package-client-guides-for-github-packages %} + {% link_in_list /using-github-packages-with-github-actions %} + {% link_in_list /configuring-apache-maven-for-use-with-github-packages %} + {% link_in_list /configuring-gradle-for-use-with-github-packages %} + {% link_in_list /configuring-npm-for-use-with-github-packages %} + {% link_in_list /configuring-dotnet-cli-for-use-with-github-packages %} + {% link_in_list /configuring-rubygems-for-use-with-github-packages %} +{% topic_link_in_list /container-guides-for-github-packages %} + {% link_in_list /configuring-docker-for-use-with-github-packages %} + {% link_in_list /about-github-container-registry %} + {% link_in_list /migrating-to-github-container-registry-for-docker-images %} + {% link_in_list /enabling-improved-container-support %} + {% link_in_list /configuring-access-control-and-visibility-for-container-images %} + {% link_in_list /connecting-a-repository-to-a-container-image %} + {% link_in_list /pushing-and-pulling-docker-images %} + {% link_in_list /deleting-a-container-image %} + diff --git a/translations/zh-CN/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md b/translations/zh-CN/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md new file mode 100644 index 0000000000..dd9cc937af --- /dev/null +++ b/translations/zh-CN/content/packages/guides/migrating-to-github-container-registry-for-docker-images.md @@ -0,0 +1,115 @@ +--- +title: 迁移到 Docker 映像的 GitHub Container Registry +intro: '如果您已经使用 GitHub Packages Docker 注册表来存储 Docker 映像，可以迁移到新的 {% data variables.product.prodname_container_registry %}。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images +versions: + free-pro-team: '*' +--- + +### {% data variables.product.prodname_github_container_registry %} 与 Docker 软件包注册表之间的主要差异 + +{% data reusables.package_registry.container-registry-beta %} + +{% data variables.product.prodname_github_container_registry %} 取代原有的Packages Docker 注册表，并且做了优化，可支持容器的一些独特需求。 + +{% data reusables.package_registry.container-registry-feature-highlights %} + +更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)”。 + +### 计费更改 + +{% data reusables.package_registry.billing-for-container-registry %} + +### 域更改 + +{% data variables.product.prodname_container_registry %} 的域是 `ghcr.io`。 + +| 注册表 | 示例 URL | +| ----------------------------------------------------------------- | --------------------------------------------------- | +| {% data variables.product.prodname_registry %} Docker 注册表 | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` | +| {% data variables.product.prodname_github_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME` | + +### 使用容器注册表进行身份验证 + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +您需要使用基本 URL `ghcr.io` 向 {% data variables.product.prodname_container_registry %} 验证。 我们建议创建新的访问令牌以使用 {% data variables.product.prodname_container_registry %}。 + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### 使用 Docker CLI 迁移 Docker 映像 + +要移动您在 {% data variables.product.prodname_registry %} Docker 注册表上托管的 Docker 映像，您必须将映像重新发布到 {% data variables.product.prodname_container_registry %}。 我们建议在本地计算机上使用命令行重新发布现有的 Docker 映像。 + +1. 使用作用域至少为 `read:packages` 的临时 PAT 登录到 Docker 注册表。 此 PAT 将仅用于登录到 Docker 注册表以下拉映像，然后可以删除。 + {% raw %} + ```shell + $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin + ``` + {% endraw %} +2. 下拉要迁移的映像，将 OWNER 替换为拥有仓库的用户或组织帐户的名称，将 REPOSITORY 替换为包含项目的仓库，将 IMAGE_NAME 替换为包或映像的名称，将 VERSION 替换为要安装的映像的标记。 例如，`docker ull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` 拉取 octo-org 组织中 `octoshift/octoshift` 映像的最新标记。 + ```shell + $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + ``` + +3. 使用新域和新映像名称重新标记映像。 更多信息请参阅 Docker 文档中的“[Docker 标记](https://docs.docker.com/engine/reference/commandline/tag/)”。 使用在上一步中用于 SOURCE URL 同一个URL。 将 TARGET_OWNER 替换为要将容器映像迁移到其中的用户或组织，将 TARGET_IMAGE_NAME 替换为新 {% data variables.product.prodname_container_registry %} 映像名称。 + ```shell + $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION + ``` + +4. 登录到新的 + +{% data variables.product.prodname_container_registry %}. 我们建议创建限于 `read:packages` 和 `write:packages` 范围的新 PAT，因为您不再需要 `repo` 范围，并且您之前的 PAT 不能具有 `write:packages` 范围。 + {% raw %} + ```shell + $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + ``` + {% endraw %} +5. 将重新标记的映像推送到 {% data variables.product.prodname_container_registry %}。 + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION + ``` + +### 更新 {% data variables.product.prodname_actions %} 工作流程 + +{% data reusables.package_registry.feature-preview-for-container-registry %} + +如果您有 {% data variables.product.prodname_actions %} 工作流程使用来自 {% data variables.product.prodname_registry %} Docker 注册表的 Docker 映像，则可能需要将工作流程更新到 {% data variables.product.prodname_container_registry %}，以允许匿名访问公共容器映像、更细致的访问权限以及更好的容器存储和带宽兼容性。 + +1. 将 Docker 映像迁移到 `ghcr.io` 上的新 {% data variables.product.prodname_container_registry %}。 例如，请参阅“[使用 Docker CLI 迁移 Docker 映像](#migrating-a-docker-image-using-the-docker-cli)”。 + +2. 在 {% data variables.product.prodname_actions %} 工作流程文件中，将包 url 从 `https://docker.pkg.github.com` 更新到 `ghcr.io`。 + +3. 将新的 {% data variables.product.prodname_container_registry %} 身份验证个人访问令牌 (PAT) 添加为 GitHub ACtions 密码。 {% data variables.product.prodname_github_container_registry %} 不支持对 PAT 使用 `GITHUB_TOKEN`，因此您必须使用不同的自定义变量，例如 `CR_PAT`。 更多信息请参阅“[创建和存储加密密码](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)”。 + +4. 在 {% data variables.product.prodname_actions %} 工作流程文件中更新身份验证 PAT，将 Docker 注册表 PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) 替换为 {% data variables.product.prodname_container_registry %} PAT 的新变量，例如 {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}。 + +#### 更新的工作流程示例 + +如果工作流程的一部分访问由 Docker 注册表托管的 Docker 映像，如： + +{% raw %} +```yaml +echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin +docker pull docker.pkg.github.com/github/octoshift/octoshift:latest +docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest +docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA +``` +{% endraw %} + +然后，您需要使用新的 URL 和 PAT {% data variables.product.prodname_container_registry %} 更新工作流程，如： + +{% raw %} +```yaml +# new login with new container registry url and PAT +echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin +# new container registry urls added +docker pull ghcr.io/github/octoshift:latest +docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest +docker push ghcr.io/github/octoshift:$GITHUB_SHA +``` +{% endraw %} diff --git a/translations/zh-CN/content/packages/guides/package-client-guides-for-github-packages.md b/translations/zh-CN/content/packages/guides/package-client-guides-for-github-packages.md new file mode 100644 index 0000000000..a7bc78ed0f --- /dev/null +++ b/translations/zh-CN/content/packages/guides/package-client-guides-for-github-packages.md @@ -0,0 +1,10 @@ +--- +title: GitHub Packages 的包客户端指南 +shortTitle: GitHub Packages 的包客户端指南 +intro: '您可以使用 {% data variables.product.prodname_registry %} 发布和检索包客户端映像。' +mapTopic: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + diff --git a/translations/zh-CN/content/packages/guides/pushing-and-pulling-docker-images.md b/translations/zh-CN/content/packages/guides/pushing-and-pulling-docker-images.md new file mode 100644 index 0000000000..69345df36b --- /dev/null +++ b/translations/zh-CN/content/packages/guides/pushing-and-pulling-docker-images.md @@ -0,0 +1,106 @@ +--- +title: 推送和拉取 Docker 映像 +intro: '您可以在 {% data variables.product.prodname_github_container_registry %} 中存储和管理 Docker 映像。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images +versions: + free-pro-team: '*' +--- + +{% data reusables.package_registry.container-registry-beta %} + +要推送和拉取组织拥有的容器映像，组织管理员必须为组织启用 {% data variables.product.prodname_github_container_registry %}。 更多信息请参阅“[启用改进的容器支持](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)”。 + +### 向 {% data variables.product.prodname_github_container_registry %} 验证 + +{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} + +{% data reusables.package_registry.authenticate-to-container-registry-steps %} + +### 推送容器映像 + +此示例推送最新版本的 `IMAGE-NAME`。 + ```shell + $ docker push ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +此示例推送 `2.5` 版的映像。 + ```shell + $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 + ``` + +首次发布包时，默认可见性是私有的。 要更改可见性或设置访问权限，请参阅“[配置容器映像的访问控制和可见性](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)”。 + +### 拉取容器映像 + +#### 通过摘要拉取 + +为了确保始终使用相同的映像，您可以通过 `digest` SHA 值指定要拉取的准确容器映像版本。 + +1. 要查找摘要 SHA 值，请使用 `docker inspect` 或 `docker pull`，并复制 `Digest:` 后的 SHA 值 + ```shell + $ docker inspect ghcr.io/OWNER/IMAGE_NAME + ``` +2. 按需要在本地删除映像。 + ```shell + $ docker rmi ghcr.io/OWNER/IMAGE_NAME:latest + ``` + +3. 拉取图像名称后有 `@YOUR_SHA_VALUE` 的容器映像。 + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs + ``` + +#### 按名称拉取 + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME + ``` + +#### 按名称和版本拉取 + +显示按名称和 `1.14.1` 版本标记拉取映像的 Docker CLI 示例： + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1 + > 5e35bd43cf78: Pull complete + > 0c48c2209aab: Pull complete + > fd45dd1aad5a: Pull complete + > db6eb50c2d36: Pull complete + > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e + > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 + > ghcr.io/orgname/image-name/release:1.14.1 + ``` + +#### 按名称和最新版本拉取 + + ```shell + $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest + > latest: Pulling from user/image-name + > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 + > Status: Downloaded newer image for ghcr.io/user/image-name:latest + > ghcr.io/user/image-name:latest + ``` + +### 构建容器映像 + +此示例构建 `hello_docker` 映像： + ```shell + $ docker build -t hello_docker . + ``` + +### 标记容器映像 + +1. 找到要标记的 Docker 映像的 ID。 + ```shell + $ docker images + > REPOSITORY TAG IMAGE ID CREATED SIZE + > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB + ``` + +2. 使用映像 ID 以及所需的映像名称和托管目标标记 Docker 映像。 + ```shell + $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest + ``` 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 new file mode 100644 index 0000000000..bb4ed48ec6 --- /dev/null +++ b/translations/zh-CN/content/packages/guides/using-github-packages-with-github-actions.md @@ -0,0 +1,54 @@ +--- +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 %}.' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions + - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### About {% data variables.product.prodname_registry %} with {% 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)." + +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 %} + +{% 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)." + +{% endif %} + +#### Authenticating to package registries on {% 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. + +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)." + +### Publishing a package using an action + +You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. + +{% data reusables.package_registry.actions-configuration %} + +### 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 %} + +{% 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 %} diff --git a/translations/zh-CN/content/packages/index.md b/translations/zh-CN/content/packages/index.md index fe9b85b45c..a3468dcc4a 100644 --- a/translations/zh-CN/content/packages/index.md +++ b/translations/zh-CN/content/packages/index.md @@ -2,31 +2,46 @@ title: GitHub 包文档 shortTitle: GitHub Packages intro: '了解如何安全地发布和使用包，将包与代码存储在一起，以及与您的团队私下分享或与开源社区公开分享您的包。 还可以使用 {% data variables.product.prodname_actions %} 自动执行您的包。' +introLinks: + quickstart: /packages/quickstart + reference: /packages/manage-packages featuredLinks: - gettingStarted: - - /packages/publishing-and-managing-packages/about-github-packages - - /packages/getting-started-with-github-container-registry/about-github-container-registry - - /packages/getting-started-with-github-container-registry - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/publishing-and-managing-packages/publishing-a-package - - /packages/publishing-and-managing-packages/installing-a-package + guides: + - /packages/learn-github-packages + - /packages/guides/using-github-packages-with-github-actions + - /packages/manage-packages/installing-a-package popular: - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages - - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages - - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images - - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/learn-github-packages/about-github-packages + - /packages/guides/configuring-apache-maven-for-use-with-github-packages + guideCards: + - /packages/guides/configuring-npm-for-use-with-github-packages + - /packages/guides/enabling-improved-container-support + - /packages/guides/configuring-rubygems-for-use-with-github-packages +changelog: + - + title: 包容器支持是一个选择性测试版 + date: '2020-11-17' + href: https://docs.github.com/packages/getting-started-with-github-container-registry/enabling-improved-container-support + - + title: 组织管理员对容器的访问 + date: '2020-11-16' + href: https://github.blog/changelog/2020-11-16-packages-organization-admins-access-to-containers/ + - + title: 包现在遵守 IP 允许列表设置 + date: '2020-11-12' + href: https://github.blog/changelog/2020-11-12-packages-now-respects-ip-allow-list-settings/ redirect_from: - /github/managing-packages-with-github-packages - /categories/managing-packages-with-github-package-registry - /github/managing-packages-with-github-package-registry +layout: product-landing versions: free-pro-team: '*' enterprise-server: '>=2.22' --- -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% link_with_intro /getting-started-with-github-container-registry %} -{% link_with_intro /managing-container-images-with-github-container-registry %} -{% link_with_intro /publishing-and-managing-packages %} -{% link_with_intro /using-github-packages-with-your-projects-ecosystem %} + + + + 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 new file mode 100644 index 0000000000..5259887ea7 --- /dev/null +++ b/translations/zh-CN/content/packages/learn-github-packages/about-github-packages.md @@ -0,0 +1,166 @@ +--- +title: 关于 GitHub 包 +intro: '{% data variables.product.prodname_registry %} 是一种软件包托管服务，允许您私下或公开托管软件包，并将包用作项目中的依赖项。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/about-github-package-registry + - /github/managing-packages-with-github-package-registry/about-github-package-registry + - /github/managing-packages-with-github-packages/about-github-packages + - /packages/publishing-and-managing-packages/about-github-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### 关于 {% 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.product_name %} API、{% data variables.product.prodname_actions %} 以及 web 挂钩集成在一起，以创建端到端的 DevOps 工作流程，其中包括您的代码、CI 和部署解决方案。 + +您可以在一个仓库中托管多个包，并通过查看包的自述文件、下载统计、版本历史等，了解每个包的更多信息。 + +{% if currentVersion == "free-pro-team@latest" %} +创建 {% data variables.product.prodname_actions %} 工作流程时，您可以使用 `GITHUB_TOKEN` 发布和安装 {% data variables.product.prodname_registry %} 中的包，无需存储和管理个人访问令牌。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)”。 + +{% data reusables.package_registry.container-registry-beta %} + +![显示节点、RubyGems、Apache Maven、Gradle、Nuget 和容器注册表及其托管 Url 的图表](/assets/images/help/package-registry/packages-overview-diagram.png) + +{% endif %} + +#### 查看包 + +您可以在 {% data variables.product.product_name %} 上查看软件包的 README、一些元数据（如许可）、下载统计、版本历史记录等。 更多信息请参阅“[查看包](/packages/manage-packages/viewing-packages)”。 + +#### 关于包权限和可见性 + +| | 包注册表 | +| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 托管位置 | 您可以在一个仓库中托管多个包。 | +| 权限 | {% 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" %} +### 关于 {% 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.container-registry-beta-billing-note %} +{% endif %} + +### 支持的客户端和格式 + +{% 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` | + +{% note %} + +**注：**禁用子域隔离时，不支持 Docker。 + +{% endnote %} + +有关子域隔离的更多信息，请参阅“[启用子域隔离](/enterprise/admin/configuration/enabling-subdomain-isolation)”。 + +{% endif %} + +有关配置包客户端以用于 {% data variables.product.prodname_registry %} 的更多信息，请参阅“[{% data variables.product.prodname_registry %} 的包客户端指南](/packages/guides/package-client-guides-for-github-packages)”。 + +{% if currentVersion == "free-pro-team@latest" %} +有关 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 %} 验证 + +{% data reusables.package_registry.authenticate-packages %} + +### 管理包 + +要安装或发布包，您必须使用具有适当作用域的令牌，并且您的用户帐户必须对该仓库具有适当的权限。 + +例如： +- 要从仓库下载和安装包，您的令牌必须具有 `read:packages` 作用域，并且您的用户帐户必须对该仓库具有读取权限。 +- 要在 {% data variables.product.product_name %} 上删除私有包的特定版本，您的令牌必须具有 `delete:packages` 和 `repo` 作用域。 公共包无法删除。 更多信息请参阅“[删除包](/packages/manage-packages/deleting-a-package)”。 + +| 作用域 | 描述 | 仓库权限 | +| ----------------- | ----------------------------------------------------------- | ------ | +| `read:packages` | 从 {% data variables.product.prodname_registry %} 下载和安装包 | 读取 | +| `write:packages` | 将包上传和发布到 {% data variables.product.prodname_registry %} | 写入 | +| `delete:packages` | 从 {% data variables.product.prodname_registry %} 删除私有包的特定版本 | 管理员 | +| `repo` | 上传和删除包（连同 `write:packages` 或 `delete:packages`） | 写入或管理员 | + +创建 {% data variables.product.prodname_actions %} 工作流程时，您可以使用 `GITHUB_TOKEN` 发布和安装 {% data variables.product.prodname_registry %} 中的包，无需存储和管理个人访问令牌。 + +更多信息请参阅： +- 遇到任何与文档相矛盾的事情 +- “[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token/)”。 +- 发布的包中含有敏感数据，例如违反 GDPR、API 密钥或个人身份信息 + +### 管理包 + +您可以在 {% 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)”。 + +您可以配置 web 挂钩来订阅与包相关的事件，例如包的发布或更新等事件。 更多信息请参阅“[`package` web 挂钩事件](/webhooks/event-payloads/#package)”。 + +### 联系支持 + +{% if currentVersion == "free-pro-team@latest" %} +如果您对 +{% data variables.product.prodname_registry %} 有反馈或功能请求，请使用 [{% data variables.product.prodname_registry %} 反馈表](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages)。 + +如果在 {% data variables.product.prodname_registry %} 方面遇到以下问题，请使用[我们的联系表](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages)联系 {% data variables.contact.github_support %}： + +* 遇到任何与文档相矛盾的事情 +* 遇到模糊或不清楚的错误 +* 发布的包中含有敏感数据，例如违反 GDPR、API 密钥或个人身份信息 + +{% else %} +如果您需要对 +{% data variables.product.prodname_registry %} 的支持，请联系网站管理员。 + +{% endif %} diff --git a/translations/zh-CN/content/packages/learn-github-packages/core-concepts-for-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/core-concepts-for-github-packages.md new file mode 100644 index 0000000000..7870aff91c --- /dev/null +++ b/translations/zh-CN/content/packages/learn-github-packages/core-concepts-for-github-packages.md @@ -0,0 +1,28 @@ +--- +title: GitHub Packages 的核心概念 +intro: '以下是我们在网站和文档中使用的 {% data variables.product.prodname_registry %} 常见术语列表。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### 包 + +包是一个自包含且可重用的软件，它包括代码和元数据，开发人员可将它们捆绑在一个位置供他人使用。 包的元数据可能包括版本号、名称和代码的依赖项。 包简化了针对常见问题的使用和分发解决方案，例如需要使用框架来开发或测试项目、进行语法检查以提高代码质量，或引入行业标准的机器学习工具来强化您的应用程序。 包存在于许多生态系统中。 例如，您可以打包 Node.js 和 Java 代码或容器映像。 + +### 容器 + +容器是一个软件单元，设计为在任何平台上以标准化的方式可靠地部署软件。 容器作为独立的虚拟环境或实例运行，可在与操作系统相同的主机内核上运行各种软件包和组件。 容器使用的资源比虚拟机少，因为它们不需要自带虚拟硬件即可运行。 容器是使用容器映像文件（如 Dockerfile）和容器客户端或运行时程序创建的。 + +### 容器映像 + +容器映像是一种包存档类型，用于指定从容器运行应用程序的软件要求。 容器映像通常包括应用程序的代码、库和运行时指令。 为确保在部署和运行映像的所有地方使用相同的映像详细信息，容器映像将自动进行版本管理，并且在容器中生成容器映像后无法更改。 + +### Docker 容器 + +Docker 容器是一种在 Docker 平台上构建的开源容器类型。 Docker 的原始映像格式已成为 OCI（开放容器计划）映像规范。 更多信息请参阅 [Docker 文档](https://docs.docker.com/get-started/overview/)。 diff --git a/translations/zh-CN/content/packages/learn-github-packages/index.md b/translations/zh-CN/content/packages/learn-github-packages/index.md new file mode 100644 index 0000000000..3c7a39cfcc --- /dev/null +++ b/translations/zh-CN/content/packages/learn-github-packages/index.md @@ -0,0 +1,16 @@ +--- +title: 了解 GitHub Packages +shortTitle: 了解 GitHub Packages +intro: '您可以找到更多关于 GitHub Packages 的信息，包括发布新包到 {% data variables.product.prodname_registry %}。' +redirect_from: + - /packages/getting-started-with-github-container-registry +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /about-github-packages %} +{% link_in_list /core-concepts-for-github-packages %} +{% link_in_list /publishing-a-package %} diff --git a/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md new file mode 100644 index 0000000000..dc1a89fa3b --- /dev/null +++ b/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md @@ -0,0 +1,37 @@ +--- +title: 发布包 +intro: '您可以将包发布到 {% data variables.product.prodname_registry %} 以供他人下载和再用。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-a-package + - /packages/publishing-and-managing-packages/publishing-a-package +permissions: 对仓库有写入权限的任何人都可以向该仓库发布包。 +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### 关于发布的包 + +您可以在包页面上提供说明和其他详细信息，例如安装和使用说明，以帮助他人了解和使用您的包。 {% data variables.product.product_name %} 提供每个版本的元数据，例如发布日期、下载活动和最新版本。 要查看示例包页面，请参阅 [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1)。 + +{% data reusables.package_registry.public-or-private-packages %} 一个仓库可包含多个包。 为避免混淆，请确保使用自述文件和说明清楚地阐明每个包的相关信息。 + +{% if currentVersion == "free-pro-team@latest" %} +如果软件包的新版本修复了安全漏洞，您应该在仓库中发布安全通告。 +{% data variables.product.prodname_dotcom %} 审查每个发布的安全通告，并且可能使用它向受影响的仓库发送 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于 GitHub 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 +{% endif %} + +### 发布包 + +您可以按照一般准则，使用任何{% if currentVersion == "free-pro-team@latest" %}支持的包客户端{% else %}为您的实例启用的包类型{% endif %}将包发布到 {% data variables.product.prodname_registry %}。 + +1. 针对要完成的任务，创建具有适当作用域的访问令牌或使用现有的此类令牌。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)”。 +2. 按照包客户端的说明，使用访问令牌向 {% data variables.product.prodname_registry %} 验证。 +3. 按照包客户端的说明发布包。 + +有关包客户端的具体说明，请参阅“[将 {% data variables.product.prodname_registry %} 用于项目的生态系统](/packages/using-github-packages-with-your-projects-ecosystem)”。 + +在发布包后，您可以在 {% data variables.product.prodname_dotcom %} 上查看该包。 更多信息请参阅“[查看包](/packages/publishing-and-managing-packages/viewing-packages)”。 diff --git a/translations/zh-CN/content/packages/manage-packages/deleting-a-package.md b/translations/zh-CN/content/packages/manage-packages/deleting-a-package.md new file mode 100644 index 0000000000..5ac6b85867 --- /dev/null +++ b/translations/zh-CN/content/packages/manage-packages/deleting-a-package.md @@ -0,0 +1,81 @@ +--- +title: 删除包 +intro: '您可以使用 GraphQL 或在 {% data variables.product.product_name %} 上删除私有包的版本。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/deleting-a-package + - /packages/publishing-and-managing-packages/deleting-a-package +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% if currentVersion == "free-pro-team@latest" %} +### 关于私有包删除 + +要在 {% data variables.product.product_name %}上删除容器映像包，请参阅“[删除容器映像](/packages/guides/deleting-a-container-image)”。 + +{% endif %} + +### 关于私有包删除 + +只能在 {% data variables.product.product_name %} 上或使用 GraphQL API 删除私有包的特定版本。 要删除 {% data variables.product.product_name %} 上出现的整个私有包，必须先删除该包的每个版本。 + +{% if currentVersion == "free-pro-team@latest" %} +### 关于公共包删除 + +为避免中断可能依赖于包的项目，您不能删除整个公共包或公共包的特定版本。 + +在特殊情况下，例如出于法律原因或为了满足 GDPR 标准，您可以使用[我们的联系表](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry)要求 {% data variables.contact.github_support %} 为您删除公共包。 + +{% else %} + +目前，{% data variables.product.prodname_registry %} on {% data variables.product.product_location %} 不支持删除公共包。 + +{% endif %} + +### 在 {% data variables.product.product_name %} 上删除私有包的版本 + +要删除私有包版本，您必须具有仓库的管理员权限。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +3. 单击要删除的包的名称。 ![包名称](/assets/images/help/package-registry/select-pkg-cloud.png) +4. 在右侧使用 **Edit package（编辑包）**下拉菜单，然后选择“Manage versions（管理版本）”。 ![包名称](/assets/images/help/package-registry/manage-versions.png) +5. 在要删除的版本的右侧，单击 **Delete（删除）**。 ![删除包按钮](/assets/images/help/package-registry/delete-package-button.png) +6. 要确认删除，请输入包名称，然后单击 **I understand the consequences, delete this version（我明白后果，删除此版本）**。 ![确认包删除按钮](/assets/images/help/package-registry/confirm-package-deletion.png) + +### 使用 GraphQL 删除私有包的版本 + +在 GraphQL API 中使用 `deletePackageVersion` 突变。 必须使用具有 `read:packages`、`delete:packages` 和 `repo` 作用域的令牌。 有关令牌的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)”。 + +以下是使用个人访问令牌，通过 cURL 命令删除包版本的示例，包版本 ID 为 `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`。 + +{% if currentVersion == "free-pro-team@latest" %} +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +https://api.github.com/graphql +``` + +{% else %} + +``` +curl -X POST \ +-H "Accept: application/vnd.github.package-deletes-preview+json" \ +-H "Authorization: bearer TOKEN" \ +-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ +HOSTNAME/graphql +``` + +{% endif %} + +要查找已发布到 {% data variables.product.prodname_registry %} 的所有私有包以及包的版本 ID，您可以使用 `registryPackagesForQuery` 连接。 您需要具有 `read:packages` 和 `repo` 作用域的令牌。 更多信息请参阅“[`registryPackagesForQuery`](/v4/object/registrypackageconnection/)”。 + +有关 `deletePackageVersion` 突变的更多信息，请参阅“[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)”。 + +您不能删除整个包，但如果您删除包的每个版本，该包将不再显示在 {% data variables.product.product_name %} 上。 diff --git a/translations/zh-CN/content/packages/manage-packages/index.md b/translations/zh-CN/content/packages/manage-packages/index.md new file mode 100644 index 0000000000..de762e497a --- /dev/null +++ b/translations/zh-CN/content/packages/manage-packages/index.md @@ -0,0 +1,18 @@ +--- +title: 管理 GitHub 包 +shortTitle: 管理 GitHub 包 +intro: '您可以将新包发布到 {% data variables.product.prodname_registry %}，查看和安装现有包，并且在特殊情况下删除现有包。' +redirect_from: + - /github/managing-packages-with-github-packages/publishing-and-managing-packages + - /github/packages/publishing-and-managing-packages + - /packages/publishing-and-managing-packages +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +{% link_in_list /viewing-packages %} +{% link_in_list /installing-a-package %} +{% link_in_list /deleting-a-package %} diff --git a/translations/zh-CN/content/packages/manage-packages/installing-a-package.md b/translations/zh-CN/content/packages/manage-packages/installing-a-package.md new file mode 100644 index 0000000000..e10b895230 --- /dev/null +++ b/translations/zh-CN/content/packages/manage-packages/installing-a-package.md @@ -0,0 +1,29 @@ +--- +title: 安装包 +intro: '您可以从 {% data variables.product.prodname_registry %} 安装包，并将包用作自己项目中的依赖项。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /github/managing-packages-with-github-packages/installing-a-package + - /packages/publishing-and-managing-packages/installing-a-package +permissions: 对仓库有读取权限的任何人都可以从该仓库安装包。 +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### 关于包的安装 + +您可以搜索 {% data variables.product.product_name %}，在 {% data variables.product.prodname_registry %} 中找到可安装在自己项目中的包。 更多信息请参阅“[搜索 {% data variables.product.prodname_registry %} 中的包](/github/searching-for-information-on-github/searching-for-packages)”。 + +找到包后，您可以在包页面上阅读包的说明以及安装和使用说明。 + +### 安装包 + +您可以按照一般准则，使用任何{% if currentVersion == "free-pro-team@latest" %}支持的包客户端{% else %}为您的实例启用的包类型{% endif %}从 {% data variables.product.prodname_registry %} 安装包。 + +1. 按照包客户端的说明，向 {% data variables.product.prodname_registry %} 验证。 更多信息请参阅“[关于令牌](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)”。 +2. 按照包客户端的说明安装包。 + +有关包客户端的具体说明，请参阅“[将 {% data variables.product.prodname_registry %} 用于项目的生态系统](/packages/using-github-packages-with-your-projects-ecosystem)”。 diff --git a/translations/zh-CN/content/packages/manage-packages/viewing-packages.md b/translations/zh-CN/content/packages/manage-packages/viewing-packages.md new file mode 100644 index 0000000000..9c30fd1a81 --- /dev/null +++ b/translations/zh-CN/content/packages/manage-packages/viewing-packages.md @@ -0,0 +1,50 @@ +--- +title: 查看包 +intro: '您可以查看已发布到仓库的包的详细信息，也可以按组织或用户缩小结果范围。' +product: '{% data reusables.gated-features.packages %}' +redirect_from: + - /articles/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages + - /github/managing-packages-with-github-packages/viewing-packages + - /packages/publishing-and-managing-packages/viewing-packages +permissions: 任何对仓库有读取权限的人都可以查看该仓库的包。 +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +### 查看仓库的包 + +包必须安装在仓库层级，但您可以查看某个组织中的所有包和您发布的所有包。 {% data reusables.package_registry.package-page-info %} + +### 查看仓库的包 + +您可以查看仓库中的所有包，也可以在仓库中搜索特定的包。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + +### 查看组织的包 + +您可以查看组织中安装的所有包，也可以搜索组织仓库中安装的特定包。 + +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +3. 在组织名称下，单击 +{% octicon "package" aria-label="The package icon" %} **包**. +{% data reusables.package_registry.navigate-to-packages %} + +### 查看您的包 + +您可以查看您安装的所有包，也可以跨所有组织和仓库搜索您安装的特定包。 + +{% data reusables.profile.access_profile %} +2. 在个人资料页面顶部的主导航栏中，单击 **Packages（包）**。 ![项目选项卡](/assets/images/help/package-registry/user-packages-tab.png) +{% data reusables.package_registry.navigate-to-packages %} + +### 延伸阅读 + +- “[搜索包](/github/searching-for-information-on-github/searching-for-packages)” diff --git a/translations/zh-CN/content/packages/quickstart.md b/translations/zh-CN/content/packages/quickstart.md new file mode 100644 index 0000000000..29951886f2 --- /dev/null +++ b/translations/zh-CN/content/packages/quickstart.md @@ -0,0 +1,110 @@ +--- +title: GitHub Packages 快速入门 +intro: '使用 {% data variables.product.prodname_actions %} 在 5 分钟内发布到 {% data variables.product.prodname_registry %}。' +allowTitleToDifferFromFilename: true +versions: + free-pro-team: '*' + enterprise-server: '>=2.22' +--- + +### 简介 + +您只需要一个现有的 {% data variables.product.prodname_dotcom %} 仓库将包发布到到 {% data variables.product.prodname_registry %}。 在本指南中，您将创建 {% data variables.product.prodname_actions %} 工作流程来测试代码，然后将其发布到 {% data variables.product.prodname_registry %}。 随意为此快速入门创建新仓库。 您可以使用它来测试当前和未来的 {% data variables.product.prodname_actions %} 工作流程。 + +### 发布包 + +1. 在 {% data variables.product.prodname_dotcom %} 上创建新仓库，为节点添加 `.gitignore`。 如果稍后要删除此包，请创建私有仓库，公共包无法删除。 更多信息请参阅“[创建新仓库](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)”。 +2. 将仓库克隆到本机。 + {% raw %} + ```shell + $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git + $ cd YOUR-REPOSITORY + ``` + {% endraw %} +3. 创建 `index.js` 文件，并添加基本警报说 "Hello world!" + {% raw %} + ```javascript{:copy} + alert("Hello, World!"); + ``` + {% endraw %} +4. 初始化 npm 包。 在包初始化向导中，输入包名称：_`@YOUR-USERNAME/YOUR-REPOSITORY`_，如果您没有任何测试，请将测试脚本设置为 `exit 0`。 提交更改并推送以 +{% data variables.product.prodname_dotcom %}. + {% raw %} + ```shell + $ npm init + ... + package name: @YOUR-USERNAME/YOUR-REPOSITORY + ... + test command: exit 0 + ... + + $ npm install + $ git add index.js package.json package-lock.json + $ git commit -m "initialize npm package" + $ git push + ``` + {% endraw %} +5. 从 {% data variables.product.prodname_dotcom %} 上的仓库，在 `.github/workflow` 目录中创建一个名为 `release-package.yml` 的新文件。 更多信息请参阅“[创建新文件](/github/managing-files-in-a-repository/creating-new-files)”。 +6. 将以下 YAML 内容复制到 `release-package.yml` 文件中。 + {% raw %} + ```yaml{:copy} + name: Node.js Package + + on: + release: + types: [created] + + jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + - run: npm ci + - run: npm test + + publish-gpr: + needs: build + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - uses: actions/setup-node@v1 + with: + node-version: 12 + registry-url: https://npm.pkg.github.com/ + - run: npm ci + - run: npm publish + env: + NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}} + ``` + {% endraw %} +7. 滚动到页面底部，然后选择 **Create a new branch for this commit and start a pull request（为此提交创建一个新分支并开始拉取请求）**。 然后，若要创建拉取请求，请单击 **Propose new file（提议新文件）**。 +8. **合并**拉取请求。 +9. 导航到 **Code（代码）**选项卡，并创建一个新版本来测试工作流程。 更多信息请参阅“[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)”。 + +在仓库中创建新版本将触发生成和测试代码的工作流程。 如果测试通过，则包将发布到 {% data variables.product.prodname_registry %}。 + +### 查看已发布的包 + +包在仓库级别发布。 您可以查看仓库中的所有包，也可以搜索特定的包。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.package_registry.packages-from-code-tab %} +{% data reusables.package_registry.navigate-to-packages %} + + +### 安装已发布的包 + +现在，您已发布包，您需要使用它作为项目之间的依赖项。 更多信息请参阅"[配置 npm 用于 {% data variables.product.prodname_registry %}](/packages/guides/configuring-npm-for-use-with-github-packages#installing-a-package)"。 + +### 后续步骤 + +您刚刚添加的基本工作流程在仓库中创建新版本时运行。 但是，这只是您可以对 {% data variables.product.prodname_registry %} 执行操作的开始。 您可以使用单个工作流和将包发布到多个注册表，触发工作流程以在发生不同事件（如合并拉取请求、管理容器等）时运行。 + +合并 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 可以帮助您实现应用程序开发过程几乎每个方面的自动化。 准备好开始了吗？ 以下是一些有用的资源，可用于执行 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 的后续步骤： + +- “[了解 {% data variables.product.prodname_registry %}](/packages/learn-github-packages)”，以获取 GitHub Packages 的深入教程 +- “[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”，以获取 GitHub Actions 的深入教程 +- “[指南](/packages/guides)”，以获取特定用例和示例 diff --git a/translations/zh-CN/content/rest/README.md b/translations/zh-CN/content/rest/README.md new file mode 100644 index 0000000000..dba045aaf1 --- /dev/null +++ b/translations/zh-CN/content/rest/README.md @@ -0,0 +1,10 @@ +# REST + +`/content/rest` 目录是 GitHub REST API 文档所在的位置！ + +* `/content/rest/guides` and `/content/rest/overview` 目录包含常规项目。 这些项目可人工编辑。 +* `/content/rest/reference` 目录对 GitHub GraphQL API 中的每组端点包含一个项目。 此目录中的大多数内容都使用 `include` 呈现。 + + `include` 标记呈现的内容来自 `/lib/rest/static` 目录，由 GitHub 内部的 API 源代码自动生成，不应人工编辑。 更多信息请参阅 [`/lib/rest/README.md`](/lib/rest/README.md)。 + + **因此，我们不能接受参与此仓库中的 REST API 参考内容。** 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 157e378b87..b87c5e8465 100644 --- a/translations/zh-CN/content/rest/guides/basics-of-authentication.md +++ b/translations/zh-CN/content/rest/guides/basics-of-authentication.md @@ -130,7 +130,7 @@ end 仅在发出请求之前检查作用域是不够的，因为用户可能会在检查与实际请求之间的时间段更改作用域。 如果发生这种情况，您期望成功的 API 调用可能会以 `404` 或 `401` 状态失败，或者返回不同的信息子集。 -为了帮助您妥善处理这些情况，使用有效令牌发出请求的所有 API 响应还包含一个 [`X-OAuth-Scopes` 标头][oauth scopes]。 此标头包含用于发出请求的令牌的作用域列表。 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 %}. 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 +为了帮助您妥善处理这些情况，使用有效令牌发出请求的所有 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 %} 的端点。 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 #### 发出经过身份验证的请求 diff --git a/translations/zh-CN/content/rest/guides/delivering-deployments.md b/translations/zh-CN/content/rest/guides/delivering-deployments.md index 3b0bb2d3b3..1ff1132109 100644 --- a/translations/zh-CN/content/rest/guides/delivering-deployments.md +++ b/translations/zh-CN/content/rest/guides/delivering-deployments.md @@ -13,7 +13,7 @@ versions: -The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with the capability to launch them on a server that you own. 结合 [状态 API][status API]，您将能够在您的代码到达 `master` 时协调部署。 +[部署 API][deploy API] 为您托管在 {% data variables.product.product_name %} 上的项目提供在您自己的服务器上启动它们的功能。 结合 [状态 API][status API]，您将能够在您的代码到达 `master` 时协调部署。 本指南将使用该 API 来演示您可以使用的设置。 在我们的场景中，我们将： 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 a7439ee421..ed2f846fec 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 @@ -373,7 +373,7 @@ $ {% data variables.product.api_url_pre %}/users/defunkt [nanoc]: http://nanoc.ws/ [gitignore templates]: https://github.com/github/gitignore [issues-api]: /rest/reference/issues -[link-header]: http://www.w3.org/wiki/LinkHeader/ +[link-header]: https://www.w3.org/wiki/LinkHeader [conditional-requests]: /rest#conditional-requests [rate-limiting]: /rest#rate-limiting [rate-limiting]: /rest#rate-limiting diff --git a/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md b/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md index 66e547c176..fa7fce061e 100644 --- a/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/zh-CN/content/rest/guides/rendering-data-as-graphs.md @@ -232,7 +232,7 @@ erb :lang_freq, :locals => { :languages => languages.to_json} ] ``` -Since we already have a list of repositories above, let's inspect each one, and call [the language listing API method][language API]: +我们在前面已经获取了仓库列表，现在我们来检查每个仓库，然后调用[语言列表 API 方法][language API]： ``` ruby repos.each do |repo| @@ -264,7 +264,7 @@ end language_bytes = [ :name => "language_bytes", :elements => language_byte_count] ``` -(For more information on D3 tree map magic, check out [this simple tutorial][language API].) +（有关 D3 树图魔方的更多信息，请查看[这个简单教程][language API]。） 最后，我们将这些 JSON 信息传递到同一个 ERB 模板： diff --git a/translations/zh-CN/content/rest/guides/working-with-comments.md b/translations/zh-CN/content/rest/guides/working-with-comments.md index 314974c3d7..4eeb0dcb38 100644 --- a/translations/zh-CN/content/rest/guides/working-with-comments.md +++ b/translations/zh-CN/content/rest/guides/working-with-comments.md @@ -18,7 +18,7 @@ versions: ### 拉取请求注释 -To access comments on a Pull Request, you'll go through [the Issues API][issues]. 乍一看这似乎不符合直觉。 但是，一旦您理解了拉取请求只是一个带有代码的议题，使用议题 API 来创建拉取请求注释就合情合理了。 +要访问拉取请求的注释，需要通过[议题 API][issues]。 乍一看这似乎不符合直觉。 但是，一旦您理解了拉取请求只是一个带有代码的议题，使用议题 API 来创建拉取请求注释就合情合理了。 我们将通过使用 [Octokit.rb][octokit.rb] 创建一个 Ruby 脚本来演示如何获取拉取请求注释 您还需要创建[个人访问令牌][personal token]。 @@ -44,7 +44,7 @@ end ### 拉取请求行注释 -在差异视图中，您可以开始讨论在拉取请求中进行的某个更改的特定方面。 这些注释出现在已更改文件中的各个行上。 The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API]. +在差异视图中，您可以开始讨论在拉取请求中进行的某个更改的特定方面。 这些注释出现在已更改文件中的各个行上。 此讨论的端点 URL 来自[拉取请求审查 API][PR Review API]。 以下代码将获取文件中所做的所有拉取请求注释（给定一个拉取请求编号）： @@ -70,7 +70,7 @@ end ### 提交注释 -最后一类注释专门针对单个提交。 For this reason, they make use of [the commit comment API][commit comment API]. +最后一类注释专门针对单个提交。 因此，它们使用 [提交注释 API][commit comment API]。 要检索对提交的注释，您需要使用该提交的 SHA1。 换句话说，您不能使用与拉取请求相关的任何标识符。 例如： diff --git a/translations/zh-CN/content/rest/overview/api-previews.md b/translations/zh-CN/content/rest/overview/api-previews.md index 9324186a13..42ae4326b2 100644 --- a/translations/zh-CN/content/rest/overview/api-previews.md +++ b/translations/zh-CN/content/rest/overview/api-previews.md @@ -53,7 +53,7 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} ### 集成 -通过 API 管理[集成](/early-access/integrations/)。 +通过 API 管理[集成](/v3/integrations)。 **自定义媒体类型：** `machine-man-preview` **公布日期：** [2016-09-14](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/) {% endif %} diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md index 9b4e697d88..9a52655193 100644 --- a/translations/zh-CN/content/rest/overview/libraries.md +++ b/translations/zh-CN/content/rest/overview/libraries.md @@ -72,7 +72,7 @@ Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/githu ### Python -Library name | Repository |---|---| **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) +Library name | Repository |---|---| **ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi) **PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) **libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas) **github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) **sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction) **agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub) **octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) **github-flask**|[github-flask (Oficial Website)](http://github-flask.readthedocs.org) **torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub) ### Ruby diff --git a/translations/zh-CN/content/rest/overview/media-types.md b/translations/zh-CN/content/rest/overview/media-types.md index 74ad097b26..f69d31cf0b 100644 --- a/translations/zh-CN/content/rest/overview/media-types.md +++ b/translations/zh-CN/content/rest/overview/media-types.md @@ -21,7 +21,7 @@ API 支持的最基本媒体类型是： application/json application/vnd.github+json -Neither of these specify a [version][versions], so you will always get the current default JSON representation of resources. +这两者都没有指定[版本][versions]，因此您总是会获取资源的当前默认 JSON 表示形式。 {% note %} @@ -57,7 +57,7 @@ $ -H "Accept: application/vnd.github.v3.full+json" ### 注释正文属性 -The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues](/rest/reference/issues), [issue comments](/rest/reference/issues#comments), [pull request comments](/rest/reference/pulls#comments), and the [gist comments](/rest/reference/gists#comments) APIs all accept these same media types: +注释正文可采用 [GitHub Flavored Markdown][gfm] 编写，[议题](/rest/reference/issues)、[议题注释](/rest/reference/issues#comments)、[拉取请求注释](/rest/reference/pulls#comments)和 [gist 注释](/rest/reference/gists#comments) API 都接受以下媒体类型： #### Raw @@ -85,7 +85,7 @@ The body of a comment can be written in [GitHub Flavored Markdown][gfm], [issues ### Git blob 属性 -The following media types are allowed when [getting a blob](/rest/reference/git#get-a-blob): +[获取 Blob](/rest/reference/git#get-a-blob) 时允许使用以下媒体类型： #### JSON @@ -102,7 +102,7 @@ The following media types are allowed when [getting a blob](/rest/reference/git# ### 提交、提交比较和拉取请求 -The [commits API](/rest/reference/repos#commits) and [pull requests API](/rest/reference/pulls) support [diff][git-diff] and [patch][git-patch] formats: +[提交 API](/rest/reference/repos#commits) 和[拉取请求 API](/rest/reference/pulls) 支持 [diff][git-diff] 和 [patch][git-patch] 格式： #### 差异 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 ab864346b6..0f2bd8f8a8 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 @@ -262,13 +262,15 @@ API v3 尽可能对每个操作使用适当的 HTTP 请求方法。 ### 分页 -默认情况下，如果请求返回了多个项，将按每页最多 30 项进行分页。 您可以使用 `?page` 参数指定更多页面。 对于某些资源，您还可以使用 `?per_page` 参数设置自定义页面大小，每页最多 100 项。 请注意，由于技术原因，并非所有端点都遵循 `?per_page` 参数，相关示例请参阅[事件](/rest/reference/activity#events)。 +默认情况下，如果请求返回了多个项，将按每页最多 30 项进行分页。 您可以使用 `page` 参数指定更多页面。 对于某些资源，您还可以使用 `per_page` 参数设置自定义页面大小，每页最多 100 项。 请注意，由于技术原因，并非所有端点都遵循 `per_page` 参数，相关示例请参阅[事件](/rest/reference/activity#events)。 ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -请注意，页码从 1 开始，省略 `?page` 参数将返回第一页。 +请注意，页码从 1 开始，省略 `page` 参数将返回第一页。 + +有些端点使用基于光标的分页。 光标是指向结果集中位置的字符串。 使用基于光标的分页时，结果集中没有固定的“页”概念，因此无法导航到特定页面。 相反，您可以使用 `before` 或 `after` 参数遍历结果。 有关分页的更多信息，请查看我们的[分页浏览][pagination-guide]指南。 @@ -280,13 +282,17 @@ $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' {% endnote %} -[链接标头](http://tools.ietf.org/html/rfc5988)包括分页信息： +[链接标头](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" _该示例包括换行符，以提高可读性。_ +或者，如果端点使用基于光标的分页： + + Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next", + 此 `Link` 响应标头包含一个或多个[超媒体](/rest#hypermedia)链接关系，其中一些可能需要扩展为 [URI 模板](http://tools.ietf.org/html/rfc6570)。 可能的 `rel` 值为： @@ -312,7 +318,7 @@ _该示例包括换行符，以提高可读性。_ {% data reusables.enterprise.rate_limit %} -请注意[搜索 API 具有自定义速率限制规则](/rest/reference/search#rate-limit)。 +请注意，[搜索 API 具有自定义速率限制规则](/rest/reference/search#rate-limit)。 任何 API 请求返回的 HTTP 标头都显示当前速率限制状态： diff --git a/translations/zh-CN/content/rest/overview/troubleshooting.md b/translations/zh-CN/content/rest/overview/troubleshooting.md index c137e1005a..96007b0ff8 100644 --- a/translations/zh-CN/content/rest/overview/troubleshooting.md +++ b/translations/zh-CN/content/rest/overview/troubleshooting.md @@ -52,7 +52,7 @@ curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos #### 调用 OAuth 授权 API -如果要调用 [OAuth 授权 API](/enterprise-server@2.22/rest/reference/oauth-authorizations) 来管理 OAuth 应用的授权或生成访问令牌，类似于以下示例： +如果要调用 [OAuth 授权 API](/enterprise-server/rest/reference/oauth-authorizations) 来管理 OAuth 应用的授权或生成访问令牌，类似于以下示例： ```bash curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}' diff --git a/translations/zh-CN/content/rest/reference/enterprise-admin.md b/translations/zh-CN/content/rest/reference/enterprise-admin.md index 0b24d3ffb0..178a87a9d3 100644 --- a/translations/zh-CN/content/rest/reference/enterprise-admin.md +++ b/translations/zh-CN/content/rest/reference/enterprise-admin.md @@ -57,6 +57,16 @@ http(s)://hostname/ {% endif %} +{% if currentVersion == "free-pro-team@latest" %} + +## 审核日志 + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'audit-log' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + {% if currentVersion == "free-pro-team@latest" %} ## 计费 diff --git a/translations/zh-CN/content/rest/reference/index.md b/translations/zh-CN/content/rest/reference/index.md index ba8904d11c..20946eb805 100644 --- a/translations/zh-CN/content/rest/reference/index.md +++ b/translations/zh-CN/content/rest/reference/index.md @@ -15,8 +15,6 @@ versions: {% link_in_list /apps %} {% link_in_list /billing %} {% link_in_list /checks %} - - {% link_in_list /codes-of-conduct %} {% link_in_list /code-scanning %} {% link_in_list /emojis %} @@ -39,6 +37,7 @@ versions: {% link_in_list /repos %} {% link_in_list /scim %} {% link_in_list /search %} +{% link_in_list /secret-scanning %} {% link_in_list /teams %} {% link_in_list /users %} {% link_in_list /permissions-required-for-github-apps %} diff --git a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md index 2752545fd5..af95c2692b 100644 --- a/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/zh-CN/content/rest/reference/permissions-required-for-github-apps.md @@ -819,10 +819,19 @@ _团队_ * [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (:write) * [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (:write) - {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +### 对于“密码扫描警报”的权限 + +- [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (:read) + +- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (:read) + +- [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (:write) +{% endif %} + +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} ### 有关“安全事件”的权限 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read) diff --git a/translations/zh-CN/content/rest/reference/search.md b/translations/zh-CN/content/rest/reference/search.md index db9ed681d3..94e770d74f 100644 --- a/translations/zh-CN/content/rest/reference/search.md +++ b/translations/zh-CN/content/rest/reference/search.md @@ -10,7 +10,7 @@ versions: 搜索 API 可帮助您搜索要查找的特定条目。 例如，您可以在仓库中找到用户或特定文件。 就像您在 Google 上执行搜索一样。 它旨在帮助您找到要查找的一个或几个结果。 就像在 Google 上搜索一样，有时您希望查看几页搜索结果，以便找到最能满足您需求的条目。 为了满足这一需求， {% data variables.product.product_name %} 搜索 API **为每个搜索提供最多 1,000 个结果**。 -您可以使用查询缩小搜索范围。 To learn more about the search query syntax, see "[Constructing a search query](/rest/reference/search#constructing-a-search-query)." +您可以使用查询缩小搜索范围。 要了解有关搜索查询语法的更多信息，请查看“[构建搜索查询](/rest/reference/search#constructing-a-search-query)”。 ### 排列搜索结果 @@ -18,7 +18,7 @@ versions: ### 速率限制 -搜索 API 有自定义速率限制。 For requests using [Basic Authentication](/rest#authentication), [OAuth](/rest#authentication), or [client ID and secret](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications), you can make up to 30 requests per minute. 对于未经身份验证的请求，速率限制允许您每分钟最多提出 10 个请求。 +搜索 API 有自定义速率限制。 对于使用[基本身份验证](/rest#authentication)、[OAuth](/rest#authentication) 或[客户端 ID 和密码](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications)的请求，您每分钟最多可以提出 30 个请求。 对于未经身份验证的请求，速率限制允许您每分钟最多提出 10 个请求。 {% data reusables.enterprise.rate_limit %} @@ -40,7 +40,7 @@ SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N GitHub Octocat in:readme user:defunkt ``` -**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. 例如： +**注意：** 请务必使用语言的首选 HTML 编码器构造查询字符串。 例如： ```javascript // JavaScript const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); diff --git a/translations/zh-CN/content/rest/reference/secret-scanning.md b/translations/zh-CN/content/rest/reference/secret-scanning.md new file mode 100644 index 0000000000..7fcffc99ca --- /dev/null +++ b/translations/zh-CN/content/rest/reference/secret-scanning.md @@ -0,0 +1,12 @@ +--- +title: 秘密扫描 +versions: + free-pro-team: '*' + enterprise-server: '>=3.1' +--- + +{% data reusables.secret-scanning.api-beta %} + +{% data variables.product.prodname_secret_scanning %} API 可让您从私有仓库检索和更新密码扫描警告。 有关私有仓库的密码扫描的更多信息，请参阅“[保护仓库](/github/administering-a-repository/securing-your-repository)”。 + +{% include rest_operations_at_current_path %} diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml index 2428be2110..c0848ab578 100644 --- a/translations/zh-CN/data/glossaries/external.yml +++ b/translations/zh-CN/data/glossaries/external.yml @@ -390,7 +390,7 @@ - term: main description: >- - 默认开发分支。只要创建 Git 仓库，就会创建一个名为 "main" 的分支，并且它会变为活动的分支。大多数情况下，这包含本地开发，但纯属惯例，而非必需。 + The default development branch. Whenever you create a Git repository, a branch named `main` is created, and becomes the active branch. In most cases, this contains the local development, though that is purely by convention and is not required. - term: master description: >- diff --git a/translations/zh-CN/data/products.yml b/translations/zh-CN/data/products.yml index d076566a91..70673aae60 100644 --- a/translations/zh-CN/data/products.yml +++ b/translations/zh-CN/data/products.yml @@ -5,10 +5,12 @@ productsInOrder: - github - 管理员 + - 讨论 - 操作 - 包 - developers - rest - graphql - insights + - education - desktop diff --git a/translations/zh-CN/data/release-notes/2-20/0.yml b/translations/zh-CN/data/release-notes/2-20/0.yml new file mode 100644 index 0000000000..5623123354 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/0.yml @@ -0,0 +1,44 @@ +--- +date: '2020-02-11' +sections: + features: + - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' + - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' + security_fixes: + - Packages have been updated to the latest security versions. + bugs: + - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' + - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" + - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' + - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" + - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' + - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' + - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' + - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' + - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' + - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' + - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' + - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' + changes: + - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' + - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' + - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' + - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' + - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' + - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' + - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/1.yml b/translations/zh-CN/data/release-notes/2-20/1.yml new file mode 100644 index 0000000000..e303f5525e --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/1.yml @@ -0,0 +1,21 @@ +--- +date: '2020-02-27' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' + bugs: + - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' + - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' + - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' + - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/10.yml b/translations/zh-CN/data/release-notes/2-20/10.yml new file mode 100644 index 0000000000..58a38245c0 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/10.yml @@ -0,0 +1,21 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' + - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" + - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/11.yml b/translations/zh-CN/data/release-notes/2-20/11.yml new file mode 100644 index 0000000000..0bdd30cf96 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/11.yml @@ -0,0 +1,19 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/12.yml b/translations/zh-CN/data/release-notes/2-20/12.yml new file mode 100644 index 0000000000..5b286392f5 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/12.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' + bugs: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' + changes: + - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/13.yml b/translations/zh-CN/data/release-notes/2-20/13.yml new file mode 100644 index 0000000000..7388ff5103 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/13.yml @@ -0,0 +1,22 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/14.yml b/translations/zh-CN/data/release-notes/2-20/14.yml new file mode 100644 index 0000000000..d33fe2b58d --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/14.yml @@ -0,0 +1,13 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/15.yml b/translations/zh-CN/data/release-notes/2-20/15.yml new file mode 100644 index 0000000000..aa3c664487 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/15.yml @@ -0,0 +1,24 @@ +date: '2020-08-26' +sections: + security_fixes: + - >- + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, + https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} + - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + bugs: + - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' + changes: + - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/16.yml b/translations/zh-CN/data/release-notes/2-20/16.yml new file mode 100644 index 0000000000..4ca63bc213 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/16.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/17.yml b/translations/zh-CN/data/release-notes/2-20/17.yml new file mode 100644 index 0000000000..5f3bf87a25 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/17.yml @@ -0,0 +1,13 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/18.yml b/translations/zh-CN/data/release-notes/2-20/18.yml new file mode 100644 index 0000000000..3aab7ba337 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/18.yml @@ -0,0 +1,26 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/19.yml b/translations/zh-CN/data/release-notes/2-20/19.yml new file mode 100644 index 0000000000..b686131852 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/19.yml @@ -0,0 +1,14 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/2.yml b/translations/zh-CN/data/release-notes/2-20/2.yml new file mode 100644 index 0000000000..78e2faa7e1 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/2.yml @@ -0,0 +1,28 @@ +--- +date: '2020-03-10' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' + bugs: + - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' + - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' + - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' + - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' + - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' + - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' + - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' + - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' + - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' + changes: + - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/20.yml b/translations/zh-CN/data/release-notes/2-20/20.yml new file mode 100644 index 0000000000..0cf4def9e0 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/20.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/21.yml b/translations/zh-CN/data/release-notes/2-20/21.yml new file mode 100644 index 0000000000..4b970a92ee --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/21.yml @@ -0,0 +1,15 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/22.yml b/translations/zh-CN/data/release-notes/2-20/22.yml new file mode 100644 index 0000000000..099ce93b0d --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/22.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/3.yml b/translations/zh-CN/data/release-notes/2-20/3.yml new file mode 100644 index 0000000000..23c25312e5 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/3.yml @@ -0,0 +1,15 @@ +--- +date: '2020-03-12' +sections: + bugs: + - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/4.yml b/translations/zh-CN/data/release-notes/2-20/4.yml new file mode 100644 index 0000000000..0f06a203cd --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/4.yml @@ -0,0 +1,18 @@ +--- +date: '2020-03-25' +sections: + bugs: + - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' + - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' + - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' + - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/5.yml b/translations/zh-CN/data/release-notes/2-20/5.yml new file mode 100644 index 0000000000..44115fdc71 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/5.yml @@ -0,0 +1,20 @@ +--- +date: '2020-04-07' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' + bugs: + - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' + - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' + - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' + - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/6.yml b/translations/zh-CN/data/release-notes/2-20/6.yml new file mode 100644 index 0000000000..568f19954f --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/6.yml @@ -0,0 +1,27 @@ +--- +date: '2020-04-23' +sections: + security_fixes: + - '**HIGH**: OpenSSL has been updated to address [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 %}' + - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' + - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' + bugs: + - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' + - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' + - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' + - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" + - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' + - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' + changes: + - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' + - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% 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: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/7.yml b/translations/zh-CN/data/release-notes/2-20/7.yml new file mode 100644 index 0000000000..b377d90b66 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/7.yml @@ -0,0 +1,21 @@ +--- +date: '2020-05-05' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' + bugs: + - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' + - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' + - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' + - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' + - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/8.yml b/translations/zh-CN/data/release-notes/2-20/8.yml new file mode 100644 index 0000000000..510bf779fb --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/8.yml @@ -0,0 +1,20 @@ +--- +date: '2020-05-19' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' + bugs: + - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' + - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' + - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' + - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' + - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-20/9.yml b/translations/zh-CN/data/release-notes/2-20/9.yml new file mode 100644 index 0000000000..326818d711 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-20/9.yml @@ -0,0 +1,17 @@ +--- +date: '2020-06-02' +sections: + security_fixes: + - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' + bugs: + - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/0.yml b/translations/zh-CN/data/release-notes/2-21/0.yml new file mode 100644 index 0000000000..cfd8a069f8 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/0.yml @@ -0,0 +1,72 @@ +--- +date: '2020-06-09' +sections: + features: + - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' + - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' + - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' + - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' + - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + security_fixes: + - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' + bugs: + - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" + - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' + - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' + - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' + - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' + - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' + - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" + - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' + - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' + - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' + - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' + - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' + - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' + - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' + - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' + - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' + - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' + - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' + - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' + - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' + - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' + - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' + changes: + - 'The web notifications interface, including new [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' + - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' + - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' + - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' + - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' + - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' + - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' + - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' + - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' + - 'Admins can [enable security alerts](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' + - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' + - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' + - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' + - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' + - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' + - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' + - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' + - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' + - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' + - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' + - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/1.yml b/translations/zh-CN/data/release-notes/2-21/1.yml new file mode 100644 index 0000000000..9b802bd1f3 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/1.yml @@ -0,0 +1,20 @@ +--- +date: '2020-06-23' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' + bugs: + - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' + - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' + - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" + - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' + - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' + - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/10.yml b/translations/zh-CN/data/release-notes/2-21/10.yml new file mode 100644 index 0000000000..65b5d9c64c --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/10.yml @@ -0,0 +1,15 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' + bugs: + - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/11.yml b/translations/zh-CN/data/release-notes/2-21/11.yml new file mode 100644 index 0000000000..ce20fbe36a --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/11.yml @@ -0,0 +1,18 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' + - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" + - 'Packages have been updated to the latest security versions. {% 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: + - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' + - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/12.yml b/translations/zh-CN/data/release-notes/2-21/12.yml new file mode 100644 index 0000000000..c347bb7aca --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/12.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' + bugs: + - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' + - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' + - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/13.yml b/translations/zh-CN/data/release-notes/2-21/13.yml new file mode 100644 index 0000000000..06e910bb50 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/13.yml @@ -0,0 +1,19 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/2.yml b/translations/zh-CN/data/release-notes/2-21/2.yml new file mode 100644 index 0000000000..bdac746dbc --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/2.yml @@ -0,0 +1,20 @@ +--- +date: '2020-07-09' +sections: + security_fixes: + - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' + bugs: + - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' + - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' + - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' + - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' + - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/3.yml b/translations/zh-CN/data/release-notes/2-21/3.yml new file mode 100644 index 0000000000..dd4ccbbb5e --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/3.yml @@ -0,0 +1,17 @@ +--- +date: '2020-07-21' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% 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: + - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' + - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' + - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/4.yml b/translations/zh-CN/data/release-notes/2-21/4.yml new file mode 100644 index 0000000000..e90460c88e --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/4.yml @@ -0,0 +1,27 @@ +--- +date: '2020-08-11' +sections: + security_fixes: + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**HIGH:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' + bugs: + - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' + - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' + - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' + - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" + - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' + - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' + - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' + - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' + - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' + - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' + - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/5.yml b/translations/zh-CN/data/release-notes/2-21/5.yml new file mode 100644 index 0000000000..444cf28527 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/5.yml @@ -0,0 +1,15 @@ +--- +date: '2020-08-12' +sections: + bugs: + - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' + - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' + - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/6.yml b/translations/zh-CN/data/release-notes/2-21/6.yml new file mode 100644 index 0000000000..8638d1d9cd --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/6.yml @@ -0,0 +1,26 @@ +date: '2020-08-26' +sections: + security_fixes: + - >- + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, + https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} + - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + bugs: + - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' + - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' + changes: + - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/7.yml b/translations/zh-CN/data/release-notes/2-21/7.yml new file mode 100644 index 0000000000..69134720e7 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/7.yml @@ -0,0 +1,14 @@ +--- +date: '2020-09-08' +sections: + bugs: + - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' + - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/8.yml b/translations/zh-CN/data/release-notes/2-21/8.yml new file mode 100644 index 0000000000..b7bf410b13 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/8.yml @@ -0,0 +1,16 @@ +--- +date: '2020-09-23' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' + bugs: + - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-21/9.yml b/translations/zh-CN/data/release-notes/2-21/9.yml new file mode 100644 index 0000000000..46656c9e6b --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-21/9.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' + - 'Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' + - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' + - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' + - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' + - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' + - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' + - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' + - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' + - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' + changes: + - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' + - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' + - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/2-22/0.yml b/translations/zh-CN/data/release-notes/2-22/0.yml new file mode 100644 index 0000000000..cb67278fca --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-22/0.yml @@ -0,0 +1,130 @@ +--- +intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. +date: '2020-09-23' +sections: + features: + - + heading: GitHub Actions Beta + notes: + - | + [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. + + You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} + - + heading: GitHub Packages Beta + notes: + - | + [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. + + Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} + - + heading: Advanced Security Code Scanning Beta + notes: + - | + [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. + + Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} + - + heading: Pull Request Retargeting + notes: + - | + When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} + - + heading: Suspend and Unsuspend an App Installation + notes: + - | + Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' + - + heading: Improved Large Scale Performance + notes: + - | + We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% 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 %}'' + + Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} + - + heading: View All of Your Users + notes: + - | + For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](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: Administration Changes + notes: + - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} + - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} + - 'It''s now possible to [manage global announcements and expiration dates through the enterprise account settings](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 %}' + - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} + - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} + - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% 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 %} + - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} + - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} + - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% 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: Security Changes + notes: + - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} + - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](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 %} + - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} + - + heading: Developer Changes + notes: + - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' + - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} + - 'Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' + - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} + - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' + - + heading: Users and organizations can add Twitter usernames to their GitHub profiles + notes: + - '[Developers and organizations can now add their Twitter username to their profile](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: API Changes + notes: + - | + #### Graduated Previews + + The following previews are now an official part of the API: + * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} + * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} + - | + #### GraphQL Schema Changes + + * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. + bugs: + - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} + - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} + - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} + - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} + - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} + deprecations: + - + heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 + notes: + - '**GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020** That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' + - + heading: Deprecation of Legacy GitHub App Webhook Events + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of Legacy GitHub Apps Endpoint + notes: + - 'Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' + - + heading: Deprecation of OAuth Application API + notes: + - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). + #- type: Backup and Disaster recovery + #note: GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} + - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} + - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a 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 %}' + - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} + - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/zh-CN/data/release-notes/2-22/1.yml b/translations/zh-CN/data/release-notes/2-22/1.yml new file mode 100644 index 0000000000..fbd3988c3d --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-22/1.yml @@ -0,0 +1,71 @@ +--- +date: '2020-10-09' +sections: + security_fixes: + - '**MEDIUM**: ImageMagick has been updated to address [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 %}' + - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' + - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' + bugs: + - | + The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} + - | + Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} + - | + Saving settings via the [management console](https://docs.github.com/en/enterprise-server@latest/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](https://docs.github.com/en/enterprise-server@latest/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} + - | + System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} + - | + The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} + - | + `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} + - | + Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} + - | + Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} + - | + Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} + - | + When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} + - | + The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} + - | + OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} + - | + Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} + - | + On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} + - | + When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} + - | + When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} + - | + Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} + - | + Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} + - | + The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} + - | + Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} + - | + A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} + - | + When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} + - | + [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} + - | + GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management 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: + - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} + - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} + - GitHub App Manifests now include the `request_oauth_on_install` field. {% 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: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/zh-CN/data/release-notes/2-22/2.yml b/translations/zh-CN/data/release-notes/2-22/2.yml new file mode 100644 index 0000000000..dc36b39e12 --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-22/2.yml @@ -0,0 +1,29 @@ +--- +date: '2020-10-20' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} + bugs: + - | + If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} + - | + A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} + - | + On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} + - | + When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} + - | + Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} + - | + The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} + - | + On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/zh-CN/data/release-notes/2-22/3.yml b/translations/zh-CN/data/release-notes/2-22/3.yml new file mode 100644 index 0000000000..45442a5d4b --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-22/3.yml @@ -0,0 +1,23 @@ +--- +date: '2020-11-03' +sections: + security_fixes: + - | + **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} + - | + **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} + - | + Packages have been updated to the latest security versions. {% 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: + - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} + - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} + - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} + - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} + - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} + - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/zh-CN/data/release-notes/2-22/4.yml b/translations/zh-CN/data/release-notes/2-22/4.yml new file mode 100644 index 0000000000..e97737ee0b --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-22/4.yml @@ -0,0 +1,16 @@ +--- +date: '2020-11-17' +sections: + security_fixes: + - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} + bugs: + - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} + - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} + - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} + - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} + known_issues: + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} + - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} + - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} + - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} diff --git a/translations/zh-CN/data/release-notes/2-22/5.yml b/translations/zh-CN/data/release-notes/2-22/5.yml new file mode 100644 index 0000000000..0520df862f --- /dev/null +++ b/translations/zh-CN/data/release-notes/2-22/5.yml @@ -0,0 +1,22 @@ +--- +date: '2020-12-03' +sections: + bugs: + - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' + - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' + - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' + - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' + - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' + - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' + - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' + - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' + - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' + - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' + - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' + - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' + known_issues: + - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/zh-CN/data/reusables/accounts/create-account.md b/translations/zh-CN/data/reusables/accounts/create-account.md new file mode 100644 index 0000000000..17623a48ab --- /dev/null +++ b/translations/zh-CN/data/reusables/accounts/create-account.md @@ -0,0 +1,2 @@ +1. 转到 {% data variables.product.product_name %} 的 [Pricing（定价）]({% data variables.product.pricing_url %})页面。 +2. 阅读关于 {% data variables.product.product_name %} 提供的不同产品和订阅的信息，然后单击您想要选择的订阅下的升级按钮。 diff --git a/translations/zh-CN/data/reusables/actions/actions-not-verified.md b/translations/zh-CN/data/reusables/actions/actions-not-verified.md index 1ef0ecac63..f56e55afbc 100644 --- a/translations/zh-CN/data/reusables/actions/actions-not-verified.md +++ b/translations/zh-CN/data/reusables/actions/actions-not-verified.md @@ -1 +1 @@ -任何人都可以在 {% data variables.product.prodname_marketplace %} 中发布操作。 {% data variables.product.prodname_dotcom %} 会验证一些合作伙伴组织，但与验证的应用程序不同，{% data variables.product.prodname_dotcom %} 不审查或验证 {% data variables.product.prodname_marketplace %} 中列出的个别操作。 +任何人都可以在 {% data variables.product.prodname_marketplace %} 中发布操作。 {% data variables.product.prodname_dotcom %} verifies some partner organizations and these are shown as verified creators. diff --git a/translations/zh-CN/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/zh-CN/data/reusables/actions/actions-packages-set-spending-limit.md new file mode 100644 index 0000000000..1be2ccb65f --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/actions-packages-set-spending-limit.md @@ -0,0 +1 @@ +You can set a specific spending limit or, for some accounts, allow unlimited spending. 支出限额适用于 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 的总超支额。 diff --git a/translations/zh-CN/data/reusables/actions/visualization-beta.md b/translations/zh-CN/data/reusables/actions/visualization-beta.md new file mode 100644 index 0000000000..ee3ad11ef4 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/visualization-beta.md @@ -0,0 +1,7 @@ +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +{% note %} + +**Note:** The workflow visualization graph for {% data variables.product.prodname_actions %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/apps/beta_feature_activation.md b/translations/zh-CN/data/reusables/apps/beta_feature_activation.md index d8d97b47f6..21197116ad 100644 --- a/translations/zh-CN/data/reusables/apps/beta_feature_activation.md +++ b/translations/zh-CN/data/reusables/apps/beta_feature_activation.md @@ -1,2 +1,2 @@ -4. In the left sidebar, click **Beta Features**. ![GitHub 应用程序或 OAuth 应用程序部分](/assets/images/github-apps/beta-features-option.png) +4. 在左边栏中，单击 **Beta Features（测试版功能）**。 ![GitHub 应用程序或 OAuth 应用程序部分](/assets/images/github-apps/beta-features-option.png) 5. 在您要为应用程序启用的测试版功能旁边，单击“**Opt-in（加入）**。。 ![用于启用测试版功能的选择加入按钮](/assets/images/github-apps/enable-beta-features.png) diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-api-info.md b/translations/zh-CN/data/reusables/audit_log/audit-log-api-info.md new file mode 100644 index 0000000000..55728a1692 --- /dev/null +++ b/translations/zh-CN/data/reusables/audit_log/audit-log-api-info.md @@ -0,0 +1,5 @@ +* Access to your organization or repository settings +* Changes in permissions +* Added or removed users in an organization, repository, or team +* Users being promoted to admin +* Changes to permissions of a {% data variables.product.prodname_github_app %} diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/zh-CN/data/reusables/audit_log/audit-log-git-events-retention.md new file mode 100644 index 0000000000..3f1584bf91 --- /dev/null +++ b/translations/zh-CN/data/reusables/audit_log/audit-log-git-events-retention.md @@ -0,0 +1 @@ +The audit log retains Git events for 7 days. This is shorter than other audit log events, which can be retained for 90 days. diff --git a/translations/zh-CN/data/reusables/classroom/about-assignments.md b/translations/zh-CN/data/reusables/classroom/about-assignments.md new file mode 100644 index 0000000000..65a3506229 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/about-assignments.md @@ -0,0 +1 @@ +Each assignment has a title and an optional deadline. You can choose the visibility of repositories that {% data variables.product.prodname_classroom %} creates and choose access permissions. You can also automatically grade assignments and create a dedicated space to discuss the assignment with the student. diff --git a/translations/zh-CN/data/reusables/classroom/about-autograding.md b/translations/zh-CN/data/reusables/classroom/about-autograding.md new file mode 100644 index 0000000000..04ed2b067c --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/about-autograding.md @@ -0,0 +1 @@ +You can use autograding to automatically check a student's work for an assignment on {% data variables.product.prodname_classroom %}. You configure tests for an assignment, and the tests run immediately every time a student pushes to an assignment repository on {% data variables.product.product_location %}. The student can view the test results, make changes, and push to see new results. diff --git a/translations/zh-CN/data/reusables/classroom/about-classrooms.md b/translations/zh-CN/data/reusables/classroom/about-classrooms.md new file mode 100644 index 0000000000..5d19bbb44a --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/about-classrooms.md @@ -0,0 +1 @@ +A classroom in {% data variables.product.prodname_classroom %} is where teachers and students interact during a course. Teachers can create a student roster for the classroom, then create, assign, review, and grade assignments within the classroom. diff --git a/translations/zh-CN/data/reusables/classroom/about-online-ides.md b/translations/zh-CN/data/reusables/classroom/about-online-ides.md new file mode 100644 index 0000000000..43818e691f --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/about-online-ides.md @@ -0,0 +1 @@ +You can optionally configure an assignment to use an online integrated development environment (IDE). Online IDEs allow your students to write code, run programs, and collaborate in a browser, without installing Git and a full development toolchain on the student's computer. If you choose an online IDE for an assignment, students can still check out and run code locally on a computer with the necessary software. diff --git a/translations/zh-CN/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/zh-CN/data/reusables/classroom/assignments-classroom-prerequisite.md new file mode 100644 index 0000000000..06284dad51 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-classroom-prerequisite.md @@ -0,0 +1 @@ +You must create a classroom before you can create an assignment. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)." diff --git a/translations/zh-CN/data/reusables/classroom/assignments-click-pencil.md b/translations/zh-CN/data/reusables/classroom/assignments-click-pencil.md new file mode 100644 index 0000000000..820afd5260 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-click-pencil.md @@ -0,0 +1 @@ +1. To the right of the assignment you want to edit, click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing assignment in list of assignments](/assets/images/help/classroom/assignments-click-pencil.png) diff --git a/translations/zh-CN/data/reusables/classroom/assignments-group-definition.md b/translations/zh-CN/data/reusables/classroom/assignments-group-definition.md new file mode 100644 index 0000000000..3143cddc70 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-group-definition.md @@ -0,0 +1 @@ +A group assignment is collaborative coursework for groups of students on {% data variables.product.prodname_classroom %}. diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-assign-a-deadline.md new file mode 100644 index 0000000000..6e8e29cc11 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-assign-a-deadline.md @@ -0,0 +1,5 @@ +Optionally, you can assign a deadline to the assignment. Under "Deadline (optional)", click in the text field, then use the date picker to assign a deadline. + +
      + Date picker for assignment deadline +
      diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-an-online-ide.md new file mode 100644 index 0000000000..54858178a5 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -0,0 +1,5 @@ +To choose an online IDE for the assignment, select the **Select an online IDE** drop-down menu, then click the IDE you'd like your students to use. + +
      + Using the 'Select an online IDE' drop-down menu to click an online IDE for the assignment +
      diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-template-repository.md new file mode 100644 index 0000000000..15bcb66cb5 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-template-repository.md @@ -0,0 +1,5 @@ +Under "Add a template repository to give students starter code", select the **Select a repository** drop-down, then type a search query. In the list of results, click the template repository you'd like to use for starter code. + +
      + Using the 'Select a repository' drop-down menu to find a template repository to use as starter code for an assignment +
      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 new file mode 100644 index 0000000000..3f4f17e1b2 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -0,0 +1,9 @@ +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)." + +Under "Repository visibility", select a visibility. Optionally, select **Grant students admin access to their repository**. + +
      + Visibility options for assignment repositories +
      diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-click-continue-after-basics.md new file mode 100644 index 0000000000..b82d19fe8e --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-click-continue-after-basics.md @@ -0,0 +1,7 @@ +
      + +When you're done, click **Continue** to configure starter code and a development environment for the assignment. + +
      + 'Continue' button +
      diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md new file mode 100644 index 0000000000..4607b61065 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md @@ -0,0 +1,7 @@ +
      + +When you're done, click **Continue** to configure automatic grading and feedback for the project. + +
      + 'Continue' button +
      diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-click-create-assignment-button.md new file mode 100644 index 0000000000..935d73f5df --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-click-create-assignment-button.md @@ -0,0 +1,5 @@ +To create the assignment, click **Create assignment**. + +
      + 'Create assignment' button +
      diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-create-review-pull-request.md new file mode 100644 index 0000000000..5cc14ee9ff --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-create-review-pull-request.md @@ -0,0 +1,5 @@ +To create pull requests for the discussion of feedback, select **Enable feedback pull requests**. + +
      + Checkbox for 'Enable feedback pull requests' +
      diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-create-the-assignment.md new file mode 100644 index 0000000000..051e169c57 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -0,0 +1,5 @@ +To create an assignment, sign into {% data variables.product.prodname_classroom_with_url %} and navigate to a classroom. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click **New assignment**. + +
      + The 'New assignment' button +
      diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-intro-for-environment.md new file mode 100644 index 0000000000..bda2c39723 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-intro-for-environment.md @@ -0,0 +1 @@ +Optionally, decide whether to provide empty repositories or starter code, and preconfigure a development environment for your students. diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md new file mode 100644 index 0000000000..6290d808ad --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md @@ -0,0 +1,3 @@ +{% data reusables.classroom.classroom-enables-invitation-urls %} + +{% data reusables.classroom.invitation-url-warning %} diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-prevent-changes.md new file mode 100644 index 0000000000..9ef39a18b9 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-prevent-changes.md @@ -0,0 +1,7 @@ +You can prevent students from changing files that contain tests for autograding, or other important files in the assignment repository. + +Under "Protected file paths", type relative paths within the repository to protect. + +
      + Text field for typing protected file paths +
      \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/zh-CN/data/reusables/classroom/assignments-guide-using-autograding.md new file mode 100644 index 0000000000..5f50beec64 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-guide-using-autograding.md @@ -0,0 +1,23 @@ +{% data reusables.classroom.about-autograding %} For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)." + +{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} For more information, see "[Grading methods](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods)." + +
      + Using the 'Add test' drop-down menu to click a grading method +
      + +
      + +Define the parameters of your test case, like the name, commands, inputs, outputs, timeout, and points. When you're done, click **Save test case**. + +
      + 'Save test case' button for an autograding test +
      + +
      + +You can add more tests with the **Add test** drop-down menu, and you can edit or delete existing tests with {% octicon "pencil" aria-label="The pencil icon" %} or {% octicon "trash" aria-label="The trash icon" %}. + +
      + Pencil and trash icons to edit or delete an autograding test +
      \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/classroom/assignments-individual-definition.md b/translations/zh-CN/data/reusables/classroom/assignments-individual-definition.md new file mode 100644 index 0000000000..33425ae2c3 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-individual-definition.md @@ -0,0 +1 @@ +An individual assignment is coursework for each student who participates in a course on {% data variables.product.prodname_classroom %}. The student is intended to complete an individual assignment without help from other students. diff --git a/translations/zh-CN/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/zh-CN/data/reusables/classroom/assignments-to-prevent-submission.md new file mode 100644 index 0000000000..62bd9cc2da --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-to-prevent-submission.md @@ -0,0 +1 @@ +To prevent acceptance or submission of an assignment by students, deselect **Enable assignment invitation URL**. To edit the assignment, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit assignment**. diff --git a/translations/zh-CN/data/reusables/classroom/assignments-type-a-title.md b/translations/zh-CN/data/reusables/classroom/assignments-type-a-title.md new file mode 100644 index 0000000000..20d32397ac --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/assignments-type-a-title.md @@ -0,0 +1,5 @@ +Type a title for the assignment. Optionally, click {% octicon "pencil" aria-label="The pencil icon" %} to edit the prefix. + +
      + Assignment title and prefix +
      diff --git a/translations/zh-CN/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/zh-CN/data/reusables/classroom/classroom-creates-group-repositories.md new file mode 100644 index 0000000000..10cdc5924a --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/classroom-creates-group-repositories.md @@ -0,0 +1 @@ +For each group assignment, {% data variables.product.prodname_classroom %} automatically creates a single shared repository for the team to access. The repository can be empty, or you can create the repository from a template repository with starter code, documentation, tests, and other resources. The repository belongs to your organization account on {% data variables.product.product_name %}, and {% data variables.product.prodname_classroom %} grants access to teams that students create or join when accepting the assignment. diff --git a/translations/zh-CN/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/zh-CN/data/reusables/classroom/classroom-creates-individual-repositories.md new file mode 100644 index 0000000000..4108abf9ad --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/classroom-creates-individual-repositories.md @@ -0,0 +1 @@ +When a student accepts an assignment, {% data variables.product.prodname_classroom %} automatically creates a new repository for the student. The repositories can be empty, or you can create the repositories from a template repository with starter code, documentation, tests, and other resources. Each assignment repository belongs to your organization account on {% data variables.product.product_name %}. diff --git a/translations/zh-CN/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/zh-CN/data/reusables/classroom/classroom-enables-invitation-urls.md new file mode 100644 index 0000000000..1b357c3a2d --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/classroom-enables-invitation-urls.md @@ -0,0 +1 @@ +By default, {% data variables.product.prodname_classroom %} enables an invitation URL for each assignment you create. Students can accept and submit the assignment while the invitation URL is enabled. You can share the URL with your students on your LMS, course homepage, or wherever you post assignments. Students can also navigate to the assignment on {% data variables.product.prodname_classroom %} if the student has already accepted an assignment for the classroom. diff --git a/translations/zh-CN/data/reusables/classroom/click-assignment-in-list.md b/translations/zh-CN/data/reusables/classroom/click-assignment-in-list.md new file mode 100644 index 0000000000..347d0bc108 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/click-assignment-in-list.md @@ -0,0 +1 @@ +1. In the list of assignments, click the assignment you want to view. ![Assignment in list of assignments for an classroom](/assets/images/help/classroom/click-assignment-in-list.png) diff --git a/translations/zh-CN/data/reusables/classroom/click-classroom-in-list.md b/translations/zh-CN/data/reusables/classroom/click-classroom-in-list.md new file mode 100644 index 0000000000..fe7d091cdc --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/click-classroom-in-list.md @@ -0,0 +1 @@ +1. In the list of classrooms, click the classroom you want to view. ![Classroom in list of classrooms for an organization](/assets/images/help/classroom/click-classroom-in-list.png) diff --git a/translations/zh-CN/data/reusables/classroom/click-settings.md b/translations/zh-CN/data/reusables/classroom/click-settings.md new file mode 100644 index 0000000000..9fe6b33d6b --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/click-settings.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. !["Settings" tab for classroom](/assets/images/help/classroom/click-settings.png) diff --git a/translations/zh-CN/data/reusables/classroom/click-students.md b/translations/zh-CN/data/reusables/classroom/click-students.md new file mode 100644 index 0000000000..13df0b1e40 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/click-students.md @@ -0,0 +1 @@ +1. Under the classroom name, click {% octicon "people" aria-label="The people icon" %} **Students**. !["Students" tab for classroom](/assets/images/help/classroom/click-students.png) diff --git a/translations/zh-CN/data/reusables/classroom/for-more-information-about-assignment-creation.md b/translations/zh-CN/data/reusables/classroom/for-more-information-about-assignment-creation.md new file mode 100644 index 0000000000..8fd113d763 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/for-more-information-about-assignment-creation.md @@ -0,0 +1 @@ +For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." 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 new file mode 100644 index 0000000000..d300f8fef5 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/guide-create-new-classroom.md @@ -0,0 +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. 更多信息请参阅“[从头开始创建新组织](/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. 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/zh-CN/data/reusables/classroom/invitation-url-warning.md b/translations/zh-CN/data/reusables/classroom/invitation-url-warning.md new file mode 100644 index 0000000000..f85e808ddc --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/invitation-url-warning.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning**: Be careful where you share invitation URLs. Anyone with an invitation URL for an assignment can accept the invitation and associate a user account on {% data variables.product.product_name %} with an identifier in your roster. + +{% endwarning %} diff --git a/translations/zh-CN/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/zh-CN/data/reusables/classroom/readme-contains-button-for-online-ide.md new file mode 100644 index 0000000000..fac85f79f1 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -0,0 +1 @@ +When a student accepts an assignment with an online IDE, the assignment repository will include a _README.md_ file with a special button at the top of the file. The button links the student directly to the workspace in the online IDE. diff --git a/translations/zh-CN/data/reusables/classroom/sign-into-github-classroom.md b/translations/zh-CN/data/reusables/classroom/sign-into-github-classroom.md new file mode 100644 index 0000000000..578bf7213e --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/sign-into-github-classroom.md @@ -0,0 +1 @@ +1. Sign into {% data variables.product.prodname_classroom_with_url %}. diff --git a/translations/zh-CN/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/zh-CN/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md new file mode 100644 index 0000000000..2486daf0a4 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md @@ -0,0 +1 @@ +Under "Add autograding tests", select the **Add test** drop-down menu, then click the grading method you want to use. diff --git a/translations/zh-CN/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/zh-CN/data/reusables/classroom/you-can-choose-a-template-repository.md new file mode 100644 index 0000000000..40eb9d273b --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/you-can-choose-a-template-repository.md @@ -0,0 +1 @@ +You can optionally choose a template repository as starter code for the assignment. The template repository must belong to your organization or be a public repository on {% data variables.product.product_name %}. diff --git a/translations/zh-CN/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/zh-CN/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md new file mode 100644 index 0000000000..e9592fb832 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md @@ -0,0 +1 @@ +You can automatically create a pull request where you can provide feedback and answer a student's questions about an assignment. For more information about the review of changes in a pull request, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)." diff --git a/translations/zh-CN/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md b/translations/zh-CN/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md new file mode 100644 index 0000000000..af5be0c098 --- /dev/null +++ b/translations/zh-CN/data/reusables/classroom/you-may-want-to-predefine-repository-settings.md @@ -0,0 +1 @@ +You may want to predefine the default settings for the assignment repositories that {% data variables.product.prodname_classroom %} creates from a template repository. For example, you may want to disable issues, define labels for pull requests, or protect a branch in some or all of the repositories. diff --git a/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md b/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md new file mode 100644 index 0000000000..b8d2b78cbc --- /dev/null +++ b/translations/zh-CN/data/reusables/dependabot/private-dependencies-note.md @@ -0,0 +1,3 @@ +When running version updates, {% data variables.product.prodname_dependabot %} must be able to resolve all dependencies from their source to verify that version updates have been successful. If your manifest or lock files contain any dependencies hosted in private {% data variables.product.prodname_dotcom %} repositories within your organization, {% data variables.product.prodname_dependabot %} must be able to access those repositories. Organization owners can configure this. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-repositories)." + +Currently, {% data variables.product.prodname_dependabot %} version updates doesn't support manifest or lock files that contain any dependencies hosted in private registries, or in private {% data variables.product.prodname_dotcom %} repositories that belong to a different organization than the dependent project. \ No newline at end of file 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 efc5b974bc..4164cef088 100644 --- a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md +++ b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md @@ -1,20 +1,23 @@ -| 包管理器 | 支持供应 | -| -------------------------- |:-----:| -| Bundler: `bundler` | **X** | -| Cargo: `cargo` | | -| Composer: `composer` | | -| Docker: `docker` | | -| Elm: `elm` | | -| Git 子模块：`gitsubmodule` | | -| GitHub 操作：`github-actions` | | -| Go 模块：`gomod` | **X** | -| Gradle: `gradle` | | -| Maven: `maven` | | -| Mix: `mix` | | -| npm: `npm` | | -| NuGet: `nuget` | | -| pip: `pip` | | -| Terraform: `terraform` | | +The following table shows, for each package manager, whether {% data variables.product.prodname_dependabot %} supports: dependencies in private {% data variables.product.prodname_dotcom %} repositories, and vendored dependencies. + +| 包管理器 | Private {% data variables.product.prodname_dotcom %} repositories | Vendoring | +| -------------------------- |:-----------------------------------------------------------------:|:---------:| +| Bundler: `bundler` | | **✓** | +| Cargo: `cargo` | **✓** | | +| Composer: `composer` | **✓** | | +| Docker: `docker` | **✓** | | +| Elixir: `hex` | | | +| Elm: `elm` | **✓** | | +| Git 子模块：`gitsubmodule` | **✓** | | +| GitHub 操作：`github-actions` | **✓** | | +| Go 模块：`gomod` | **✓** | **✓** | +| Gradle: `gradle` | **✓** | | +| Maven: `maven` | **✓** | | +| Mix: `mix` | **✓** | | +| npm: `npm` | **✓** | | +| NuGet: `nuget` | **✓** | | +| pip: `pip` | | | +| Terraform: `terraform` | **✓** | | {% note %} diff --git a/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md b/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md new file mode 100644 index 0000000000..a17ca2ca53 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md @@ -0,0 +1 @@ +All discussions must be created in a category, and repository administrators and maintainers define the categories for a repository. Categories can contain open-ended conversations, or conversations with a question/answer format. diff --git a/translations/zh-CN/data/reusables/discussions/about-discussions.md b/translations/zh-CN/data/reusables/discussions/about-discussions.md new file mode 100644 index 0000000000..c61b8b0f0a --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/about-discussions.md @@ -0,0 +1 @@ +Discussions are an open forum for conversation among maintainers and the community for a project on {% data variables.product.product_name %}. diff --git a/translations/zh-CN/data/reusables/discussions/beta.md b/translations/zh-CN/data/reusables/discussions/beta.md new file mode 100644 index 0000000000..cd030287a9 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/beta.md @@ -0,0 +1,5 @@ +{% note %} + +**注意：**{% data variables.product.prodname_discussions %} 目前处于测试阶段，可能会更改。 + +{% endnote %} diff --git a/translations/zh-CN/data/reusables/discussions/click-discussion-in-list.md b/translations/zh-CN/data/reusables/discussions/click-discussion-in-list.md new file mode 100644 index 0000000000..8156c86331 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/click-discussion-in-list.md @@ -0,0 +1 @@ +1. In the list of discussions, click the discussion you want to view. ![Discussion in list of discussions for a repository](/assets/images/help/discussions/click-discussion-in-list.png) diff --git a/translations/zh-CN/data/reusables/discussions/discussions-tab.md b/translations/zh-CN/data/reusables/discussions/discussions-tab.md new file mode 100644 index 0000000000..67795aa5ae --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/discussions-tab.md @@ -0,0 +1 @@ +1. Under your repository name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. !["Discussions" tab for a repository](/assets/images/help/discussions/repository-discussions-tab.png) diff --git a/translations/zh-CN/data/reusables/discussions/edit-categories.md b/translations/zh-CN/data/reusables/discussions/edit-categories.md new file mode 100644 index 0000000000..6f4f6af574 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/edit-categories.md @@ -0,0 +1 @@ +1. To the right of "Categories", click {% octicon "pencil" aria-label="The pencil icon" %}. ![Pencil icon for editing categories](/assets/images/help/discussions/click-edit-categories.png) diff --git a/translations/zh-CN/data/reusables/discussions/edit-category-details.md b/translations/zh-CN/data/reusables/discussions/edit-category-details.md new file mode 100644 index 0000000000..8004b70314 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/edit-category-details.md @@ -0,0 +1 @@ +Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." diff --git a/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md new file mode 100644 index 0000000000..8c89711e18 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -0,0 +1,5 @@ +You can enable or disable discussions for a repository. + +{% data reusables.repositories.navigate-to-repo %} +1. 在仓库名称下，单击 {% octicon "gear" aria-label="The gear icon" %} **Settings（设置）**。 ![仓库设置按钮](/assets/images/help/discussions/public-repo-settings.png) +1. Under "Features", select **Discussions**. ![Checkbox under "Features" for enabling or disabling discussions for a repository](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/zh-CN/data/reusables/discussions/github-recognizes-members.md b/translations/zh-CN/data/reusables/discussions/github-recognizes-members.md new file mode 100644 index 0000000000..b6874b910d --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/github-recognizes-members.md @@ -0,0 +1 @@ +{% data variables.product.prodname_dotcom %} will automatically recognize community members who contribute the most comments marked as answers to discussions with a question/answer format. diff --git a/translations/zh-CN/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/zh-CN/data/reusables/discussions/marking-a-comment-as-an-answer.md new file mode 100644 index 0000000000..bdefffdea0 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/marking-a-comment-as-an-answer.md @@ -0,0 +1,14 @@ +You can mark a comment in the discussion as an answer to the discussion if a discussion is within a category that accepts answers. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + +When you mark a question as an answer, {% data variables.product.product_name %} will highlight the comment and replies to the comment to help visitors quickly find the answer. + +![Comment marked as answer to a discussion](/assets/images/help/discussions/comment-marked-as-answer.png) + +You can't mark a threaded comment in response to a comment as the answer to a discussion. You also can't mark a minimized comment as the answer to a discussion. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the unanswered discussion you want to mark as answered. ![Unanswered discussion](/assets/images/help/discussions/unanswered-discussion.png) +1. In the discussion, find the comment you want to mark as the answer. +1. In the upper-right corner of the comment, click {% octicon "check-circle" aria-label="The circular check icon" %}. !["Mark as answer" circular check icon for marking comment as answer in a discussion](/assets/images/help/discussions/comment-mark-as-answer-button.png) +1. Optionally, to unmark a comment as the answer, click {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}. diff --git a/translations/zh-CN/data/reusables/discussions/repository-category-limit.md b/translations/zh-CN/data/reusables/discussions/repository-category-limit.md new file mode 100644 index 0000000000..293d3632b5 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/repository-category-limit.md @@ -0,0 +1 @@ +Each repository can have up to 10 categories. diff --git a/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md b/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md new file mode 100644 index 0000000000..242e3abf9b --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md @@ -0,0 +1,6 @@ +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +1. Click **New discussion**. !["New discussion" button within the "Discussions" tab for a repository](/assets/images/help/discussions/new-discussion-button.png) +1. Select the **Select Category** drop-down menu, and click a category for your discussion. !["Select Category" drop-down menu and list of available categories in a repository](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) +1. Type a title and body for your discussion. ![Text fields for new discussion's title and body](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) +1. Click **Start discussion**. !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png) diff --git a/translations/zh-CN/data/reusables/discussions/you-can-categorize-discussions.md b/translations/zh-CN/data/reusables/discussions/you-can-categorize-discussions.md new file mode 100644 index 0000000000..bb05316d77 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/you-can-categorize-discussions.md @@ -0,0 +1 @@ +You can categorize discussions to help community members begin conversations in the right place, and to help community members find related discussions. diff --git a/translations/zh-CN/data/reusables/discussions/you-can-convert-an-issue.md b/translations/zh-CN/data/reusables/discussions/you-can-convert-an-issue.md new file mode 100644 index 0000000000..1421256e1f --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/you-can-convert-an-issue.md @@ -0,0 +1 @@ +If an issue turns out to be a question or open-ended conversation instead of a work item to track and prioritize, you can convert the issue to a discussion. diff --git a/translations/zh-CN/data/reusables/discussions/you-can-use-discussions.md b/translations/zh-CN/data/reusables/discussions/you-can-use-discussions.md new file mode 100644 index 0000000000..27c1ba7cb2 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/you-can-use-discussions.md @@ -0,0 +1 @@ +You can use discussions to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/discussions/you-cannot-convert-a-discussion.md b/translations/zh-CN/data/reusables/discussions/you-cannot-convert-a-discussion.md new file mode 100644 index 0000000000..9e9b687b67 --- /dev/null +++ b/translations/zh-CN/data/reusables/discussions/you-cannot-convert-a-discussion.md @@ -0,0 +1 @@ +You cannot convert a discussion to an issue. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/zh-CN/data/reusables/dotcom_billing/actions-packages-unpaid-account.md index 7e91b528c1..c4716abc76 100644 --- a/translations/zh-CN/data/reusables/dotcom_billing/actions-packages-unpaid-account.md +++ b/translations/zh-CN/data/reusables/dotcom_billing/actions-packages-unpaid-account.md @@ -2,4 +2,4 @@ * 您的帐户中包含的 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 存储空间或分钟数将不会重置，直到付款处理成功。 * 如果在当前计费周期内，帐户中有剩余的存储空间或分钟数，则 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 将继续可用，直到所含用量全部用完。 -* 如果在当前计费周期内，帐户中所含的 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 用量已用完，则 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 都将被禁用，以防进一步超限。 如果您通过发票支付帐户，必须[联系我们的帐户管理团队](https://enterprise.github.com/contact)处理付款并重置您的使用。 +* 如果在当前计费周期内，帐户中所含的 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 用量已用完，则 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_registry %} 都将被禁用，以防进一步超限。 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 dc0184a992..faea1133c4 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 %}](https://education.github.com/partners/schools)”。 +在申请个人折扣之前，请检查您的学习社区是否已作为 {% data variables.product.prodname_education %} 学校与我们合作。 更多信息请参阅“[关于 {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education/about-github-education)”。 diff --git a/translations/zh-CN/data/reusables/education/apply-for-team.md b/translations/zh-CN/data/reusables/education/apply-for-team.md index 6d3465c33a..85c543c340 100644 --- a/translations/zh-CN/data/reusables/education/apply-for-team.md +++ b/translations/zh-CN/data/reusables/education/apply-for-team.md @@ -1 +1 @@ -- 申请免费 [{% data variables.product.prodname_team %}](/articles/github-s-products)，允许无限制的用户和私有仓库。 更多信息请参阅“[申请教育者或研究人员折扣](/articles/applying-for-an-educator-or-researcher-discount)”。 +- 申请免费 [{% data variables.product.prodname_team %}](/articles/github-s-products)，允许无限制的用户和私有仓库。 For more information, see "[Apply for an educator or researcher discount](/education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount)." diff --git a/translations/zh-CN/data/reusables/education/click-get-teacher-benefits.md b/translations/zh-CN/data/reusables/education/click-get-teacher-benefits.md new file mode 100644 index 0000000000..25bbacd747 --- /dev/null +++ b/translations/zh-CN/data/reusables/education/click-get-teacher-benefits.md @@ -0,0 +1 @@ +1. Under "Individuals", click **Get teacher benefits**. !["Get teacher benefits" on {% data variables.product.prodname_education %} homepage](/assets/images/help/education/click-get-teacher-benefits.png) diff --git a/translations/zh-CN/data/reusables/education/educator-requirements.md b/translations/zh-CN/data/reusables/education/educator-requirements.md new file mode 100644 index 0000000000..622a132a62 --- /dev/null +++ b/translations/zh-CN/data/reusables/education/educator-requirements.md @@ -0,0 +1,6 @@ +To apply for an educator or researcher discount, you must meet the following requirements. + +- 是教育者、教师或研究人员. +- 具有学校分发的可验证电子邮件地址. +- 上传证明您的学校隶属关系文件. +- Have a user account on {% data variables.product.product_name %}. diff --git a/translations/zh-CN/data/reusables/gated-features/discussions.md b/translations/zh-CN/data/reusables/gated-features/discussions.md new file mode 100644 index 0000000000..5ada0a25ee --- /dev/null +++ b/translations/zh-CN/data/reusables/gated-features/discussions.md @@ -0,0 +1 @@ +{% data variables.product.prodname_discussions %} is available in beta for public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/zh-CN/data/reusables/github-actions/actions-billing.md b/translations/zh-CN/data/reusables/github-actions/actions-billing.md index a1a5b6ea45..027a6b7f42 100644 --- a/translations/zh-CN/data/reusables/github-actions/actions-billing.md +++ b/translations/zh-CN/data/reusables/github-actions/actions-billing.md @@ -1 +1 @@ -公共仓库和自托管运行器免费使用 {% data variables.product.prodname_actions %}。 对于私有仓库，每个 {% data variables.product.prodname_dotcom %} 帐户可获得一定数量的免费记录和存储，具体取决于帐户所使用的产品。 +公共仓库和自托管运行器免费使用 {% data variables.product.prodname_actions %}。 对于私有仓库，每个 {% data variables.product.prodname_dotcom %} 帐户可获得一定数量的免费记录和存储，具体取决于帐户所使用的产品。 Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md b/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md index 21cfadcdcd..0e618e3f82 100644 --- a/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md +++ b/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -##### **使用单一事件的示例** +##### 使用单一事件的示例 ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -##### **使用事件列表的示例** +##### 使用事件列表的示例 ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -##### **使用具有活动类型或配置的多个事件示例** +##### 使用具有活动类型或配置的多个事件示例 如果您需要为一个事件指定活动类型或配置，必须分别配置每个事件。 您必须为所有事件附加冒号 (`: diff --git a/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-brief.md new file mode 100644 index 0000000000..20d912fb21 --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-detailed.md new file mode 100644 index 0000000000..1d056800e2 --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/actions-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.github-actions.actions-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where a workflow is run. 您帐户中的任何优惠券都不适用于 {% data variables.product.prodname_actions %} 超额费用。 diff --git a/translations/zh-CN/data/reusables/github-actions/contacting-support.md b/translations/zh-CN/data/reusables/github-actions/contacting-support.md index 4079291be1..b86167e223 100644 --- a/translations/zh-CN/data/reusables/github-actions/contacting-support.md +++ b/translations/zh-CN/data/reusables/github-actions/contacting-support.md @@ -1,4 +1,4 @@ -如果需要任何与工作流程配置相关的帮助，比如语法、{% data variables.product.prodname_dotcom %} 托管的运行器或构建操作，请在 [{% data variables.product.prodname_gcf %} 的 {% data variables.product.prodname_actions %} 版面](https://github.community/c/github-actions)中查找现有主题或发起一个新主题。 +If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} category](https://github.community/c/code-to-cloud/github-actions/41). 如果您有对 {% data variables.product.prodname_actions %} 的反馈或功能请求，请在 {% data variables.contact.contact_feedback_actions %} 中分享。 diff --git a/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md b/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md index 71d92ad12b..e6db4f8803 100644 --- a/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/zh-CN/data/reusables/github-actions/macos-runner-preview.md @@ -1,5 +1,5 @@ {% note %} -**注：**MacOS 11.0 虚拟环境目前仅作为预览提供。 `macos-latest` YAML 工作流程标签仍使用 MacOS 10.15 虚拟环境。 +**Note:** The macOS 11.0 virtual environment is currently provided as a preview only. The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment. {% endnote %} diff --git a/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md index 265f721712..2343033949 100644 --- a/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md +++ b/translations/zh-CN/data/reusables/github-actions/publish-to-maven-workflow-step.md @@ -1 +1 @@ -运行 `mvn -B deploy` 命令以发布到 `ossrh` 仓库。 `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 +Runs the `mvn --batch-mode deploy` command to publish to the `ossrh` repository. `MAVEN_USERNAME` 环境变量将使用 `OSSRH_USERNAME` 密码的内容设置，而 `MAVEN_PASSWORD` 环境变量将使用 `OSSRH_TOKEN` 密码的内容设置。 diff --git a/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md index cce03eee8d..e025f2b31f 100644 --- a/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ b/translations/zh-CN/data/reusables/github-actions/publish-to-packages-workflow-step.md @@ -1 +1 @@ -运行 `mvn -B deploy` 命令以发布到 {% data variables.product.prodname_registry %}。 `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 +Runs the `mvn --batch-mode deploy` command to publish to {% data variables.product.prodname_registry %}. `GITHUB_TOKEN` 环境变量将使用 `GITHUB_TOKEN` 密码的内容设置。 diff --git a/translations/zh-CN/data/reusables/github-insights/download-latest-release.md b/translations/zh-CN/data/reusables/github-insights/download-latest-release.md index 03d98b7e1d..e480cb08d5 100644 --- a/translations/zh-CN/data/reusables/github-insights/download-latest-release.md +++ b/translations/zh-CN/data/reusables/github-insights/download-latest-release.md @@ -1,3 +1,3 @@ -1. 从应用程序服务器中 `github/insights-releases` 的[发行版页面](https://github.com/github/insights-releases/releases/latest)上，找到 {% data variables.product.prodname_insights %} 的最新版本。 +1. From the application server, navigate to the latest release of {% data variables.product.prodname_insights %} on the Releases page for `github/insights-releases`. 2. 要下载最新版本，请在“Assets（资产）”下单击 `insights-VERSION.tar.gz`。 ![安装资产](/assets/images/help/insights/installation-tgz.png) 3. 解压缩目录。 diff --git a/translations/zh-CN/data/reusables/marketplace/app-transfer-to-org-for-verification.md b/translations/zh-CN/data/reusables/marketplace/app-transfer-to-org-for-verification.md new file mode 100644 index 0000000000..0621a9e6e9 --- /dev/null +++ b/translations/zh-CN/data/reusables/marketplace/app-transfer-to-org-for-verification.md @@ -0,0 +1 @@ +If you want to sell an app that's owned by your user account, first you'll need to transfer the app to an organization, and then request verification for a listing created by the organization. diff --git a/translations/zh-CN/data/reusables/marketplace/free-plan-note.md b/translations/zh-CN/data/reusables/marketplace/free-plan-note.md new file mode 100644 index 0000000000..bf63caa53d --- /dev/null +++ b/translations/zh-CN/data/reusables/marketplace/free-plan-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** If you're listing an app on {% data variables.product.prodname_marketplace %}, you can't list your app with a free pricing plan if you offer a paid service outside of {% data variables.product.prodname_marketplace %}. + +{% endnote %} diff --git a/translations/zh-CN/data/reusables/marketplace/launch-with-free.md b/translations/zh-CN/data/reusables/marketplace/launch-with-free.md index a2e184b5d4..2151c241cc 100644 --- a/translations/zh-CN/data/reusables/marketplace/launch-with-free.md +++ b/translations/zh-CN/data/reusables/marketplace/launch-with-free.md @@ -1 +1 @@ -您可以提交未经验证和经过验证的应用程序。 这将允许您使用免费版本的应用程序启动。 GitHub 验证您的应用程序后，该程序在 {% data variables.product.prodname_marketplace %} 中的上架状态将从未经验证变为经过验证，GitHub 将发布您的新定价计划。 +You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the verified creator badge and any paid pricing plans when you complete verification and financial onboarding. diff --git a/translations/zh-CN/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/zh-CN/data/reusables/marketplace/marketplace-billing-ui-requirements.md index 591ad2f4c8..b5936198c3 100644 --- a/translations/zh-CN/data/reusables/marketplace/marketplace-billing-ui-requirements.md +++ b/translations/zh-CN/data/reusables/marketplace/marketplace-billing-ui-requirements.md @@ -1,7 +1,7 @@ -- 取消从 {% data variables.product.prodname_marketplace %} 购买的付费计划的客户必须被自动降级到该应用程序的免费计划（如果有）。 {% data reusables.marketplace.cancellation-clarification %} 强烈建议允许客户重新启用他们以前的计划。 -- 如果您用以下格式提供[升级 URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls)，客户必须能够从应用程序的 UI 升级：`https://www.github.com/marketplace//upgrade//` -- 如果客户购买了席位（单位定价计划）或支持无限协作者的计划，他们必须能够修改哪些用户可以从应用程序的网站访问应用程序。 -- 客户必须能够在应用程序网站的帐单、个人资料或帐户设置部分立即看到其帐户的以下变动： +- Customers who cancel a paid plan purchased from {% data variables.product.prodname_marketplace %} should be automatically downgraded to the app's free plan if it exists. {% data reusables.marketplace.cancellation-clarification %} 强烈建议允许客户重新启用他们以前的计划。 +- Customers should be able to upgrade from your app's user interface if you provide an [upgrade URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in this format: `https://www.github.com/marketplace//upgrade//` +- Customers should be able to modify which users have access to your app from your app's website if they purchased seats (per-unit pricing plan) or the plan offers unlimited collaborators. +- Customers should be able to see the following changes to their account immediately in the billing, profile, or account settings section of the app's website: - 当前计划和价格。 - 购买的新计划。 - 升级、降级、取消以及免费试用剩余天数。 diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md b/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md index 238385f0f7..75645f5826 100644 --- a/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md +++ b/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md @@ -3,7 +3,7 @@ {% if currentVersion == "free-pro-team@latest" %} 要使用 {% data variables.product.prodname_actions %} 工作流程验证： -- 对于包注册表 (`PACKAGE-REGISTRY.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`)，您可以使用 `GITHUB_TOKEN`。 +- 对于包注册表 (`PACKAGE-REGISTRY.pkg.github.com`)，您可以使用 `GITHUB_TOKEN`。 - 对于容器注册表 (`ghcr.io/OWNER/IMAGE-NAME`)，必须使用个人访问令牌。 {% else %} 要 diff --git a/translations/zh-CN/data/reusables/package_registry/billing-for-container-registry.md b/translations/zh-CN/data/reusables/package_registry/billing-for-container-registry.md index b2d32c4c84..f35936bf72 100644 --- a/translations/zh-CN/data/reusables/package_registry/billing-for-container-registry.md +++ b/translations/zh-CN/data/reusables/package_registry/billing-for-container-registry.md @@ -1,3 +1,3 @@ -在 {% data variables.product.prodname_github_container_registry %} 测试期间，新的 {% data variables.product.prodname_container_registry %} 和现有的 {% data variables.product.prodname_registry %} Docker 注册表都是免费的。 有关 {% data variables.product.prodname_registry %} Docker 注册表的更多信息，请参阅“[配置 Docker 与 {% data variables.product.prodname_registry %} 一起使用](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)”。 +在 {% data variables.product.prodname_github_container_registry %} 测试期间，新的 {% data variables.product.prodname_container_registry %} 和现有的 {% data variables.product.prodname_registry %} Docker 注册表都是免费的。 有关 {% data variables.product.prodname_registry %} Docker 注册表的更多信息，请参阅“[配置 Docker 与 {% data variables.product.prodname_registry %} 一起使用](/packages/guides/configuring-docker-for-use-with-github-packages)”。 测试后，其他 {% 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)”。 diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-beta-billing-note.md b/translations/zh-CN/data/reusables/package_registry/container-registry-beta-billing-note.md index 8403f7a36c..479d469629 100644 --- a/translations/zh-CN/data/reusables/package_registry/container-registry-beta-billing-note.md +++ b/translations/zh-CN/data/reusables/package_registry/container-registry-beta-billing-note.md @@ -1,5 +1,5 @@ {% note %} -**容器映像存储的计费更新：** 在 {% data variables.product.prodname_github_container_registry %} 的测试版阶段，Docker 映像存储和带宽对旧 `docker.pkg.github.com` 和新 `ghcr.io` 服务是免费的。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)”。 +**容器映像存储的计费更新：** 在 {% data variables.product.prodname_github_container_registry %} 的测试版阶段，Docker 映像存储和带宽对旧 `docker.pkg.github.com` 和新 `ghcr.io` 服务是免费的。 更多信息请参阅“[关于 {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)”。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md b/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md index 57de6c3ba3..9ca5a7c5e6 100644 --- a/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md +++ b/translations/zh-CN/data/reusables/package_registry/container-registry-beta.md @@ -1,5 +1,5 @@ {% note %} -**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" and "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**注：**{% data variables.product.prodname_github_container_registry %} 目前处于公测阶段，可能会更改。 在测试阶段，存储和带宽是免费的。 To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/guides/about-github-container-registry)" and "[Enabling improved container support](/packages/guides/enabling-improved-container-support)." {% endnote %} 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 2df9364c31..a23fdc598b 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/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" and "[Getting started with {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry)."{% endif %} +**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 %} {% endwarning %} diff --git a/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md b/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md index b0cddc8bcb..75bd1537f3 100644 --- a/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md +++ b/translations/zh-CN/data/reusables/package_registry/feature-preview-for-container-registry.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)." +**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. 更多信息请参阅“[启用改进的容器支持](/packages/guides/enabling-improved-container-support)”。 {% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/package_registry/packages-billing.md b/translations/zh-CN/data/reusables/package_registry/packages-billing.md index e403ef07c1..3d870ad218 100644 --- a/translations/zh-CN/data/reusables/package_registry/packages-billing.md +++ b/translations/zh-CN/data/reusables/package_registry/packages-billing.md @@ -1 +1 @@ -公共包免费使用 {% data variables.product.prodname_registry %}。 对于私有包，每个 {% data variables.product.product_name %} 帐户可获得一定数量的免费存储和数据传输，具体取决于帐户所使用的产品。 默认情况下，您的帐户支出限额为 0 美元，这将防止您在达到包含的限额后额外使用存储或数据传输。 如果您的支出限额高于默认的 0 美元，您将会收到额外存储或数据传输的帐单，也称为超限费用，最高可达到您的支出限额。 您帐户中的任何优惠券都不适用于 {% data variables.product.prodname_registry %} 超额费用。 +公共包免费使用 {% data variables.product.prodname_registry %}。 对于私有包，每个 {% data variables.product.product_name %} 帐户可获得一定数量的免费存储和数据传输，具体取决于帐户所使用的产品。 Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/zh-CN/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/zh-CN/data/reusables/package_registry/packages-spending-limit-brief.md new file mode 100644 index 0000000000..ea07621d29 --- /dev/null +++ b/translations/zh-CN/data/reusables/package_registry/packages-spending-limit-brief.md @@ -0,0 +1 @@ +If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you pay your account by invoice, your account will have an unlimited default spending limit. diff --git a/translations/zh-CN/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/zh-CN/data/reusables/package_registry/packages-spending-limit-detailed.md new file mode 100644 index 0000000000..fffd151df9 --- /dev/null +++ b/translations/zh-CN/data/reusables/package_registry/packages-spending-limit-detailed.md @@ -0,0 +1,3 @@ +{% data reusables.package_registry.packages-spending-limit-brief %} + +If you have an unlimited spending limit or a spending limit set higher than $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. 您帐户中的任何优惠券都不适用于 {% data variables.product.prodname_registry %} 超额费用。 diff --git a/translations/zh-CN/data/reusables/package_registry/required-scopes.md b/translations/zh-CN/data/reusables/package_registry/required-scopes.md index da146e9e6b..10a6a7ad46 100644 --- a/translations/zh-CN/data/reusables/package_registry/required-scopes.md +++ b/translations/zh-CN/data/reusables/package_registry/required-scopes.md @@ -1 +1 @@ -您必须使用具有适当范围的个人访问令牌才可在 {% data variables.product.prodname_registry %} 中发布和安装。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)”。 +您必须使用具有适当范围的个人访问令牌才可在 {% data variables.product.prodname_registry %} 中发布和安装。 更多信息请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)”。 diff --git a/translations/zh-CN/data/reusables/package_registry/viewing-packages.md b/translations/zh-CN/data/reusables/package_registry/viewing-packages.md index 4c3437645d..f8810c3049 100644 --- a/translations/zh-CN/data/reusables/package_registry/viewing-packages.md +++ b/translations/zh-CN/data/reusables/package_registry/viewing-packages.md @@ -1 +1 @@ -在发布包后，您可以在 {% data variables.product.prodname_dotcom %} 上查看该包。 更多信息请参阅“[查看包](/packages/publishing-and-managing-packages/viewing-packages)”。 +在发布包后，您可以在 {% data variables.product.prodname_dotcom %} 上查看该包。 更多信息请参阅“[查看包](/packages/manage-packages/viewing-packages)”。 diff --git a/translations/zh-CN/data/reusables/repositories/dependency-review.md b/translations/zh-CN/data/reusables/repositories/dependency-review.md new file mode 100644 index 0000000000..e780074c3c --- /dev/null +++ b/translations/zh-CN/data/reusables/repositories/dependency-review.md @@ -0,0 +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)." +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/navigate-to-job-superlinter.md b/translations/zh-CN/data/reusables/repositories/navigate-to-job-superlinter.md index 944ab99357..819a92c78f 100644 --- a/translations/zh-CN/data/reusables/repositories/navigate-to-job-superlinter.md +++ b/translations/zh-CN/data/reusables/repositories/navigate-to-job-superlinter.md @@ -1,5 +1,7 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} +1. 在 **Jobs（作业）**下或可视化图中，单击您要查看的作业。 ![Lint 代码库作业](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png) +{% elsif currentVersion ver_gt "enterprise-server@2.22" %} 1. 在左侧边栏中，单击您要查看的作业。 ![Lint 代码库作业](/assets/images/help/repository/superlinter-lint-code-base-job.png) {% else %} 1. 在左侧边栏中，单击您要查看的作业。 ![选择工作流程作业](/assets/images/help/repository/workflow-job.png) -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/zh-CN/data/reusables/repositories/two-dot-diff-comparison-example-urls.md index e0fad7b0e7..1a25944892 100644 --- a/translations/zh-CN/data/reusables/repositories/two-dot-diff-comparison-example-urls.md +++ b/translations/zh-CN/data/reusables/repositories/two-dot-diff-comparison-example-urls.md @@ -1 +1 @@ -例如，此 URL 使用简短的 7 字符 SHA 代码比较提交 `c3a414e` 与 `faf7c6f`：`https://github.com/github/linguist/compare/c3a414e..faf7c6f`。 +For example, this URL uses the shortened seven-character SHA codes to compare commits `c3a414e` and `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`. diff --git a/translations/zh-CN/data/reusables/repositories/view-failed-job-results-superlinter.md b/translations/zh-CN/data/reusables/repositories/view-failed-job-results-superlinter.md index 1d84c91e8d..48099e1db4 100644 --- a/translations/zh-CN/data/reusables/repositories/view-failed-job-results-superlinter.md +++ b/translations/zh-CN/data/reusables/repositories/view-failed-job-results-superlinter.md @@ -1,5 +1,8 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. 任何失败的步骤都会自动展开以显示结果。 ![Super linter 工作流程结果](/assets/images/help/repository/super-linter-workflow-results-updated.png) +1. 任何失败的步骤都会自动展开以显示结果。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![Super linter 工作流程结果](/assets/images/help/repository/super-linter-workflow-results-updated-2.png){% else %} +![Super linter workflow results](/assets/images/help/repository/super-linter-workflow-results-updated.png){% endif %} {% else %} 1. 展开**运行 Super-Linter** 步骤以查看结果。 ![Super linter 工作流程结果](/assets/images/help/repository/super-linter-workflow-results.png) {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/view-specific-line-superlinter.md b/translations/zh-CN/data/reusables/repositories/view-specific-line-superlinter.md index bf994a6112..18606dab36 100644 --- a/translations/zh-CN/data/reusables/repositories/view-specific-line-superlinter.md +++ b/translations/zh-CN/data/reusables/repositories/view-specific-line-superlinter.md @@ -1,5 +1,10 @@ {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -1. （可选）要获取指向日志中特定行的链接，请单击该步骤的行号。 然后，您可以从 web 浏览器的地址栏中复制链接。 ![复制链接的按钮](/assets/images/help/repository/copy-link-button-updated.png) +1. （可选）要获取指向日志中特定行的链接，请单击该步骤的行号。 然后，您可以从 web 浏览器的地址栏中复制链接。 + {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} + ![复制链接的按钮](/assets/images/help/repository/copy-link-button-updated-2.png) + {% else %} + ![复制链接的按钮](/assets/images/help/repository/copy-link-button-updated.png) + {% endif %} {% else %} 1. （可选）要获取指向日志中特定行的链接，请单击该步骤的行号。 然后，您可以从 web 浏览器的地址栏中复制链接。 ![复制链接的按钮](/assets/images/help/repository/copy-link-button.png) {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/search/date_gt_lt.md b/translations/zh-CN/data/reusables/search/date_gt_lt.md index 2b09211d39..57a206f28c 100644 --- a/translations/zh-CN/data/reusables/search/date_gt_lt.md +++ b/translations/zh-CN/data/reusables/search/date_gt_lt.md @@ -1 +1 @@ -日期支持[大于、小于和范围限定符](/articles/understanding-the-search-syntax)。 +When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." diff --git a/translations/zh-CN/data/reusables/secret-scanning/api-beta.md b/translations/zh-CN/data/reusables/secret-scanning/api-beta.md new file mode 100644 index 0000000000..510473ea8d --- /dev/null +++ b/translations/zh-CN/data/reusables/secret-scanning/api-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The {% data variables.product.prodname_secret_scanning %} API is currently in beta and subject to change. + +{% endnote %} diff --git a/translations/zh-CN/data/reusables/sponsors/billing-switcher.md b/translations/zh-CN/data/reusables/sponsors/billing-switcher.md new file mode 100644 index 0000000000..4831c34a3b --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/billing-switcher.md @@ -0,0 +1 @@ +1. Optionally, to manage your sponsorship on behalf of an organization, in the upper-left corner, use the **Personal settings** drop-down menu, and click the organization. ![Drop-down menu to switch accounts for settings](/assets/images/help/sponsors/billing-account-switcher.png) diff --git a/translations/zh-CN/data/reusables/sponsors/change-tier.md b/translations/zh-CN/data/reusables/sponsors/change-tier.md index 2f6f84948e..28beec6902 100644 --- a/translations/zh-CN/data/reusables/sponsors/change-tier.md +++ b/translations/zh-CN/data/reusables/sponsors/change-tier.md @@ -1 +1 @@ -1. 在“{% data variables.product.prodname_sponsors %}”下，在被赞助开源贡献者的右侧，单击被赞助帐户旁边的 {% octicon "triangle-down" aria-label="The down triangle octicon" %}，然后单击 **Change tier（更改等级）**。 ![更改等级按钮](/assets/images/help/billing/edit-sponsor-billing.png) +1. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored account, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your tier amount, then click **Change tier**. ![更改等级按钮](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/zh-CN/data/reusables/sponsors/choose-updates.md b/translations/zh-CN/data/reusables/sponsors/choose-updates.md new file mode 100644 index 0000000000..ade59cf05b --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/choose-updates.md @@ -0,0 +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) diff --git a/translations/zh-CN/data/reusables/sponsors/manage-sponsorship.md b/translations/zh-CN/data/reusables/sponsors/manage-sponsorship.md new file mode 100644 index 0000000000..00689ed747 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/manage-sponsorship.md @@ -0,0 +1 @@ +1. To the right of your current tier, click **Manage**. ![管理赞助按钮](/assets/images/help/sponsors/manage-your-sponsorship-button.png) \ No newline at end of file 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 new file mode 100644 index 0000000000..0cd08d5382 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/manage-updates-for-orgs.md @@ -0,0 +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)." diff --git a/translations/zh-CN/data/reusables/sponsors/maximum-tier.md b/translations/zh-CN/data/reusables/sponsors/maximum-tier.md index 7505c500a4..ce4d0360b9 100644 --- a/translations/zh-CN/data/reusables/sponsors/maximum-tier.md +++ b/translations/zh-CN/data/reusables/sponsors/maximum-tier.md @@ -1 +1 @@ -最高价格为每月 6000 美元。 +最高价格为每月 12,000 美元。 diff --git a/translations/zh-CN/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/zh-CN/data/reusables/sponsors/navigate-to-sponsored-account.md new file mode 100644 index 0000000000..def70f43f1 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/navigate-to-sponsored-account.md @@ -0,0 +1 @@ +1. On {% data variables.product.product_name %}, navigate to the sponsored account's profile. diff --git a/translations/zh-CN/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/zh-CN/data/reusables/sponsors/navigate-to-sponsors-dashboard.md new file mode 100644 index 0000000000..7920429321 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/navigate-to-sponsors-dashboard.md @@ -0,0 +1,2 @@ +1. 在任何页面的右上角，单击您的个人资料照片，然后单击 **{% data variables.product.prodname_sponsors %}**。 ![{% data variables.product.prodname_sponsors %} 按钮](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) +2. If a list of your sponsored and eligible accounts is shown, to the right of the account you want to manage, click **Dashboard**. ![开发者赞助者仪表板按钮](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) diff --git a/translations/zh-CN/data/reusables/sponsors/no-fees.md b/translations/zh-CN/data/reusables/sponsors/no-fees.md index 9135ecbfed..9f3119de50 100644 --- a/translations/zh-CN/data/reusables/sponsors/no-fees.md +++ b/translations/zh-CN/data/reusables/sponsors/no-fees.md @@ -1 +1 @@ -{% data variables.product.prodname_sponsors %} 不从用户帐户收取赞助费，因此这些赞助 100% 会转到被赞助的开发者或组织。 +{% data variables.product.prodname_sponsors %} 不从用户帐户收取赞助费，因此这些赞助 100% 会转到被赞助的开发者或组织。 The 10% fee for sponsorships from organizations is waived during the beta. diff --git a/translations/zh-CN/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/zh-CN/data/reusables/sponsors/org-sponsors-release-phase.md new file mode 100644 index 0000000000..75983073a4 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/org-sponsors-release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Sponsoring on behalf of an organization is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md b/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md new file mode 100644 index 0000000000..f201de957c --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/pay-prorated-amount.md @@ -0,0 +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 diff --git a/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md b/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md index 6c920908fd..56a047d867 100644 --- a/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md +++ b/translations/zh-CN/data/reusables/sponsors/prorated-sponsorship.md @@ -1 +1 @@ -您将立即被收取下一个固定结算日期之前的金额（按时间比例计算）。 +If you're sponsoring on behalf of your user account, you will immediately be charged a prorated amount for the time until your next regular billing date. If you're sponsoring on behalf of an organization, you can choose to pay the prorated amount or make the full monthly payment. diff --git a/translations/zh-CN/data/reusables/sponsors/sponsor-account.md b/translations/zh-CN/data/reusables/sponsors/sponsor-account.md new file mode 100644 index 0000000000..5f6d921d2d --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/sponsor-account.md @@ -0,0 +1 @@ +1. Click **Sponsor _ACCOUNT_**. ![赞助按钮](/assets/images/help/sponsors/sponsor-developer-button.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/sponsors/sponsorship-dashboard.md b/translations/zh-CN/data/reusables/sponsors/sponsorship-dashboard.md new file mode 100644 index 0000000000..e730f9e0a7 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/sponsorship-dashboard.md @@ -0,0 +1,4 @@ +1. Navigate to your sponsorship dashboard for the account. + - If you're sponsoring a user account, under the user's name, click **Sponsoring**. ![赞助按钮](/assets/images/help/profile/sponsoring-button.png) + - If you're sponsoring an organization, to the right of the organization's name, click **Sponsoring**. ![赞助按钮](/assets/images/help/sponsors/org-sponsoring-button.png) +1. Optionally, to manage a sponsorship on behalf of an organization, on the right side of the page, use the **Sponsoring as** drop-down menu, and click the organization. ![Drop-down menu to choose the account you're sponsoring as](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png) diff --git a/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md b/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md index b1a997d1bb..28cc3635f6 100644 --- a/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md +++ b/translations/zh-CN/data/reusables/sponsors/sponsorship-details.md @@ -1 +1 @@ -拥有 {% data variables.product.product_name %} 帐户的任何人都可通过每月定期付款来赞助拥有被赞助开发者个人资料或被赞助组织档案的任何人。 有多个赞助等级可供选择，每月支付金额和福利由被赞助开发者或组织设定。 您的赞助将分享您帐户的现有帐单日期、付款方式和收据。 +You can sponsor anyone with a sponsored developer profile or sponsored organization profile on behalf of your user account or an organization. You can choose from multiple sponsorship tiers, with monthly payment amounts and benefits that are set by the sponsored account. 您的赞助将分享您帐户的现有帐单日期、付款方式和收据。 diff --git a/translations/zh-CN/data/reusables/user-settings/marketplace_apps.md b/translations/zh-CN/data/reusables/user-settings/marketplace_apps.md index 40792d90e3..8e01a3e23c 100644 --- a/translations/zh-CN/data/reusables/user-settings/marketplace_apps.md +++ b/translations/zh-CN/data/reusables/user-settings/marketplace_apps.md @@ -1,4 +1,4 @@ {% if currentVersion == "free-pro-team@latest" %} -1. 在左边栏中，单击 **OAuth Apps（OAuth 应用程序）**或 **GitHub Apps（GitHub 应用程序）**，具体取决于您要管理的 {% data variables.product.prodname_marketplace %} 上架信息。 **注：**您也可以通过导航到 https://github.com/marketplace/manage 来管理您的上架信息。 ![App type selection](/assets/images/settings/apps_choose_app.png) +1. 在左边栏中，单击 **OAuth Apps（OAuth 应用程序）**或 **GitHub Apps（GitHub 应用程序）**，具体取决于您要管理的 {% data variables.product.prodname_marketplace %} 上架信息。 **注：**您也可以通过导航到 https://github.com/marketplace/manage 来管理您的上架信息。 ![应用程序类型选择](/assets/images/settings/apps_choose_app.png) {% endif %} diff --git a/translations/zh-CN/data/reusables/webhooks/app_always_desc.md b/translations/zh-CN/data/reusables/webhooks/app_always_desc.md new file mode 100644 index 0000000000..12c37f4512 --- /dev/null +++ b/translations/zh-CN/data/reusables/webhooks/app_always_desc.md @@ -0,0 +1 @@ +`installation` | `object` | {% data variables.product.prodname_github_app %} 安装。 diff --git a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_properties.md new file mode 100644 index 0000000000..a58983f8a4 --- /dev/null +++ b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_properties.md @@ -0,0 +1,4 @@ +| 键 | 类型 | 描述 | +| -------- | ----- | ----------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作内容. This can be either `created`, `resolved`, or `reopened`. | +| `警报` | `对象` | The secret scanning alert involved in the event. | diff --git a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md new file mode 100644 index 0000000000..e57ad29240 --- /dev/null +++ b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md @@ -0,0 +1 @@ +Activity related to secret scanning alerts in a repository. 活动类型在有效负载对象的操作属性中指定。 For more information, see “[About secret scanning](/github/administering-a-repository/about-secret-scanning).” diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml index 8f1026a3ff..b56a5e817e 100644 --- a/translations/zh-CN/data/ui.yml +++ b/translations/zh-CN/data/ui.yml @@ -7,7 +7,7 @@ header: release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.''' localization_complete: 我们经常发布文档更新，此页面的翻译可能仍在进行中。有关最新信息，请访问英文文档。如果此页面上的翻译有问题，请告诉我们。 localization_in_progress: 你好，探索者！ 此页面正在积极开发或仍在翻译中。有关最新和最准确的信息，请访问我们的英文文档。 - early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.' + early_access: '📣 Please do not share this URL publicly. This page contains content about an early access feature.' search: need_help: 需要帮助？ placeholder: 搜索主题、产品... @@ -56,6 +56,14 @@ contribution_cta: button: 做出贡献 or: 或, to_guidelines: 了解如何参与。 +enterprise_releases_list: + title: Enterprise Server Releases + currently_supported: Currently supported + currently_supported_message: See GitHub Enterprise for information about the latest release. + deprecated: Deprecated + deprecated_message: 'These docs remain available but are no longer maintained:' + deprecated_developer: Deprecated on developer.github.com + deprecated_developer_message: 'These docs remain available on the legacy developer site but are no longer maintained:' products: graphql: reference: @@ -123,3 +131,4 @@ footer: product_landing: quick_start: 快速入门 reference_guides: 参考指南 + overview: 概览 diff --git a/translations/zh-CN/data/variables/action_code_examples.yml b/translations/zh-CN/data/variables/action_code_examples.yml index 9fe8643d56..76dd4ac209 100644 --- a/translations/zh-CN/data/variables/action_code_examples.yml +++ b/translations/zh-CN/data/variables/action_code_examples.yml @@ -1,12 +1,4 @@ --- -- - title: Starter workflows - description: Workflow files for helping people get started with GitHub Actions - languages: TypeScript - href: actions/starter-workflows - tags: - - official - - 工作流程 - title: Example services description: Example workflows using service containers @@ -334,3 +326,10 @@ - monorepo - copybara - 工作流程 +- + title: Deploy static files to GitHub Pages + description: GitHub Action to publish website to GitHub Pages automatically + languages: 'TypeScript, JavaScript' + href: peaceiris/actions-gh-pages + tags: + - publishing diff --git a/translations/zh-CN/data/variables/command_line.yml b/translations/zh-CN/data/variables/command_line.yml index 805c67903e..5d1f568716 100644 --- a/translations/zh-CN/data/variables/command_line.yml +++ b/translations/zh-CN/data/variables/command_line.yml @@ -1,5 +1,5 @@ --- -#Use this variable wherever backticks are necessary: https://github.com/github/docs-internal/pull/1176#discussion-diff-19853931 +#Use this variable wherever backticks are necessary backticks: >- {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} #Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!) diff --git a/translations/zh-CN/data/variables/discussions_community_examples.yml b/translations/zh-CN/data/variables/discussions_community_examples.yml new file mode 100644 index 0000000000..8b3594f2ec --- /dev/null +++ b/translations/zh-CN/data/variables/discussions_community_examples.yml @@ -0,0 +1,38 @@ +--- +- + #Images and descriptions are pulled directly from the repo + repo: vercel/next.js + description: The React Framework +- + repo: gatsbyjs/gatsby + description: Build blazing fast, modern apps and websites with React +- + repo: nodejs/node + description: Node.js JavaScript runtime ✨🐢🚀✨ +- + repo: tailwindlabs/tailwindcss + description: A utility-first CSS framework for rapid UI development. +- + repo: laravel/framework + description: Laravel is a web application framework with expressive, elegant syntax. +- + repo: prisma/prisma + description: Modern database access (ORM alternative) for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB & SQLite +- + repo: dotnet/csharplang + description: 'The official repo for the design of the C# programming language' +- + repo: home-assistant/frontend + description: '🍭 Frontend for Home Assistant' +- + repo: jspsych/jsPsych + description: A JavaScript library for creating and running behavioral experiments in a web browser +- + repo: adonisjs/core + description: '🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence' +- + repo: ImageMagick/ImageMagick + description: '🧙‍♂️ ImageMagick 7' +- + repo: react-hook-form/react-hook-form + description: '📋 React Hooks for forms validation (Web + React Native)' diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 448b086398..74d512c6d4 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -37,7 +37,10 @@ prodname_unified_search: '统一搜索' #GitHub Education prodname_education: 'GitHub Education' prodname_education_community: '教育社区' +prodname_education_community_with_url: 'the [GitHub Education Community](https://education.github.community)' prodname_classroom: 'GitHub 课堂' +prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)' +prodname_campus_program: 'GitHub Campus Program' prodname_student_pack: 'GitHub Student Developer Pack' #GitHub CLI prodname_cli: 'GitHub CLI' @@ -69,6 +72,8 @@ ae_azure_ad_app_link: 'the [GitHub AE application](https://azuremarketplace.micr prodname_actions: 'GitHub Actions' #GitHub Debug prodname_debug: 'GitHub Debug' +#GitHub Discussions +prodname_discussions: 'GitHub Discussions' #GitHub Packages prodname_registry: 'GitHub Packages' prodname_github_container_registry: 'GitHub Container Registry'