Crowdin translations (translation-batch-1612885307) (#17760)
* New Crowdin translations by Github Action * Revert broken translated files to content from branch * fix known frontmatter errors * Revert broken translated files to content from branch * fix translation errors Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: Jason Etcovitch <jasonetco@github.com>
This commit is contained in:
Vanessa Yuen
@@ -63,7 +63,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
|
||||
{% data reusables.github-actions.usage-api-requests %}
|
||||
- **Auftrags-Matrix** - {% data reusables.github-actions.usage-matrix-limits %}
|
||||
|
||||
### Unterstützte Betriebssysteme für selbst-gehostete Runner
|
||||
### Supported architectures and operating systems for self-hosted runners
|
||||
|
||||
The following operating systems are supported for the self-hosted runner application.
|
||||
|
||||
@@ -92,6 +92,14 @@ The following operating systems are supported for the self-hosted runner applica
|
||||
|
||||
- macOS 10.13 (High Sierra) oder höher
|
||||
|
||||
#### Architectures
|
||||
|
||||
The following processor architectures are supported for the self-hosted runner application.
|
||||
|
||||
- `x64` - Linux, macOS, Windows.
|
||||
- `ARM64` - Linux only.
|
||||
- `ARM32` - Linux only.
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
### Kommunikation zwischen selbst-gehosteten Runnern und {% data variables.product.prodname_dotcom %}
|
||||
|
||||
@@ -29,7 +29,7 @@ Ein selbst-gehosteter Runner erhält automatisch bestimmte Labels, wenn er zu {%
|
||||
|
||||
* `self-hosted`: Standard-Label, welches allen selbst-gehosteten Runnern zugeteilt wird.
|
||||
* `Linux`, `windows`, oder `macOS`: Je nach Betriebssystem zugeteilt.
|
||||
* `x86`, `x64`, `ARM`oder `ARM64`: Je nach Hardware-Architektur zugeteilt.
|
||||
* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture.
|
||||
|
||||
Du kannst die YAML Deines Workflows verwenden, um Jobs an eine Kombination dieser Labels zu senden. In diesem Beispiel ist ein selbst-gehosteter Runner, der allen drei Labels entspricht, berechtigt, den Job auszuführen:
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Specifications for GitHub-hosted runners
|
||||
intro: '{% data variables.product.prodname_dotcom %} bietet gehostete virtuelle Maschinen, um Workflows auszuführen. Die virtuelle Maschine umfasst eine Umgebung mit Tools, Paketen und Einstellungen für {% data variables.product.prodname_actions %}.'
|
||||
intro: '{% data variables.product.prodname_dotcom %} offers hosted virtual machines to run workflows. The virtual machine contains an environment of tools, packages, and settings available for {% data variables.product.prodname_actions %} to use.'
|
||||
product: '{% data reusables.gated-features.actions %}'
|
||||
redirect_from:
|
||||
- /articles/virtual-environments-for-github-actions
|
||||
@@ -17,35 +17,40 @@ versions:
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
### Informationen zu {% data variables.product.prodname_dotcom %}-gehosteten Runnern
|
||||
### About {% data variables.product.prodname_dotcom %}-hosted runners
|
||||
|
||||
Ein {% data variables.product.prodname_dotcom %}-gehosteter Runner ist eine virtuelle Maschine, die von {% data variables.product.prodname_dotcom %} gehostet wird und auf der die Runner-Anwendung der {% data variables.product.prodname_actions %} installiert ist. {% data variables.product.prodname_dotcom %} bietet Runner mit den Betriebssystemen Linux, Windows und MacOS.
|
||||
A {% data variables.product.prodname_dotcom %}-hosted runner is a virtual machine hosted by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner application installed. {% data variables.product.prodname_dotcom %} offers runners with Linux, Windows, and macOS operating systems.
|
||||
|
||||
Wenn Du einen {% data variables.product.prodname_dotcom %}-gehosteten Runner verwendest, werden Wartung und Upgrade der Maschine für Dich erledigt. Sie können Workflows direkt auf der virtuellen Maschine oder in einem Docker-Container ausführen.
|
||||
When you use a {% data variables.product.prodname_dotcom %}-hosted runner, machine maintenance and upgrades are taken care of for you. You can run workflows directly on the virtual machine or in a Docker container.
|
||||
|
||||
Du kannst in einem Workflow für jeden Job die Art des Runners festlegen. Jeder Job in einem Workflow wird in einer neuen Instanz der virtuellen Maschine ausgeführt. Alle Schritte des Jobs werden in derselben Instanz der virtuellen Maschine ausgeführt, sodass die Aktionen in diesem Job über das Dateisystem Informationen austauschen können.
|
||||
You can specify the runner type for each job in a workflow. Each job in a workflow executes in a fresh instance of the virtual machine. All steps in the job execute in the same instance of the virtual machine, allowing the actions in that job to share information using the filesystem.
|
||||
|
||||
{% data reusables.github-actions.runner-app-open-source %}
|
||||
|
||||
#### Cloud-Hosts für {% data variables.product.prodname_dotcom %}-gehostete Runner
|
||||
#### Cloud hosts for {% data variables.product.prodname_dotcom %}-hosted runners
|
||||
|
||||
{% data variables.product.prodname_dotcom %} betreibt Linux- und Windows-Runner auf den virtuellen Maschinen nach Standard_DS2_v2 in Microsoft Azure, auf denen die Runner-Anwendung der {% data variables.product.prodname_actions %} installiert ist. Die Runner-Anwendung auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern ist eine Fork-Kopie des Azure-Pipelines-Agenten. Bei Azure werden eingehende ICMP-Pakete werden für alle virtuellen Maschinen blockiert, so dass die Befehle ping und traceroute möglicherweise nicht funktionieren. Weitere Informationen zu den Ressourcen der Standard_DS2_v2-Maschinen findest Du unter „[Serien Dv2 und DSv2](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)“ in der Dokumentation zu Microsoft Azure.
|
||||
{% data variables.product.prodname_dotcom %} hosts Linux and Windows runners on Standard_DS2_v2 virtual machines in Microsoft Azure with the {% data variables.product.prodname_actions %} runner application installed. The {% data variables.product.prodname_dotcom %}-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work. For more information about the Standard_DS2_v2 machine resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation.
|
||||
|
||||
{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud.
|
||||
|
||||
#### Administrative Rechte von {% data variables.product.prodname_dotcom %}-gehosteten Runnern
|
||||
#### Administrative privileges of {% data variables.product.prodname_dotcom %}-hosted runners
|
||||
|
||||
Die virtuellen Maschinen unter Linux und macOS werden beide mit dem passwortlosen Befehl `sudo` ausgeführt. Wenn Sie Befehle ausführen oder Tools installieren müssen, die höhere Berechtigungen als der aktuelle Benutzer erfordern, können Sie `sudo` verwenden, ohne ein Passwort angeben zu müssen. Weitere Informationen findest Du im „[Sudo-Handbuch](https://www.sudo.ws/man/1.8.27/sudo.man.html)“.
|
||||
The Linux and macOS virtual machines both run using passwordless `sudo`. When you need to execute commands or install tools that require more privileges than the current user, you can use `sudo` without needing to provide a password. For more information, see the "[Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html)."
|
||||
|
||||
Die virtuellen Windows-Maschinen sind so konfiguriert, dass sie als Administratoren laufen, wobei die Benutzerkonten-Steuerung (UAC) deaktiviert ist. For more information, see "[How User Account Control works](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" in the Windows documentation.
|
||||
Windows virtual machines are configured to run as administrators with User Account Control (UAC) disabled. For more information, see "[How User Account Control works](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" in the Windows documentation.
|
||||
|
||||
### Unterstützte Runner und Hardwareressourcen
|
||||
### Supported runners and hardware resources
|
||||
|
||||
Für jede virtuelle Maschine stehen die gleichen Hardware-Ressourcen zur Verfügung.
|
||||
|
||||
- CPU mit 2 Kernen
|
||||
- 7 GB RAM-Speicher
|
||||
- 14 GB SSD-Festplattenspeicher
|
||||
Hardware specification for Windows and Linux virtual machines:
|
||||
- 2-core CPU
|
||||
- 7 GB of RAM memory
|
||||
- 14 GB of SSD disk space
|
||||
|
||||
Hardware specification for macOS virtual machines:
|
||||
- 3-core CPU
|
||||
- 14 GB of RAM memory
|
||||
- 14 GB of SSD disk space
|
||||
|
||||
{% data reusables.github-actions.supported-github-runners %}
|
||||
|
||||
@@ -56,7 +61,7 @@ Workflow logs list the runner used to run a job. For more information, see "[Vie
|
||||
|
||||
### Supported software
|
||||
|
||||
The software tools included in {% data variables.product.prodname_dotcom %}-hosted runners are updated weekly. Die neueste Liste der mitgelieferten Werkzeuge für jedes Runner-Betriebssystem findest Du unter den folgenden Links:
|
||||
The software tools included in {% data variables.product.prodname_dotcom %}-hosted runners are updated weekly. For the latest list of included tools for each runner operating system, see the links below:
|
||||
|
||||
* [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md)
|
||||
* [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-README.md)
|
||||
@@ -69,17 +74,23 @@ The software tools included in {% data variables.product.prodname_dotcom %}-host
|
||||
{% data reusables.github-actions.ubuntu-runner-preview %}
|
||||
{% data reusables.github-actions.macos-runner-preview %}
|
||||
|
||||
{% data variables.product.prodname_dotcom %}-gehostete Runner enthalten zusätzlich zu den oben aufgeführten Paketen die standardmäßig integrierten Tools des Betriebssystems. Zum Beispiel beinhalten Ubuntu und macOS Läufer `grep`, `find`, und `which` neben anderen Standard-Tools.
|
||||
{% data variables.product.prodname_dotcom %}-hosted runners include the operating system's default built-in tools, in addition to the packages listed in the above references. For example, Ubuntu and macOS runners include `grep`, `find`, and `which`, among other default tools.
|
||||
|
||||
Workflow logs include a link to the preinstalled tools on the runner. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
|
||||
Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow.
|
||||
|
||||
For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
|
||||
|
||||
Wenn Sie ein bestimmtes Tool anfordern möchten, öffnen Sie bitte einen Issue unter [actions/virtual-environments](https://github.com/actions/virtual-environments).
|
||||
We recommend using actions to interact with the software installed on runners. This approach has several benefits:
|
||||
- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters
|
||||
- It ensures the tool versions used in your workflow will remain the same regardless of software updates
|
||||
|
||||
If there is a tool that you'd like to request, please open an issue at [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners.
|
||||
|
||||
### IP addresses
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notiz:** Wenn Du eine Liste mit erlaubten IP-Adressen für Dein Organisations- oder Unternehmenskonto auf {% data variables.product.prodname_dotcom %} verwendest, kannst Du keine {% data variables.product.prodname_dotcom %}-gehosteten Runner verwenden, sondern benötigst stattdessen selbst-gehostete Runner. Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners)“.
|
||||
**Note:** If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you cannot use {% data variables.product.prodname_dotcom %}-hosted runners and must instead use self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -87,25 +98,25 @@ Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP
|
||||
|
||||
To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API . For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint. You can use this list of IP addresses if you require an allow-list to prevent unauthorized access to your internal resources.
|
||||
|
||||
The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week.
|
||||
The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week.
|
||||
|
||||
### File systems
|
||||
|
||||
{% data variables.product.prodname_dotcom %} führt Aktionen und Shell-Befehle in bestimmten Verzeichnissen auf der virtuellen Maschine aus. Die Dateipfade auf virtuellen Maschinen sind nicht statisch. Verwende die von {% data variables.product.prodname_dotcom %} bereitgestellten Umgebungsvariablen zum Erstellen von Dateipfaden für die Verzeichnisse `home`, `workspace`und `workflow`.
|
||||
{% data variables.product.prodname_dotcom %} executes actions and shell commands in specific directories on the virtual machine. The file paths on virtual machines are not static. Use the environment variables {% data variables.product.prodname_dotcom %} provides to construct file paths for the `home`, `workspace`, and `workflow` directories.
|
||||
|
||||
| Verzeichnis | Umgebungsvariable | Beschreibung |
|
||||
| --------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `home` | `HOME` | Enthält benutzerbezogene Daten. In diesem Verzeichnis können sich beispielsweise die Anmeldeinformation aus einem Anmeldeversuch befinden. |
|
||||
| `workspace` | `GITHUB_WORKSPACE` | Aktionen und Shell-Befehle werden in diesem Verzeichnis ausgeführt. Eine Aktion kann den Inhalt dieses Verzeichnisses ändern, auf den dann nachfolgende Aktionen zugreifen können. |
|
||||
| `workflow/event.json` | `GITHUB_EVENT_PATH` | Die `POST`-Nutzlast des Webhook-Ereignisses, das den Workflow ausgelöst hat. {% data variables.product.prodname_dotcom %} schreibt dies bei jeder ausgeführten Aktion neu, sodass der Dateiinhalt zwischen den Aktionen isoliert wird. |
|
||||
| Directory | Environment variable | Description |
|
||||
|-----------|----------------------|-------------|
|
||||
| `home` | `HOME` | Contains user-related data. For example, this directory could contain credentials from a login attempt. |
|
||||
| `workspace` | `GITHUB_WORKSPACE` | Actions and shell commands execute in this directory. An action can modify the contents of this directory, which subsequent actions can access. |
|
||||
| `workflow/event.json` | `GITHUB_EVENT_PATH` | The `POST` payload of the webhook event that triggered the workflow. {% data variables.product.prodname_dotcom %} rewrites this each time an action executes to isolate file content between actions.
|
||||
|
||||
Eine Liste der von {% data variables.product.prodname_dotcom %} für jeden Workflow erstellten Umgebungsvariablen findest Du unter „[Umgebungsvariablen verwenden](/github/automating-your-workflow-with-github-actions/using-environment-variables)“.
|
||||
For a list of the environment variables {% data variables.product.prodname_dotcom %} creates for each workflow, see "[Using environment variables](/github/automating-your-workflow-with-github-actions/using-environment-variables)."
|
||||
|
||||
#### Docker-Container-Dateisystem
|
||||
#### Docker container filesystem
|
||||
|
||||
Für Aktionen, die in Docker-Containern ausgeführt werden, befinden sich statische Verzeichnisse im Pfad `/github`. Wir empfehlen jedoch dringend, die Standard-Umgebungsvariablen zu verwenden, um Dateipfade in Docker-Containern zu erstellen.
|
||||
Actions that run in Docker containers have static directories under the `/github` path. However, we strongly recommend using the default environment variables to construct file paths in Docker containers.
|
||||
|
||||
In {% data variables.product.prodname_dotcom %} wird das Pfadpräfix `/github` reserviert, und es werden drei Verzeichnisse für Aktionen erstellt.
|
||||
{% data variables.product.prodname_dotcom %} reserves the `/github` path prefix and creates three directories for actions.
|
||||
|
||||
- `/github/home`
|
||||
- `/github/workspace` - {% data reusables.repositories.action-root-user-required %}
|
||||
@@ -113,7 +124,7 @@ In {% data variables.product.prodname_dotcom %} wird das Pfadpräfix `/github` r
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
### Weiterführende Informationen
|
||||
- „[Abrechnung für {{ site.data.variables.product.prodname_actions }} verwalten](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)“
|
||||
### Further reading
|
||||
- "[Managing billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions)"
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -73,7 +73,7 @@ If the server on which you are running
|
||||
{% endif %}
|
||||
|
||||
#### Enabling code scanning for individual repositories
|
||||
After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file.
|
||||
After you configure a self-hosted runner, {% if currentVersion == "enterprise-server@2.22" %}and provision the actions,{% endif %} users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}
|
||||
If you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}.
|
||||
|
||||
@@ -20,7 +20,7 @@ For encryption in transit, {% data variables.product.product_name %} uses Transp
|
||||
|
||||
The key that you provide is stored in a hardware security module (HSM) in a key vault that {% data variables.product.company_short %} manages.
|
||||
|
||||
To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and delete your encryption key. Note that deleting your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation.
|
||||
To configure your encryption key, use the REST API. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. For more information about the API endpoints, see "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation.
|
||||
|
||||
### Adding or updating an encryption key
|
||||
|
||||
@@ -48,24 +48,24 @@ Your 2048 bit RSA private key should be in PEM format, for example in a file cal
|
||||
curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
|
||||
```
|
||||
|
||||
### Deleting your encryption key
|
||||
### Disabling your encryption key
|
||||
|
||||
To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by deleting your encryption key.
|
||||
To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled.
|
||||
|
||||
To unfreeze your enterprise after you've deleted your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)."
|
||||
|
||||
1. To delete your key and disable encryption at rest, use the `DELETE /enterprise/encryption` endpoint.
|
||||
1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently.
|
||||
|
||||
```shell
|
||||
curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
|
||||
```
|
||||
|
||||
2. Optionally, check the status of the delete operation.
|
||||
2. Optionally, check the status of the delete operation. It takes approximately ten minutes to disable encryption at rest.
|
||||
|
||||
```shell
|
||||
curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
|
||||
```
|
||||
|
||||
To unfreeze your enterprise after you've disabled your encryption key, contact support. For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)."
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
- "[Encryption at rest](/rest/reference/enterprise-admin#encryption-at-rest)" in the REST API documentation
|
||||
|
||||
@@ -29,6 +29,26 @@ versions:
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
|
||||
|
||||
### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
|
||||
|
||||
Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
|
||||
|
||||
Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
|
||||
|
||||
| Benutzerlizenzen | vCPUs | Arbeitsspeicher | Attached-Storage | Root-Storage |
|
||||
|:---------------------------------------------------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| ------------:|
|
||||
| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | **4**<br/>_Up from 2_ | **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ | 200 GB |
|
||||
| 10–3000 | **8**<br/>_Up from 4_ | **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ | 200 GB |
|
||||
| 3000–5000 | **12**<br/>_Up from 8_ | 64 GB | 500 GB | 200 GB |
|
||||
| 5000–8000 | **16**<br/>_Up from 12_ | 96 GB | 750 GB | 200 GB |
|
||||
| 8000–10000+ | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ | 1000 GB | 200 GB |
|
||||
|
||||
{% data reusables.enterprise_installation.about-adjusting-resources %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Snapshot erstellen
|
||||
|
||||
Ein Snapshot ist ein Checkpoint einer virtuellen Maschine (VM) zu einem bestimmten Zeitpunkt. Es wird dringend empfohlen, ein Snapshot zu erstellen, bevor Sie Ihre virtuelle Maschine upgraden, damit Sie bei einem Fehlschlagen eines Upgrades Ihre VM auf den Snapshot zurücksetzen können. Wenn Sie ein Upgrade auf eine neue Feature-Veröffentlichung durchführen, müssen Sie einen VM-Snapshot erstellen. Wenn Sie ein Upgrade auf eine Patch-Veröffentlichung durchführen, können Sie die vorhandene Daten-Disk anhängen.
|
||||
|
||||
@@ -9,13 +9,7 @@ versions:
|
||||
enterprise-server: '>=2.22'
|
||||
---
|
||||
|
||||
{% if currentVersion == "enterprise-server@2.22" %}
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/).
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -23,11 +17,33 @@ versions:
|
||||
|
||||
This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Review hardware considerations
|
||||
|
||||
{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. Weitere Informationen finden Sie unter „[Upgrade von {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)“.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.actions.enterprise-hardware-considerations %}
|
||||
|
||||
{% endif %}
|
||||
For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform.
|
||||
|
||||
- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
|
||||
- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
|
||||
- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
|
||||
- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
|
||||
- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
|
||||
- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
|
||||
- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations)
|
||||
|
||||
{% data reusables.enterprise_installation.about-adjusting-resources %}
|
||||
|
||||
### External storage requirements
|
||||
|
||||
@@ -55,7 +71,7 @@ To enable {% data variables.product.prodname_actions %} on {% data variables.pro
|
||||
|
||||
### Enabling {% data variables.product.prodname_actions %}
|
||||
|
||||
{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. [Sign up for the beta](https://resources.github.com/beta-signup/).
|
||||
{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)."
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
|
||||
@@ -8,40 +8,40 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
### Repositorys klonen
|
||||
Repositorys auf {% data variables.product.prodname_dotcom %} existieren als Remote-Repositorys. Du kannst öffentliche Repositorys klonen, die anderen Personen gehören. Du kannst Dein Repository klonen, um eine lokale Kopie auf Deinem Computer zu erstellen, und die beiden Speicherorte synchronisieren.
|
||||
### About local repositories
|
||||
Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer.
|
||||
|
||||
You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. For more information, see "[Syncing your branch](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)."
|
||||
|
||||
When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. Weitere Informationen findest Du unter „[Informationen zu Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)“.
|
||||
|
||||
When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)".
|
||||
|
||||
Darüber hinaus kannst Du ein Repository direkt über {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} klonen. Weitere Informationen findest Du unter „[Ein Repository von {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_desktop %} klonen](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)“.
|
||||
|
||||
{% mac %}
|
||||
### Ein Repository klonen
|
||||
|
||||
{% data reusables.desktop.choose-clone-repository %}
|
||||
|
||||
{% data reusables.desktop.cloning-location-tab %}
|
||||
|
||||
{% data reusables.desktop.cloning-repository-list %}
|
||||
|
||||
4. Klicke auf **Choose...** (Auswählen), und navigiere mithilfe des Finder-Fensters zu einem lokalen Pfad, wo Du das Repository klonen möchtest. 
|
||||
5. Klicke auf **Clone** (Klonen). 
|
||||
{% data reusables.desktop.choose-local-path %}
|
||||
{% data reusables.desktop.click-clone %}
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
### Repository forken
|
||||
If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork.
|
||||
|
||||
{% data reusables.desktop.choose-clone-repository %}
|
||||
|
||||
{% data reusables.desktop.cloning-location-tab %}
|
||||
|
||||
{% data reusables.desktop.cloning-repository-list %}
|
||||
|
||||
4. Klicke auf **Choose...** (Auswählen), und navigiere mithilfe des Windows-Explorers zu einem lokalen Pfad, wohin Du das Repository klonen möchtest. 
|
||||
5. Klicke auf **Clone** (Klonen). 
|
||||
{% data reusables.desktop.choose-local-path %}
|
||||
{% data reusables.desktop.click-clone %}
|
||||
{% data reusables.desktop.fork-type-prompt %}
|
||||
|
||||
{% endwindows %}
|
||||
### Managing fork behavior
|
||||
You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}.
|
||||
|
||||
### Repositorys per Fork kopieren
|
||||
Um zu einem Projekt beizutragen, in dem Du keinen Schreibzugriff hast, kannst Du mit {% data variables.product.prodname_desktop %} das Repository per Fork kopieren. Änderungen an Deinem Fork wirken sich nicht auf das ursprüngliche Repository aus. Du kannst per Commit Änderungen in deinen Fork übernehmen und dann in dem ursprünglichen Repository einen Pull-Request mit deinen vorgeschlagenen Änderungen öffnen. Weitere Informationen findest Du unter „[Informationen zu Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)“.
|
||||
{% data reusables.desktop.open-repository-settings %}
|
||||
{% data reusables.desktop.select-fork-behavior %}
|
||||
|
||||
1. Wenn Du ein Repository geklont hast, in dem Du keinen Schreibzugriff hast, und dann versuchst, Änderungen per Commit zu übertragen, warnt {% data variables.product.prodname_desktop %}: „‚You don't have write access to **REPOSITORY**‘ (Du hast keinen Schreibzugriff auf **REPOSITORY**. ‚Click **create a fork**‘ (Klicke **Fork erstellen**).“ 
|
||||
3. Klicke „**Fork this repository“ (Dieses Repository per Fork kopieren)**. 
|
||||
4. Um Deinen Fork auf {% data variables.product.prodname_dotcom %} zu sehen, klickst Du in der oberen rechten Ecke von {% data variables.product.prodname_dotcom %} auf Dein Profilbild und dann auf „**Your Repositories“ (Deine Repositorys)**. 
|
||||
### Weiterführende Informationen
|
||||
- [Informationen zu Remote-Repositorys](/github/using-git/about-remote-repositories)
|
||||
|
||||
@@ -9,7 +9,7 @@ versions:
|
||||
|
||||
### Informationen zu „Tags“ (Schlagworten) in {% data variables.product.prodname_desktop %}
|
||||
|
||||
{% data variables.product.prodname_desktop %} ermöglicht Dir, kommentierte Tags zu erstellen. Du kannst ein Tag verwenden, um einen einzelnen Punkt im Verlauf Deines Repositorys zu markieren, einschließlich einer Versionsnummer für eine Freigabe („Release“). Weitere Informationen zu Release-Tags findest Du unter „[Informationen zu Releases](/github/administering-a-repository/about-releases)“.
|
||||
{% data variables.product.prodname_desktop %} ermöglicht Dir, kommentierte Tags zu erstellen. Tags are associated with commits, so you can use a tag to mark an individual point in your repository's history, including a version number for a release. Weitere Informationen zu Release-Tags findest Du unter „[Informationen zu Releases](/github/administering-a-repository/about-releases)“.
|
||||
|
||||
{% data reusables.desktop.tags-push-with-commits %}
|
||||
|
||||
@@ -44,3 +44,7 @@ versions:
|
||||
|
||||
{% data reusables.desktop.history-tab %}
|
||||
{% data reusables.desktop.delete-tag %}
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
- "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation
|
||||
|
||||
@@ -3,6 +3,8 @@ title: Activating beta features for apps
|
||||
intro: 'You can test new app features released in public beta for your {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_app %}s.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
github-ae: '*'
|
||||
---
|
||||
|
||||
{% warning %}
|
||||
|
||||
@@ -110,7 +110,7 @@ The example above uses the maximum expiration time of 10 minutes, after which th
|
||||
```json
|
||||
{
|
||||
"message": "'Expiration' claim ('exp') must be a numeric value representing the future time at which the assertion expires.",
|
||||
"documentation_url": "{% data variables.product.doc_url_pre %}/v3"
|
||||
"documentation_url": "{% data variables.product.doc_url_pre %}"
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ versions:
|
||||
|
||||
### Einführung
|
||||
|
||||
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.
|
||||
This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests.
|
||||
|
||||
CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Durch häufige Code-Aktualisierungen lassen sich zudem Änderungen von verschiedenen Mitgliedern eines Software-Entwicklungsteams leichter zusammenführen. Dies bedeutet einen erheblichen Vorteil für die Entwickler, die sich damit stärker auf das Schreiben des Codes konzentrieren können, statt Fehler debuggen oder Mergekonflikte beheben zu müssen. 🙌
|
||||
|
||||
@@ -49,7 +49,7 @@ To get an idea of what your Checks API CI server will do when you've completed t
|
||||
|
||||
### Vorrausetzungen
|
||||
|
||||
Before you get started, you may want to familiarize yourself with [Github Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details.
|
||||
Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details.
|
||||
|
||||
You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app.
|
||||
|
||||
@@ -203,7 +203,7 @@ Great! You've told GitHub to create a check run. You can see the check run statu
|
||||
|
||||
### Schritt 1.4. Updating a check run
|
||||
|
||||
When your `create_check_run` method runs, it asks GitHub to create a new check run. When Github finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check.
|
||||
When your `create_check_run` method runs, it asks GitHub to create a new check run. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check.
|
||||
|
||||
You'll want to update your event handler to look for the `created` action. While you're updating the event handler, you can add a conditional for the `rerequested` action. When someone re-runs a single test on GitHub by clicking the "Re-run" button, GitHub sends the `rerequested` check run event to your app. When a check run is `rerequested`, you'll want to start the process all over and create a new check run.
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ GitHub Apps use [sliding rules for rate limits](/apps/building-github-apps/under
|
||||
|
||||
#### Register a new 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/).
|
||||
Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/).
|
||||
|
||||
#### Determine the permissions your app requires
|
||||
|
||||
@@ -62,7 +62,7 @@ In your GitHub App's settings, you can specify whether your app needs `No Access
|
||||
|
||||
#### Subscribe to webhooks
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
#### Understand the different methods of authentication
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ This callback request will send you a new access token and a new refresh token.
|
||||
{
|
||||
"access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a",
|
||||
"expires_in": "28800",
|
||||
"refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692",
|
||||
"refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c",
|
||||
"refresh_token_expires_in": "15811200",
|
||||
"scope": "",
|
||||
"token_type": "bearer"
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /apps/managing-github-apps/suspending-a-github-app-installation
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
github-ae: '*'
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -14,7 +14,7 @@ versions:
|
||||
|
||||
{% warning %}
|
||||
|
||||
If you offer a GitHub App in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate OAuth App to support this flow. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information.
|
||||
If you offer a {% data variables.product.prodname_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 {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -24,7 +24,7 @@ Before a customer purchases your {% data variables.product.prodname_marketplace
|
||||
|
||||
The customer completes the purchase by clicking **Complete order and begin installation**.
|
||||
|
||||
GitHub then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app.
|
||||
{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app.
|
||||
|
||||
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.
|
||||
|
||||
@@ -34,27 +34,27 @@ See "[{% data variables.product.prodname_marketplace %} webhook events](/marketp
|
||||
|
||||
### Schritt 2. Installation
|
||||
|
||||
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.
|
||||
If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories.
|
||||
|
||||
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.
|
||||
At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} 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 {% data variables.product.prodname_github_app %}.
|
||||
|
||||
{% 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 %}.
|
||||
**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% 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).
|
||||
If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} 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).
|
||||
|
||||
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`.
|
||||
When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} 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`.
|
||||
|
||||
### Schritt 3. Autorisierung
|
||||
|
||||
When a customer purchases your app, you must send the customer through the OAuth authorization flow:
|
||||
|
||||
* 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/)."
|
||||
* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/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/)."
|
||||
* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/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.
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ Repl.it is an online integrated development environment (IDE) that supports mult
|
||||
|
||||
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 more information about working on Repl.it, see the [Repl.it Quickstart Guide](https://docs.repl.it/repls/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.
|
||||
|
||||
|
||||
@@ -3,6 +3,7 @@ title: About Dependabot version updates
|
||||
intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the packages you use updated to the latest versions.'
|
||||
redirect_from:
|
||||
- /github/administering-a-repository/about-dependabot
|
||||
- /github/administering-a-repository/about-github-dependabot
|
||||
- /github/administering-a-repository/about-github-dependabot-version-updates
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
@@ -14,9 +15,9 @@ versions:
|
||||
|
||||
{% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on.
|
||||
|
||||
You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file in to your repository. The configuration file specifies the location of the manifest, or other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository, rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary.
|
||||
You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary.
|
||||
|
||||
When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to directly replace the outdated dependency with the new version. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)."
|
||||
When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Enabling and disabling version updates](/github/administering-a-repository/enabling-and-disabling-version-updates)."
|
||||
|
||||
If you enable security updates, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
|
||||
|
||||
|
||||
@@ -82,13 +82,13 @@ After enabling required status checks, all required status checks must pass befo
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Du kannst die erforderlichen Statusprüfungen entweder als "loose" (locker) oder als "strict" (streng) einrichten. The type of required status check you choose determines whether your branch is required to be up-to-date with the base branch before merging.
|
||||
Du kannst die erforderlichen Statusprüfungen entweder als "loose" (locker) oder als "strict" (streng) einrichten. Die Art der erforderlichen Statuschecks bestimmt, ob Dein Branch vor dem Zusammenführen auf dem aktuellen Stand mit dem Basisbranch sein muss.
|
||||
|
||||
| Art des erforderlichen Statuschecks | Einstellung | Merge-Anforderungen | Erwägungen |
|
||||
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| **Streng** | Das Kontrollkästchen **Require branches to be up-to-date before merging** (Aktualität der Branches vor dem Zusammenführen erzwingen) ist aktiviert. | Der Branch **muss** vor dem Zusammenführen auf dem Stand des Basisbranches sein. | Dies ist das Standardverhalten für erforderliche Statuschecks. Weitere Builds können erforderlich sein, da Du den Head-Branch auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests in den geschützten Basisbranch überführt haben. |
|
||||
| **Locker** | Das Kontrollkästchen **Require branches to be up-to-date before merging** (Aktualität der Branches vor dem Zusammenführen erzwingen) ist **nicht** aktiviert. | Der Branch muss vor dem Zusammenführen **nicht** auf dem Stand des Basisbranches sein. | Es sind weniger Builds erforderlich, da Du den Head-Branch nicht auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests überführt haben. Statuschecks schlagen nach dem Zusammenführen Deines Branches möglicherweise fehl, wenn inkompatible Änderungen am Basisbranch vorliegen. |
|
||||
| **Deaktiviert** | Das Kontrollkästchen **Require status checks to pass before merging** (Statuschecks müssen vor dem Zusammenführen bestanden werden) ist **deaktiviert**. | Für den Branch gelten keine Merge-Einschränkungen. | Wenn die erforderlichen Statuschecks nicht aktiviert sind, können Mitarbeiter den Branch unabhängig von seinem Stand gegenüber dem Basisbranch jederzeit zusammenführen. Die Wahrscheinlich inkompatibler Änderungen erhöht sich dadurch jedoch. |
|
||||
| Art des erforderlichen Statuschecks | Einstellung | Merge-Anforderungen | Erwägungen |
|
||||
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| **Streng** | The **Require branches to be up to date before merging** checkbox is checked. | Der Branch **muss** vor dem Zusammenführen auf dem Stand des Basisbranches sein. | Dies ist das Standardverhalten für erforderliche Statuschecks. Weitere Builds können erforderlich sein, da Du den Head-Branch auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests in den geschützten Basisbranch überführt haben. |
|
||||
| **Locker** | The **Require branches to be up to date before merging** checkbox is **not** checked. | Der Branch muss vor dem Zusammenführen **nicht** auf dem Stand des Basisbranches sein. | Es sind weniger Builds erforderlich, da Du den Head-Branch nicht auf den neuesten Stand bringen musst, nachdem andere Mitarbeiter Pull Requests überführt haben. Statuschecks schlagen nach dem Zusammenführen Deines Branches möglicherweise fehl, wenn inkompatible Änderungen am Basisbranch vorliegen. |
|
||||
| **Deaktiviert** | Das Kontrollkästchen **Require status checks to pass before merging** (Statuschecks müssen vor dem Zusammenführen bestanden werden) ist **deaktiviert**. | Für den Branch gelten keine Merge-Einschränkungen. | Wenn die erforderlichen Statuschecks nicht aktiviert sind, können Mitarbeiter den Branch unabhängig von seinem Stand gegenüber dem Basisbranch jederzeit zusammenführen. Die Wahrscheinlich inkompatibler Änderungen erhöht sich dadurch jedoch. |
|
||||
|
||||
For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)."
|
||||
|
||||
|
||||
@@ -14,6 +14,8 @@ The first step to securing a repository is to set up who can see and modify your
|
||||
|
||||
{% data variables.product.prodname_dotcom %} has a growing set of security features that help you keep your code secure. You can find these on the **Security** tab for your repository.
|
||||
|
||||
#### Available for all repositories
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
- **Security policy**
|
||||
|
||||
@@ -43,15 +45,23 @@ Use
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
#### Available {% if currentVersion == "free-pro-team@latest" %}for public repositories and for repositories {% endif %}with {% data variables.product.prodname_advanced_security %}
|
||||
|
||||
These features are available {% if currentVersion == "free-pro-team@latest" %}for all public repositories, and for private repositories owned by organizations with {% else %}if you have {% endif %}an {% data variables.product.prodname_advanced_security %} license. {% data reusables.advanced-security.more-info-ghas %}
|
||||
|
||||
- **{% data variables.product.prodname_code_scanning_capc %} alerts**
|
||||
|
||||
Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
|
||||
|
||||
- **Detected secrets**
|
||||
View any secrets that
|
||||
|
||||
{% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}For private repositories, view {% else if %}View {% endif %}any secrets that {% data variables.product.prodname_dotcom %} has found in your code. You should treat tokens or credentials that have been checked into the repository as compromised. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
|
||||
{% endif %}
|
||||
|
||||
### Exploring dependencies
|
||||
{% data variables.product.prodname_dotcom %}'s dependency graph allows you to explore:
|
||||
@@ -59,6 +69,6 @@ View any secrets that
|
||||
* Ecosystems and packages that your repository depends on
|
||||
* Repositories and packages that depend on your repository
|
||||
|
||||
You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities.
|
||||
You must enable the dependency graph before {% data variables.product.prodname_dotcom %} can generate {% data variables.product.prodname_dependabot_alerts %} for dependencies with security vulnerabilities. {% if currentVersion == "free-pro-team@latest" %}Enabling the dependency graph also enables {% data variables.product.prodname_dotcom %} to run dependency reviews of pull requests.{% endif %}
|
||||
|
||||
You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
|
||||
@@ -27,13 +27,13 @@ versions:
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-security-and-analysis %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
4. If "{% data variables.product.prodname_secret_scanning_caps %}" is not shown on the page, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**. 
|
||||
5. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action. 
|
||||
6. When you enable
|
||||
{% data variables.product.prodname_GH_advanced_security %} this may automatically enable {% data variables.product.prodname_secret_scanning %} for the repository (this is controlled by the organization configuration). If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled.
|
||||
{% endif %}
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
{% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %}
|
||||
4. To the right of "
|
||||
{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**.
|
||||
|
||||
|
||||
@@ -4,13 +4,12 @@ intro: "You can allow or disallow auto-merge for pull requests in your repositor
|
||||
product: '{% data reusables.gated-features.auto-merge %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.1'
|
||||
permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository.
|
||||
---
|
||||
|
||||
{% data reusables.pull_requests.auto-merge-release-phase %}
|
||||
|
||||
If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. Under "Merge button", select or deselect **Allow auto-merge**. 
|
||||
1. Under "Merge button", select or deselect **Allow auto-merge**. 
|
||||
|
||||
@@ -33,10 +33,15 @@ You can manage the security and analysis features for your {% if currentVersion
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-security-and-analysis %}
|
||||
4. Under "Configure security and analysis features", to the right of the feature, click **Disable** or **Enable**.
|
||||
{% if currentVersion == "free-pro-team@latest" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first.
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If "{% data variables.product.prodname_secret_scanning_caps %}" is not displayed, you may need to enable {% data variables.product.prodname_GH_advanced_security %} first.
|
||||
|
||||
{% endif %}
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
{% note %}
|
||||
**Note:** If you disable
|
||||
|
||||
{% data variables.product.prodname_GH_advanced_security %}, both {% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail.
|
||||
{% endnote %}
|
||||
|
||||
{% else if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@3.0" %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -6,5 +6,6 @@ redirect_from:
|
||||
- /articles/securing-your-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
---
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ We recommend reviewing the following caveats before you change the visibility of
|
||||
* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}The visibility of any forks will also change to private.{% elsif currentVersion == "github-ae@latest" %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"{% if currentVersion == "free-pro-team@latest" %}
|
||||
* If you're using {% data variables.product.prodname_free_user %} for user accounts or organizations, some features won't be available in the repository after you change the visibility to private. {% data reusables.gated-features.more-info %}{% endif %}
|
||||
* Any published {% data variables.product.prodname_pages %} site will be automatically unpublished.{% if currentVersion == "free-pro-team@latest" %} If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working unless the repository is owned by an organization that has a license for {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% if enterpriseServerVersions contains currentVersion %}
|
||||
* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %}
|
||||
|
||||
|
||||
@@ -33,14 +33,18 @@ Wenn Sie einen GPG-Schlüssel verwenden, der mit Ihrer Beitragenderidentität un
|
||||
Comment: <em>GitHub key</em>
|
||||
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit?
|
||||
```
|
||||
7. Gib `O` ein, um Deine Auswahl zu speichern.
|
||||
7. Enter `O` to confirm your selections.
|
||||
8. Gib die Passphrase Deines Schlüssels ein.
|
||||
9. Gib `gpg --armor --export GPG key ID` ein. Setze dabei die gewünschte GPG-Schlüssel-ID ein. Im folgenden Beispiel ist die GPG-Schlüssel-ID `3AA5C34371567BD2`:
|
||||
9. Enter `gpg> save` to save the changes
|
||||
```shell
|
||||
$ gpg> save
|
||||
```
|
||||
10. Geben Sie `gpg --armor --export GPG key ID` ein. Setzen Sie dabei die gewünschte GPG-Schlüssel-ID ein. Im folgenden Beispiel ist die GPG-Schlüssel-ID `3AA5C34371567BD2`:
|
||||
```shell
|
||||
$ gpg --armor --export <em>3AA5C34371567BD2</em>
|
||||
# Gibt den GPG Schluessel im ASCII armor format aus
|
||||
```
|
||||
10. Lade den GPG-Schlüssel hoch, indem Du ihn [zu Deinem GitHub-Konto hinzufügst](/articles/adding-a-new-gpg-key-to-your-github-account).
|
||||
11. Laden Sie den GPG-Schlüssel hoch, indem Sie ihn [zu Ihrem GitHub-Konto hinzufügen](/articles/adding-a-new-gpg-key-to-your-github-account).
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
|
||||
@@ -4,10 +4,9 @@ intro: 'You can increase development velocity by enabling auto-merge for a pull
|
||||
product: '{% data reusables.gated-features.auto-merge %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.1'
|
||||
---
|
||||
|
||||
{% data reusables.pull_requests.auto-merge-release-phase %}
|
||||
|
||||
### About auto-merge
|
||||
|
||||
If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks.
|
||||
|
||||
@@ -9,7 +9,6 @@ versions:
|
||||
github-ae: '*'
|
||||
---
|
||||
|
||||
|
||||
### Informationen zum Zusammenführen von Pull Requests
|
||||
|
||||
Mit einem Pull Request schlägst Du vor, dass Änderungen, die Du an einem Head-Branch gemacht hast, in einen Basis-Branch zusammengeführt werden sollten. Standardmäßig kann jeder Pull Request jederzeit zusammengeführt werden, es sei denn, der Head-Branch steht in Konflikt mit dem Basisbranch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).“
|
||||
|
||||
@@ -23,7 +23,7 @@ Wenn ein Benutzer mit Administrator- oder Inhaberberechtigungen die erforderlich
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. Weitere Informationen findest Du unter „[Code Review-Zuweisung für Dein Team verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
Wenn eine Datei einen Codeinhaber hat, kannst Du sehen, wer der Codeinhaber ist, bevor Du einen Pull Request öffnest. In the repository, you can browse to the file and hover over
|
||||
{% octicon "shield-lock" aria-label="The edit icon" %}.
|
||||
|
||||
|
||||
@@ -12,25 +12,26 @@ versions:
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
### Informationen zu {% data variables.product.prodname_code_scanning %}
|
||||
### About {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
With {% data variables.product.prodname_code_scanning %}, developers can quickly and automatically analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors.
|
||||
{% data reusables.code-scanning.about-code-scanning %}
|
||||
|
||||
You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push.
|
||||
|
||||
If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. Nachdem Du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt {% data variables.product.prodname_dotcom %} die Meldung. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
|
||||
If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
|
||||
|
||||
To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)."
|
||||
To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use webhooks and the {% data variables.product.prodname_code_scanning %} API. For information about the webhooks for {% data variables.product.prodname_code_scanning %}, see
|
||||
"[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)." For information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning)."
|
||||
|
||||
To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)."
|
||||
To get started with {% data variables.product.prodname_code_scanning %}, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
### Informationen zu {% data variables.product.prodname_codeql %}
|
||||
### About {% data variables.product.prodname_codeql %}
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
|
||||
You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
|
||||
|
||||
{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website.
|
||||
|
||||
For more information about API endpoints for {% data variables.product.prodname_code_scanning %}, see "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)."
|
||||
{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
|
||||
|
||||
{% data reusables.code-scanning.supported-languages %}
|
||||
|
||||
@@ -38,9 +39,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
### Informationen zur Abrechnung für {% data variables.product.prodname_code_scanning %}
|
||||
### About billing for {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).“
|
||||
{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -52,7 +53,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam
|
||||
|
||||
{% data reusables.code-scanning.get-started-uploading-third-party-data %}
|
||||
|
||||
### Weiterführende Informationen
|
||||
### Further reading
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
|
||||
|
||||
@@ -134,19 +134,22 @@ Attempts to build the code for the compiled languages C/C++, C#, and Java. For t
|
||||
|
||||
Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_location %}.
|
||||
|
||||
| Flag | Erforderlich | Input value |
|
||||
| -------------------------------- |:------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `--repository` | ✓ | Name of the repository to analyze. |
|
||||
| `--commit` | ✓ | SHA of the commit to analyze. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`. |
|
||||
| `--ref` | ✓ | Name of the reference to analyze, for example `refs/heads/main`. In Git and in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
|
||||
| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. |
|
||||
| `--github-auth` | ✓ | A {% data variables.product.prodname_github_apps %} token or personal access token. |
|
||||
| <nobr>`--checkout-path`</nobr> | | The path to the checkout of your repository. The default is the current working directory. |
|
||||
| `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_location %}. |
|
||||
| `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. |
|
||||
| `--temp-dir` | | Directory where temporary files are stored. The default is _./codeql-runner_. |
|
||||
| `--debug` | | None. Prints more verbose output. |
|
||||
| `-h`, `--help` | | None. Displays help for the command. |
|
||||
| Flag | Erforderlich | Input value |
|
||||
| ---------------------------------- |:------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `--repository` | ✓ | Name of the repository to analyze. |
|
||||
| `--commit` | ✓ | SHA of the commit to analyze. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`. |
|
||||
| `--ref` | ✓ | Name of the reference to analyze, for example `refs/heads/main`. In Git and in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
|
||||
| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. |
|
||||
| `--github-auth` | ✓ | A {% data variables.product.prodname_github_apps %} token or personal access token. |
|
||||
| <nobr>`--checkout-path`</nobr> | | The path to the checkout of your repository. The default is the current working directory. |
|
||||
| `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_location %}. |
|
||||
| `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. |
|
||||
| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. |
|
||||
| <nobr>`--no-add-snippets`</nobr> | | None. Excludes code snippets from the SARIF output. |
|
||||
| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. |
|
||||
| `--temp-dir` | | Directory where temporary files are stored. The default is _./codeql-runner_. |
|
||||
| `--debug` | | None. Prints more verbose output. |
|
||||
| `-h`, `--help` | | None. Displays help for the command. |
|
||||
|
||||
#### `hochladen`
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ versions:
|
||||
|
||||
### About the {% data variables.product.prodname_codeql_workflow %} and compiled languages
|
||||
|
||||
You enable {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file.
|
||||
You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. **Note**: This article refers to {% data variables.product.prodname_code_scanning %} powered by {% data variables.product.prodname_codeql %}, not to {% data variables.product.prodname_code_scanning %} resulting from the upload of third-party static analysis tools. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
{% data reusables.code-scanning.edit-workflow %}
|
||||
For general information about configuring
|
||||
|
||||
@@ -14,7 +14,7 @@ versions:
|
||||
{% topic_link_in_list /automatically-scanning-your-code-for-vulnerabilities-and-errors %}
|
||||
{% link_in_list /about-code-scanning %}
|
||||
{% link_in_list /triaging-code-scanning-alerts-in-pull-requests %}
|
||||
{% link_in_list /enabling-code-scanning %}
|
||||
{% link_in_list /setting-up-code-scanning-for-a-repository %}
|
||||
{% link_in_list /managing-code-scanning-alerts-for-your-repository %}
|
||||
{% link_in_list /configuring-code-scanning %}
|
||||
{% link_in_list /configuring-the-codeql-workflow-for-compiled-languages %}
|
||||
|
||||
@@ -16,7 +16,7 @@ redirect_from:
|
||||
|
||||
### About alerts from {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. The default {% data variables.product.prodname_code_scanning %} workflow uses the `on.push` event to trigger a code scan on every push to any branch containing the workflow file.
|
||||
You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
|
||||
@@ -28,7 +28,7 @@ Each alert highlights a problem with the code and the name of the tool that iden
|
||||
|
||||
|
||||
|
||||
If you enable {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
|
||||
If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
|
||||
|
||||
When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
|
||||
|
||||
@@ -65,7 +65,7 @@ Closing an alert is a way to resolve an alert that you don't think needs to be f
|
||||
|
||||
### Dismissing or deleting alerts
|
||||
|
||||
There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have enabled a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have enabled {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
|
||||
There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
|
||||
|
||||
Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab.
|
||||
|
||||
@@ -127,5 +127,5 @@ If a project has multiple alerts that you want to dismiss for the same reason, y
|
||||
### Weiterführende Informationen
|
||||
|
||||
- "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)"
|
||||
- "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)"
|
||||
- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)"
|
||||
- "[About integration with {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning)"
|
||||
|
||||
@@ -24,7 +24,7 @@ If you use a continuous integration or continuous delivery/deployment (CI/CD) sy
|
||||
|
||||
{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
|
||||
|
||||
You can use the {% data variables.product.prodname_codeql_runner %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_location %}. For information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)."
|
||||
You can use the {% data variables.product.prodname_codeql_runner %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_location %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_location %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
|
||||
|
||||
|
||||
@@ -97,7 +97,6 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr
|
||||
| `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. |
|
||||
| `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). |
|
||||
| `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). |
|
||||
| `suppressions[].state` | **Optional.** When the `state` is set to `accepted`, {% data variables.product.prodname_code_scanning %} will update the state of the result to `Closed` on {% data variables.product.prodname_dotcom %}. |
|
||||
|
||||
#### `location` object
|
||||
|
||||
|
||||
@@ -0,0 +1,117 @@
|
||||
---
|
||||
title: Setting up code scanning for a repository
|
||||
shortTitle: Setting up code scanning
|
||||
intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.'
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/configuring-automated-code-scanning
|
||||
- /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning
|
||||
- /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
---
|
||||
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
|
||||
|
||||
### Options for setting up {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)."
|
||||
|
||||
{% data reusables.code-scanning.enabling-options %}
|
||||
|
||||
### Setting up {% data variables.product.prodname_code_scanning %} using actions
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).“{% endif %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
3. To the right of "{% data variables.product.prodname_code_scanning_capc %}", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} 
|
||||
4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. 
|
||||
5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
|
||||
|
||||
Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
|
||||
|
||||
For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
|
||||
6. Use the **Start commit** drop-down, and type a commit message. 
|
||||
7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request. 
|
||||
8. Click **Commit new file** or **Propose new file**.
|
||||
|
||||
In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence.
|
||||
|
||||
### Bulk set up of {% data variables.product.prodname_code_scanning %}
|
||||
You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository.
|
||||
|
||||
### Viewing the logging output from {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run.
|
||||
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
|
||||
You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message.
|
||||
|
||||
|
||||
|
||||
1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow.
|
||||
|
||||
1. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
|
||||
|
||||
|
||||
|
||||
1. Review the logging output from the actions in this workflow as they run.
|
||||
|
||||
1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-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.
|
||||
|
||||
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Understanding the pull request checks
|
||||
|
||||
Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
#### 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.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan.
|
||||
|
||||
* 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 %}.
|
||||
|
||||
* 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 %}.
|
||||
|
||||
### Nächste Schritte:
|
||||
|
||||
After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can:
|
||||
|
||||
- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
|
||||
- View any alerts generated for a pull request submitted after you set up {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
- Set up notifications for completed runs. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)."
|
||||
- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)."
|
||||
- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
|
||||
@@ -15,7 +15,7 @@ versions:
|
||||
|
||||
In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
|
||||
|
||||
If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that has been enabled for {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“
|
||||
If {% data variables.product.prodname_code_scanning %} has any results with a severity of `error`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notices and the check succeeds. If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then you must either fix or {% if currentVersion == "enterprise-server@2.22" %}close{% else %}dismiss{% endif %} all error alerts before the pull request can be merged. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -75,7 +75,7 @@ When
|
||||
|
||||
### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
|
||||
|
||||
You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
|
||||
You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
|
||||
By default, we notify people with admin permissions in the affected repositories about new
|
||||
@@ -89,6 +89,11 @@ Standardmäßig senden wir Sicherheitsmeldungen an Personen mit Administratorrec
|
||||
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
You can also see all the
|
||||
{% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)."
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
### Weiterführende Informationen
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Es gibt vier mögliche Schweregrade, die im [Common Vulnerability Scoring System
|
||||
- Hoch
|
||||
- Kritisch
|
||||
|
||||
The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above. {% data variables.product.product_name %} doesn't publish CVSS scores.
|
||||
The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above.
|
||||
|
||||
{% data reusables.repositories.github-security-lab %}
|
||||
|
||||
@@ -41,24 +41,39 @@ Die Datenbank ist auch über die GraphQL-API zugänglich. For more information,
|
||||
{% endnote %}
|
||||
|
||||
### Durchsuche die {% data variables.product.prodname_advisory_database %}
|
||||
Du kannst die Datenbank durchsuchen und mit den Qualifizierern Deine Suche auf Hinweise einschränken, die an einem bestimmten Datum, in einem bestimmten Ökosystem oder in einer bestimmten Bibliothek erstellt wurden.
|
||||
|
||||
You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
|
||||
|
||||
{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
|
||||
|
||||
{% data reusables.search.date_gt_lt %}
|
||||
|
||||
| Qualifizierer | Beispiel |
|
||||
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `ecosystem:ÖKOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) wird nur Hinweise zeigen, die NPM Pakete betreffen. |
|
||||
| `severity:STUFE` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) wird nur Hinweise mit einer Schweregrad von Hoch zeigen. |
|
||||
| `affects:BIBLIOTHEK` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) wird nur Hinweise anzeigen, die die lodash Bibliothek betreffen. |
|
||||
| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) sortiert nach ältesten Hinweisen zuerst. |
|
||||
| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) sortiert nach neuesten Hinweisen zuerst. |
|
||||
| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) sortiert nach den ältesten Aktualisierungen von Hinweisen zuerst. |
|
||||
| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) sortiert nach den neuesten Aktualisierungen von Hinweisen zuerst. |
|
||||
| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) zeigt nur zurückgezogene Hinweise. |
|
||||
| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) zeigt nur Hinweise, die an diesem Datum erstellt wurden. |
|
||||
| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) zeigt nur Hinweise, die an diesem Datum aktualisiert wurden. |
|
||||
| Qualifizierer | Beispiel |
|
||||
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
|
||||
| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
|
||||
| `ecosystem:ÖKOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) wird nur Hinweise zeigen, die NPM Pakete betreffen. |
|
||||
| `severity:STUFE` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) wird nur Hinweise mit einer Schweregrad von Hoch zeigen. |
|
||||
| `affects:BIBLIOTHEK` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) wird nur Hinweise anzeigen, die die lodash Bibliothek betreffen. |
|
||||
| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
|
||||
| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
|
||||
| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) sortiert nach ältesten Hinweisen zuerst. |
|
||||
| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) sortiert nach neuesten Hinweisen zuerst. |
|
||||
| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) sortiert nach den ältesten Aktualisierungen von Hinweisen zuerst. |
|
||||
| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) sortiert nach den neuesten Aktualisierungen von Hinweisen zuerst. |
|
||||
| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) zeigt nur zurückgezogene Hinweise. |
|
||||
| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) zeigt nur Hinweise, die an diesem Datum erstellt wurden. |
|
||||
| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) zeigt nur Hinweise, die an diesem Datum aktualisiert wurden. |
|
||||
|
||||
### Viewing your vulnerable repositories
|
||||
|
||||
For any vulnerability in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories have a {% data variables.product.prodname_dependabot %} alert for that vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)." |
|
||||
|
||||
1. Navigiere zu „https://github.com/advisories“.
|
||||
2. Click an advisory.
|
||||
3. At the top of the advisory page, click **Dependabot alerts**. 
|
||||
4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). 
|
||||
5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name.
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
|
||||
@@ -12,6 +12,8 @@ versions:
|
||||
|
||||
{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
|
||||
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
|
||||
Minuten werden jeden Monat zurückgesetzt, während Speichernutzung dies nicht tut.
|
||||
|
||||
| Produkt | Speicher | Minuten (pro Monat) |
|
||||
|
||||
@@ -14,6 +14,8 @@ versions:
|
||||
|
||||
{% data reusables.package_registry.container-registry-beta-billing-note %}
|
||||
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
|
||||
Die Datenübertragung wird jeden Monat zurückgesetzt, während Speichernutzung dies nicht tut.
|
||||
|
||||
| Produkt | Speicher | Datenübertragung (pro Monat) |
|
||||
|
||||
@@ -14,6 +14,8 @@ versions:
|
||||
|
||||
{% 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)."
|
||||
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
|
||||
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.
|
||||
|
||||
@@ -14,6 +14,8 @@ versions:
|
||||
|
||||
{% 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)."
|
||||
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
|
||||
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.
|
||||
|
||||
@@ -23,8 +23,13 @@ versions:
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.security-and-analysis %}
|
||||
|
||||
The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization. {% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features.
|
||||
The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}If your organization, or the enterprise that owns it, has a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features.{% endif %}
|
||||
|
||||
{% if currentVersion ver_gt "enterprise-server@3.0" %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features.{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -42,24 +47,21 @@ You can enable or disable features for all repositories. {% if currentVersion ==
|
||||
|
||||
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**.
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
|
||||
{% endif %}
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
{% endif %}
|
||||
2. Optionally, enable the feature by default for new repositories in your organization.
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
|
||||
{% endif %}
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
{% endif %}
|
||||
1. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
3. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
|
||||
{% endif %}
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -68,10 +70,9 @@ You can enable or disable features for all repositories. {% if currentVersion ==
|
||||
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
|
||||
{% if currentVersion == "free-pro-team@latest" %}, or all new private repositories,{% endif %} in your organization.
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
|
||||
{% endif %}
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -70,7 +70,7 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben
|
||||
{% endif %}
|
||||
| Apply/dismiss labels | | **X** | **X** | **X** | **X** |
|
||||
| Create, edit, delete labels | | | **X** | **X** | **X** |
|
||||
| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X**
|
||||
{% endif %}
|
||||
| Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** |
|
||||
@@ -150,8 +150,8 @@ In this section, you can find the repository permission levels required for secu
|
||||
| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** |
|
||||
| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |
|
||||
| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies | | | | | **X** |
|
||||
| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** |
|
||||
| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |
|
||||
| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Aktivieren des Abhängigkeitsdiagramms](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) für ein privates Repository | | | | | **X** |
|
||||
| [View dependency reviews](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request) | **X** | **X** | **X** | **X** | **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** |
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: Connecting an Azure subscription to your enterprise
|
||||
intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the included amounts for your enterprise.'
|
||||
product: '{% data reusables.gated-features.enterprise-accounts %}'
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
### About Azure subscriptions and {% data variables.product.product_name %}
|
||||
|
||||
{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 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) and "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."
|
||||
|
||||
After you connect an Azure subscription, you can also manage your spending limit. 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)" and "[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)."
|
||||
|
||||
### Connecting your Azure subscription to your enterprise account
|
||||
|
||||
To connect your Azure subscription, you must have owner permissions to the subscription.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.billing-tab %}
|
||||
{% data reusables.enterprise-accounts.payment-information-tab %}
|
||||
1. Under "Payment Information", click **Add Azure Subscription**.
|
||||
1. To sign in to your Microsoft account, follow the prompts.
|
||||
1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**.
|
||||
1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise.
|
||||
1. Click **Connect**.
|
||||
|
||||
### Disconnecting your Azure subscription from your enterprise account
|
||||
|
||||
After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.billing-tab %}
|
||||
{% data reusables.enterprise-accounts.payment-information-tab %}
|
||||
1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trashcan" aria-label="The trashcan icon" %}**.
|
||||
1. Review the prompt, then click **Remove**.
|
||||
@@ -18,6 +18,7 @@ versions:
|
||||
{% link_in_list /about-enterprise-accounts %}
|
||||
{% link_in_list /viewing-the-subscription-and-usage-for-your-enterprise-account %}
|
||||
{% link_in_list /managing-licenses-for-visual-studio-subscription-with-github-enterprise %}
|
||||
{% link_in_list /connecting-an-azure-subscription-to-your-enterprise %}
|
||||
{% topic_link_in_list /managing-users-in-your-enterprise %}
|
||||
{% link_in_list /roles-in-an-enterprise %}
|
||||
{% link_in_list /inviting-people-to-manage-your-enterprise %}
|
||||
|
||||
@@ -31,7 +31,7 @@ Enterprise owners have complete control over the enterprise and can take every a
|
||||
|
||||
Keinen Zugriff haben Enterprise-Inhaber auf die Einstellungen und Inhalte der einzelnen Organisationen, es sei denn, sie sind auch Inhaber einer Organisation oder ihnen wird direkter Zugriff auf das Repository einer Organisation erteilt. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners.
|
||||
|
||||
You can add as many enterprise owners as you'd like to your enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business.
|
||||
An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% if currentVersion == "free-pro-team@latest" %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business.
|
||||
|
||||
### Enterprise-Mitglieder
|
||||
|
||||
@@ -52,7 +52,7 @@ Billing managers only have access to your enterprise's billing settings. Billing
|
||||
- Liste der Abrechnungsmanager anzeigen
|
||||
- Andere Abrechnungsmanager hinzufügen oder entfernen
|
||||
|
||||
Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Abrechnungsmanager müssen über ein persönliches Konto auf {% data variables.product.prodname_dotcom %} verfügen.
|
||||
Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Abrechnungsmanager müssen über ein persönliches Konto auf {% data variables.product.prodname_dotcom %} verfügen.
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
|
||||
@@ -15,6 +15,8 @@ versions:
|
||||
|
||||
Enterprise-Konten sind derzeit für {% data variables.product.prodname_enterprise %}-Kunden verfügbar, die per Rechnung bezahlen. Die Abrechnung für alle Organisationen und {% data variables.product.prodname_ghe_server %}-Instanzen, die mit Deinem Enterprise-Konto verbunden sind, wird in eine einzige Rechnung für alle Deine bezahlten {% data variables.product.prodname_dotcom_the_website %}-Dienste zusammengefasst (inklusive bezahlte Lizenzen in Organisationen, {% data variables.large_files.product_name_long %}-Datenpakete und Abonnements für {% data variables.product.prodname_marketplace %}-Apps).
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."{% endif %}
|
||||
|
||||
For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)."
|
||||
|
||||
### Abonnement und Nutzung für Dein Enterprise-Konto anzeigen
|
||||
|
||||
@@ -50,7 +50,7 @@ Der Repository-Inhaber besitzt die vollständige Kontrolle über das Repository.
|
||||
| Codeinhaber für das Repository definieren | „[Informationen zu Codeinhabern](/github/creating-cloning-and-archiving-repositories/about-code-owners)“ |
|
||||
| Archive the repository | "[About archiving repositories](/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)" |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Sicherheitshinweise erstellen | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
|
||||
| Eine Sponsorenschaltfläche anzeigen | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |
|
||||
| Eine Sponsorenschaltfläche anzeigen | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %}
|
||||
|
||||
### Collaborator access for a repository owned by a user account
|
||||
|
||||
@@ -25,8 +25,6 @@ Bevor Sie mit Jekyll eine {% data variables.product.prodname_pages %}-Website er
|
||||
|
||||
{% data reusables.pages.new-or-existing-repo %}
|
||||
|
||||
{% data reusables.pages.private_pages_are_public_warning %}
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
{% data reusables.repositories.owner-drop-down %}
|
||||
{% data reusables.pages.create-repo-name %}
|
||||
@@ -36,6 +34,8 @@ Bevor Sie mit Jekyll eine {% data variables.product.prodname_pages %}-Website er
|
||||
|
||||
{% data reusables.pages.must-have-repo-first %}
|
||||
|
||||
{% data reusables.pages.private_pages_are_public_warning %}
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. Wenn Du noch keine lokale Kopie Deines Repositorys besitzt, navigiere zu dem Speicherort, an dem Du die Quelldateien Deiner Website speichern möchtest, und ersetze dabei _PARENT-FOLDER_ durch den Ordner, der den Ordner für Dein Repository enthalten soll.
|
||||
```shell
|
||||
|
||||
@@ -20,8 +20,6 @@ versions:
|
||||
|
||||
{% data reusables.pages.new-or-existing-repo %}
|
||||
|
||||
{% data reusables.pages.private_pages_are_public_warning %}
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
{% data reusables.repositories.owner-drop-down %}
|
||||
{% data reusables.pages.create-repo-name %}
|
||||
@@ -33,6 +31,8 @@ versions:
|
||||
|
||||
{% data reusables.pages.must-have-repo-first %}
|
||||
|
||||
{% data reusables.pages.private_pages_are_public_warning %}
|
||||
|
||||
{% data reusables.pages.navigate-site-repo %}
|
||||
{% data reusables.pages.decide-publishing-source %}
|
||||
3. Wenn Deine ausgewählte Veröffentlichungsquelle bereits vorhanden ist, navigiere zu dieser Quelle. Wenn Deine ausgewählte Veröffentlichungsquelle nicht vorhanden ist, erstelle die Veröffentlichungsquelle.
|
||||
|
||||
@@ -57,7 +57,7 @@ Library name | Repository | |---|---| **NodeJS GitHub library**| [pksunkara/octo
|
||||
|
||||
### Julia
|
||||
|
||||
Library name | Repository | |---|---| **Github.jl**|[WestleyArgentum/Github.jl](https://github.com/WestleyArgentum/GitHub.jl)
|
||||
Library name | Repository | |---|---| **GitHub.jl**|[WestleyArgentum/GitHub.jl](https://github.com/WestleyArgentum/GitHub.jl)
|
||||
|
||||
### OCaml
|
||||
|
||||
@@ -65,11 +65,11 @@ Library name | Repository | |---|---| **ocaml-github**|[mirage/ocaml-github](htt
|
||||
|
||||
### Perl
|
||||
|
||||
Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::Github**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:Github CPAN](https://metacpan.org/pod/Net::GitHub)
|
||||
Library name | Repository | metacpan Website for the Library |---|---|---| **Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub) **Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub)
|
||||
|
||||
### PHP
|
||||
|
||||
Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-Github](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GithubAPI](https://github.com/FlexyProject/GitHubAPI)
|
||||
Library name | Repository |---|---| **GitHub PHP Client**|[tan-tan-kanarek/github-php-client](https://github.com/tan-tan-kanarek/github-php-client) **PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) **GitHub API**|[yiiext/github-api](https://github.com/yiiext/github-api) **GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api) **GitHub Nette Extension**|[kdyby/github](https://github.com/kdyby/github) **GitHub API Easy Access**|[milo/github-api](https://github.com/milo/github-api) **GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) **PHP7 Client & WebHook wrapper**|[FlexyProject/GitHubAPI](https://github.com/FlexyProject/GitHubAPI)
|
||||
|
||||
### Python
|
||||
|
||||
|
||||
@@ -129,7 +129,7 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar
|
||||
|
||||
> {
|
||||
> "message": "Bad credentials",
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}/v3"
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}"
|
||||
> }
|
||||
```
|
||||
|
||||
@@ -141,7 +141,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f
|
||||
> HTTP/1.1 403 Forbidden
|
||||
> {
|
||||
> "message": "Maximum number of login attempts exceeded. Please try again later.",
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}/v3"
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}"
|
||||
> }
|
||||
```
|
||||
|
||||
@@ -358,7 +358,7 @@ If you exceed the rate limit, an error response returns:
|
||||
|
||||
> {
|
||||
> "message": "API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}/v3/#rate-limiting"
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting"
|
||||
> }
|
||||
```
|
||||
|
||||
@@ -403,7 +403,7 @@ If your application triggers this rate limit, you'll receive an informative resp
|
||||
|
||||
> {
|
||||
> "message": "You have triggered an abuse detection mechanism and have been temporarily blocked from content creation. Please retry your request again later.",
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}/v3/#abuse-rate-limits"
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits"
|
||||
> }
|
||||
```
|
||||
|
||||
|
||||
@@ -141,7 +141,7 @@ Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-
|
||||
|
||||
### Inactive deployments
|
||||
|
||||
When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
|
||||
When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository to the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
|
||||
|
||||
You can communicate that a transient environment no longer exists by setting its `state` to `inactive`. Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it.
|
||||
|
||||
|
||||
@@ -1,7 +1,12 @@
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
|
||||
**Note:** {% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. The beta has ended. {% data variables.product.prodname_actions %} is now generally available in {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
|
||||
|
||||
<br/>
|
||||
|
||||
- For more information about upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)."
|
||||
- For more information about configuring {% data variables.product.prodname_actions %} after you upgrade, see the [documentation for {% data variables.product.prodname_ghe_server %} 3.0](/enterprise-server@3.0/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server).
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
* {% data reusables.actions.enterprise-hardware-considerations %}
|
||||
* Review the hardware requirements for {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
|
||||
* TLS must be configured for {% data variables.product.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)."
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
{% data variables.product.prodname_ghe_server %} requires additional CPU and memory resources when {% data variables.product.prodname_actions %} is enabled. Before enabling {% data variables.product.prodname_actions %}, review the "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" and ensure that you satisfy the minimum requirements for the features that you want to enable on {% data variables.product.product_location %}.
|
||||
If you {% if currentVersion == "enterprise-server@2.22" %} configured the beta of{% else %} configure{% endif %} {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, we recommend that you provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
{% note %}
|
||||
|
||||
**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license.
|
||||
**Note:** If you enable {% data variables.product.prodname_GH_advanced_security %}, committers to these repositories will use seats on your {% data variables.product.prodname_GH_advanced_security %} license. This option controls access to all {% data variables.product.prodname_advanced_security %} features including {% if currentVersion == "free-pro-team@latest" %}dependency review,{% endif %} {% data variables.product.prodname_code_scanning %}, and {% data variables.product.prodname_secret_scanning %}.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -15,7 +15,7 @@
|
||||
</td>
|
||||
|
||||
<td>
|
||||
Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository#enabling-code-scanning-using-actions">Enabling {% data variables.product.prodname_code_scanning %} using actions</a>") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system">Running code scanning in your CI system</a>").
|
||||
Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system">Running code scanning in your CI system</a>").
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -25,7 +25,7 @@
|
||||
</td>
|
||||
|
||||
<td>
|
||||
Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository#enabling-code-scanning-using-actions">Enabling {% data variables.product.prodname_code_scanning %} using actions</a>") or generated externally and uploaded to {% data variables.product.product_name %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">Uploading a SARIF file to {% data variables.product.prodname_dotcom %}</a>").
|
||||
Using {% data variables.product.prodname_actions %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions">Setting up {% data variables.product.prodname_code_scanning %} using actions</a>") or generated externally and uploaded to {% data variables.product.product_name %} (see "<a href="/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github">Uploading a SARIF file to {% data variables.product.prodname_dotcom %}</a>").
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@@ -8,7 +8,7 @@ The following table shows, for each package manager:
|
||||
| -------------- | ---------------- | ------------------------- |:--------------------:|:---------:|
|
||||
| Bundler | `bundler` | v1 | | **✓** |
|
||||
| Cargo | `cargo` | v1 | **✓** | |
|
||||
| Composer | `composer` | v1,v2 | **✓** | |
|
||||
| Composer | `composer` | v1, v2 | **✓** | |
|
||||
| Docker | `docker` | v1 | **✓** | |
|
||||
| Elixir | `mix` | v1 | **✓** | |
|
||||
| Elm | `elm` | v0.18, v0.19 | **✓** | |
|
||||
@@ -17,7 +17,7 @@ The following table shows, for each package manager:
|
||||
| Go modules | `gomod` | v1 | **✓** | **✓** |
|
||||
| Gradle | `gradle` | see (A) below | **✓** | |
|
||||
| Maven | `maven` | see (B) below | **✓** | |
|
||||
| npm | `npm` | v6 | **✓** | |
|
||||
| npm | `npm` | v6, v7 | **✓** | |
|
||||
| NuGet | `nuget` | <= 4.8.</br>see (C) below | **✓** | |
|
||||
| pip | `pip` | v20 | | |
|
||||
| pipenv | `pip` | <= 2018.11.26 | | |
|
||||
|
||||
@@ -1 +1,13 @@
|
||||
1. Klicke im Menü **File** (Datei) auf ** Clone repository** (Repository klonen).
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
1. Click **Choose...** and navigate to a local path where you want to clone the repository.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
14
translations/de-DE/data/reusables/desktop/click-clone.md
Normal file
14
translations/de-DE/data/reusables/desktop/click-clone.md
Normal file
@@ -0,0 +1,14 @@
|
||||
1. Klicke auf **Clone** (Klonen).
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -1 +1,13 @@
|
||||
1. Klicke auf die Registerkarte, die dem Speicherort des zu klonenden Repositorys entspricht. Du kannst auch auf **URL** klicken, um den Repository-Speicherort manuell einzugeben.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -1 +1,14 @@
|
||||
1. Wähle in der Liste das zu klonende Repository aus.
|
||||
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
@@ -0,0 +1,42 @@
|
||||
1. If you plan to use this fork for contributing to the original upstream repository, click **To contribute to the parent project**.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
2. If you plan to use this fork for a project not connected to the upstream, click **For my own purposes**.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
3. Click **Continue**.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -0,0 +1,14 @@
|
||||
1. Open the **Repository** menu, then click **Repository settings...**.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -0,0 +1,28 @@
|
||||
1. Click **Fork behavior**, then select how you want to use the fork.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
2. Klicke auf **Save** (Speichern).
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the amounts including with your account.
|
||||
@@ -0,0 +1 @@
|
||||
1. Under "Billing", click **Payment information**.
|
||||
@@ -0,0 +1 @@
|
||||
For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)."
|
||||
@@ -1,37 +1,13 @@
|
||||
{% data variables.product.prodname_ghe_server %} wird auf den folgenden EC2-Instance-Typen unterstützt. Weitere Informationen findest Du auf der [Übersichtsseite zu AWS-EC2-Instance-Typen](http://aws.amazon.com/ec2/instance-types/).
|
||||
{% data variables.product.prodname_ghe_server %} is supported on the following EC2 instance sizes. Weitere Informationen findest Du auf der [Übersichtsseite zu AWS-EC2-Instance-Typen](http://aws.amazon.com/ec2/instance-types/).
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | ---------------------------------- |
|
||||
| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge |
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | ---------------------------------- |
|
||||
| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge |
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | -------------------------------------------------------------------- |
|
||||
| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge |
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | --------------------- |
|
||||
| M3 | m3.xlarge, m3.2xlarge |
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | ----------------------------------------------------------- |
|
||||
| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge |
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | --------------------------------------------------------------------- |
|
||||
| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge |
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | -------------------------------------------------------------------- |
|
||||
| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge |
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %}
|
||||
|
||||
| EC2-Instance-Typ | Modell |
|
||||
| ---------------- | ------------------------ |
|
||||
| X1 | x1.16xlarge, x1.32xlarge |
|
||||
| Typ | Size |
|
||||
|:--- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge |
|
||||
| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge |
|
||||
| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge |
|
||||
| M3 | m3.xlarge, m3.2xlarge |
|
||||
| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge |
|
||||
| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge |
|
||||
| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge |
|
||||
| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.19" %}, r5n.large, r5n.xlarge, r5n.2xlarge, r5n.4xlarge, r5n.12xlarge, r5n.24xlarge, r5a.large, r5a.xlarge, r5a.2xlarge, r5a.4xlarge, r5a.12xlarge, r5a.24xlarge{% endif %}
|
||||
| X1 | x1.16xlarge, x1.32xlarge |
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
- [Minimum requirements](#minimum-requirements){% if currentVersion == "enterprise-server@2.22" %}
|
||||
- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}{% if currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
- [Optional features](#optional-features){% endif %}
|
||||
- [Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% endif %}
|
||||
- [Speicher](#storage)
|
||||
- [CPU and memory](#cpu-and-memory)
|
||||
|
||||
@@ -8,20 +7,7 @@
|
||||
|
||||
We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better.
|
||||
|
||||
{% data reusables.enterprise_installation.hardware-rec-table %}{% if currentVersion ver_gt "enterprise-server@2.21" %} If you enable {% if currentVersion == "enterprise-server@2.22" %}the beta for {% endif %}{% data variables.product.prodname_actions %}, review the following requirements and recommendations.
|
||||
|
||||
- You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners)“.
|
||||
- You must configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
|
||||
- You may need to configure additional CPU and memory resources. The additional resources you need to provision for {% data variables.product.prodname_actions %} depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations.
|
||||
|
||||
| Maximum jobs per minute | Additional vCPUs | Additional memory |
|
||||
|:----------------------- | ----------------:| -----------------:|
|
||||
| Light testing | 4 | 30.5 GB |
|
||||
| 25 | 8 | 61 GB |
|
||||
| 35 | 16 | 122 GB |
|
||||
| 100 | 32 | 244 GB |
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.enterprise_installation.hardware-rec-table %}
|
||||
|
||||
#### Speicher
|
||||
|
||||
@@ -31,7 +17,7 @@ Your instance requires a persistent data disk separate from the root disk. Weite
|
||||
|
||||
{% if currentVersion ver_gt "enterprise-server@2.21" %}
|
||||
|
||||
If you enable{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you'll need to configure external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
|
||||
To configure{% if currentVersion == "enterprise-server@2.22" %} the beta of{% endif %} {% data variables.product.prodname_actions %}, you must provide external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -39,7 +25,7 @@ You can resize your instance's root disk by building a new instance or using an
|
||||
|
||||
#### CPU and memory
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} requires more CPU and memory resources depending on levels of activity for users, automations, and integrations.
|
||||
The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations. {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data reusables.actions.enterprise-hardware-considerations %}{% endif %}
|
||||
|
||||
{% data reusables.enterprise_installation.increasing-cpus-req %}
|
||||
|
||||
|
||||
@@ -1,20 +1,20 @@
|
||||
{% if currentVersion ver_gt "enterprise-server@2.21" %}
|
||||
{% if currentVersion == "enterprise-server@2.22" %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If you enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %}, your instance requires additional hardware resources. Minimum requirements for an instance with {% if currentVersion == "enterprise-server@2.22" %}beta{% else %}optional{% endif %} features enabled are **bold** in the following table. For more information, see "{% if currentVersion == "enterprise-server@2.22" %}[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222){% else %}[Optional features](#optional-features){% endif %}."
|
||||
**Note**: If you joined the beta for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} and enabled the features, your instance requires additional hardware resources. Minimum requirements for an instance with beta features enabled are **bold** in the following table. For more information, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
| Benutzerlizenzen | vCPUs | Arbeitsspeicher | Attached-Storage | Root-Storage |
|
||||
|:---------------------------------------------------------- | --------------------------------------------:| ----------------------------------------------------:| ----------------------------------------------------:| ------------:|
|
||||
| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | 2<br/>or [**4**](#optional-features) | 16 GB<br/>or [**32 GB**](#optional-features) | 100 GB<br/>or [**150 GB**](#optional-features) | 200 GB |
|
||||
| 10–3000 | 4<br/>or [**8**](#optional-features) | 32 GB<br/>or [**48 GB**](#optional-features) | 250 GB<br/>or [**300 GB**](#optional-features) | 200 GB |
|
||||
| 3000–5000 | 8<br/>or [**12**](#optional-features) | 64 GB | 500 GB | 200 GB |
|
||||
| 5000–8000 | 12<br/>or [**16**](#optional-features) | 96 GB | 750 GB | 200 GB |
|
||||
| 8000–10000+ | 16<br/>or [**20**](#optional-features) | 128 GB<br/>or [**160 GB**](#optional-features) | 1000 GB | 200 GB |
|
||||
| Benutzerlizenzen | vCPUs | Arbeitsspeicher | Attached-Storage | Root-Storage |
|
||||
|:---------------------------------------------------------- | -----:| ---------------:| ----------------:| ------------:|
|
||||
| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | 4 | 32 GB | 150 GB | 200 GB |
|
||||
| 10–3000 | 8 | 48 GB | 300 GB | 200 GB |
|
||||
| 3000–5000 | 12 | 64 GB | 500 GB | 200 GB |
|
||||
| 5000–8000 | 16 | 96 GB | 750 GB | 200 GB |
|
||||
| 8000–10000+ | 20 | 160 GB | 1000 GB | 200 GB |
|
||||
|
||||
{% else %}
|
||||
|
||||
@@ -28,22 +28,20 @@
|
||||
|
||||
{% endif %}
|
||||
|
||||
For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)."
|
||||
{% data reusables.enterprise_installation.about-adjusting-resources %}
|
||||
|
||||
{% if currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
If you plan to configure {% data variables.product.prodname_actions %} for your instance, you should provision additional resources. You must also configure at least one self-hosted runner to execute workflows. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "enterprise-server@2.22" %}
|
||||
|
||||
#### Beta features in {% data variables.product.prodname_ghe_server %} 2.22
|
||||
|
||||
You can sign up for beta features available in {% data variables.product.prodname_ghe_server %} 2.22 such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22#release-2.22.0) on the {% data variables.product.prodname_enterprise %} website.
|
||||
{% data variables.product.prodname_ghe_server %} 2.22 offered features in beta, such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_code_scanning %}. For more information, see the [{% data variables.product.prodname_ghe_server %} 2.22 release notes](/enterprise-server@2.22/admin/release-notes#2.22.0).
|
||||
|
||||
If you enable beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)".
|
||||
|
||||
{% elsif currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
#### Optional features
|
||||
|
||||
You can enable optional features for {% data variables.product.prodname_ghe_server %}, such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)" or "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
|
||||
|
||||
If you enable optional features, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)".
|
||||
If you enabled beta features for {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information, see "[Minimum requirements](#minimum-requirements)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1 +1 @@
|
||||
Auto-merge for pull requests is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %}
|
||||
Auto-merge for pull requests is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %}
|
||||
|
||||
@@ -1 +1,4 @@
|
||||
{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.
|
||||
{%- elsif currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_code_scanning_capc %} is available if {% data variables.product.prodname_GH_advanced_security %} is enabled for the repository.
|
||||
{%- else %}
|
||||
{% data variables.product.prodname_code_scanning_capc %} is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
| Virtuelle Umgebung | YAML-Workflow-Kennzeichnung |
|
||||
| -------------------- | ------------------------------------ |
|
||||
| Windows Server 2019 | `windows-latest` oder `windows-2019` |
|
||||
| Ubuntu 20.04 | `ubuntu-20.04` |
|
||||
| Ubuntu 18.04 | `ubuntu-latest` oder `ubuntu-18.04` |
|
||||
| Ubuntu 16.04 | `ubuntu-16.04` |
|
||||
| macOS Big Sur 11.0 | `macos-11.0` |
|
||||
| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` |
|
||||
| Virtuelle Umgebung | YAML-Workflow-Kennzeichnung |
|
||||
| -------------------- | -------------------------------------------- |
|
||||
| Windows Server 2019 | `windows-latest` oder `windows-2019` |
|
||||
| Ubuntu 20.04 | `ubuntu-latest` (see note) or `ubuntu-20.04` |
|
||||
| Ubuntu 18.04 | `ubuntu-latest` (see note) or `ubuntu-18.04` |
|
||||
| Ubuntu 16.04 | `ubuntu-16.04` |
|
||||
| macOS Big Sur 11.0 | `macos-11.0` |
|
||||
| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` |
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** The Ubuntu 20.04 virtual environment is currently provided as a preview only. The `ubuntu-latest` YAML workflow label still uses the Ubuntu 18.04 virtual environment.
|
||||
**Note:** The `ubuntu-latest` label is currently being migrated from the Ubuntu 18.04 virtual environment to Ubuntu 20.04. Specifying the `ubuntu-latest` label during the migration might use either virtual environment. To explicitly use Ubuntu 20.04 or Ubuntu 18.04, specify `ubuntu-20.04` or `ubuntu-18.04`. When the migration is complete, `ubuntu-latest` will use the Ubuntu 20.04 virtual environment. For more information about the migration, see "[Ubuntu-latest workflows will use Ubuntu-20.04](https://github.com/actions/virtual-environments/issues/1816)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -6,3 +6,4 @@ Organisationen beinhalten:
|
||||
- [Nested teams that reflect your company or group's structure](/articles/about-teams) with cascading access permissions and mentions{% if currentVersion != "github-ae@latest" %}
|
||||
- Die Möglichkeit für Organisationsinhaber, den [Zwei-Faktor-Authentifizierungsstatus (2FA)](/articles/about-two-factor-authentication) der Mitglieder anzuzeigen
|
||||
- The option to [require all organization members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization){% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}- The option to purchase a license for {% data variables.product.prodname_GH_advanced_security %} and use the features on private repositories. {% data reusables.advanced-security.more-info-ghas %}{% endif %}
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
Wenn Deine Website ein unabhängiges Projekt ist, kannst Du ein neues Repository erstellen, um den Quellcode Deiner Website zu speichern. If your site is associated with an existing project, you can add the source code {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}to that project's repository, in a `/docs` folder on the default branch or on a different branch.{% else %}for your site to a `gh-pages` branch or a `docs` folder on the `master` branch in that project's repository.{% endif %} For example, if you're creating a site to publish documentation for a project that's already on {% data variables.product.product_name %}, you may want to store the source code for the site in the same repository as the project.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}If the account that owns the repository uses {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_free_team %}, the repository must be public.{% endif %}
|
||||
|
||||
Wenn Du eine Website in einem vorhandenen Repository erstellen möchtest, springe zum Abschnitt „[Erstellen Deiner Website](#creating-your-site)".
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
You can configure a pull request to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
| Schlüssel | Typ | Beschreibung |
|
||||
| --------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `action` | `string` | die Aktion, die durchgeführt wurde. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. |
|
||||
| Schlüssel | Typ | Beschreibung |
|
||||
| --------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `action` | `string` | die Aktion, die durchgeführt wurde. Can be one of `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `converted_to_draft`, `labeled`, `unlabeled`, `synchronize`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}`auto_merge_enabled`, `auto_merge_disabled`,{% endif %} `locked`, `unlocked`, or `reopened`. If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged. |
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
- labels
|
||||
-
|
||||
title: Add releases to GitHub
|
||||
description: Publish Github releases in an action
|
||||
description: Publish GitHub releases in an action
|
||||
languages: 'Dockerfile, Shell'
|
||||
href: elgohr/Github-Release-Action
|
||||
tags:
|
||||
@@ -32,7 +32,7 @@
|
||||
- publishing
|
||||
-
|
||||
title: Publish a docker image to Dockerhub
|
||||
description: A Github Action used to build and publish Docker images
|
||||
description: A GitHub Action used to build and publish Docker images
|
||||
languages: 'Dockerfile, Shell'
|
||||
href: elgohr/Publish-Docker-Github-Action
|
||||
tags:
|
||||
@@ -123,7 +123,7 @@
|
||||
- publishing
|
||||
-
|
||||
title: Label your Pull Requests auto-magically (using committed files)
|
||||
description: Github action to label your pull requests auto-magically (using committed files)
|
||||
description: GitHub action to label your pull requests auto-magically (using committed files)
|
||||
languages: 'TypeScript, Dockerfile, JavaScript'
|
||||
href: Decathlon/pull-request-labeler-action
|
||||
tags:
|
||||
@@ -132,7 +132,7 @@
|
||||
- labels
|
||||
-
|
||||
title: Add Label to your Pull Requests based on the author team name
|
||||
description: Github action to label your pull requests based on the author name
|
||||
description: GitHub action to label your pull requests based on the author name
|
||||
languages: 'TypeScript, JavaScript'
|
||||
href: JulienKode/team-labeler-action
|
||||
tags:
|
||||
|
||||
@@ -147,10 +147,10 @@ current-340-version: '11.10.354'
|
||||
#Developer site product variables
|
||||
#Use this inside command-line and other code blocks
|
||||
doc_url_pre: >-
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://developer.github.com{% else %}https://developer.github.com/enterprise/{{currentVersion}}{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://docs.github.com/rest{% elsif enterpriseServerVersions contains currentVersion %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif currentVersion == "github-ae@latest" %}https://docs.github.com/github-ae@latest/rest{% endif %}
|
||||
#Use this inside command-line code blocks
|
||||
api_url_pre: >-
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% else %}http(s)://<em>[hostname]</em>/api/v3{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://<em>[hostname]</em>/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.<em>[hostname]</em>{% endif %}
|
||||
#Use this inside command-line code blocks
|
||||
#Enterprise OAuth paths that don't include "/graphql" or "/api/v3"
|
||||
oauth_host_code: >-
|
||||
@@ -159,10 +159,10 @@ device_authorization_url: >-
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}[`https://github.com/login/device`](https://github.com/login/device){% else %}`http(s)://[hostname]/login/device`{% endif %}
|
||||
#Use this all other code blocks
|
||||
api_url_code: >-
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% else %}http(s)://[hostname]/api/v3{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/v3{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]{% endif %}
|
||||
#Use this inside command-line code blocks
|
||||
graphql_url_pre: >-
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% else %}http(s)://<em>[hostname]</em>/api/graphql{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://<em>[hostname]</em>/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.<em>[hostname]</em>/graphql{% endif %}
|
||||
#Use this all other code blocks
|
||||
graphql_url_code: >-
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% else %}http(s)://[hostname]/api/graphql{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% elsif enterpriseServerVersions contains currentVersion %}http(s)://[hostname]/api/graphql{% elsif currentVersion == "github-ae@latest" %}https://api.[hostname]/graphql{% endif %}
|
||||
|
||||
@@ -63,7 +63,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
|
||||
{% data reusables.github-actions.usage-api-requests %}
|
||||
- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
|
||||
|
||||
### Supported operating systems for self-hosted runners
|
||||
### Supported architectures and operating systems for self-hosted runners
|
||||
|
||||
The following operating systems are supported for the self-hosted runner application.
|
||||
|
||||
@@ -92,6 +92,14 @@ The following operating systems are supported for the self-hosted runner applica
|
||||
|
||||
- macOS 10.13 (High Sierra) or later
|
||||
|
||||
#### Architectures
|
||||
|
||||
The following processor architectures are supported for the self-hosted runner application.
|
||||
|
||||
- `x64` - Linux, macOS, Windows.
|
||||
- `ARM64` - Linux only.
|
||||
- `ARM32` - Linux only.
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
### Supported actions on self-hosted runners
|
||||
|
||||
@@ -29,7 +29,7 @@ Un ejecutor auto-hospedado recibe ciertas etiquetas automáticamente cuando se a
|
||||
|
||||
* `autoalojado`: Etiqueta por defecto aplicada a todos los ejecutores autoalojados.
|
||||
* `linux`, `windows`, o `macOS`: Se aplican dependiendo del sistema operativo.
|
||||
* `x86`, `x64`, `ARM`, o `ARM64`: Se aplican dependiendo de la arquitectura del hardware.
|
||||
* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture.
|
||||
|
||||
Puedes utilizar el YAML de tu flujo de trabajo para mandar jobs a las diferentes combinaciones de estas etiquetas. En este ejemplo, un ejecutor auto-hospedado que empate con las tres etiquetas será elegible para ejecutar el job:
|
||||
|
||||
|
||||
@@ -41,12 +41,17 @@ Las máquinas virtuales de Windows están configuradas para ejecutarse como admi
|
||||
|
||||
### Ejecutores y recursos de hardware compatibles
|
||||
|
||||
Cada máquina virtual tiene los mismos recursos de hardware disponibles.
|
||||
|
||||
Hardware specification for Windows and Linux virtual machines:
|
||||
- CPU de 2 núcleos
|
||||
- 7 GB de memoria RAM
|
||||
- 14 GB de espacio en el disco SSD
|
||||
|
||||
Hardware specification for macOS virtual machines:
|
||||
- CPU de 3 núcleos
|
||||
- 14 GB de memoria RAM
|
||||
- 14 GB de espacio en el disco SSD
|
||||
|
||||
{% data reusables.github-actions.supported-github-runners %}
|
||||
|
||||
{% data reusables.github-actions.ubuntu-runner-preview %}
|
||||
@@ -71,9 +76,13 @@ Las herramientas de software que se incluyen en los ejecutores hospedados en {%
|
||||
|
||||
Los ejecutores alojados en {% data variables.product.prodname_dotcom %} incluyen las herramientas integradas predeterminadas del sistema operativo, además de los paquetes enumerados en las referencias anteriores. Por ejemplo, los ejecutores de Ubuntu y macOS incluyen `grep`, `find` y `which`, entre otras herramientas predeterminadas.
|
||||
|
||||
Las bitácoras de flujo de trabajo incluyen un enlace a las herramientas preinstaladas en el ejecutor. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)".
|
||||
Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Virtual Environment` section. The link following `Included Software` will tell you the the preinstalled tools on the runner that ran the workflow.  For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
|
||||
|
||||
Si hay alguna herramienta que quieras solicitar, abre una propuesta en [actions/virtual-environments](https://github.com/actions/virtual-environments).
|
||||
We recommend using actions to interact with the software installed on runners. This approach has several benefits:
|
||||
- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters
|
||||
- It ensures the tool versions used in your workflow will remain the same regardless of software updates
|
||||
|
||||
Si hay alguna herramienta que quieras solicitar, abre una propuesta en [actions/virtual-environments](https://github.com/actions/virtual-environments). This repository also contains announcements about all major software updates on runners.
|
||||
|
||||
### Direcciones IP
|
||||
|
||||
|
||||
@@ -73,7 +73,7 @@ Si el servidor en donde estás ejecutando
|
||||
{% endif %}
|
||||
|
||||
#### Habilitar el escaneo de código para los repositorios individuales
|
||||
Después de que configuras un ejecutor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}y aprovisionas las acciones,{% endif %} los usuarios pueden habilitar el {% data variables.product.prodname_code_scanning %} para los repositorios individuales de {% data variables.product.product_location %}. El flujo de trabajo predeterminado de {% data variables.product.prodname_code_scanning %} utiliza el evento `on.push` para activar el escaneo de código cada vez que alguien carga información a cualquier rama que contenga el archivo de flujo de trabajo.
|
||||
Después de que configuras un ejecutor auto-hospedado, {% if currentVersion == "enterprise-server@2.22" %}y aprovisionas las acciones,{% endif %} los usuarios pueden habilitar el {% data variables.product.prodname_code_scanning %} para los repositorios individuales de {% data variables.product.product_location %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository)."
|
||||
|
||||
### Ejecutar el {% data variables.product.prodname_code_scanning %} utilizando el {% data variables.product.prodname_codeql_runner %}
|
||||
Si no quieres utilizar {% data variables.product.prodname_actions %}, puedes ejecutar el {% data variables.product.prodname_code_scanning %} utilizando el {% data variables.product.prodname_codeql_runner %}.
|
||||
|
||||
@@ -20,7 +20,7 @@ Para el cifrado en tránsito, {% data variables.product.product_name %} utiliza
|
||||
|
||||
La llave que proporciones se almacena en un módulo de seguridad de hardware (HSM) en una bóveda de llaves que administra {% data variables.product.company_short %}.
|
||||
|
||||
Para configurar tu llave de cifrado, utiliza la API de REST. Existen varias terminales de la API, por ejemplo, para verificar el estado de cifrado, actualiza tu llave de cifrado y bórrala. Nota que el borrar tu llave hará que tu empresa se congele. Para obtener más información acerca de las terminales de la API, consulta la sección "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST.
|
||||
Para configurar tu llave de cifrado, utiliza la API de REST. There are a number of API endpoints, for example to check the status of encryption, update your encryption key, and disable your encryption key. Note that disabling your key will freeze your enterprise. Para obtener más información acerca de las terminales de la API, consulta la sección "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST.
|
||||
|
||||
### Agregar o actualizar una llave de cifrado
|
||||
|
||||
@@ -48,24 +48,24 @@ Tu llave privada de RSA de 2048 bits deberá estar en formato PEM, por ejemplo,
|
||||
curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
|
||||
```
|
||||
|
||||
### Borrar tu llave de cifrado
|
||||
### Disabling your encryption key
|
||||
|
||||
Para congelar tu empresa, por ejemplo, en caso de alguna irrupción, puedes inhabilitar el cifrado estático si borras tu llave de cifrado.
|
||||
To freeze your enterprise, for example in the case of a breach, you can disable encryption at rest by marking your encryption key as disabled.
|
||||
|
||||
Para descongelar tu empresa después de que hayas borrado tu llave de cifrado, contacta a soporte. Para obtener más información, consulta la sección "[Acerca de {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)".
|
||||
|
||||
1. Para borrar tu llave e inhabilitar el cifrado estático, utiliza la terminal `DELETE /enterprise/encryption`.
|
||||
1. To disable your key and encryption at rest, use the `DELETE /enterprise/encryption` endpoint. This operation does not delete the key permanently.
|
||||
|
||||
```shell
|
||||
curl -X DELETE http(s)://<em>hostname</em>/api/v3/enterprise/encryption
|
||||
```
|
||||
|
||||
2. Opcionalmente, verifica el estado de la operación de borrado.
|
||||
2. Opcionalmente, verifica el estado de la operación de borrado. It takes approximately ten minutes to disable encryption at rest.
|
||||
|
||||
```shell
|
||||
curl -X GET http(s)://<em>hostname</em>/api/v3/enterprise/encryption/status/<em>request_id</em>
|
||||
```
|
||||
|
||||
To unfreeze your enterprise after you've disabled your encryption key, contact support. Para obtener más información, consulta la sección "[Acerca de {% data variables.contact.enterprise_support %}](/admin/enterprise-support/about-github-enterprise-support)".
|
||||
|
||||
### Leer más
|
||||
|
||||
- "[Cifrado estático](/rest/reference/enterprise-admin#encryption-at-rest)" en la documentación de la API de REST
|
||||
|
||||
@@ -29,6 +29,26 @@ versions:
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
|
||||
|
||||
### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
|
||||
|
||||
Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
|
||||
|
||||
Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
|
||||
|
||||
| Licencias de usuario | vCPU | Memoria | Almacenamiento conectado | Almacenamiento raíz |
|
||||
|:---------------------------------------- | -------------------------------:| ---------------------------------------:| ---------------------------------------:| -------------------:|
|
||||
| Prueba, Demo o 10 usuarios no frecuentes | **4**<br/>_Up from 2_ | **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ | 200 GB |
|
||||
| 10-3000 | **8**<br/>_Up from 4_ | **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ | 200 GB |
|
||||
| 3000-5000 | **12**<br/>_Up from 8_ | 64 GB | 500 GB | 200 GB |
|
||||
| 5000-8000 | **16**<br/>_Up from 12_ | 96 GB | 750 GB | 200 GB |
|
||||
| 8000-10000+ | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ | 1000 GB | 200 GB |
|
||||
|
||||
{% data reusables.enterprise_installation.about-adjusting-resources %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Tomar una instantánea
|
||||
|
||||
Una instantánea es un punto de verificación de una máquina virtual (VM) en un momento en el tiempo. Recomendamos firmemente tomar una instantánea antes de actualizar tu máquina virtual para que si falla una actualización, puedas revertir tu VM nuevamente a la instantánea. Si no estás actualizando a un nuevo lanzamiento de característica, debes tomar una instantánea de VM. Si estás actualizando a un nuevo lanzamiento de patch, puedes adjuntar el disco de datos existente.
|
||||
|
||||
@@ -9,13 +9,7 @@ versions:
|
||||
enterprise-server: '>=2.22'
|
||||
---
|
||||
|
||||
{% if currentVersion == "enterprise-server@2.22" %}
|
||||
{% note %}
|
||||
|
||||
**Nota:** El soporte para {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} 2.22 es un beta público limitado. Revisa los requisitos de almacenamiento externo mencionados a continuación y [regístrate para el beta](https://resources.github.com/beta-signup/).
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -23,11 +17,33 @@ versions:
|
||||
|
||||
Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_server %} para utilizar {% data variables.product.prodname_actions %}. Esto cubre los requisitos de hardware y software, presenta las opciones de almacenamiento y describe las políticas de administración de seguridad.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Revisar las consideraciones de hardware
|
||||
|
||||
{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.actions.enterprise-hardware-considerations %}
|
||||
|
||||
{% endif %}
|
||||
For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform.
|
||||
|
||||
- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
|
||||
- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
|
||||
- [Plataforma de Google Cloud](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
|
||||
- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
|
||||
- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
|
||||
- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
|
||||
- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations)
|
||||
|
||||
{% data reusables.enterprise_installation.about-adjusting-resources %}
|
||||
|
||||
### Requisitos de almacenamiento externo
|
||||
|
||||
@@ -55,7 +71,7 @@ Para habilitar {% data variables.product.prodname_actions %} en {% data variable
|
||||
|
||||
### Habilitar {% data variables.product.prodname_actions %}
|
||||
|
||||
El soporte de {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} 2.22 se ecuentra en un beta público limitado. [Regístrate para el beta](https://resources.github.com/beta-signup/).
|
||||
{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)."
|
||||
|
||||
### Leer más
|
||||
|
||||
@@ -69,7 +85,7 @@ El soporte de {% data variables.product.prodname_actions %} en {% data variables
|
||||
|
||||
Sigue uno de los procedimientos siguientes para habilitar las {% data variables.product.prodname_actions %} con el proveedor de almacenamiento de tu elección:
|
||||
|
||||
* [Habilitar las GitHub Actions con Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
|
||||
* [Habilitar las GitHub Actions con el almacenamiento de Azure Blob](/admin/github-actions/enabling-github-actions-with-azure-blob-storage)
|
||||
* [Habilitar las GitHub Actions con el almacenamiento de Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage)
|
||||
* [Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage)
|
||||
|
||||
@@ -81,7 +97,7 @@ Puedes utilizar políticas para administrar el acceso a las {% data variables.pr
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores auto-hospedados a nivel de empresa, organización o repositorio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
|
||||
Para ejecutar los flujos de trabajo de {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados. Puedes agregar ejecutores auto-hospedados a nivel de empresa, organización o repositorio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
|
||||
|
||||
### Administrar qué acciones pueden utilizarse en tu empresa
|
||||
|
||||
|
||||
@@ -8,40 +8,40 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
### Clonar repositorios
|
||||
Los repositorios en {% data variables.product.prodname_dotcom %} son remotos. Puedes clonar repositorios públicos de otros dueños. Puedes clonar tu propio repositorio para crear una copia local en tu computadora y sincronizarla entre las dos ubicaciones.
|
||||
### About local repositories
|
||||
Repositories on {% data variables.product.prodname_dotcom %} are remote repositories. You can clone or fork a repository with {% data variables.product.prodname_desktop %} to create a local repository on your computer.
|
||||
|
||||
You can create a local copy of any repository on {% data variables.product.product_name %} that you have access to by cloning the repository. If you own a repository or have write permissions, you can sync between the local and remote locations. Para obtener más información, consulta la sección "[Sincronizar tu rama](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)".
|
||||
|
||||
When you clone a repository, any changes you push to {% data variables.product.product_name %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. Para obtener más información, visita "[Acerca de las ramificaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)."
|
||||
|
||||
When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see "[Managing fork behavior](#managing-fork-behavior)".
|
||||
|
||||
También puedes clonar un repositorio directamente desde {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. Para obtener más información, visita "[Cómo clonar un repositorio desde {% data variables.product.prodname_dotcom %} hacia {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)".
|
||||
|
||||
{% mac %}
|
||||
### Clonar un repositorio
|
||||
|
||||
{% data reusables.desktop.choose-clone-repository %}
|
||||
|
||||
{% data reusables.desktop.cloning-location-tab %}
|
||||
|
||||
{% data reusables.desktop.cloning-repository-list %}
|
||||
|
||||
4. Haz clic en **Choose...** (Elegir...) y, a través de la ventana Finder (Buscador) desplázate hasta la ruta donde deseas clonar el repositorio. 
|
||||
5. Haz clic en **Clone**. 
|
||||
{% data reusables.desktop.choose-local-path %}
|
||||
{% data reusables.desktop.click-clone %}
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
### Bifurcar un repositorio
|
||||
If you clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will create a fork. After creating or cloning a fork, {% data variables.product.prodname_desktop %} will ask how you are planning to use the fork.
|
||||
|
||||
{% data reusables.desktop.choose-clone-repository %}
|
||||
|
||||
{% data reusables.desktop.cloning-location-tab %}
|
||||
|
||||
{% data reusables.desktop.cloning-repository-list %}
|
||||
|
||||
4. Haz clic en **Choose...** (Elegir...) y, a través de Windows Explorer, desplázate hasta la ruta donde deseas clonar el repositorio. 
|
||||
5. Haz clic en **Clone**. 
|
||||
{% data reusables.desktop.choose-local-path %}
|
||||
{% data reusables.desktop.click-clone %}
|
||||
{% data reusables.desktop.fork-type-prompt %}
|
||||
|
||||
{% endwindows %}
|
||||
### Managing fork behavior
|
||||
You can change how a fork behaves with the upstream repository in {% data variables.product.prodname_desktop %}.
|
||||
|
||||
### Ramificar repositorios
|
||||
Puedes utilizar {% data variables.product.prodname_desktop %} para crear una ramificación del repositorio y contribuir con un proyecto en donde no tengas privilegios de escritura. Los cambios en tu ramificación no afectarán al repositorio original. Puedes confirmar los cambios en tu ramificación y generar una solicitud de extracción del repositorio original con los cambios que propones. Para obtener más información, visita "[Acerca de las ramificaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)."
|
||||
{% data reusables.desktop.open-repository-settings %}
|
||||
{% data reusables.desktop.select-fork-behavior %}
|
||||
|
||||
1. Si clonaste un repositorio en donde no tienes privilegios de escritura, intenta confirmar los cambios, {% data variables.product.prodname_desktop %} enviará una alerta de que "No cuentas con privilegios de escritura para el **REPOSITORIO**". Da clic en **crear una ramificación**. 
|
||||
3. Da clic en **Ramificar este repositorio**. 
|
||||
4. Para ver tu ramificación en {% data variables.product.prodname_dotcom %}, da clic en tu foto de perfil en la esquina superior derecha de {% data variables.product.prodname_dotcom %} y posteriormente en **Tus repositorios**. 
|
||||
### Leer más
|
||||
- [Acerca de los repositorios remotos](/github/using-git/about-remote-repositories)
|
||||
|
||||
@@ -9,7 +9,7 @@ versions:
|
||||
|
||||
### Acerca de las etiquetas en {% data variables.product.prodname_desktop %}
|
||||
|
||||
{% data variables.product.prodname_desktop %} te permite crear etiquetas anotadas. Puedes utilizar una etiqueta para marcar un punto individual en el historial de tu repositorio, incluyendo un número de versión para un lanzamiento. Para obtener más información acerca de las etiquetas de lanzamiento, consulta la sección "[Acerca de los lanzamientos](/github/administering-a-repository/about-releases)".
|
||||
{% data variables.product.prodname_desktop %} te permite crear etiquetas anotadas. Tags are associated with commits, so you can use a tag to mark an individual point in your repository's history, including a version number for a release. Para obtener más información acerca de las etiquetas de lanzamiento, consulta la sección "[Acerca de los lanzamientos](/github/administering-a-repository/about-releases)".
|
||||
|
||||
{% data reusables.desktop.tags-push-with-commits %}
|
||||
|
||||
@@ -44,3 +44,7 @@ versions:
|
||||
|
||||
{% data reusables.desktop.history-tab %}
|
||||
{% data reusables.desktop.delete-tag %}
|
||||
|
||||
### Leer más
|
||||
|
||||
- "[Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)" in the Git documentation
|
||||
|
||||
@@ -3,6 +3,8 @@ title: Activar las características beta para las apps
|
||||
intro: 'Puedes probar nuevas características que se lanzan para el beta público para tus {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_app %}s.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
github-ae: '*'
|
||||
---
|
||||
|
||||
{% warning %}
|
||||
|
||||
@@ -110,7 +110,7 @@ El ejemplo anterior utiliza el tiempo de caducidad máximo de 10 minutos, despu
|
||||
```json
|
||||
{
|
||||
"message": "'Expiration' claim ('exp') must be a numeric value representing the future time at which the assertion expires.",
|
||||
"documentation_url": "{% data variables.product.doc_url_pre %}/v3"
|
||||
"documentation_url": "{% data variables.product.doc_url_pre %}"
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ versions:
|
||||
|
||||
### Introducción
|
||||
|
||||
Esta guía te dará una introducción a las [GitHub Apps](/apps/) y a la [API de verificaciones](/rest/reference/checks), las cuales utilizarás para crear un servidor de Integración contínua (CI) que ejecute pruebas.
|
||||
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.
|
||||
|
||||
La IC es una práctica de software que requiere código confirmado frecuente en un repositorio compartido. El código de confirmación generar errores de manera temprana frecuentemente, así como reduce la cantidad de código que necesita un desarrollador para hacer depuraciones cuando encuentra la fuente de un error. Las actualizaciones frecuentes de código facilitan también la fusión de cambios de diferentes miembros de un equipo de desarrollo de software. Esto es excelente para los desarrolladores, que pueden dedicar más tiempo a escribir código y menos tiempo a depurar errores o resolver conflictos de fusión. 🙌
|
||||
|
||||
@@ -49,7 +49,7 @@ Para obtener una idea de lo que hará tu servidor de IC para la API de Verificac
|
||||
|
||||
### Prerrequisitos
|
||||
|
||||
Antes de que inicies, tal vez quieras familiarizarte con las [GitHub Apps](/apps/), los [Webhooks](/webhooks), y con la [API de Verificaciones](/rest/reference/checks), si aún no lo has hecho. Encontrarás más API en los [documentos de la API de REST](/rest). La API de Verificaciones también se encuentra disponible para su uso en [GraphQL](/graphql), pero este inicio rápido se enfoca en REST. Consulta los objetos de [Conjuntos de Verificaciones](/graphql/reference/objects#checksuite) y [Ejecución de Verificación](/graphql/reference/objects#checkrun) de GraphQL para obtener más detalles.
|
||||
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. Encontrarás más API en los [documentos de la API de REST](/rest). La API de Verificaciones también se encuentra disponible para su uso en [GraphQL](/graphql), pero este inicio rápido se enfoca en REST. Consulta los objetos de [Conjuntos de Verificaciones](/graphql/reference/objects#checksuite) y [Ejecución de Verificación](/graphql/reference/objects#checkrun) de GraphQL para obtener más detalles.
|
||||
|
||||
Utilizarás el [Lenguaje de Programación Ruby](https://www.ruby-lang.org/en/), el servicio de entrega de carga útil para el webhook de [Smee](https://smee.io/), la [biblioteca de Ruby Ocktokit.rb](http://octokit.github.io/octokit.rb/) para la API de REST de GitHub, y el [marco de trabajo web Sinatra](http://sinatrarb.com/) para crear tu aplicación de servidor de IC para la API de Verificaciones.
|
||||
|
||||
@@ -203,7 +203,7 @@ Si ves otras apps en la pestaña de verificaciones, significa que tienes otras a
|
||||
|
||||
### Paso 1.4. Actualizar una ejecución de verificación
|
||||
|
||||
Cuando tu método de `create_check_run` se ejecuta, éste solicita a GitHub crear una ejecución de verificación nueva. Cuando GitHub termine de crear la ejecución de verificación, recibirás un evento de webhook de `check_run` con la acción como `created`. Este evento es tu señal para comenzar a ejecutar la verificación.
|
||||
Cuando tu método de `create_check_run` se ejecuta, éste solicita a GitHub crear una ejecución de verificación nueva. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. Este evento es tu señal para comenzar a ejecutar la verificación.
|
||||
|
||||
Necesitas actualizar tu gestor de eventos para buscar la acción que se encuentra como `created`. Mientras actualizas el gestor de eventos, puedes agregar una condicional para la acción que se encuentra como `rerequested`. Cuando alguien re-ejecuta una sola prueba en GitHub, al dar clic en el botón de "Re-ejecutar", GitHub envía a tu app el evento de ejecución de verificación que está como `rerequested`. Cuando una ejecución de verificación se pone como `rerequested`, necesitarás iniciar el proceso desde cero y crear una ejecución de verificación nueva.
|
||||
|
||||
@@ -435,7 +435,7 @@ El código anterior obtiene el nombre completo del repositorio y el SHA de encab
|
||||
|
||||
### Paso 2.3. Ejecutar RuboCop
|
||||
|
||||
¡Genial! Estás clonando el repositorio y creando ejecuciones de verificación al utilizar tu servidor de IC. Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run).
|
||||
¡Genial! Estás clonando el repositorio y creando ejecuciones de verificación al utilizar tu servidor de IC. Ahora te meterás en los detalles más minusciosos del [Limpiador de RuboCop](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) y de las [Anotaciones de la API de Verificaciones](/rest/reference/checks#create-a-check-run).
|
||||
|
||||
El siguiente código ejecuta RuboCop y guarda los errores de estilo en el código con un formato JSON. Agrega el código siguiente debajo de la llamada a `clone_repository` que agregaste en el [paso anterior](#step-22-cloning-the-repository) y sobre el código que actualiza la ejecución de verificación para completarse.
|
||||
|
||||
@@ -447,7 +447,7 @@ logger.debug @report
|
||||
@output = JSON.parse @report
|
||||
```
|
||||
|
||||
Este código utiliza RuboCop en todos los archivos dentro del directorio del repositorio. La opción `--format json` es una manera útil de guardar una copia de los resultados que se han limpiado en un formato que pueda analizar la máquina. See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format.
|
||||
Este código utiliza RuboCop en todos los archivos dentro del directorio del repositorio. La opción `--format json` es una manera útil de guardar una copia de los resultados que se han limpiado en un formato que pueda analizar la máquina. Consulta los [Documentos de RuboCop](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) para obtener más detalles y un ejemplo del formato en JSON.
|
||||
|
||||
Ya que este código almacena los resultados de RuboCop en una variable de `@report`, puede eliminar la salida del repositorio con seguridad. Este código también analiza el JSON para que puedas acceder fácilmente a las claves y valores en tu GitHub App utilizando la variable `@output`.
|
||||
|
||||
@@ -588,7 +588,7 @@ Este código limita la cantidad total de anotaciones a 50. Pero puedes modificar
|
||||
|
||||
Cuando la `offense_count` es de cero, la prueba de IC se muestra como `success`. Si hay errores, este código configura la conclusión como `neutral` para prevenir los errores estrictamente implementados desde los limpiadores de código. Pero puedes cambiar la conclusión a `failure` si quisieras garantizar que el conjunto de verificaciones falle cuando existan errores de limpieza.
|
||||
|
||||
Cuando se reportan los errores, el código anterior itera a través de la matriz de `files` en el reporte de RuboCop. Para cada archivo, extrae la ruta del mismo y configura el nivel de anotcación en `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`.
|
||||
Cuando se reportan los errores, el código anterior itera a través de la matriz de `files` en el reporte de RuboCop. Para cada archivo, extrae la ruta del mismo y configura el nivel de anotcación en `notice`. Puedes incluso ir más allá y especificar ls niveles de advertencia para cada tipo de [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), pero para simplificar todo aún más en esta guía rápida, todos los errores se configurarán en un nivel de `notice`.
|
||||
|
||||
Este código también itera a través de cada error en la matriz de `offenses` y recolecta la ubicación de la falta y el mensaje de error. Después de extraer la información requerida, el código crea una anotación para cada error y lo almacena en la matriz de `annotations`. Ya que las anotaciones solo son compatibles con las columnas de inicio y fin en la misma línea, `start_column` y `end_column` se agregarán únicamente al objeto `annotation` si los valores iniciales y finales de la línea son los mismos.
|
||||
|
||||
@@ -718,7 +718,7 @@ Si las anotaciones se relacionan con un archivo que ya se incluya en la solicitu
|
||||
|
||||
Si has llegado hasta aquí, ¡excelente! 👏 Ya creaste una prueba de IC. En esta sección vas a agregar una característica más que utiliza a RuboCop para corregir automáticamente los errores que encuentre. Ya agregaste el botón de "Corregir esto" en la [sección anterior](#step-25-updating-the-check-run-with-ci-test-results). Ahora agregarás el código para gestionar el evento de ejecución de verificación `requested_action` que se activa cuando alguien da clic en dicho botón.
|
||||
|
||||
The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. Cuado utilizas la característica de `--auto-correct`, se aplican las actualizaciones en los archivos locales del servidor. Necesitarás cargar los cambios a GitHub después de que RuboCop haga su magia.
|
||||
La herramienta de RuboCop [ofrece](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) la opción de línea de comandos `--auto-correct` para corregir automáticamente los errores que encuentre. Cuado utilizas la característica de `--auto-correct`, se aplican las actualizaciones en los archivos locales del servidor. Necesitarás cargar los cambios a GitHub después de que RuboCop haga su magia.
|
||||
|
||||
Para cargar un repositorio, tu app debe tener permisos de escritura para "contenido de repositorio". Estos permisos los configuraste en el [Paso 2.2. Clonar el repositorio](#step-22-cloning-the-repository) como **Lectura & escritura**, así que estás listo.
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ Las GitHub Apps utilizan [reglas móviles para los límites de tasa](/apps/build
|
||||
|
||||
#### Registrar una GitHub App nueva
|
||||
|
||||
Una vez que hayas decidido hacer el cambio hacia GitHub Apps, necesitarás [crear una GitHub App nueva](/apps/building-github-apps/).
|
||||
Once you've decided to make the switch to GitHub Apps, you'll need to [create a new GitHub App](/apps/building-github-apps/).
|
||||
|
||||
#### Determinar los permisos que necesitará tu app
|
||||
|
||||
@@ -62,7 +62,7 @@ En la configuración de tu GitHub App, puedes especificar si tu app necesita acc
|
||||
|
||||
#### Suscribirte a los webhooks
|
||||
|
||||
Después de que creaste una GitHub App nueva y seleccionaste sus permisos, puedes seleccionar los eventos de webhook a los cuales deseas suscribirte. Consulta la sección "[Editar los permisos de una GitHub App](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para aprender sobre cómo suscribirte a los webhooks.
|
||||
Después de que creaste una GitHub App nueva y seleccionaste sus permisos, puedes seleccionar los eventos de webhook a los cuales deseas suscribirte. See "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" to learn how to subscribe to webhooks.
|
||||
|
||||
#### Entender los diferentes métodos de autenticación
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ Esta solicitud de rellamada te enviará un token de acceso y un token de actuali
|
||||
{
|
||||
"access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a",
|
||||
"expires_in": "28800",
|
||||
"refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692",
|
||||
"refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e169246c34e1ccbf66c46812d16d5b1a9dc86a149873c",
|
||||
"refresh_token_expires_in": "15811200",
|
||||
"scope": "",
|
||||
"token_type": "bearer"
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user