repo sync
This commit is contained in:
Octomerger Bot
@@ -5,6 +5,8 @@ product: '{% data reusables.gated-features.actions %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
authors:
|
||||
- potatoqualitee
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -0,0 +1,318 @@
|
||||
---
|
||||
title: Building and testing Ruby
|
||||
intro: You can create a continuous integration (CI) workflow to build and test your Ruby project.
|
||||
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 shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem.
|
||||
|
||||
### Vorrausetzungen
|
||||
|
||||
We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. Weitere Informationen findest Du unter:
|
||||
|
||||
- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
|
||||
- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/)
|
||||
|
||||
### Starting with the Ruby workflow template
|
||||
|
||||
{% data variables.product.prodname_dotcom %} provides a Ruby workflow template that will work for most Ruby projects. For more information, see the [Ruby workflow template](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
|
||||
|
||||
Um schnell loszulegen, füge die Vorlage in das Verzeichnis `.github/workflows` Deines Repositorys ein.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
name: Ruby
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [ $default-branch ]
|
||||
pull_request:
|
||||
branches: [ $default-branch ]
|
||||
|
||||
jobs:
|
||||
test:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- name: Set up Ruby
|
||||
# To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
|
||||
# change this to (see https://github.com/ruby/setup-ruby#versioning):
|
||||
# uses: ruby/setup-ruby@v1
|
||||
uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- name: Install dependencies
|
||||
run: bundle install
|
||||
- name: Run tests
|
||||
run: bundle exec rake
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Specifying the Ruby version
|
||||
|
||||
The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
|
||||
|
||||
Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby.
|
||||
|
||||
The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: 2.6 # Not needed with a .ruby-version file
|
||||
- run: bundle install
|
||||
- run: bundle exec rake
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
Alternatively, you can check a `.ruby-version` file into the root of your repository and `setup-ruby` will use the version defined in that file.
|
||||
|
||||
### Testing with multiple versions of Ruby
|
||||
|
||||
You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
ruby-version: [2.7.x, 2.6.x, 2.5.x]
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "Workflow syntax for GitHub Actions" and "Context and expression syntax for GitHub Actions."
|
||||
|
||||
The full updated workflow with a matrix strategy could look like this:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
name: Ruby CI
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [ $default-branch ]
|
||||
pull_request:
|
||||
branches: [ $default-branch ]
|
||||
|
||||
jobs:
|
||||
test:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
strategy:
|
||||
matrix:
|
||||
ruby-version: [2.7.x, 2.6.x, 2.5.x]
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- name: Set up Ruby ${{ matrix.ruby-version }}
|
||||
# To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
|
||||
# change this to (see https://github.com/ruby/setup-ruby#versioning):
|
||||
# uses: ruby/setup-ruby@v1
|
||||
uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0
|
||||
with:
|
||||
ruby-version: ${{ matrix.ruby-version }}
|
||||
- name: Install dependencies
|
||||
run: bundle install
|
||||
- name: Run tests
|
||||
run: bundle exec rake
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Installing dependencies with Bundler
|
||||
|
||||
The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- run: bundle install
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### Abhängigkeiten „cachen“ (zwischenspeichern)
|
||||
|
||||
The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs.
|
||||
|
||||
To enable caching, set the following.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
bundler-cache: true
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
|
||||
|
||||
**Caching without setup-ruby**
|
||||
|
||||
For greater control over caching, you can use the `actions/cache` Action directly. Weitere Informationen findest Du unter „[Abhängigkeiten im Cache zwischenspeichern, um Deinen Workflow zu beschleunigen](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)“.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: actions/cache@v2
|
||||
with:
|
||||
path: vendor/bundle
|
||||
key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
|
||||
restore-keys: |
|
||||
${{ runner.os }}-gems-
|
||||
- name: Bundle install
|
||||
run: |
|
||||
bundle config path vendor/bundle
|
||||
bundle install --jobs 4 --retry 3
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: actions/cache@v2
|
||||
with:
|
||||
path: vendor/bundle
|
||||
key: bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }}
|
||||
restore-keys: |
|
||||
bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-
|
||||
- name: Bundle install
|
||||
run: |
|
||||
bundle config path vendor/bundle
|
||||
bundle install --jobs 4 --retry 3
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Matrix testing your code
|
||||
|
||||
The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
name: Matrix Testing
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [ $default-branch ]
|
||||
pull_request:
|
||||
branches: [ $default-branch ]
|
||||
|
||||
jobs:
|
||||
test:
|
||||
runs-on: ${{ matrix.os }}-latest
|
||||
strategy:
|
||||
fail-fast: false
|
||||
matrix:
|
||||
os: [ubuntu, macos]
|
||||
ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
|
||||
continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: ${{ matrix.ruby }}
|
||||
- run: bundle install
|
||||
- run: bundle exec rake
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Linting your code
|
||||
|
||||
The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
name: Linting
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
test:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- run: bundle install
|
||||
- name: Rubocop
|
||||
run: rubocop
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Publishing Gems
|
||||
|
||||
You can configure your workflow to publish your Ruby 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 `GitHub Package Registry` and `RubyGems`.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
name: Ruby Gem
|
||||
|
||||
on:
|
||||
# Manually publish
|
||||
workflow_dispatch:
|
||||
# Alternatively, publish whenever changes are merged to the default branch.
|
||||
push:
|
||||
branches: [ $default-branch ]
|
||||
pull_request:
|
||||
branches: [ $default-branch ]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
name: Build + Publish
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- name: Set up Ruby 2.6
|
||||
uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- run: bundle install
|
||||
|
||||
- name: Publish to GPR
|
||||
run: |
|
||||
mkdir -p $HOME/.gem
|
||||
touch $HOME/.gem/credentials
|
||||
chmod 0600 $HOME/.gem/credentials
|
||||
printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
|
||||
gem build *.gemspec
|
||||
gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
|
||||
env:
|
||||
GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
|
||||
OWNER: ${{ github.repository_owner }}
|
||||
|
||||
- name: Publish to RubyGems
|
||||
run: |
|
||||
mkdir -p $HOME/.gem
|
||||
touch $HOME/.gem/credentials
|
||||
chmod 0600 $HOME/.gem/credentials
|
||||
printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
|
||||
gem build *.gemspec
|
||||
gem push *.gem
|
||||
env:
|
||||
GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@@ -31,6 +31,7 @@ You can use {% data variables.product.prodname_actions %} to create custom conti
|
||||
{% link_in_list /building-and-testing-nodejs %}
|
||||
{% link_in_list /building-and-testing-powershell %}
|
||||
{% link_in_list /building-and-testing-python %}
|
||||
{% link_in_list /building-and-testing-ruby %}
|
||||
{% link_in_list /building-and-testing-java-with-maven %}
|
||||
{% link_in_list /building-and-testing-java-with-gradle %}
|
||||
{% link_in_list /building-and-testing-java-with-ant %}
|
||||
|
||||
@@ -8,6 +8,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
authors:
|
||||
- GitHub
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -11,6 +11,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
authors:
|
||||
- GitHub
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -7,31 +7,40 @@ introLinks:
|
||||
reference: /actions/reference
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /actions/guides/setting-up-continuous-integration-using-workflow-templates
|
||||
- /actions/learn-github-actions
|
||||
- /actions/guides/about-continuous-integration
|
||||
- /actions/guides/about-packaging-with-github-actions
|
||||
gettingStarted:
|
||||
- /actions/managing-workflow-runs
|
||||
- /actions/hosting-your-own-runners
|
||||
guideCards:
|
||||
- /actions/guides/setting-up-continuous-integration-using-workflow-templates
|
||||
- /actions/guides/publishing-nodejs-packages
|
||||
- /actions/guides/building-and-testing-powershell
|
||||
popular:
|
||||
- /actions/reference/workflow-syntax-for-github-actions
|
||||
- /actions/reference/events-that-trigger-workflows
|
||||
- /actions/learn-github-actions
|
||||
- /actions/reference/context-and-expression-syntax-for-github-actions
|
||||
- /actions/reference/workflow-commands-for-github-actions
|
||||
- /actions/reference/environment-variables
|
||||
changelog:
|
||||
-
|
||||
title: Removing set-env and add-path commands on November 16
|
||||
date: '2020-11-09'
|
||||
href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
|
||||
-
|
||||
title: 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/
|
||||
-
|
||||
title: Ability to change retention days for artifacts and logs
|
||||
date: '2020-10-08'
|
||||
href: https://github.blog/changelog/2020-10-08-github-actions-ability-to-change-retention-days-for-artifacts-and-logs
|
||||
-
|
||||
title: Deprecating set-env and add-path commands
|
||||
date: '2020-10-01'
|
||||
href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands
|
||||
-
|
||||
title: Fine-tune access to external actions
|
||||
date: '2020-10-01'
|
||||
href: https://github.blog/changelog/2020-10-01-github-actions-fine-tune-access-to-external-actions
|
||||
redirect_from:
|
||||
- /articles/automating-your-workflow-with-github-actions/
|
||||
- /articles/customizing-your-project-with-github-actions/
|
||||
@@ -54,107 +63,26 @@ versions:
|
||||
<!-- {% link_with_intro /reference %} -->
|
||||
|
||||
<!-- Code examples -->
|
||||
{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
|
||||
{% if actionsCodeExamples %}
|
||||
<div class="my-6 pt-6">
|
||||
<h2 class="mb-2">More guides</h2>
|
||||
<h2 class="mb-2 font-mktg h1">Code examples</h2>
|
||||
|
||||
<div class="d-flex flex-wrap gutter">
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-nodejs">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Node.js</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Node.js application.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">JavaScript/TypeScript</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-nodejs</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-python">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Python</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Python application.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">Python</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-python</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-java-with-maven">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Java with Maven</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Java project with Maven.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">Java</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-java-with-maven</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-java-with-gradle">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Java with Gradle</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Java project with Gradle.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">Java</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-java-with-gradle</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-java-with-ant">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Java with Ant</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Java project with Ant.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">Java</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-java-with-ant</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/publishing-nodejs-packages">
|
||||
<div class="p-4">
|
||||
<h4>Publishing Node.js packages</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to push your Node.js package to GitHub Packages or npm.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">JavaScript/TypeScript</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/publishing-nodejs-packages</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="pr-lg-3 mb-5 mt-3">
|
||||
<input class="js-code-example-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="Search code examples" type="search" autocomplete="off" aria-label="Search code examples"/>
|
||||
</div>
|
||||
|
||||
<a href="/actions/guides" class="btn btn-outline mt-4">Show all guides {% octicon "arrow-right" %}</a>
|
||||
<div class="d-flex flex-wrap gutter">
|
||||
{% render 'code-example-card' for actionsCodeExamples as example %}
|
||||
</div>
|
||||
|
||||
<button class="js-code-example-show-more btn btn-outline float-right">Show more {% octicon "arrow-right" %}</button>
|
||||
|
||||
<div class="js-code-example-no-results d-none py-4 text-center text-gray font-mktg">
|
||||
<div class="mb-3">{% octicon "search" width="24" %}</div>
|
||||
<h3 class="text-normal">Sorry, there is no result for <strong class="js-code-example-filter-value"></strong></h3>
|
||||
<p class="my-3 f4">It looks like we don't have an example that fits your filter.<br>Try another filter or add your code example</p>
|
||||
<a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">Learn how to add a code example {% octicon "arrow-right" %}</a>
|
||||
</div>
|
||||
</div>
|
||||
{% endif %}
|
||||
|
||||
@@ -42,7 +42,7 @@ A job is a set of steps that execute on the same runner. By default, a workflow
|
||||
|
||||
#### Steps
|
||||
|
||||
A step is an individual task that can run commands (known as _actions_). Each step in a job executes on the same runner, allowing the actions in that job to share data with each other.
|
||||
A step is an individual task that can run commands in a job. A step can be either an _action_ or a shell command. Each step in a job executes on the same runner, allowing the actions in that job to share data with each other.
|
||||
|
||||
#### Actions
|
||||
|
||||
@@ -50,7 +50,7 @@ _Actions_ are standalone commands that are combined into _steps_ to create a _jo
|
||||
|
||||
#### Runners
|
||||
|
||||
A runner is a server that has the {% data variables.product.prodname_actions %} runner application installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. For {% data variables.product.prodname_dotcom %}-hosted runners, each job in a workflow runs in a fresh virtual environment.
|
||||
A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. You can use a runner hosted by {% data variables.product.prodname_dotcom %}, or you can host your own. A runner listens for available jobs, runs one job at a time, and reports the progress, logs, and results back to {% data variables.product.prodname_dotcom %}. For {% data variables.product.prodname_dotcom %}-hosted runners, each job in a workflow runs in a fresh virtual environment.
|
||||
|
||||
{% data variables.product.prodname_dotcom %}-hosted runners are based on Ubuntu Linux, Microsoft Windows, and macOS. For information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/virtual-environments-for-github-hosted-runners)." If you need a different operating system or require a specific hardware configuration, you can host your own runners. For information on self-hosted runners, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
|
||||
|
||||
@@ -197,7 +197,7 @@ To help you understand how YAML syntax is used to create a workflow file, this s
|
||||
|
||||
#### Visualizing the workflow file
|
||||
|
||||
In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action. Steps 1 and 2 use prebuilt community actions. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
|
||||
In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell command. Steps 1 and 2 use prebuilt community actions. Steps 3 and 4 run shell commands directly on the runner. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ versions:
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
{% data reusables.repositories.permissions-statement-read %}
|
||||
{% data reusables.repositories.permissions-statement-write %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
|
||||
@@ -73,3 +73,69 @@ The super-linter workflow you just added runs any time code is pushed to your re
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial
|
||||
- "[Guides](/actions/guides)" for specific uses cases and examples
|
||||
- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action
|
||||
|
||||
<div id="quickstart-treatment" hidden>
|
||||
|
||||
### Introduction
|
||||
|
||||
Printing "Hello, World!" is a great way to explore the basic set up and syntax of a new programming language. In this guide, you'll use GitHub Actions to print "Hello, World!" within your {% data variables.product.prodname_dotcom %} repository's workflow logs. All you need to get started is a {% data variables.product.prodname_dotcom %} repository where you feel comfortable creating and running a sample {% data variables.product.prodname_actions %} workflow. Feel free to create a new repository for this Quickstart, you can use it to test this and future {% data variables.product.prodname_actions %} workflows.
|
||||
|
||||
### Creating your first workflow
|
||||
|
||||
1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `hello-world.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
|
||||
2. Copy the following YAML contents into the `hello-world.yml` file.
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
name: Say hello!
|
||||
|
||||
# GitHub Actions Workflows are automatically triggered by GitHub events
|
||||
on:
|
||||
# For this workflow, we're using the workflow_dispatch event which is triggered when the user clicks Run workflow in the GitHub Actions UI
|
||||
workflow_dispatch:
|
||||
# The workflow_dispatch event accepts optional inputs so you can customize the behavior of the workflow
|
||||
inputs:
|
||||
name:
|
||||
description: 'Person to greet'
|
||||
required: true
|
||||
default: 'World'
|
||||
# When the event is triggered, GitHub Actions will run the jobs indicated
|
||||
jobs:
|
||||
say_hello:
|
||||
# Uses a ubuntu-lates runner to complete the requested steps
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- run: |
|
||||
echo "Hello ${{ github.event.inputs.name }}!"
|
||||
```
|
||||
{% endraw %}
|
||||
3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
|
||||
|
||||
4. Once the pull request has been merged, you'll be ready to move on to "Trigger your workflow".
|
||||
|
||||
### Trigger your workflow
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
1. In the left sidebar, click the workfow you want to run.
|
||||
|
||||
1. On the right, click the **Run workflow** drop-down and click **Run workflow**. Optionally, you can enter a custom message into the "Person to greet" input before running the workflow.
|
||||
|
||||
1. The workflow run will appear at the top of the list of "Say hello!" workflow runs. Click "Say hello!" to see the result of the workflow run.
|
||||
|
||||
1. In the left sidebar, click the "say_hello" job.
|
||||
|
||||
1. In the workflow logs, expand the 'Run echo "Hello World!"' section.
|
||||
|
||||
|
||||
### More starter workflows
|
||||
|
||||
{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}.
|
||||
|
||||
### Next steps
|
||||
|
||||
The hello-world workflow you just added is a simple example of a manually triggered workflow. This is only the beginning of what you can do with {% data variables.product.prodname_actions %}. Your repository can contain multiple workflows that trigger different jobs based on different events. {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial
|
||||
- "[Guides](/actions/guides)" for specific uses cases and examples
|
||||
|
||||
</div>
|
||||
|
||||
@@ -327,6 +327,7 @@ The `issue_comment` event occurs for comments on both issues and pull requests.
|
||||
|
||||
For example, you can choose to run the `pr_commented` job when comment events occur in a pull request, and the `issue_commented` job when comment events occur in an issue.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
on: issue_comment
|
||||
|
||||
@@ -349,6 +350,7 @@ jobs:
|
||||
- run: |
|
||||
echo "Comment on issue #${{ github.event.issue.number }}"
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### `Issues (Lieferungen)`
|
||||
|
||||
@@ -540,7 +542,7 @@ Führt Deinen Workflow aus, wenn das Ereignis `pull_request_review` eintritt. {%
|
||||
|
||||
{% data reusables.developer-site.limit_workflow_to_activity_types %}
|
||||
|
||||
Du kannst einen Workflow beispielsweise ausführen, wenn ein Pull-Request-Review bearbeitet (`edited`) oder verworfen (`dismissed`) wurde.
|
||||
Sie können einen Workflow beispielsweise ausführen, wenn ein Pull-Request-Review bearbeitet (`edited`) oder verworfen (`dismissed`) wurde.
|
||||
|
||||
```yaml
|
||||
on:
|
||||
@@ -560,7 +562,7 @@ Führt den Workflow aus, wenn ein Kommentar zum vereinheitlichten Diff für eine
|
||||
|
||||
{% data reusables.developer-site.limit_workflow_to_activity_types %}
|
||||
|
||||
Du kannst einen Workflow beispielsweise ausführen, wenn ein Pull-Request-Review-Kommentar erstellt (`created`) oder gelöscht (`deleted`) wurde.
|
||||
Sie können einen Workflow beispielsweise ausführen, wenn ein Pull-Request-Review-Kommentar erstellt (`created`) oder gelöscht (`deleted`) wurde.
|
||||
|
||||
```yaml
|
||||
on:
|
||||
|
||||
@@ -31,7 +31,7 @@ Du kannst in einem Workflow für jeden Job die Art des Runners festlegen. Jeder
|
||||
|
||||
{% data variables.product.prodname_dotcom %} betreibt Linux- und Windows-Runner auf den virtuellen Maschinen nach Standard_DS2_v2 in Microsoft Azure, auf denen die Runner-Anwendung der {% data variables.product.prodname_actions %} installiert ist. Die Runner-Anwendung auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern ist eine Fork-Kopie des Azure-Pipelines-Agenten. Bei Azure werden eingehende ICMP-Pakete werden für alle virtuellen Maschinen blockiert, so dass die Befehle ping und traceroute möglicherweise nicht funktionieren. Weitere Informationen zu den Ressourcen der Standard_DS2_v2-Maschinen findest Du unter „[Serien Dv2 und DSv2](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)“ in der Dokumentation zu Microsoft Azure.
|
||||
|
||||
{% data variables.product.prodname_dotcom %} verwendet [MacStadium](https://www.macstadium.com/), um die virtuellen macOS-Runner zu betreiben.
|
||||
{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud.
|
||||
|
||||
#### Administrative Rechte von {% data variables.product.prodname_dotcom %}-gehosteten Runnern
|
||||
|
||||
|
||||
@@ -446,7 +446,7 @@ steps:
|
||||
uses: monacorp/action-name@main
|
||||
- name: My backup step
|
||||
if: {% raw %}${{ failure() }}{% endraw %}
|
||||
uses: actions/heroku@master
|
||||
uses: actions/heroku@1.0.0
|
||||
```
|
||||
|
||||
#### **`jobs.<job_id>.steps.name`**
|
||||
@@ -492,7 +492,7 @@ jobs:
|
||||
steps:
|
||||
- name: My first step
|
||||
# Uses the default branch of a public repository
|
||||
uses: actions/heroku@master
|
||||
uses: actions/heroku@1.0.0
|
||||
- name: My second step
|
||||
# Uses a specific version tag of a public repository
|
||||
uses: actions/aws@v2.0.1
|
||||
@@ -659,7 +659,7 @@ Für integrierte Shell-Stichwörter gelten die folgenden Standards, die durch au
|
||||
|
||||
- `cmd`
|
||||
- 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` wird mit dem Errorlevel des zuletzt ausgeführten Programms beendet, und dieser Fehlercode wird an den Runner übergeben. 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.
|
||||
- `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`**
|
||||
|
||||
@@ -718,7 +718,7 @@ steps:
|
||||
entrypoint: /a/different/executable
|
||||
```
|
||||
|
||||
Das Schlüsselwort `entrypoint` ist für Docker Container-Aktionen vorgesehen, kann jedoch auch für JavaScript-Aktionen herangezogen werden, in denen keine Eingaben definiert werden.
|
||||
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`**
|
||||
|
||||
|
||||
@@ -28,16 +28,7 @@ To configure authentication and user provisioning for {% data variables.product.
|
||||
|
||||
{% if currentVersion == "github-ae@latest" %}
|
||||
|
||||
1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on.
|
||||
|
||||
| Value in Azure AD | Value from {% data variables.product.prodname_ghe_managed %}
|
||||
|:---------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Identifier (Entity ID) | `https://<em>YOUR-GITHUB-AE-HOSTNAME</em><code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="left">Reply URL</td>
|
||||
<td align="left"><code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/saml/consume` |
|
||||
| Sign on URL | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/sso</code> |
|
||||
1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs.
|
||||
|
||||
1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant.
|
||||
|
||||
|
||||
@@ -38,6 +38,12 @@ After a user successfully authenticates on your IdP, the user's SAML session for
|
||||
|
||||
{% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
|
||||
|
||||
The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
|
||||
|
||||
| IdP | Weitere Informationen |
|
||||
|:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs |
|
||||
|
||||
During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML Service Provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP.
|
||||
|
||||
| Wert | Other names | Beschreibung | Beispiel |
|
||||
|
||||
@@ -62,7 +62,15 @@ You must have administrative access on your IdP to configure the application for
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "SCIM User Provisioning", select **Require SCIM user provisioning**. 
|
||||
1. Klicke auf **Save** (Speichern). 
|
||||
1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}.
|
||||
1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP.
|
||||
|
||||
The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
|
||||
|
||||
| IdP | Weitere Informationen |
|
||||
|:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs |
|
||||
|
||||
The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}.
|
||||
|
||||
| Wert | Other names | Beschreibung | Beispiel |
|
||||
|:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- |
|
||||
|
||||
@@ -11,7 +11,7 @@ versions:
|
||||
|
||||
### Externen `collectd`-Server einrichten
|
||||
|
||||
Falls Sie noch keinen externen `collectd`-Server eingerichtet haben, müssen Sie dies erledigen, bevor Sie die `collectd`-Weiterleitung auf {% data variables.product.product_location %} aktivieren. Ihr `collectd`-Server muss `collectd` Version 5.x oder höher ausführen.
|
||||
Falls Sie noch keinen externen `collectd`-Server eingerichtet haben, müssen Sie dies erledigen, bevor Sie die `collectd`-Weiterleitung auf {% data variables.product.product_location %} aktivieren. Your `collectd` server must be running `collectd` version 5.x or higher.
|
||||
|
||||
1. Melden Sie sich bei Ihrem `collectd`-Server an.
|
||||
2. Erstellen Sie die `collectd`-Konfigurationsdatei, oder bearbeiten Sie sie so, dass das Netzwerk-Plug-in geladen und in die Server- und Portdirektiven die entsprechenden Werte eingetragen werden. Auf den meisten Distributionen befindet sie sich unter `/etc/collectd/collectd.conf`.
|
||||
|
||||
@@ -21,7 +21,10 @@ For the best experience, we recommend using a dedicated bucket for {% data varia
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
|
||||
**Warnungen:**
|
||||
- It's critical you set the restrictive access policies you want for your storage bucket because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. For more information, see [Setting bucket and object access permissions](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html) in the AWS Documentation.
|
||||
- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
|
||||
- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
title: Managing GitHub Packages for your enterprise
|
||||
shortTitle: GitHub Packages
|
||||
intro: 'You can enable {% data variables.product.prodname_registry %} for your enterprise and manage {% data variables.product.prodname_registry %} settings and allowed packaged types.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/packages
|
||||
|
||||
@@ -36,17 +36,23 @@ Wenn Sie in Ihrem Texteditor Änderungen an Dateien vornehmen und Sie diese loka
|
||||
|
||||
#### Partiellen Commit erstellen
|
||||
|
||||
Wenn eine Datei mehrere Änderungen aufweist, Du aber möchtest, dass nur *einige* dieser Änderungen in einem Commit enthalten sind, kannst Du einen partiellen Commit erstellen. Der Rest Deiner Änderungen bleibt erhalten, sodass Du zusätzliche Änderungen und Commits vornehmen kannst. Dadurch kannst Du separate, aussagekräftige Commits erstellen, beispielsweise kannst Du Änderungen der Zeilenumbrüche in einem Commit vom Code oder von Fließtextänderungen getrennt halten.
|
||||
If one file contains multiple changes, but you only want some of those changes to be included in a commit, you can create a partial commit. Der Rest Deiner Änderungen bleibt erhalten, sodass Du zusätzliche Änderungen und Commits vornehmen kannst. Dadurch kannst Du separate, aussagekräftige Commits erstellen, beispielsweise kannst Du Änderungen der Zeilenumbrüche in einem Commit vom Code oder von Fließtextänderungen getrennt halten.
|
||||
|
||||
Wenn Du den Diff der Datei überprüfst, werden die Zeilen, die in den Commit aufgenommen werden, blau hervorgehoben. Um die Änderung auszuschließen, klickst Du auf die geänderte Zeile, damit das Blau verschwindet.
|
||||
{% note %}
|
||||
|
||||
|
||||
**Note:** Split diff displays are currently in beta and subject to change.
|
||||
|
||||
#### Änderungen verwerfen
|
||||
{% endnote %}
|
||||
|
||||
Du kannst alle nicht per Commit übertragenen Änderungen in einer einzelnen Datei, in einer Gruppe von Dateien oder alle Änderungen in allen Dateien seit dem letzten Commit verwerfen.
|
||||
1. To choose how your changes are displayed, in the top-right corner of the changed file, use {% octicon "gear" aria-label="The Gear icon" %} to select **Unified** or **Split**. 
|
||||
2. To exclude changed lines from your commit, click one or more changed lines so the blue disappears. The lines that are still highlighted in blue will be included in the commit. 
|
||||
|
||||
{% mac %}
|
||||
### 3. Änderungen verwerfen
|
||||
If you have uncommitted changes that you don't want to keep, you can discard the changes. This will remove the changes from the files on your computer. You can discard all uncommitted changes in one or more files, or you can discard specific lines you added.
|
||||
|
||||
Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied.
|
||||
|
||||
#### Discarding changes in one or more files
|
||||
|
||||
{% data reusables.desktop.select-discard-files %}
|
||||
{% data reusables.desktop.click-discard-files %}
|
||||
@@ -54,32 +60,27 @@ Du kannst alle nicht per Commit übertragenen Änderungen in einer einzelnen Dat
|
||||
{% data reusables.desktop.confirm-discard-files %}
|
||||
|
||||
|
||||
{% tip %}
|
||||
#### Discarding changes in one or more lines
|
||||
You can discard one or more changed lines that are uncommitted.
|
||||
|
||||
**Tipp:** Die von Dir verworfenen Änderungen werden unter „Trash“ (Papierkorb) in einer Datei mit entsprechender Datumsangabe gespeichert. Du kannst diese wiederherstellen, bis der Papierkorb geleert wird.
|
||||
{% note %}
|
||||
|
||||
{% endtip %}
|
||||
**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines.
|
||||
|
||||
{% endmac %}
|
||||
{% endnote %}
|
||||
|
||||
{% windows %}
|
||||
To discard one added line, in the list of changed lines, right click on the line you want to discard and select **Discard added line**.
|
||||
|
||||
{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %}
|
||||
|
||||
{% data reusables.desktop.confirm-discard-files %}
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
To discard a group of changed lines, right click the vertical bar to the right of the line numbers for the lines you want to discard, then select **Discard added lines**.
|
||||
|
||||
**Tipp:** Die von Dir verworfenen Dateien werden im „Recycle Bin“ (Papierkorb) in einer Datei gespeichert. Du kannst diese wiederherstellen, bis der Papierkorb geleert wird.
|
||||
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% endwindows %}
|
||||
### 4. Eine Commit-Mitteilung schreiben und Deine Änderungen per Push übertragen
|
||||
|
||||
### 3. Eine Commit-Mitteilung schreiben und Deine Änderungen per Push übertragen
|
||||
|
||||
Sobald Du mit den Änderungen zufrieden bist, die Du in Deinen Commit aufnehmen möchtest, schreibest Du Deine Commit-Mitteilung, und überträgst Deine Änderungen per Push. Wenn Du an einem Commit mitgewirkt hast, kannst Du einen Commit auch mehr als einem Autor zuweisen.
|
||||
Sobald Sie mit den Änderungen zufrieden sind, die Sie in Ihren Commit aufnehmen möchten, schreiben Sie Ihre Commit-Mitteilung, und übertragen Sie Ihre Änderungen per Push-Vorgang. Wenn Sie an einem Commit mitgewirkt haben, können Sie einen Commit auch mehr als einem Autor zuweisen.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -34,8 +34,6 @@ Different server-to-server request rate limits apply to {% data variables.produc
|
||||
|
||||
### User-to-server requests
|
||||
|
||||
{% data reusables.apps.deprecating_password_auth %}
|
||||
|
||||
{% data variables.product.prodname_github_app %}s can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
@@ -52,7 +50,7 @@ User-to-server requests are rate limited at 5,000 requests per hour and per auth
|
||||
|
||||
#### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits
|
||||
|
||||
When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user.
|
||||
When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -82,6 +82,32 @@ See [our guide on Git automation with tokens][git-automation].
|
||||
7. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository.
|
||||
8. Click **Add key**.
|
||||
|
||||
##### Using multiple repositories on one server
|
||||
|
||||
If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.
|
||||
|
||||
In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. Ein Beispiel:
|
||||
|
||||
```bash
|
||||
Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0
|
||||
Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}
|
||||
IdentityFile=/home/user/.ssh/repo-0_deploy_key
|
||||
|
||||
Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1
|
||||
Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}
|
||||
IdentityFile=/home/user/.ssh/repo-1_deploy_key
|
||||
```
|
||||
|
||||
* `Host {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias.
|
||||
* `Hostname {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias.
|
||||
* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias.
|
||||
|
||||
You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. Ein Beispiel:
|
||||
|
||||
```bash
|
||||
$ git clone git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git
|
||||
```
|
||||
|
||||
### Machine users
|
||||
|
||||
If your server needs to access multiple repositories, you can create a new {% data variables.product.product_name %} account and attach an SSH key that will be used exclusively for automation. Since this {% data variables.product.product_name %} account won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team).
|
||||
|
||||
@@ -79,7 +79,7 @@ Content-Length: 0123
|
||||
]
|
||||
```
|
||||
|
||||
The message body is a JSON array that contains one or more objects with the following contents. When multiple matches are found, {% data variables.product.prodname_dotcom %} may send a single message with more than one secret match.
|
||||
The message body is a JSON array that contains one or more objects with the following contents. When multiple matches are found, {% data variables.product.prodname_dotcom %} may send a single message with more than one secret match. Your endpoint should be able to handle requests with a large number of matches without timing out.
|
||||
|
||||
* **Token**: The value of the secret match.
|
||||
* **Type**: The unique name you provided to identify your regular expression.
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Über „secret scanning" (Durchsuchen nach Geheimnissen)
|
||||
intro: '{% data variables.product.product_name %} durchsucht Repositorys nach bekannten Geheimnis-Typen, um die betrügerische Verwendung von Geheimnissen zu verhindern, die versehentlich freigegeben wurden.'
|
||||
product: '{% data reusables.gated-features.secret-scanning %}'
|
||||
redirect_from:
|
||||
- /github/administering-a-repository/about-token-scanning
|
||||
- /articles/about-token-scanning
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: '„Secret scanning" (Durchsuchung nach Geheimnissen) für private Repositorys konfigurieren'
|
||||
intro: 'Du kannst konfigurieren, wie {% data variables.product.product_name %} Deine privaten Repositories nach Geheimnissen durchsucht.'
|
||||
product: '{% data reusables.gated-features.secret-scanning %}'
|
||||
permissions: 'Personen mit Administratorberechtigungen für ein privates Repository können {% data variables.product.prodname_secret_scanning %} für das Repository aktivieren.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Warnungen von „secret scanning" (Durchsuchen nach Geheimnissen) verwalten
|
||||
intro: Du kannst Warnungen für Geheimnisse, welche in Deinem Repository geprüft wurden, anschauen und schließen.
|
||||
product: '{% data reusables.gated-features.secret-scanning %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
@@ -31,7 +31,7 @@ Weitere Informationen findest Du unter „[Deine Commit-E-Mail-Adresse festlegen
|
||||
|
||||
### Commits mit Co-Autor mit {% data variables.product.prodname_desktop %} erstellen
|
||||
|
||||
Sie können mit {% data variables.product.prodname_desktop %} einen Commit mit einem Co-Autor erstellen. Weitere Informationen findest Du unter „[Commit-Mitteilung schreiben und Deine Änderungen via Push übertragen](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)“ und „[{% data variables.product.prodname_desktop %}](https://desktop.github.com)“.
|
||||
Sie können mit {% data variables.product.prodname_desktop %} einen Commit mit einem Co-Autor erstellen. Weitere Informationen findest Du unter „[Commit-Mitteilung schreiben und Deine Änderungen via Push übertragen](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)“ und „[{% data variables.product.prodname_desktop %}](https://desktop.github.com)“.
|
||||
|
||||
|
||||
|
||||
@@ -74,4 +74,4 @@ Der neue Commit samt Mitteilung wird auf {% data variables.product.product_locat
|
||||
- „[Eine Zusammenfassung der Repository-Aktivitäten anzeigen](/articles/viewing-a-summary-of-repository-activity)“
|
||||
- „[Die Mitarbeiter eines Projekts anzeigen](/articles/viewing-a-projects-contributors)“
|
||||
- „[Eine Commit-Mitteilung ändern](/articles/changing-a-commit-message)“
|
||||
- „[Änderungen an Deinem Projekt freigeben und überprüfen](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)“ in der {% data variables.product.prodname_desktop %}-Dokumentation
|
||||
- „[Änderungen an Deinem Projekt freigeben und überprüfen](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)“ in der {% data variables.product.prodname_desktop %}-Dokumentation
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using Codespaces in Visual Studio Code
|
||||
intro: 'Du kannst über {% data variables.product.prodname_vscode %} direkt in Deinem Codespace entwickeln, indem Du die {% data variables.product.prodname_vs_codespaces %}-Erweiterung mit Deinem Konto auf {% data variables.product.product_name %} verbindest.'
|
||||
intro: 'Du kannst über {% data variables.product.prodname_vscode %} direkt in Deinem Codespace entwickeln, indem Du die {% data variables.product.prodname_github_codespaces %}-Erweiterung mit Deinem Konto auf {% data variables.product.product_name %} verbindest.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
redirect_from:
|
||||
- /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
|
||||
@@ -12,17 +12,16 @@ versions:
|
||||
|
||||
### Vorrausetzungen
|
||||
|
||||
Bevor Du über {% data variables.product.prodname_vscode %} direkt in einem Codespace entwickeln kannst, musst Du die {% data variables.product.prodname_vs_codespaces %}-Erweiterung so konfigurieren, dass sie sich zu Deinem {% data variables.product.product_name %}-Konto verbindet.
|
||||
To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must sign into the {% data variables.product.prodname_github_codespaces %} extension. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later.
|
||||
|
||||
1. Du kannst {% data variables.product.prodname_vs %}-Marketplace verwenden, um die [{% data variables.product.prodname_vs_codespaces %}](https://marketplace.visualstudio.com/items?itemName=ms-vsonline.vsonline)-Erweiterung zu installieren. Weitere Informationen findest Du unter „[Marketplace-Erweiterung](https://code.visualstudio.com/docs/editor/extension-gallery)" in der {% data variables.product.prodname_vscode %}-Dokumentation.
|
||||
2. Klicke in der linken Seitenleiste in {% data variables.product.prodname_vscode %} auf das Symbol „Extensions" (Erweiterungen). 
|
||||
3. Klicke unterhalb von {% data variables.product.prodname_vs_codespaces %} auf das Symbol „Manage" (Verwalten), und klicke dann auf **Extension Settings** (Erweiterungseinstellungen). 
|
||||
4. Verwende das Dropdownmenü „Vsonline: Account Provider" (Vsonline: Kontoanbieter) und wähle {% data variables.product.prodname_dotcom %}. 
|
||||
1. Use the
|
||||
|
||||
{% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. Weitere Informationen findest Du unter „[Marketplace-Erweiterung](https://code.visualstudio.com/docs/editor/extension-gallery)" in der {% data variables.product.prodname_vscode %}-Dokumentation.
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
6. Wenn {% data variables.product.prodname_codespaces %} in der Kopfzeile noch nicht ausgewählt ist, klicke auf **{% data variables.product.prodname_codespaces %}**. 
|
||||
7. Klicke auf **Sign in to view {% data variables.product.prodname_codespaces %}...** (Anmelden zur Anzeige von...). 
|
||||
8. Um {% data variables.product.prodname_vscode %} für den Zugriff zu Deinem Konto auf {% data variables.product.product_name %} zu autorisieren, klicke auf **Allow** (Genehmigen).
|
||||
9. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen.
|
||||
2. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**. 
|
||||
3. Klicke auf **Sign in to view {% data variables.product.prodname_codespaces %}...** (Anmelden zur Anzeige von...). 
|
||||
4. Um {% data variables.product.prodname_vscode %} für den Zugriff zu Deinem Konto auf {% data variables.product.product_name %} zu autorisieren, klicke auf **Allow** (Genehmigen).
|
||||
5. Melde Dich bei {% data variables.product.product_name %} an, um die Erweiterung zu genehmigen.
|
||||
|
||||
### Creating a codespace in {% data variables.product.prodname_vscode %}
|
||||
|
||||
@@ -31,8 +30,8 @@ After you connect your {% data variables.product.product_name %} account to the
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
2. Click the Add icon, then click **Create New Codespace**. 
|
||||
3. Type, then click the repository's name you want to develop in. 
|
||||
4. Click the branch you want to develop in. 
|
||||
|
||||
4. Click the branch you want to develop on. 
|
||||
5. Click the instance type you want to develop in. 
|
||||
### Einen Codespace in {% data variables.product.prodname_vscode %} eröffnen
|
||||
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
|
||||
@@ -12,26 +12,25 @@ versions:
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
### About {% data variables.product.prodname_code_scanning %}
|
||||
### Informationen zu {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
{% data reusables.code-scanning.about-code-scanning %}
|
||||
With {% data variables.product.prodname_code_scanning %}, developers can quickly and automatically analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors.
|
||||
|
||||
You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push.
|
||||
|
||||
If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
|
||||
If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. Nachdem Du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt {% data variables.product.prodname_dotcom %} die Meldung. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
|
||||
|
||||
To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API.
|
||||
For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/v3/code-scanning)."
|
||||
You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation.
|
||||
|
||||
To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)."
|
||||
To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning)."
|
||||
|
||||
### About {% data variables.product.prodname_codeql %}
|
||||
### Informationen zu {% data variables.product.prodname_codeql %}
|
||||
|
||||
You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
|
||||
{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
|
||||
|
||||
{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website.
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
|
||||
For more information about API endpoints for {% data variables.product.prodname_code_scanning %}, see "[{% data variables.product.prodname_code_scanning_capc %}](http://developer.github.com/v3/code-scanning)."
|
||||
|
||||
{% data reusables.code-scanning.supported-languages %}
|
||||
|
||||
@@ -39,9 +38,9 @@ You can view and contribute to the queries for {% data variables.product.prodnam
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
### About billing for {% data variables.product.prodname_code_scanning %}
|
||||
### Informationen zur Abrechnung für {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."
|
||||
{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. Weitere Informationen findest Du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).“
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -53,7 +52,7 @@ You can view and contribute to the queries for {% data variables.product.prodnam
|
||||
|
||||
{% data reusables.code-scanning.get-started-uploading-third-party-data %}
|
||||
|
||||
### Further reading
|
||||
### Weiterführende Informationen
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
|
||||
|
||||
@@ -94,7 +94,7 @@ If the `autobuild` command can't build your code, you can run the build steps yo
|
||||
|
||||
By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command.
|
||||
|
||||
Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-an-alert)."
|
||||
Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
|
||||
|
||||
### {% data variables.product.prodname_codeql_runner %} command reference
|
||||
|
||||
|
||||
@@ -17,29 +17,25 @@ versions:
|
||||
|
||||
### Options for enabling {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
You decide how you generate {% data variables.product.prodname_code_scanning %} alerts, and which tools you use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. For more information, see "[About {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)."
|
||||
You decide how you generate {% data variables.product.prodname_code_scanning %} alerts, and which tools you use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. Weitere Informationen findest Du unter „[ Über {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)."
|
||||
|
||||
{% data reusables.code-scanning.enabling-options %}
|
||||
|
||||
### Enabling {% data variables.product.prodname_code_scanning %} using actions
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. Weitere Informationen finden Sie unter „[Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions).“{% endif %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
3. To the right of "{% data variables.product.prodname_code_scanning_capc %}", click **Set up {% data variables.product.prodname_code_scanning %}**.
|
||||
|
||||
4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow.
|
||||
|
||||
3. To the right of "{% data variables.product.prodname_code_scanning_capc %}", click **Set up {% data variables.product.prodname_code_scanning %}**. 
|
||||
4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. 
|
||||
5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
|
||||
|
||||
Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
|
||||
|
||||
For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
|
||||
6. Use the **Start commit** drop-down, and type a commit message.
|
||||
|
||||
7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request.
|
||||
|
||||
6. Use the **Start commit** drop-down, and type a commit message. 
|
||||
7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request. 
|
||||
8. Click **Commit new file** or **Propose new file**.
|
||||
|
||||
In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence.
|
||||
@@ -62,7 +58,7 @@ After enabling {% data variables.product.prodname_code_scanning %} for your repo
|
||||
|
||||
1. Review the logging output from the actions in this workflow as they run.
|
||||
|
||||
1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-an-alert)."
|
||||
1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -106,12 +102,12 @@ There are other situations where there may be no analysis for the latest commit
|
||||
|
||||
Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}.
|
||||
|
||||
### Next steps
|
||||
### Nächste Schritte:
|
||||
|
||||
After enabling {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can:
|
||||
|
||||
- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)."
|
||||
- View any alerts generated for a pull request submitted after you enabled {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
- Set up notifications for completed runs. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)."
|
||||
- Set up notifications for completed runs. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)."
|
||||
- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)."
|
||||
- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)."
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Managing code scanning alerts for your repository
|
||||
shortTitle: Warnungen verwalten
|
||||
intro: 'You can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
|
||||
intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
|
||||
versions:
|
||||
@@ -30,9 +30,11 @@ If you enable {% data variables.product.prodname_code_scanning %} using {% data
|
||||
|
||||
When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
|
||||
|
||||
### Viewing an alert
|
||||
### Viewing the alerts for a repository
|
||||
|
||||
Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} alerts on pull requests. However, you need write permission to view a summary of alerts for repository on the **Security** tab. By default, alerts are shown for the default branch.
|
||||
Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
|
||||
You need write permission to view a summary of all the alerts for a repository on the **Security** tab. By default, alerts are shown for the default branch.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
@@ -45,7 +47,7 @@ Anyone with read permission for a repository can see {% data variables.product.p
|
||||
|
||||
Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
|
||||
If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing an alert](#viewing-an-alert)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
|
||||
If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
|
||||
|
||||
Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Triaging code scanning alerts in pull requests
|
||||
shortTitle: Triaging alerts in pull requests
|
||||
intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
permissions: 'If you have write permission to a repository, you can resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.'
|
||||
permissions: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
@@ -31,9 +31,9 @@ When you look at the **Files changed** tab for a pull request, you see annotatio
|
||||
|
||||
|
||||
|
||||
Some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)."
|
||||
If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://help.semmle.com/QL/learn-ql/intro-to-data-flow.html)."
|
||||
|
||||
For more information about an alert, click **Show more details** on the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem.
|
||||
To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem.
|
||||
|
||||
In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code.
|
||||
|
||||
@@ -41,11 +41,11 @@ In the detailed view for an alert, some {% data variables.product.prodname_code_
|
||||
|
||||
### {% if currentVersion == "enterprise-server@2.22" %}Resolving{% else %}Fixing{% endif %} an alert on your pull request
|
||||
|
||||
Anyone with write permission for a repository can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on a pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
|
||||
Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
|
||||
|
||||
{% if currentVersion == "enterprise-server@2.22" %}
|
||||
|
||||
If you don't think that an alert needs to be fixed, you can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
|
||||
If you don't think that an alert needs to be fixed, users with write permission can close the alert manually. {% data reusables.code-scanning.close-alert-examples %} The **Close** button is available in annotations and in the alerts view if you have write permission for the repository.
|
||||
|
||||
{% data reusables.code-scanning.false-positive-fix-codeql %}
|
||||
|
||||
@@ -63,4 +63,4 @@ An alternative way of closing an alert is to dismiss it. You can dismiss an aler
|
||||
|
||||
For more information about dismissing alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -66,7 +66,7 @@ For more information, see the workflow extract in "[Automatic build for a compil
|
||||
* Building using a distributed build system external to GitHub Actions, using a daemon process.
|
||||
* {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
|
||||
|
||||
For C# projects using either `dotnet build` or `msbuild` which target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later.
|
||||
For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild` that target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later.
|
||||
|
||||
For example, the following configuration for C# will pass the flag during the first build step.
|
||||
|
||||
|
||||
@@ -21,5 +21,5 @@ Die Produkte und Funktionen von {% data variables.product.product_name %} könne
|
||||
|
||||
Du kannst eine Liste der Funktionen sehen, die in der Beta-Version verfügbar sind, und eine kurze Beschreibung für jede Funktion. Jede Funktion enthält einen Link, um Feedback zu geben.
|
||||
|
||||
1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf Dein Profilfoto und dann auf **Feature preview** (Funktions-Vorschau). 
|
||||
{% data reusables.feature-preview.feature-preview-setting %}
|
||||
2. Klicke optional auf der rechten Seite einer Funktion auf **Aktivieren** oder **Deaktivieren**. 
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Managing secret scanning for your organization
|
||||
intro: 'You can control which repositories in your organization {% data variables.product.product_name %} will scan for secrets.'
|
||||
product: '{% data reusables.gated-features.secret-scanning %}'
|
||||
permissions: 'Organization owners can manage {% data variables.product.prodname_secret_scanning %} for repositories in the organization.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
|
||||
@@ -43,74 +43,77 @@ Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben
|
||||
|
||||
### Repository-Zugriff der einzelnen Berechtigungsebenen
|
||||
|
||||
| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten |
|
||||
|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|
|
||||
| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** |
|
||||
| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** |
|
||||
| Bearbeiten und Löschen eigener Kommentare | **X** | **X** | **X** | **X** | **X** |
|
||||
| Eröffnen von Issues | **X** | **X** | **X** | **X** | **X** |
|
||||
| Schließen der selbst eröffneten Issues | **X** | **X** | **X** | **X** | **X** |
|
||||
| Erneutes Eröffnen von selbst geschlossenen Issues | **X** | **X** | **X** | **X** | **X** |
|
||||
| Sich-Selbst-Zuweisen von Issues | **X** | **X** | **X** | **X** | **X** |
|
||||
| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **X** | **X** | **X** | **X** | **X** |
|
||||
| Absenden von Reviews zu Pull Requests | **X** | **X** | **X** | **X** | **X** |
|
||||
| Anzeigen veröffentlichter Releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [GitHub Actions-Workflow-Ausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) ansehen | **X** | **X** | **X** | **X** | **X** |{% endif %}
|
||||
| Bearbeiten von Wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Melden von Missbrauch oder Spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %}
|
||||
| Anwenden von Kennzeichnungen | | **X** | **X** | **X** | **X** |
|
||||
| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |
|
||||
| Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** |
|
||||
| Markieren von [Issues und Pull Requests als Duplikat](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** |
|
||||
| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** |
|
||||
| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **X** | **X** | **X** |
|
||||
| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **X** | **X** | **X** |
|
||||
| [Ausblenden der Kommentare beliebiger Benutzer](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** |
|
||||
| [Blockieren von Unterhaltungen](/articles/locking-conversations) | | | **X** | **X** | **X** |
|
||||
| Übertragen von Issues (siehe „[Issue auf ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“) | | | **X** | **X** | **X** |
|
||||
| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **X** | **X** | **X** |
|
||||
| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
|
||||
| [Einen Pull Request in einen Entwurf umwandeln](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %}
|
||||
| Absenden von Reviews, die sich auf die Merge-Fähigkeit eines Pull Request auswirken | | | **X** | **X** | **X** |
|
||||
| [Anwenden vorgeschlagener Änderungen](/articles/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **X** | **X** | **X** |
|
||||
| Erstellen von [Statuschecks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Erstellen, Bearbeiten, Ausführen, Neuausführen und Abbrechen von [GitHub-Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %}
|
||||
| Erstellen und Bearbeiten von Releases | | | **X** | **X** | **X** |
|
||||
| Anzeigen von Release-Entwürfen | | | **X** | **X** | **X** |
|
||||
| Bearbeiten von Repository-Beschreibungen | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Pakete anzeigen und installieren](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** |
|
||||
| [Pakete veröffentlichen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** |
|
||||
| [Pakete löschen](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %}
|
||||
| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** |
|
||||
| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **X** | **X** |
|
||||
| Aktivieren von Projektboards | | | | **X** | **X** |
|
||||
| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** |
|
||||
| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** |
|
||||
| [An geschützte Branches pushen](/articles/about-protected-branches) | | | | **X** | **X** |
|
||||
| [Erstellen und Bearbeiten sozialer Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Interaktionen in einem Repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) limitieren | | | | **X** | **X** |{% endif %}
|
||||
| Löschen von Issues (siehe „[Issue löschen](/articles/deleting-an-issue)“) | | | | | **X** |
|
||||
| Mergen von Pull Requests in geschützten Branches auch ohne Genehmigungsreviews | | | | | **X** |
|
||||
| [Festlegen der Codeinhaber eines Repositorys](/articles/about-code-owners) | | | | | **X** |
|
||||
| Ein Repository zu einem Team hinzufügen (siehe „[Teamzugriff auf ein Organisations-Repository verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)") | | | | | **X** |
|
||||
| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** |
|
||||
| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** |
|
||||
| Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“) | | | | | **X** |
|
||||
| Ändern der Einstellungen eines Repositorys | | | | | **X** |
|
||||
| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **X** |
|
||||
| Bearbeiten des Standardbranch eines Repositorys | | | | | **X** |
|
||||
| Manage webhooks and deploy keys | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Aktivieren des Abhängigkeitsdiagramms](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) für ein privates Repository | | | | | **X** |
|
||||
| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** |
|
||||
| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |
|
||||
| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) for vulnerable dependencies | | | | | **X** |
|
||||
| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" %}| Create [security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %}
|
||||
| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** |
|
||||
| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** |
|
||||
| [Löschen von Repositorys oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** |
|
||||
| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Anzeigen einer Sponsorenschaltfläche (siehe „[Sponsorenschaltfläche in Ihrem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“) | | | | | **X** |{% endif %}
|
||||
| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |
|
||||
| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten |
|
||||
|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:--------------------------------------------------------------------------------------------------------------------------------------------------:|
|
||||
| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** |
|
||||
| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** |
|
||||
| Bearbeiten und Löschen eigener Kommentare | **X** | **X** | **X** | **X** | **X** |
|
||||
| Eröffnen von Issues | **X** | **X** | **X** | **X** | **X** |
|
||||
| Schließen der selbst eröffneten Issues | **X** | **X** | **X** | **X** | **X** |
|
||||
| Erneutes Eröffnen von selbst geschlossenen Issues | **X** | **X** | **X** | **X** | **X** |
|
||||
| Sich-Selbst-Zuweisen von Issues | **X** | **X** | **X** | **X** | **X** |
|
||||
| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **X** | **X** | **X** | **X** | **X** |
|
||||
| Absenden von Reviews zu Pull Requests | **X** | **X** | **X** | **X** | **X** |
|
||||
| Anzeigen veröffentlichter Releases | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [GitHub Actions-Workflow-Ausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) ansehen | **X** | **X** | **X** | **X** | **X** |{% endif %}
|
||||
| Bearbeiten von Wikis | **X** | **X** | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Melden von Missbrauch oder Spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %}
|
||||
| Anwenden von Kennzeichnungen | | **X** | **X** | **X** | **X** |
|
||||
| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |
|
||||
| Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** |
|
||||
| Markieren von [Issues und Pull Requests als Duplikat](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** |
|
||||
| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** |
|
||||
| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **X** | **X** | **X** |
|
||||
| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **X** | **X** | **X** |
|
||||
| [Ausblenden der Kommentare beliebiger Benutzer](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** |
|
||||
| [Blockieren von Unterhaltungen](/articles/locking-conversations) | | | **X** | **X** | **X** |
|
||||
| Übertragen von Issues (siehe „[Issue auf ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“) | | | **X** | **X** | **X** |
|
||||
| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **X** | **X** | **X** |
|
||||
| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}
|
||||
| [Einen Pull Request in einen Entwurf umwandeln](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %}
|
||||
| Absenden von Reviews, die sich auf die Merge-Fähigkeit eines Pull Request auswirken | | | **X** | **X** | **X** |
|
||||
| [Anwenden vorgeschlagener Änderungen](/articles/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **X** | **X** | **X** |
|
||||
| Erstellen von [Statuschecks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Erstellen, Bearbeiten, Ausführen, Neuausführen und Abbrechen von [GitHub-Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %}
|
||||
| Erstellen und Bearbeiten von Releases | | | **X** | **X** | **X** |
|
||||
| Anzeigen von Release-Entwürfen | | | **X** | **X** | **X** |
|
||||
| Bearbeiten von Repository-Beschreibungen | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Pakete anzeigen und installieren](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** |
|
||||
| [Pakete veröffentlichen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** |
|
||||
| [Pakete löschen](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **X** |{% endif %}
|
||||
| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** |
|
||||
| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **X** | **X** |
|
||||
| Aktivieren von Projektboards | | | | **X** | **X** |
|
||||
| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** |
|
||||
| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** |
|
||||
| [An geschützte Branches pushen](/articles/about-protected-branches) | | | | **X** | **X** |
|
||||
| [Erstellen und Bearbeiten sozialer Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Interaktionen in einem Repository](/github/building-a-strong-community/limiting-interactions-in-your-repository) limitieren | | | | **X** | **X** |{% endif %}
|
||||
| Löschen von Issues (siehe „[Issue löschen](/articles/deleting-an-issue)“) | | | | | **X** |
|
||||
| Mergen von Pull Requests in geschützten Branches auch ohne Genehmigungsreviews | | | | | **X** |
|
||||
| [Festlegen der Codeinhaber eines Repositorys](/articles/about-code-owners) | | | | | **X** |
|
||||
| Ein Repository zu einem Team hinzufügen (siehe „[Teamzugriff auf ein Organisations-Repository verwalten](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)") | | | | | **X** |
|
||||
| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** |
|
||||
| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** |
|
||||
| Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“) | | | | | **X** |
|
||||
| Ändern der Einstellungen eines Repositorys | | | | | **X** |
|
||||
| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **X** |
|
||||
| Bearbeiten des Standardbranch eines Repositorys | | | | | **X** |
|
||||
| Manage webhooks and deploy keys | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [Aktivieren des Abhängigkeitsdiagramms](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) für ein privates Repository | | | | | **X** |
|
||||
| Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** |
|
||||
| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |
|
||||
| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) for vulnerable dependencies | | | | | **X** |
|
||||
| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** |
|
||||
| [Sicherheitshinweise](/github/managing-security-vulnerabilities/about-github-security-advisories) erstellen | | | | | **X** |{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
|
||||
| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** |
|
||||
| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% endif %}
|
||||
| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** |
|
||||
| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** |
|
||||
| [Löschen von Repositorys oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** |
|
||||
| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| Anzeigen einer Sponsorenschaltfläche (siehe „[Sponsorenschaltfläche in Ihrem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“) | | | | | **X** |{% endif %}
|
||||
| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |
|
||||
|
||||
### Weiterführende Informationen
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Reviewing the audit log for your organization
|
||||
intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.'
|
||||
miniTocMaxHeadingLevel: 4
|
||||
redirect_from:
|
||||
- /articles/reviewing-the-audit-log-for-your-organization
|
||||
versions:
|
||||
@@ -11,7 +12,7 @@ versions:
|
||||
|
||||
### Accessing the audit log
|
||||
|
||||
The audit log lists actions performed within the last 90 days. Only owners can access an organization's audit log.
|
||||
The audit log lists events triggered by activities that affect your organization within the last 90 days. Only owners can access an organization's audit log.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
@@ -26,73 +27,110 @@ The audit log lists actions performed within the last 90 days. Only owners can a
|
||||
|
||||
To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories:
|
||||
|
||||
| Category Name | Description
|
||||
| Category name | Description
|
||||
|------------------|-------------------{% if currentVersion == "free-pro-team@latest" %}
|
||||
| `account` | Contains all activities related to your organization account.{% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
| `billing` | Contains all activities related to your organization's billing.{% endif %}
|
||||
| `discussion_post` | Contains all activities related to discussions posted to a team page.
|
||||
| `discussion_post_reply` | Contains all activities related to replies to discussions posted to a team page.
|
||||
| `hook` | Contains all activities related to webhooks.
|
||||
| `integration_installation_request` | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% if currentVersion == "free-pro-team@latest" %}
|
||||
| `marketplace_agreement_signature` | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
| `marketplace_listing` | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
|
||||
| `members_can_create_pages` | Contains all activities related to disabling the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." | {% endif %}
|
||||
| `org` | Contains all activities related to organization membership{% if currentVersion == "free-pro-team@latest" %}
|
||||
| `org_credential_authorization` | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
|
||||
| `organization_label` | Contains all activities related to default labels for repositories in your organization.{% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
| `payment_method` | Contains all activities related to how your organization pays for GitHub.{% endif %}
|
||||
| `profile_picture` | Contains all activities related to your organization's profile picture.
|
||||
| `project` | Contains all activities related to project boards.
|
||||
| `protected_branch` | Contains all activities related to protected branches.
|
||||
| `repo` | Contains all activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %}
|
||||
| `repository_content_analysis` | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).
|
||||
| `repository_dependency_graph` | Contains all activities related to [enabling or disabling the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository).{% endif %}{% if currentVersion != "github-ae@latest" %}
|
||||
| `repository_vulnerability_alert` | Contains all activities related to [{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
| `sponsors` | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
|
||||
| `team` | Contains all activities related to teams in your organization.{% endif %}
|
||||
| `team_discussions` | Contains activities related to managing team discussions for an organization.
|
||||
| [`account`](#account-category-actions) | Contains all activities related to your organization account.
|
||||
| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.
|
||||
| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot %} alerts in new repositories created in the organization.
|
||||
| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
|
||||
| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.
|
||||
| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %}
|
||||
| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page.
|
||||
| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.
|
||||
| [`hook`](#hook-category-actions) | Contains all activities related to webhooks.
|
||||
| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |
|
||||
| [`issue`](#issue-category-actions) | Contains activities related to deleting an issue. {% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
|
||||
| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to disabling the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." | {% endif %}
|
||||
| [`org`](#org-category-actions) | Contains activities related to organization membership.{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
|
||||
| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %}
|
||||
| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. {% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %}
|
||||
| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture.
|
||||
| [`project`](#project-category-actions) | Contains all activities related to project boards.
|
||||
| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches.
|
||||
| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% if currentVersion != "github-ae@latest" %}
|
||||
| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% if currentVersion != "github-ae@latest" %}
|
||||
| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. {% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
| [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
|
||||
| [`team`](#team-category-actions) | Contains all activities related to teams in your organization.{% endif %}
|
||||
| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.
|
||||
|
||||
You can search for specific sets of actions using these terms. For example:
|
||||
|
||||
* `action:team` finds all events grouped within the team category.
|
||||
* `-action:hook` excludes all events in the webhook category.
|
||||
|
||||
Each category has a set of associated events that you can filter on. For example:
|
||||
Each category has a set of associated actions that you can filter on. For example:
|
||||
|
||||
* `action:team.create` finds all events where a team was created.
|
||||
* `-action:hook.events_changed` excludes all events where the events on a webhook have been altered.
|
||||
|
||||
This list describes the available categories and associated events:
|
||||
#### Search based on time of action
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}- [The `account` category](#the-account-category)
|
||||
- [The `billing` category](#the-billing-category){% endif %}
|
||||
- [The `discussion_post` category](#the-discussion_post-category)
|
||||
- [The `discussion_post_reply` category](#the-discussion_post_reply-category)
|
||||
- [The `hook` category](#the-hook-category)
|
||||
- [The `integration_installation_request` category](#the-integration_installation_request-category)
|
||||
- [The `issue` category](#the-issue-category){% if currentVersion == "free-pro-team@latest" %}
|
||||
- [The `marketplace_agreement_signature` category](#the-marketplace_agreement_signature-category)
|
||||
- [The `marketplace_listing` category](#the-marketplace_listing-category){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
|
||||
- [The `members_can_create_pages` category](#the-members_can_create_pages-category){% endif %}
|
||||
- [The `org` category](#the-org-category){% if currentVersion == "free-pro-team@latest" %}
|
||||
- [The `org_credential_authorization` category](#the-org_credential_authorization-category){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
|
||||
- [The `organization_label` category](#the-organization_label-category){% endif %}
|
||||
- [The `oauth_application` category](#the-oauth_application-category){% if currentVersion == "free-pro-team@latest" %}
|
||||
- [The `payment_method` category](#the-payment_method-category){% endif %}
|
||||
- [The `profile_picture` category](#the-profile_picture-category)
|
||||
- [The `project` category](#the-project-category)
|
||||
- [The `protected_branch` category](#the-protected_branch-category)
|
||||
- [The `repo` category](#the-repo-category){% if currentVersion == "free-pro-team@latest" %}
|
||||
- [The `repository_content_analysis` category](#the-repository_content_analysis-category)
|
||||
- [The `repository_dependency_graph` category](#the-repository_dependency_graph-category){% endif %}{% if currentVersion != "github-ae@latest" %}
|
||||
- [The `repository_vulnerability_alert` category](#the-repository_vulnerability_alert-category){% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
- [The `sponsors` category](#the-sponsors-category){% endif %}{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
|
||||
- [The `team` category](#the-team-category){% endif %}
|
||||
- [The `team_discussions` category](#the-team_discussions-category)
|
||||
Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
|
||||
|
||||
{% data reusables.search.date_gt_lt %} For example:
|
||||
|
||||
* `created:2014-07-08` finds all events that occurred on July 8th, 2014.
|
||||
* `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014.
|
||||
* `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014.
|
||||
* `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
|
||||
|
||||
The audit log contains data for the past 90 days, but you can use the `created` qualifier to search for events earlier than that.
|
||||
|
||||
#### Search based on location
|
||||
|
||||
Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example:
|
||||
|
||||
* `country:de` finds all events that occurred in Germany.
|
||||
* `country:Mexico` finds all events that occurred in Mexico.
|
||||
* `country:"United States"` all finds events that occurred in the United States.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
### Exporting the audit log
|
||||
|
||||
{% data reusables.audit_log.export-log %}
|
||||
{% data reusables.audit_log.exported-log-keys-and-values %}
|
||||
{% endif %}
|
||||
|
||||
### Using the Audit log API
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The Audit log API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
To ensure a secure IP and maintain compliance for your organization, you can use the Audit log API to keep copies of your audit log data and monitor:
|
||||
* Access to your organization or repository settings.
|
||||
* Changes in permissions.
|
||||
* Added or removed users in an organization, repository, or team.
|
||||
* Users being promoted to admin.
|
||||
* Changes to permissions of a GitHub App.
|
||||
|
||||
The GraphQL response can include data for up to 90 to 120 days.
|
||||
|
||||
For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log](/graphql/reference/interfaces#auditentry/)."
|
||||
|
||||
### Audit log actions
|
||||
|
||||
An overview of some of the most common actions that are recorded as events in the audit log.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
##### The `account` category
|
||||
#### `account` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -101,30 +139,81 @@ This list describes the available categories and associated events:
|
||||
| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/).
|
||||
| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/).
|
||||
|
||||
##### The `billing` category
|
||||
#### `advisory_credit` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)."
|
||||
| `create` | Triggered when the administrator of a security advisory adds someone to the credit section.
|
||||
| `decline` | Triggered when someone declines credit for a security advisory.
|
||||
| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section.
|
||||
|
||||
#### `billing` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method).
|
||||
| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes.
|
||||
|
||||
#### `dependabot_alerts` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
|
||||
| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories.
|
||||
|
||||
#### `dependabot_alerts_new_repos` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
|
||||
| `enable` | Triggered when an organization owner enbles {% data variables.product.prodname_dependabot_alerts %} for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories.
|
||||
|
||||
#### `dependabot_security_updates` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
|
||||
| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories.
|
||||
|
||||
#### `dependabot_security_updates_new_repos` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
|
||||
| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories.
|
||||
|
||||
#### `dependency_graph` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables the dependency graph for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
|
||||
| `enable` | Triggered when an organization owner enables the dependency graph for all existing repositories.
|
||||
|
||||
#### `dependency_graph_new_repos` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables the dependency graph for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
|
||||
| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories.
|
||||
|
||||
{% endif %}
|
||||
|
||||
##### The `discussion_post` category
|
||||
#### `discussion_post` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `update` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment).
|
||||
| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment).
|
||||
|
||||
##### The `discussion_post_reply` category
|
||||
#### `discussion_post_reply` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment).
|
||||
| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment).
|
||||
|
||||
##### The `hook` category
|
||||
#### `hook` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -133,14 +222,14 @@ This list describes the available categories and associated events:
|
||||
| `destroy` | Triggered when an existing hook was removed from a repository.
|
||||
| `events_changed` | Triggered when the events on a hook have been altered.
|
||||
|
||||
##### The `integration_installation_request` category
|
||||
#### `integration_installation_request` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization.
|
||||
| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request.
|
||||
|
||||
##### The `issue` category
|
||||
#### `issue` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -148,13 +237,13 @@ This list describes the available categories and associated events:
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
##### The `marketplace_agreement_signature` category
|
||||
#### `marketplace_agreement_signature` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
|
||||
##### The `marketplace_listing` category
|
||||
#### `marketplace_listing` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -168,7 +257,7 @@ This list describes the available categories and associated events:
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
|
||||
|
||||
##### The `members_can_create_pages` category
|
||||
#### `members_can_create_pages` category actions
|
||||
|
||||
For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)."
|
||||
|
||||
@@ -179,7 +268,7 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
|
||||
{% endif %}
|
||||
|
||||
##### The `org` category
|
||||
#### `org` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------{% if currentVersion == "free-pro-team@latest"%}
|
||||
@@ -222,7 +311,7 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
##### The `org_credential_authorization` category
|
||||
#### `org_credential_authorization` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -233,7 +322,7 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %}
|
||||
##### The `organization_label` category
|
||||
#### `organization_label` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -243,7 +332,7 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
|
||||
{% endif %}
|
||||
|
||||
##### The `oauth_application` category
|
||||
#### `oauth_application` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -255,7 +344,7 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
##### The `payment_method` category
|
||||
#### `payment_method` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -265,12 +354,12 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
|
||||
{% endif %}
|
||||
|
||||
##### The `profile_picture` category
|
||||
#### `profile_picture` category actions
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| update | Triggered when you set or update your organization's profile picture.
|
||||
|
||||
##### The `project` category
|
||||
#### `project` category actions
|
||||
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
@@ -284,7 +373,7 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. |
|
||||
| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.|
|
||||
|
||||
##### The `protected_branch` category
|
||||
#### `protected_branch` category actions
|
||||
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
@@ -304,7 +393,7 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch.
|
||||
{% endif %}
|
||||
|
||||
##### The `repo` category
|
||||
#### `repo` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -334,34 +423,80 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
##### The `repository_content_analysis` category
|
||||
#### `repository_advisory` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data.variables.product.prodname_dotcom %} for a draft security advisory.
|
||||
| `github_broadcast` | Triggered when {% data.variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}.
|
||||
| `github_withdraw` | Triggered when {% data.variables.product.prodname_dotcom %} withdraws a security advisory that was published in error.
|
||||
| `open` | Triggered when someone opens a draft security advisory.
|
||||
| `publish` | Triggered when someone publishes a security advisory.
|
||||
| `reopen` | Triggered when someone reopens as draft security advisory.
|
||||
| `update` | Triggered when someone edits a draft or published security advisory.
|
||||
|
||||
#### `repository_content_analysis` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository).
|
||||
| `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository).
|
||||
|
||||
##### The `repository_dependency_graph` category
|
||||
{% endif %}{% if currentVersion != "github-ae@latest" %}
|
||||
|
||||
#### `repository_dependency_graph` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `enable` | Triggered when a repository owner or person with admin access to the repository [enables the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository).
|
||||
| `disable` | Triggered when a repository owner or person with admin access to the repository [disables the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository).
|
||||
| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
| `enable` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository.
|
||||
|
||||
{% endif %}
|
||||
{% if currentVersion != "github-ae@latest" %}
|
||||
##### The `repository_vulnerability_alert` category
|
||||
{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
#### `repository_secret_scanning` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when {% data variables.product.product_name %} creates a [{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a vulnerable dependency](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a particular repository.
|
||||
| `resolve` | Triggered when someone with write access to a repository [pushes changes to update and resolve a vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a project dependency.
|
||||
| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency.{% if currentVersion == "free-pro-team@latest" %}
|
||||
| `authorized_users_teams` | Triggered when an organization owner or a member with admin permissions to the repository [updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-dependabot-alerts) for vulnerable dependencies in the repository.{% endif %}
|
||||
| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repository.
|
||||
|
||||
{% endif %}{% if currentVersion != "github-ae@latest" %}
|
||||
#### `repository_vulnerability_alert` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when {% data variables.product.product_name %} creates a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency.
|
||||
| `resolve` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency.
|
||||
|
||||
{% endif %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
#### `repository_vulnerability_alerts` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-dependabot-alerts)."
|
||||
| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}.
|
||||
| `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}.
|
||||
|
||||
{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
#### `secret_scanning` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
| `enable` | Triggered when an organization owner enables secret scanning for all existing{% if currentVersion == "free-pro-team@latest" %}, private{% endif %} repositories.
|
||||
|
||||
#### `secret_scanning_new_repos` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `disable` | Triggered when an organization owner disables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
|
||||
| `enable` | Triggered when an organization owner enables secret scanning for all new {% if currentVersion == "free-pro-team@latest" %}private {% endif %}repositories.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
##### The `sponsors` category
|
||||
#### `sponsors` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -370,7 +505,7 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
{% endif %}
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
|
||||
##### The `team` category
|
||||
#### `team` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
@@ -384,60 +519,13 @@ For more information, see "[Restricting publication of {% data variables.product
|
||||
| `remove_repository` | Triggered when a repository is no longer under a team's control.
|
||||
{% endif %}
|
||||
|
||||
##### The `team_discussions` category
|
||||
#### `team_discussions` category actions
|
||||
|
||||
| Action | Description
|
||||
|---|---|
|
||||
| `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)."
|
||||
| `enable` | Triggered when an organization owner enables team discussions for an organization.
|
||||
|
||||
#### Search based on time of action
|
||||
|
||||
Use the `created` qualifier to filter actions in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
|
||||
|
||||
{% data reusables.search.date_gt_lt %} For example:
|
||||
|
||||
* `created:2014-07-08` finds all events that occurred on July 8th, 2014.
|
||||
* `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014.
|
||||
* `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014.
|
||||
* `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
|
||||
|
||||
The audit log contains data for the past 90 days, but you can use the `created` qualifier to search for events earlier than that.
|
||||
|
||||
#### Search based on location
|
||||
|
||||
Using the qualifier `country`, you can filter actions in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example:
|
||||
|
||||
* `country:de` finds all events that occurred in Germany.
|
||||
* `country:Mexico` finds all events that occurred in Mexico.
|
||||
* `country:"United States"` all finds events that occurred in the United States.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
### Exporting the audit log
|
||||
|
||||
{% data reusables.audit_log.export-log %}
|
||||
{% data reusables.audit_log.exported-log-keys-and-values %}
|
||||
{% endif %}
|
||||
|
||||
### Using the Audit log API
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The Audit log API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
To ensure a secure IP and maintain compliance for your organization, you can use the Audit log API to keep copies of your audit log data and monitor:
|
||||
* Access to your organization or repository settings.
|
||||
* Changes in permissions.
|
||||
* Added or removed users in an organization, repository, or team.
|
||||
* Users being promoted to admin.
|
||||
* Changes to permissions of a GitHub App.
|
||||
|
||||
The GraphQL response can include data for up to 90 to 120 days.
|
||||
|
||||
For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log](/graphql/reference/interfaces#auditentry/)."
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Keeping your organization secure](/articles/keeping-your-organization-secure)"
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Managing licenses for Visual Studio subscription with GitHub Enterprise
|
||||
intro: 'You can manage {% data variables.product.prodname_enterprise %} licensing for {% data variables.product.prodname_vss_ghe %}.'
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle
|
||||
- /github/setting-up-and-managing-your-enterprise-account/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle
|
||||
- /github/articles/about-the-github-and-visual-studio-bundle
|
||||
- /articles/about-the-github-and-visual-studio-bundle
|
||||
- /github/setting-up-and-managing-your-enterprise-account/managing-licenses-for-visual-studio-subscription-with-github-enterprise
|
||||
|
||||
@@ -37,6 +37,8 @@ Während Sie den Dienst nutzen, dürfen Sie unter keinen Umständen
|
||||
|
||||
- eine Einzelperson oder Gruppe, einschließlich Ihrer Mitarbeiter, Führungskräfte, Vertreter und anderer Benutzer, belästigen, beleidigen, bedrohen oder zur Gewalt gegen sie aufrufen,
|
||||
|
||||
- post off-topic content, or interact with platform features, in a way that significantly or repeatedly disrupts the experience of other users;
|
||||
|
||||
- unsere Server für irgendeine Art von übermäßigen automatisierten Massenaktivitäten (beispielsweise Spam oder Kryptowährungs-Mining) verwenden, die unsere Server durch automatisierte Mittel übermäßig belasten, oder irgendeine andere Form von unerwünschter Werbung oder Aufforderungen, z. B. Systeme, die schnellen Reichtum versprechen, über unsere Server verbreiten,
|
||||
|
||||
- unsere Server nutzen, um Dienste, Geräte, Daten, Konten oder Netzwerke zu stören oder zu versuchen, diese zu stören, oder um unbefugten Zugang zu erlangen oder dies zu versuchen (es sei denn, dies wurde im Rahmen des [GitHub Bug Bounty-Programms](https://bounty.github.com) genehmigt),
|
||||
@@ -48,15 +50,17 @@ Während Sie den Dienst nutzen, dürfen Sie unter keinen Umständen
|
||||
### 4. Einschränkungen hinsichtlich der Dienstnutzung
|
||||
Sie dürfen keinen Teil des Dienstes, der Nutzung des Dienstes oder des Zugriffs auf den Dienst reproduzieren, duplizieren, kopieren, verkaufen, wiederverkaufen oder ausnutzen.
|
||||
|
||||
### 5. Beschränkungen hinsichtlich Scrapings und der API-Nutzung
|
||||
Der Begriff „Scraping“ bezieht sich auf die Extrahierung von Daten aus unserem Dienst mithilfe automatischer Prozesse wie z. B. Bots oder Webcrawlern. Er umfasst nicht die Erfassung von Informationen über unser API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms. Scraping ist Ihnen auf unserer Website für die folgenden Zwecke gestattet:
|
||||
### 5. Information Usage Restrictions
|
||||
You may use information from our Service for the following reasons, regardless of whether the information was scraped, collected through our API, or obtained otherwise:
|
||||
|
||||
- Forscher können öffentliche, nicht personenbezogene Daten aus dem Dienst zu Forschungszwecken extrahieren, vorausgesetzt, die sich aus dieser Forschung ergebenden Veröffentlichungen werden öffentlich zugänglich gemacht.
|
||||
- Archivare können öffentliche Daten zu Archivierungszwecken aus dem Dienst extrahieren.
|
||||
- Researchers may use public, non-personal information from the Service for research purposes, only if any publications resulting from that research are [open access](https://en.wikipedia.org/wiki/Open_access).
|
||||
- Archivists may use public information from the Service for archival purposes.
|
||||
|
||||
Sie dürfen keine Daten aus dem Dienst für Spamzwecke extrahieren. Dies gilt auch für den Verkauf von personenbezogenen Daten von Benutzern (gemäß Definition in der [GitHub-Datenschutzerklärung](/articles/github-privacy-statement)) beispielsweise an Personalvermittler, Headhunter und Stellenbörsen.
|
||||
Scraping refers to extracting information from our Service via an automated process, such as a bot or webcrawler. Scraping does not refer to the collection of information through our API. Please see Section H of our [Terms of Service](/articles/github-terms-of-service#h-api-terms) for our API Terms.
|
||||
|
||||
Alle Daten, die mittels Scraping gesammelt werden, müssen den Vorgaben der [GitHub-Datenschutzerklärung](/articles/github-privacy-statement) entsprechen.
|
||||
You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling User Personal Information (as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement)), such as to recruiters, headhunters, and job boards.
|
||||
|
||||
Your use of information from the Service must comply with the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement).
|
||||
|
||||
### 6. Datenschutz
|
||||
Der Missbrauch personenbezogener Daten von Benutzern ist untersagt.
|
||||
|
||||
@@ -4,7 +4,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
Version Effective Date: November 1, 2020
|
||||
Version Effective Date: November 13, 2020
|
||||
|
||||
Wenn Sie ein Konto erstellen, erhalten Sie Zugriff auf viele verschiedene Features und Produkte, die alle Teil des Dienstes sind. Da viele dieser Features und Produkte unterschiedliche Funktionen bieten, erfordern sie möglicherweise zusätzliche Geschäftsbedingungen, die für dieses Feature oder dieses Produkt spezifisch sind. Below, we've listed those features and products, along with the corresponding additional terms that apply to your use of them.
|
||||
|
||||
@@ -89,7 +89,7 @@ In order to become a Sponsored Developer, you must agree to the [GitHub Sponsors
|
||||
|
||||
### 9. GitHub Advanced Security
|
||||
|
||||
Mit GitHub Advanced Security können Sie Sicherheitslücken durch anpassbare und automatisierte semantische Codeanalyse identifizieren. GitHub Advanced Security ist pro Benutzer lizenziert. Wenn Sie GitHub Advanced Security als Teil von GitHub Enterprise Cloud verwenden, erfordern viele Funktionen von GitHub Advanced Security, einschließlich des automatisierten Code-Scannens privater Repositorys, auch die Verwendung von GitHub Actions. Die Abrechnung für die Nutzung von GitHub Actions erfolgt nutzungsbasiert und unterliegt den [GitHub Actions-Bedingungen](/github/site-policy/github-additional-product-terms#c-payment-and-billing-for-actions-and-packages).
|
||||
GitHub Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. Wenn Sie GitHub Advanced Security als Teil von GitHub Enterprise Cloud verwenden, erfordern viele Funktionen von GitHub Advanced Security, einschließlich des automatisierten Code-Scannens privater Repositorys, auch die Verwendung von GitHub Actions.
|
||||
|
||||
### 10. Dependabot Preview
|
||||
|
||||
@@ -108,4 +108,3 @@ We need the legal right to submit your contributions to the GitHub Advisory Data
|
||||
#### b. Lizenz für das GitHub Advisory Database
|
||||
|
||||
The GitHub Advisory Database is licensed under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/). The attribution term may be fulfilled by linking to the GitHub Advisory Database at <https://github.com/advisories> or to individual GitHub Advisory Database records used, prefixed by <https://github.com/advisories>.
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ Millionen von Entwicklern hosten Millionen von Projekten auf GitHub – sowohl O
|
||||
|
||||
Die weltweiten GitHub-Benutzer verfügen über völlig unterschiedliche Perspektiven, Ideen und Erfahrungen und umfassen sowohl Personen, die letzte Woche ihr erstes "Hello World"-Projekt ins Leben gerufen haben, als auch die bekanntesten Software-Entwickler der Welt. Wir sind bestrebt, GitHub zu einem einladenden Umfeld für all die verschiedenen Stimmen und Perspektiven in unserer Community zu machen und gleichzeitig einen Raum zu bieten, in dem sich Personen frei äußern können.
|
||||
|
||||
Wir sind darauf angewiesen, dass unsere Community-Mitglieder Erwartungen kommunizieren, ihre Projekte [moderieren ](#what-if-something-or-someone-offends-you)und {% data variables.contact.report_abuse %} oder {% data variables.contact.report_content %}. Wir durchsuchen nicht aktiv die Inhalte, um sie zu moderieren. Wir hoffen, Ihnen durch die Darstellung unserer Erwartungen an unsere Community verständlich zu machen, wie Sie am besten auf GitHub mitwirken können und welche Art von Handlungen oder Inhalten möglicherweise gegen unsere [Nutzungsbedingungen](#legal-notices) verstoßen. Wir werden allen Meldungen über Missbrauch nachgehen und können öffentliche Inhalte auf unserer Website moderieren, bei denen wir feststellen, dass sie gegen unsere Nutzungsbedingungen verstoßen.
|
||||
Wir sind darauf angewiesen, dass unsere Community-Mitglieder Erwartungen kommunizieren, ihre Projekte [moderieren ](#what-if-something-or-someone-offends-you)und {% data variables.contact.report_abuse %} oder {% data variables.contact.report_content %}. By outlining what we expect to see within our community, we hope to help you understand how best to collaborate on GitHub, and what type of actions or content may violate our [Terms of Service](#legal-notices), which include our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). Wir werden allen Meldungen über Missbrauch nachgehen und können öffentliche Inhalte auf unserer Website moderieren, bei denen wir feststellen, dass sie gegen unsere Nutzungsbedingungen verstoßen.
|
||||
|
||||
### Eine starke Community aufbauen
|
||||
|
||||
@@ -47,23 +47,25 @@ Selbstverständlich können Sie uns jederzeit kontaktieren, um {% data variables
|
||||
|
||||
Wir setzen uns für die Aufrechterhaltung einer Community ein, in der es den Benutzer freisteht, sich auszudrücken und die Ideen des anderen in Frage zu stellen, sowohl technisch als auch anderweitig. Solche Diskussionen fördern jedoch keinen fruchtbaren Dialog, wenn Ideen zum Schweigen gebracht werden, weil Community-Mitglieder niedergeschrien werden oder Angst haben, sich zu äußern. Das bedeutet, dass Sie jederzeit respektvoll und höflich sein und andere nicht auf der Grundlage ihrer Identität angreifen sollten. Wir tolerieren kein Verhalten, das Grenzen in den folgenden Bereichen überschreitet:
|
||||
|
||||
* **Gewaltandrohungen** - Sie dürfen nicht mit Gewalt gegen andere drohen oder die Website nutzen, um Akte realer Gewalt oder Terrorismus zu organisieren, zu fördern oder anzustiften. Denken Sie sorgfältig über Ihre Wortwahl, von Ihnen gepostete Bilder sowie auch über die Software, die Sie verfassen, nach und wie diese von anderen interpretiert werden können. Selbst wenn Sie etwas als Scherz gemeint haben, wird es möglicherweise nicht auf diese Weise aufgenommen. Wenn Sie glauben, dass jemand anderes die Inhalte, die Sie posten, als Bedrohung oder als Förderung von Gewalt oder Terrorismus interpretieren *könnte*, hören Sie auf. Veröffentlichen Sie sie nicht auf GitHub. In außergewöhnlichen Fällen können wir Gewaltandrohungen an die Strafverfolgungsbehörden melden, wenn wir der Meinung sind, dass ein echtes Risiko körperlicher Schäden oder eine Bedrohung der öffentlichen Sicherheit besteht.
|
||||
- #### Threats of violence You may not threaten violence towards others or use the site to organize, promote, or incite acts of real-world violence or terrorism. Denken Sie sorgfältig über Ihre Wortwahl, von Ihnen gepostete Bilder sowie auch über die Software, die Sie verfassen, nach und wie diese von anderen interpretiert werden können. Selbst wenn Sie etwas als Scherz gemeint haben, wird es möglicherweise nicht auf diese Weise aufgenommen. Wenn Sie glauben, dass jemand anderes die Inhalte, die Sie posten, als Bedrohung oder als Förderung von Gewalt oder Terrorismus interpretieren *könnte*, hören Sie auf. Veröffentlichen Sie sie nicht auf GitHub. In außergewöhnlichen Fällen können wir Gewaltandrohungen an die Strafverfolgungsbehörden melden, wenn wir der Meinung sind, dass ein echtes Risiko körperlicher Schäden oder eine Bedrohung der öffentlichen Sicherheit besteht.
|
||||
|
||||
* **Hassreden und Diskriminierung.** - Obwohl es nicht verboten ist, Themen wie Alter, Körpergröße, ethnische Zugehörigkeit, Geschlechtsidentität und Ausdruck, Erfahrungsgrad, Nationalität, persönliches Aussehen, Rasse, Religion oder sexuelle Identität und Orientierung anzusprechen, tolerieren wir keine Sprache, die eine Person oder eine Gruppe von Menschen auf der Grundlage dessen angreift, wer sie sind. Machen Sie sich einfach bewusst, dass diese (und andere) heikle Themen, wenn sie auf aggressive oder beleidigende Weise angegangen werden, dazu führen können, dass sich andere unwillkommen oder gar unsicher fühlen. Obwohl es immer das Potenzial für Missverständnisse gibt, erwarten wir von unseren Community-Mitgliedern, dass sie respektvoll und zivil bleiben, wenn sie sensible Themen diskutieren.
|
||||
- #### Hate speech and discrimination While it is not forbidden to broach topics such as age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation, we do not tolerate speech that attacks a person or group of people on the basis of who they are. Machen Sie sich einfach bewusst, dass diese (und andere) heikle Themen, wenn sie auf aggressive oder beleidigende Weise angegangen werden, dazu führen können, dass sich andere unwillkommen oder gar unsicher fühlen. Obwohl es immer das Potenzial für Missverständnisse gibt, erwarten wir von unseren Community-Mitgliedern, dass sie respektvoll und zivil bleiben, wenn sie sensible Themen diskutieren.
|
||||
|
||||
* **Mobbing und Belästigung** - Wir tolerieren kein Mobbing und keine Belästigung. Dazu gehört jede Form der Belästigung oder Einschüchterung, die auf eine bestimmte Person oder Personengruppe abzielt. Wenn Ihre Handlungen unerwünscht sind und Sie diese dennoch fortsetzen, ist die Wahrscheinlichkeit groß, dass Sie auf Mobbing oder Belästigung ausgerichtet sind.
|
||||
- #### Bullying and harassment We do not tolerate bullying or harassment. Dazu gehört jede Form der Belästigung oder Einschüchterung, die auf eine bestimmte Person oder Personengruppe abzielt. Wenn Ihre Handlungen unerwünscht sind und Sie diese dennoch fortsetzen, ist die Wahrscheinlichkeit groß, dass Sie auf Mobbing oder Belästigung ausgerichtet sind.
|
||||
|
||||
* **Impersonifizierung** - Sie dürfen nicht versuchen, andere bezüglich Ihrer Identität zu täuschen, indem Sie einen Avatar einer anderen Person kopieren, Inhalte unter deren E-Mail-Adresse posten, absichtlich einen täuschend ähnlichen Benutzernamen verwenden oder sich anderweitig als jemand anderes ausgeben. Impersonifizierung ist eine Form der Belästigung.
|
||||
- #### Disrupting the experience of other users Being part of a community includes recognizing how your behavior affects others and engaging in meaningful and productive interactions with people and the platform they rely on. Behaviors such as repeatedly posting off-topic comments, opening empty or meaningless issues or pull requests, or using any other platform feature in a way that continually disrupts the experience of other users are not allowed. While we encourage maintainers to moderate their own projects on an individual basis, GitHub staff may take further restrictive action against accounts that are engaging in these types of behaviors.
|
||||
|
||||
* **Doxxing und Eingriff in die Privatsphäre ** - Posten Sie keine persönlichen Daten anderer Personen, z. B. Telefonnummern, private E-Mail-Adressen, physische Adressen, Kreditkartennummern, Sozialversicherungs-/Nationale Identitätsnummern oder Kennwörter. Je nach Kontext, z. B. bei Einschüchterung oder Belästigung, können wir andere Informationen, wie Fotos oder Videos, die ohne Zustimmung des Betreffenden aufgenommen oder verbreitet wurden, als Eingriff in die Privatsphäre betrachten, insbesondere wenn dieses Material ein Sicherheitsrisiko für das Thema darstellt.
|
||||
- #### Impersonation You may not seek to mislead others as to your identity by copying another person's avatar, posting content under their email address, using a similar username or otherwise posing as someone else. Impersonifizierung ist eine Form der Belästigung.
|
||||
|
||||
* **Sexuell obszöne Inhalte** - Posten Sie keine pornographischen Inhalte. Das bedeutet nicht, dass Nacktheit oder jeder Kodex und Inhalt im Zusammenhang mit Sexualität verboten ist. Wir erkennen an, dass Sexualität ein Teil des Lebens ist und nicht-pornografische sexuelle Inhalte ein Teil Ihres Projekts sein können oder zu pädagogischen oder künstlerischen Zwecken präsentiert werden können. Wir erlauben keine obszönen sexuellen Inhalte oder Inhalte, die die Ausbeutung oder Sexualisierung von Minderjährigen beinhalten können.
|
||||
- #### Doxxing and invasion of privacy Don't post other people's personal information, such as personal, private email addresses, phone numbers, physical addresses, credit card numbers, Social Security/National Identity numbers, or passwords. Je nach Kontext, z. B. bei Einschüchterung oder Belästigung, können wir andere Informationen, wie Fotos oder Videos, die ohne Zustimmung des Betreffenden aufgenommen oder verbreitet wurden, als Eingriff in die Privatsphäre betrachten, insbesondere wenn dieses Material ein Sicherheitsrisiko für das Thema darstellt.
|
||||
|
||||
* **Gewalttätige Inhalte** - Posten Sie keine gewalttätigen Bilder, Texte oder andere Inhalte ohne angemessenen Kontext oder Warnungen. Obwohl es oft in Ordnung ist, gewalttätige Inhalte in Videospiele, Nachrichtenberichte und Beschreibungen historischer Ereignisse aufzunehmen, erlauben wir keine gewalttätigen Inhalte, die wahllos gepostet werden oder die in einer Weise gepostet werden, dass es für andere Benutzer schwierig ist, sie zu vermeiden (z. B. einen Profil-Avatar oder einen Issue-Kommentar). Eine klare Warnung oder ein Haftungsausschluss in anderen Kontexten hilft Benutzern, eine fundierte Entscheidung darüber zu treffen, ob sie sich mit solchen Inhalten beschäftigen möchten oder nicht.
|
||||
- #### Sexually obscene content Don’t post content that is pornographic. Das bedeutet nicht, dass Nacktheit oder jeder Kodex und Inhalt im Zusammenhang mit Sexualität verboten ist. Wir erkennen an, dass Sexualität ein Teil des Lebens ist und nicht-pornografische sexuelle Inhalte ein Teil Ihres Projekts sein können oder zu pädagogischen oder künstlerischen Zwecken präsentiert werden können. Wir erlauben keine obszönen sexuellen Inhalte oder Inhalte, die die Ausbeutung oder Sexualisierung von Minderjährigen beinhalten können.
|
||||
|
||||
* **Irreführung und Fehlinformationen** - Sie dürfen keine Inhalte posten, die ein verzerrtes Bild der Realität vermitteln, unabhängig davon, ob es sich um ungenaue oder falsche (Fehlinformationen) oder absichtlich täuschende (Irreführung) Inhalte handelt, weil solche Inhalte der Öffentlichkeit Schaden zufügen oder faire und gleiche Chancen für alle zur Teilnahme am öffentlichen Leben beeinträchtigen könnten. Zum Beispiel lassen wir keine Inhalte zu, die das Wohlergehen von Personengruppen gefährden oder ihre Fähigkeit einschränken, an einer freien und offenen Gesellschaft teilzunehmen. Wir ermutigen zur aktiven Teilnahme am Austausch von Ideen, Perspektiven und Erfahrungen und sind möglicherweise nicht in der Lage, persönliche Berichte oder Feststellungen anzufechten. Wir erlauben in der Regel Parodie und Satire, die mit unseren akzeptablen Nutzungsrichtlinien übereinstimmen, und wir halten den Kontext für wichtig, wie Informationen empfangen und verstanden werden; Daher kann es angemessen sein, Ihre Absichten durch Haftungsausschluss oder andere Mittel sowie die Quelle(n) Ihrer Informationen zu klären.
|
||||
- #### Gratuitously violent content Don’t post violent images, text, or other content without reasonable context or warnings. Obwohl es oft in Ordnung ist, gewalttätige Inhalte in Videospiele, Nachrichtenberichte und Beschreibungen historischer Ereignisse aufzunehmen, erlauben wir keine gewalttätigen Inhalte, die wahllos gepostet werden oder die in einer Weise gepostet werden, dass es für andere Benutzer schwierig ist, sie zu vermeiden (z. B. einen Profil-Avatar oder einen Issue-Kommentar). Eine klare Warnung oder ein Haftungsausschluss in anderen Kontexten hilft Benutzern, eine fundierte Entscheidung darüber zu treffen, ob sie sich mit solchen Inhalten beschäftigen möchten oder nicht.
|
||||
|
||||
* **Active malware or exploits** - Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Beachten Sie jedoch, dass wir die Veröffentlichung von Quellcode, der zur Entwicklung von Malware oder Exploits verwendet werden könnte, nicht verbieten, da die Veröffentlichung und Verbreitung eines solchen Quellcodes einen lehrreichen Wert hat und für die Sicherheits-Community einen klaren Nutzen darstellt.
|
||||
- #### Misinformation and disinformation You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. Zum Beispiel lassen wir keine Inhalte zu, die das Wohlergehen von Personengruppen gefährden oder ihre Fähigkeit einschränken, an einer freien und offenen Gesellschaft teilzunehmen. Wir ermutigen zur aktiven Teilnahme am Austausch von Ideen, Perspektiven und Erfahrungen und sind möglicherweise nicht in der Lage, persönliche Berichte oder Feststellungen anzufechten. Wir erlauben in der Regel Parodie und Satire, die mit unseren akzeptablen Nutzungsrichtlinien übereinstimmen, und wir halten den Kontext für wichtig, wie Informationen empfangen und verstanden werden; Daher kann es angemessen sein, Ihre Absichten durch Haftungsausschluss oder andere Mittel sowie die Quelle(n) Ihrer Informationen zu klären.
|
||||
|
||||
- #### Active malware or exploits Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Beachten Sie jedoch, dass wir die Veröffentlichung von Quellcode, der zur Entwicklung von Malware oder Exploits verwendet werden könnte, nicht verbieten, da die Veröffentlichung und Verbreitung eines solchen Quellcodes einen lehrreichen Wert hat und für die Sicherheits-Community einen klaren Nutzen darstellt.
|
||||
|
||||
|
||||
### Was passiert, wenn jemand die Regeln verletzt?
|
||||
|
||||
@@ -9,7 +9,7 @@ versions:
|
||||
VIELEN DANK, DASS SIE SICH FÜR GITHUB ENTSCHIEDEN HABEN, UM DIE ANFORDERUNGEN IHRES UNTERNEHMENS ZU ERFÜLLEN. BITTE LESEN SIE DIESE VEREINBARUNG SORGFÄLTIG DURCH; SIE REGELT DIE VERWENDUNG DER PRODUKTE (WIE UNTEN DEFINIERT), ES SEI DENN, GITHUB HAT ZU DIESEM ZWECK EINE SEPARATE SCHRIFTLICHE VEREINBARUNG MIT DEM KUNDEN ABGESCHLOSSEN. WENN DER KUNDE AUF „I AGREE“ („ICH STIMME ZU“) ODER EINE ÄHNLICHE SCHALTFLÄCHE KLICKT ODER EINES DER PRODUKTE VERWENDET, AKZEPTIERT ER ALLE GESCHÄFTSBEDINGUNGEN DIESER VEREINBARUNG. WENN DER KUNDE DIESE VEREINBARUNG IM NAMEN EINES UNTERNEHMENS ODER EINER ANDEREN JURISTISCHEN PERSON ABSCHLIESST, SICHERT ER ZU, DASS ER RECHTLICH DAZU BEFUGT IST, DIESE VEREINBARUNG FÜR DAS UNTERNEHMEN ODER DIE JURISTISCHE PERSON ZU SCHLIESSEN.
|
||||
|
||||
### Unternehmensnutzungsbedingungen für GitHub
|
||||
Datum des Inkrafttretens dieser Fassung: 20. Juli 2020
|
||||
Version Effective Date: November 16, 2020
|
||||
|
||||
Diese Vereinbarung gilt für die folgenden Angebote von GitHub, die nachfolgend genauer definiert werden (zusammen die **„Produkte“**):
|
||||
- der Dienst;
|
||||
@@ -133,13 +133,13 @@ Kunden können im Rahmen der Nutzung des Dienstes benutzergenerierte Inhalte ers
|
||||
Der Kunde behält die Eigentumsrechte an Kundeninhalten, die der Kunde erstellt oder die sein Eigentum sind. Der Kunde erklärt sich einverstanden, dass er (a) für die Kundeninhalte haftet, (b) ausschließlich Kundeninhalte sendet, für die er über das Recht zur Veröffentlichung verfügt (einschließlich Inhalten von Dritten und benutzergenerierter Inhalte), und (c) in vollem Umfang alle Bedingungen für Lizenzen Dritter im Zusammenhang mit Kundeninhalten erfüllt, die der Kunde veröffentlicht. Der Kunde gewährt die Rechte nach den Abschnitten D.3 bis D.6 kostenlos und zu den in den entsprechenden Abschnitten angegebenen Zwecken, bis der Kunde die Kundeninhalte von den GitHub-Servern entfernt. Davon ausgenommen sind Inhalte, die der Kunde öffentlich veröffentlicht hat und für die externe Benutzer ein Forking vorgenommen haben. In diesem Fall gilt die Lizenz unbefristet, bis alle Forks von Kundeninhalten von den GitHub-Servern entfernt wurden. Lädt der Kunde Kundeninhalte hoch, für die bereits eine Lizenz besteht, die GitHub die erforderlichen Rechte zur Ausführung des Dienstes gewährt, ist keine weitere Lizenz erforderlich.
|
||||
|
||||
#### 3. Lizenzvergabe an uns
|
||||
Der Kunde gewährt GitHub das Recht, Kundeninhalte zu speichern, zu analysieren und anzuzeigen und gelegentlich Kopien zu erstellen, insoweit dies zur Bereitstellung des Dienstes erforderlich ist. Dazu zählt das Recht, Kundeninhalte in die GitHub-Datenbank zu kopieren und Sicherungen zu erstellen, Kundeninhalte dem Kunden und anderen anzuzeigen, denen der Kunde die Inhalte anzeigen möchte, Kundeninhalte für einen Suchindex oder auf andere Weise auf den GitHub-Servern zu analysieren, Kundeninhalte für externe Benutzer freizugeben, für die der Kunde die Inhalte freigeben möchte, und Kundeninhalte wiederzugeben, insoweit es sich um Musik, Videos usw. handelt. Diese Rechte gelten sowohl für öffentliche als auch private Repositorys. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb des Dienstes zu verwenden. Der Kunde gewährt GitHub die nötigen Rechte zur Verwendung von Kundeninhalten ohne Namensnennung und zur Durchführung angemessener Änderungen von Kundeninhalten, insoweit dies für die Bereitstellung des Dienstes erforderlich ist.
|
||||
Customer grants to GitHub the right to store, archive, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service, including improving the Service over time. This license includes the right to copy Customer Content to GitHub's database and make backups; display Customer Content to Customer and those to whom Customer chooses to show it; parse Customer Content into a search index or otherwise analyze it on GitHub's servers; share Customer Content with External Users with whom Customer chooses to share it; and perform Customer Content, in case it is something like music or video. Diese Rechte gelten sowohl für öffentliche als auch private Repositorys. This license does not grant GitHub the right to sell Customer Content. It also does not grant GitHub the right to otherwise distribute or use Customer Content outside of our provision of the Service, except that as part of the right to archive Customer Content, GitHub may permit our partners to store and archive Customer Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program. Der Kunde gewährt GitHub die nötigen Rechte zur Verwendung von Kundeninhalten ohne Namensnennung und zur Durchführung angemessener Änderungen von Kundeninhalten, insoweit dies für die Bereitstellung des Dienstes erforderlich ist.
|
||||
|
||||
#### 4. Lizenzgewährung für externe Benutzer
|
||||
Inhalte, die der Kunde öffentlich postet, darunter Issues, Kommentare und Beiträge in Repositorys externer Benutzer, können von anderen angezeigt werden. Indem der Kunde seine Repositorys für die öffentliche Anzeige konfiguriert, stimmt er zu, dass externe Benutzer die Repositorys des Kunden anzeigen und kopieren können. Konfiguriert der Kunde seine Pages und Repositorys für die öffentliche Anzeige, gewährt der Kunde externen Benutzern eine nicht exklusive, weltweite Lizenz zur Verwendung, Anzeige und Wiedergabe von Kundeninhalten über den Dienst und zur Reproduktion von Kundeninhalten ausschließlich im Dienst, insoweit dies nach den von GitHub bereitgestellten Funktionen zulässig ist (beispielsweise durch Forking). Der Kunde kann weitere Rechte an Kundeninhalten gewähren, wenn der Kunde eine Lizenz einführt. Wenn der Kunde Kundeninhalte hochlädt, die er nicht erstellt hat oder die ihm nicht gehören, haftet der Kunde dafür sicherzustellen, dass die hochgeladenen Kundeninhalte nach den Bedingungen lizenziert sind, mit denen diese Rechte externen Benutzern gewährt werden
|
||||
|
||||
#### 5. Beiträge im Rahmen einer Repository-Lizenz
|
||||
Macht der Kunde einen Beitrag zu einem Repository mit einem Lizenzhinweis, lizenziert der Kunde seinen Beitrag zu denselben Bedingungen und erklärt, dass er das Recht hat, den entsprechenden Beitrag zu diesen Bedingungen zu lizenzieren. Verfügt der Kunde über eine gesonderte Vereinbarung zur Lizenzierung seiner Beiträge nach anderen Bedingungen wie z. B. einer Mitwirkungslizenzvereinbarung, hat die entsprechende Vereinbarung Vorrang.
|
||||
Whenever Customer adds Content to a repository containing notice of a license, it licenses that Content under the same terms and agrees that it has the right to license that Content under those terms. If Customer has a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede.
|
||||
|
||||
#### 6. Urheberpersönlichkeitsrechte
|
||||
Der Kunde behält alle Urheberpersönlichkeitsrechte an Kundeninhalten, die er hochlädt, veröffentlicht oder an einen Teil des Dienstes sendet, die Rechte auf Unantastbarkeit und Namensnennung eingeschlossen. Der Kunde verzichtet jedoch auf diese Rechte und stimmt zu, diese gegenüber GitHub nicht geltend zu machen, um GitHub die angemessene Ausübung der Rechte nach Abschnitt D zu ermöglichen, wobei dies jedoch ausschließlich zu diesem Zweck gilt.
|
||||
@@ -153,10 +153,13 @@ Der Kunde haftet für die Verwaltung des Zugriffs auf seine privaten Repositorys
|
||||
GitHub betrachtet Kundeninhalte in den privaten Repositorys des Kunden als vertrauliche Informationen des Kunden. GitHub sorgt nach Abschnitt P für den Schutz und die strikte Wahrung der Vertraulichkeit von Kundeninhalten in privaten Repositorys.
|
||||
|
||||
#### 3. Zugriff
|
||||
GitHub-Mitarbeiter können ausschließlich in folgenden Fällen auf private Repositorys des Kunden zugreifen: (i) aus Gründen des Supports mit dem Wissen und unter Zustimmung des Kunden oder (ii) wenn der Zugriff aus Sicherheitsgründen erforderlich ist. Der Kunde kann zusätzlichen Zugriff auf seine privaten Repositorys aktivieren. Beispielsweise kann der Kunde mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Kundeninhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Dienst oder Feature andere sein. GitHub behandelt Kundeninhalte in den privaten Repositorys des Kunden jedoch weiterhin als vertrauliche Informationen des Kunden. Sind für diese Dienste oder Features neben den Rechten, die für die Dienstbereitstellung erforderlich sind, zusätzliche Rechte erforderlich, gibt GitHub eine Erläuterung dieser Rechte.
|
||||
GitHub personnel may only access Customer's Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents).
|
||||
|
||||
#### 4. Ausnahmen
|
||||
Hat GitHub Grund zu der Annahme, dass Inhalte eines privaten Repositorys gegen Gesetze oder diese Vereinbarung verstoßen, hat GitHub das Recht, auf die betreffenden Inhalte zuzugreifen und sie zu prüfen sowie zu entfernen. Darüber hinaus kann GitHub [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte der privaten Repositorys des Kunden offenzulegen. Sofern GitHub nicht durch gesetzliche Auflagen oder in Reaktion auf eine Sicherheitsbedrohung oder ein sonstiges Sicherheitsrisiko anders gebunden ist, informiert GitHub über entsprechende Maßnahmen.
|
||||
Der Kunde kann zusätzlichen Zugriff auf seine privaten Repositorys aktivieren. Beispielsweise kann der Kunde mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Kundeninhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Dienst oder Feature andere sein. GitHub behandelt Kundeninhalte in den privaten Repositorys des Kunden jedoch weiterhin als vertrauliche Informationen des Kunden. Sind für diese Dienste oder Features neben den Rechten, die für die Dienstbereitstellung erforderlich sind, zusätzliche Rechte erforderlich, gibt GitHub eine Erläuterung dieser Rechte.
|
||||
|
||||
Darüber hinaus können wir [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte Ihrer privaten Repositorys offenzulegen.
|
||||
|
||||
GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
|
||||
|
||||
### F. Richtlinien bezüglich geistigem Eigentum
|
||||
|
||||
@@ -270,12 +273,12 @@ Keine Partei verwendet die vertraulichen Informationen der jeweils anderen Parte
|
||||
Fordert der Kunde Dienstleistungen an, legt GitHub eine Leistungsbeschreibung zu den entsprechenden Dienstleistungen vor. GitHub erbringt die in der jeweiligen Leistungsbeschreibung beschriebenen Dienstleistungen. GitHub steuert die Art und die Mittel zur Erbringung der Dienstleistungen und behält sich das Recht vor, die beauftragten Mitarbeiter auszuwählen. GitHub kann die Dienstleistungen durch Dritte erbringen lassen, sofern GitHub für deren Handlungen und Unterlassungen haftet. Der Kunde ist einverstanden und akzeptiert, dass GitHub alle Rechte, Ansprüche und Anteile an allen Elementen behält, die in Zusammenhang mit der Erbringung der Dienstleistungen genutzt oder entwickelt werden, unter anderem Software, Tools, Spezifikationen, Ideen, Entwürfe, Erfindungen, Prozesse, Verfahren und Know-how. Insoweit GitHub dem Kunden während der Erbringung der Dienstleistungen Elemente bereitstellt, gewährt GitHub dem Kunden eine nicht exklusive, nicht übertragbare, weltweite, unentgeltliche, zeitlich beschränkte Lizenz zur Nutzung dieser Elemente über die Laufzeit dieser Vereinbarung, die ausschließlich in Verbindung mit der Nutzung des Dienstes durch den Kunden gilt.
|
||||
|
||||
### R. Änderungen des Dienstes oder der Nutzungsbedingungen
|
||||
GitHub behält sich das Recht vor, diese Vereinbarung jederzeit nach alleinigem Ermessen zu ändern, und aktualisiert diese Vereinbarung im Fall entsprechender Änderungen. GitHub informiert den Kunden durch Veröffentlichung einer Mitteilung im Dienst über wesentliche Änderungen dieser Vereinbarung wie z. B. Preisänderungen mindestens 30 Tage vor Inkrafttreten der Änderung. Bei geringfügigen Änderungen stellt die fortgesetzte Nutzung des Dienstes durch den Kunden die Zustimmung zu den Änderungen dieser Vereinbarung dar. Der Kunde kann alle Änderungen dieser Vereinbarung in unserem [Websiterichtlinien](https://github.com/github/site-policy)-Repository einsehen.
|
||||
GitHub behält sich das Recht vor, diese Vereinbarung jederzeit nach alleinigem Ermessen zu ändern, und aktualisiert diese Vereinbarung im Fall entsprechender Änderungen. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Der Kunde kann alle Änderungen dieser Vereinbarung in unserem [Websiterichtlinien](https://github.com/github/site-policy)-Repository einsehen.
|
||||
|
||||
Die Änderung des Dienstes durch GitHub erfolgt durch Updates und Hinzufügen neuer Funktionen. Ungeachtet des Vorstehenden behält sich GitHub das Recht vor, den Dienst (oder einen Teil davon) jederzeit mit oder ohne vorherige Ankündigung vorübergehend oder dauerhaft zu ändern oder einzustellen.
|
||||
|
||||
### S. Unterstützung
|
||||
GitHub leistet mit Ausnahme von Wochenenden und US-Feiertagen an fünf (5) Tagen pro Woche rund um die Uhr kostenlosen technischen Standard-Support für den Dienst. holidays. Standard-Support wird ausschließlich über webgestützte Ticketeinreichung über den GitHub-Support erbracht, und Supportanfragen müssen von einem Benutzer stammen, mit dem das GitHub-Supportteam interagieren kann. GitHub kann Premium-Support (gemäß den Bedingungen von [GitHub-Premium-Support für Enterprise](/articles/about-github-premium-support)) oder besonderen technischen Support für den Dienst mit der Supportstufe zu den Gebühren über die Abonnementlaufzeit gewähren, die in einem Auftragsformular oder einer Leistungsbeschreibung angegeben sind.
|
||||
GitHub leistet mit Ausnahme von Wochenenden und US-Feiertagen an fünf (5) Tagen pro Woche rund um die Uhr kostenlosen technischen Standard-Support für den Dienst. holidays. Standard-Support wird ausschließlich über webgestützte Ticketeinreichung über den GitHub-Support erbracht, und Supportanfragen müssen von einem Benutzer stammen, mit dem das GitHub-Supportteam interagieren kann. GitHub may provide premium Support (subject to the [GitHub Premium Support for Enterprise Cloud](/articles/about-github-premium-support) terms) or dedicated technical Support for the Service at the Support level, Fees, and Subscription Term specified in an Order Form or SOW.
|
||||
|
||||
### T. Sonstiges
|
||||
|
||||
|
||||
@@ -26,6 +26,6 @@ For definitions of each Service feature (“**Service Feature**”) and to revi
|
||||
Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology.
|
||||
|
||||
## Service Credits Redemption
|
||||
If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption should be sent to [GitHub Support](https://support.github.com/contact).
|
||||
If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption and GitHub Enterprise Cloud custom monthly or quarterly reports should be sent to [GitHub Support](https://support.github.com/contact).
|
||||
|
||||
Service Credits may take the form of a refund or credit to Customer’s account, cannot be exchanged into a cash amount, are limited to a maximum of ninety (90) days of paid service per calendar quarter, require Customer to have paid any outstanding invoices, and expire upon termination of Customer’s agreement with GitHub. Service Credits are the sole and exclusive remedy for any failure by GitHub to meet any obligations in this SLA.
|
||||
|
||||
@@ -7,7 +7,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
Datum des Inkrafttretens dieser Fassung: 20. Juli 2020
|
||||
Version Effective Date: November 16, 2020
|
||||
|
||||
WENN DER KUNDE AUF „I AGREE“ („ICH STIMME ZU“) ODER EINE ÄHNLICHE SCHALTFLÄCHE KLICKT ODER EINES DER (NACHFOLGEND DEFINIERTEN) PRODUKTE VERWENDET, AKZEPTIERT ER DIE GESCHÄFTSBEDINGUNGEN DIESER VEREINBARUNG. WENN DER KUNDE DIESE VEREINBARUNG IM NAMEN EINER JURISTISCHEN PERSON SCHLIESST, SICHERT ER ZU, DASS ER RECHTLICH DAZU BEFUGT IST, DIESE VEREINBARUNG FÜR DIE JURISTISCHE PERSON ZU SCHLIESSEN.
|
||||
|
||||
@@ -197,7 +197,7 @@ Diese Vereinbarung bildet zusammen mit den Anhängen und den einzelnen Auftragsf
|
||||
|
||||
#### 1.13.11 Änderungen, Vorrang
|
||||
|
||||
GitHub behält sich das Recht vor, diese Vereinbarung jederzeit nach alleinigem Ermessen zu ändern, und aktualisiert diese Vereinbarung im Fall entsprechender Änderungen. GitHub informiert den Kunden durch Veröffentlichung einer Mitteilung im Dienst über wesentliche Änderungen dieser Vereinbarung wie z. B. Preisänderungen mindestens 30 Tage vor Inkrafttreten der Änderung. Bei geringfügigen Änderungen stellt die fortgesetzte Nutzung des Dienstes durch den Kunden die Zustimmung zu den Änderungen dieser Vereinbarung dar. Der Kunde kann alle Änderungen dieser Vereinbarung in unserem [Websiterichtlinien](https://github.com/github/site-policy)-Repository einsehen. Bei Widersprüchen zwischen den Bestimmungen dieser Vereinbarung und einem Auftragsformular oder einer Leistungsbeschreibung haben die Bestimmungen des Auftragsformulars oder der Leistungsbeschreibung Vorrang, jedoch nur für das entsprechende Auftragsformular bzw. die entsprechende Leistungsbeschreibung.
|
||||
GitHub behält sich das Recht vor, diese Vereinbarung jederzeit nach alleinigem Ermessen zu ändern, und aktualisiert diese Vereinbarung im Fall entsprechender Änderungen. GitHub will notify Customer of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on the Service or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, Customer's continued use of the Service constitutes agreement to our revisions of this Agreement. Der Kunde kann alle Änderungen dieser Vereinbarung in unserem [Websiterichtlinien](https://github.com/github/site-policy)-Repository einsehen. Bei Widersprüchen zwischen den Bestimmungen dieser Vereinbarung und einem Auftragsformular oder einer Leistungsbeschreibung haben die Bestimmungen des Auftragsformulars oder der Leistungsbeschreibung Vorrang, jedoch nur für das entsprechende Auftragsformular bzw. die entsprechende Leistungsbeschreibung.
|
||||
|
||||
#### 1.13.12 Salvatorische Klausel
|
||||
|
||||
@@ -296,7 +296,7 @@ Kunden können im Rahmen der Nutzung des Dienstes benutzergenerierte Inhalte ers
|
||||
**(ii)** Der Kunde gewährt die Rechte nach den Abschnitten 3.3.3 bis 3.3.6 kostenlos und zu den in den entsprechenden Abschnitten angegebenen Zwecken, bis der Kunde die Kundeninhalte von den GitHub-Servern entfernt. Davon ausgenommen sind Inhalte, die der Kunde öffentlich veröffentlicht hat und für die externe Benutzer ein Forking vorgenommen haben. In diesem Fall gilt die Lizenz unbefristet, bis alle Forks von Kundeninhalten von den GitHub-Servern entfernt wurden. Lädt der Kunde Kundeninhalte hoch, für die bereits eine Lizenz besteht, die GitHub die erforderlichen Rechte zur Ausführung des Dienstes gewährt, ist keine weitere Lizenz erforderlich.
|
||||
|
||||
#### 3.3.3 Lizenzgewährung für GitHub
|
||||
Der Kunde gewährt GitHub das Recht, Kundeninhalte zu speichern, zu analysieren und anzuzeigen und gelegentlich Kopien zu erstellen, insoweit dies zur Bereitstellung des Dienstes erforderlich ist. Dazu zählt das Recht, Kundeninhalte in die GitHub-Datenbank zu kopieren und Sicherungen zu erstellen, Kundeninhalte dem Kunden und anderen anzuzeigen, denen der Kunde die Inhalte anzeigen möchte, Kundeninhalte für einen Suchindex oder auf andere Weise auf den GitHub-Servern zu analysieren, Kundeninhalte für externe Benutzer freizugeben, für die der Kunde die Inhalte freigeben möchte, und Kundeninhalte wiederzugeben, insoweit es sich um Musik, Videos usw. handelt. Diese Rechte gelten sowohl für öffentliche als auch private Repositorys. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb des Dienstes zu verwenden. Der Kunde gewährt GitHub die nötigen Rechte zur Verwendung von Kundeninhalten ohne Namensnennung und zur Durchführung angemessener Änderungen von Kundeninhalten, insoweit dies für die Bereitstellung des Dienstes erforderlich ist.
|
||||
Customer grants to GitHub the right to store, parse, and display Customer Content, and make incidental copies, only as necessary to provide the Service. Dazu zählt das Recht, Kundeninhalte in die GitHub-Datenbank zu kopieren und Sicherungen zu erstellen, Kundeninhalte dem Kunden und anderen anzuzeigen, denen der Kunde die Inhalte anzeigen möchte, Kundeninhalte für einen Suchindex oder auf andere Weise auf den GitHub-Servern zu analysieren, Kundeninhalte für externe Benutzer freizugeben, für die der Kunde die Inhalte freigeben möchte, und Kundeninhalte wiederzugeben, insoweit es sich um Musik, Videos usw. handelt. Diese Rechte gelten sowohl für öffentliche als auch private Repositorys. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb des Dienstes zu verwenden. Der Kunde gewährt GitHub die nötigen Rechte zur Verwendung von Kundeninhalten ohne Namensnennung und zur Durchführung angemessener Änderungen von Kundeninhalten, insoweit dies für die Bereitstellung des Dienstes erforderlich ist.
|
||||
|
||||
#### 3.3.4 Lizenzgewährung für externe Benutzer
|
||||
**(i)** Inhalte, die der Kunde öffentlich postet, darunter Issues, Kommentare und Beiträge in Repositorys externer Benutzer, können von anderen angezeigt werden. Indem der Kunde seine Repositorys für die öffentliche Anzeige konfiguriert, stimmt er zu, dass externe Benutzer die Repositorys des Kunden anzeigen und kopieren können.
|
||||
@@ -318,10 +318,13 @@ Der Kunde haftet für die Verwaltung des Zugriffs auf seine privaten Repositorys
|
||||
GitHub betrachtet Kundeninhalte in den privaten Repositorys des Kunden als vertrauliche Informationen des Kunden. GitHub sorgt nach Abschnitt 1.4 für den Schutz und die strikte Wahrung der Vertraulichkeit von Kundeninhalten in privaten Repositorys.
|
||||
|
||||
#### 3.4.3 Zugriff
|
||||
GitHub kann ausschließlich in folgenden Fällen auf private Repositorys des Kunden zugreifen: (i) aus Gründen des Supports mit dem Wissen und unter Zustimmung des Kunden oder (ii) wenn der Zugriff aus Sicherheitsgründen erforderlich ist. Der Kunde kann zusätzlichen Zugriff auf seine privaten Repositorys aktivieren. Beispielsweise kann der Kunde mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Kundeninhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Dienst oder Feature andere sein. GitHub behandelt Kundeninhalte in den privaten Repositorys des Kunden jedoch weiterhin als vertrauliche Informationen des Kunden. Sind für diese Dienste oder Features neben den Rechten, die für die Dienstbereitstellung erforderlich sind, zusätzliche Rechte erforderlich, gibt GitHub eine Erläuterung dieser Rechte.
|
||||
GitHub personnel may only access Customer’s Private Repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents).
|
||||
|
||||
#### 3.4.4 Ausschlüsse
|
||||
Hat GitHub Grund zu der Annahme, dass Inhalte eines privaten Repositorys gegen Gesetze oder diese Vereinbarung verstoßen, hat GitHub das Recht, auf die betreffenden Inhalte zuzugreifen und sie zu prüfen sowie zu entfernen. Darüber hinaus kann GitHub gesetzlich verpflichtet sein, Inhalte in privaten Repositorys des Kunden offenzulegen. Sofern GitHub nicht durch gesetzliche Auflagen oder in Reaktion auf eine Sicherheitsbedrohung oder ein sonstiges Sicherheitsrisiko anders gebunden ist, informiert GitHub über entsprechende Maßnahmen.
|
||||
Der Kunde kann zusätzlichen Zugriff auf seine privaten Repositorys aktivieren. Beispielsweise kann der Kunde mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Kundeninhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Dienst oder Feature andere sein. GitHub behandelt Kundeninhalte in den privaten Repositorys des Kunden jedoch weiterhin als vertrauliche Informationen des Kunden. Sind für diese Dienste oder Features neben den Rechten, die für die Dienstbereitstellung erforderlich sind, zusätzliche Rechte erforderlich, gibt GitHub eine Erläuterung dieser Rechte.
|
||||
|
||||
Darüber hinaus können wir [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte Ihrer privaten Repositorys offenzulegen.
|
||||
|
||||
GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
|
||||
|
||||
### 3.5. Urheberrechtsvermerke
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
Effective date: July 22, 2020
|
||||
Effective date: November 16, 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.
|
||||
|
||||
@@ -150,23 +150,39 @@ Wir verkaufen Ihre personenbezogenen Benutzerinformationen **nicht** gegen eine
|
||||
|
||||
Bitte beachten Sie: Der California Consumer Privacy Act of 2018 ("CCPA") verpflichtet Unternehmen, in ihren Datenschutzrichtlinien anzugeben, ob sie personenbezogene Daten gegen eine finanzielle oder sonstige Gegenleistung offenlegen. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. Weitere Informationen über den CCPA und wie wir diesen umsetzen, finden Sie [hier](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act).
|
||||
|
||||
### Weitere wichtige Informationen
|
||||
### Repository-Inhalt
|
||||
|
||||
#### Repository-Inhalt
|
||||
#### Access to private repositories
|
||||
|
||||
Personal von GitHub [haben keinen Zugang zu privaten Repositorys](/github/site-policy/github-terms-of-service#e-private-repositories), es sei denn, dies ist aus Sicherheitsgründen, zur Unterstützung des Repository-Eigentümers bei einer Supportanfrage, zur Aufrechterhaltung der Integrität des Dienstes oder zur Erfüllung unserer rechtlichen Verpflichtungen erforderlich. However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, or other content known to violate our Terms, such as violent extremist or terrorist content or child exploitation imagery based on algorithmic fingerprinting techniques. Unsere Nutzungsbedingungen enthalten [weitere Details](/github/site-policy/github-terms-of-service#e-private-repositories).
|
||||
If your repository is private, you control the access to your Content. If you include User Personal Information or Sensitive Personal Information, that information may only be accessible to GitHub in accordance with this Privacy Statement. GitHub personnel [do not access private repository content](/github/site-policy/github-terms-of-service#e-private-repositories) except for
|
||||
- security purposes
|
||||
- to assist the repository owner with a support matter
|
||||
- to maintain the integrity of the Service
|
||||
- to comply with our legal obligations
|
||||
- if we have reason to believe the contents are in violation of the law, or
|
||||
- mit Ihrer Zustimmung.
|
||||
|
||||
Wenn Ihr Repository öffentlich ist, kann jeder seinen Inhalt anzeigen. Wenn Sie private, vertrauliche oder [Sensible personenbezogene Daten](https://gdpr-info.eu/art-9-gdpr/), wie z.B. E-Mail-Adressen oder Passwörter, in Ihr öffentliches Repository eingeben, können diese Informationen von Suchmaschinen indexiert oder von Dritten verwendet werden.
|
||||
However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, known vulnerabilities in dependencies, or other content known to violate our Terms of Service, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques (collectively, "automated scanning"). Our Terms of Service provides more details on [private repositories](/github/site-policy/github-terms-of-service#e-private-repositories).
|
||||
|
||||
Please note, you may choose to disable certain access to your private repositories that is enabled by default as part of providing you with the Service (for example, automated scanning needed to enable Dependency Graph and Dependabot alerts).
|
||||
|
||||
GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
|
||||
|
||||
#### Public repositories
|
||||
|
||||
Wenn Ihr Repository öffentlich ist, kann jeder seinen Inhalt anzeigen. If you include User Personal Information, [Sensitive Personal Information](https://gdpr-info.eu/art-9-gdpr/), or confidential information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties.
|
||||
|
||||
Weitere Informationen finden Sie unter [Personenbezogene Benutzerdaten in öffentlichen Repositorys](/github/site-policy/github-privacy-statement#public-information-on-github).
|
||||
|
||||
### Weitere wichtige Informationen
|
||||
|
||||
#### Öffentliche Informationen auf GitHub
|
||||
|
||||
Viele GitHub-Dienste und -Funktionen sind öffentlich zugänglich. Wenn Ihre Inhalte öffentlich zugänglich sind, können Dritte auf diese in Übereinstimmung mit unseren Nutzungsbedingungen zugreifen und diese verwenden, z. B. indem Sie Ihr Profil oder Ihre Repositorys anzeigen oder Daten über unser API abrufen. Wir verkaufen diese Inhalte nicht; sie gehören Ihnen. Wir gestatten es jedoch Dritten, wie z.B. Forschungsorganisationen oder Archiven, öffentlich zugängliche GitHub-Informationen zu sammeln. Es ist bekannt, dass andere Dritte, wie z.B. Datenbroker, ebenfalls mittels Scraping auf GitHub zurückgreifen und Daten sammeln.
|
||||
|
||||
Ihre personenbezogenen Benutzerdaten in Verbindung mit Ihren Inhalten könnten von Dritten im Rahmen dieser Erfassungen von GitHub-Daten gesammelt werden. Wenn Sie nicht möchten, dass Ihre personenbezogenen Benutzerdaten in den GitHub-Datensammlungen von Dritten erscheinen, machen Sie Ihre personenbezogenen Benutzerdaten bitte nicht öffentlich zugänglich und stellen Sie sicher, dass [Ihre E-Mail-Adresse in Ihrem Benutzerprofil](https://github.com/settings/emails) und in Ihren [Git Commit-Einstellungen als privat konfiguriert ist](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Wir setzen derzeit standardmäßig die E-Mail-Adresse der Benutzer auf privat, aber alte GitHub-Benutzer müssen möglicherweise ihre Einstellungen aktualisieren.
|
||||
|
||||
Wenn Sie GitHub-Daten zusammenstellen möchten, müssen Sie unsere Nutzungsbedingungen in Bezug auf [Scraping](/github/site-policy/github-acceptable-use-policies#5-scraping-and-api-usage-restrictions) und [Datenschutz](/github/site-policy/github-acceptable-use-policies#6-privacy) erfüllen, und Sie dürfen alle öffentlich zugänglichen personenbezogenen Daten, die Sie sammeln, nur für den Zweck verwenden, für den unser Benutzer dies autorisiert hat. Wenn z. B. ein GitHub-Benutzer eine E-Mail-Adresse zum Zwecke der Identifizierung und Zuordnung öffentlich zugänglich gemacht hat, dürfen Sie Sie diese E-Mail-Adresse nicht für kommerzielle Werbung verwenden. Wir erwarten von Ihnen, dass Sie einen angemessenen Schutz aller personenbezogenen Daten von Benutzern, die Sie von dem Dienst erfasst haben garantieren, und Beschwerden, Aufforderungen zur Löschung und Kontaktverbote von uns oder anderen Benutzern umgehend beantworten.
|
||||
If you would like to compile GitHub data, you must comply with our Terms of Service regarding [information usage](/github/site-policy/github-acceptable-use-policies#5-information-usage-restrictions) and [privacy](/github/site-policy/github-acceptable-use-policies#6-privacy), and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling User Personal Information, such as to recruiters, headhunters, and job boards, or for commercial advertising. Wir erwarten von Ihnen, dass Sie einen angemessenen Schutz aller personenbezogenen Daten von Benutzern, die Sie von dem Dienst erfasst haben garantieren, und Beschwerden, Aufforderungen zur Löschung und Kontaktverbote von uns oder anderen Benutzern umgehend beantworten.
|
||||
|
||||
Ebenso können Projekte auf GitHub öffentlich zugängliche personenbezogene Benutzerdaten enthalten, die im Rahmen des kollaborativen Prozesses erfasst werden. Wenn Sie eine Beschwerde über persönliche Benutzerdaten auf GitHub haben, lesen Sie bitte unseren Abschnitt [Beilegung von Beschwerden](/github/site-policy/github-privacy-statement#resolving-complaints).
|
||||
|
||||
@@ -219,7 +235,7 @@ Die von Ihnen angegebene E-Mail-Adresse [über Ihre Git-Commit-Einstellungen](/g
|
||||
|
||||
#### Cookies
|
||||
|
||||
GitHub verwendet Cookies, um die Interaktion mit unserem Dienst einfach und sinnvoll zu machen. Cookies sind kleine Textdateien, die oft von Websites auf Computer-Festplatten oder mobilen Geräten von Besuchern gespeichert werden. Wir verwenden Cookies (und ähnliche Technologien wie HTML5 localStorage), um Sie eingeloggt zu halten, Ihre Präferenzen zu speichern und Informationen für die zukünftige Entwicklung von GitHub bereitzustellen. Wir verwenden Cookies aus Sicherheitsgründen, um ein Gerät zu identifizieren. 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 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.
|
||||
|
||||
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.
|
||||
|
||||
@@ -300,7 +316,7 @@ Im unwahrscheinlichen Fall, dass es zu einem Streit zwischen Ihnen und GitHub ü
|
||||
|
||||
### Änderungen an unserer Datenschutzerklärung
|
||||
|
||||
GitHub kann unsere Datenschutzerklärung von Zeit zu Zeit ändern, wobei die meisten Änderungen eher geringfügig sein dürften. Wir werden die Benutzer über unsere Website mindestens 30 Tage vor Inkrafttreten der Änderung über wesentliche Änderungen dieser Datenschutzerklärung informieren, indem wir eine Benachrichtigung auf unserer Homepage veröffentlichen oder E-Mails an die primäre E-Mail-Adresse versenden, die in Ihrem GitHub-Konto angegeben ist. Wir werden auch unser [Websiterichtlinien-Repository](https://github.com/github/site-policy/) aktualisieren, das alle Änderungen an dieser Richtlinie nachverfolgt. Für Änderungen an dieser Datenschutzerklärung, die keine wesentlichen Änderungen sind oder ihre Rechte nicht beeinträchtigen, empfehlen wir Benutzern, regelmäßig unser Websiterichtlinien-Repository zu besuchen.
|
||||
GitHub kann unsere Datenschutzerklärung von Zeit zu Zeit ändern, wobei die meisten Änderungen eher geringfügig sein dürften. Wir werden die Benutzer über unsere Website mindestens 30 Tage vor Inkrafttreten der Änderung über wesentliche Änderungen dieser Datenschutzerklärung informieren, indem wir eine Benachrichtigung auf unserer Homepage veröffentlichen oder E-Mails an die primäre E-Mail-Adresse versenden, die in Ihrem GitHub-Konto angegeben ist. Wir werden auch unser [Websiterichtlinien-Repository](https://github.com/github/site-policy/) aktualisieren, das alle Änderungen an dieser Richtlinie nachverfolgt. For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently.
|
||||
|
||||
### Lizenz
|
||||
|
||||
|
||||
@@ -32,11 +32,11 @@ Vielen Dank für die Nutzung von GitHub! Wir freuen uns, dass Sie hier sind. Bit
|
||||
| [N. Gewährleistungsausschluss](#n-disclaimer-of-warranties) | Wir bieten unseren Service so an, wie er ist, und wir geben keine Versprechungen oder Garantien für diesen Service. **Bitte lesen Sie diesen Abschnitt sorgfältig durch; es sollte Ihnen klar sein, was Sie erwartet.** |
|
||||
| [O. Haftungsbeschränkung](#o-limitation-of-liability) | Wir sind nicht haftbar für Schäden oder Verluste, die sich aus Ihrer Nutzung oder der Unfähigkeit zur Nutzung des Dienstes oder anderweitig aus dieser Vereinbarung ergeben. **Bitte lesen Sie diesen Abschnitt sorgfältig durch; er schränkt unsere Verpflichtungen Ihnen gegenüber ein.** |
|
||||
| [P. Freistellung und Schadloshaltung](#p-release-and-indemnification) | Sie tragen die volle Verantwortung für Ihre Nutzung des Dienstes. |
|
||||
| [Q. Änderungen an diesen Nutzungsbedingungen](#q-changes-to-these-terms) | Wir können diese Vereinbarung ändern, aber wir werden Sie 30 Tage vorher über Änderungen informieren, die Ihre Rechte beeinträchtigen. |
|
||||
| [Q. Änderungen an diesen Nutzungsbedingungen](#q-changes-to-these-terms) | We may modify this agreement, but we will give you 30 days' notice of material changes. |
|
||||
| [R. Sonstiges](#r-miscellaneous) | Bitte beachten Sie diesen Abschnitt für rechtliche Einzelheiten einschließlich unserer Rechtswahl. |
|
||||
|
||||
### Die GitHub-Nutzungsbedingungen
|
||||
Datum des Inkrafttretens: 2. April 2020
|
||||
Effective date: November 16, 2020
|
||||
|
||||
|
||||
### A. Definitionen
|
||||
@@ -98,7 +98,7 @@ Sie erklären sich damit einverstanden, dass Sie unter keinen Umständen gegen u
|
||||
Sie können im Rahmen der Nutzung des Dienstes benutzergenerierte Inhalte erstellen oder hochladen. Sie sind allein verantwortlich für den Inhalt und für Schäden, die sich aus nutzergenerierten Inhalten ergeben, die Sie veröffentlichen, hochladen, verlinken oder anderweitig über den Dienst zur Verfügung stellen, unabhängig von der Form dieser Inhalte. Wir haften nicht für die Veröffentlichung oder den falschen Gebrauch benutzergenerierter Inhalte.
|
||||
|
||||
#### 2. GitHub kann Inhalte entfernen
|
||||
We do not pre-screen User-Generated Content, but we have the right (though not the obligation) to refuse or remove any User-Generated Content that, in our sole discretion, violates any [GitHub terms or policies](/github/site-policy).
|
||||
We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or [GitHub terms or policies](/github/site-policy). User-Generated Content displayed on GitHub for mobile may be subject to mobile app stores' additional terms.
|
||||
|
||||
#### 3. Eigentumsrechte an Inhalten, Recht auf Veröffentlichung und Lizenzgewährung
|
||||
Sie verbleiben Eigentümer Ihrer Inhalte und sind für diese verantwortlich. Wenn Sie etwas veröffentlichen, das Sie nicht selbst erstellt haben oder für das Sie nicht die Rechte besitzen, erklären Sie sich damit einverstanden, dass Sie für alle Inhalte, die Sie veröffentlichen, verantwortlich sind; dass Sie nur Inhalte einreichen, zu deren Veröffentlichung Sie berechtigt sind; und dass Sie alle Lizenzen Dritter in Bezug auf Inhalte, die Sie veröffentlichen vollständig einhalten werden.
|
||||
@@ -106,9 +106,9 @@ Sie verbleiben Eigentümer Ihrer Inhalte und sind für diese verantwortlich. Wen
|
||||
Da Sie weiterhin das Eigentum und die Verantwortung für Ihre Inhalte behalten, müssen Sie uns – und anderen GitHub-Benutzern – bestimmte Berechtigungen erteilen, die in den Abschnitten D.4 - D7. Diese Lizenzerteilungen gelten für Ihre Inhalte. Laden Sie Inhalte hoch, für die bereits eine Lizenz besteht, die GitHub die erforderlichen Rechte zur Ausführung des Dienstes gewährt, ist keine weitere Lizenz erforderlich. Sie verstehen, dass Sie keine Zahlung für eines der in den Abschnitten D.4 — D.7 gewährten Rechte erhalten. Die Lizenzen, die Sie uns gewähren, enden, wenn Sie Ihre Inhalte von unseren Servern entfernen, es sei denn er wurde von anderen Benutzern geforkt.
|
||||
|
||||
#### 4. Lizenzvergabe an uns
|
||||
Wir müssen gesetzlich befugt sein, Dinge wie das Hosten Ihrer Inhalte, deren Veröffentlichung und Weitergabe durchzuführen. Sie gewähren uns und unseren Rechtsnachfolgern das Recht, Ihre Inhalte zu speichern, zu analysieren und anzuzeigen und bei Bedarf Nebenkopien anzustellen, um die Website zu erstellen und den Dienst bereitzustellen. Dies schließt das Recht ein, Aktivitäten wie das Kopieren in unsere Datenbank und die Anfertigung von Sicherungskopien durchzuführen, sie Ihnen und anderen Benutzern zu zeigen, sie in einen Suchindex zu übernehmen oder anderweitig auf unseren Servern zu analysieren, sie mit anderen Benutzern zu teilen und sie vorzuführen, falls es sich bei Ihren Inhalten um Musik oder Videos handelt.
|
||||
Wir müssen gesetzlich befugt sein, Dinge wie das Hosten Ihrer Inhalte, deren Veröffentlichung und Weitergabe durchzuführen. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video.
|
||||
|
||||
Diese Lizenz gewährt GitHub nicht das Recht, Ihre Inhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb unseres bereitgestellten Dienstes zu verwenden.
|
||||
This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the [GitHub Arctic Code Vault and GitHub Archive Program](https://archiveprogram.github.com/).
|
||||
|
||||
#### 5. Lizenzgewährung für andere Benutzer
|
||||
Benutzergenerierte Inhalte, die Sie öffentlich posten, darunter Issues, Kommentare und Beiträge in Repositorys externer Benutzer, können von anderen angezeigt werden. Indem Sie festlegen, dass Ihre Repositorys öffentlich angezeigt werden, erklären Sie sich damit einverstanden, dass andere Ihre Repositorys anzeigen und „forken" können (das bedeutet, dass andere ihre eigenen Kopien von Inhalten aus Ihren Repositorys in von ihnen kontrollierte Repositorys erstellen können).
|
||||
@@ -116,7 +116,7 @@ Benutzergenerierte Inhalte, die Sie öffentlich posten, darunter Issues, Komment
|
||||
Konfigurieren Sie Ihre Pages und Repositorys für die öffentliche Anzeige, gewähren Sie allen GitHub-Benutzern eine nicht exklusive, weltweite Lizenz zur Verwendung, Anzeige und Wiedergabe Ihrer Inhalte über den GitHub-Dienst und zur Reproduktion von Ihrer Inhalte ausschließlich auf GitHub, insoweit dies nach den von GitHub bereitgestellten Funktionen zulässig ist (beispielsweise durch Forking). Sie können weitere Rechte gewähren, wenn der Sie [eine Lizenz einführen](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Wenn Sie Inhalte hochladen, die Sie nicht selber erstellt haben oder die Ihnen nicht gehören, haften Sie dafür sicherzustellen, dass die von Ihnen hochgeladenen Inhalte nach den Bedingungen lizenziert sind, mit denen diese Rechte GitHub-Benutzern gewährt werden.
|
||||
|
||||
#### 6. Beiträge im Rahmen einer Repository-Lizenz
|
||||
Jedesmal wenn Sie einen Beitrag zu einem Repository mit einem Lizenzhinweis machen, lizenzieren Sie Ihren Beitrag zu denselben Bedingungen und erklären, dass Sie das Recht haben, den entsprechenden Beitrag zu diesen Bedingungen zu lizenzieren. Wenn Sie über eine gesonderte Vereinbarung zur Lizenzierung Ihrer Beiträge nach anderen Bedingungen wie z. B. einer Mitwirkungslizenzvereinbarung verfügen, hat die entsprechende Vereinbarung Vorrang.
|
||||
Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede.
|
||||
|
||||
Funktioniert das nicht bereits so? Ja. Dies wird weithin als die Norm in der Open-Source-Community akzeptiert; es wird üblicherweise mit der Abkürzung "inbound=outbound" bezeichnet. Wir machen es nur explizit.
|
||||
|
||||
@@ -126,7 +126,7 @@ Sie behalten alle Urheberpersönlichkeitsrechte an Ihren Inhalten, die Sie hochl
|
||||
Soweit diese Vereinbarung durch anwendbares Recht nicht durchsetzbar ist gewähren Sie GitHub die Rechte, die wir benötigen, um Ihren Inhalt ohne Nennung zu nutzen und angemessene Anpassungen an Ihren Inhalten vorzunehmen, wenn dies für die Darstellung der Website und die Bereitstellung der Dienste erforderlich ist.
|
||||
|
||||
### E. Private Repositorys
|
||||
**Kurzversion:** *Sie haben möglicherweise Zugriff auf private Repositorys. Wir behandeln den Inhalt privater Repositorys vertraulich und greifen nur aus Supportgründen, mit Ihrer Zustimmung oder wenn dies aus Sicherheitsgründen erforderlich ist, darauf zu.*
|
||||
**Short version:** *We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.*
|
||||
|
||||
#### 1. Kontrolle privater Repositorys
|
||||
Einige Konten verfügen möglicherweise über private Repositorys, die es dem Benutzer ermöglichen, den Zugriff auf Inhalte zu steuern.
|
||||
@@ -135,15 +135,14 @@ Einige Konten verfügen möglicherweise über private Repositorys, die es dem Be
|
||||
GitHub betrachtet den Inhalt privater Repositorys als vertraulich. GitHub schützt die Inhalte privater Repositorys vor unbefugter Nutzung, Unbefugtem Zugriff oder Offenlegung in der gleichen Weise, die wir verwenden würden, um unsere eigenen vertraulichen Informationen ähnlicher Art, und in keinem Fall mit weniger als einem angemessenen Maß an Sorgfalt, zu schützen.
|
||||
|
||||
#### 3. Zugriff
|
||||
GitHub-Mitarbeiter dürfen nur in den folgenden Situationen auf den Inhalt Ihrer privaten Repositorys zugreifen:
|
||||
- Mit Ihrer Zustimmung und Ihrem Wissen, aus Supportgründen. Wenn GitHub aus Supportgründen auf ein privates Repository zugreift, tun wir dies nur mit der Zustimmung und dem Wissen des Eigentümers.
|
||||
- Wenn der Zugriff aus Sicherheitsgründen erforderlich ist, einschließlich wenn dies zur Aufrechterhaltung der kontinuierlichen Vertraulichkeit, Integrität, Verfügbarkeit und Belastbarkeit der Systeme und Dienste von GitHub erforderlich ist.
|
||||
GitHub personnel may only access the content of your private repositories in the situations described in our [Privacy Statement](/github/site-policy/github-privacy-statement#repository-contents).
|
||||
|
||||
Sie können zusätzlichen Zugriff auf Ihre privaten Repositorys aktivieren. Ein Beispiel:
|
||||
- Sie können beispielsweise mehrere GitHub-Dienste oder -Features aktivieren, für die zusätzliche Rechte für Ihre Inhalte in privaten Repositorys erforderlich sind. Diese Rechte können je nach Service oder Funktion variieren, aber GitHub wird Ihre privaten Repository-Inhalte weiterhin vertraulich behandeln. Sind für diese Dienste oder Features neben den Rechten, die für die Bereitstellung des GitHub-Dienstes erforderlich sind, zusätzliche Rechte erforderlich, geben wir eine Erläuterung dieser Rechte.
|
||||
|
||||
#### 4. Ausnahmen
|
||||
Haben wir Grund zu der Annahme, dass Inhalte eines privaten Repositorys gegen Gesetze oder diese Bedingungen verstoßen, haben wir das Recht, auf die betreffenden Inhalte zuzugreifen und sie zu prüfen sowie zu entfernen. Darüber hinaus können wir [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte Ihrer privaten Repositorys offenzulegen.
|
||||
Darüber hinaus können wir [gesetzlich verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure) Inhalte Ihrer privaten Repositorys offenzulegen.
|
||||
|
||||
GitHub will provide notice regarding our access to private repository content, unless [for legal disclosure](/github/site-policy/github-privacy-statement#for-legal-disclosure), to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
|
||||
|
||||
### F. Urheberrechtsverletzungen und DMCA-Richtlinie
|
||||
Wenn Sie glauben, dass Inhalte auf unserer Website gegen Ihr Urheberrecht verstoßen kontaktieren Sie uns bitte in Übereinstimmung mit unserer [Digital Millennium Copyright Act Policy](/articles/dmca-takedown-policy/). Wenn Sie ein Urheberrechtsinhaber sind und der Meinung sind, dass Inhalte auf GitHub Ihre Rechte verletzen, kontaktieren Sie uns bitte über [unser dafür vorgesehenes DMCA-Formular](https://github.com/contact/dmca) oder per E-Mail unter copyright@github.com. Die Zusendung einer falschen oder leichtfertigen Takedown-Mitteilung kann rechtliche Konsequenzen haben. Bevor Sie eine Takedown-Anfrage senden, müssen Sie rechtliche Verwendungszwecke wie faire Nutzung und lizenzierte Nutzungen in Betracht ziehen.
|
||||
@@ -286,9 +285,9 @@ Wenn Sie eine Streitigkeit mit einem oder mehreren Benutzer haben, entbinden Sie
|
||||
Sie erklären sich damit einverstanden, uns in Bezug auf alle Ansprüche, Verbindlichkeiten und Ausgaben, einschließlich Anwaltskosten, die sich aus Ihrer Nutzung der Website und des Dienstes ergeben, zu befreien, zu verteidigen und schadlos zu halten, unter anderem aufgrund Ihrer Verletzung diesen Nutzungsbedingungen, vorausgesetzt, dass GitHub (1) Sie unverzüglich schriftlich über den Anspruch, die Forderung, die Klage oder das Verfahren informiert; (2) Ihnen die alleinige Kontrolle über die Verteidigung und Beilegung des Anspruchs, der Forderung, der Klage oder des Verfahrens gibt (vorausgesetzt, dass Sie keinen Anspruch, keine Forderung, keine Klage oder kein Verfahren beilegen dürfen, solange diese Beilegung GitHub nicht bedingungslos von jeglicher Haftung entbindet); und (3) Ihnen auf Ihre Kosten jede angemessene Unterstützung gewährt.
|
||||
|
||||
### Q. Änderungen dieser Bedingungen
|
||||
**Kurzversion:** *Wir möchten, dass unsere Benutzer über wichtige Änderungen unserer Bedingungen informiert werden, aber einige Änderungen sind nicht so wichtig – wir wollen Sie nicht jedes Mal stören, wenn wir einen Tippfehler korrigieren. Obwohl wir diese Vereinbarung jederzeit ändern können, werden wir die Benutzer über alle Änderungen informieren, die Ihre Rechte beeinträchtigen, und Ihnen Zeit geben, sich darauf einzustellen.*
|
||||
**Kurzversion:** *Wir möchten, dass unsere Benutzer über wichtige Änderungen unserer Bedingungen informiert werden, aber einige Änderungen sind nicht so wichtig – wir wollen Sie nicht jedes Mal stören, wenn wir einen Tippfehler korrigieren. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.*
|
||||
|
||||
Wir behalten uns das Recht vor, diese Nutzungsbedingungen jederzeit nach unserem alleinigem Ermessen zu ändern, und aktualisieren diese Vereinbarung im Fall entsprechender Änderungen. Wir informieren unsere Benutzer über wesentliche Änderungen dieser Vereinbarung wie z. B. Preisänderungen mindestens 30 Tage vor Inkrafttreten der Änderung durch Veröffentlichung einer Mitteilung auf unserer Website. Bei geringfügigen Änderungen stellt Ihre fortgesetzte Nutzung der Website die Zustimmung zu den Änderungen dieser Nutzungsbedingungen dar. Alle Änderungen dieser Bedingungen können Sie in unserem Repository [Site Policy](https://github.com/github/site-policy) einsehen.
|
||||
Wir behalten uns das Recht vor, diese Nutzungsbedingungen jederzeit nach unserem alleinigem Ermessen zu ändern, und aktualisieren diese Vereinbarung im Fall entsprechender Änderungen. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. Alle Änderungen dieser Bedingungen können Sie in unserem Repository [Site Policy](https://github.com/github/site-policy) einsehen.
|
||||
|
||||
Wir behalten uns das Recht vor, die Website (oder einen Teil davon) zu gegebener Zeit und ohne Ankündigung vorübergehend oder dauerhaft zu modifizieren oder einzustellen.
|
||||
|
||||
|
||||
@@ -41,12 +41,12 @@ In Unterhaltungen auf {% data variables.product.product_name %} werden Verweise
|
||||
|
||||
Verweise auf den SHA-Hash eines Commits werden zum Committen auf {% data variables.product.product_name %} automatisch in verkürzte Links umgewandelt.
|
||||
|
||||
| Verweistyp | Rohverweis | Kurzlink |
|
||||
| --------------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
|
||||
| Commit-URL | https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| Benutzer@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| Benutzername/Repository@SHA | jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord/sheetsee.js@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| Verweistyp | Rohverweis | Kurzlink |
|
||||
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
|
||||
| Commit-URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| Benutzer@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| `Benutzername/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
|
||||
### Benutzerdefinierte automatische Verknüpfungen von externen Ressourcen
|
||||
|
||||
|
||||
@@ -8,19 +8,24 @@ versions:
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free.
|
||||
**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
{% data reusables.package_registry.container-registry-feature-highlights %}
|
||||
|
||||
To share context about your package's use, you can link a repository to your container image on {% data variables.product.prodname_dotcom %}. For more information, see "[Connecting a repository to a container image](/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image)."
|
||||
|
||||
### Unterstützte Formate
|
||||
|
||||
The {% data variables.product.prodname_container_registry %} currently only supports Docker images.
|
||||
The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
|
||||
|
||||
* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
|
||||
* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)
|
||||
|
||||
#### Manifest Lists/Image Indexes
|
||||
|
||||
{% data variables.product.prodname_github_container_registry %} also supports [Docker Manifest List](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)/[OCI Image Index](https://github.com/opencontainers/image-spec/blob/79b036d80240ae530a8de15e1d21c7ab9292c693/image-index.md) formats which are defined in the Docker V2, Schema 2 and OCI image specifications.
|
||||
|
||||
### Visibility and access permissions for container images
|
||||
|
||||
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: Enabling improved container support
|
||||
intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)“.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Enabling {% data variables.product.prodname_github_container_registry %} for your personal account
|
||||
|
||||
Once {% data variables.product.prodname_github_container_registry %} is enabled for your personal user account, you can publish containers to {% data variables.product.prodname_github_container_registry %} owned by your user account.
|
||||
|
||||
To use {% data variables.product.prodname_github_container_registry %} within an organization, the organization owner must enable the feature for organization members.
|
||||
|
||||
{% data reusables.feature-preview.feature-preview-setting %}
|
||||
2. On the left, select "Improved container support", then click **Enable**. 
|
||||
|
||||
### Enabling {% data variables.product.prodname_github_container_registry %} for your organization account
|
||||
|
||||
Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
4. On the left, click **Packages**.
|
||||
5. Under "Improved container support", select "Enable improved container support" and click **Save**. 
|
||||
6. Under "Container creation", choose whether you want to enable the creation of public and/or private container images.
|
||||
- To enable organization members to create public container images, click **Public**.
|
||||
- To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images. For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)."
|
||||
|
||||
|
||||
@@ -8,8 +8,8 @@ versions:
|
||||
{% data reusables.package_registry.container-registry-beta %}
|
||||
|
||||
{% link_in_list /about-github-container-registry %}
|
||||
{% link_in_list /enabling-improved-container-support %}
|
||||
{% link_in_list /core-concepts-for-github-container-registry %}
|
||||
{% link_in_list /migrating-to-github-container-registry-for-docker-images %}
|
||||
{% link_in_list /enabling-github-container-registry-for-your-organization %}
|
||||
|
||||
For more information about configuring, deleting, pushing, or pulling container images, see "[Managing container images with {% data variables.product.prodname_github_container_registry %}](/packages/managing-container-images-with-github-container-registry)."
|
||||
|
||||
@@ -31,6 +31,8 @@ The domain for the {% data variables.product.prodname_container_registry %} is `
|
||||
|
||||
### Authenticating with the container registry
|
||||
|
||||
{% data reusables.package_registry.feature-preview-for-container-registry %}
|
||||
|
||||
You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}.
|
||||
|
||||
{% data reusables.package_registry.authenticate_with_pat_for_container_registry %}
|
||||
@@ -72,6 +74,8 @@ To move Docker images that you host on {% data variables.product.prodname_regist
|
||||
|
||||
### Updating your {% data variables.product.prodname_actions %} workflow
|
||||
|
||||
{% data reusables.package_registry.feature-preview-for-container-registry %}
|
||||
|
||||
If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers.
|
||||
|
||||
1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)."
|
||||
|
||||
@@ -24,7 +24,7 @@ If you have admin permissions to an organization-owned container image, you can
|
||||
|
||||
If your package is owned by an organization and private, then you can only give access to other organization members or teams.
|
||||
|
||||
For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)."
|
||||
For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)."
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-org-level %}
|
||||
1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. 
|
||||
@@ -54,7 +54,7 @@ When you first publish a package, the default visibility is private and only you
|
||||
|
||||
A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
|
||||
|
||||
For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)."
|
||||
For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)."
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-org-level %}
|
||||
5. Under "Danger Zone", choose a visibility setting:
|
||||
|
||||
@@ -16,8 +16,6 @@ To delete a container image, you must have admin permissions to the container im
|
||||
|
||||
When deleting public packages, be aware that you may break projects that depend on your package.
|
||||
|
||||
|
||||
|
||||
### Reserved package versions and names
|
||||
|
||||
{% data reusables.package_registry.package-immutability %}
|
||||
|
||||
@@ -8,7 +8,7 @@ versions:
|
||||
|
||||
{% data reusables.package_registry.container-registry-beta %}
|
||||
|
||||
To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)."
|
||||
To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)."
|
||||
|
||||
### Bei {% data variables.product.prodname_github_container_registry %} authentifizieren
|
||||
|
||||
|
||||
@@ -26,6 +26,8 @@ When you create a {% data variables.product.prodname_actions %} workflow, you ca
|
||||
|
||||
{% data reusables.package_registry.container-registry-beta %}
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### Pakete anzeigen
|
||||
@@ -34,17 +36,17 @@ You can configure webhooks to subscribe to package-related events, such as when
|
||||
|
||||
#### About package permissions and visibility
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
| | Package registries | {% data variables.product.prodname_github_container_registry %}
|
||||
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Hosting locations | You can host multiple packages in one repository. | You can host multiple container images in one organization or user account. |
|
||||
| Permissions | {{ site.data.reusables.package_registry.public-or-private-packages }} You can use {{ site.data.variables.product.prodname_dotcom }} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. |
|
||||
| | Package registries | {% data variables.product.prodname_github_container_registry %}
|
||||
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Hosting locations | You can host multiple packages in one repository. | You can host multiple container images in one organization or user account. |
|
||||
| Permissions | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. |
|
||||
Visibility | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | Anonymous access | N/A | You can access public container images anonymously.
|
||||
|
||||
{% else %}
|
||||
| | Package registries |
|
||||
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Hosting locations | You can host multiple packages in one repository. |
|
||||
| Permissions | {{ site.data.reusables.package_registry.public-or-private-packages }} You can use {{ site.data.variables.product.prodname_dotcom }} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. |
|
||||
| | Package registries |
|
||||
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Hosting locations | You can host multiple packages in one repository. |
|
||||
| Permissions | {% data reusables.package_registry.public-or-private-packages %} You can use {% data variables.product.prodname_dotcom %} roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version. |
|
||||
| Visibility | {% data reusables.package_registry.public-or-private-packages %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -37,12 +37,22 @@ $ curl -u <em>username</em>:<em>token</em> {% data variables.product.api_url_pre
|
||||
|
||||
This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features.
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion %}
|
||||
#### Via username and password
|
||||
|
||||
{% data reusables.apps.deprecating_password_auth %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
To use Basic Authentication with the {% data variables.product.product_name %} API, simply send the username and password associated with the account.
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% data variables.product.prodname_dotcom %} API with an API token, such as an OAuth access token, GitHub App installation access token, or personal access token, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion %}
|
||||
To use Basic Authentication with the
|
||||
{% data variables.product.product_name %} API, simply send the username and
|
||||
password associated with the account.
|
||||
|
||||
For example, if you're accessing the API via [cURL][curl], the following command would authenticate you if you replace `<username>` with your {% data variables.product.product_name %} username. (cURL will prompt you to enter the password.)
|
||||
|
||||
@@ -88,14 +98,13 @@ The value `organizations` is a comma-separated list of organization IDs for orga
|
||||
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
### Working with two-factor authentication
|
||||
|
||||
{% data reusables.apps.deprecating_password_auth %}
|
||||
|
||||
When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a personal access token or OAuth token instead of your username and password.
|
||||
|
||||
You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}with [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %} or use the "[Create a new authorization][create-access]" endpoint in the OAuth Authorizations API to generate a new OAuth token. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the GitHub API. The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.
|
||||
When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a personal access token{% if enterpriseServerVersions contains currentVersion %} or OAuth token instead of your username and password{% endif %}.
|
||||
|
||||
You can generate a new personal access token {% if currentVersion == "free-pro-team@latest" %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% if enterpriseServerVersions contains currentVersion %} or with the "\[Create a new authorization\]\[/rest/reference/oauth-authorizations#create-a-new-authorization\]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% data variables.product.prodname_dotcom %} API.{% if enterpriseServerVersions contains currentVersion %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion %}
|
||||
#### Using the OAuth Authorizations API with two-factor authentication
|
||||
|
||||
When you make calls to the OAuth Authorizations API, Basic Authentication requires that you use a one-time password (OTP) and your username and password instead of tokens. When you attempt to authenticate with the OAuth Authorizations API, the server will respond with a `401 Unauthorized` and one of these headers to let you know that you need a two-factor authentication code:
|
||||
@@ -114,7 +123,6 @@ $ curl --request POST \
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
[create-access]: /v3/oauth_authorizations/#create-a-new-authorization
|
||||
[curl]: http://curl.haxx.se/
|
||||
[oauth-auth]: /v3/#authentication
|
||||
[personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line
|
||||
|
||||
@@ -135,9 +135,9 @@ $ curl -i {% data variables.product.api_url_pre %} -u foo:bar
|
||||
After detecting several requests with invalid credentials within a short period, the API will temporarily reject all authentication attempts for that user (including ones with valid credentials) with `403 Forbidden`:
|
||||
|
||||
```shell
|
||||
$ curl -i {% data variables.product.api_url_pre %} -u valid_username:valid_password
|
||||
$ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
|
||||
-u <em>valid_username</em>:<em>valid_token</em> {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u <em>valid_username</em>:<em>valid_password</em> {% endif %}
|
||||
> HTTP/1.1 403 Forbidden
|
||||
|
||||
> {
|
||||
> "message": "Maximum number of login attempts exceeded. Please try again later.",
|
||||
> "documentation_url": "{% data variables.product.doc_url_pre %}/v3"
|
||||
@@ -165,19 +165,10 @@ $ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product.
|
||||
You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports:
|
||||
|
||||
```shell
|
||||
$ curl {% if currentVersion == "github-ae@latest" %}-u <em>username</em>:<em>token</em> {% endif %}{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}-u <em>username</em>:<em>password</em> {% endif %}{% data variables.product.api_url_pre %}
|
||||
$ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %}
|
||||
-u <em>username</em>:<em>token</em> {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u <em>username</em>:<em>password</em> {% endif %}{% data variables.product.api_url_pre %}
|
||||
```
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** For {% data variables.product.prodname_ghe_server %}, [as with all other endpoints](/v3/enterprise-admin/#endpoint-urls), you'll need to pass your username and password.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
### GraphQL global node IDs
|
||||
|
||||
See the guide on "[Using Global Node IDs](/v4/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations.
|
||||
|
||||
@@ -13,16 +13,53 @@ versions:
|
||||
|
||||
If you're encountering some oddities in the API, here's a list of resolutions to some of the problems you may be experiencing.
|
||||
|
||||
### Why am I getting a `404` error on a repository that exists?
|
||||
### `404` error for an existing repository
|
||||
|
||||
Typically, we send a `404` error when your client isn't properly authenticated. You might expect to see a `403 Forbidden` in these cases. However, since we don't want to provide _any_ information about private repositories, the API returns a `404` error instead.
|
||||
|
||||
To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), and [third-party application restrictions][oap-guide] are not blocking access.
|
||||
|
||||
### Why am I not seeing all my results?
|
||||
### Not all results returned
|
||||
|
||||
Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support pagination. If you're making requests and receiving an incomplete set of results, you're probably only seeing the first page. You'll need to request the remaining pages in order to get more results.
|
||||
|
||||
It's important to *not* try and guess the format of the pagination URL. Not every API call uses the same structure. Instead, extract the pagination information from [the Link Header](/v3/#pagination), which is sent with every request.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
### Basic authentication errors
|
||||
|
||||
On November 13, 2020 username and password authentication to the REST API and the OAuth Authorizations API were deprecated and no longer work.
|
||||
|
||||
#### Using `username`/`password` for basic authentication
|
||||
|
||||
If you're using `username` and `password` for API calls, then they are no longer able to authenticate. Ein Beispiel:
|
||||
|
||||
```bash
|
||||
curl -u my_user:my_password https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
Instead, use a [personal access token](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) when testing endpoints or doing local development:
|
||||
|
||||
```bash
|
||||
curl -H 'Authorization: token my_access_token' https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
For OAuth Apps, you should use the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate an OAuth token to use in the API call's header:
|
||||
|
||||
```bash
|
||||
curl -H 'Authorization: token my-oauth-token' https://api.github.com/user/repos
|
||||
```
|
||||
|
||||
#### Calls to OAuth Authorizations API
|
||||
|
||||
If you're making [OAuth Authorization API](/enterprise-server@2.22/rest/reference/oauth-authorizations) calls to manage your OAuth app's authorizations or to generate access tokens, similar to this example:
|
||||
|
||||
```bash
|
||||
curl -u my_username:my_password -X POST "https://api.github.com/authorizations" -d '{"scopes":["public_repo"], "note":"my token", "client_id":"my_client_id", "client_secret":"my_client_secret"}'
|
||||
```
|
||||
|
||||
Then you must switch to the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate access tokens.
|
||||
|
||||
{% endif %}
|
||||
|
||||
[oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
|
||||
|
||||
@@ -6,7 +6,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
---
|
||||
|
||||
Users interact with repositories by commenting, opening issues, and creating pull requests. The Interactions APIs allow people with owner or admin access to temporarily restrict certain users from interacting with public repositories.
|
||||
Users interact with repositories by commenting, opening issues, and creating pull requests. The Interactions APIs allow people with owner or admin access to temporarily restrict interaction with public repositories to a certain type of user.
|
||||
|
||||
{% for operation in currentRestOperations %}
|
||||
{% unless operation.subcategory %}{% include rest_operation %}{% endunless %}
|
||||
@@ -14,24 +14,42 @@ Users interact with repositories by commenting, opening issues, and creating pul
|
||||
|
||||
## Organisation
|
||||
|
||||
The Organization Interactions API allows organization owners to temporarily restrict which users can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the groups of {% data variables.product.product_name %} users:
|
||||
The Organization Interactions API allows organization owners to temporarily restrict which type of user can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users:
|
||||
|
||||
* {% data reusables.interactions.existing-user-limit-definition %} in the organization.
|
||||
* {% data reusables.interactions.contributor-user-limit-definition %} in the organization.
|
||||
* {% data reusables.interactions.collaborator-user-limit-definition %} in the organization.
|
||||
|
||||
Setting the interaction limit at the organization level will overwrite any interaction limits that are set for individual repositories owned by the organization. To set different interaction limits for individual repositories owned by the organization, use the [Repository](#repository) interactions endpoints instead.
|
||||
|
||||
{% for operation in currentRestOperations %}
|
||||
{% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
## Repository
|
||||
|
||||
The Repository Interactions API allows people with owner or admin access to temporarily restrict which users can comment, open issues, or create pull requests in a public repository. {% data reusables.interactions.interactions-detail %} Here's more about the groups of {% data variables.product.product_name %} users:
|
||||
The Repository Interactions API allows people with owner or admin access to temporarily restrict which type of user can comment, open issues, or create pull requests in a public repository. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users:
|
||||
|
||||
* {% data reusables.interactions.existing-user-limit-definition %} in the repository.
|
||||
* {% data reusables.interactions.contributor-user-limit-definition %} in the repository.
|
||||
* {% data reusables.interactions.collaborator-user-limit-definition %} in the repository.
|
||||
|
||||
If an interaction limit is enabled for the user or organization that owns the repository, the limit cannot be changed for the individual repository. Instead, use the [User](#user) or [Organization](#organization) interactions endpoints to change the interaction limit.
|
||||
|
||||
{% for operation in currentRestOperations %}
|
||||
{% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
## Benutzer
|
||||
|
||||
The User Interactions API allows you to temporarily restrict which type of user can comment, open issues, or create pull requests on your public repositories. {% data reusables.interactions.interactions-detail %} Here's more about the types of {% data variables.product.product_name %} users:
|
||||
|
||||
* {% data reusables.interactions.existing-user-limit-definition %} from interacting with your repositories.
|
||||
* {% data reusables.interactions.contributor-user-limit-definition %} from interacting with your repositories.
|
||||
* {% data reusables.interactions.collaborator-user-limit-definition %} from interacting with your repositories.
|
||||
|
||||
Setting the interaction limit at the user level will overwrite any interaction limits that are set for individual repositories owned by the user. To set different interaction limits for individual repositories owned by the user, use the [Repository](#repository) interactions endpoints instead.
|
||||
|
||||
{% for operation in currentRestOperations %}
|
||||
{% if operation.subcategory == 'user' %}{% include rest_operation %}{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
@@ -4,13 +4,9 @@ redirect_from:
|
||||
- /v3/oauth_authorizations
|
||||
- /v3/oauth-authorizations
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
---
|
||||
|
||||
{% data reusables.apps.deprecating_token_oauth_authorizations %}
|
||||
{% data reusables.apps.deprecating_password_auth %}
|
||||
|
||||
You can use this API to manage the access OAuth applications have to your account. You can only access this API via [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) using your username and password, not tokens.
|
||||
|
||||
If you or your users have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication).
|
||||
|
||||
@@ -31,13 +31,19 @@ Each endpoint in the Search API uses [query parameters](https://en.wikipedia.org
|
||||
A query can contain any combination of search qualifiers supported on {% data variables.product.product_name %}. The format of the search query is:
|
||||
|
||||
```
|
||||
q=SEARCH_KEYWORD_1+SEARCH_KEYWORD_N+QUALIFIER_1+QUALIFIER_N
|
||||
SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
|
||||
```
|
||||
|
||||
For example, if you wanted to search for all _repositories_ owned by `defunkt` that contained the word `GitHub` and `Octocat` in the README file, you would use the following query with the _search repositories_ endpoint:
|
||||
|
||||
```
|
||||
q=GitHub+Octocat+in:readme+user:defunkt
|
||||
GitHub Octocat in:readme user:defunkt
|
||||
```
|
||||
|
||||
**Note:** Be sure to use your language's preferred HTML-encoder to construct your query strings. Ein Beispiel:
|
||||
```javascript
|
||||
// JavaScript
|
||||
const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
|
||||
```
|
||||
|
||||
See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax/)."
|
||||
|
||||
@@ -85,7 +85,7 @@
|
||||
toggled_on:
|
||||
- Mutation.createContentAttachment
|
||||
owning_teams:
|
||||
- '@github/ce-extensibility'
|
||||
- '@github/feature-lifecycle'
|
||||
-
|
||||
title: Pinned Issues Preview
|
||||
description: This preview adds support for pinned issues.
|
||||
|
||||
@@ -2,112 +2,112 @@
|
||||
upcoming_changes:
|
||||
-
|
||||
location: Migration.uploadUrlTemplate
|
||||
description: "`uploadUrlTemplate` will be removed. Use `uploadUrl` instead."
|
||||
reason: "`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step."
|
||||
description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
|
||||
reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
|
||||
date: '2019-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: AssignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: EnterpriseBillingInfo.availableSeats
|
||||
description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead."
|
||||
reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned"
|
||||
description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.'
|
||||
reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: EnterpriseBillingInfo.seats
|
||||
description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead."
|
||||
reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned"
|
||||
description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.'
|
||||
reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: UnassignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: Sponsorship.maintainer
|
||||
description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead."
|
||||
reason: "`Sponsorship.maintainer` will be removed."
|
||||
description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.'
|
||||
reason: '`Sponsorship.maintainer` will be removed.'
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: antn
|
||||
-
|
||||
location: EnterprisePendingMemberInvitationEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All pending members consume a license
|
||||
date: '2020-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterpriseOwnerInfo.pendingCollaborators
|
||||
description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead."
|
||||
description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.'
|
||||
reason: Repository invitations can now be associated with an email, not only an invitee.
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
-
|
||||
location: Issue.timeline
|
||||
description: "`timeline` will be removed. Use Issue.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use Issue.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: PullRequest.timeline
|
||||
description: "`timeline` will be removed. Use PullRequest.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: RepositoryInvitationOrderField.INVITEE_LOGIN
|
||||
description: "`INVITEE_LOGIN` will be removed."
|
||||
reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee."
|
||||
description: '`INVITEE_LOGIN` will be removed.'
|
||||
reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
-
|
||||
location: Sponsorship.sponsor
|
||||
description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead."
|
||||
reason: "`Sponsorship.sponsor` will be removed."
|
||||
description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.'
|
||||
reason: '`Sponsorship.sponsor` will be removed.'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: nholden
|
||||
-
|
||||
location: EnterpriseMemberEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All members consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All outside collaborators consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterprisePendingCollaboratorEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All pending collaborators consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: MergeStateStatus.DRAFT
|
||||
description: "`DRAFT` will be removed. Use PullRequest.isDraft instead."
|
||||
description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.'
|
||||
reason: DRAFT state will be removed from this enum and `isDraft` should be used instead
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
|
||||
@@ -2,63 +2,63 @@
|
||||
upcoming_changes:
|
||||
-
|
||||
location: Migration.uploadUrlTemplate
|
||||
description: "`uploadUrlTemplate` will be removed. Use `uploadUrl` instead."
|
||||
reason: "`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step."
|
||||
description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
|
||||
reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
|
||||
date: '2019-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: ContributionOrder.field
|
||||
description: "`field` will be removed. Only one order field is supported."
|
||||
reason: "`field` will be removed."
|
||||
description: '`field` will be removed. Only one order field is supported.'
|
||||
reason: '`field` will be removed.'
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Issue.timeline
|
||||
description: "`timeline` will be removed. Use Issue.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use Issue.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: Organization.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: PullRequest.timeline
|
||||
description: "`timeline` will be removed. Use PullRequest.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: RepositoryOwner.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: User.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: AssignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: UnassignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
|
||||
@@ -2,560 +2,560 @@
|
||||
upcoming_changes:
|
||||
-
|
||||
location: Migration.uploadUrlTemplate
|
||||
description: "`uploadUrlTemplate` will be removed. Use `uploadUrl` instead."
|
||||
reason: "`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step."
|
||||
description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
|
||||
reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
|
||||
date: '2019-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: ContributionOrder.field
|
||||
description: "`field` will be removed. Only one order field is supported."
|
||||
reason: "`field` will be removed."
|
||||
description: '`field` will be removed. Only one order field is supported.'
|
||||
reason: '`field` will be removed.'
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Issue.timeline
|
||||
description: "`timeline` will be removed. Use Issue.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use Issue.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: Organization.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: PullRequest.timeline
|
||||
description: "`timeline` will be removed. Use PullRequest.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: RepositoryOwner.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: User.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: AssignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: EnterpriseBillingInfo.availableSeats
|
||||
description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead."
|
||||
reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned"
|
||||
description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.'
|
||||
reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: EnterpriseBillingInfo.seats
|
||||
description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead."
|
||||
reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned"
|
||||
description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.'
|
||||
reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: UnassignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: Organization.registryPackages
|
||||
description: "`registryPackages` will be removed. Use the `PackageOwner` object instead."
|
||||
description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Organization.registryPackagesForQuery
|
||||
description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead."
|
||||
description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.color
|
||||
description: "`color` will be removed. Use the `Package` object instead."
|
||||
description: '`color` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.latestVersion
|
||||
description: "`latestVersion` will be removed. Use the `Package` object instead."
|
||||
description: '`latestVersion` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.name
|
||||
description: "`name` will be removed. Use the `Package` object instead."
|
||||
description: '`name` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.nameWithOwner
|
||||
description: "`nameWithOwner` will be removed. Use the `Package` object instead."
|
||||
description: '`nameWithOwner` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.packageFileByGuid
|
||||
description: "`packageFileByGuid` will be removed. Use the `Package` object."
|
||||
description: '`packageFileByGuid` will be removed. Use the `Package` object.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.packageFileBySha256
|
||||
description: "`packageFileBySha256` will be removed. Use the `Package` object."
|
||||
description: '`packageFileBySha256` will be removed. Use the `Package` object.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.packageType
|
||||
description: "`packageType` will be removed. Use the `Package` object instead."
|
||||
description: '`packageType` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.preReleaseVersions
|
||||
description: "`preReleaseVersions` will be removed. Use the `Package` object instead."
|
||||
description: '`preReleaseVersions` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.registryPackageType
|
||||
description: "`registryPackageType` will be removed. Use the `Package` object instead."
|
||||
description: '`registryPackageType` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.repository
|
||||
description: "`repository` will be removed. Use the `Package` object instead."
|
||||
description: '`repository` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.statistics
|
||||
description: "`statistics` will be removed. Use the `Package` object instead."
|
||||
description: '`statistics` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.tags
|
||||
description: "`tags` will be removed. Use the `Package` object."
|
||||
description: '`tags` will be removed. Use the `Package` object.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.topics
|
||||
description: "`topics` will be removed. Use the `Package` object."
|
||||
description: '`topics` will be removed. Use the `Package` object.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.version
|
||||
description: "`version` will be removed. Use the `Package` object instead."
|
||||
description: '`version` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.versionByPlatform
|
||||
description: "`versionByPlatform` will be removed. Use the `Package` object instead."
|
||||
description: '`versionByPlatform` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.versionBySha256
|
||||
description: "`versionBySha256` will be removed. Use the `Package` object instead."
|
||||
description: '`versionBySha256` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.versions
|
||||
description: "`versions` will be removed. Use the `Package` object instead."
|
||||
description: '`versions` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.versionsByMetadatum
|
||||
description: "`versionsByMetadatum` will be removed. Use the `Package` object instead."
|
||||
description: '`versionsByMetadatum` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageDependency.dependencyType
|
||||
description: "`dependencyType` will be removed. Use the `PackageDependency` object instead."
|
||||
description: '`dependencyType` will be removed. Use the `PackageDependency` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageDependency.name
|
||||
description: "`name` will be removed. Use the `PackageDependency` object instead."
|
||||
description: '`name` will be removed. Use the `PackageDependency` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageDependency.version
|
||||
description: "`version` will be removed. Use the `PackageDependency` object instead."
|
||||
description: '`version` will be removed. Use the `PackageDependency` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.guid
|
||||
description: "`guid` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`guid` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.md5
|
||||
description: "`md5` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`md5` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.metadataUrl
|
||||
description: "`metadataUrl` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`metadataUrl` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.name
|
||||
description: "`name` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`name` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.packageVersion
|
||||
description: "`packageVersion` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`packageVersion` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.sha1
|
||||
description: "`sha1` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`sha1` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.sha256
|
||||
description: "`sha256` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`sha256` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.size
|
||||
description: "`size` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`size` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.url
|
||||
description: "`url` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`url` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageOwner.registryPackages
|
||||
description: "`registryPackages` will be removed. Use the `PackageOwner` object instead."
|
||||
description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageSearch.registryPackagesForQuery
|
||||
description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead."
|
||||
description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsThisMonth
|
||||
description: "`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsThisWeek
|
||||
description: "`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsThisYear
|
||||
description: "`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsToday
|
||||
description: "`downloadsToday` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsToday` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsTotalCount
|
||||
description: "`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageTag.name
|
||||
description: "`name` will be removed. Use the `PackageTag` object instead."
|
||||
description: '`name` will be removed. Use the `PackageTag` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageTag.version
|
||||
description: "`version` will be removed. Use the `PackageTag` object instead."
|
||||
description: '`version` will be removed. Use the `PackageTag` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.dependencies
|
||||
description: "`dependencies` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`dependencies` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.fileByName
|
||||
description: "`fileByName` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`fileByName` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.files
|
||||
description: "`files` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`files` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.installationCommand
|
||||
description: "`installationCommand` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`installationCommand` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.manifest
|
||||
description: "`manifest` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`manifest` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.platform
|
||||
description: "`platform` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`platform` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.preRelease
|
||||
description: "`preRelease` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`preRelease` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.readme
|
||||
description: "`readme` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`readme` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.readmeHtml
|
||||
description: "`readmeHtml` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`readmeHtml` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.registryPackage
|
||||
description: "`registryPackage` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`registryPackage` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.release
|
||||
description: "`release` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`release` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.sha256
|
||||
description: "`sha256` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`sha256` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.size
|
||||
description: "`size` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`size` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.statistics
|
||||
description: "`statistics` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`statistics` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.summary
|
||||
description: "`summary` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`summary` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.updatedAt
|
||||
description: "`updatedAt` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`updatedAt` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.version
|
||||
description: "`version` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`version` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.viewerCanEdit
|
||||
description: "`viewerCanEdit` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`viewerCanEdit` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsThisMonth
|
||||
description: "`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsThisWeek
|
||||
description: "`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsThisYear
|
||||
description: "`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsToday
|
||||
description: "`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsTotalCount
|
||||
description: "`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Repository.registryPackages
|
||||
description: "`registryPackages` will be removed. Use the `PackageOwner` object instead."
|
||||
description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Repository.registryPackagesForQuery
|
||||
description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead."
|
||||
description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Sponsorship.maintainer
|
||||
description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead."
|
||||
reason: "`Sponsorship.maintainer` will be removed."
|
||||
description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.'
|
||||
reason: '`Sponsorship.maintainer` will be removed.'
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: antn
|
||||
-
|
||||
location: User.registryPackages
|
||||
description: "`registryPackages` will be removed. Use the `PackageOwner` object instead."
|
||||
description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: User.registryPackagesForQuery
|
||||
description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead."
|
||||
description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
|
||||
@@ -2,568 +2,568 @@
|
||||
upcoming_changes:
|
||||
-
|
||||
location: Migration.uploadUrlTemplate
|
||||
description: "`uploadUrlTemplate` will be removed. Use `uploadUrl` instead."
|
||||
reason: "`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step."
|
||||
description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
|
||||
reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
|
||||
date: '2019-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: ContributionOrder.field
|
||||
description: "`field` will be removed. Only one order field is supported."
|
||||
reason: "`field` will be removed."
|
||||
description: '`field` will be removed. Only one order field is supported.'
|
||||
reason: '`field` will be removed.'
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Organization.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: RepositoryOwner.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: User.pinnedRepositories
|
||||
description: "`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead."
|
||||
description: '`pinnedRepositories` will be removed. Use ProfileOwner.pinnedItems instead.'
|
||||
reason: pinnedRepositories will be removed
|
||||
date: '2019-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: cheshire137
|
||||
-
|
||||
location: AssignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: EnterpriseBillingInfo.availableSeats
|
||||
description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead."
|
||||
reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned"
|
||||
description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.'
|
||||
reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: EnterpriseBillingInfo.seats
|
||||
description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead."
|
||||
reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned"
|
||||
description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.'
|
||||
reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: UnassignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: Organization.registryPackages
|
||||
description: "`registryPackages` will be removed. Use the `PackageOwner` object instead."
|
||||
description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Organization.registryPackagesForQuery
|
||||
description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead."
|
||||
description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.color
|
||||
description: "`color` will be removed. Use the `Package` object instead."
|
||||
description: '`color` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.latestVersion
|
||||
description: "`latestVersion` will be removed. Use the `Package` object instead."
|
||||
description: '`latestVersion` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.name
|
||||
description: "`name` will be removed. Use the `Package` object instead."
|
||||
description: '`name` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.nameWithOwner
|
||||
description: "`nameWithOwner` will be removed. Use the `Package` object instead."
|
||||
description: '`nameWithOwner` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.packageFileByGuid
|
||||
description: "`packageFileByGuid` will be removed. Use the `Package` object."
|
||||
description: '`packageFileByGuid` will be removed. Use the `Package` object.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.packageFileBySha256
|
||||
description: "`packageFileBySha256` will be removed. Use the `Package` object."
|
||||
description: '`packageFileBySha256` will be removed. Use the `Package` object.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.packageType
|
||||
description: "`packageType` will be removed. Use the `Package` object instead."
|
||||
description: '`packageType` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.preReleaseVersions
|
||||
description: "`preReleaseVersions` will be removed. Use the `Package` object instead."
|
||||
description: '`preReleaseVersions` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.registryPackageType
|
||||
description: "`registryPackageType` will be removed. Use the `Package` object instead."
|
||||
description: '`registryPackageType` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.repository
|
||||
description: "`repository` will be removed. Use the `Package` object instead."
|
||||
description: '`repository` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.statistics
|
||||
description: "`statistics` will be removed. Use the `Package` object instead."
|
||||
description: '`statistics` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.tags
|
||||
description: "`tags` will be removed. Use the `Package` object."
|
||||
description: '`tags` will be removed. Use the `Package` object.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.topics
|
||||
description: "`topics` will be removed. Use the `Package` object."
|
||||
description: '`topics` will be removed. Use the `Package` object.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.version
|
||||
description: "`version` will be removed. Use the `Package` object instead."
|
||||
description: '`version` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.versionByPlatform
|
||||
description: "`versionByPlatform` will be removed. Use the `Package` object instead."
|
||||
description: '`versionByPlatform` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.versionBySha256
|
||||
description: "`versionBySha256` will be removed. Use the `Package` object instead."
|
||||
description: '`versionBySha256` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.versions
|
||||
description: "`versions` will be removed. Use the `Package` object instead."
|
||||
description: '`versions` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackage.versionsByMetadatum
|
||||
description: "`versionsByMetadatum` will be removed. Use the `Package` object instead."
|
||||
description: '`versionsByMetadatum` will be removed. Use the `Package` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageDependency.dependencyType
|
||||
description: "`dependencyType` will be removed. Use the `PackageDependency` object instead."
|
||||
description: '`dependencyType` will be removed. Use the `PackageDependency` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageDependency.name
|
||||
description: "`name` will be removed. Use the `PackageDependency` object instead."
|
||||
description: '`name` will be removed. Use the `PackageDependency` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageDependency.version
|
||||
description: "`version` will be removed. Use the `PackageDependency` object instead."
|
||||
description: '`version` will be removed. Use the `PackageDependency` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.guid
|
||||
description: "`guid` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`guid` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.md5
|
||||
description: "`md5` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`md5` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.metadataUrl
|
||||
description: "`metadataUrl` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`metadataUrl` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.name
|
||||
description: "`name` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`name` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.packageVersion
|
||||
description: "`packageVersion` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`packageVersion` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.sha1
|
||||
description: "`sha1` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`sha1` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.sha256
|
||||
description: "`sha256` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`sha256` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.size
|
||||
description: "`size` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`size` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageFile.url
|
||||
description: "`url` will be removed. Use the `PackageFile` object instead."
|
||||
description: '`url` will be removed. Use the `PackageFile` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageOwner.registryPackages
|
||||
description: "`registryPackages` will be removed. Use the `PackageOwner` object instead."
|
||||
description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageSearch.registryPackagesForQuery
|
||||
description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead."
|
||||
description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsThisMonth
|
||||
description: "`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsThisMonth` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsThisWeek
|
||||
description: "`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsThisWeek` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsThisYear
|
||||
description: "`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsThisYear` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsToday
|
||||
description: "`downloadsToday` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsToday` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageStatistics.downloadsTotalCount
|
||||
description: "`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead."
|
||||
description: '`downloadsTotalCount` will be removed. Use the `PackageStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageTag.name
|
||||
description: "`name` will be removed. Use the `PackageTag` object instead."
|
||||
description: '`name` will be removed. Use the `PackageTag` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageTag.version
|
||||
description: "`version` will be removed. Use the `PackageTag` object instead."
|
||||
description: '`version` will be removed. Use the `PackageTag` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.deleted
|
||||
description: "`deleted` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`deleted` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.dependencies
|
||||
description: "`dependencies` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`dependencies` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.fileByName
|
||||
description: "`fileByName` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`fileByName` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.files
|
||||
description: "`files` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`files` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.installationCommand
|
||||
description: "`installationCommand` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`installationCommand` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.manifest
|
||||
description: "`manifest` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`manifest` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.platform
|
||||
description: "`platform` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`platform` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.preRelease
|
||||
description: "`preRelease` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`preRelease` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.readme
|
||||
description: "`readme` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`readme` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.readmeHtml
|
||||
description: "`readmeHtml` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`readmeHtml` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.registryPackage
|
||||
description: "`registryPackage` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`registryPackage` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.release
|
||||
description: "`release` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`release` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.sha256
|
||||
description: "`sha256` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`sha256` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.size
|
||||
description: "`size` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`size` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.statistics
|
||||
description: "`statistics` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`statistics` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.summary
|
||||
description: "`summary` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`summary` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.updatedAt
|
||||
description: "`updatedAt` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`updatedAt` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.version
|
||||
description: "`version` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`version` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersion.viewerCanEdit
|
||||
description: "`viewerCanEdit` will be removed. Use the `PackageVersion` object instead."
|
||||
description: '`viewerCanEdit` will be removed. Use the `PackageVersion` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsThisMonth
|
||||
description: "`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsThisMonth` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsThisWeek
|
||||
description: "`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsThisWeek` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsThisYear
|
||||
description: "`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsThisYear` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsToday
|
||||
description: "`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsToday` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: RegistryPackageVersionStatistics.downloadsTotalCount
|
||||
description: "`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead."
|
||||
description: '`downloadsTotalCount` will be removed. Use the `PackageVersionStatistics` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Repository.registryPackages
|
||||
description: "`registryPackages` will be removed. Use the `PackageOwner` object instead."
|
||||
description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Repository.registryPackagesForQuery
|
||||
description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead."
|
||||
description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Sponsorship.maintainer
|
||||
description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead."
|
||||
reason: "`Sponsorship.maintainer` will be removed."
|
||||
description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.'
|
||||
reason: '`Sponsorship.maintainer` will be removed.'
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: antn
|
||||
-
|
||||
location: User.registryPackages
|
||||
description: "`registryPackages` will be removed. Use the `PackageOwner` object instead."
|
||||
description: '`registryPackages` will be removed. Use the `PackageOwner` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: User.registryPackagesForQuery
|
||||
description: "`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead."
|
||||
description: '`registryPackagesForQuery` will be removed. Use the `PackageSearch` object instead.'
|
||||
reason: Renaming GitHub Packages fields and objects.
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: dinahshi
|
||||
-
|
||||
location: Issue.timeline
|
||||
description: "`timeline` will be removed. Use Issue.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use Issue.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: PullRequest.timeline
|
||||
description: "`timeline` will be removed. Use PullRequest.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
|
||||
@@ -2,71 +2,71 @@
|
||||
upcoming_changes:
|
||||
-
|
||||
location: Migration.uploadUrlTemplate
|
||||
description: "`uploadUrlTemplate` will be removed. Use `uploadUrl` instead."
|
||||
reason: "`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step."
|
||||
description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
|
||||
reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
|
||||
date: '2019-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: AssignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: EnterpriseBillingInfo.availableSeats
|
||||
description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead."
|
||||
reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned"
|
||||
description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.'
|
||||
reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: EnterpriseBillingInfo.seats
|
||||
description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead."
|
||||
reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned"
|
||||
description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.'
|
||||
reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: UnassignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: Sponsorship.maintainer
|
||||
description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead."
|
||||
reason: "`Sponsorship.maintainer` will be removed."
|
||||
description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.'
|
||||
reason: '`Sponsorship.maintainer` will be removed.'
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: antn
|
||||
-
|
||||
location: EnterprisePendingMemberInvitationEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All pending members consume a license
|
||||
date: '2020-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterpriseOwnerInfo.pendingCollaborators
|
||||
description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead."
|
||||
description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.'
|
||||
reason: Repository invitations can now be associated with an email, not only an invitee.
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
-
|
||||
location: Issue.timeline
|
||||
description: "`timeline` will be removed. Use Issue.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use Issue.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: PullRequest.timeline
|
||||
description: "`timeline` will be removed. Use PullRequest.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
@@ -86,15 +86,15 @@ upcoming_changes:
|
||||
owner: oneill38
|
||||
-
|
||||
location: RepositoryInvitationOrderField.INVITEE_LOGIN
|
||||
description: "`INVITEE_LOGIN` will be removed."
|
||||
reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee."
|
||||
description: '`INVITEE_LOGIN` will be removed.'
|
||||
reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
-
|
||||
location: Sponsorship.sponsor
|
||||
description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead."
|
||||
reason: "`Sponsorship.sponsor` will be removed."
|
||||
description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.'
|
||||
reason: '`Sponsorship.sponsor` will be removed.'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: nholden
|
||||
@@ -107,21 +107,21 @@ upcoming_changes:
|
||||
owner: oneill38
|
||||
-
|
||||
location: EnterpriseMemberEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All members consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All outside collaborators consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterprisePendingCollaboratorEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All pending collaborators consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
|
||||
@@ -102,7 +102,7 @@
|
||||
toggled_on:
|
||||
- Mutation.createContentAttachment
|
||||
owning_teams:
|
||||
- '@github/ce-extensibility'
|
||||
- '@github/feature-lifecycle'
|
||||
-
|
||||
title: Pinned Issues Preview
|
||||
description: This preview adds support for pinned issues.
|
||||
|
||||
@@ -2,119 +2,119 @@
|
||||
upcoming_changes:
|
||||
-
|
||||
location: Migration.uploadUrlTemplate
|
||||
description: "`uploadUrlTemplate` will be removed. Use `uploadUrl` instead."
|
||||
reason: "`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step."
|
||||
description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
|
||||
reason: '`uploadUrlTemplate` is being removed because it is not a standard URL and adds an extra user step.'
|
||||
date: '2019-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: AssignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: EnterpriseBillingInfo.availableSeats
|
||||
description: "`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead."
|
||||
reason: "`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned"
|
||||
description: '`availableSeats` will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.'
|
||||
reason: '`availableSeats` will be replaced with `totalAvailableLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: EnterpriseBillingInfo.seats
|
||||
description: "`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead."
|
||||
reason: "`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned"
|
||||
description: '`seats` will be removed. Use EnterpriseBillingInfo.totalLicenses instead.'
|
||||
reason: '`seats` will be replaced with `totalLicenses` to provide more clarity on the value being returned'
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BlakeWilliams
|
||||
-
|
||||
location: UnassignedEvent.user
|
||||
description: "`user` will be removed. Use the `assignee` field instead."
|
||||
description: '`user` will be removed. Use the `assignee` field instead.'
|
||||
reason: Assignees can now be mannequins.
|
||||
date: '2020-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: tambling
|
||||
-
|
||||
location: Query.sponsorsListing
|
||||
description: "`sponsorsListing` will be removed. Use `Sponsorable.sponsorsListing` instead."
|
||||
reason: "`Query.sponsorsListing` will be removed."
|
||||
description: '`sponsorsListing` will be removed. Use `Sponsorable.sponsorsListing` instead.'
|
||||
reason: '`Query.sponsorsListing` will be removed.'
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: antn
|
||||
-
|
||||
location: Sponsorship.maintainer
|
||||
description: "`maintainer` will be removed. Use `Sponsorship.sponsorable` instead."
|
||||
reason: "`Sponsorship.maintainer` will be removed."
|
||||
description: '`maintainer` will be removed. Use `Sponsorship.sponsorable` instead.'
|
||||
reason: '`Sponsorship.maintainer` will be removed.'
|
||||
date: '2020-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: antn
|
||||
-
|
||||
location: EnterprisePendingMemberInvitationEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All pending members consume a license
|
||||
date: '2020-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterpriseOwnerInfo.pendingCollaborators
|
||||
description: "`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead."
|
||||
description: '`pendingCollaborators` will be removed. Use the `pendingCollaboratorInvitations` field instead.'
|
||||
reason: Repository invitations can now be associated with an email, not only an invitee.
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
-
|
||||
location: Issue.timeline
|
||||
description: "`timeline` will be removed. Use Issue.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use Issue.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: PullRequest.timeline
|
||||
description: "`timeline` will be removed. Use PullRequest.timelineItems instead."
|
||||
reason: "`timeline` will be removed"
|
||||
description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
|
||||
reason: '`timeline` will be removed'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: mikesea
|
||||
-
|
||||
location: RepositoryInvitationOrderField.INVITEE_LOGIN
|
||||
description: "`INVITEE_LOGIN` will be removed."
|
||||
reason: "`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee."
|
||||
description: '`INVITEE_LOGIN` will be removed.'
|
||||
reason: '`INVITEE_LOGIN` is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
-
|
||||
location: Sponsorship.sponsor
|
||||
description: "`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead."
|
||||
reason: "`Sponsorship.sponsor` will be removed."
|
||||
description: '`sponsor` will be removed. Use `Sponsorship.sponsorEntity` instead.'
|
||||
reason: '`Sponsorship.sponsor` will be removed.'
|
||||
date: '2020-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: nholden
|
||||
-
|
||||
location: EnterpriseMemberEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All members consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterpriseOutsideCollaboratorEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All outside collaborators consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: EnterprisePendingCollaboratorEdge.isUnlicensed
|
||||
description: "`isUnlicensed` will be removed."
|
||||
description: '`isUnlicensed` will be removed.'
|
||||
reason: All pending collaborators consume a license
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: BrentWheeldon
|
||||
-
|
||||
location: MergeStateStatus.DRAFT
|
||||
description: "`DRAFT` will be removed. Use PullRequest.isDraft instead."
|
||||
description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.'
|
||||
reason: DRAFT state will be removed from this enum and `isDraft` should be used instead
|
||||
date: '2021-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf Dein Profilfoto und dann auf **Feature preview** (Funktions-Vorschau). 
|
||||
@@ -0,0 +1 @@
|
||||
{% data variables.product.prodname_secret_scanning_caps %} is available in public repositories, and in private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %}
|
||||
@@ -1 +1 @@
|
||||
When restrictions are enabled, only the specified group of {% data variables.product.product_name %} users will be able to participate in interactions. Restrictions expire 24 hours from the time they are set.
|
||||
When restrictions are enabled, only the specified type of {% data variables.product.product_name %} user will be able to participate in interactions. Restrictions automatically expire after a defined duration.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)“.
|
||||
**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use {% data variables.product.prodname_github_container_registry %}, you must enable the feature preview. For more information, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" and "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -0,0 +1,5 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** Before you can use {% data variables.product.prodname_github_container_registry %}, you must enable the feature for your account. For more information, see "[Enabling improved container support](/packages/getting-started-with-github-container-registry/enabling-improved-container-support)."
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,5 +1,5 @@
|
||||
{% note %}
|
||||
|
||||
**Hinweis:** {% data variables.product.prodname_secret_scanning_caps %} für private Repositorys befindet sich derzeit in der Beta-Version und kann sich jederzeit verändern. Um Zugriff auf die Beta-Version zu erhalten, [tritt der Warteliste bei](https://github.com/features/security/advanced-security/signup).
|
||||
**Hinweis:** {% data variables.product.prodname_secret_scanning_caps %} für private Repositorys befindet sich derzeit in der Beta-Version und kann sich jederzeit verändern.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -4,9 +4,10 @@ header:
|
||||
contact: Kontakt
|
||||
notices:
|
||||
ghae_silent_launch: GitHub AE is currently under limited release. Please <a href="https://enterprise.github.com/contact">contact our Sales Team</a> to find out more.
|
||||
release_candidate: '# The version name is rendered before the below text via includes/header-notification.html '' is currently under limited release as a release candidate.'''
|
||||
localization_complete: Wir veröffentlichen regelmäßig Aktualisierungen unserer Dokumentation, und die Übersetzung dieser Seite kann noch im Gange sein. Die neuesten Informationen findest Du in der <a id="to-english-doc" href="/en">englischsprachigen Dokumentation</a>. <a href="https://github.com/contact?form[subject]=translation%20issue%20on%20help.github.com&form[comments]=">Informieren Sie uns bitte</a>, falls auf dieser Seite ein Problem mit den Übersetzungen vorliegt.
|
||||
localization_in_progress: Hallo, Entdecker! An dieser Seite wird aktiv gearbeitet, oder sie wird noch übersetzt. Die neuesten und genauesten Informationen findest Du in unserer <a id="to-english-doc" href="/en">englischsprachigen Dokumentation</a>.
|
||||
product_in_progress: '👋 Hallo, Entdecker! An dieser Seite wird aktiv gearbeitet. Die neuesten und genauesten Informationen findest du in unserer <a href="https://developer.github.com">Entwicklerdokumentation</a>.'
|
||||
early_access: '👋 This page contains content about an early access feature. Please do not share this URL publicly.'
|
||||
search:
|
||||
need_help: Benötigen Sie Hilfe?
|
||||
placeholder: Themen, Produkte suchen …
|
||||
@@ -19,7 +20,7 @@ toc:
|
||||
guides: Leitfäden
|
||||
whats_new: What's new
|
||||
pages:
|
||||
article_version: "Artikelversion:"
|
||||
article_version: 'Artikelversion:'
|
||||
miniToc: Inhalt dieses Artikels
|
||||
errors:
|
||||
oops: Hoppla!
|
||||
|
||||
149
translations/de-DE/data/variables/action_code_examples.yml
Normal file
149
translations/de-DE/data/variables/action_code_examples.yml
Normal file
@@ -0,0 +1,149 @@
|
||||
---
|
||||
-
|
||||
title: Starter workflows
|
||||
description: Workflow files for helping people get started with GitHub Actions
|
||||
languages: TypeScript
|
||||
href: actions/starter-workflows
|
||||
tags:
|
||||
- official
|
||||
- workflows
|
||||
-
|
||||
title: Example services
|
||||
description: Example workflows using service containers
|
||||
languages: JavaScript
|
||||
href: actions/example-services
|
||||
tags:
|
||||
- service containers
|
||||
-
|
||||
title: Declaratively setup GitHub Labels
|
||||
description: GitHub Action to declaratively setup labels across repos
|
||||
languages: JavaScript
|
||||
href: lannonbr/issue-label-manager-action
|
||||
tags:
|
||||
- Issues (Lieferungen)
|
||||
- labels
|
||||
-
|
||||
title: Declaratively sync GitHub labels
|
||||
description: GitHub Action to sync GitHub labels in the declarative way
|
||||
languages: 'Go, Dockerfile'
|
||||
href: micnncim/action-label-syncer
|
||||
tags:
|
||||
- Issues (Lieferungen)
|
||||
- labels
|
||||
-
|
||||
title: Add releases to GitHub
|
||||
description: Publish Github releases in an action
|
||||
languages: 'Dockerfile, Shell'
|
||||
href: elgohr/Github-Release-Action
|
||||
tags:
|
||||
- veröffentlichungen
|
||||
- publishing
|
||||
-
|
||||
title: Publish a docker image to Dockerhub
|
||||
description: A Github Action used to build and publish Docker images
|
||||
languages: 'Dockerfile, Shell'
|
||||
href: elgohr/Publish-Docker-Github-Action
|
||||
tags:
|
||||
- docker
|
||||
- publishing
|
||||
- build
|
||||
-
|
||||
title: Create an issue using content from a file
|
||||
description: A GitHub action to create an issue using content from a file
|
||||
languages: 'JavaScript, Python'
|
||||
href: peter-evans/create-issue-from-file
|
||||
tags:
|
||||
- Issues (Lieferungen)
|
||||
-
|
||||
title: Publish GitHub Releases with Assets
|
||||
description: GitHub Action for creating GitHub Releases
|
||||
languages: 'TypeScript, Shell, JavaScript'
|
||||
href: softprops/action-gh-release
|
||||
tags:
|
||||
- veröffentlichungen
|
||||
- publishing
|
||||
-
|
||||
title: GitHub Project Automation+
|
||||
description: Automate GitHub Project cards with any webhook event.
|
||||
languages: JavaScript
|
||||
href: alex-page/github-project-automation-plus
|
||||
tags:
|
||||
- projects
|
||||
- automation
|
||||
- Issues (Lieferungen)
|
||||
- pull requests
|
||||
-
|
||||
title: Run GitHub Actions Locally with a web interface
|
||||
description: Runs GitHub Actions workflows locally (local)
|
||||
languages: 'JavaScript, HTML, Dockerfile, CSS'
|
||||
href: phishy/wflow
|
||||
tags:
|
||||
- local-development
|
||||
- devops
|
||||
- docker
|
||||
-
|
||||
title: Run your GitHub Actions locally
|
||||
description: Run GitHub Actions Locally in Terminal
|
||||
languages: 'Go, Shell'
|
||||
href: nektos/act
|
||||
tags:
|
||||
- local-development
|
||||
- devops
|
||||
- docker
|
||||
-
|
||||
title: Build and Publish Android debug APK
|
||||
description: Build and release debug APK from your Android project
|
||||
languages: 'Shell, Dockerfile'
|
||||
href: ShaunLWM/action-release-debugapk
|
||||
tags:
|
||||
- android
|
||||
- build
|
||||
-
|
||||
title: Generate sequential build numbers for GitHub Actions
|
||||
description: GitHub action for generating sequential build numbers.
|
||||
languages: JavaScript
|
||||
href: einaregilsson/build-number
|
||||
tags:
|
||||
- build
|
||||
- automation
|
||||
-
|
||||
title: GitHub actions to push back to repository
|
||||
description: Push Git changes to GitHub repository without authentication difficulties
|
||||
languages: 'JavaScript, Shell'
|
||||
href: ad-m/github-push-action
|
||||
tags:
|
||||
- publishing
|
||||
-
|
||||
title: Generate release notes based on your events
|
||||
description: Action to auto generate a release note based on your events
|
||||
languages: 'Shell, Dockerfile'
|
||||
href: Decathlon/release-notes-generator-action
|
||||
tags:
|
||||
- veröffentlichungen
|
||||
- publishing
|
||||
-
|
||||
title: Create a GitHub wiki page based on the provided markdown file
|
||||
description: Create a GitHub wiki page based on the provided markdown file
|
||||
languages: 'Shell, Dockerfile'
|
||||
href: Decathlon/wiki-page-creator-action
|
||||
tags:
|
||||
- wiki
|
||||
- publishing
|
||||
-
|
||||
title: Label your Pull Requests auto-magically (using committed files)
|
||||
description: >-
|
||||
Github action to label your pull requests auto-magically (using committed files)
|
||||
languages: 'TypeScript, Dockerfile, JavaScript'
|
||||
href: Decathlon/pull-request-labeler-action
|
||||
tags:
|
||||
- projects
|
||||
- Issues (Lieferungen)
|
||||
- labels
|
||||
-
|
||||
title: Add Label to your Pull Requests based on the author team name
|
||||
description: Github action to label your pull requests based on the author name
|
||||
languages: 'TypeScript, JavaScript'
|
||||
href: JulienKode/team-labeler-action
|
||||
tags:
|
||||
- Pull Request
|
||||
- labels
|
||||
@@ -10,7 +10,7 @@ contact_dmca: >-
|
||||
{% if currentVersion == "free-pro-team@latest" %}[Copyright claims form](https://github.com/contact/dmca){% endif %}
|
||||
contact_privacy: >-
|
||||
{% if currentVersion == "free-pro-team@latest" %}[Privacy contact form](https://github.com/contact/privacy){% endif %}
|
||||
contact_enterprise_sales: '[GitHub''s Vertriebsteam](https://enterprise.github.com/contact)'
|
||||
contact_enterprise_sales: "[GitHub's Vertriebsteam](https://enterprise.github.com/contact)"
|
||||
contact_feedback_actions: '[Feedback-Formular für GitHub Actions](https://support.github.com/contact/feedback?contact[category]=actions)'
|
||||
#The team that provides Standard Support
|
||||
enterprise_support: 'GitHub Enterprise-Support'
|
||||
|
||||
2
translations/de-DE/data/variables/release_candidate.yml
Normal file
2
translations/de-DE/data/variables/release_candidate.yml
Normal file
@@ -0,0 +1,2 @@
|
||||
---
|
||||
version: ''
|
||||
@@ -5,6 +5,8 @@ product: '{% data reusables.gated-features.actions %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
authors:
|
||||
- potatoqualitee
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_actions %} の支払いを管理する
|
||||
|
||||
@@ -0,0 +1,318 @@
|
||||
---
|
||||
title: Building and testing Ruby
|
||||
intro: You can create a continuous integration (CI) workflow to build and test your Ruby project.
|
||||
product: '{% data reusables.gated-features.actions %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_actions %} の支払いを管理する
|
||||
{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。
|
||||
|
||||
### はじめに
|
||||
|
||||
This guide shows you how to create a continuous integration (CI) workflow that builds and tests a Ruby application. If your CI tests pass, you may want to deploy your code or publish a gem.
|
||||
|
||||
### 必要な環境
|
||||
|
||||
We recommend that you have a basic understanding of Ruby, YAML, workflow configuration options, and how to create a workflow file. 詳しい情報については、以下を参照してください。
|
||||
|
||||
- [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
|
||||
- [Ruby in 20 minutes](https://www.ruby-lang.org/en/documentation/quickstart/)
|
||||
|
||||
### Starting with the Ruby workflow template
|
||||
|
||||
{% data variables.product.prodname_dotcom %} provides a Ruby workflow template that will work for most Ruby projects. For more information, see the [Ruby workflow template](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
|
||||
|
||||
手早く始めるために、テンプレートをリポジトリの`.github/workflows`ディレクトリに追加してください。
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
name: Ruby
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [ $default-branch ]
|
||||
pull_request:
|
||||
branches: [ $default-branch ]
|
||||
|
||||
jobs:
|
||||
test:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- name: Set up Ruby
|
||||
# To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
|
||||
# change this to (see https://github.com/ruby/setup-ruby#versioning):
|
||||
# uses: ruby/setup-ruby@v1
|
||||
uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- name: Install dependencies
|
||||
run: bundle install
|
||||
- name: Run tests
|
||||
run: bundle exec rake
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Specifying the Ruby version
|
||||
|
||||
The easiest way to specify a Ruby version is by using the `ruby/setup-ruby` action provided by the Ruby organization on GitHub. The action adds any supported Ruby version to `PATH` for each job run in a workflow. For more information see, the [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
|
||||
|
||||
Using either Ruby's `ruby/setup-ruby` action or GitHub's `actions/setup-ruby` action is the recommended way of using Ruby with GitHub Actions because it ensures consistent behavior across different runners and different versions of Ruby.
|
||||
|
||||
The `setup-ruby` action takes a Ruby version as an input and configures that version on the runner.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: 2.6 # Not needed with a .ruby-version file
|
||||
- run: bundle install
|
||||
- run: bundle exec rake
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
Alternatively, you can check a `.ruby-version` file into the root of your repository and `setup-ruby` will use the version defined in that file.
|
||||
|
||||
### Testing with multiple versions of Ruby
|
||||
|
||||
You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 2.7, 2.6, and 2.5. The 'x' is a wildcard character that matches the latest patch release available for a version.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
ruby-version: [2.7.x, 2.6.x, 2.5.x]
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "Workflow syntax for GitHub Actions" and "Context and expression syntax for GitHub Actions."
|
||||
|
||||
The full updated workflow with a matrix strategy could look like this:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
name: Ruby CI
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [ $default-branch ]
|
||||
pull_request:
|
||||
branches: [ $default-branch ]
|
||||
|
||||
jobs:
|
||||
test:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
strategy:
|
||||
matrix:
|
||||
ruby-version: [2.7.x, 2.6.x, 2.5.x]
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- name: Set up Ruby ${{ matrix.ruby-version }}
|
||||
# To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
|
||||
# change this to (see https://github.com/ruby/setup-ruby#versioning):
|
||||
# uses: ruby/setup-ruby@v1
|
||||
uses: ruby/setup-ruby@ec106b438a1ff6ff109590de34ddc62c540232e0
|
||||
with:
|
||||
ruby-version: ${{ matrix.ruby-version }}
|
||||
- name: Install dependencies
|
||||
run: bundle install
|
||||
- name: Run tests
|
||||
run: bundle exec rake
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Installing dependencies with Bundler
|
||||
|
||||
The `setup-ruby` action will automatically install bundler for you. The version is determined by your `gemfile.lock` file. If no version is present in your lockfile, then the latest compatible version will be installed.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- run: bundle install
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### 依存関係のキャッシング
|
||||
|
||||
The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs.
|
||||
|
||||
To enable caching, set the following.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
bundler-cache: true
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by Actions and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
|
||||
|
||||
**Caching without setup-ruby**
|
||||
|
||||
For greater control over caching, you can use the `actions/cache` Action directly. 詳しい情報については「[ワークフローを高速化するための依存関係のキャッシング](/actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows)」を参照してください。
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: actions/cache@v2
|
||||
with:
|
||||
path: vendor/bundle
|
||||
key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
|
||||
restore-keys: |
|
||||
${{ runner.os }}-gems-
|
||||
- name: Bundle install
|
||||
run: |
|
||||
bundle config path vendor/bundle
|
||||
bundle install --jobs 4 --retry 3
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
If you're using a matrix build, you will want to include the matrix variables in your cache key. For example, if you have a matrix strategy for different ruby versions (`matrix.ruby-version`) and different operating systems (`matrix.os`), your workflow steps might look like this:
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
steps:
|
||||
- uses: actions/cache@v2
|
||||
with:
|
||||
path: vendor/bundle
|
||||
key: bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }}
|
||||
restore-keys: |
|
||||
bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-
|
||||
- name: Bundle install
|
||||
run: |
|
||||
bundle config path vendor/bundle
|
||||
bundle install --jobs 4 --retry 3
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Matrix testing your code
|
||||
|
||||
The following example matrix tests all stable releases and head versions of MRI, JRuby and TruffleRuby on Ubuntu and macOS.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
name: Matrix Testing
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [ $default-branch ]
|
||||
pull_request:
|
||||
branches: [ $default-branch ]
|
||||
|
||||
jobs:
|
||||
test:
|
||||
runs-on: ${{ matrix.os }}-latest
|
||||
strategy:
|
||||
fail-fast: false
|
||||
matrix:
|
||||
os: [ubuntu, macos]
|
||||
ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
|
||||
continue-on-error: ${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: ${{ matrix.ruby }}
|
||||
- run: bundle install
|
||||
- run: bundle exec rake
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Linting your code
|
||||
|
||||
The following example installs `rubocop` and uses it to lint all files. For more information, see [Rubocop](https://github.com/rubocop-hq/rubocop). You can [configure Rubocop](https://docs.rubocop.org/rubocop/configuration.html) to decide on the specific linting rules.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
name: Linting
|
||||
|
||||
on: [push]
|
||||
|
||||
jobs:
|
||||
test:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- run: bundle install
|
||||
- name: Rubocop
|
||||
run: rubocop
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
### Publishing Gems
|
||||
|
||||
You can configure your workflow to publish your Ruby package to any package registry you'd like when your CI tests pass.
|
||||
|
||||
パッケージを公開するのに必要なアクセストークンやクレデンシャルは、リポジトリシークレットを使って保存できます。 The following example creates and publishes a package to `GitHub Package Registry` and `RubyGems`.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
||||
name: Ruby Gem
|
||||
|
||||
on:
|
||||
# Manually publish
|
||||
workflow_dispatch:
|
||||
# Alternatively, publish whenever changes are merged to the default branch.
|
||||
push:
|
||||
branches: [ $default-branch ]
|
||||
pull_request:
|
||||
branches: [ $default-branch ]
|
||||
|
||||
jobs:
|
||||
build:
|
||||
name: Build + Publish
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
- name: Set up Ruby 2.6
|
||||
uses: ruby/setup-ruby@v1
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- run: bundle install
|
||||
|
||||
- name: Publish to GPR
|
||||
run: |
|
||||
mkdir -p $HOME/.gem
|
||||
touch $HOME/.gem/credentials
|
||||
chmod 0600 $HOME/.gem/credentials
|
||||
printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
|
||||
gem build *.gemspec
|
||||
gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
|
||||
env:
|
||||
GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
|
||||
OWNER: ${{ github.repository_owner }}
|
||||
|
||||
- name: Publish to RubyGems
|
||||
run: |
|
||||
mkdir -p $HOME/.gem
|
||||
touch $HOME/.gem/credentials
|
||||
chmod 0600 $HOME/.gem/credentials
|
||||
printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
|
||||
gem build *.gemspec
|
||||
gem push *.gem
|
||||
env:
|
||||
GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@@ -31,6 +31,7 @@ versions:
|
||||
{% link_in_list /building-and-testing-nodejs %}
|
||||
{% link_in_list /building-and-testing-powershell %}
|
||||
{% link_in_list /building-and-testing-python %}
|
||||
{% link_in_list /building-and-testing-ruby %}
|
||||
{% link_in_list /building-and-testing-java-with-maven %}
|
||||
{% link_in_list /building-and-testing-java-with-gradle %}
|
||||
{% link_in_list /building-and-testing-java-with-ant %}
|
||||
|
||||
@@ -8,6 +8,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
authors:
|
||||
- GitHub
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_actions %} の支払いを管理する
|
||||
|
||||
@@ -11,6 +11,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
authors:
|
||||
- GitHub
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_actions %} の支払いを管理する
|
||||
|
||||
@@ -7,31 +7,40 @@ introLinks:
|
||||
reference: /actions/reference
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /actions/guides/setting-up-continuous-integration-using-workflow-templates
|
||||
- /actions/learn-github-actions
|
||||
- /actions/guides/about-continuous-integration
|
||||
- /actions/guides/about-packaging-with-github-actions
|
||||
gettingStarted:
|
||||
- /actions/managing-workflow-runs
|
||||
- /actions/hosting-your-own-runners
|
||||
guideCards:
|
||||
- /actions/guides/setting-up-continuous-integration-using-workflow-templates
|
||||
- /actions/guides/publishing-nodejs-packages
|
||||
- /actions/guides/building-and-testing-powershell
|
||||
popular:
|
||||
- /actions/reference/workflow-syntax-for-github-actions
|
||||
- /actions/reference/events-that-trigger-workflows
|
||||
- /actions/learn-github-actions
|
||||
- /actions/reference/context-and-expression-syntax-for-github-actions
|
||||
- /actions/reference/workflow-commands-for-github-actions
|
||||
- /actions/reference/environment-variables
|
||||
changelog:
|
||||
-
|
||||
title: Removing set-env and add-path commands on November 16
|
||||
date: '2020-11-09'
|
||||
href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
|
||||
-
|
||||
title: 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/
|
||||
-
|
||||
title: Ability to change retention days for artifacts and logs
|
||||
date: '2020-10-08'
|
||||
href: https://github.blog/changelog/2020-10-08-github-actions-ability-to-change-retention-days-for-artifacts-and-logs
|
||||
-
|
||||
title: Deprecating set-env and add-path commands
|
||||
date: '2020-10-01'
|
||||
href: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands
|
||||
-
|
||||
title: Fine-tune access to external actions
|
||||
date: '2020-10-01'
|
||||
href: https://github.blog/changelog/2020-10-01-github-actions-fine-tune-access-to-external-actions
|
||||
redirect_from:
|
||||
- /articles/automating-your-workflow-with-github-actions/
|
||||
- /articles/customizing-your-project-with-github-actions/
|
||||
@@ -54,107 +63,26 @@ versions:
|
||||
<!-- {% link_with_intro /reference %} -->
|
||||
|
||||
<!-- Code examples -->
|
||||
{% assign actionsCodeExamples = site.data.variables.action_code_examples %}
|
||||
{% if actionsCodeExamples %}
|
||||
<div class="my-6 pt-6">
|
||||
<h2 class="mb-2">その他のガイド</h2>
|
||||
<h2 class="mb-2 font-mktg h1">Code examples</h2>
|
||||
|
||||
<div class="d-flex flex-wrap gutter">
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-nodejs">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Node.js</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Node.js application.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">JavaScript/TypeScript</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-nodejs</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-python">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Python</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Python application.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">Python</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-python</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-java-with-maven">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Java with Maven</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Java project with Maven.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">Java</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-java-with-maven</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-java-with-gradle">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Java with Gradle</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Java project with Gradle.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">Java</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-java-with-gradle</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/building-and-testing-java-with-ant">
|
||||
<div class="p-4">
|
||||
<h4>Building and testing Java with Ant</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to power CI in your Java project with Ant.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">Java</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/building-and-testing-java-with-ant</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="col-12 col-lg-4 mb-4">
|
||||
<a class="Box d-block hover-grow no-underline text-gray-dark" href="/actions/guides/publishing-nodejs-packages">
|
||||
<div class="p-4">
|
||||
<h4>Publishing Node.js packages</h4>
|
||||
<p class="mt-2 mb-4">Use GitHub Actions to push your Node.js package to GitHub Packages or npm.</p>
|
||||
<div class="d-flex">
|
||||
<span class="IssueLabel text-white bg-blue mr-2">JavaScript/TypeScript</span>
|
||||
<span class="IssueLabel text-white bg-blue mr-2">CI</span>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="border-top p-4 text-gray d-flex flex-items-center">
|
||||
{% octicon "workflow" class="flex-shrink-0" %}
|
||||
<span class="ml-2">/guides/publishing-nodejs-packages</span>
|
||||
</footer>
|
||||
</a>
|
||||
</div>
|
||||
<div class="pr-lg-3 mb-5 mt-3">
|
||||
<input class="js-code-example-filter input-lg py-2 px-3 col-12 col-lg-8 form-control" placeholder="Search code examples" type="search" autocomplete="off" aria-label="Search code examples"/>
|
||||
</div>
|
||||
|
||||
<a href="/actions/guides" class="btn btn-outline mt-4">すべてのガイド表示 {% octicon "arrow-right" %}</a>
|
||||
<div class="d-flex flex-wrap gutter">
|
||||
{% render 'code-example-card' for actionsCodeExamples as example %}
|
||||
</div>
|
||||
|
||||
<button class="js-code-example-show-more btn btn-outline float-right">Show more {% octicon "arrow-right" %}</button>
|
||||
|
||||
<div class="js-code-example-no-results d-none py-4 text-center text-gray font-mktg">
|
||||
<div class="mb-3">{% octicon "search" width="24" %}</div>
|
||||
<h3 class="text-normal">Sorry, there is no result for <strong class="js-code-example-filter-value"></strong></h3>
|
||||
<p class="my-3 f4">It looks like we don't have an example that fits your filter.<br>Try another filter or add your code example</p>
|
||||
<a href="https://github.com/github/docs/blob/main/data/variables/action_code_examples.yml">Learn how to add a code example {% octicon "arrow-right" %}</a>
|
||||
</div>
|
||||
</div>
|
||||
{% endif %}
|
||||
|
||||
@@ -42,7 +42,7 @@ versions:
|
||||
|
||||
#### ステップ
|
||||
|
||||
ステップは、コマンド（_アクション_と呼ばれる）を実行できる個々のタスクです。 ジョブの各ステップは同じランナーで実行され、そのジョブのアクションが互いにデータを共有できるようにします。
|
||||
A step is an individual task that can run commands in a job. A step can be either an _action_ or a shell command. ジョブの各ステップは同じランナーで実行され、そのジョブのアクションが互いにデータを共有できるようにします。
|
||||
|
||||
#### アクション
|
||||
|
||||
@@ -50,7 +50,7 @@ _アクション_は、_ジョブ_を作成するために_ステップ_に結
|
||||
|
||||
#### ランナー
|
||||
|
||||
ランナーは、{% data variables.product.prodname_actions %} ランナーアプリケーションがインストールされているサーバーです。 {% data variables.product.prodname_dotcom %} がホストするランナーを使用することも、自分でランナーをホストすることもできます。 ランナーは、使用可能なジョブをリッスンし、一度に 1 つのジョブを実行し、進行状況、ログ、および結果を {% data variables.product.prodname_dotcom %} に返します。 {% data variables.product.prodname_dotcom %}ホストランナーでは、ワークフロー内の各ジョブは新しい仮想環境で実行されます。
|
||||
A runner is a server that has the [{% data variables.product.prodname_actions %} runner application](https://github.com/actions/runner) installed. {% data variables.product.prodname_dotcom %} がホストするランナーを使用することも、自分でランナーをホストすることもできます。 ランナーは、使用可能なジョブをリッスンし、一度に 1 つのジョブを実行し、進行状況、ログ、および結果を {% data variables.product.prodname_dotcom %} に返します。 {% data variables.product.prodname_dotcom %}ホストランナーでは、ワークフロー内の各ジョブは新しい仮想環境で実行されます。
|
||||
|
||||
{% data variables.product.prodname_dotcom %} ホストランナーは、Ubuntu Linux、Microsoft Windows、および macOS に基づいています。 {% data variables.product.prodname_dotcom %} ホストランナーの詳細については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners)」を参照してください。 別のオペレーティングシステムが必要な場合、または特定のハードウェア設定が必要な場合は、自分のランナーをホストできます。 セルフホストランナーの詳細については、「[自分のランナーをホストする](/actions/hosting-your-own-runners)」を参照してください。
|
||||
|
||||
@@ -197,7 +197,7 @@ YAML 構文を使用してワークフローファイルを作成する方法を
|
||||
|
||||
#### ワークフローファイルの視覚化
|
||||
|
||||
この図では、作成したワークフローファイルと、{% data variables.product.prodname_actions %} コンポーネントが階層にどのように整理されているかを確認できます。 各ステップでは、単一のアクションが実行されます。 ステップ 1 と 2 は、ビルド済みのコミュニティアクションを使用します。 ワークフローのビルド済みアクションの詳細については、「[アクションの検索とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。
|
||||
この図では、作成したワークフローファイルと、{% data variables.product.prodname_actions %} コンポーネントが階層にどのように整理されているかを確認できます。 Each step executes a single action or shell command. ステップ 1 と 2 は、ビルド済みのコミュニティアクションを使用します。 Steps 3 and 4 run shell commands directly on the runner. ワークフローのビルド済みアクションの詳細については、「[アクションの検索とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions)」を参照してください。
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ versions:
|
||||
{% data variables.product.prodname_actions %} の支払いを管理する
|
||||
{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。
|
||||
|
||||
{% data reusables.repositories.permissions-statement-read %}
|
||||
{% data reusables.repositories.permissions-statement-write %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
|
||||
@@ -73,3 +73,69 @@ versions:
|
||||
- 詳細なチュートリアルは、「[{% data variables.product.prodname_actions %}を学ぶ](/actions/learn-github-actions)」
|
||||
- 特定の使用例とサンプルについては、「[ガイド](/actions/guides)」
|
||||
- Super-Linter アクションの設定の詳細については、[github/super-linter](https://github.com/github/super-linter)
|
||||
|
||||
<div id="quickstart-treatment" hidden>
|
||||
|
||||
### Introduction
|
||||
|
||||
Printing "Hello, World!" is a great way to explore the basic set up and syntax of a new programming language. In this guide, you'll use GitHub Actions to print "Hello, World!" within your {% data variables.product.prodname_dotcom %} repository's workflow logs. All you need to get started is a {% data variables.product.prodname_dotcom %} repository where you feel comfortable creating and running a sample {% data variables.product.prodname_actions %} workflow. Feel free to create a new repository for this Quickstart, you can use it to test this and future {% data variables.product.prodname_actions %} workflows.
|
||||
|
||||
### Creating your first workflow
|
||||
|
||||
1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `hello-world.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
|
||||
2. Copy the following YAML contents into the `hello-world.yml` file.
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
name: Say hello!
|
||||
|
||||
# GitHub Actions Workflows are automatically triggered by GitHub events
|
||||
on:
|
||||
# For this workflow, we're using the workflow_dispatch event which is triggered when the user clicks Run workflow in the GitHub Actions UI
|
||||
workflow_dispatch:
|
||||
# The workflow_dispatch event accepts optional inputs so you can customize the behavior of the workflow
|
||||
inputs:
|
||||
name:
|
||||
description: 'Person to greet'
|
||||
required: true
|
||||
default: 'World'
|
||||
# When the event is triggered, GitHub Actions will run the jobs indicated
|
||||
jobs:
|
||||
say_hello:
|
||||
# Uses a ubuntu-lates runner to complete the requested steps
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- run: |
|
||||
echo "Hello ${{ github.event.inputs.name }}!"
|
||||
```
|
||||
{% endraw %}
|
||||
3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
|
||||
|
||||
4. Once the pull request has been merged, you'll be ready to move on to "Trigger your workflow".
|
||||
|
||||
### Trigger your workflow
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
1. In the left sidebar, click the workfow you want to run.
|
||||
|
||||
1. On the right, click the **Run workflow** drop-down and click **Run workflow**. Optionally, you can enter a custom message into the "Person to greet" input before running the workflow.
|
||||
|
||||
1. The workflow run will appear at the top of the list of "Say hello!" workflow runs. Click "Say hello!" to see the result of the workflow run.
|
||||
|
||||
1. In the left sidebar, click the "say_hello" job.
|
||||
|
||||
1. In the workflow logs, expand the 'Run echo "Hello World!"' section.
|
||||
|
||||
|
||||
### More starter workflows
|
||||
|
||||
{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}.
|
||||
|
||||
### Next steps
|
||||
|
||||
The hello-world workflow you just added is a simple example of a manually triggered workflow. This is only the beginning of what you can do with {% data variables.product.prodname_actions %}. リポジトリには、さまざまなイベントに基づいてさまざまなジョブをトリガーする複数のワークフローを含めることができます。 {% data variables.product.prodname_actions %} は、アプリケーション開発プロセスのほぼすべての要素を自動化するのに役立ちます。 開始する場合、 Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial
|
||||
- "[Guides](/actions/guides)" for specific uses cases and examples
|
||||
|
||||
</div>
|
||||
|
||||
@@ -390,6 +390,7 @@ The `issue_comment` event occurs for comments on both issues and pull requests.
|
||||
|
||||
For example, you can choose to run the `pr_commented` job when comment events occur in a pull request, and the `issue_commented` job when comment events occur in an issue.
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
||||
```yaml
|
||||
@@ -416,6 +417,8 @@ jobs:
|
||||
```
|
||||
|
||||
|
||||
{% endraw %}
|
||||
|
||||
|
||||
|
||||
#### `issues`
|
||||
|
||||
@@ -31,7 +31,7 @@ versions:
|
||||
|
||||
{% data variables.product.prodname_dotcom %}は、Microsoft AzureのStandard_DS2_v2仮想マシン上で{% data variables.product.prodname_actions %}ランナーアプリケーションがインストールされたLinux及びWindowsランナーをホストします。 {% data variables.product.prodname_dotcom %}ホストランナーアプリケーションは、Azure Pipelines Agentのフォークです。 インバウンドのICMPパケットはすべてのAzure仮想マシンでブロックされるので、pingやtracerouteコマンドは動作しないでしょう。 For more information about the Standard_DS2_v2 machine resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation.
|
||||
|
||||
{% data variables.product.prodname_dotcom %}は、macOSランナーのホストに[MacStadium](https://www.macstadium.com/)を使用しています。
|
||||
{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud.
|
||||
|
||||
#### {% data variables.product.prodname_dotcom %}ホストランナーの管理権限
|
||||
|
||||
|
||||
@@ -446,7 +446,7 @@ steps:
|
||||
uses: monacorp/action-name@main
|
||||
- name: My backup step
|
||||
if: {% raw %}${{ failure() }}{% endraw %}
|
||||
uses: actions/heroku@master
|
||||
uses: actions/heroku@1.0.0
|
||||
```
|
||||
|
||||
#### **`jobs.<job_id>.steps.name`**
|
||||
@@ -491,10 +491,10 @@ jobs:
|
||||
my_first_job:
|
||||
steps:
|
||||
- name: My first step
|
||||
# 公開リポジトリのデフォルトブランチを使用する
|
||||
uses: actions/heroku@master
|
||||
# Uses the default branch of a public repository
|
||||
uses: actions/heroku@1.0.0
|
||||
- name: My second step
|
||||
# パブリックリポジトリの特定のバージョンタグを使用する
|
||||
# Uses a specific version tag of a public repository
|
||||
uses: actions/aws@v2.0.1
|
||||
```
|
||||
|
||||
@@ -659,7 +659,7 @@ steps:
|
||||
|
||||
- `cmd`
|
||||
- 各エラーコードをチェックしてそれぞれに対応するスクリプトを書く以外、フェイルファースト動作を完全にオプトインする方法はないようです。 デフォルトでその動作を指定することはできないため、この動作はスクリプトに記述する必要があります。
|
||||
- `cmd.exe`は、実行した最後のプログラムのエラーレベルで終了し、runnerにそのエラーコードを返します。 この動作は、これ以前の`sh`および`pwsh`のデフォルト動作と内部的に一貫しており、`cmd.exe`のデフォルトなので、この動作には影響しません。
|
||||
- `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. この動作は、これ以前の`sh`および`pwsh`のデフォルト動作と内部的に一貫しており、`cmd.exe`のデフォルトなので、この動作には影響しません。
|
||||
|
||||
#### **`jobs.<job_id>.steps.with`**
|
||||
|
||||
@@ -718,7 +718,7 @@ steps:
|
||||
entrypoint: /a/different/executable
|
||||
```
|
||||
|
||||
この`entrypoint`キーワードはDockerコンテナのアクションを使おうとしていますが、これは入力を定義しないJavaScriptのアクションにも使えます。
|
||||
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`**
|
||||
|
||||
|
||||
@@ -28,16 +28,7 @@ To configure authentication and user provisioning for {% data variables.product.
|
||||
|
||||
{% if currentVersion == "github-ae@latest" %}
|
||||
|
||||
1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on.
|
||||
|
||||
| Value in Azure AD | Value from {% data variables.product.prodname_ghe_managed %}
|
||||
|:---------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Identifier (Entity ID) | `https://<em>YOUR-GITHUB-AE-HOSTNAME</em><code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="left">Reply URL</td>
|
||||
<td align="left"><code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/saml/consume` |
|
||||
| Sign on URL | <code>https://<em>YOUR-GITHUB-AE-HOSTNAME</em>/sso</code> |
|
||||
1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs.
|
||||
|
||||
1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant.
|
||||
|
||||
|
||||
@@ -38,6 +38,12 @@ After a user successfully authenticates on your IdP, the user's SAML session for
|
||||
|
||||
{% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
|
||||
|
||||
The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
|
||||
|
||||
| IdP | 詳細情報 |
|
||||
|:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Azure AD | [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs |
|
||||
|
||||
During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML Service Provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP.
|
||||
|
||||
| 値 | Other names | 説明 | サンプル |
|
||||
|
||||
@@ -62,7 +62,15 @@ You must have administrative access on your IdP to configure the application for
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "SCIM User Provisioning", select **Require SCIM user provisioning**. 
|
||||
1. [**Save**] をクリックします。 
|
||||
1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}.
|
||||
1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP.
|
||||
|
||||
The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
|
||||
|
||||
| IdP | 詳細情報 |
|
||||
|:-------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs |
|
||||
|
||||
The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.product.product_location %}.
|
||||
|
||||
| 値 | Other names | 説明 | サンプル |
|
||||
|:------------- |:----------------------------------- |:----------------------------------------------------------------------------------------------------------- |:------------------------------------------- |
|
||||
|
||||
@@ -11,7 +11,7 @@ versions:
|
||||
|
||||
### 外部 `collectd` サーバーを設置
|
||||
|
||||
{% data variables.product.product_location %}に`collectd` の転送をまだ有効にしていない場合は、外部の `collectd` サーバを設置する必要があります。 `collectd` サーバは、`collectd` 5.x以上のバージョンを使わなければなりません。
|
||||
{% data variables.product.product_location %}に`collectd` の転送をまだ有効にしていない場合は、外部の `collectd` サーバを設置する必要があります。 Your `collectd` server must be running `collectd` version 5.x or higher.
|
||||
|
||||
1. `collectd` サーバにログインする
|
||||
2. `collectd` を作成、または編集することで、ネットワークプラグインをロードし、適切な値をサーバとポートのディレクティブに追加する。 たいていのディストリビューションでは、これは `/etc/collectd/collectd.conf` にあります。
|
||||
|
||||
@@ -21,7 +21,10 @@ versions:
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告:** 今後使用するバケットを必ず設定してください。 {% data variables.product.prodname_registry %} の使用開始後にストレージを変更することはお勧めしません。
|
||||
**警告:**
|
||||
- It's critical you set the restrictive access policies you want for your storage bucket because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. For more information, see [Setting bucket and object access permissions](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html) in the AWS Documentation.
|
||||
- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
|
||||
- Make sure to configure the bucket you'll want to use in the future. {% data variables.product.prodname_registry %} の使用開始後にストレージを変更することはお勧めしません。
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
title: Enterprise 向けの GitHub Packages を管理する
|
||||
shortTitle: GitHub Packages
|
||||
intro: 'Enterprise で {% data variables.product.prodname_registry %} を有効にして、{% data variables.product.prodname_registry %} 設定と許可されたパッケージタイプを管理できます。'
|
||||
redirect_from:
|
||||
- /enterprise/admin/packages
|
||||
|
||||
@@ -36,17 +36,23 @@ versions:
|
||||
|
||||
#### 部分的なコミットの作成方法
|
||||
|
||||
1つのファイルに複数の変更があり、*一部*だけをコミットに含めたい場合は、部分的なコミットを作成できます。 追加変更やコミットできるように、他の変更はそのまま残ります。 これにより、改行の変更をコードや構文の変更から区別するなど、個別で有意義なコミットの作成が可能になります。
|
||||
If one file contains multiple changes, but you only want some of those changes to be included in a commit, you can create a partial commit. 追加変更やコミットできるように、他の変更はそのまま残ります。 これにより、改行の変更をコードや構文の変更から区別するなど、個別で有意義なコミットの作成が可能になります。
|
||||
|
||||
ファイルのdiffを確認するとき、コミットに含まれる行は青色で強調表示されます。 変更を除外するには、青色が消えるように変更された行をクリックします。
|
||||
{% note %}
|
||||
|
||||
|
||||
**Note:** Split diff displays are currently in beta and subject to change.
|
||||
|
||||
#### 変更の廃棄
|
||||
{% endnote %}
|
||||
|
||||
1つのファイルや複数のファイルのコミットされていない全ての変更の廃棄、または最新コミット以降の全てのファイルの全ての変更の廃棄ができます。
|
||||
1. To choose how your changes are displayed, in the top-right corner of the changed file, use {% octicon "gear" aria-label="The Gear icon" %} to select **Unified** or **Split**. 
|
||||
2. To exclude changed lines from your commit, click one or more changed lines so the blue disappears. The lines that are still highlighted in blue will be included in the commit. 
|
||||
|
||||
{% mac %}
|
||||
### 3. 変更の廃棄
|
||||
If you have uncommitted changes that you don't want to keep, you can discard the changes. This will remove the changes from the files on your computer. You can discard all uncommitted changes in one or more files, or you can discard specific lines you added.
|
||||
|
||||
Discarded changes are saved in a dated file in the Trash. You can recover discarded changes until the Trash is emptied.
|
||||
|
||||
#### Discarding changes in one or more files
|
||||
|
||||
{% data reusables.desktop.select-discard-files %}
|
||||
{% data reusables.desktop.click-discard-files %}
|
||||
@@ -54,30 +60,25 @@ versions:
|
||||
{% data reusables.desktop.confirm-discard-files %}
|
||||
![確定ダイアログ内の [Discard Changes] ボタン](/assets/images/help/desktop/discard-changes-confirm-mac.png)
|
||||
|
||||
{% tip %}
|
||||
#### Discarding changes in one or more lines
|
||||
You can discard one or more changed lines that are uncommitted.
|
||||
|
||||
**ヒント：**廃棄した変更は、Trash内の日付付きファイルに保存され、Trashが空になるまでは復元できます。
|
||||
{% note %}
|
||||
|
||||
{% endtip %}
|
||||
**Note:** Discarding single lines is disabled in a group of changes that adds and removes lines.
|
||||
|
||||
{% endmac %}
|
||||
{% endnote %}
|
||||
|
||||
{% windows %}
|
||||
To discard one added line, in the list of changed lines, right click on the line you want to discard and select **Discard added line**.
|
||||
|
||||
{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %}
|
||||
![コンテキストメニュー内の [Discard Changes] オプション](/assets/images/help/desktop/discard-changes-win.png)
|
||||
{% data reusables.desktop.confirm-discard-files %}
|
||||
![確定ダイアログ内の [Discard Changes] ボタン](/assets/images/help/desktop/discard-changes-confirm-win.png)
|
||||
|
||||
|
||||
{% tip %}
|
||||
To discard a group of changed lines, right click the vertical bar to the right of the line numbers for the lines you want to discard, then select **Discard added lines**.
|
||||
|
||||
**ヒント：**廃棄した変更は、Recycle Bin内のファイルに保存され、空になるまでは復元できます。
|
||||
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
### 3. コミットメッセージの入力と変更のプッシュ
|
||||
### 4. コミットメッセージの入力と変更のプッシュ
|
||||
|
||||
コミットに含めたい変更を決めたら、コミットメッセージを入力して変更をプッシュします。 コミットで共同作業した場合、コミットに 1 人以上の作者を追加できます。
|
||||
|
||||
|
||||
@@ -351,7 +351,7 @@ Checks API を使用すると、ステータス、画像、要約、アノテー
|
||||
|
||||
### ステップ 2.1. Ruby ファイルを追加する
|
||||
|
||||
RuboCop がチェックするため、特定のファイルまたはディレクトリ全体を渡すことができます。 このクイックスタートでは、ディレクトリ全体で RuboCop を実行します。 RuboCop がチェックするのは Ruby のコードのみなので、エラーが含まれる Ruby ファイルをリポジトリ内に最低 1 つ置くとよいでしょう。 以下に示すサンプルのファイルには、いくつかのエラーが含まれています。 Add this example Ruby file to the repository where your app is installed (make sure to name the file with an `.rb` extension, as in `myfile.rb`):
|
||||
RuboCop がチェックするため、特定のファイルまたはディレクトリ全体を渡すことができます。 このクイックスタートでは、ディレクトリ全体で RuboCop を実行します。 RuboCop がチェックするのは Ruby のコードのみなので、エラーが含まれる Ruby ファイルをリポジトリ内に最低 1 つ置くとよいでしょう。 以下に示すサンプルのファイルには、いくつかのエラーが含まれています。 このサンプルの Ruby ファイルを、アプリケーションがインストールされているリポジトリに追加します (`myfile.rb` などのように、ファイル名には `.rb` の拡張子を必ず付けてください)。
|
||||
|
||||
```ruby
|
||||
# The Octocat class tells you about different breeds of Octocat
|
||||
@@ -375,15 +375,15 @@ m.display
|
||||
|
||||
### ステップ 2.2. リポジトリをクローンする
|
||||
|
||||
RuboCop is available as a command-line utility. That means your GitHub App will need to clone a local copy of the repository on the CI server so RuboCop can parse the files. To run Git operations in your Ruby app, you can use the [ruby-git](https://github.com/ruby-git/ruby-git) gem.
|
||||
RuboCop はコマンドラインユーティリティとして使用できます。 これはつまり、RuboCop がファイルを解析するためには、GitHub App が CI サーバー上のリポジトリのローカルコピーをクローンする必要があるということです。 Ruby アプリケーションで Git の操作を実行するには、[ruby-git](https://github.com/ruby-git/ruby-git) gem を使用できます。
|
||||
|
||||
The `Gemfile` in the `building-a-checks-api-ci-server` repository already includes the ruby-git gem, and you installed it when you ran `bundle install` in the [prerequisite steps](#prerequisites). To use the gem, add this code to the top of your `template_server.rb` file:
|
||||
`building-a-checks-api-ci-server` リポジトリの `Gemfile` には既に ruby-git gem が含まれており、[必要な環境のステップ](#prerequisites)で `bundle install` を実行した時にインストール済みです。 gem を使用するには、`template_server.rb` ファイルの先頭に次のコードを追加します。
|
||||
|
||||
``` ruby
|
||||
require 'git'
|
||||
```
|
||||
|
||||
Your app needs read permission for "Repository contents" to clone a repository. Later in this quickstart, you'll need to push contents to GitHub, which requires write permission. Go ahead and set your app's "Repository contents" permission to **Read & write** now so you don't need to update it again later. アプリケーションの権限を更新するには、以下の手順に従います。
|
||||
リポジトリをクローンするには、アプリケーションに「リポジトリコンテンツ」の読み取り権限が必要です。 このクイックスタートでは、後ほどコンテンツを GitHub にプッシュする必要がありますが、そのためには書き込み権限が必要です。 Go ahead and set your app's "Repository contents" permission to **Read & write** now so you don't need to update it again later. アプリケーションの権限を更新するには、以下の手順に従います。
|
||||
|
||||
1. [アプリケーションの設定ページ](https://github.com/settings/apps)からアプリケーションを選択肢、サイドバーの [**Permissions & Webhooks**] をクリックします。
|
||||
1. In the "Permissions" section, find "Repository contents", and select **Read & write** in the "Access" dropdown next to it.
|
||||
|
||||
@@ -34,8 +34,6 @@ Different server-to-server request rate limits apply to {% data variables.produc
|
||||
|
||||
### User-to-server requests
|
||||
|
||||
{% data reusables.apps.deprecating_password_auth %}
|
||||
|
||||
{% data variables.product.prodname_github_app %}s can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
@@ -52,7 +50,7 @@ User-to-server requests are rate limited at 5,000 requests per hour and per auth
|
||||
|
||||
#### {% data variables.product.prodname_ghe_cloud %} user-to-server rate limits
|
||||
|
||||
When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user.
|
||||
When a user belongs to a {% data variables.product.prodname_ghe_cloud %} account, user-to-server requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account are rate limited at 15,000 requests per hour and per authenticated user. All OAuth applications authorized by that user, personal access tokens owned by that user, and {% data variables.product.prodname_ghe_cloud %} requests authenticated with that user's username and password share the same quota of 5,000 requests per hour for that user.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user