Merge branch 'main' into patch-1
This commit is contained in:
Janice
@@ -56,26 +56,26 @@ Before you begin, you'll create a {% data variables.product.product_name %} repo
|
||||
{% raw %}
|
||||
**action.yml**
|
||||
```yaml
|
||||
Name: 'Hello World'
|
||||
Beschreibung: 'Greet someone'
|
||||
name: 'Hello World'
|
||||
description: 'Greet someone'
|
||||
inputs:
|
||||
who-to-greet: 'id of input
|
||||
who-to-greet: # id of input
|
||||
description: 'Who to greet'
|
||||
required: true
|
||||
default: 'World'
|
||||
outputs:
|
||||
zuzufällige Zahl:
|
||||
Beschreibung: "Zufallszahl"
|
||||
Wert:{{ steps.random-number-generator.outputs.random-id }}
|
||||
läuft:
|
||||
mit: "composite"
|
||||
Schritten:
|
||||
- laufen:{{ inputs.who-to-greet }}echo
|
||||
random-number:
|
||||
description: "Random number"
|
||||
value: ${{ steps.random-number-generator.outputs.random-id }}
|
||||
runs:
|
||||
using: "composite"
|
||||
steps:
|
||||
- run: echo Hello ${{ inputs.who-to-greet }}.
|
||||
shell: bash
|
||||
- id: random-number-generator
|
||||
run: echo "::set-output name=random-id::'(echo $RANDOM)"
|
||||
run: echo "::set-output name=random-id::$(echo $RANDOM)"
|
||||
shell: bash
|
||||
- run: '{{ github.action_path }}/goodbye.sh
|
||||
- run: ${{ github.action_path }}/goodbye.sh
|
||||
shell: bash
|
||||
```
|
||||
{% endraw %}
|
||||
@@ -109,20 +109,20 @@ Copy the workflow code into a `.github/workflows/main.yml` file in another repos
|
||||
{% raw %}
|
||||
**.github/workflows/main.yml**
|
||||
```yaml
|
||||
zu: [push]
|
||||
on: [push]
|
||||
|
||||
Jobs:
|
||||
jobs:
|
||||
hello_world_job:
|
||||
läuft auf: ubuntu-latest
|
||||
Name: Ein Job, um Hallo zu sagen
|
||||
Schritte:
|
||||
- verwendet: aktionen/checkout@v2
|
||||
runs-on: ubuntu-latest
|
||||
name: A job to say hello
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- id: foo
|
||||
verwendet: actions/hello-world-composite-run-steps-action@v1
|
||||
mit:
|
||||
uses: actions/hello-world-composite-run-steps-action@v1
|
||||
with:
|
||||
who-to-greet: 'Mona the Octocat'
|
||||
- run: echo random-{{ steps.foo.outputs.random-number }}
|
||||
number
|
||||
- run: echo random-number ${{ steps.foo.outputs.random-number }}
|
||||
shell: bash
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
@@ -117,6 +117,7 @@ läuft:
|
||||
{% endraw %}
|
||||
|
||||
#### `outputs.<output_id>.value`
|
||||
|
||||
**Erforderliche** Der Wert, dem der Ausgabeparameter zugeordnet wird. Sie können dies auf eine `Zeichenfolge` oder einen Ausdruck mit Kontext festlegen. Sie können z. B. die `Schritte` Kontext verwenden, um den `Wert` einer Ausgabe auf den Ausgabewert eines Schritts festzulegen.
|
||||
|
||||
For more information on how to use context and expression syntax, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
|
||||
@@ -204,9 +205,11 @@ In diesem Beispiel läuft `cleanup.js` nur auf Linux-basierten Runnern:
|
||||
|
||||
**Erforderliche** Die Ausführungsschritte, die Sie in dieser Aktion ausführen möchten.
|
||||
|
||||
##### `runs.steps.run`
|
||||
##### `runs.steps[*].run`
|
||||
|
||||
**Erforderliche** Der Befehl, den Sie ausführen möchten. Dies kann inline oder ein Skript in Ihrem Aktions-Repository sein:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
läuft:
|
||||
mit: "composite"
|
||||
@@ -214,8 +217,9 @@ läuft:
|
||||
- ausführen:{{ github.action_path }}/test/script.sh
|
||||
Shell: bash
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
Alternativ können Sie `$GITHUB_ACTION_PATH`verwenden:
|
||||
Alternatively, you can use `$GITHUB_ACTION_PATH`:
|
||||
|
||||
```yaml
|
||||
läuft:
|
||||
@@ -225,27 +229,27 @@ läuft:
|
||||
Shell: bash
|
||||
```
|
||||
|
||||
Weitere Informationen finden Sie unter "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
|
||||
For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
|
||||
|
||||
##### `runs.steps.shell`
|
||||
##### `runs.steps[*].shell`
|
||||
|
||||
**Erforderliche** Die Shell, in der Sie den Befehl ausführen möchten. Sie können eine der hier aufgeführten Shells [](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)verwenden.
|
||||
**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell).
|
||||
|
||||
##### `runs.steps.name`
|
||||
##### `runs.steps[*].name`
|
||||
|
||||
**Optionaler** Der Name des zusammengesetzten Ausführungsschritts.
|
||||
**Optional** The name of the composite run step.
|
||||
|
||||
##### `runs.steps.id`
|
||||
##### `runs.steps[*].id`
|
||||
|
||||
**Optionaler** Ein eindeutiger Bezeichner für den Schritt. Anhand der `id` können Sie in Kontexten auf den Schritt verweisen. Weitere Informationen findest Du unter "[Kontext- und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
|
||||
**Optional** A unique identifier for the step. Anhand der `id` können Sie in Kontexten auf den Schritt verweisen. Weitere Informationen findest Du unter "[Kontext- und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
|
||||
|
||||
##### `runs.steps.env`
|
||||
##### `runs.steps[*].env`
|
||||
|
||||
**Optionale** Legt eine `Zuordnung` von Umgebungsvariablen nur für diesen Schritt fest. If you want to modify the environment variable stored in the workflow, use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} in a composite run step.
|
||||
**Optional** Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} in a composite run step.
|
||||
|
||||
##### `runs.steps.working-directory`
|
||||
##### `runs.steps[*].working-directory`
|
||||
|
||||
**Optionale** Gibt das Arbeitsverzeichnis an, in dem der Befehl ausgeführt wird.
|
||||
**Optional** Specifies the working directory where the command is run.
|
||||
|
||||
### `runs` for Docker actions
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ Zum Erstellen und Testen des Codes ist ein Server erforderlich. Sie können Aktu
|
||||
|
||||
### Informationen zur kontinuierlichen Integration mit {% data variables.product.prodname_actions %}
|
||||
|
||||
CI mit {% data variables.product.prodname_actions %} bietet Workflows, die den Code in Ihrem Repository erstellen und Ihre Tests ausführen können. Workflows können auf {% data variables.product.prodname_dotcom %}gehosteten virtuellen Maschinen oder auf Computern ausgeführt werden, die Sie selbst hosten. Weitere Informationen finden Sie unter "[Virtuelle Umgebungen für {% data variables.product.prodname_dotcom %}gehostete Läufer](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)" und "[über selbst gehostete Läufer](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)".
|
||||
CI mit {% data variables.product.prodname_actions %} bietet Workflows, die den Code in Ihrem Repository erstellen und Ihre Tests ausführen können. Workflows können auf {% data variables.product.prodname_dotcom %}gehosteten virtuellen Maschinen oder auf Computern ausgeführt werden, die Sie selbst hosten. For more information, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
|
||||
|
||||
Sie können Ihren CI-Workflow so konfigurieren, dass er ausgeführt wird, wenn ein {% data variables.product.product_name %} Ereignis auftritt (z. B. wenn neuer Code an Ihr Repository übertragen wird), nach einem festgelegten Zeitplan oder wenn ein externes Ereignis mithilfe des Repository-Dispatch-Webhooks auftritt.
|
||||
|
||||
|
||||
@@ -193,9 +193,9 @@ steps:
|
||||
|
||||
{% data reusables.github-actions.setup-node-intro %}
|
||||
|
||||
Um Dich bei Deiner privaten Registry zu authentifizieren, musst Du in Deinen Repository-Einstellungen Dein npm-Authentifizierungs-Token als Geheimnis ablegen. Erstelle z.B. ein Geheimnis namens `NPM_TOKEN`. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
|
||||
To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
|
||||
|
||||
Im folgenden Beispiel enthält das Geheimnis `NPM_TOKEN` den npm-Authentifizierungs-Token. Die Aktion `setup-node` konfiguriert die Datei *.npmrc*, um den npm-Authentifizierung-Token aus der Umgebungsvariablen `NODE_AUTH_TOKEN` zu lesen. Wenn Du die Aktion `setup-node` verwendest, um eine Datei *.npmrc* zu erstellen, musst Du die Umgebungsvariable `NPM_AUTH_TOKEN` auf das Geheimnis setzen, das Deinen npm-Authentifizierungs-Token enthält.
|
||||
Im folgenden Beispiel enthält das Geheimnis `NPM_TOKEN` den npm-Authentifizierungs-Token. Die Aktion `setup-node` konfiguriert die Datei *.npmrc*, um den npm-Authentifizierung-Token aus der Umgebungsvariablen `NODE_AUTH_TOKEN` zu lesen. When using the `setup-node` action to create an *.npmrc* file, you must set the `NODE_AUTH_TOKEN` environment variable with the secret that contains your npm authentication token.
|
||||
|
||||
Bevor Du Abhängigkeiten installierst, verwende die Aktion `setup-node`, um die Datei *.npmrc* zu erstellen. Die Aktion hat zwei Eingabeparameter. Der Parameter `node-version` legt die Version von Node.js fest und der Parameter `registry-url` bestimmt die Standard-Registry. Wenn Deine Paket-Registry Geltungsbereiche verwendet, musst Du den Parameter `scope` verwenden. Weitere Informationen findest Du unter [`npm-scope`](https://docs.npmjs.com/misc/scope).
|
||||
|
||||
|
||||
@@ -214,7 +214,7 @@ The `always()` function configures the job to continue processing even if there
|
||||
|
||||
### Publishing to PowerShell Gallery
|
||||
|
||||
You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use repository secrets to store any tokens or credentials needed to publish your package. Weitere Informationen findest Du unter "[Verschlüsselte Geheimnisse erstellen und verwenden](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
|
||||
You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use secrets to store any tokens or credentials needed to publish your package. Weitere Informationen findest Du unter "[Verschlüsselte Geheimnisse erstellen und verwenden](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
|
||||
|
||||
The following example creates a package and uses `Publish-Module` to publish it to the PowerShell Gallery:
|
||||
|
||||
|
||||
@@ -391,7 +391,7 @@ jobs:
|
||||
|
||||
You can configure your workflow to publish your Python package to any package registry you'd like when your CI tests pass.
|
||||
|
||||
You can store any access tokens or credentials needed to publish your package using repository secrets. The following example creates and publishes a package to PyPI using `twine` and `dist`. Weitere Informationen findest Du unter "[Verschlüsselte Geheimnisse erstellen und verwenden](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
|
||||
You can store any access tokens or credentials needed to publish your package using secrets. The following example creates and publishes a package to PyPI using `twine` and `dist`. Weitere Informationen findest Du unter "[Verschlüsselte Geheimnisse erstellen und verwenden](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
@@ -0,0 +1,148 @@
|
||||
---
|
||||
title: Deploying to Amazon Elastic Container Service
|
||||
intro: You can deploy to Amazon Elastic Container Service (ECS) as part of your continuous deployment (CD) workflows.
|
||||
product: '{% data reusables.gated-features.actions %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
### Einführung
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/).
|
||||
|
||||
On every new release in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS.
|
||||
|
||||
### Vorrausetzungen
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps for Amazon ECR and ECS:
|
||||
|
||||
1. Create an Amazon ECR repository to store your images.
|
||||
|
||||
For example, using [the AWS CLI](https://aws.amazon.com/cli/):
|
||||
|
||||
{% raw %}```bash{:copy}
|
||||
aws ecr create-repository \ --repository-name MY_ECR_REPOSITORY \ --region MY_AWS_REGION
|
||||
```{% endraw %}
|
||||
|
||||
Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below.
|
||||
|
||||
Ensure that you use the same AWS region value for the `AWS_REGION` (represented here by `MY_AWS_REGION`) variable in the workflow below.
|
||||
|
||||
2. Create an Amazon ECS task definition, cluster, and service.
|
||||
|
||||
For details, follow the [Getting started wizard on the Amazon ECS console](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), or the [Getting started guide](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) in the Amazon ECS documentation.
|
||||
|
||||
Ensure that you note the names you set for the Amazon ECS service and cluster, and use them for the `ECS_SERVICE` and `ECS_CLUSTER` variables in the workflow below.
|
||||
|
||||
3. Store your Amazon ECS task definition as a JSON file in your {% data variables.product.company_short %} repository.
|
||||
|
||||
The format of the file should be the same as the output generated by:
|
||||
|
||||
{% raw %}```bash{:copy}
|
||||
aws ecs register-task-definition --generate-cli-skeleton
|
||||
```{% endraw %}
|
||||
|
||||
Ensure that you set the `ECS_TASK_DEFINITION` variable in the workflow below as the path to the JSON file.
|
||||
|
||||
Ensure that you set the `CONTAINER_NAME` variable in the workflow below as the container name in the `containerDefinitions` section of the task definition.
|
||||
|
||||
4. Create {% data variables.product.prodname_actions %} secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to store the values for your Amazon IAM access key.
|
||||
|
||||
For more information on creating secrets for {% data variables.product.prodname_actions %}, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
|
||||
|
||||
See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials.
|
||||
|
||||
### Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build a container image and push it to Amazon ECR. It then updates the task definition with the new image ID, and deploys the task definition to Amazon ECS.
|
||||
|
||||
Ensure that you provide your own values for all the variables in the `env` key of the workflow.
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
name: Deploy to Amazon ECS
|
||||
|
||||
on:
|
||||
release:
|
||||
types: [ created ]
|
||||
|
||||
env:
|
||||
AWS_REGION: MY_AWS_REGION # set this to your preferred AWS region, e.g. us-west-1
|
||||
ECR_REPOSITORY: MY_ECR_REPOSITORY # set this to your Amazon ECR repository name
|
||||
ECS_SERVICE: MY_ECS_SERVICE # set this to your Amazon ECS service name
|
||||
ECS_CLUSTER: MY_ECS_CLUSTER # set this to your Amazon ECS cluster name
|
||||
ECS_TASK_DEFINITION: MY_ECS_TASK_DEFINITION # set this to the path to your Amazon ECS task definition
|
||||
# file, e.g. .aws/task-definition.json
|
||||
CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the
|
||||
# containerDefinitions section of your task definition
|
||||
|
||||
defaults:
|
||||
run:
|
||||
shell: bash
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
name: Deploy
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v2
|
||||
|
||||
- name: Configure AWS credentials
|
||||
uses: aws-actions/configure-aws-credentials@v1
|
||||
with:
|
||||
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
|
||||
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
|
||||
aws-region: $AWS_REGION
|
||||
|
||||
- name: Login to Amazon ECR
|
||||
id: login-ecr
|
||||
uses: aws-actions/amazon-ecr-login@v1
|
||||
|
||||
- name: Build, tag, and push image to Amazon ECR
|
||||
id: build-image
|
||||
env:
|
||||
ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }}
|
||||
IMAGE_TAG: ${{ github.sha }}
|
||||
run: |
|
||||
# Build a docker container and
|
||||
# push it to ECR so that it can
|
||||
# be deployed to ECS.
|
||||
docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG .
|
||||
docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG
|
||||
echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" >> $GITHUB_ENV
|
||||
|
||||
- name: Fill in the new image ID in the Amazon ECS task definition
|
||||
id: task-def
|
||||
uses: aws-actions/amazon-ecs-render-task-definition@v1
|
||||
with:
|
||||
task-definition: $ECS_TASK_DEFINITION
|
||||
container-name: $CONTAINER_NAME
|
||||
image: ${{ steps.build-image.outputs.image }}
|
||||
|
||||
- name: Deploy Amazon ECS task definition
|
||||
uses: aws-actions/amazon-ecs-deploy-task-definition@v1
|
||||
with:
|
||||
task-definition: ${{ steps.task-def.outputs.task-definition }}
|
||||
service: $ECS_SERVICE
|
||||
cluster: $ECS_CLUSTER
|
||||
wait-for-service-stability: true
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Additional resources
|
||||
|
||||
For more information on the services used in these examples, see the following documentation:
|
||||
|
||||
* "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation.
|
||||
* Official AWS "[Configure AWS Credentials](https://github.com/aws-actions/configure-aws-credentials)" action.
|
||||
* Official AWS [Amazon ECR "Login"](https://github.com/aws-actions/amazon-ecr-login) action.
|
||||
* Official AWS [Amazon ECS "Render Task Definition"](https://github.com/aws-actions/amazon-ecs-render-task-definition) action.
|
||||
* Official AWS [Amazon ECS "Deploy Task Definition"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) action.
|
||||
@@ -0,0 +1,115 @@
|
||||
---
|
||||
title: Deploying to Azure App Service
|
||||
intro: You can deploy to Azure App Service as part of your continuous deployment (CD) workflows.
|
||||
product: '{% data reusables.gated-features.actions %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
### Einführung
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy an application to [Azure App Service](https://azure.microsoft.com/en-us/services/app-service/).
|
||||
|
||||
Azure App Service can run web apps in several languages, but this guide demonstrates deploying an existing Node.js project.
|
||||
|
||||
### Vorrausetzungen
|
||||
|
||||
Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
|
||||
|
||||
1. Create an Azure App Service plan.
|
||||
|
||||
For example, you can use the Azure CLI to create a new App Service plan:
|
||||
|
||||
```bash{:copy}
|
||||
az appservice plan create \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--name MY_APP_SERVICE_PLAN \
|
||||
--is-linux
|
||||
```
|
||||
|
||||
In the command above, replace `MY_RESOURCE_GROUP` with your pre-existing Azure Resource Group, and `MY_APP_SERVICE_PLAN` with a new name for the App Service plan.
|
||||
|
||||
See the Azure documentation for more information on using the [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/):
|
||||
|
||||
* For authentication, see "[Sign in with Azure CLI](https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli)".
|
||||
* If you need to create a new resource group, see "[az group](https://docs.microsoft.com/en-us/cli/azure/group?view=azure-cli-latest#az_group_create)."
|
||||
|
||||
2. Create a web app.
|
||||
|
||||
For example, you can use the Azure CLI to create an Azure App Service web app with a node runtime:
|
||||
|
||||
```bash{:copy}
|
||||
az webapp create \
|
||||
--name MY_WEBAPP_NAME \
|
||||
--plan MY_APP_SERVICE_PLAN \
|
||||
--resource-group MY_RESOURCE_GROUP \
|
||||
--runtime "node|10.14"
|
||||
```
|
||||
|
||||
In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
|
||||
|
||||
3. Configure an Azure publish profile and create an `AZURE_WEBAPP_PUBLISH_PROFILE` secret.
|
||||
|
||||
Generate your Azure deployment credentials using a publish profile. For more information, see "[Generate deployment credentials](https://docs.microsoft.com/en-us/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials)" in the Azure documentation.
|
||||
|
||||
In your {% data variables.product.prodname_dotcom %} repository, create a secret named `AZURE_WEBAPP_PUBLISH_PROFILE` that contains the contents of the publish profile. For more information on creating secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
|
||||
|
||||
### Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service.
|
||||
|
||||
Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created.
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
on:
|
||||
release:
|
||||
types: [created]
|
||||
|
||||
env:
|
||||
AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name
|
||||
AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root
|
||||
NODE_VERSION: '10.x' # set this to the node version to use
|
||||
|
||||
jobs:
|
||||
build-and-deploy:
|
||||
name: Build and Deploy
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
|
||||
- name: Use Node.js ${{ env.NODE_VERSION }}
|
||||
uses: actions/setup-node@v1
|
||||
with:
|
||||
node-version: ${{ env.NODE_VERSION }}
|
||||
|
||||
- name: npm install, build, and test
|
||||
run: |
|
||||
# Build and test the project, then
|
||||
# deploy to Azure Web App.
|
||||
npm install
|
||||
npm run build --if-present
|
||||
npm run test --if-present
|
||||
|
||||
- name: 'Deploy to Azure WebApp'
|
||||
uses: azure/webapps-deploy@v2
|
||||
with:
|
||||
app-name: ${{ env.AZURE_WEBAPP_NAME }}
|
||||
publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}
|
||||
package: ${{ env.AZURE_WEBAPP_PACKAGE_PATH }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Additional resources
|
||||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/master/ci/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
|
||||
* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/en-us/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
|
||||
@@ -0,0 +1,177 @@
|
||||
---
|
||||
title: Deploying to Google Kubernetes Engine
|
||||
intro: You can deploy to Google Kubernetes Engine as part of your continuous deployment (CD) workflows.
|
||||
product: '{% data reusables.gated-features.actions %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
### Einführung
|
||||
|
||||
This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE).
|
||||
|
||||
GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
|
||||
|
||||
### Vorrausetzungen
|
||||
|
||||
Before you proceed with creating the workflow, you will need to complete the following steps for your Kubernetes project. This guide assumes the root of your project already has a `Dockerfile` and a Kubernetes Deployment configuration file. For an example, see [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).
|
||||
|
||||
#### Creating a GKE cluster
|
||||
|
||||
To create the GKE cluster, you will first need to authenticate using the `gcloud` CLI. For more information on this step, see the following articles:
|
||||
- [`gcloud auth login`](https://cloud.google.com/sdk/gcloud/reference/auth/login)
|
||||
- [`gcloud` CLI](https://cloud.google.com/sdk/gcloud/reference)
|
||||
- [`gcloud` CLI and Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
|
||||
|
||||
Ein Beispiel:
|
||||
|
||||
{% raw %}
|
||||
```bash{:copy}
|
||||
$ gcloud container clusters create $GKE_CLUSTER \
|
||||
--project=$GKE_PROJECT \
|
||||
--zone=$GKE_ZONE
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### Enabling the APIs
|
||||
|
||||
Enable the Kubernetes Engine and Container Registry APIs. Ein Beispiel:
|
||||
|
||||
{% raw %}
|
||||
```bash{:copy}
|
||||
$ gcloud services enable \
|
||||
containerregistry.googleapis.com \
|
||||
container.googleapis.com
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### Configuring a service account and storing its credentials
|
||||
|
||||
This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded [encrypted repository secret](/actions/reference/encrypted-secrets) named `GKE_SA_KEY`.
|
||||
|
||||
1. Create a new service account:
|
||||
{% raw %}
|
||||
```
|
||||
$ gcloud iam service-accounts create $SA_NAME
|
||||
```
|
||||
{% endraw %}
|
||||
1. Retrieve the email address of the service account you just created:
|
||||
{% raw %}
|
||||
```
|
||||
$ gcloud iam service-accounts list
|
||||
```
|
||||
{% endraw %}
|
||||
1. Add roles to the service account. Note: Apply more restrictive roles to suit your requirements.
|
||||
{% raw %}
|
||||
```
|
||||
$ gcloud projects add-iam-policy-binding $GKE_PROJECT \
|
||||
--member=serviceAccount:$SA_EMAIL \
|
||||
--role=roles/container.admin \
|
||||
--role=roles/storage.admin
|
||||
```
|
||||
{% endraw %}
|
||||
1. Download the JSON keyfile for the service account:
|
||||
{% raw %}
|
||||
```
|
||||
$ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
|
||||
```
|
||||
{% endraw %}
|
||||
1. Store the project ID as a secret named `GKE_PROJECT`:
|
||||
{% raw %}
|
||||
```
|
||||
$ export GKE_SA_KEY=$(cat key.json | base64)
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### (Optional) Configuring kustomize
|
||||
Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage).
|
||||
|
||||
### Creating the workflow
|
||||
|
||||
Once you've completed the prerequisites, you can proceed with creating the workflow.
|
||||
|
||||
The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment.
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
name: Build and Deploy to GKE
|
||||
|
||||
on:
|
||||
release:
|
||||
types: [created]
|
||||
|
||||
env:
|
||||
PROJECT_ID: ${{ secrets.GKE_PROJECT }}
|
||||
GKE_CLUSTER: cluster-1 # Add your cluster name here.
|
||||
GKE_ZONE: us-central1-c # Add your cluster zone here.
|
||||
DEPLOYMENT_NAME: gke-test # Add your deployment name here.
|
||||
IMAGE: static-site
|
||||
|
||||
jobs:
|
||||
setup-build-publish-deploy:
|
||||
name: Setup, Build, Publish, and Deploy
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v2
|
||||
|
||||
# Setup gcloud CLI
|
||||
- uses: google-github-actions/setup-gcloud@v0.2.0
|
||||
with:
|
||||
service_account_key: ${{ secrets.GKE_SA_KEY }}
|
||||
project_id: ${{ secrets.GKE_PROJECT }}
|
||||
|
||||
# Configure docker to use the gcloud command-line tool as a credential helper
|
||||
- run: |-
|
||||
gcloud --quiet auth configure-docker
|
||||
|
||||
# Get the GKE credentials so we can deploy to the cluster
|
||||
- uses: google-github-actions/get-gke-credentials@v0.2.1
|
||||
with:
|
||||
cluster_name: ${{ env.GKE_CLUSTER }}
|
||||
location: ${{ env.GKE_ZONE }}
|
||||
credentials: ${{ secrets.GKE_SA_KEY }}
|
||||
|
||||
# Build the Docker image
|
||||
- name: Build
|
||||
run: |-
|
||||
docker build \
|
||||
--tag "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" \
|
||||
--build-arg GITHUB_SHA="$GITHUB_SHA" \
|
||||
--build-arg GITHUB_REF="$GITHUB_REF" \
|
||||
.
|
||||
|
||||
# Push the Docker image to Google Container Registry
|
||||
- name: Publish
|
||||
run: |-
|
||||
docker push "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA"
|
||||
|
||||
# Set up kustomize
|
||||
- name: Set up Kustomize
|
||||
run: |-
|
||||
curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64
|
||||
chmod u+x ./kustomize
|
||||
|
||||
# Deploy the Docker image to the GKE cluster
|
||||
- name: Deploy
|
||||
run: |-
|
||||
./kustomize edit set image gcr.io/PROJECT_ID/IMAGE:TAG=gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA
|
||||
./kustomize build . | kubectl apply -f -
|
||||
kubectl rollout status deployment/$DEPLOYMENT_NAME
|
||||
kubectl get services -o wide
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Additional resources
|
||||
|
||||
For more information on the tools used in these examples, see the following documentation:
|
||||
|
||||
* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/master/ci/google.yml).
|
||||
* For more starter workflows and accompanying code, see Google's [{% data variables.product.prodname_actions %} example workflows](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/).
|
||||
* The Kubernetes YAML customization engine: [Kustomize](https://kustomize.io/).
|
||||
* "[Deploying a containerized web application](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" in the Google Kubernetes Engine documentation.
|
||||
@@ -36,6 +36,14 @@ You can use {% data variables.product.prodname_actions %} to create custom conti
|
||||
{% link_in_list /building-and-testing-java-with-gradle %}
|
||||
{% link_in_list /building-and-testing-java-with-ant %}
|
||||
|
||||
### Creating custom continuous deployment workflows
|
||||
|
||||
You can use {% data variables.product.prodname_actions %} to create custom continuous deployment (CD) workflows that deploy projects to a number of cloud partner ecosystems.
|
||||
|
||||
{% link_in_list /deploying-to-amazon-elastic-container-service %}
|
||||
{% link_in_list /deploying-to-azure-app-service %}
|
||||
{% link_in_list /deploying-to-google-kubernetes-engine %}
|
||||
|
||||
### Publishing software packages
|
||||
|
||||
You can automate publishing software packages as part your continuous delivery (CD) workflow. Packages can be published to any package host and to {% data reusables.gated-features.packages %}.
|
||||
|
||||
@@ -46,11 +46,11 @@ In dieser Anleitung wir werden die Docker-Aktion `build-push-action` verwenden,
|
||||
|
||||
Im folgenden Beispiel-Workflow verwenden wir die Docker-Aktion `build-push-action`, um das Docker-Image zu bauen und, wenn der Build erfolgreich ist, das gebaute Image auf „Docker Hub“ zu übertragen.
|
||||
|
||||
Um zum „Docker Hub“ zu pushen, benötigst Du ein Benutzerkonto auf „Docker Hub“ und musst ein „Docker Hub“-Repository erstellt haben. Weitere Informationen findest Du unter „[Images auf ‚Docker Hub‘ freigeben](https://docs.docker.com/get-started/part3/)“ in der Docker-Dokumentation.
|
||||
Um zum „Docker Hub“ zu pushen, benötigst Du ein Benutzerkonto auf „Docker Hub“ und musst ein „Docker Hub“-Repository erstellt haben. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
|
||||
|
||||
„Docker Hub“ benötigt für `build-push-action` die folgenden Optionen:
|
||||
|
||||
* `username` und `password`: Dies ist Dein Benutzername und Passwort auf „Docker Hub“. We recommend storing your Docker Hub username and password as encrypted secrets in your {% data variables.product.prodname_dotcom %} repository so they aren't exposed in your workflow file. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
|
||||
* `username` und `password`: Dies ist Dein Benutzername und Passwort auf „Docker Hub“. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
|
||||
* `repository`: Dein „Docker Hub“-Repository im Format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY`.
|
||||
|
||||
{% raw %}
|
||||
|
||||
@@ -44,7 +44,7 @@ Wenn Du Schritte in Deinen Workflow einfügst, um die `publishConfig`-Felder in
|
||||
|
||||
Jedes Mal, wenn Du ein neues Release erstellst, kannst Du einen Workflow anstoßen, um Dein Paket zu veröffentlichen. Der Workflow im folgenden Beispiel wird von dem Ereignis `release` vom Typ `created` angestoßen. Der Workflow veröffentlicht das Paket im npm-Registry sofern es die CI-Tests besteht.
|
||||
|
||||
Um in Deinem Workflow authentifizierte Operationen gegenüber der npm-Registry durchzuführen, musst Du Dein npm-Authentifizierungstoken als Geheimnis in Deinen Repository-Einstellungen ablegen. Erstelle z.B. ein Geheimnis namens `NPM_TOKEN`. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
|
||||
To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und verwenden](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)“.
|
||||
|
||||
Standardmäßig verwendet npm das Feld `name` der Datei *package.json*, um die npm-Registry zu ermitteln. Wenn Du in einem globalen Namespace veröffentlichst, brauchst Du nur den Paketnamen anzugeben. Zum Beispiel würdest Du ein Paket namens `npm-hello-world-test` auf `https://www.npmjs.com/package/npm-hello-world-test` veröffentlichen.
|
||||
|
||||
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
defaultPlatform: linux
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -8,6 +8,7 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
defaultPlatform: linux
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -25,6 +25,10 @@ featuredLinks:
|
||||
- /actions/reference/workflow-commands-for-github-actions
|
||||
- /actions/reference/environment-variables
|
||||
changelog:
|
||||
-
|
||||
title: Workflow visualization
|
||||
date: '2020-12-08'
|
||||
href: https://github.blog/changelog/2020-12-08-github-actions-workflow-visualization/
|
||||
-
|
||||
title: Removing set-env and add-path commands on November 16
|
||||
date: '2020-11-09'
|
||||
@@ -33,14 +37,6 @@ changelog:
|
||||
title: Ubuntu-latest workflows will use Ubuntu-20.04
|
||||
date: '2020-10-29'
|
||||
href: https://github.blog/changelog/2020-10-29-github-actions-ubuntu-latest-workflows-will-use-ubuntu-20-04
|
||||
-
|
||||
title: MacOS Big Sur Preview
|
||||
date: '2020-10-29'
|
||||
href: https://github.blog/changelog/2020-10-29-github-actions-macos-big-sur-preview
|
||||
-
|
||||
title: Self-Hosted Runner Group Access Changes
|
||||
date: '2020-10-16'
|
||||
href: https://github.blog/changelog/2020-10-16-github-actions-self-hosted-runner-group-access-changes/
|
||||
product_video: https://www.youtube-nocookie.com/embed/cP0I9w2coGU
|
||||
redirect_from:
|
||||
- /articles/automating-your-workflow-with-github-actions/
|
||||
|
||||
@@ -76,7 +76,7 @@ Schritte:
|
||||
|
||||
#### Using branches
|
||||
|
||||
Referring to a specific branch means that the action will always use include the latest updates on the target branch, but can create problems if those updates include breaking changes. This example targets a branch named `@main`:
|
||||
Referring to a specific branch means that the action will always use the latest updates on the target branch, but can create problems if those updates include breaking changes. This example targets a branch named `@main`:
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Managing complex workflows
|
||||
shortTitle: Managing complex workflows
|
||||
intro: 'This guide shows you how to use the advanced features of {% data variables.product.prodname_actions %}, with secret management, dependent jobs, caching, build matrices, and labels.'
|
||||
intro: 'This guide shows you how to use the advanced features of {% data variables.product.prodname_actions %}, with secret management, dependent jobs, caching, build matrices,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} environments,{% endif %} and labels.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
@@ -148,6 +148,12 @@ jobs:
|
||||
|
||||
For more information, see ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
### Using environments
|
||||
|
||||
You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)."
|
||||
{% endif %}
|
||||
|
||||
### Nächste Schritte:
|
||||
|
||||
To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)."
|
||||
|
||||
@@ -57,7 +57,7 @@ Jenkins verwendet Anweisungen um _Deklarative Pipelines_ zu verwalten. Diese Anw
|
||||
|
||||
| Anweisungen in Jenkins | {% data variables.product.prodname_actions %}
|
||||
| ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment) | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
|
||||
| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment) | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
|
||||
| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) |
|
||||
| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters) | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs) |
|
||||
| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\|pull_request>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths) |
|
||||
|
||||
@@ -175,7 +175,7 @@ When migrating from Travis CI, consider the following key features in {% data va
|
||||
|
||||
#### Storing secrets
|
||||
|
||||
{% data variables.product.prodname_actions %} allows you to store secrets and reference them in your jobs. {% data variables.product.prodname_actions %} also includes policies that allow you to limit access to secrets at the repository and organization level. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
|
||||
{% data variables.product.prodname_actions %} allows you to store secrets and reference them in your jobs. {% data variables.product.prodname_actions %} organizations can limit which repositories can access organization secrets. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}Environment protection rules can require manual approval for a workflow to access environment secrets. {% endif %}For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
|
||||
|
||||
#### Sharing files between jobs and workflows
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ This guide explains how to configure security hardening for certain {% data vari
|
||||
|
||||
### Using secrets
|
||||
|
||||
Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization or repository level, and allow you to store sensitive information in {% data variables.product.product_name %}.
|
||||
Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environment{% else %} or repository{% endif %} level, and allow you to store sensitive information in {% data variables.product.product_name %}.
|
||||
|
||||
Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps the minimize risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime.
|
||||
|
||||
@@ -38,6 +38,10 @@ To help prevent accidental disclosure, {% data variables.product.product_name %}
|
||||
- **Audit and rotate registered secrets**
|
||||
- Periodically review the registered secrets to confirm they are still required. Remove those that are no longer needed.
|
||||
- Rotate secrets periodically to reduce the window of time during which a compromised secret is valid.
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
- **Consider requiring review for access to secrets**
|
||||
- You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)."
|
||||
{% endif %}
|
||||
|
||||
### Using third-party actions
|
||||
|
||||
@@ -66,13 +70,13 @@ This means that a compromise of a single action within a workflow can be very si
|
||||
|
||||
### Considering cross-repository access
|
||||
|
||||
{% data variables.product.product_name %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` used in the workflow environment grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so having the `GITHUB_TOKEN` for one repository grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to the workflow environment, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators.
|
||||
{% data variables.product.product_name %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying workflow files. Users have specific permissions for each repository, so having the `GITHUB_TOKEN` for one repository grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators.
|
||||
|
||||
We have [a plan on the {% data variables.product.prodname_dotcom %} roadmap](https://github.com/github/roadmap/issues/74) to support a flow that allows cross-repository access within {% data variables.product.product_name %}, but this is not yet a supported feature. Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow environment. Because many authentication token types do not allow for granular access to specific resources, there is significant risk in using the wrong token type, as it can grant much broader access than intended.
|
||||
We have [a plan on the {% data variables.product.prodname_dotcom %} roadmap](https://github.com/github/roadmap/issues/74) to support a flow that allows cross-repository access within {% data variables.product.product_name %}, but this is not yet a supported feature. Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow. Because many authentication token types do not allow for granular access to specific resources, there is significant risk in using the wrong token type, as it can grant much broader access than intended.
|
||||
|
||||
This list describes the recommended approaches for accessing repository data within a workflow, in descending order of preference:
|
||||
|
||||
1. **The `GITHUB_TOKEN` in the workflow environment**
|
||||
1. **The `GITHUB_TOKEN`**
|
||||
- This token is intentionally scoped to the single repository that invoked the workflow, and has the same level of access as a write-access user on the repository. The token is created before each job begins and expires when the job is finished. Weitere Informationen findest Du unter „[Authentifizierung mit dem GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
|
||||
- The `GITHUB_TOKEN` should be used whenever possible.
|
||||
2. **Repository deploy key**
|
||||
|
||||
@@ -13,6 +13,9 @@ versions:
|
||||
Diese zusätzlichen Protokolle werden aktiviert, indem Geheimnisse im Repository, die den Workflow enthalten, gesetzt werden, sodass die gleichen Berechtigungsanforderungen gelten:
|
||||
|
||||
- {% data reusables.github-actions.permissions-statement-secrets-repository %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
- {% data reusables.github-actions.permissions-statement-secrets-environment %}
|
||||
{% endif %}
|
||||
- {% data reusables.github-actions.permissions-statement-secrets-organization %}
|
||||
- {% data reusables.github-actions.permissions-statement-secrets-api %}
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Managing workflow runs
|
||||
shortTitle: Managing workflow runs
|
||||
intro: 'Sie können den Status und die Ergebnisse der einzelnen Schritte in Ihrem Workflow anzeigen, einen ausstehenden Workflow abbrechen, fakturierbare Auftragsausführungsminuten anzeigen, einen fehlgeschlagenen Workflow debuggen und erneut ausführen, Protokolle suchen und herunterladen und Artefakte herunterladen.'
|
||||
intro: 'You can view the status and results of each step in your workflow, cancel a pending workflow, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}review deployments, {% endif %}view billable job execution minutes, debug and re-run a failed workflow, search and download logs, and download artifacts.'
|
||||
redirect_from:
|
||||
- /actions/configuring-and-managing-workflows/managing-a-workflow-run
|
||||
- /articles/viewing-your-repository-s-workflows
|
||||
@@ -24,6 +24,7 @@ versions:
|
||||
{% link_in_list /manually-running-a-workflow %}
|
||||
{% link_in_list /re-running-a-workflow %}
|
||||
{% link_in_list /canceling-a-workflow %}
|
||||
{% link_in_list /reviewing-deployments %}
|
||||
{% link_in_list /disabling-and-enabling-a-workflow %}
|
||||
{% link_in_list /deleting-a-workflow-run %}
|
||||
{% link_in_list /viewing-job-execution-time %}
|
||||
|
||||
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: Reviewing deployments
|
||||
intro: You can approve or reject jobs awaiting review.
|
||||
product: '{% data reusables.gated-features.environments %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.1'
|
||||
---
|
||||
|
||||
{% data reusables.actions.environments-beta %}
|
||||
|
||||
### About required reviews in workflows
|
||||
|
||||
Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled.
|
||||
|
||||
For more information about environments and required approvals, see "[Environments](/actions/reference/environments)."
|
||||
|
||||
### Approving or rejecting a job
|
||||
|
||||
1. Navigate to the workflow run that requires review. For more information about navigating to a workflow run, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
|
||||
2. Click **Review deployments**. 
|
||||
3. Select the job environment(s) to approve or reject. Optionally, leave a comment. 
|
||||
4. Approve or reject:
|
||||
- To approve the job, click **Approve and deploy**. Once a job is approved (and any other environment protection rules have passed), the job will proceed. At this point, the job can access any secrets stored in the environment.
|
||||
- To reject the job, click **Reject**. If a job is rejected, the workflow will fail.
|
||||
@@ -14,11 +14,9 @@ versions:
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
Jeder mit `write`(schreiben)-Zugriff auf ein Repository kann Geheimnisse erstellen, lesen und verwenden.
|
||||
|
||||
### Informationen zum `GITHUB_TOKEN`-Geheimnis
|
||||
|
||||
{% data variables.product.prodname_dotcom %} erstellt automatisch ein `GITHUB_TOKEN`-Geheimnis für den Workflow. Du kannst den `GITHUB_TOKEN` verwenden, um Dich in einem Workflow zu authentifizieren.
|
||||
{% data variables.product.prodname_dotcom %} erstellt automatisch ein `GITHUB_TOKEN`-Geheimnis für Deinen Workflow. Du kannst den `GITHUB_TOKEN` verwenden, um Dich in einem Workflow zu authentifizieren.
|
||||
|
||||
Wenn Du {% data variables.product.prodname_actions %} aktivierst, installiert {% data variables.product.prodname_dotcom %} eine {% data variables.product.prodname_github_app %} in Deinem Repository. Das `GITHUB_TOKEN`-Geheimnis ist ein {% data variables.product.prodname_github_app %}-Token für Installations-Zugriff. Du kannst das Installationszugriffs-Token verwenden, um Dich im Namen der auf Deinem Repository installierten {% data variables.product.prodname_github_app %} zu authentifizieren. Die Berechtigungen des Tokens sind auf das Repository beschränkt, in dem sich der Workflow befindet. Weitere Informationen findest Du unter "[Berechtigungen für das `GITHUB_TOKEN`](#permissions-for-the-github_token)."
|
||||
|
||||
@@ -28,7 +26,7 @@ Das Token ist auch im `github.token`-Kontext verfügbar. Weitere Informationen f
|
||||
|
||||
### Das `GITHUB_TOKEN` in einem Workflow verwenden
|
||||
|
||||
Um das `GITHUB_TOKEN`-Geheimnis zu verwenden, musst Du es in Deiner Workflow-Datei referenzieren. Hierbei musst Du das Token ggf. als Eingabe für eine Aktion übergeben, für die dieses Token erforderlich ist, oder authentifizierte Aufrufe der {% data variables.product.prodname_dotcom %}-API ausführen.
|
||||
Um das `GITHUB_TOKEN`-Geheimnis zu verwenden, musst Du es in Deiner Workflow-Datei referenzieren. Hierbei müssen Sie das Token ggf. als Eingabe für eine Aktion übergeben, für die dieses Token erforderlich ist, oder authentifizierte {% data variables.product.prodname_dotcom %}-API-Aufrufe ausführen.
|
||||
|
||||
{% data reusables.github-actions.actions-do-not-trigger-workflows %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Encrypted secrets
|
||||
intro: Verschlüsselte Geheimnisse ermöglichen es Ihnen, vertrauliche Informationen in Ihrem Repository oder Ihrer Organisation zu speichern.
|
||||
intro: Encrypted secrets allow you to store sensitive information in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or repository environments{% else %} or repository{% endif %}.
|
||||
product: '{% data reusables.gated-features.actions %}'
|
||||
redirect_from:
|
||||
- /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
|
||||
@@ -12,14 +12,19 @@ versions:
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.environments-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
### Informationen zu verschlüsselten Geheimnissen
|
||||
|
||||
Geheimnisse sind verschlüsselte Umgebungsvariablen, die Sie in einem Repository oder einer Organisation erstellen. The secrets you create are available to use in {% data variables.product.prodname_actions %} workflows. {% data variables.product.prodname_dotcom %} verwendet eine [versiegelte Libsodium-Box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) um sicherzustellen, dass Geheimnisse verschlüsselt werden, bevor sie {% data variables.product.prodname_dotcom %} erreichen, und verschlüsselt bleiben, bis Du sie in einem Workflow verwendest.
|
||||
Secrets are encrypted environment variables that you create in an organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or repository environment{% else %} or repository{% endif %}. The secrets that you create are available to use in {% data variables.product.prodname_actions %} workflows. {% data variables.product.prodname_dotcom %} uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to help ensure that secrets are encrypted before they reach {% data variables.product.prodname_dotcom %} and remain encrypted until you use them in a workflow.
|
||||
|
||||
{% data reusables.github-actions.secrets-org-level-overview %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
For secrets stored at the environment level, you can enable required reviewers to control access to the secrets. A workflow job cannot access environment secrets until approval is granted by required approvers.
|
||||
{% endif %}
|
||||
|
||||
#### Benennen Ihrer Geheimnisse
|
||||
|
||||
Die folgenden Regeln gelten für geheime Namen:
|
||||
@@ -27,13 +32,16 @@ Die folgenden Regeln gelten für geheime Namen:
|
||||
* Geheime Namen dürfen nur alphanumerische Zeichen (`[a-z]`, `[A-Z]`, `[0-9]`) oder Unterstriche (`_`) enthalten. Leerzeichen sind nicht zulässig.
|
||||
* Geheime Namen dürfen nicht mit dem `GITHUB_` -Präfix beginnen.
|
||||
* Geheime Namen dürfen nicht mit einer Zahl beginnen.
|
||||
* Geheime Namen müssen auf der Ebene eindeutig sein, auf der sie erstellt werden. Beispielsweise muss ein geheimer Schlüssel, der auf Organisationsebene erstellt wird, einen eindeutigen Namen auf dieser Ebene haben, und ein geheimer Schlüssel, der auf Repository-Ebene erstellt wird, muss einen eindeutigen Namen in diesem Repository haben. Wenn ein Geheimschlüssel auf Organisationsebene denselben Namen wie ein Geheimschlüssel auf Repository-Ebene hat, hat der geheime Schlüssel auf Repository-Ebene Vorrang.
|
||||
* Secret names are not case-sensitive.
|
||||
* Geheime Namen müssen auf der Ebene eindeutig sein, auf der sie erstellt werden. For example, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}a secret created at the environment level must have a unique name in that environment, {% endif %}a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
|
||||
|
||||
If a secret with the same name exists at multiple levels, the secret at the lower level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.{% endif %}
|
||||
|
||||
To help ensure that {% data variables.product.prodname_dotcom %} redacts your secret in logs, avoid using structured data as the values of secrets. Vermeide beispielsweise Geheimnisse zu erstellen, die JSON oder codierte Git-Blobs enthalten.
|
||||
|
||||
#### Zugriff auf Ihre Geheimnisse
|
||||
|
||||
Um ein Geheimnis für eine Aktion verfügbar zu machen, legen Sie das Geheimnis als Eingabe oder Umgebungsvariable in der Workflow-Datei fest. In der README-Datei der Aktion erfahren Sie, welche Eingaben und Umgebungsvariablen die Aktion erwartet. Weitere Informationen finden Sie unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)“.
|
||||
Um ein Geheimnis für eine Aktion verfügbar zu machen, legen Sie das Geheimnis als Eingabe oder Umgebungsvariable in der Workflow-Datei fest. In der README-Datei der Aktion erfahren Sie, welche Eingaben und Umgebungsvariablen die Aktion erwartet. Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)“.
|
||||
|
||||
Du kannst verschlüsselte Geheimnisse in einer Workflow-Datei verwenden und lesen, wenn Du auf die Datei Bearbeitungs-Zugriff hast. Weitere Informationen findest Du unter „[Zugriffsberechtigungen auf {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)“.
|
||||
|
||||
@@ -43,6 +51,10 @@ Du kannst verschlüsselte Geheimnisse in einer Workflow-Datei verwenden und lese
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
|
||||
{% endif %}
|
||||
|
||||
Sie können Geheimnisse auch mit der REST-API verwalten. For more information, see "[Secrets](/rest/reference/actions#secrets)."
|
||||
|
||||
#### Einschränken von Anmeldeinformationsberechtigungen
|
||||
@@ -56,12 +68,27 @@ Beim Generieren von Anmeldeinformationen wird empfohlen, möglichst geringe Bere
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.github-actions.sidebar-secret %}
|
||||
1. Klicken Sie auf **Add a new secret** (Neues Geheimnis hinzufügen).
|
||||
1. Click **New repository secret**.
|
||||
1. Geben Sie einen Namen für Ihr Geheimnis in das Eingabefeld **Name** ein.
|
||||
1. Geben Sie den Wert für Ihr Geheimnis ein.
|
||||
1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen).
|
||||
|
||||
Wenn Ihr Repository auf Geheimnisse der übergeordneten Organisation zugreifen kann, werden diese Geheimnisse auch auf dieser Seite aufgeführt.
|
||||
If your repository {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}has environment secrets or {% endif %}can access secrets from the parent organization, then those secrets are also listed on this page.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
### Creating encrypted secrets for an environment
|
||||
|
||||
{% data reusables.github-actions.permissions-statement-secrets-environment %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.github-actions.sidebar-environment %}
|
||||
1. Click on the environment that you want to add a secret to.
|
||||
1. Under **Environment secrets**, click **Add secret**.
|
||||
1. Geben Sie einen Namen für Ihr Geheimnis in das Eingabefeld **Name** ein.
|
||||
1. Geben Sie den Wert für Ihr Geheimnis ein.
|
||||
1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen).
|
||||
{% endif %}
|
||||
|
||||
### Erstellen verschlüsselter Geheimnisse für eine Organisation
|
||||
|
||||
@@ -72,7 +99,7 @@ Beim Erstellen eines geheimen Schlüssels in einer Organisation können Sie eine
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.github-actions.sidebar-secret %}
|
||||
1. Klicken Sie auf **Neue geheime**.
|
||||
1. Click **New organization secret**.
|
||||
1. Geben Sie einen Namen für Ihr Geheimnis in das Eingabefeld **Name** ein.
|
||||
1. Geben Sie den **Value** für Ihr Geheimnis ein.
|
||||
1. Wählen Sie im **Repository-Zugriff** Dropdownliste eine Zugriffsrichtlinie aus.
|
||||
@@ -90,7 +117,7 @@ Sie können überprüfen, welche Zugriffsrichtlinien auf einen geheimen Schlüss
|
||||
|
||||
### Verschlüsselte Geheimnisse in einem Workflow verwenden
|
||||
|
||||
Mit Ausnahme von `GITHUB_TOKEN` werden Geheimnisse nicht an den Runner übergeben, wenn ein Workflow von einem geforkten Repository aus ausgelöst wird.
|
||||
{% data reusables.actions.forked-secrets %}
|
||||
|
||||
Um eine Aktion mit einem Geheimnis als Eingabe- oder Umgebungsvariable zu versehen, kannst Du den `secrets` Kontext verwenden, um auf Geheimnisse zuzugreifen, die Du in Deinem Repository erstellt hast. Weitere Informationen findest Du unter "[Kontext und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)" und "[Workflow-Syntax für {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
|
||||
|
||||
@@ -150,13 +177,13 @@ steps:
|
||||
|
||||
### Einschränkungen für Geheimnisse
|
||||
|
||||
Dein Workflow kann bis zu 100 Geheimnisse haben. Die Namen von Geheimnis-Umgebungsvariablen müssen Repository-weit eindeutig sein.
|
||||
You can store up to 1,000 secrets per organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, 100 secrets per repository, and 100 secrets per environment{% else %} and 100 secrets per repository{% endif %}. A workflow may use up to 100 organization secrets and 100 repository secrets.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} Additionally, a job referencing an environment may use up to 100 environment secrets.{% endif %}
|
||||
|
||||
Geheimnisse sind auf 64 KB beschränkt. Um Geheimnisse zu verwenden, die größer als 64 KB sind, können Sie verschlüsselte Geheimnisse in Ihrem Repository speichern und die Passphrase zur Entschlüsselung als Geheimnis auf {% data variables.product.prodname_dotcom %} speichern. Sie können beispielsweise `gpg` verwenden, um Ihre Anmeldeinformationen lokal zu verschlüsseln, bevor Sie die Datei in Ihrem Repository auf {% data variables.product.prodname_dotcom %} einchecken. Weitere Informationen finden Sie auf der „[gpg-Manpage](https://www.gnupg.org/gph/de/manual/r1023.html)“.
|
||||
Geheimnisse sind auf 64 KB beschränkt. Um Geheimnisse zu verwenden, die größer als 64 KB sind, kannst Du verschlüsselte Geheimnisse in Deinem Repository speichern und die Passphrase zur Entschlüsselung als Geheimnis auf {% data variables.product.prodname_dotcom %} speichern. Du kannst beispielsweise `gpg` verwenden, um Deine Anmeldeinformationen lokal zu verschlüsseln, bevor Du die Datei in Ihrem Repository auf {% data variables.product.prodname_dotcom %} eincheckst. Weitere Informationen finden Sie auf der „[gpg-Manpage](https://www.gnupg.org/gph/de/manual/r1023.html)“.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warnung**: Achte darauf, dass Deine Geheimnisse nicht gedruckt werden, wenn Deine Aktion ausgeführt wird. Wenn Sie diesen Workaround verwenden, redigiert {% data variables.product.prodname_dotcom %} keine Geheimnisse, die in Protokollen gedruckt werden.
|
||||
**Warnung**: Achte darauf, dass Deine Geheimnisse nicht gedruckt werden, wenn Deine Aktion ausgeführt wird. Wenn Du diesen Workaround verwendest, redigiert {% data variables.product.prodname_dotcom %} keine Geheimnisse, die in Protokollen gedruckt werden.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ versions:
|
||||
|
||||
{% data variables.product.prodname_dotcom %} setzt Standard-Umgebungsvariablen, die für jeden Schritt in einem Workflow-Lauf verfügbar sind. Bei Umgebungsvariablen wird die Groß-/Kleinschreibung berücksichtigt. Befehle, die in Aktionen oder „Steps“ (Schritten) ausgeführt werden, können Umgebungsvariablen erstellen, lesen und ändern.
|
||||
|
||||
Um benutzerdefinierte Umgebungsvariablen festzulegen, musst Du die Variablen in der Workflow-Datei angeben. Du kannst Umgebungsvariablen für einen „Step“ (Schritt), Job, oder ganzen Workflow festlegen, indem Du die Schlüsselworte [`jobs.<job_id>.steps.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv) oder [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) verwendest. Weitere Informationen finden Sie unter „[Workflow-Syntax für {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)“.
|
||||
Um benutzerdefinierte Umgebungsvariablen festzulegen, musst Du die Variablen in der Workflow-Datei angeben. You can define environment variables for a step, job, or entire workflow using the [`jobs.<job_id>.steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), and [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) keywords. Weitere Informationen finden Sie unter „[Workflow-Syntax für {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)“.
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
@@ -51,8 +51,8 @@ Es wird dringend empfohlen, dass Aktionen Umgebungsvariablen verwenden, um auf d
|
||||
| `GITHUB_WORKSPACE` | Pfad zum Verzeichnis der Arbeitsoberfläche von {% data variables.product.prodname_dotcom %}. The workspace directory is a copy of your repository if your workflow uses the [actions/checkout](https://github.com/actions/checkout) action. Wenn Du die Aktion `actions/checkout` nicht verwendest, ist das Verzeichnis leer. Beispiel: `/home/runner/work/my-repo-name/my-repo-name`. |
|
||||
| `GITHUB_SHA` | Commit-SHA, die den Workflow ausgelöst hat. Beispiel: `ffac537e6cbbf934b08745a378932722df287a53`. |
|
||||
| `GITHUB_REF` | Branch- oder Tag-Ref, das den Workflow ausgelöst hat. Beispiel: `refs/heads/feature-branch-1`. Wenn für den Ereignistyp weder ein Branch noch ein Tag vorliegt, ist die Variable nicht vorhanden. |
|
||||
| `GITHUB_HEAD_REF` | Nur für geforkte Repositorys festgelegt. Der Branch des Head-Repositorys. |
|
||||
| `GITHUB_BASE_REF` | Nur für geforkte Repositorys festgelegt. Der Branch des Basis-Repositorys. |
|
||||
| `GITHUB_HEAD_REF` | Only set for pull request events. The name of the head branch. |
|
||||
| `GITHUB_BASE_REF` | Only set for pull request events. The name of the base branch. |
|
||||
| `GITHUB_SERVER_URL` | Returns the URL of the {% data variables.product.product_name %} server. For example: `https://github.com`. |
|
||||
| `GITHUB_API_URL` | Gibt die API-URL zurück. For example: `https://api.github.com`. |
|
||||
| `GITHUB_GRAPHQL_URL` | Gibt die GraphQL-API-URL zurück. For example: `https://api.github.com/graphql`. |
|
||||
|
||||
69
translations/de-DE/content/actions/reference/environments.md
Normal file
69
translations/de-DE/content/actions/reference/environments.md
Normal file
@@ -0,0 +1,69 @@
|
||||
---
|
||||
title: Environments
|
||||
intro: You can configure environments with protection rules and secrets. A workflow job can reference an environment to use the environment's protection rules and secrets.
|
||||
product: '{% data reusables.gated-features.environments %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.1'
|
||||
---
|
||||
|
||||
{% data reusables.actions.environments-beta %}
|
||||
|
||||
### About environments
|
||||
|
||||
You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
Environment protection rules and environment secrets are only available on public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets.
|
||||
{% endif %}
|
||||
|
||||
#### Environment protection rules
|
||||
|
||||
Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. You can use environment protection rules to require a manual approval or to delay a job.
|
||||
|
||||
##### Required reviewers
|
||||
|
||||
Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed.
|
||||
|
||||
For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
|
||||
|
||||
##### Wait timer
|
||||
|
||||
Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days).
|
||||
|
||||
#### Environment secrets
|
||||
|
||||
Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
|
||||
|
||||
### Creating an environment
|
||||
|
||||
{% data reusables.github-actions.permissions-statement-environment %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.github-actions.sidebar-environment %}
|
||||
1. Click **New environment**.
|
||||
1. Enter a name for the environment, then click **Configure environment**. Environment names are not case sensitive. An environment name may not exceed 255 characters and must be unique within the repository.
|
||||
1. Configure any environment protection rules or environment secrets.
|
||||
|
||||
Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment.
|
||||
|
||||
### Referencing an environment
|
||||
|
||||
Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. When the job is sent to the runner, the job can access the environment's secrets.
|
||||
|
||||
For more information on syntax to reference environments in workflows, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idenvironment)." For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
|
||||
|
||||
When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
|
||||
|
||||
### Deleting an environment
|
||||
|
||||
{% data reusables.github-actions.permissions-statement-environment %}
|
||||
|
||||
Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.github-actions.sidebar-environment %}
|
||||
1. Next the the environment that you want to delete, click {% octicon "trashcan" aria-label="The trashcan icon" %}.
|
||||
2. Click **I understand, delete this environment**.
|
||||
@@ -309,9 +309,9 @@ Führt den Workflow aus, wenn das Ereignis `issue_comment` eintritt. {% data reu
|
||||
|
||||
{% data reusables.github-actions.branch-requirement %}
|
||||
|
||||
| Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` |
|
||||
| --------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------- | --------------- |
|
||||
| [`issue_comment`](/rest/reference/activity#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Letzter Commit im Standard-Branch | Standard-Branch |
|
||||
| Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` |
|
||||
| -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------- | --------------- |
|
||||
| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Letzter Commit im Standard-Branch | Standard-Branch |
|
||||
|
||||
{% data reusables.developer-site.limit_workflow_to_activity_types %}
|
||||
|
||||
@@ -534,7 +534,7 @@ on:
|
||||
|
||||
#### `pull_request_review`
|
||||
|
||||
Führt Deinen Workflow aus, wenn das Ereignis `pull_request_review` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)."
|
||||
Führt den Workflow aus, wenn das Ereignis `pull_request_review` eintritt. {% data reusables.developer-site.multiple_activity_types %} For information about the REST API, see "[Pull request reviews](/rest/reference/pulls#reviews)."
|
||||
|
||||
| Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` |
|
||||
| ---------------------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------------- | ------------------------------------------- |
|
||||
@@ -576,7 +576,13 @@ on:
|
||||
|
||||
#### `pull_request_target`
|
||||
|
||||
This event is similar to `pull_request`, except that it runs in the context of the base repository of the pull request, rather than in the merge commit. This means that you can more safely make your secrets available to the workflows triggered by the pull request, because only workflows defined in the commit on the base repository are run. For example, this event allows you to create workflows that label and comment on pull requests, based on the contents of the event payload.
|
||||
This event runs in the context of the base of the pull request, rather than in the merge commit as the `pull_request` event does. This prevents executing unsafe workflow code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow. This event allows you to do things like create workflows that label and comment on pull requests based on the contents of the event payload.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** The `pull_request_target` event is granted a read/write repository token and can access secrets, even when it is triggered from a fork. Although the workflow runs in the context of the base of the pull request, you should make sure that you do not check out, build, or run untrusted code from the pull request with this event. Additionally, any caches share the same scope as the base branch, and to help prevent cache poisoning, you should not save the cache if there is a possibility that the cache contents were altered.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
| Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` |
|
||||
| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | -------------- |
|
||||
@@ -725,4 +731,4 @@ on:
|
||||
|
||||
{% data reusables.github-actions.actions-do-not-trigger-workflows %} weitere Informationen findest Du unter „[Authentifizierung mit dem GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)“.
|
||||
|
||||
Wenn Du einen Workflow aus einem Workflow-Lauf auslösen möchtest, kannst Du das Ereignis mithilfe eines persönlichen Zugangs-Tokens auslösen. Du musst einen persönlichen Zugangs-Token erstellen und ihn als Geheimnis speichern. Um Dein Nutzungskosten für {% data variables.product.prodname_actions %} zu minimieren, pass auf, dass Du keine rekursiven oder unbeabsichtigten Workflow-Läufe erzeugst. Weitere Informationen findest Du unter „[Verschlüsselte Geheimnisse erstellen und speichern](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)“.
|
||||
Wenn Du einen Workflow aus einem Workflow-Lauf auslösen möchtest, kannst Du das Ereignis mithilfe eines persönlichen Zugangs-Tokens auslösen. Du musst einen persönlichen Zugangs-Token erstellen und ihn als Geheimnis speichern. Um Dein Nutzungskosten für {% data variables.product.prodname_actions %} zu minimieren, pass auf, dass Du keine rekursiven oder unbeabsichtigten Workflow-Läufe erzeugst. For more information on storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
|
||||
|
||||
@@ -27,11 +27,19 @@ You can configure workflows to run when specific GitHub events occur, at a sched
|
||||
|
||||
### Authentication and secrets
|
||||
|
||||
{% data variables.product.prodname_dotcom %} stellt ein Token zur Verfügung, mit dem Du Dich im Namen von {% data variables.product.prodname_actions %} authentifizieren kannst. You can also store sensitive information as a secret in your organization or repository. {% data variables.product.prodname_dotcom %} encrypts all secrets.
|
||||
{% data variables.product.prodname_dotcom %} stellt ein Token zur Verfügung, mit dem Du Dich im Namen von {% data variables.product.prodname_actions %} authentifizieren kannst. You can also store sensitive information as a secret in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}, repository, or environments{% else %} or repository{% endif %}. {% data variables.product.prodname_dotcom %} encrypts all secrets.
|
||||
|
||||
{% link_in_list /authentication-in-a-workflow %}
|
||||
{% link_in_list /encrypted-secrets %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
### Environments
|
||||
|
||||
Workflow jobs can reference environments that have protection rules or environment-specific secrets.
|
||||
|
||||
{% link_in_list /environments %}
|
||||
{% endif %}
|
||||
|
||||
### {% data variables.product.prodname_dotcom %}-gehostete Runner
|
||||
|
||||
GitHub offers hosted virtual machines to run workflows. The virtual machine contains an environment with tools, packages, and environment variables for GitHub Actions to use.
|
||||
|
||||
@@ -305,11 +305,13 @@ steps:
|
||||
|
||||
`echo "{path}" >> $GITHUB_PATH`
|
||||
|
||||
Fügt für alle nachfolgenden Aktionen im aktuellen Auftrag vor der Systemvariablen `PATH` ein Verzeichnis hinzu. Die gerade ausgeführte Aktion kann nicht auf die neue Pfadvariable zugreifen.
|
||||
Prepends a directory to the system `PATH` variable and makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action.
|
||||
|
||||
#### Beispiel
|
||||
|
||||
This example demonstrates how to add the user `$HOME/.local/bin` directory to `PATH`:
|
||||
|
||||
``` bash
|
||||
echo "/path/to/dir" >> $GITHUB_PATH
|
||||
echo "$HOME/.local/bin" >> $GITHUB_PATH
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
@@ -187,7 +187,7 @@ Weitere Informationen zur Cron-Syntax findest Du unter „[Ereignisse, die Workf
|
||||
|
||||
### `env`
|
||||
|
||||
Eine `map` mit Umgebungsvariablen, die für alle Jobs und Schritte im Workflow verfügbar sind. Darüber hinaus kannst Du auch Umgebungsvariablen festlegen, die ausschließlich für einen Job oder Schritt bereitstehen. Weitere Informationen findest Du unter [`jobs.<job_id>.env`](#jobsjob_idenv) und [`jobs.<job_id>.steps.env`](#jobsjob_idstepsenv).
|
||||
Eine `map` mit Umgebungsvariablen, die für alle Jobs und Schritte im Workflow verfügbar sind. Darüber hinaus kannst Du auch Umgebungsvariablen festlegen, die ausschließlich für einen Job oder Schritt bereitstehen. For more information, see [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
|
||||
|
||||
{% data reusables.repositories.actions-env-var-note %}
|
||||
|
||||
@@ -223,7 +223,7 @@ defaults:
|
||||
|
||||
Ein Workflow-Lauf besteht aus mindestens einem Auftrag. Die Aufträge werden standardmäßig parallel ausgeführt. Sollen Aufträge sequenziell ausgeführt werden, können Sie mit dem Stichwort `jobs.<job_id>.needs` eine Abhängigkeit von anderen Aufträgen definieren.
|
||||
|
||||
Jeder Job läuft in einer Umgebung, die mit `runs-on` angegeben wird.
|
||||
Each job runs in a runner environment specified by `runs-on`.
|
||||
|
||||
Innerhalb der Nutzungsbeschränkungen des Workflows kannst Du unbegrenzt viele Jobs ausführen. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
|
||||
|
||||
@@ -320,6 +320,39 @@ runs-on: [self-hosted, linux]
|
||||
|
||||
Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)“ und „[Selbst-gehostete Runner in einem Workflow verwenden](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)“.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
### `jobs.<job_id>.environment`
|
||||
|
||||
The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)."
|
||||
|
||||
You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)."
|
||||
|
||||
##### Example using a single environment name
|
||||
|
||||
```yaml
|
||||
environment: staging_environment
|
||||
```
|
||||
|
||||
##### Example using environment name and URL
|
||||
|
||||
```yaml
|
||||
environment:
|
||||
name: production_environment
|
||||
url: https://github.com
|
||||
```
|
||||
|
||||
The URL can be an expression and can use any context except for the `secrets` context. For more information about expressions, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
|
||||
|
||||
#### Beispiel
|
||||
{% raw %}
|
||||
```yaml
|
||||
environment:
|
||||
name: production_environment
|
||||
url: ${{ steps.step_name.outputs.url_output }}
|
||||
```
|
||||
{% endraw %}
|
||||
{% endif %}
|
||||
|
||||
### `jobs.<job_id>.outputs`
|
||||
|
||||
Eine `map` der Ausgaben eines Jobs. Ausgaben eines Jobs stehen allen nachgelagerten Jobs zur Verfügung, die von diesem Job abhängen. Weitere Informationen zur Definition von Abhängigkeiten zwischen Jobs findest Du unter [`Jobs.<job_id>.needs`](#jobsjob_idneeds).
|
||||
@@ -354,7 +387,7 @@ jobs:
|
||||
|
||||
### `jobs.<job_id>.env`
|
||||
|
||||
Eine `map` mit Umgebungsvariablen, die für alle Schritte im Auftrag verfügbar sind. Darüber hinaus können Sie Umgebungsvariablen für den gesamten Workflow oder für einen einzelnen Schritt festlegen. Weitere Informationen finden Sie unter [`env`](#env) und [`jobs.<job_id>.steps.env`](#jobsjob_idstepsenv).
|
||||
Eine `map` mit Umgebungsvariablen, die für alle Schritte im Auftrag verfügbar sind. Darüber hinaus können Sie Umgebungsvariablen für den gesamten Workflow oder für einen einzelnen Schritt festlegen. For more information, see [`env`](#env) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
|
||||
|
||||
{% data reusables.repositories.actions-env-var-note %}
|
||||
|
||||
@@ -429,11 +462,11 @@ jobs:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### `jobs.<job_id>.steps.id`
|
||||
### `jobs.<job_id>.steps[*].id`
|
||||
|
||||
Eindeutige Kennung für den Schritt. Anhand der `id` können Sie in Kontexten auf den Schritt verweisen. Weitere Informationen findest Du unter „[Kontext- und Ausdrucks-Syntax für {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)“.
|
||||
|
||||
### `jobs.<job_id>.steps.if`
|
||||
### `jobs.<job_id>.steps[*].if`
|
||||
|
||||
Mit der Bedingung `if` gibst Du an, dass ein Schritt nur dann ausgeführt werden soll, wenn eine bestimmte Bedingung erfüllt ist. Du kannst eine Bedingung mit jedem unterstützten Kontext und Ausdruck erstellen.
|
||||
|
||||
@@ -463,11 +496,11 @@ steps:
|
||||
uses: actions/heroku@1.0.0
|
||||
```
|
||||
|
||||
### `jobs.<job_id>.steps.name`
|
||||
### `jobs.<job_id>.steps[*].name`
|
||||
|
||||
Name Deines Schritts, der auf {% data variables.product.prodname_dotcom %} angezeigt wird.
|
||||
|
||||
### `jobs.<job_id>.steps.uses`
|
||||
### `jobs.<job_id>.steps[*].uses`
|
||||
|
||||
Wählt eine Aktion aus, die als Teil eines Schritts im Auftrag ausgeführt wird. Eine Aktion ist eine wiederverwendbare Code-Einheit. Sie können eine Aktion verwenden, die im selben Repository wie der Workflow, in einem öffentlichen Repository oder in einem [veröffentlichten Docker-Container-Image](https://hub.docker.com/) definiert ist.
|
||||
|
||||
@@ -570,7 +603,7 @@ jobs:
|
||||
uses: docker://gcr.io/cloud-builders/gradle
|
||||
```
|
||||
|
||||
### `jobs.<job_id>.steps.run`
|
||||
### `jobs.<job_id>.steps[*].run`
|
||||
|
||||
Führt Befehlszeilen-Programme über die Betriebssystem-Shell aus. Wenn Du keinen `name` angibst, wird standardmäßig der im Befehl `run` angegebene Text als Name für den Schritt übernommen.
|
||||
|
||||
@@ -675,7 +708,7 @@ Für integrierte Shell-Schlüsselwörter gelten die folgenden Standards, die dur
|
||||
- Wenn Du das Fail-Fast-Verhalten uneingeschränkt nutzen möchtest, hast Du anscheinend keine andere Wahl, als Dein Skript so zu schreiben, dass jeder Fehlercode geprüft und eine entsprechende Reaktion eingeleitet wird. Dieses Verhalten kann nicht standardmäßig bereitgestellt werden; Du musst es explizit in Dein Skript schreiben.
|
||||
- `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. Dieses Verhalten ist intern mit dem vorherigen Standardverhalten von `sh` und `pwsh` konsistent und ist der Standard für `cmd.exe`, weshalb dieses Verhalten unverändert bleibt.
|
||||
|
||||
### `jobs.<job_id>.steps.with`
|
||||
### `jobs.<job_id>.steps[*].with`
|
||||
|
||||
Eine `map` der Eingabeparameter, die in der Aktion definiert sind. Jeder Eingabeparameter ist ein Schlüssel-Wert-Paar. Eingabeparameter werden als Umgebungsvariablen festgelegt. Die Variable erhält das Präfix `INPUT_` und wird in Großbuchstaben umgewandelt.
|
||||
|
||||
@@ -695,7 +728,7 @@ jobs:
|
||||
last_name: Octocat
|
||||
```
|
||||
|
||||
### `jobs.<job_id>.steps.with.args`
|
||||
### `jobs.<job_id>.steps[*].with.args`
|
||||
|
||||
Ein `string`, der die Eingaben für einen Docker-Container definiert. Beim Start des Containers übergibt {% data variables.product.prodname_dotcom %} die `args`-Anweisung an den `ENTRYPOINT` des Containers. Ein `array of strings` wird von diesem Parameter nicht unterstützt.
|
||||
|
||||
@@ -718,7 +751,7 @@ Die `args`-Anweisungen werden anstelle der `CMD`-Anweisung in einem `Dockerfile`
|
||||
1. Verwenden Sie Standardwerte, die die Verwendung der Aktion ohne Angabe von `args` erlauben.
|
||||
1. Wenn die Aktion einen Schalter `--help` oder Ähnliches anbietet, verwende diesen als Standard, um eine selbstständige Dokumentation der Aktion herbeizuführen.
|
||||
|
||||
### `jobs.<job_id>.steps.with.entrypoint`
|
||||
### `jobs.<job_id>.steps[*].with.entrypoint`
|
||||
|
||||
Überschreibt den Docker-`ENTRYPOINT` im `Dockerfile` oder legt ihn fest, sofern er noch nicht angegeben wurde. Im Gegensatz zur Docker `ENTRYPOINT`-Anweisung, die eine Shell- und eine ausführbare Form aufweist, akzeptiert das Stichwort `entrypoint` nur einen einzigen Schritt, der die entsprechende ausführbare Datei definiert.
|
||||
|
||||
@@ -734,7 +767,7 @@ steps:
|
||||
|
||||
The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs.
|
||||
|
||||
### `jobs.<job_id>.steps.env`
|
||||
### `jobs.<job_id>.steps[*].env`
|
||||
|
||||
Legt Umgebungsvariablen für Schritte fest, die in der Runner-Umgebung verwendet werden sollen. Darüber hinaus können Sie Umgebungsvariablen für den gesamten Workflow oder für einen Auftrag festlegen. Weitere Informationen finden Sie unter [`env`](#env) und [`jobs.<job_id>.env`](#jobsjob_idenv).
|
||||
|
||||
@@ -755,11 +788,11 @@ steps:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### `jobs.<job_id>.steps.continue-on-error`
|
||||
### `jobs.<job_id>.steps[*].continue-on-error`
|
||||
|
||||
Verhindert das Fehlschlagen eines Auftrags, wenn ein Schritt fehlschlägt. Leg `true` fest, damit ein Auftrag auch dann erfolgreich abgeschlossen werden kann, wenn dieser Schritt fehlschlägt.
|
||||
|
||||
### `jobs.<job_id>.steps.timeout-minutes`
|
||||
### `jobs.<job_id>.steps[*].timeout-minutes`
|
||||
|
||||
Maximaler Zeitraum in Minuten für die Ausführung des Schritts, bevor der Prozess abgebrochen wird.
|
||||
|
||||
@@ -769,7 +802,7 @@ Die maximale Anzahl von Minuten, die ein Job ausgeführt wird, bevor {% data var
|
||||
|
||||
### `jobs.<job_id>.strategy`
|
||||
|
||||
Mit einer Strategie wird eine Build-Matrix für die Aufträge erstellt. Sie können verschiedene Varianten einer Umgebung definieren, in denen die einzelnen Aufträge ausgeführt werden.
|
||||
Mit einer Strategie wird eine Build-Matrix für die Aufträge erstellt. You can define different variations to run each job in.
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix`
|
||||
|
||||
|
||||
@@ -19,6 +19,7 @@ Your dedicated technical account manager in
|
||||
{% data variables.contact.github_support %} can configure email for notifications to be sent through your SMTP server. Make sure you include the following details in your support request.
|
||||
|
||||
- Your SMTP server address
|
||||
- Login information to authenticate to the server: username and password
|
||||
- The port your SMTP server uses to send email
|
||||
- The domain name that your SMTP server will send with a HELO response, if any
|
||||
- The type of encryption used by your SMTP server
|
||||
|
||||
@@ -94,7 +94,7 @@ For urgent issues, we can help you in English 24 hours per day, 7 days per week,
|
||||
| Tag nach Thanksgiving | Vierter Freitag im November |
|
||||
| Heiligabend | 24. Dezember |
|
||||
| 1. Weihnachtsfeiertag | 25. Dezember |
|
||||
| 2. Weihnachtsfeiertag | 26. Dezember |
|
||||
| 2. Weihnachtsfeiertag | 28. Dezember |
|
||||
| Silvester | 31. Dezember |
|
||||
|
||||
#### Feiertage in Japan
|
||||
|
||||
@@ -44,7 +44,7 @@ We offer support for {% data variables.product.prodname_advanced_security %} in
|
||||
|
||||
{% data variables.contact.enterprise_support %} beobachtet diese Feiertage in den USA. holidays.
|
||||
|
||||
| U.S. Weihnachtsfeiertag | Datum im Jahr 2018 |
|
||||
| U.S. Weihnachtsfeiertag | Date observed |
|
||||
| ----------------------- | ------------------------------ |
|
||||
| Neujahr | 1. Januar |
|
||||
| Martin Luther King Day | Dritter Montag im Januar |
|
||||
@@ -57,7 +57,7 @@ We offer support for {% data variables.product.prodname_advanced_security %} in
|
||||
| Tag nach Thanksgiving | Vierter Freitag im November |
|
||||
| Heiligabend | 24. Dezember |
|
||||
| 1. Weihnachtsfeiertag | 25. Dezember |
|
||||
| 2. Weihnachtsfeiertag | 26. Dezember |
|
||||
| 2. Weihnachtsfeiertag | 28. Dezember |
|
||||
| Silvester | 31. Dezember |
|
||||
|
||||
### {% data variables.product.prodname_advanced_security %}-Updates installieren
|
||||
|
||||
@@ -18,7 +18,11 @@ An enterprise account allows you to manage multiple organizations{% if enterpris
|
||||
- Security {% if enterpriseServerVersions contains currentVersion %}(single sign-on, two factor authentication)
|
||||
- Requests {% if enterpriseServerVersions contains currentVersion %}and support bundle sharing {% endif %}with {% data variables.contact.enterprise_support %}{% endif %}
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
|
||||
{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about the management of your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
|
||||
|
||||
For more information about the management of users, organizations, data, and policies for {% data variables.product.product_location %}, see "[Managing users, organizations, and repositories](/admin/user-management)" and "[Setting policies for your enterprise](/admin/policies)."
|
||||
|
||||
For more information about the management of enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)."
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
|
||||
@@ -51,6 +51,7 @@ GitHub Desktop-Tastenkürzel auf macOS
|
||||
| <kbd>⌘</kbd><kbd>2</kbd> | Commit-Verlauf anzeigen |
|
||||
| <kbd>⌘</kbd><kbd>B</kbd> | Alle Ihre Branches anzeigen |
|
||||
| <kbd>⌘</kbd><kbd>G</kbd> | Zum Commit-Zusammenfassungsfeld navigieren |
|
||||
| <kbd>⌘</kbd><kbd>Enter</kbd> | Commit changes when summary or description field is active |
|
||||
| <kbd>space (Leerzeichen)</kbd> | Select or deselect all highlighted files |
|
||||
| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>N</kbd> | Neuen Branch erstellen |
|
||||
| <kbd>⇧</kbd><kbd>⌘</kbd><kbd>R</kbd> | Aktuellen Branch umbenennen |
|
||||
@@ -104,6 +105,7 @@ GitHub Desktop-Tastenkürzel auf Windows
|
||||
| <kbd>STRG</kbd><kbd>2</kbd> | Commit-Verlauf anzeigen |
|
||||
| <kbd>STRG</kbd><kbd>B</kbd> | Alle Ihre Branches anzeigen |
|
||||
| <kbd>STRG</kbd><kbd>G</kbd> | Zum Commit-Zusammenfassungsfeld navigieren |
|
||||
| <kbd>Ctrl</kbd><kbd>Enter</kbd> | Commit changes when summary or description field is active |
|
||||
| <kbd>space (Leerzeichen)</kbd> | Select or deselect all highlighted files |
|
||||
| <kbd>STRG</kbd><kbd>UMSCHALT</kbd><kbd>N</kbd> | Neuen Branch erstellen |
|
||||
| <kbd>STRG</kbd><kbd>UMSCHALT</kbd><kbd>R</kbd> | Aktuellen Branch umbenennen |
|
||||
|
||||
@@ -265,7 +265,9 @@ The optional `redirect_uri` parameter can also be used for localhost URLs. If th
|
||||
|
||||
For the `http://localhost/path` callback URL, you can use this `redirect_uri`:
|
||||
|
||||
http://localhost:1234/path
|
||||
```
|
||||
http://localhost:1234/path
|
||||
```
|
||||
|
||||
### Creating multiple tokens for OAuth Apps
|
||||
|
||||
|
||||
@@ -49,39 +49,39 @@ The complete list of available query parameters, permissions, and events is list
|
||||
|
||||
You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission.
|
||||
|
||||
| Berechtigung | Beschreibung |
|
||||
| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Berechtigung | Beschreibung |
|
||||
| -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
|
||||
| [`checks (Prüfungen)`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`. |
|
||||
| `content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. |
|
||||
| [`contents (Inhalte)`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. |
|
||||
| [`checks (Prüfungen)`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`. |
|
||||
| `content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. |
|
||||
| [`contents (Inhalte)`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. |
|
||||
| [`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/v3/repos/deployments/). Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
| [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %}
|
||||
| [`follower`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`Issues (Lieferungen)`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`follower`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`Issues (Lieferungen)`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`Metadaten`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. |
|
||||
| [`Metadaten`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. |
|
||||
| [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %}
|
||||
| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/v3/orgs/hooks/). Can be one of: `none`, `read`, or `write`. |
|
||||
| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`. |
|
||||
| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/v3/orgs/hooks/). Can be one of: `none`, `read`, or `write`. |
|
||||
| `organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`. |
|
||||
| [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
|
||||
| [`Seiten`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/v3/repos/pages/). Can be one of: `none`, `read`, or `write`. |
|
||||
| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. |
|
||||
| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. |
|
||||
| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`Seiten`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/v3/repos/pages/). Can be one of: `none`, `read`, or `write`. |
|
||||
| `plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`. |
|
||||
| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. |
|
||||
| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}
|
||||
| [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
|
||||
| [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %}
|
||||
| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`statuses (Statusangaben)`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`. |
|
||||
| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. |
|
||||
| `beobachten` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. |
|
||||
| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`statuses (Statusangaben)`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. |
|
||||
| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %}
|
||||
| `vulnerability_alerts` | Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`.{% endif %}
|
||||
| `beobachten` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. |
|
||||
|
||||
### {% data variables.product.prodname_github_app %} webhook events
|
||||
|
||||
|
||||
@@ -85,7 +85,7 @@ Unlike OAuth apps, GitHub Apps have targeted permissions that allow them to requ
|
||||
|
||||
| GitHub Apps | OAuth Apps |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| By default, GitHub Apps have a single webhook that receives the events they are configured to receive for every repository they have access to. | OAuth Apps request the webhook scope to create a repository webhook for each repository they needs to receive events from. |
|
||||
| By default, GitHub Apps have a single webhook that receives the events they are configured to receive for every repository they have access to. | OAuth Apps request the webhook scope to create a repository webhook for each repository they need to receive events from. |
|
||||
| GitHub Apps receive certain organization-level events with the organization member's permission. | OAuth Apps request the organization webhook scope to create an organization webhook for each organization they need to receive organization-level events from. |
|
||||
|
||||
### Git access
|
||||
|
||||
@@ -67,7 +67,7 @@ If the user accepts your request, GitHub redirects back to your site with a temp
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)."
|
||||
Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)."
|
||||
|
||||
Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %}
|
||||
|
||||
|
||||
@@ -7,13 +7,11 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.pre-release-program.suspend-installation-beta %}
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
### Suspending a GitHub App
|
||||
|
||||
|
||||
@@ -166,7 +166,7 @@ To create a Probot App, follow these steps:
|
||||
}
|
||||
```
|
||||
|
||||
4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to [localhost:3000](http://localhost:3000), and click the **Register GitHub App** button:
|
||||
4. [Run the GitHub App locally](https://probot.github.io/docs/development/#running-the-app-locally). Navigate to `http://localhost:3000`, and click the **Register GitHub App** button:
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -4,6 +4,5 @@ intro: 'You can list free and paid tools for developers to use in {% data variab
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
---
|
||||
|
||||
|
||||
@@ -48,7 +48,7 @@ Customers can start a free trial for any paid plan on a Marketplace listing that
|
||||
|
||||
Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel.
|
||||
|
||||
For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)."
|
||||
For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)."
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -13,8 +13,14 @@ versions:
|
||||
|
||||
|
||||
|
||||
After your {% data variables.product.prodname_marketplace %} listing is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the onboarding process.
|
||||
After your {% data variables.product.prodname_marketplace %} listing for an app with a paid plan is created and approved, you'll provide payment details to {% data variables.product.product_name %} as part of the financial onboarding process.
|
||||
|
||||
Once your revenue reaches a minimum of $500 U.S. Dollars for the month, you'll receive an electronic payment from {% data variables.product.product_name %} for 75% of the sales price.
|
||||
Once your revenue reaches a minimum of $500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. This will be the income from marketplace transactions minus the amount charged by {% data variables.product.company_short %} to cover their running costs.
|
||||
|
||||
{% data reusables.apps.marketplace_revenue_share %}
|
||||
For transactions made before January 1, 2021, {% data variables.product.company_short %} retains 25% of transaction income. For transactions made after that date, only 5% is retained by {% data variables.product.company_short %}. This change will be reflected in payments received from the end of January 2021 onward.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** For details of the current pricing and payment terms, see "[{% data variables.product.prodname_marketplace %} developer agreement](/github/site-policy/github-marketplace-developer-agreement)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -53,7 +53,7 @@ In addition to the requirements for all apps above, each app that you offer as a
|
||||
- {% data variables.product.prodname_github_app %}s should have a minimum of 100 installations.
|
||||
- {% data variables.product.prodname_oauth_app %}s should have a minimum of 200 users.
|
||||
- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below.
|
||||
- Publishing organizations must have a verified domain and must enable two-factor authentication. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization.")
|
||||
- Publishing organizations must have a verified domain and must enable two-factor authentication. Weitere Informationen finden Sie unter „[Zwei-Faktor-Authentifizierung in Ihrer Organisation erzwingen](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)“.
|
||||
|
||||
When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the listing.
|
||||
|
||||
|
||||
@@ -11,6 +11,7 @@ versions:
|
||||
|
||||
{% link_in_list /about-githubs-apis %}
|
||||
{% link_in_list /managing-deploy-keys %}
|
||||
{% link_in_list /viewing-deployment-history %}
|
||||
{% link_in_list /using-ssh-agent-forwarding %}
|
||||
{% link_in_list /secret-scanning %}
|
||||
{% link_in_list /replacing-github-services %}
|
||||
|
||||
@@ -43,7 +43,9 @@ If you don't want to use SSH keys, you can use [HTTPS with OAuth tokens][git-aut
|
||||
* Users don't have to change their local SSH settings.
|
||||
* Multiple tokens (one for each user) are not needed; one token per server is enough.
|
||||
* A token can be revoked at any time, turning it essentially into a one-use password.
|
||||
{% if enterpriseServerVersions contains currentVersion %}
|
||||
* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization).
|
||||
{% endif %}
|
||||
|
||||
##### Cons
|
||||
|
||||
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: Viewing deployment history
|
||||
intro: View current and previous deployments for your repository.
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
---
|
||||
|
||||
{% data reusables.actions.environments-beta %}
|
||||
|
||||
You can deliver deployments through {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}{% data variables.product.prodname_actions %} and environments or with {% endif %}the REST API and third party apps. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information about {% data variables.product.prodname_actions %}, see "[{% data variables.product.prodname_actions %}](/actions)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)."
|
||||
|
||||
To view current and past deployments, click **Environments** on the home page of your repository. 
|
||||
|
||||
The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a "View deployment" button that links to the URL is shown next to the deployment.
|
||||
|
||||
The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/repos#inactive-deployments)."
|
||||
|
||||
You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)."
|
||||
@@ -91,7 +91,7 @@ The base reference branch of the pull request changed.
|
||||
|:------------------------- |:----------------:|:-------------------:|
|
||||
| <ul><li>Pull Requests</li></ul> | **X** | |
|
||||
|
||||
### Event object properties
|
||||
#### Event object properties
|
||||
|
||||
{% data reusables.issue-events.issue-event-common-properties %}
|
||||
|
||||
|
||||
@@ -71,7 +71,7 @@ end
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
|
||||
def verify_signature(payload_body)
|
||||
signature = 'sha256=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha256'), ENV['SECRET_TOKEN'], payload_body)
|
||||
return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_HUB_SIGNATURE_2'])
|
||||
return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_HUB_SIGNATURE_256'])
|
||||
end{% elsif currentVersion ver_lt "enterprise-server@2.23" %}
|
||||
def verify_signature(payload_body)
|
||||
signature = 'sha1=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha1'), ENV['SECRET_TOKEN'], payload_body)
|
||||
|
||||
@@ -430,7 +430,7 @@ When someone revokes their authorization of a {% data variables.product.prodname
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.pre-release-program.suspend-installation-beta %} For more information, see "[Suspending a {% data variables.product.prodname_github_app %} installation](/apps/managing-github-apps/suspending-a-github-app-installation/)."
|
||||
@@ -715,7 +715,7 @@ The webhook this event is configured on was deleted. This event will only listen
|
||||
|
||||
### paketieren
|
||||
|
||||
Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[blocking organization users](/rest/reference/orgs#blocking)" REST API. For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}.
|
||||
Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}.
|
||||
|
||||
#### Availability
|
||||
|
||||
@@ -1125,9 +1125,11 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends
|
||||
{{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }}
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@1.19" %}
|
||||
### security_advisory
|
||||
|
||||
Activity related to a security advisory. A security advisory provides information about security-related vulnerabilities in software on GitHub. The security advisory dataset also powers the GitHub security alerts, see "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies/)."
|
||||
{% endif %}
|
||||
|
||||
#### Availability
|
||||
|
||||
|
||||
@@ -28,4 +28,4 @@ To create and access the feedback pull request, you must enable the feedback pul
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](http://localhost:4000/en/free-pro-team@latest/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)"
|
||||
- "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)"
|
||||
|
||||
@@ -18,7 +18,7 @@ Damit Du ein {% data variables.product.prodname_student_pack %} nutzen kannst, m
|
||||
- Ein [{% data variables.product.prodname_dotcom %}-Benutzerkonto](/articles/signing-up-for-a-new-github-account) besitzen,
|
||||
- Mindestens 13 Jahre alt sein
|
||||
|
||||
Zu den Dokumenten, die Deinen aktuellen Status als Schüler oder Student belegen, gehören ein Bild Deines Schulausweises, Deines Stundenplans und Deiner Zeugnisse sowie ein Schreiben zur Bestätigung der Mitgliedschaft oder Immatrikulation.
|
||||
Documents that prove your current student status include a picture of your school ID with current enrollment date, class schedule, transcript, and affiliation or enrollment verification letter.
|
||||
|
||||
Während Deiner Zeit als Student wirst Du möglicherweise dazu aufgefordert, in regelmäßigen Abständen Deinen aktuellen akademischen Status zu bestätigen.
|
||||
|
||||
|
||||
@@ -11,17 +11,21 @@ versions:
|
||||
github-ae: '*'
|
||||
---
|
||||
|
||||
### Informationen zu geschützten Branches
|
||||
|
||||
{% data reusables.pull_requests.about-protected-branches %} Du kannst entscheiden, Einschränkungen zu erzwingen über die Art und Weise, wie ein Pull Request in Dein Repository zusammengeführt wird.
|
||||
|
||||
Durch das Erstellen von Regeln für geschützte Branches können Repository-Inhaber und Personen mit Administratorberechtigung für ein Repository bestimmte Workflows oder Anforderungen erzwingen, bevor ein Mitarbeiter einen Branch in Dein Repository überführen kann.
|
||||
|
||||
{% data reusables.repositories.branch-rules-example %} Weitere Informationen findest Du unter „[Geschützte Branches konfigurieren](/articles/configuring-protected-branches/).“
|
||||
|
||||
{% data reusables.pull_requests.you-can-auto-merge %}
|
||||
|
||||
### Priorisierung von Regeln für geschützte Branches
|
||||
|
||||
Wenn ein Repository mehrere Branch-Schutzregeln hat, die dieselben Branches betreffen, haben die Regeln, die einen spezifischen Branch-Namen enthalten, die höchste Priorität. Wenn es mehr als eine Branch-Schutzregel gibt, die auf den gleichen spezifischen Branch-Namen verweist, hat die zuerst erstellte Branch-Regel eine höhere Priorität.
|
||||
Wenn es für ein Repository mehrere Regeln für geschützte Branches gibt, die dieselben Branches betreffen, haben die Regeln, die einen spezifischen Branch-Namen enthalten, die höchste Priorität. Wenn es mehr als eine Regel für geschützte Branches gibt, die auf den gleichen spezifischen Branch-Namen verweist, hat die zuerst erstellte Branch-Regel eine höhere Priorität.
|
||||
|
||||
Branch-Schutzregeln mit einem Sonderzeichen, wie `*`, `?` oder `]` werden in der Reihenfolge ihrer Erstellung angewendet, sodass ältere Regeln mit diesen Zeichen eine höhere Priorität haben.
|
||||
Regeln für geschützte Branches mit einem Sonderzeichen, wie `*`, `?` oder `]`, werden in der Reihenfolge ihrer Erstellung angewendet, sodass ältere Regeln mit diesen Zeichen eine höhere Priorität haben.
|
||||
|
||||
### Einstellungen für geschützte Branches
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Pull-Request-Merges konfigurieren
|
||||
intro: 'Sie können Pull-Request-Merges auf {% data variables.product.product_location %} so konfigurieren, dass eine Angleichung an Ihren Workflow und Ihre Voreinstellungen für die Verwaltung des Git-Verlaufs erfolgt, indem Sie standardmäßige Merge-Commits, Squash-Commits oder Rebase-Commits an alle Pull Requests in Ihrem Repository aktivieren, deaktivieren oder erzwingen.'
|
||||
intro: 'You can configure pull request merges on {% data variables.product.product_location %} to match your workflow and preferences for managing Git history.'
|
||||
mapTopic: true
|
||||
redirect_from:
|
||||
- /articles/configuring-pull-request-merges
|
||||
|
||||
@@ -39,6 +39,7 @@ versions:
|
||||
{% link_in_list /about-merge-methods-on-github %}
|
||||
{% link_in_list /configuring-commit-squashing-for-pull-requests %}
|
||||
{% link_in_list /configuring-commit-rebasing-for-pull-requests %}
|
||||
{% link_in_list /managing-auto-merge-for-pull-requests-in-your-repository %}
|
||||
{% link_in_list /managing-the-automatic-deletion-of-branches %}
|
||||
{% topic_link_in_list /defining-the-mergeability-of-pull-requests %}
|
||||
{% link_in_list /about-protected-branches %}
|
||||
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: Managing auto-merge for pull requests in your repository
|
||||
intro: "You can allow or disallow auto-merge for pull requests in your repository."
|
||||
product: '{% data reusables.gated-features.auto-merge %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository.
|
||||
---
|
||||
|
||||
{% 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**. 
|
||||
@@ -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 included the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if enterpriseServerVersions contains currentVersion %}
|
||||
* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."{% endif %}{% if enterpriseServerVersions contains currentVersion %}
|
||||
* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
|
||||
|
||||
@@ -38,7 +38,7 @@ Wenn eine {% data variables.product.prodname_oauth_app %} Sie anhand Ihres {% da
|
||||
|
||||
*Scopes* sind benannte Gruppen von Berechtigungen, die eine {% data variables.product.prodname_oauth_app %} anfordern kann, um auf öffentliche wie nicht öffentliche Daten zuzugreifen.
|
||||
|
||||
Wenn Sie eine {% data variables.product.prodname_oauth_app %} verwenden möchten, die in {% data variables.product.product_name %} integriert ist, teilt die App Ihnen mit, welche Art von Zugriff auf Ihre Daten benötigt wird. Wenn Du der App Zugriff erteilen, kann sie Aktionen für Dich durchführen, beispielsweise das Lesen oder Ändern von Daten. Wenn Du beispielsweise eine App verwenden möchtest, die den Scope `user:email` fordert, hat die App Lesezugriff auf Deine privaten E-Mail-Adressen. For more information, see "[About scopes for {% data variables.product.prodname_oauth_app %}s](//apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
|
||||
Wenn Sie eine {% data variables.product.prodname_oauth_app %} verwenden möchten, die in {% data variables.product.product_name %} integriert ist, teilt die App Ihnen mit, welche Art von Zugriff auf Ihre Daten benötigt wird. Wenn Du der App Zugriff erteilen, kann sie Aktionen für Dich durchführen, beispielsweise das Lesen oder Ändern von Daten. Wenn Du beispielsweise eine App verwenden möchtest, die den Scope `user:email` fordert, hat die App Lesezugriff auf Deine privaten E-Mail-Adressen. For more information, see "[About scopes for {% data variables.product.prodname_oauth_app %}s](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ Anwendungen können *Lese*- oder *Schreib*zugriff auf Deine {% data variables.pr
|
||||
|
||||
*Scopes* sind benannte Gruppen von Berechtigungen, die eine Anwendung anfordern kann, um auf öffentliche und nicht öffentliche Daten zuzugreifen.
|
||||
|
||||
Wenn Sie eine Drittanbieter-Anwendung verwenden möchten, die in {% data variables.product.product_name %} integriert ist, teilt diese Anwendung Ihnen mit, welche Art von Zugriff auf Ihre Daten benötigt wird. Wenn Du der App Zugriff erteilst, kann sie Aktionen in Deinem Namen durchführen, beispielsweise das Lesen oder Ändern von Daten. Wenn Du beispielsweise eine App verwenden möchtest, die den Scope `user:email` fordert, hat die App Lesezugriff auf Deine privaten E-Mail-Adressen. For more information, see "[About scopes for {% data variables.product.prodname_oauth_app %}s](//apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
|
||||
Wenn Sie eine Drittanbieter-Anwendung verwenden möchten, die in {% data variables.product.product_name %} integriert ist, teilt diese Anwendung Ihnen mit, welche Art von Zugriff auf Ihre Daten benötigt wird. Wenn Du der App Zugriff erteilst, kann sie Aktionen in Deinem Namen durchführen, beispielsweise das Lesen oder Ändern von Daten. Wenn Du beispielsweise eine App verwenden möchtest, die den Scope `user:email` fordert, hat die App Lesezugriff auf Deine privaten E-Mail-Adressen. For more information, see "[About scopes for {% data variables.product.prodname_oauth_app %}s](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
|
||||
@@ -126,8 +126,8 @@ Bevor Du einen neuen SSH-Schlüssel zum SSH-Agenten für die Verwaltung Deiner S
|
||||
|
||||
1. Stellen Sie sicher, dass ssh-agent ausgeführt wird. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually:
|
||||
```shell
|
||||
# Den SSH-Agenten im Hintergrund starten
|
||||
$ eval $(ssh-agent -s)
|
||||
# start the ssh-agent in the background
|
||||
$ eval `ssh-agent -s`
|
||||
> Agent pid 59566
|
||||
```
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ Für den Test Deiner Verbindung musst Du diese Aktion mit Deinem Passwort authen
|
||||
> Are you sure you want to continue connecting (yes/no)?
|
||||
```
|
||||
|
||||
3. Vergewissere Dich, dass der in dieser Meldung angegebene Fingerprint mit einem der Fingerprints der Meldungen aus Schritt 2 übereinstimmt, und gib dann `yes` ein:
|
||||
3. Verify that the fingerprint in the message you see matches {% if currentVersion == "free-pro-team@latest" %}[{% data variables.product.prodname_dotcom %}'s RSA public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`:
|
||||
```shell
|
||||
> Hi <em>username</em>! You've successfully authenticated, but GitHub does not
|
||||
> provide shell access.
|
||||
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: Automatically merging a pull request
|
||||
intro: 'You can increase development velocity by enabling auto-merge for a pull request so that the pull request will merge automatically when all merge requirements are met.'
|
||||
product: '{% data reusables.gated-features.auto-merge %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
{% 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.
|
||||
|
||||
Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."
|
||||
|
||||
You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback).
|
||||
|
||||
### Enabling auto-merge
|
||||
|
||||
People with write permissions to a repository can enable auto-merge for a pull request.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-pr %}
|
||||
1. In the "Pull Requests" list, click the pull request you'd like to auto-merge.
|
||||
1. Optionally, to choose a merge method, select the **Enable auto-merge** drop-down menu, then click a merge method. Weitere Informationen finden Sie unter „[Informationen zum Mergen von Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)“. 
|
||||
1. Click **Enable auto-merge**. 
|
||||
1. If you chose the merge or squash and merge methods, type a commit message and description and choose the email address you want to author the merge commit. 
|
||||
1. Click **Confirm auto-merge**. 
|
||||
|
||||
### Disabling auto-merge
|
||||
|
||||
People with write permissions to a repository and pull request authors can disable auto-merge for a pull request.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-pr %}
|
||||
1. In the "Pull Requests" list, click the pull request you'd like to disable auto-merge for.
|
||||
1. In the merge box, click **Disable auto-merge**. 
|
||||
@@ -3,7 +3,7 @@ title: Einen Pull Request von einem Fork erstellen
|
||||
intro: Du kannst einen Pull Request erstellen, um Änderungen vorzuschlagen, die Du an einer Fork eines vorgelagerten Repositorys vorgenommen hast.
|
||||
redirect_from:
|
||||
- /articles/creating-a-pull-request-from-a-fork
|
||||
permissions: Jeder, der Schreibzugriff auf ein Repository hat, kann einen Pull-Request von einer benutzereigenen Fork erstellen.
|
||||
permissions: Anyone with write access to a repository can create a pull request from a user-owned fork.
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -60,5 +60,6 @@ versions:
|
||||
{% topic_link_in_list /incorporating-changes-from-a-pull-request %}
|
||||
{% link_in_list /about-pull-request-merges %}
|
||||
{% link_in_list /merging-a-pull-request %}
|
||||
{% link_in_list /automatically-merging-a-pull-request %}
|
||||
{% link_in_list /closing-a-pull-request %}
|
||||
{% link_in_list /reverting-a-pull-request %}
|
||||
|
||||
@@ -14,13 +14,15 @@ versions:
|
||||
|
||||
Mit einem Pull Request schlägst Du vor, dass Änderungen, die Du an einem Head-Branch gemacht hast, in einen Basis-Branch zusammengeführt werden sollten. {% data reusables.pull_requests.about-protected-branches %} Es kann jedoch Einschränkungen geben, wann Du einen Pull Request zu einem bestimmten Branch zusammenführen kannst. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).“
|
||||
|
||||
Wenn beim Pull Request Mergekonflikte vorliegen oder Du die Änderungen vor dem Zusammenführen testen möchtest, kannst Du [den Pull Request lokal auschecken](/articles/checking-out-pull-requests-locally) und ihn über die Befehlszeile zusammenführen.
|
||||
{% data reusables.pull_requests.you-can-auto-merge %}
|
||||
|
||||
Wenn beim Pull Request Mergekonflikte vorliegen oder Sie die Änderungen vor dem Mergen testen möchten, können Sie [den Pull Request lokal auschecken](/articles/checking-out-pull-requests-locally) und ihn über die Befehlszeile mergen.
|
||||
|
||||
Pull-Request-Entwürfe kannst du nicht zusammenführen. Weitere Informationen zu Entwürfen von Pull Requests findest Du unter „[Informationen zu Pull Requests](/articles/about-pull-requests#draft-pull-requests).“
|
||||
|
||||
{% data reusables.pull_requests.automatically-delete-branches %}
|
||||
|
||||
Wenn Du die Änderungen in einem Themen-Branch nicht in den vorgelagerten Branch zusammenführen möchtest, kannst Du [den Pull Request schließen](/articles/closing-a-pull-request), ohne ihn zusammenzuführen.
|
||||
Wenn Sie die Änderungen in einem Themen-Branch nicht in den vorgelagerten Branch mergen möchten, können Sie [den Pull Request schließen](/articles/closing-a-pull-request), ohne ihn zu mergen.
|
||||
|
||||
### Einen Pull Request auf {% data variables.product.prodname_dotcom %} zusammenführen
|
||||
|
||||
|
||||
@@ -296,7 +296,7 @@ You can quickly analyze small portions of a monorepo when you modify code in spe
|
||||
|
||||
### Accessing private repositories
|
||||
|
||||
If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs.<job_id>.steps.env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
|
||||
If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs.<job_id>.steps[*].env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
|
||||
|
||||
For example, the following configuration has Git replace the full URLs to the `ghost/foo`, `ghost/bar`, and `ghost/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable.
|
||||
|
||||
|
||||
@@ -54,7 +54,7 @@ On Windows, the `codeql-runner-win.exe` file usually requires no change to permi
|
||||
Once you have downloaded the {% data variables.product.prodname_codeql_runner %} and verified that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. It is important to notice that each CI server that you intend to use for {% data variables.product.prodname_code_scanning %} needs to have the {% data variables.product.prodname_codeql_runner %}. You might configure each server to copy the runner from a central, internal location, or you could use the REST API to get the runner direct from GitHub, for example:
|
||||
|
||||
```shell
|
||||
wget https://github.com/github/codeql-action/releases/download/codeql-bundle-20200826/codeql-runner-linux
|
||||
wget https://github.com/github/codeql-action/releases/latest/download/codeql-runner-linux
|
||||
chmod +x codeql-runner-linux
|
||||
```
|
||||
|
||||
@@ -129,7 +129,7 @@ This example is similar to the previous example, however this time the repositor
|
||||
> ...
|
||||
> CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
|
||||
and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
|
||||
Please export these variables to future processes so the build can be traced, for example by running "
|
||||
Please export these variables to future processes so that CodeQL can monitor the build, for example by running "
|
||||
. /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
|
||||
```
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ Um Dir zu helfen, Deine Abonnements zu verstehen und zu entscheiden, ob du Dich
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** Anstatt Dich abzumelden, hast Du die Möglichkeit, ein Repository zu ignorieren. Wenn Du ein Repository ignorierst, erhältst du keine Benachrichtigungen. Es wird nicht empfohlen, Repositorys zu ignorieren, da Du in diesem Fall auch keine Benachrichtigung erhältst, wenn Du @erwähnt wirst. {% if currentVersion == "free-pro-team@latest" %}If you're experiencing abuse and want to ignore a repository, please [contact support](/contact) so we can help. {% data reusables.policies.abuse %}{% endif %}
|
||||
**Hinweis:** Anstatt Dich abzumelden, hast Du die Möglichkeit, ein Repository zu ignorieren. Wenn Du ein Repository ignorierst, erhältst du keine Benachrichtigungen. Es wird nicht empfohlen, Repositorys zu ignorieren, da Du in diesem Fall auch keine Benachrichtigung erhältst, wenn Du @erwähnt wirst. {% if currentVersion == "free-pro-team@latest" %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -33,7 +33,7 @@ Zudem kannst Du Releases in einem Repository beobachten und deren Beobachtung be
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis:**Du kannst auch auswählen, dass ein Repository ignoriert werden soll. Wenn Du ein Repository ignorierst, erhältst du keine Benachrichtigungen. Es wird nicht empfohlen, Repositorys zu ignorieren, da Du in diesem Fall auch keine Benachrichtigung erhältst, wenn Du @erwähnt wirst. {% if currentVersion == "free-pro-team@latest" %}If you experiencing abuse and want to ignore a repository, please [contact support](/contact) so we can help. {% data reusables.policies.abuse %}{% endif %}
|
||||
**Hinweis:**Du kannst auch auswählen, dass ein Repository ignoriert werden soll. Wenn Du ein Repository ignorierst, erhältst du keine Benachrichtigungen. Es wird nicht empfohlen, Repositorys zu ignorieren, da Du in diesem Fall auch keine Benachrichtigung erhältst, wenn Du @erwähnt wirst. {% if currentVersion == "free-pro-team@latest" %}If you experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -27,10 +27,11 @@ Aufgrund der Komplexität der Codesuche gelten bei der Durchführung der Suche E
|
||||
- Only the _default branch_ is indexed for code search.{% if currentVersion == "free-pro-team@latest" %}
|
||||
- Nur Dateien kleiner 384 KB sind durchsuchbar.{% else %}* Nur Dateien kleiner 5 MB sind durchsuchbar.
|
||||
- Nur die ersten 500 KB jeder Datei sind durchsuchbar.{% endif %}
|
||||
- Nur Repositorys mit weniger als 500.000 Dateien sind durchsuchbar.
|
||||
- Ihre Suchabfrage nach Code muss mindestens einen Suchbegriff enthalten. Ausgenommen hiervon sind Suchen nach [`filename`](#search-by-filename). Beispielsweise ist eine Suche nach [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) ungültig, [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) ist dagegen gültig.
|
||||
- Only repositories with fewer than 500,000 files are searchable.{% if currentVersion == "free-pro-team@latest" %}
|
||||
- Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %}
|
||||
- Deine Quellcode-Suche muss mindestens einen Suchbegriff enthalten, ausgenommen bei [`filename`-Suchen](#search-by-filename). Beispielsweise ist eine Suche nach [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) ungültig, [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) ist dagegen gültig.
|
||||
- Die Suchergebnisse können maximal zwei gefundene Fragmente der gleichen Datei anzeigen, selbst wenn die Datei mehr Treffer enthält.
|
||||
- Folgende Platzhalterzeichen können in Suchabfragen nicht verwendet werden: <code>. , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ]</code>. Diese Zeichen werden bei der Suche ignoriert.
|
||||
- Folgende Platzhalterzeichen können in Suchabfragen nicht verwendet werden: <code>. , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ]</code>. Diese Zeichen werden bei der Suche schlicht ignoriert.
|
||||
|
||||
### Suche nach Dateiinhalten oder Dateipfad
|
||||
|
||||
|
||||
@@ -39,6 +39,7 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late
|
||||
| Auf das Auditprotokoll der Organisation zugreifen | **X** | | |
|
||||
| Die Profilseite der Organisation bearbeiten (siehe „[Informationen zum Profil Ihrer Organisation](/articles/about-your-organization-s-profile)“) | **X** | | |
|
||||
| Die Domänen der Organisation überprüfen (siehe „[Domänen Deiner Organisation überprüfen](/articles/verifying-your-organization-s-domain)“) | **X** | | |
|
||||
| Restrict email notifications to verified domains (see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)" for details) | **X** | | |
|
||||
| **Alle Teams** löschen | **X** | | |
|
||||
| Das Organisationskonto einschließlich aller Repositorys löschen | **X** | | |
|
||||
| Teams erstellen (siehe „[Berechtigungen für die Teamerstellung in Ihrer Organisation festlegen](/articles/setting-team-creation-permissions-in-your-organization)“) | **X** | **X** | |
|
||||
@@ -47,13 +48,13 @@ Organization members can have *owner*{% if currentVersion == "free-pro-team@late
|
||||
| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | |
|
||||
| Ein sichtbares Team @erwähnen | **X** | **X** | |
|
||||
| Kann *Team-Beteuern* werden | **X** | **X** | |
|
||||
| Einblicke für die Organisation anzeigen (siehe „[Einblicke für Deine Organisation anzeigen ](/articles/viewing-insights-for-your-organization)“) | **X** | **X** | |
|
||||
| Einblicke für die Organisation anzeigen (siehe „[Einblicke für Ihre Organisation anzeigen ](/articles/viewing-insights-for-your-organization)“) | **X** | **X** | |
|
||||
| Öffentliche Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | **X** | |
|
||||
| Private Teamdiskussionen zu **allen Teams** anzeigen und veröffentlichen (siehe „[Informationen zu Teamdiskussionen](/articles/about-team-discussions)“) | **X** | | |
|
||||
| Teamdiskussionen in **allen Teams** bearbeiten und löschen (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments)“) | **X** | | |
|
||||
| Kommentare zu Commits, Pull Requests und Issues ausblenden (siehe „[Störende Kommentare verwalten](/articles/managing-disruptive-comments/#hiding-a-comment)“) | **X** | **X** | |
|
||||
| Teamdiskussionen für eine Organisation deaktivieren (siehe „[Teamdiskussionen innerhalb Ihrer Organisation deaktivieren](/articles/disabling-team-discussions-for-your-organization)“) | **X** | | |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Die Anzeige von Abhängigkeiten-Einblicke einer Organisation verwalten (siehe „[Die Sichtbarkeit der Abhängigkeiten-Einblicke Deiner Organisation ändern](/articles/changing-the-visibility-of-your-organizations-dependency-insights)“) | **X** | | |{% endif %}
|
||||
| Die Anzeige von Einblicken zu den Abhängigkeiten einer Organisation verwalten (siehe „[Die Sichtbarkeit der Einblicke zu den Abhängigkeiten Ihrer Organisation ändern](/articles/changing-the-visibility-of-your-organizations-dependency-insights)“) | **X** | | |{% endif %}
|
||||
| Ein Team-Profilbild in **allen Teams** einrichten (siehe „[Profilbild Deines Teams festlegen](/articles/setting-your-team-s-profile-picture)“) | **X** | | |
|
||||
| Sponsor accounts and manage the organization's sponsorships (see "[Sponsoring open-source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" for details) | **X** | **X** | |
|
||||
| Manage email updates from sponsored accounts (see "[Managing updates from accounts your organization's sponsors](/github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors)" for details) | **X** | | |
|
||||
|
||||
@@ -60,7 +60,8 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben
|
||||
| [Melden von Missbrauch oder Spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %}
|
||||
| Anwenden von Kennzeichnungen | | **X** | **X** | **X** | **X** |
|
||||
| Create, edit, delete labels | | | **X** | **X** | **X** |
|
||||
| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |
|
||||
| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** |{% endif %}
|
||||
| Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** |
|
||||
| Markieren von [Issues und Pull Requests als Duplikat](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** |
|
||||
| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** |
|
||||
|
||||
@@ -9,13 +9,19 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
Wenn in einer Organisation beschränkte E-Mail-Benachrichtigungen aktiviert sind, können die Mitglieder der Organisation E-Mail-Benachrichtigungen zu den Aktivitäten der Organisation nur an E-Mail-Adressen innerhalb der hierfür verifizierten Domäne der Organisation erhalten. Weitere Informationen findest Du unter „[Domäne Deiner Organisation verifizieren](/articles/verifying-your-organization-s-domain).“
|
||||
### About email restrictions
|
||||
|
||||
When restricted email notifications are enabled in an organization, members can only use an email address associated with the organization's verified domains to receive email notifications about organization activity. Weitere Informationen findest Du unter „[Domäne Deiner Organisation verifizieren](/articles/verifying-your-organization-s-domain).“
|
||||
|
||||
Externe Mitarbeiter unterliegen nicht den Einschränkungen für E-Mail-Benachrichtigungen für verifizierte Domänen. Weitere Informationen zu externen Mitarbeitern findest Du unter „[Berechtigungsebenen für eine Organisation](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)."
|
||||
|
||||
If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified for the enterprise account, in addition to any domains verified for the organization. For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)."
|
||||
|
||||
### E-Mail-Benachrichtigungen auf eine genehmigte Domäne beschränken
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.verified-domains %}
|
||||
5. Aktiviere unter „Enforcement preferences“ (Durchsetzungspräferenzen) das Kontrollkästchen **Restrict email notifications to domain email** (E-Mail-Benachrichtigungen auf eine genehmigte E-Mail-Domäne beschränken) aus. 
|
||||
{% data reusables.organizations.restrict-email-notifications %}
|
||||
6. Klicke auf **Save** (Speichern).
|
||||
|
||||
@@ -8,39 +8,31 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
### About domain verification
|
||||
|
||||
Um Domänen auf {% data variables.product.product_name %} zu verifizieren, musst Du in der Organisation über Inhaberberechtigungen verfügen. Weitere Informationen finden Sie unter „[Berechtigungsebenen für eine Organisation](/articles/permission-levels-for-an-organization)". Darüber hinaus benötigst Du Zugriff, um die Domänen-Einträge mit Deinem Domänen-Hosting-Dienst zu ändern.
|
||||
|
||||
Nachdem Du die Inhaberschaft der Domains Deiner Organisation verifiziert hast, wird im Profil der Organisation der Badge „Verified“ (Verifiziert) angezeigt. Wenn Ihre Organisation in {% data variables.product.prodname_ghe_cloud %} vorhanden ist und den Unternehmensnutzungsbedingungen zugestimmt hat, können Organisationsinhaber die Identität der Organisationsmitglieder verifizieren, indem sie die E-Mail-Adresse der jeweiligen Mitglieder in der verifizierten Domain anzeigen. Weitere Informationen findest Du unter „[Informationen zum Profil Deiner Organisation](/articles/about-your-organization-s-profile/)“ und „[Auf Unternehmensnutzungsbedingungen umsteigen](/articles/upgrading-to-the-corporate-terms-of-service).“
|
||||
|
||||
Damit der Badge „Verified“ (Verifiziert) angezeigt wird, müssen die in Deinem Profil angezeigten Website- und E-Mail-Informationen mit denen der verifizierten Domäne oder Domänen übereinstimmen. Wenn die im Profil Deiner Organisation angezeigten Website- und E-Mail-Adressen auf unterschiedlichen Domänen gehostet werden, musst Du alle Domänen verifizieren.
|
||||
If your organization is owned by an enterprise account, a "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** Wenn die im Profil Deiner Organisation angezeigte E-Mail- und Websiteadresse Varianten derselben Domäne verwendet, musst Du beide Varianten verifizieren. Wenn das Profil Deiner Organisation beispielsweise die Website `www.example.com` und die E-Mail-Adresse `info@example.com` zeigt, musst Du sowohl `www.example.com` wie auch `example.com` verifizieren.
|
||||
|
||||
{% endnote %}
|
||||
{% data reusables.organizations.verified-domains-details %}
|
||||
|
||||
Auf {% data variables.product.prodname_ghe_cloud %} können Sie nach dem Verifizieren der Inhaberschaft der Domain Ihrer Organisation E-Mail-Benachrichtigungen für die Organisation auf diese Domain beschränken. Weitere Informationen findest Du unter „[E-Mail-Benachrichtigungen auf eine genehmigte Domäne beschränken](/articles/restricting-email-notifications-to-an-approved-domain).“
|
||||
|
||||
### Domänen Deiner Organisation überprüfen
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.verified-domains %}
|
||||
5. Klicke auf **Add a domain** (Domäne hinzufügen). 
|
||||
6. Gib im Domänen-Feld die Domäne ein, die verifiziert werden soll. Klicke anschließend auf **Add domain** (Domäne hinzufügen). 
|
||||
7. Befolge die unter **Add a DNS TXT record** (TXT-Eintrag für DNS hinzufügen) angegebenen Anweisungen, um mit Deinem Domänen-Hosting-Dienst einen TXT-Eintrag für DNS zu erstellen. Es kann bis zu 72 Stunden dauern, bis sich Deine DNS-Konfiguration ändert. Wechsle zum nächsten Schritt, sobald sich Deine DNS-Konfiguration geändert hat. 
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tipp:** Du kannst bestätigen, dass sich Deine DNS-Konfiguration geändert hat. Führe dazu den Befehl `dig` auf der Befehlszeile aus. Ersetze im Beispiel den Wert `ORGANIZATION` durch den Namen Deiner Organisation und den Wert `example.com` durch die Domäne, die verifiziert werden soll. In der Befehlsausgabe sollte Dein neuer TXT-Eintrag aufgelistet werden.
|
||||
|
||||
{% data reusables.organizations.add-domain %}
|
||||
{% data reusables.organizations.add-dns-txt-record %}
|
||||
1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. In der Befehlsausgabe sollte Ihr neuer TXT-Eintrag aufgelistet werden.
|
||||
```shell
|
||||
$ dig _github-challenge-<em>ORGANIZATION</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
|
||||
```
|
||||
|
||||
{% endtip %}
|
||||
|
||||
8. Nachdem Du bestätigt hast, dass Deinem DNS-Eintrag der TXT-Eintrag hinzugefügt wurde, solltest Du in den Einstellungen Deiner Organisation zur Registerkarte „Verified domains“ (Verifizierte Domänen) navigieren. Du kannst die obigen Schritte eins bis vier durchführen, um nach der Registerkarte für verifizierte Domänen zu suchen. 
|
||||
9. Klicke neben der Domäne, deren Verifizierung aussteht, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und anschließend auf **Continue verifying** (Verifizierung fortsetzen). 
|
||||
10. Klicke auf **Verify domain** (Domäne verifizieren). 
|
||||
11. Sobald der Badge „Verified“ (Verifiziert) auf der Profilseite Deiner Organisation sichtbar ist, kannst Du den TXT-Eintrag im Domänen-Hosting-Dienst optional aus dem DNS-Eintrag löschen. 
|
||||
8. Nachdem Sie bestätigt haben, dass Ihrem DNS-Eintrag der TXT-Eintrag hinzugefügt wurde, sollten Sie in den Einstellungen Ihrer Organisation zur Registerkarte „Verified domains“ (Verifizierte Domains) navigieren. Sie können die Schritte eins bis vier durchführen, um nach der Registerkarte für verifizierte Domains zu suchen. 
|
||||
{% data reusables.organizations.continue-verifying-domain %}
|
||||
11. Sobald der Badge „Verified“ (Verifiziert) auf der Profilseite Ihrer Organisation sichtbar ist, können Sie den TXT-Eintrag im Domain-Hosting-Dienst optional aus dem DNS-Eintrag löschen.
|
||||
|
||||
@@ -34,6 +34,8 @@ versions:
|
||||
{% link_in_list /enforcing-team-policies-in-your-enterprise-account %}
|
||||
{% link_in_list /enforcing-security-settings-in-your-enterprise-account %}
|
||||
{% link_in_list /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta %}
|
||||
{% link_in_list /verifying-your-enterprise-accounts-domain %}
|
||||
{% link_in_list /restricting-email-notifications-for-your-enterprise-account-to-approved-domains %}
|
||||
{% link_in_list /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account %}
|
||||
{% link_in_list /enforcing-github-actions-policies-in-your-enterprise-account %}
|
||||
{% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account %}
|
||||
|
||||
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: Restricting email notifications for your enterprise account to approved domains
|
||||
intro: "You can prevent your enterprise's information from leaking into personal accounts by restricting email notifications about activity in organizations owned by your enterprise account to verified domains."
|
||||
product: '{% data reusables.gated-features.enterprise-accounts %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
permissions: Enterprise owners can restrict email notifications for an enterprise account.
|
||||
---
|
||||
|
||||
{% data reusables.enterprise-accounts.verifying-domains-release-phase %}
|
||||
|
||||
### About email restrictions for your enterprise account
|
||||
|
||||
When you restrict email notifications to verified domains, enterprise members can only use an email address associated with a verified domain to receive email notifications about activity in organizations owned by your enterprise account. The domains can be inherited from the enterprise account or configured for the specific organization. For more information about email restrictions for organizations, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)."
|
||||
|
||||
If email restrictions are enabled for an enterprise account, organization owners cannot disable email restrictions for any organization owned by the enterprise account. If changes occur that result in an organization having no verified domains, either inherited from an enterprise account that owns the organization or for the specific organization, email restrictions will be disabled for the organization.
|
||||
|
||||
### Restricting email notifications for your enterprise account
|
||||
|
||||
Before you can restrict email notifications for your enterprise account, you must verify at least one domain for the enterprise account. For more information, see "[Verifying your enterprise account's domain](/github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain)."
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.verified-domains-tab %}
|
||||
{% data reusables.organizations.restrict-email-notifications %}
|
||||
1. Klicke auf **Save** (Speichern).
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: Verifying your enterprise account's domain
|
||||
intro: 'You can confirm the identity of organizations owned by your enterprise account by verifying ownership of your domain names with {% data variables.product.company_short %}.'
|
||||
product: '{% data reusables.gated-features.enterprise-accounts %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
permissions: Enterprise owners can verify an enterprise account's domain.
|
||||
redirect_from:
|
||||
- /github/articles/verifying-your-enterprise-accounts-domain
|
||||
- /early-access/github/articles/verifying-your-enterprise-accounts-domain
|
||||
---
|
||||
|
||||
{% data reusables.enterprise-accounts.verifying-domains-release-phase %}
|
||||
|
||||
### About domain verification
|
||||
|
||||
You can confirm that the websites and email addresses listed on the profiles of any organization owned by your enterprise account are controlled by your enterprise by verifying the domains. Verified domains for an enterprise account apply to every organization owned by the enterprise account, and organization owners can verify additional domains for their organizations. Weitere Informationen findest Du unter „[Domänen Deiner Organisation überprüfen](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain).“
|
||||
|
||||
After you verify ownership of your enterprise account's domains, a "Verified" badge will display on the profile of each organization that has the domain listed on its profile. {% data reusables.organizations.verified-domains-details %}
|
||||
|
||||
Organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain.
|
||||
|
||||
After you verify domains for your enterprise account, you can restrict email notifications to verified domains for all the organizations owned by your enterprise account. For more information, see "[Restricting email notifications for your enterprise account to approved domains](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains)."
|
||||
|
||||
Even if you don't restrict email notifications for the enterprise account, if an organization owner has restricted email notifications for the organization, organization members will be able to receive notifications from any domains verified for the enterprise account, in addition to any domains verified for the organization. For more information about restricting notifications for an organization, see "[Restricting email notifications to an approved domain](/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)."
|
||||
|
||||
### Verifying your enterprise account's domain
|
||||
|
||||
To verify your enterprise account's domain, you must have access to modify domain records with your domain hosting service.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.verified-domains-tab %}
|
||||
1. Klicke auf **Add a domain** (Domäne hinzufügen). 
|
||||
{% data reusables.organizations.add-domain %}
|
||||
{% data reusables.organizations.add-dns-txt-record %}
|
||||
1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ENTERPRISE-ACCOUNT` with the name of your enterprise account, and `example.com` with the domain you'd like to verify. In der Befehlsausgabe sollte Ihr neuer TXT-Eintrag aufgelistet werden.
|
||||
```shell
|
||||
dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
|
||||
```
|
||||
{% data reusables.organizations.continue-verifying-domain %}
|
||||
1. Optionally, after the "Verified" badge is visible on your organizations' profiles, delete the TXT entry from the DNS record at your domain hosting service. 
|
||||
@@ -46,7 +46,8 @@ 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)" |{% endif %}
|
||||
| Eine Sponsorenschaltfläche anzeigen | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |
|
||||
| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | {% endif %}
|
||||
|
||||
### Collaborator access for a repository owned by a user account
|
||||
|
||||
@@ -60,23 +61,24 @@ Collaborators on a personal repository can pull (read) the contents of the repos
|
||||
|
||||
Collaborators can also perform the following actions.
|
||||
|
||||
| Aktion | Weitere Informationen |
|
||||
|:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Fork the repository | „[Über Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |
|
||||
| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"</li></ul> |
|
||||
| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
|
||||
| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
|
||||
| Manage milestones for issues and pull requests in the repository | „[Meilensteine für Issues und Pull Requests erstellen und bearbeiten](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)“ |
|
||||
| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
|
||||
| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
|
||||
| Apply suggested changes to pull requests in the repository | "[Incorporating feedback in your pull request](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" |
|
||||
| Create a pull request from a fork of the repository | „[Einen Pull Request von einem Fork erstellen](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)“ |
|
||||
| Submit a review on a pull request that affects the mergeability of the pull request | „[Vorgeschlagene Änderungen in einem Pull Request überprüfen](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
|
||||
| Create and edit a wiki for the repository | „[Informationen zu Wikis](/github/building-a-strong-community/about-wikis)“ |
|
||||
| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
|
||||
| Aktion | Weitere Informationen |
|
||||
|:----------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Fork the repository | „[Über Forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |
|
||||
| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/github/building-a-strong-community/managing-disruptive-comments)"</li></ul> |
|
||||
| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
|
||||
| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
|
||||
| Manage milestones for issues and pull requests in the repository | „[Meilensteine für Issues und Pull Requests erstellen und bearbeiten](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)“ |
|
||||
| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
|
||||
| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)"{% endif %}
|
||||
| Apply suggested changes to pull requests in the repository | "[Incorporating feedback in your pull request](/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request)" |
|
||||
| Create a pull request from a fork of the repository | „[Einen Pull Request von einem Fork erstellen](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)“ |
|
||||
| Submit a review on a pull request that affects the mergeability of the pull request | „[Vorgeschlagene Änderungen in einem Pull Request überprüfen](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
|
||||
| Create and edit a wiki for the repository | „[Informationen zu Wikis](/github/building-a-strong-community/about-wikis)“ |
|
||||
| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
|
||||
| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
|
||||
| sich selbst als Mitarbeiter aus dem Repository entfernen | „[Dich selbst aus dem Repository eines Mitarbeiters entfernen](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)“ |
|
||||
| sich selbst als Mitarbeiter aus dem Repository entfernen | „[Dich selbst aus dem Repository eines Mitarbeiters entfernen](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)“ |
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
|
||||
@@ -4,8 +4,11 @@ intro: '{% data variables.product.prodname_insights %} analyzes your {% data var
|
||||
product: '{% data reusables.gated-features.github-insights %}'
|
||||
redirect_from:
|
||||
- /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization
|
||||
- /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization
|
||||
- /enterprise-server@2.21/github/site-policy/github-insights-and-data-protection-for-your-organization
|
||||
- /enterprise-server@2.20/github/site-policy/github-insights-and-data-protection-for-your-organization
|
||||
versions:
|
||||
enterprise-server: '*'
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
For more information about the terms that govern {% data variables.product.prodname_insights %}, see your {% data variables.product.prodname_ghe_one %} subscription agreement.
|
||||
|
||||
@@ -8,7 +8,7 @@ versions:
|
||||
|
||||
**DIESE BESTIMMUNGEN UND BEDINGUNGEN (DIE "VEREINBARUNG") REGELN IHRE TEILNAHME AM GITHUB MARKETPLACE-PROGRAMM. DURCH DIE ANMELDUNG ZUR TEILNAHME AM MARKETPLACE-PROGRAMM ODER DURCH KLICKEN AUF "ICH AKZEPTIERE" UNTEN BESTÄTIGEN SIE, DASS SIE DIESE VEREINBARUNG VERSTANDEN HABEN UND DASS SIE ALLE IHRE BESTIMMUNGEN UND BEDINGUNGEN AKZEPTIEREN. WENN SIE DIESE VEREINBARUNG IM NAMEN EINES UNTERNEHMENS ODER EINER ANDEREN JURISTISCHEN PERSON ABSCHLIEßEN, VERSICHERN SIE, DASS SIE RECHTLICH BEFUGT SIND, DIE PERSON AN DIESE VEREINBARUNG ZU BINDEN. IN DIESEM FALL BEDEUTET "SIE" DIE PERSON, DIE SIE VERTRETEN.**
|
||||
|
||||
Effective Date: July 21, 2020
|
||||
Effective Date: January 1, 2021
|
||||
|
||||
### 1. DEFINITIONEN
|
||||
|
||||
@@ -143,7 +143,7 @@ Für den Fall, dass Ihr Angebot zwangsläufig entfernt wird, weil es fehlerhaft
|
||||
|
||||
**6.1** GitHub fungiert als Vertragspartner für Entwicklerprodukte, die von Endbenutzern über den Marketplace gekauft werden.
|
||||
|
||||
**6.2** Preise für Marketplace-Angebote von Entwickleranwendungen werden in US-Dollar (USD) festgelegt. Der Entwickler hat die vollständige Kontrolle über die Festlegung von Preisen für jedes Angebot, und sobald diese Preise festgelegt sind, können diese Preise nicht geändert werden. Sie können eine Preisübersicht für ein bestehendes Angebot zurückziehen und eine neue Preisübersicht für ein solches Angebot hinzufügen, unter der Voraussetzung, dass sich diese neue Preisübersicht nicht negativ auf bestehende Endnutzer auswirkt. Die Preise, die Sie für Entwicklerprodukte festlegen, bestimmen den Zahlungsbetrag, den Sie erhalten. GitHub überweist 75% des Verkaufspreises in USD ohne Abzug von Steuern mit Ausnahme von Quellensteuern, die nach geltendem Recht erforderlich sind. Die restlichen 25 % des Verkaufspreises werden GitHub zugeteilt und einbehalten. GitHub überweist Ihnen am Ende jedes Monats und sobald ein Mindestbetrag von 500 USD erreicht wird, Ihren Zahlungsanteil.
|
||||
**6.2** Preise für Marketplace-Angebote von Entwickleranwendungen werden in US-Dollar (USD) festgelegt. Der Entwickler hat die vollständige Kontrolle über die Festlegung von Preisen für jedes Angebot, und sobald diese Preise festgelegt sind, können diese Preise nicht geändert werden. Sie können eine Preisübersicht für ein bestehendes Angebot zurückziehen und eine neue Preisübersicht für ein solches Angebot hinzufügen, unter der Voraussetzung, dass sich diese neue Preisübersicht nicht negativ auf bestehende Endnutzer auswirkt. Die Preise, die Sie für Entwicklerprodukte festlegen, bestimmen den Zahlungsbetrag, den Sie erhalten. GitHub überweist 95% des Verkaufspreises in USD ohne Abzug von Steuern mit Ausnahme von Quellensteuern, die nach geltendem Recht erforderlich sind. Die restlichen 5 % des Verkaufspreises werden GitHub zugeteilt und einbehalten. GitHub überweist Ihnen am Ende jedes Monats und sobald ein Mindestbetrag von 500 USD erreicht wird, Ihren Zahlungsanteil.
|
||||
|
||||
**6.3** Rückerstattungsanforderungen. Sie sind dafür verantwortlich, die Bedingungen für Rückerstattungen an Ihre Endbenutzer festzulegen. In keinem Fall ist GitHub dafür verantwortlich, Unterstützung für Rückerstattungen zu leisten; ebenfalls haftet GitHub nicht für die Bezahlung von Rückerstattungen.
|
||||
|
||||
@@ -169,7 +169,7 @@ UNTER KEINEN UMSTÄNDEN UND UNTER KEINER RECHTLICHEN GRUNDLAGE (SEI ES VERTRAGLI
|
||||
|
||||
**10.3** GitHub kann diese Vereinbarung jederzeit kündigen, wenn (a) Sie gegen eine Bestimmung dieser Vereinbarung verstoßen haben oder (b) GitHub gesetzlich dazu verpflichtet ist.
|
||||
|
||||
**10.4** Folgen der Kündigung durch den Entwickler. Nach Erhalt einer fünfundvierzig (45) Tage im Voraus erfolgenden schriftlichen Kündigung durch den Entwickler wird die Annahme neuer Kunden über den Marketplace für den Entwickler gesperrt. Alle ausstehenden Gebühren werden nach Beendigung und Entfernung des Entwicklerprodukts aus dem Marketplace überwiesen. Wird die Kündigung aufgrund einer Anderung dieser Bedingungen durch GitHub eingeleitet (Abschnitt 11), gelten die unmittelbar vor dieser Änderung in Kraft getretenen Bedingungen für die Dauer der 45-tägigen Kündigungsfrist bis zum Datum der tatsächlichen Kündigung.
|
||||
**10.4** Folgen der Kündigung durch den Entwickler. Nach Erhalt einer fünfundvierzig (45) Tage im Voraus erfolgenden schriftlichen Kündigung durch den Entwickler wird die Annahme neuer Kunden über den Marketplace für den Entwickler gesperrt. Alle ausstehenden Gebühren werden nach Beendigung und Entfernung des Entwicklerprodukts aus dem Marketplace überwiesen. If termination is initiated as a result of a GitHub modification to these terms (Section 11), the terms in effect immediately prior to such modification shall govern for the duration of the 45-day notice period until the date of actual termination.
|
||||
|
||||
**10.5** Die Verpflichtungen in den Abschnitten 2, 3, 4, 5, 8, 9 und 12-18 gelten auch nach Ablauf oder Kündigung dieser Vereinbarung.
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
Effective date: November 16, 2020
|
||||
Effective date: December 19, 2020
|
||||
|
||||
Vielen Dank, dass Sie GitHub Inc. ("GitHub", "wir") Ihren Quellcode, Ihre Projekte und Ihre persönlichen Informationen anvertrauen. Die Speicherung Ihrer persönlichen Daten ist eine große Verantwortung, und wir möchten, dass Sie wissen, wie wir diese handhaben.
|
||||
|
||||
@@ -28,14 +28,14 @@ Natürlich enthalten die Kurzfassung und die Zusammenfassung unten nicht alle In
|
||||
|
||||
| Abschnitt | Welche Informationen sind dort enthalten? |
|
||||
| ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [Welche Daten erfasst GitHub](#what-information-github-collects) | GitHub erfasst Daten direkt von Ihnen für Ihre Registrierung, Zahlung, Transaktionen und Ihr Benutzerprofil. Wir erfassen von Ihnen außerdem automatisch Ihre Nutzungsinformationen, Cookies und ähnliche Technologien und Geräteinformationen, die erforderlichenfalls Ihrer Zustimmung unterliegen. GitHub kann auch personenbezogene Benutzerinformationen von Dritten erfassen. Wir erfassen von Ihnen nur die minimale Menge an personenbezogenen Daten, die wir benötigen, es sei denn, Sie geben weitere an. |
|
||||
| [Welche Daten erfasst GitHub](#what-information-github-collects) | GitHub erfasst Daten direkt von Ihnen für Ihre Registrierung, Zahlung, Transaktionen und Ihr Benutzerprofil. We also automatically collect from you your usage information, cookies, and device information, subject, where necessary, to your consent. GitHub kann auch personenbezogene Benutzerinformationen von Dritten erfassen. Wir erfassen von Ihnen nur die minimale Menge an personenbezogenen Daten, die wir benötigen, es sei denn, Sie geben weitere an. |
|
||||
| [Welche Daten erfasst GitHub _nicht_](#what-information-github-does-not-collect) | Wir erfassen nicht wissentlich Daten von Kindern unter 13 Jahren, und wir erfassen keine [Sensiblen persönlichen Daten](https://gdpr-info.eu/art-9-gdpr/). |
|
||||
| [Wie verwendet GitHub Ihre Informationen](#how-github-uses-your-information) | In this section, we describe the ways in which we use your information, including to provide you the Service, to communicate with you, for security and compliance purposes, and to improve our Service. Wir beschreiben außerdem die Rechtsgrundlage, auf der wir Ihre Daten verarbeiten, sofern dies gesetzlich vorgeschrieben ist. |
|
||||
| [Weitergabe der von uns erfassten Daten](#how-we-share-the-information-we-collect) | Wir können Ihre Daten unter einem der folgenden Umstände an Dritte weitergeben: mit Ihrem Einverständnis, an unsere Dienstleistungsanbieter, zu Sicherheitszwecken, zur Erfüllung unserer gesetzlichen Verpflichtungen oder wenn es zu einem Wechsel der Kontrolle oder zum Verkauf von Unternehmenseinheiten oder Geschäftsbereichen kommt. Wir verkaufen Ihre persönlichen Daten nicht, und wir betreiben keine Werbung auf GitHub. Sie können eine Liste der Dienstanbieter einsehen, die auf Ihre Informationen zugreifen können. |
|
||||
| [Weitere wichtige Informationen](#other-important-information) | Wir stellen zusätzliche Informationen für Repository-Inhalte, öffentliche Informationen und Organisationen auf GitHub bereit. |
|
||||
| [Weitere Dienste](#additional-services) | Wir bieten Informationen zu zusätzlichen Serviceangeboten, einschließlich Anwendungen von Drittanbietern, GitHub Pages und GitHub-Anwendungen. |
|
||||
| [Wie Sie auf die von uns erfassten Daten zugreifen und diese kontrollieren können](#how-you-can-access-and-control-the-information-we-collect) | Wir bieten Ihnen Möglichkeiten, auf Ihre personenbezogenen Daten zuzugreifen, sie zu ändern oder zu löschen. |
|
||||
| [Unsere Verwendung von Cookies und Tracking](#our-use-of-cookies-and-tracking) | Wir verwenden Cookies für die allgemeine Funktionalität unserer Website, und wir verwenden eine kleine Anzahl von Tracking- und Analysediensten auf einigen Teilen unserer Website. Wir bieten eine Seite, die dies sehr transparent macht. Weitere Informationen finden Sie in diesem Abschnitt. |
|
||||
| [Unsere Verwendung von Cookies und Tracking](#our-use-of-cookies-and-tracking) | We only use strictly necessary cookies to provide, secure and improve our service. Wir bieten eine Seite, die dies sehr transparent macht. Weitere Informationen finden Sie in diesem Abschnitt. |
|
||||
| [Wie GitHub Ihre Daten schützt](#how-github-secures-your-information) | Wir setzen alle erforderlichen Maßnahmen ein, um die Vertraulichkeit, Integrität und Verfügbarkeit Ihrer persönlichen Daten auf GitHub zu schützen und die Ausfallsicherheit unserer Server zu gewährleisten. |
|
||||
| [GitHubs globale Datenschutzpraktiken](#githubs-global-privacy-practices) | We provide the same high standard of privacy protection to all our users around the world. |
|
||||
| [zur Kommunikation mit Ihnen](#how-we-communicate-with-you) | Die Kommunikation mit Ihnen erfolgt per E-Mail. Sie können in Ihren Kontoeinstellungen oder durch Kontaktaufnahme mit uns festlegen, wie wir Sie kontaktieren. |
|
||||
@@ -74,8 +74,8 @@ Wenn Sie ein kostenpflichtiges Konto bei uns haben, eine Anwendung verkaufen, di
|
||||
##### Usage information
|
||||
Wenn Sie auf unseren Dienst oder unsere Website zugreifen, erfassen wir automatisch dieselben grundlegenden Informationen, die die meisten Dienste sammeln, gegebenenfalls vorbehaltlich Ihrer Zustimmung. Dazu gehören Informationen darüber, wie Sie den Dienst verwenden, z. B. die von Ihnen angezeigten Seiten, die Referenz-Website, Ihre IP-Adresse und Sitzungsinformationen sowie Datum und Uhrzeit jeder Anfrage. Dies sind Informationen, die wir von jedem Besucher der Website erfassen, unabhängig davon, ob er ein Konto hat oder nicht. Diese Informationen können personenbezogene Benutzerdaten enthalten.
|
||||
|
||||
##### Cookies and similar technologies information
|
||||
Wie weiter unten beschrieben und gegebenenfalls vorbehaltlich Ihrer Zustimmung sammeln wir automatisch Informationen aus Cookies und ähnlichen Technologien (wie z. B. Cookie-ID und Einstellungen), damit Sie eingeloggt bleiben, um Ihre Präferenzen zu speichern und um Sie und Ihr Gerät zu identifizieren.
|
||||
##### Cookies
|
||||
As further described below, we automatically collect information from cookies (such as cookie ID and settings) to keep you logged in, to remember your preferences, to identify you and your device and to analyze your use of our service.
|
||||
|
||||
##### Device information
|
||||
Wir erfassen möglicherweise bestimmte Informationen über Ihr Gerät, z. B. die IP-Adresse, Browser- oder Clientanwendungsinformationen, Spracheinstellungen, Betriebssystem- und Anwendungsversion, Gerätetyp und -ID sowie Gerätemodell und Hersteller. Diese Informationen können personenbezogene Benutzerdaten enthalten.
|
||||
@@ -235,15 +235,17 @@ Die von Ihnen angegebene E-Mail-Adresse [über Ihre Git-Commit-Einstellungen](/g
|
||||
|
||||
#### Cookies
|
||||
|
||||
GitHub uses cookies and similar technologies (e.g., HTML5 localStorage) to make interactions with our service easy and meaningful. Cookies sind kleine Textdateien, die oft von Websites auf Computer-Festplatten oder mobilen Geräten von Besuchern gespeichert werden. We use cookies and similar technologies (hereafter collectively "cookies") to provide you our services, for example, to keep you logged in, remember your preferences, identify your device for security purposes, and provide information for future development of GitHub. Durch die Nutzung unserer Website erklären Sie sich damit einverstanden, dass wir diese Arten von Cookies auf Ihrem Computer oder Gerät speichern. Wenn Sie die Speicherung von Cookies auf Ihrem Browser oder Gerät deaktivieren, können Sie sich weder anmelden noch die Dienste von GitHub nutzen.
|
||||
GitHub only uses strictly necessary cookies. Cookies sind kleine Textdateien, die oft von Websites auf Computer-Festplatten oder mobilen Geräten von Besuchern gespeichert werden.
|
||||
|
||||
Auf unserer Webseite [Cookies und Tracking](/github/site-policy/github-subprocessors-and-cookies) beschreiben wir die von uns gesetzten Cookies, die Voraussetzungen für diese Cookies und die unterschiedlichen Arten von Cookies (temporär oder permanent). Die Website enthält außerdem eine Liste unserer externen Analyse- und Dienstanbieter sowie genaue Angaben darüber, welche Teile unserer Website von diesen Anbietern erfasst werden dürfen.
|
||||
We use cookies solely to provide, secure, and improve our service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, analyze your use of our service, compile statistical reports, and provide information for future development of GitHub. We use our own cookies for analytics purposes, but do not use any third-party analytics service providers.
|
||||
|
||||
#### Tracking und Analyse
|
||||
By using our service, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our service.
|
||||
|
||||
Wir verwenden eine Reihe von externen Analyse- und Dienstanbietern, um uns bei der Bewertung der Verwendung von GitHub durch unsere Benutzer zu unterstützen, statistische Berichte über Aktivitäten zusammenzustellen und unsere Inhalte und die Website-Leistung zu verbessern. Wir verwenden diese externen Analyseanbieter nur in bestimmten Bereichen unserer Website und alle von ihnen haben mit uns Datenschutzvereinbarungen unterzeichnet, die die Art der personenbezogenen Daten, die sie sammeln können, und den Zweck, für den sie die Informationen verarbeiten können, einschränken. Darüber hinaus verwenden wir unsere eigene interne Analysesoftware zur Bereitstellung von Funktionen und zur Verbesserung unserer Inhalte und Leistungen.
|
||||
Auf unserer Webseite [Cookies und Tracking](/github/site-policy/github-subprocessors-and-cookies) beschreiben wir die von uns gesetzten Cookies, die Voraussetzungen für diese Cookies und die unterschiedlichen Arten von Cookies (temporär oder permanent).
|
||||
|
||||
Einige Browser verfügen über integrierte "Do Not Track"-Funktionen (DNT), die ein Signal an die von Ihnen besuchten Websites senden können, um zu signalisieren, dass Sie nicht getracked werden möchten. GitHub reagiert auf Browser-DNT-Signale und folgt dem [W3C-Standard für das Reagieren auf DNT-Signale](https://www.w3.org/TR/tracking-dnt/). Wenn Sie DNT auf einem Browser, der DNT unterstützt, nicht aktiviert haben, können Cookies an bestimmten Stellen unserer Website Ihre Online-Surfaktivitäten auf anderen Online-Diensten nachverfolgen, aber wir gestatten es keinen Dritten, außer unseren Analyse- und Dienstanbietern, die Aktivitäten von GitHub-Benutzern auf GitHub zu verfolgen. You can read more about DNT in our [Tracking on GitHub](/github/site-policy/github-subprocessors-and-cookies#tracking-on-github) section of our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page.
|
||||
#### DNT
|
||||
|
||||
"[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. GitHub reagiert auf Browser-DNT-Signale und folgt dem [W3C-Standard für das Reagieren auf DNT-Signale](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. Es gibt auch gute Anwendungen, die die Online-Verfolgung verhindern. Ein gutes Beispiel dafür ist [Privacy Badger](https://privacybadger.org/).
|
||||
|
||||
### Wie GitHub Ihre Daten schützt
|
||||
|
||||
|
||||
@@ -10,9 +10,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
Effective date: **October 2, 2020**
|
||||
Effective date: **December 30, 2020**
|
||||
|
||||
GitHub bietet viel Transparenz darüber, wie wir Ihre Daten verwenden, wie wir Ihre Daten sammeln und mit wem wir Ihre Daten teilen. Zu diesem Zweck stellen wir Ihnen diese Seite zur Verfügung, mit Details zu [unseren Unterauftragsverarbeitern](#github-subprocessors), darüber, wie wir [Cookies](#cookies-on-github) verwenden, und wo und wie wir auf Git Hub [Tracking](#tracking-on-github) durchführen.
|
||||
GitHub bietet viel Transparenz darüber, wie wir Ihre Daten verwenden, wie wir Ihre Daten sammeln und mit wem wir Ihre Daten teilen. To that end, we provide this page, which details [our subprocessors](#github-subprocessors), and how we use [cookies](#cookies-on-github).
|
||||
|
||||
### GitHub-Unterauftragsverarbeiter
|
||||
|
||||
@@ -29,14 +29,13 @@ Wenn wir Ihre Daten an Unterauftragsverarbeiter, wie z. B. unsere Anbieter und D
|
||||
| Eloqua | Automatisierung von Marketingkampagnen | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Google Apps | Interne Unternehmensinfrastruktur | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Google Analytics | Analytics and performance | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| LinkedIn Navigator | Marketing-Datenanreicherungsservice | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| LinkedIn Navigator | Data enrichment service | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Magic Robot | Kampagnenberichte (Salesforce Add-on) | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| MailChimp | Kunden-Ticketing-E-Mail Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Mailgun | Transaktions-Mail-Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Microsoft | Microsoft Services | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Monday.com | Plattform für Teamkollaboration und Projektmanagement | Vereinigte Staaten von Amerika | Israel |
|
||||
| Nexmo | SMS-Benachrichtigungsanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Oracle | Unternehmens-Finanzsystem | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Salesforce.com | Customer Relations-Management | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Sendgrid | Transaktions-Mail-Dienstanbieter | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
| Sentry.io | Application monitoring provider | Vereinigte Staaten von Amerika | Vereinigte Staaten von Amerika |
|
||||
@@ -49,49 +48,35 @@ Wenn wir einen neuen Unterauftragsverarbeiter einsetzen, der die personenbezogen
|
||||
|
||||
### Cookies auf GitHub
|
||||
|
||||
GitHub uses cookies and similar technologies (collectively, “cookies”) to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them.
|
||||
GitHub uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our [Privacy Statement](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking) if you’d like more information about cookies, and on how and why we use them.
|
||||
|
||||
Since the number and names of cookies may change,the table below may be updated from time to time.
|
||||
|
||||
| Service Provider | Cookie Name | Beschreibung | Expiration* |
|
||||
|:------------------ |:------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------ |:------------------------------------------------------------- |
|
||||
| GitHub | `app_manifest_token` | This cookie is used during the App Manifest flow to maintain the state of the flow during the redirect to fetch a user session. | five minutes |
|
||||
| GitHub | `cookie-preferences` | This cookie is used to track user cookie preferences. | one year |
|
||||
| GitHub | `_device_id` | This cookie is used to track recognized devices. | one year |
|
||||
| GitHub | `dotcom_user` | This cookie is used to signal to us that the user is already logged in. | one year |
|
||||
| GitHub | `_gh_ent` | This cookie is used for temporary application and framework state between pages like what step the customer is on in a multiple step form. | two weeks |
|
||||
| GitHub | `_gh_sess` | This cookie is used for temporary application and framework state between pages like what step the user is on in a multiple step form. | Session, Sitzung |
|
||||
| GitHub | `gist_oauth_csrf` | This cookie is set by Gist to ensure the user that started the oauth flow is the same user that completes it. | deleted when oauth state is validated |
|
||||
| GitHub | `gist_user_session` | This cookie is used by Gist when running on a separate host. | two weeks |
|
||||
| GitHub | `has_recent_activity` | This cookie is used to prevent showing the security interstitial to users that have visited the app recently. | one hour |
|
||||
| GitHub | `__Host-gist_user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks |
|
||||
| GitHub | `__Host-user_session_same_site` | This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub. | two weeks |
|
||||
| GitHub | `logged_in` | This cookie is used to signal to us that the user is already logged in. | one year |
|
||||
| GitHub | `marketplace_repository_ids` | This cookie is used for the marketplace installation flow. | one hour |
|
||||
| GitHub | `marketplace_suggested_target_id` | This cookie is used for the marketplace installation flow. | one hour |
|
||||
| GitHub | `_octo` | This cookie is used by our internal analytics service to distinguish unique users and clients. | one year |
|
||||
| GitHub | `org_transform_notice` | This cookie is used to provide notice during organization transforms. | one hour |
|
||||
| GitHub | `private_mode_user_session` | This cookie is used for Enterprise authentication requests. | two weeks |
|
||||
| GitHub | `saml_csrf_token` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
|
||||
| GitHub | `saml_csrf_token_legacy` | This cookie is set by SAML auth path method to associate a token with the client. | until user closes browser or completes authentication request |
|
||||
| GitHub | `saml_return_to` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
|
||||
| GitHub | `saml_return_to_legacy` | This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop. | until user closes browser or completes authentication request |
|
||||
| GitHub | `tz` | This cookie allows your browser to tell us what time zone you're in. | Session, Sitzung |
|
||||
| GitHub | `user_session` | This cookie is used to log you in. | two weeks |
|
||||
| Google Analytics** | `_ga` | This cookie is used by Google Analytics. | two years |
|
||||
| Google Analytics** | `_gat` | This cookie is used by Google Analytics. | one minute |
|
||||
| Google Analytics** | `_gid` | This cookie is used by Google Analytics. | one day |
|
||||
| Service Provider | Cookie Name | Beschreibung | Expiration* |
|
||||
|:---------------- |:------------------------------------ |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------- |
|
||||
| GitHub | `app_manifest_token` | This cookie is used during the App Manifest flow to maintain the state of the flow during the redirect to fetch a user session. | five minutes |
|
||||
| GitHub | `_device_id` | This cookie is used to track recognized devices for security purposes. | one year |
|
||||
| GitHub | `dotcom_user` | Dieses Cookie wird verwendet, um uns zu signalisieren, dass der Benutzer bereits angemeldet ist. | one year |
|
||||
| GitHub | `_gh_ent` | This cookie is used for temporary application and framework state between pages like what step the customer is on in a multiple step form. | two weeks |
|
||||
| GitHub | `_gh_sess` | Dieses Cookie wird für temporäre Anwendungen und Framework-Status zwischen Seiten verwendet, z. B. in welchem Schritt sich der Benutzer in einem mehrstufigen Formular befindet. | Session, Sitzung |
|
||||
| GitHub | `gist_oauth_csrf` | Dieses Cookie wird von Gist gesetzt, um sicherzustellen, dass der Benutzer, der den auth-Flow gestartet hat, derselbe Benutzer ist, der ihn abschließt. | deleted when oauth state is validated |
|
||||
| GitHub | `gist_user_session` | Dieses Cookie wird von Gist verwendet, wenn es auf einem separaten Host ausgeführt wird. | two weeks |
|
||||
| GitHub | `has_recent_activity` | This cookie is used to prevent showing the security interstitial to users that have visited the app recently. | one hour |
|
||||
| GitHub | `__Host-gist_user_session_same_site` | Dieses Cookie wird so gesetzt, dass Browser, die SameSite-Cookies unterstützen, überprüfen können, ob eine Anfrage von GitHub stammt. | two weeks |
|
||||
| GitHub | `__Host-user_session_same_site` | Dieses Cookie wird so gesetzt, dass Browser, die SameSite-Cookies unterstützen, überprüfen können, ob eine Anfrage von GitHub stammt. | two weeks |
|
||||
| GitHub | `logged_in` | Dieses Cookie wird verwendet, um uns zu signalisieren, dass der Benutzer bereits angemeldet ist. | one year |
|
||||
| GitHub | `marketplace_repository_ids` | This cookie is used for the marketplace installation flow. | one hour |
|
||||
| GitHub | `marketplace_suggested_target_id` | This cookie is used for the marketplace installation flow. | one hour |
|
||||
| GitHub | `_octo` | This cookie is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics. | one year |
|
||||
| GitHub | `org_transform_notice` | This cookie is used to provide notice during organization transforms. | one hour |
|
||||
| GitHub | `private_mode_user_session` | This cookie is used for Enterprise authentication requests. | two weeks |
|
||||
| GitHub | `saml_csrf_token` | Dieses Cookie wird von der SAML auth path-Methode gesetzt, um dem Client ein Token zuzuordnen. | until user closes browser or completes authentication request |
|
||||
| GitHub | `saml_csrf_token_legacy` | Dieses Cookie wird von der SAML auth path-Methode gesetzt, um dem Client ein Token zuzuordnen. | until user closes browser or completes authentication request |
|
||||
| GitHub | `saml_return_to` | Dieses Cookie wird von der SAML auth path-Methode gesetzt, um den Status während der SAML-Authentifizierungsschleife beizubehalten. | until user closes browser or completes authentication request |
|
||||
| GitHub | `saml_return_to_legacy` | Dieses Cookie wird von der SAML auth path-Methode gesetzt, um den Status während der SAML-Authentifizierungsschleife beizubehalten. | until user closes browser or completes authentication request |
|
||||
| GitHub | `tz` | This cookie allows us to customize timestamps to your time zone. | Session, Sitzung |
|
||||
| GitHub | `user_session` | Dieses Cookie wird verwendet, um Sie anzumelden. | two weeks |
|
||||
|
||||
_*_ The **expiration** dates for the cookies listed below generally apply on a rolling basis.
|
||||
|
||||
_**_ We use **Google Analytics** as a third party analytics service to collect information about how our website performs and how our users, in general, navigate through and use GitHub. This helps us evaluate our users' use of GitHub, compile statistical reports on activity, and improve our content and website performance.
|
||||
|
||||
You can control your Google Analytics cookie preferences through our cookie preference link located at the footer of our website. In addition, Google provides further information about its own privacy practices and [offers a browser add-on to opt out of Google Analytics tracking](https://tools.google.com/dlpage/gaoptout).
|
||||
|
||||
(!) Please note certain pages on our website may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets.
|
||||
|
||||
### Tracking on GitHub
|
||||
|
||||
"[Do Not Track](https://www.eff.org/issues/do-not-track)" (DNT) is a privacy preference you can set in your browser if you do not want online services to collect and share certain kinds of information about your online activity from third party tracking services. GitHub reagiert auf Browser-DNT-Signale und folgt dem [W3C-Standard für das Reagieren auf DNT-Signale](https://www.w3.org/TR/tracking-dnt/). If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as [Privacy Badger](https://www.eff.org/privacybadger).
|
||||
|
||||
If you have not enabled DNT on a browser that supports it, cookies on some parts of our website will track your online browsing activity on other online services over time, though we do not permit third parties other than our analytics and service providers to track GitHub users' activity over time on GitHub. We have agreements with certain vendors, such as analytics providers, who help us track visitors' movements on certain pages on our website. Only our vendors, who are collecting personal information on our behalf, may collect data on our pages, and we have signed data protection agreements with every vendor who collects this data on our behalf. We use the data we receive from these vendors to better understand our visitors' interests, to understand our website's performance, and to improve our content. Any analytics vendor will be listed in our [subprocessor list](#github-subprocessors), and you may see a list of every page where we collect this kind of data below.
|
||||
(!) Please note while we limit our use of third party cookies to those necessary to provide external functionality when rendering external content, certain pages on our website may set other third party cookies. Beispielsweise können wir Inhalte, z. B. Videos, von einer anderen Website, die ein Cookie setzt, einbetten. Während wir versuchen, diese Cookies von Drittanbietern zu minimieren, können wir nicht immer kontrollieren, welche Cookies diese Inhalte von Drittanbietern setzen.
|
||||
|
||||
@@ -163,8 +163,6 @@ c/o Corporation Service Company
|
||||
Sacramento, CA 95833-3505, USA.
|
||||
```
|
||||
|
||||
Sie können auch eine Kopie an legal@support.github.com senden.
|
||||
|
||||
Bitte formulieren Sie Ihre Wünsche so spezifisch und begrenzt wie möglich, einschließlich der folgenden Informationen:
|
||||
|
||||
- Vollständige Informationen über die Behörde, die die Anfrage ausstellt
|
||||
|
||||
@@ -39,12 +39,6 @@ If vulnerabilities have been detected in the repository, these are shown at the
|
||||
Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to
|
||||
{% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_ghe_server %} does not populate the **Dependents** view.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
@@ -58,12 +52,6 @@ Any direct and indirect dependencies that are specified in the repository's mani
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %}
|
||||
Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to security alerts.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_ghe_server %} does not populate the **Dependents** view.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
@@ -93,6 +81,24 @@ You can also enable or disable the dependency graph for all repositories owned b
|
||||
4. Read the message about granting {% data variables.product.product_name %} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**. 
|
||||
|
||||
You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the Security & analysis tab.
|
||||
|
||||
### Changing the "Used by" package
|
||||
|
||||
If the dependency graph is enabled, and your repository contains a package that's published on a supported package ecosystem, {% data variables.product.prodname_dotcom %} displays a "Used by" section in the sidebar of the **Code** tab of your repository. For more information about the supported package ecosystems, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
|
||||
|
||||
The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
|
||||
|
||||
|
||||
|
||||
Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
|
||||
|
||||
The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-security-and-analysis %}
|
||||
4. Under "Configure security and analysis features", click the drop-down menu in the "Used by counter" section and choose a package. 
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Fehler beim Abhängigkeitsdiagramm beheben
|
||||
|
||||
@@ -40,8 +40,9 @@ Zum Einrichten einer `www`- oder benutzerdefinierten Subdomäne wie `www.example
|
||||
{% data reusables.pages.navigate-site-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.pages.save-custom-domain %}
|
||||
5. Navigiere zu Deinem DNS-Provider, und erstelle einen `CNAME` Datensatz, welcher Deine Subdomäne auf die Standarddomäne Deiner Website verweist. Soll beispielsweise die Subdomäne `www.example.com` für Deine Benutzer-Website verwendet werden, erstelle einen `CNAME`-Datensatz, mit dem `www.example.com` auf `<user>.github.io` verweist. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `<organization>.github.io`. The `CNAME` file should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name.
|
||||
{% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
5. Navigiere zu Deinem DNS-Provider, und erstelle einen `CNAME` Datensatz, welcher Deine Subdomäne auf die Standarddomäne Deiner Website verweist. Soll beispielsweise die Subdomäne `www.example.com` für Deine Benutzer-Website verwendet werden, erstelle einen `CNAME`-Datensatz, mit dem `www.example.com` auf `<user>.github.io` verweist. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
|
||||
{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. Prüfe die korrekte Konfiguration des DNS-Datensatzes mit dem Befehl `dig`, und ersetze _WWW.EXAMPLE.COM_ dabei durch Deine Subdomäne.
|
||||
```shell
|
||||
@@ -72,6 +73,8 @@ Zum Einrichten einer Apex-Domäne, beispielsweise `example.com`, musst Du eine _
|
||||
185.199.110.153
|
||||
185.199.111.153
|
||||
```
|
||||
|
||||
{% indented_data_reference site.data.reusables.pages.wildcard-dns-warning spaces=3 %}
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. Prüfe die korrekte Konfiguration des DNS-Datensatzes mit dem Befehl `dig`, und ersetze _EXAMPLE.COM_ dabei durch Deine Apex-Domäne. Prüfe, ob die Ergebnisse mit den obigen IP-Adressen für {% data variables.product.prodname_pages %} übereinstimmen.
|
||||
```shell
|
||||
|
||||
@@ -39,11 +39,7 @@ Deine Website darf nicht:
|
||||
- Mehrere `www`-Subdomänen umfassen. Beispiel: `www.example.com` und `www.anotherexample.com`.
|
||||
- Sowohl eine Apex-Domäne als auch eine benutzerdefinierte Subdomäne umfassen. Beispiel: `example.com` und `docs.example.com`.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warnung:** Es wird dringend empfohlen, keine Platzhalter-DNS-Einträge wie `*.example.com` zu verwenden. Dadurch würdest Du jedem ermöglichen, eine {% data variables.product.prodname_pages %}-Website auf Deinen Subdomänen zu hosten.
|
||||
|
||||
{% endwarning %}
|
||||
{% data reusables.pages.wildcard-dns-warning %}
|
||||
|
||||
Eine Liste der unterstützten benutzerdefinierten Domänen findest Du unter „[Informationen zu benutzerdefinierten Domänen und {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains).“
|
||||
|
||||
@@ -53,7 +49,7 @@ Zugriff über HTTPS ist auf {% data variables.product.prodname_pages %}-Websites
|
||||
|
||||
Nach der Konfiguration Deiner benutzerdefinierten Domäne kann es bis zu einer Stunde dauern, bis die Website über HTTPS verfügbar ist. Nach einer Aktualisierung bestehender DNS-Einstellungen musst Du Deine benutzerdefinierte Domäne zudem eventuell aus dem Repository Deiner Website entfernen und erneut dort einfügen, um den Prozess der HTTPS-Aktivierung zu initiieren. Weitere Informationen findest Du unter „[Eine benutzerdefinierte Domäne für Deine {% data variables.product.prodname_pages %}-Website verwalten](/articles/managing-a-custom-domain-for-your-github-pages-site).“
|
||||
|
||||
Wenn Du CAA-Einträge (Certification Authority Authorization) verwendest, muss mindestens ein CAA-Eintrag mit dem Wert `letsencrypt.org` vorhanden sein, wenn Deine Website über HTTPS zugänglich sein soll. Weitere Informationen findest Du in der 'Let's Encrypt'-Dokumentation unter „[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)“.
|
||||
Wenn Du CAA-Einträge (Certification Authority Authorization) verwendest, muss mindestens ein CAA-Eintrag mit dem Wert `letsencrypt.org` vorhanden sein, wenn Deine Website über HTTPS zugänglich sein soll. Weitere Informationen finden Sie in der Let's Encrypt-Dokumentation unter „[Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)“.
|
||||
|
||||
### URL-Formatierung unter Linux
|
||||
|
||||
|
||||
@@ -117,7 +117,7 @@ These two examples show how to calculate the total nodes in a call.
|
||||
|
||||
= 22,060 total nodes</pre>
|
||||
|
||||
### Rate limit
|
||||
## Rate limit
|
||||
|
||||
The GraphQL API v4 limit is different from the REST API v3's [rate limits](/rest/overview/resources-in-the-rest-api#rate-limiting).
|
||||
|
||||
@@ -130,12 +130,6 @@ To accurately represent the server cost of a query, the GraphQL API v4 calculate
|
||||
|
||||
The GraphQL API v4 rate limit is **5,000 points per hour**.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
For {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 points per hour.
|
||||
|
||||
{% endif %}
|
||||
|
||||
Note that 5,000 points per hour is not the same as 5,000 calls per hour: the GraphQL API v4 and REST API v3 use different rate limits.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Enums
|
||||
redirect_from:
|
||||
- /v4/enum
|
||||
- /v4/reference/enum
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Input objects
|
||||
redirect_from:
|
||||
- /v4/input_object
|
||||
- /v4/reference/input_object
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Interfaces
|
||||
redirect_from:
|
||||
- /v4/interface
|
||||
- /v4/reference/interface
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Mutations
|
||||
redirect_from:
|
||||
- /v4/mutation
|
||||
- /v4/reference/mutation
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Objects
|
||||
redirect_from:
|
||||
- /v4/object
|
||||
- /v4/reference/object
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Queries
|
||||
miniTocMaxHeadingLevel: 2
|
||||
redirect_from:
|
||||
- /v4/query
|
||||
- /v4/reference/query
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Scalars
|
||||
redirect_from:
|
||||
- /v4/scalar
|
||||
- /v4/reference/scalar
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: Unions
|
||||
redirect_from:
|
||||
- /v4/union
|
||||
- /v4/reference/union
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
|
||||
@@ -19,4 +19,4 @@ You can choose which contributors are included in metrics and create teams of co
|
||||
|
||||
### Weiterführende Informationen
|
||||
- "[Metrics available with {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)"
|
||||
- "[{% data variables.product.prodname_insights %} and data protection for your organization](/github/site-policy/github-insights-and-data-protection-for-your-organization)"
|
||||
- "<a href="/github/site-policy/github-insights-and-data-protection-for-your-organization" class="dotcom-only">{% data variables.product.prodname_insights %} and data protection for your organization</a>"
|
||||
@@ -99,4 +99,4 @@ To configure {% data variables.product.prodname_insights %} to connect to {% dat
|
||||
### Weiterführende Informationen
|
||||
|
||||
- "[Managing repositories](/insights/installing-and-configuring-github-insights/managing-repositories)"
|
||||
- "[{% data variables.product.prodname_insights %} and data protection for your organization](/github/site-policy/github-insights-and-data-protection-for-your-organization)"
|
||||
- "<a href="/github/site-policy/github-insights-and-data-protection-for-your-organization" class="dotcom-only">{% data variables.product.prodname_insights %} and data protection for your organization</a>"
|
||||
|
||||
@@ -16,6 +16,17 @@ versions:
|
||||
|
||||
**Note:** When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
### Limits for published npm versions
|
||||
|
||||
If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage.
|
||||
|
||||
To reduce the number of versions you have published for your npm package, consider deleting package versions. Weitere Informationen findest Du unter „[Ein Paket löschen](/packages/manage-packages/deleting-a-package)."
|
||||
|
||||
In the future, {% data variables.product.company_short %} will enforce a hard limit on publishing more than 1,000 versions of an npm package. When we start enforcing the 1,000 versions limit for each npm package hosted on {% data variables.product.prodname_registry %}, we will offer more guidance on how to manage your package versions.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Bei {% data variables.product.prodname_registry %} authentifizieren
|
||||
|
||||
{% data reusables.package_registry.authenticate-packages %}
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user