Octomerger Bot
@@ -66,9 +66,10 @@ function pullRequestBodyReport() {
|
||||
.forEach((reason) => {
|
||||
const files = filesByReason[reason]
|
||||
body.push(`\n### ${reason}`)
|
||||
body.push(`\n${files.length} files:\n`)
|
||||
body.push(`\n<details><summary>${files.length} files:</summary>\n`)
|
||||
const checkBoxes = files.map((file) => `- [ ] ${file}`)
|
||||
body.push(checkBoxes)
|
||||
body.push('\n</details>')
|
||||
})
|
||||
|
||||
return body.flat().join('\n')
|
||||
|
||||
@@ -19,13 +19,13 @@ topics:
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
{% data reusables.actions.ae-beta %}
|
||||
|
||||
## 概要
|
||||
## Overview
|
||||
|
||||
{% data reusables.actions.workflow-organization-templates %}
|
||||
|
||||
## ワークフロー テンプレートの作成
|
||||
## Creating a workflow template
|
||||
|
||||
ワークフローテンプレートは、Organizationの `.github` リポジトリへの書き込みアクセス権を持つユーザが作成できます。 その後、ワークフローを作成する権限を持つOrganizationのメンバーがテンプレートを使用できます。
|
||||
Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows.
|
||||
|
||||
{% ifversion fpt %}
|
||||
Your workflow templates can be used to create workflows in public repositories only. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use workflow templates to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/learn-github-actions/creating-workflow-templates).
|
||||
@@ -39,15 +39,15 @@ Your workflow templates can be used to create workflows in public repositories o
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
この手順では、ワークフロー テンプレートとメタデータ ファイルを作成する方法を示します。 メタデータ ファイルには、ユーザが新しいワークフローを作成するときにテンプレートがどのように表示されるかについて説明します。
|
||||
This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the template is presented to users when they are creating a new workflow.
|
||||
|
||||
1. 存在しない場合は、Organization内で`.github`という名前の新しいパブリック リポジトリを作成します。
|
||||
2. `workflow-templates`という名前のディレクトリを作成します。
|
||||
3. `workflow-templates` ディレクトリ内に新しいワークフローファイルを作成します。
|
||||
1. If it doesn't already exist, create a new public repository named `.github` in your organization.
|
||||
2. Create a directory named `workflow-templates`.
|
||||
3. Create your new workflow file inside the `workflow-templates` directory.
|
||||
|
||||
リポジトリのデフォルトブランチを参照する必要がある場合は、 `$default-branch` プレースホルダを使用できます。 テンプレートを使用してワークフローを作成すると、プレースホルダはリポジトリのデフォルトブランチの名前に自動的に置き換えられます。
|
||||
If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created using your template, the placeholder will be automatically replaced with the name of the repository's default branch.
|
||||
|
||||
たとえば、`octo-organization-ci.yml`という名前のこのファイルは、基本的なワークフローを示しています。
|
||||
For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow.
|
||||
|
||||
```yaml
|
||||
name: Octo Organization CI
|
||||
@@ -68,7 +68,7 @@ Your workflow templates can be used to create workflows in public repositories o
|
||||
- name: Run a one-line script
|
||||
run: echo Hello from Octo Organization
|
||||
```
|
||||
4. `workflow-templates` ディレクトリ内にメタデータファイルを作成します。 メタデータ ファイルは、ワークフロー ファイルと同じ名前である必要がありますが、 `.yml` 拡張子の代わりに、 `.properties.json`を付ける必要があります。 たとえば`octo-organization-ci.properties.json`という名前のこのファイルには 、`octo-organization-ci.yml`という名前のワークフローファイルのメタデータが含まれています。
|
||||
4. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
|
||||
```yaml
|
||||
{
|
||||
"name": "Octo Organization Workflow",
|
||||
@@ -84,16 +84,16 @@ Your workflow templates can be used to create workflows in public repositories o
|
||||
]
|
||||
}
|
||||
```
|
||||
* `name` - **必須。** ワークフロー テンプレートの名前。 これは、使用可能なテンプレートの一覧に表示されます。
|
||||
* `description` - **必須。** ワークフロー テンプレートの説明。 これは、使用可能なテンプレートの一覧に表示されます。
|
||||
* `iconName` - **必須。** テンプレート リスト内のワークフローのエントリのアイコンを定義します。 `iconName` は、同じ名前の SVG アイコンである必要があり、 `workflow-templates` ディレクトリに格納する必要があります。 たとえば、`example-icon.svg`という名前の SVG ファイルは、 `example-icon`として参照されます。
|
||||
* `categories` - **オプション。** ワークフローの言語カテゴリを定義します。 ユーザーが使用可能なテンプレートを表示する際に、同じ言語に一致するテンプレートが目立つようにになります。 使用可能な言語カテゴリについては、「https://github.com/github/linguist/blob/master/lib/linguist/languages.yml」を参照してください。
|
||||
* `filePatterns` - **オプション 。** 定義された正規表現に一致するファイルがユーザーのリポジトリのルート ディレクトリにある場合に、テンプレートを使用できるようにします。
|
||||
* `name` - **Required.** The name of the workflow template. This is displayed in the list of available templates.
|
||||
* `description` - **Required.** The description of the workflow template. This is displayed in the list of available templates.
|
||||
* `iconName` - **Optional.** Defines an icon for the workflow's entry in the template list. The `iconName` must be an SVG icon of the same name, and must be stored in the `workflow-templates` directory. For example, a SVG file named `example-icon.svg` is referenced as `example-icon`.
|
||||
* `categories` - **Optional.** Defines the language category of the workflow. When a user views the available templates, those templates that match the same language will feature more prominently. For information on the available language categories, see https://github.com/github/linguist/blob/master/lib/linguist/languages.yml.
|
||||
* `filePatterns` - **Optional.** Allows the template to be used if the user's repository has a file in its root directory that matches a defined regular expression.
|
||||
|
||||
別のワークフロー テンプレートを追加するには、同じ `workflow-templates` ディレクトリにファイルを追加します。 例:
|
||||
To add another workflow template, add your files to the same `workflow-templates` directory. For example:
|
||||
|
||||
|
||||
|
||||
|
||||
## 次のステップ
|
||||
## Next steps
|
||||
|
||||
To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Node.jsパッケージの公開
|
||||
intro: 継続的インテグレーション（CI）ワークフローの一部として、Node.jsのパッケージをレジストリに公開できます。
|
||||
title: Publishing Node.js packages
|
||||
intro: You can publish Node.js packages to a registry as part of your continuous integration (CI) workflow.
|
||||
redirect_from:
|
||||
- /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
|
||||
- /actions/language-and-framework-guides/publishing-nodejs-packages
|
||||
@@ -23,44 +23,44 @@ shortTitle: Node.js packages
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
{% data reusables.actions.ae-beta %}
|
||||
|
||||
## はじめに
|
||||
## Introduction
|
||||
|
||||
本ガイドでは、継続的インテグレーション（CI）テストにパスした後、Node.jsのパッケージを{% data variables.product.prodname_registry %}及びnpmレジストリに公開するワークフローの作成方法を紹介します。 1つのワークフローで、パッケージを1つのレジストリや複数のレジストリに公開できます。
|
||||
This guide shows you how to create a workflow that publishes Node.js packages to the {% data variables.product.prodname_registry %} and npm registries after continuous integration (CI) tests pass. With a single workflow, you can publish packages to a single registry or multiple registries.
|
||||
|
||||
## 必要な環境
|
||||
## Prerequisites
|
||||
|
||||
ワークフローの設定オプションと、ワークフローファイルの作成方法についての基本的な知識を持っておくことをおすすめします。 詳しい情報については、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
|
||||
We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
|
||||
|
||||
Node.jsプロジェクトのためのCIワークフローの作成に関する詳しい情報については「[{% data variables.product.prodname_actions %}でのNode.jsの利用](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)」を参照してください。
|
||||
For more information about creating a CI workflow for your Node.js project, see "[Using Node.js with {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)."
|
||||
|
||||
また、以下の基本的な理解があれば役立ちます。
|
||||
You may also find it helpful to have a basic understanding of the following:
|
||||
|
||||
- 「[npm レジストリの利用](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)」
|
||||
- 「[環境変数](/actions/reference/environment-variables)」
|
||||
- 「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」
|
||||
- 「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow)」
|
||||
- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
|
||||
- "[Environment variables](/actions/reference/environment-variables)"
|
||||
- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
|
||||
- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
|
||||
|
||||
## パッケージの設定について
|
||||
## About package configuration
|
||||
|
||||
*package.json*ファイル中の`name`及び`version`フィールドは、レジストリがパッケージをレジストリにリンクするために利用するユニークな識別子を作成します。 *package.json*ファイル中に`description`を含めることによって、パッケージのリストページのためのまとめを追加できます。 詳しい情報については、npmのドキュメンテーション中の「[package.jsonファイルの作成](https://docs.npmjs.com/creating-a-package-json-file)」及び「[Node.jsモジュールの作成](https://docs.npmjs.com/creating-node-js-modules)」を参照してください。
|
||||
The `name` and `version` fields in the *package.json* file create a unique identifier that registries use to link your package to a registry. You can add a summary for the package listing page by including a `description` field in the *package.json* file. For more information, see "[Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file)" and "[Creating Node.js modules](https://docs.npmjs.com/creating-node-js-modules)" in the npm documentation.
|
||||
|
||||
ローカルの*.npmrc*ファイルがあり、`registry`の値が指定されている場合、`npm publish`コマンドは*.npmrc*ファイルで設定されたレジストリを使います。 {% data reusables.github-actions.setup-node-intro %}
|
||||
When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.github-actions.setup-node-intro %}
|
||||
|
||||
`setup-node`アクションを使えば、ランナーにインストールされたNode.jsのバージョンを指定できます。
|
||||
You can specify the Node.js version installed on the runner using the `setup-node` action.
|
||||
|
||||
*package.json*ファイルに`publishConfig`フィールドを設定するステップをワークフローに追加したなら、`setup-node`アクションを使ってregistry-urlを指定する必要はありませんが、パッケージを公開するレジストリは1つだけに限られます。 詳しい情報についてはnpmドキュメンテーションの「[Configの公開](https://docs.npmjs.com/files/package.json#publishconfig)」を参照してください。
|
||||
If you add steps in your workflow to configure the `publishConfig` fields in your *package.json* file, you don't need to specify the registry-url using the `setup-node` action, but you will be limited to publishing the package to one registry. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
|
||||
|
||||
## npmレジストリへのパッケージの公開
|
||||
## Publishing packages to the npm registry
|
||||
|
||||
新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすればnpmレジストリにパッケージを公開します。
|
||||
Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs when the `release` event triggers with type `created`. The workflow publishes the package to the npm registry if CI tests pass.
|
||||
|
||||
ワークフロー中で npm レジストリに対して認証を受けた操作を行うためには、npm の認証トークンをシークレットとして保存しなければなりません。 たとえば、`NPM_TOKEN` というリポジトリシークレットを作成します。 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
|
||||
To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
|
||||
|
||||
デフォルトでは、npmは*package.json*ファイルの`name`フィールドを使ってnpmレジストリを決めます。 グローバルな名前空間に公開する場合は、パッケージ名だけを含める必要があります。 たとえば`https://www.npmjs.com/package/npm-hello-world-test`に`npm-hello-world-test`という名前のパッケージを公開できます。
|
||||
By default, npm uses the `name` field of the *package.json* file to determine the npm registry. When publishing to a global namespace, you only need to include the package name. For example, you would publish a package named `npm-hello-world-test` to the `https://www.npmjs.com/package/npm-hello-world-test`.
|
||||
|
||||
スコープのプレフィックスを含むパッケージを公開するなら、そのスコープを*package.json*ファイルの名前に含めてください。 たとえばnpmのスコーププレフィックスがoctocatであり、パッケージ名がhello-worldなら、*package.json*ファイル中の`name`は`@octocat/hello-world`とすべきです。 npmパッケージがスコーププレフィックスを使っており、パブリックであるなら、`npm publish --access public`オプションを使う必要があります。 これは、意図せずプライベートパッケージを公開してしまうことを防ぐためにnpmが必要とするオプションです。
|
||||
If you're publishing a package that includes a scope prefix, include the scope in the name of your *package.json* file. For example, if your npm scope prefix is octocat and the package name is hello-world, the `name` in your *package.json* file should be `@octocat/hello-world`. If your npm package uses a scope prefix and the package is public, you need to use the option `npm publish --access public`. This is an option that npm requires to prevent someone from publishing a private package unintentionally.
|
||||
|
||||
以下の例は、`NPM_TOKEN`シークレットを環境変数の`NODE_AUTH_TOKEN`に保存します。 `setup-node`アクションが*.npmrc*ファイルを作成する際には、環境変数の`NODE_AUTH_TOKEN`からトークンを参照します。
|
||||
This example stores the `NPM_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable.
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -73,19 +73,19 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
# npm に公開するように .npmrc ファイルを設定する
|
||||
# Setup .npmrc file to publish to npm
|
||||
- uses: actions/setup-node@v2
|
||||
with:
|
||||
node-version: '12.x'
|
||||
registry-url: 'https://registry.npmjs.org'
|
||||
- run: npm install
|
||||
- run: npm ci
|
||||
- run: npm publish
|
||||
env:
|
||||
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
上の例では、`setup-node`アクションは以下の内容でランナー上に*.npmrc*ファイルを作成します。
|
||||
In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents:
|
||||
|
||||
```ini
|
||||
//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
|
||||
@@ -93,15 +93,15 @@ registry=https://registry.npmjs.org/
|
||||
always-auth=true
|
||||
```
|
||||
|
||||
## {% data variables.product.prodname_registry %}へのパッケージの公開
|
||||
## Publishing packages to {% data variables.product.prodname_registry %}
|
||||
|
||||
新しいリリースを作成するたびに、パッケージを公開するワークフローを起動できます。 以下の例でのワークフローは、`created`という種類で`release`イベントが発生したときに実行されます。 このワークフローは、CIテストをパスすれば{% data variables.product.prodname_registry %}にパッケージを公開します。
|
||||
Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass.
|
||||
|
||||
### 宛先リポジトリの設定
|
||||
### Configuring the destination repository
|
||||
|
||||
*package.json* ファイルで `repository` キーを指定しない場合、{% data variables.product.prodname_registry %} は *package.json* ファイルの `name` フィールドで指定した {% data variables.product.prodname_dotcom %} リポジトリにパッケージを公開します。 たとえば、`@my-org/test` という名前のパッケージは、`my-org/test` {% data variables.product.prodname_dotcom %} というリポジトリに公開されます。
|
||||
If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository.
|
||||
|
||||
ただし、`repository` キーを指定すると、そのキーのリポジトリが {% data variables.product.prodname_registry %} の宛先 npm レジストリとして使用されます。 たとえば、以下の *package.json* を公開すると、`my-amazing-package` という名前のパッケージが `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} リポジトリに公開されます。
|
||||
However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository.
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -112,15 +112,15 @@ always-auth=true
|
||||
},
|
||||
```
|
||||
|
||||
### 宛先リポジトリへの認証
|
||||
### Authenticating to the destination repository
|
||||
|
||||
ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`GITHUB_TOKEN`が使えます。 {% data reusables.github-actions.github-token-permissions %}
|
||||
To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
|
||||
|
||||
パッケージを別のリポジトリに公開する場合は、宛先リポジトリ内のパッケージに書き込む権限を持つ個人アクセストークン (PAT) を使用する必要があります。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」および「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。
|
||||
If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
|
||||
|
||||
### ワークフローの例
|
||||
### Example workflow
|
||||
|
||||
以下の例は、`GITHUB_TOKEN`シークレットを環境変数の`NODE_AUTH_TOKEN`に保存します。 `setup-node`アクションが*.npmrc*ファイルを作成する際には、環境変数の`NODE_AUTH_TOKEN`からトークンを参照します。
|
||||
This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Node.js Package
|
||||
@@ -142,13 +142,13 @@ jobs:
|
||||
registry-url: 'https://npm.pkg.github.com'
|
||||
# Defaults to the user or organization that owns the workflow file
|
||||
scope: '@octocat'
|
||||
- run: npm install
|
||||
- run: npm ci
|
||||
- run: npm publish
|
||||
env:
|
||||
NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
|
||||
```
|
||||
|
||||
`setup-node`アクションは、ランナー上で*.npmrc*ファイルを作成します。 `setup-node`アクションで`scope`インプットを使うと、*.npmrc*ファイルにはスコーププレフィックスが含まれます。 デフォルトでは、`setup-node`アクションは*.npmrc*ファイルのスコープを、ワークフローファイルを含むアカウントに設定します。
|
||||
The `setup-node` action creates an *.npmrc* file on the runner. When you use the `scope` input to the `setup-node` action, the *.npmrc* file includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the account that contains that workflow file.
|
||||
|
||||
```ini
|
||||
//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
|
||||
@@ -156,9 +156,9 @@ jobs:
|
||||
always-auth=true
|
||||
```
|
||||
|
||||
## yarnを利用したパッケージの公開
|
||||
## Publishing packages using yarn
|
||||
|
||||
パッケージマネージャーのYarnを使う場合、Yarnを使ってパッケージのインストールと公開が行えます。
|
||||
If you use the Yarn package manager, you can install and publish packages using Yarn.
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -171,12 +171,12 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v2
|
||||
# npm に公開するように .npmrc ファイルを設定する
|
||||
# Setup .npmrc file to publish to npm
|
||||
- uses: actions/setup-node@v2
|
||||
with:
|
||||
node-version: '12.x'
|
||||
registry-url: 'https://registry.npmjs.org'
|
||||
# 既定値はワークフローファイルを所有するユーザまたは Organization
|
||||
# Defaults to the user or organization that owns the workflow file
|
||||
scope: '@octocat'
|
||||
- run: yarn
|
||||
- run: yarn publish
|
||||
@@ -185,25 +185,25 @@ jobs:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
## npmと{% data variables.product.prodname_registry %}へのパッケージの公開
|
||||
## Publishing packages to npm and {% data variables.product.prodname_registry %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**ノート：** 異なるスコーププレフィックスを持つレジストリへ公開する必要がある場合は、ランナー上の*package.json*ファイルを修正してスコーププレフィックスを変更しなければなりません。 たとえばnpmに対しては`@mona`スコープで、{% data variables.product.prodname_registry %}に対しては`@octocat`スコープでパッケージを公開する場合は、npmへの公開後、{% data variables.product.prodname_registry %}への公開前にランナー上の*package.json*ファイルの`@mona`スコープを`@octocat`で置き換えることができます。
|
||||
**Note:** If you need to publish to registries that have different scope prefixes, you'll need to modify the *package.json* file on the runner to change the scope prefix. For example, if you publish a package to the `@mona` scope for npm and `@octocat` scope for {% data variables.product.prodname_registry %}, you can replace the `@mona` scope with `@octocat` in the *package.json* file on the runner after publishing to npm and before publishing to {% data variables.product.prodname_registry %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
`setup-node`アクションをそれぞれのレジストリに対して利用すれば、npmレジストリと{% data variables.product.prodname_registry %}の両方にパッケージを公開できます。
|
||||
You can publish your packages to both the npm registry and {% data variables.product.prodname_registry %} by using the `setup-node` action for each registry.
|
||||
|
||||
両方のレジストリにパッケージを公開するなら、npm上のスコーププレフィックスが{% data variables.product.prodname_dotcom %}のユーザ名もしくはOrganization名と一致することを確認する必要があります。 パッケージをスコーププレフィックス付きでパブリックなレジストリに公開するには、`npm publish --access public`コマンドが使えます。 詳しい情報については、npmドキュメンテーション中の[`npm-scope`](https://docs.npmjs.com/misc/scope)及び「[スコープ付きのパブリックパッケージの作成と公開](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)」を参照してください。
|
||||
If you publish a package to both registries, you'll need to ensure that your scope prefix on npm matches your {% data variables.product.prodname_dotcom %} user or organization name. To publish packages to a public registry with a scope prefix, you can use the command `npm publish --access public`. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope) and "[Creating and publishing scoped public packages](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)" in the npm documentation.
|
||||
|
||||
*package.json*ファイルに{% data variables.product.prodname_dotcom %}レジストリとnpmレジストリのスコープが含まれていることを確かめてください。 たとえば、`octocat/npm-hello-world-test`リポジトリ内のパッケージを{% data variables.product.prodname_dotcom %}及びhttps://www.npmjs.com/package/@octocat/npm-hello-world-testに公開する計画をしているなら、*package.json*ファイル内の名前は`"name": "@octocat/npm-hello-world-test"`となるでしょう。
|
||||
Ensure your *package.json* file includes the scope of your {% data variables.product.prodname_dotcom %} repository and npm registry. For example, if you plan to publish a package in the `octocat/npm-hello-world-test` repository to {% data variables.product.prodname_dotcom %} and https://www.npmjs.com/package/@octocat/npm-hello-world-test, the name in your *package.json* file would be `"name": "@octocat/npm-hello-world-test"`.
|
||||
|
||||
ワークフロー中で{% data variables.product.prodname_registry %}レジストリに対して認証を受けた操作をするには、`GITHUB_TOKEN`が使えます。 {% data reusables.github-actions.github-token-permissions %}
|
||||
To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
|
||||
|
||||
`setup-node`アクションで`scope`インプットを使うと、このアクションはスコーププレフィックスを含む*.npmrc*ファイルを作成します。 デフォルトでは、`setup-node`アクションは*.npmrc*ファイル中のスコープを、ワークフローファイルを所有するユーザもしくはOrganizationに設定します。
|
||||
When you use the `scope` input to the `setup-node` action, the action creates an *.npmrc* file that includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the user or organization that owns the workflow file.
|
||||
|
||||
このワークフローは、`setup-node`アクションを2回呼びます。 `setup-node`アクションは、実行されるたびに*.npmrc*ファイルを上書きします。 *.npmrc*ファイルは、パッケージレジストリに対する認証を受けた操作を行えるようにしてくれるトークンを、環境変数の`NODE_AUTH_TOKEN`から参照します。 このワークフローは、環境変数の`NODE_AUTH_TOKEN`を`npm publish`コマンドが実行されるたびに設定します。初回はnpmへの公開のためのトークン（`NPM_TOKEN`）が、続いて{% data variables.product.prodname_registry %}への公開のためのトークン（`GITHUB_TOKEN`）が使われます。
|
||||
This workflow calls the `setup-node` action two times. Each time the `setup-node` action runs, it overwrites the *.npmrc* file. The *.npmrc* file references the token that allows you to perform authenticated operations against the package registry from the `NODE_AUTH_TOKEN` environment variable. The workflow sets the `NODE_AUTH_TOKEN` environment variable each time the `npm publish` command is run, first with a token to publish to npm (`NPM_TOKEN`) and then with a token to publish to {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`).
|
||||
|
||||
|
||||
```yaml{:copy}
|
||||
@@ -224,7 +224,7 @@ jobs:
|
||||
with:
|
||||
node-version: '10.x'
|
||||
registry-url: 'https://registry.npmjs.org'
|
||||
- run: npm install
|
||||
- run: npm ci
|
||||
# Publish to npm
|
||||
- run: npm publish --access public
|
||||
env:{% raw %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: セキュリティログをレビューする
|
||||
intro: ユーザアカウントのセキュリティログをレビューして、自分が実行したアクションと、他のユーザが実行したアクションについて詳しく知ることができます。
|
||||
title: Reviewing your security log
|
||||
intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /articles/reviewing-your-security-log
|
||||
@@ -14,258 +14,254 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: セキュリティ ログ
|
||||
shortTitle: Security log
|
||||
---
|
||||
|
||||
## セキュリティログにアクセスする
|
||||
## Accessing your security log
|
||||
|
||||
The security log lists all actions performed within the last 90 days.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
2. ユーザ設定サイドバーで [**Security log**] をクリックします。 
|
||||
2. In the user settings sidebar, click **Security log**.
|
||||
|
||||
{% else %}
|
||||
{% data reusables.user_settings.security %}
|
||||
3. [Security history] の下に、自分のログが表示されます。 
|
||||
4. エントリをクリックして、イベントに関する詳細情報を表示します。 
|
||||
3. Under "Security history," your log is displayed.
|
||||
|
||||
4. Click on an entry to see more information about the event.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
## セキュリティログを検索する
|
||||
## Searching your security log
|
||||
|
||||
{% data reusables.audit_log.audit-log-search %}
|
||||
|
||||
### 実行されたアクションに基づく検索
|
||||
### Search based on the action performed
|
||||
{% else %}
|
||||
## セキュリティログでのイベントを理解する
|
||||
## Understanding events in your security log
|
||||
{% endif %}
|
||||
|
||||
セキュリティログにリストされているイベントは、アクションによってトリガーされます。 アクションは次のカテゴリに分類されます。
|
||||
The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
|
||||
|
||||
| カテゴリ名 | 説明 |
|
||||
| -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
|
||||
| [`account_recovery_token`](#account_recovery_token-category-actions) | | カテゴリ名 | 説明 [リカバリトークンの追加](/articles/configuring-two-factor-authentication-recovery-methods)に関連するすべての活動が対象です。 |
|
||||
| [`支払い`](#billing-category-actions) | 自分の支払い情報に関連するすべての活動が対象です。 |
|
||||
| [`codespaces`](#codespaces-category-actions) | {% data variables.product.prodname_codespaces %} に関連するすべての活動が対象です。 詳しい情報については、「[{% data variables.product.prodname_codespaces %} について](/github/developing-online-with-codespaces/about-codespaces)」を参照してください。 |
|
||||
| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。 |
|
||||
| [`marketplace_listing`](#marketplace_listing-category-actions) | {% data variables.product.prodname_marketplace %} に一覧表示しているアプリに関連するすべての活動が対象です。{% endif %}
|
||||
| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
|
||||
| [`payment_method`](#payment_method-category-actions) | {% data variables.product.prodname_dotcom %} プランに対する支払いに関連するすべての活動が対象です。{% endif %}
|
||||
| [`profile_picture`](#profile_picture-category-actions) | 自分のプロファイル写真に関連するすべての活動が対象です。 |
|
||||
| [`project`](#project-category-actions) | プロジェクト ボードに関連するすべての活動が対象です。 |
|
||||
| [`public_key`](#public_key-category-actions) | [公開 SSH キー](/articles/adding-a-new-ssh-key-to-your-github-account)に関連するすべての活動が対象です。 |
|
||||
| [`repo`](#repo-category-actions) | 自分が所有するリポジトリに関連するすべての活動が対象です。{% ifversion fpt or ghec %}
|
||||
| [`sponsors`](#sponsors-category-actions) | {% data variables.product.prodname_sponsors %} およびスポンサーボタンに関連するすべてのイベントが対象です (「[{% data variables.product.prodname_sponsors %} について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)」と「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照){% endif %}{% ifversion ghes or ghae %}
|
||||
| [`Team`](#team-category-actions) | 所属する Team に関連するすべてのアクティビティが対象です。{% endif %}{% ifversion not ghae %}
|
||||
| [`two_factor_authentication`](#two_factor_authentication-category-actions) | [2 要素認証](/articles/securing-your-account-with-two-factor-authentication-2fa)に関連するすべてのアクティビティが対象です。{% endif %}
|
||||
| [`ユーザ`](#user-category-actions) | アカウントに関連するすべての活動が対象です。 |
|
||||
| Category name | Description
|
||||
|------------------|-------------------{% ifversion fpt or ghec %}
|
||||
| [`billing`](#billing-category-actions) | Contains all activities related to your billing information.
|
||||
| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."
|
||||
| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}
|
||||
| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
|
||||
| [`payment_method`](#payment_method-category-actions) | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %}
|
||||
| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your profile picture.
|
||||
| [`project`](#project-category-actions) | Contains all activities related to project boards.
|
||||
| [`public_key`](#public_key-category-actions) | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account).
|
||||
| [`repo`](#repo-category-actions) | Contains all activities related to the repositories you own.{% ifversion fpt or ghec %}
|
||||
| [`sponsors`](#sponsors-category-actions) | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% ifversion ghes or ghae %}
|
||||
| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% ifversion not ghae %}
|
||||
| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
|
||||
| [`user`](#user-category-actions) | Contains all activities related to your account.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## セキュリティログをエクスポートする
|
||||
## Exporting your security log
|
||||
|
||||
{% data reusables.audit_log.export-log %}
|
||||
{% data reusables.audit_log.exported-log-keys-and-values %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## セキュリティログのアクション
|
||||
## Security log actions
|
||||
|
||||
セキュリティログにイベントとして記録される最も一般的なアクションの概要です。
|
||||
An overview of some of the most common actions that are recorded as events in the security log.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
### `account_recovery_token` カテゴリアクション
|
||||
### `billing` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| --------------- | ----------------------------------------------------------------------------------------------------------- |
|
||||
| `confirm` | 正常に[リカバリプロバイダ付きの新たなトークンを保存する](/articles/configuring-two-factor-authentication-recovery-methods)ときにトリガーされます。 |
|
||||
| `recover` | 正常に[アカウント リカバリ トークンを引き換える](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)ときにトリガーされます。 |
|
||||
| `recover_error` | トークンが使用されているにもかかわらず {% data variables.product.prodname_dotcom %} がそれを有効にできないときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
|
||||
| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address).
|
||||
|
||||
### `billing` カテゴリアクション
|
||||
### `codespaces` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| --------------------- | -------------------------------------------------------------------------------------------------------------------- |
|
||||
| `change_billing_type` | {% data variables.product.prodname_dotcom %} の[支払い方法を変更する](/articles/adding-or-editing-a-payment-method)ときにトリガーされます。 |
|
||||
| `change_email` | [自分のメール アドレスを変更する](/articles/changing-your-primary-email-address)ときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [create a codespace](/github/developing-online-with-codespaces/creating-a-codespace).
|
||||
| `resume` | Triggered when you resume a suspended codespace.
|
||||
| `delete` | Triggered when you [delete a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).
|
||||
| `manage_access_and_security` | Triggered when you update [the repositories a codespace has access to](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
|
||||
### `codespaces` カテゴリアクション
|
||||
### `marketplace_agreement_signature` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `create` | [コードスペースを作成](/github/developing-online-with-codespaces/creating-a-codespace)するとトリガーされます。 |
|
||||
| `resume` | 中断されたコードスペースを再開するとトリガーされます。 |
|
||||
| `delete` | [コードスペースを削除](/github/developing-online-with-codespaces/deleting-a-codespace)するとトリガーされます。 |
|
||||
| `manage_access_and_security` | [コードスペースがアクセスできるリポジトリ](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)を更新するとトリガーされます。 |
|
||||
| `trusted_repositories_access_update` | ユーザーアカウントの [ アクセスと、{% data variables.product.prodname_codespaces %} のセキュリティ設定](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)を変更するとトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
|
||||
### `marketplace_agreement_signature` カテゴリアクション
|
||||
### `marketplace_listing` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| -------- | --------------------------------------------------------------------------------------- |
|
||||
| `create` | {% data variables.product.prodname_marketplace %} Developer Agreement に署名するときにトリガーされます。 |
|
||||
|
||||
### `marketplace_listing` カテゴリアクション
|
||||
|
||||
| アクション | 説明 |
|
||||
| --------- | ----------------------------------------------------------------------------------- |
|
||||
| `承認` | 一覧表を {% data variables.product.prodname_marketplace %}に掲載することが承認されるときにトリガーされます。 |
|
||||
| `create` | {% data variables.product.prodname_marketplace %} で自分のアプリケーションの一覧表を作成するときにトリガーされます。 |
|
||||
| `delist` | 一覧表が {% data variables.product.prodname_marketplace %} から削除されるときにトリガーされます。 |
|
||||
| `redraft` | 一覧表がドラフト状態に戻されるときにトリガーされます。 |
|
||||
| `reject` | 一覧表が {% data variables.product.prodname_marketplace %} に掲載することを認められないときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
|
||||
| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
|
||||
| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
|
||||
| `redraft` | Triggered when your listing is sent back to draft state.
|
||||
| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### `oauth_authorization` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
|
||||
| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
### `payment_method` カテゴリアクション
|
||||
### `payment_method` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| -------- | -------------------------------------------------------------------- |
|
||||
| `clear` | ファイルでの[支払い方法](/articles/removing-a-payment-method)が削除されるときにトリガーされます。 |
|
||||
| `create` | 新しいクレジット カードや PayPal アカウントなど、新たな支払い方法が追加されるときにトリガーされます。 |
|
||||
| `update` | 既存の支払い方法が更新されるときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed.
|
||||
| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account.
|
||||
| `update` | Triggered when an existing payment method is updated.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### `profile_picture` カテゴリアクション
|
||||
### `profile_picture` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| -------- | ---------------------------------------------------------------------------- |
|
||||
| `update` | [自分のプロフィール写真を設定または更新する](/articles/setting-your-profile-picture/)ときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/).
|
||||
|
||||
### `project` カテゴリアクション
|
||||
### `project` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| ------------------------ | ----------------------------------------------------------------------- |
|
||||
| `access` | プロジェクト ボードの可視性が変更されるときにトリガーされます。 |
|
||||
| `create` | プロジェクト ボードが作成されるときにトリガーされます。 |
|
||||
| `rename` | プロジェクトボードの名前が変更されるときにトリガーされます。 |
|
||||
| `update` | プロジェクト ボードが更新されるときにトリガーされます。 |
|
||||
| `delete` | プロジェクトボードが削除されるときにトリガーされます。 |
|
||||
| `link` | リポジトリがプロジェクト ボードにリンクされるときにトリガーされます。 |
|
||||
| `unlink` | リポジトリがプロジェクトボードからリンク解除されるときにトリガーされます。 |
|
||||
| `update_user_permission` | 外部のコラボレータがプロジェクトボードに追加またはプロジェクトボードから削除されたとき、あるいは許可レベルが変更されたときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `access` | Triggered when a project board's visibility is changed.
|
||||
| `create` | Triggered when a project board is created.
|
||||
| `rename` | Triggered when a project board is renamed.
|
||||
| `update` | Triggered when a project board is updated.
|
||||
| `delete` | Triggered when a project board is deleted.
|
||||
| `link` | Triggered when a repository is linked to a project board.
|
||||
| `unlink` | Triggered when a repository is unlinked from a project board.
|
||||
| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed.
|
||||
|
||||
### `public_key` カテゴリアクション
|
||||
### `public_key` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). |
|
||||
| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys). |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account).
|
||||
| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).
|
||||
|
||||
### `repo` カテゴリアクション
|
||||
### `repo` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `access` | 自分が所有するリポジトリが["プライベート" から "パブリック" に切り替えられる](/articles/making-a-private-repository-public) (またはその逆) ときにトリガーされます。 |
|
||||
| `add_member` | {% data variables.product.product_name %} ユーザがリポジトリへの {% ifversion fpt or ghec %}[共同アクセス権を保有するように招待される](/articles/inviting-collaborators-to-a-personal-repository){% else %}[共同アクセス権を付与される](/articles/inviting-collaborators-to-a-personal-repository){% endif %}ときにトリガーされます。 |
|
||||
| `add_topic` | リポジトリのオーナーがリポジトリに[トピックを追加する](/articles/classifying-your-repository-with-topics)ときにトリガーされます。 |
|
||||
| `archived` | リポジトリのオーナーが[リポジトリをアーカイブする](/articles/about-archiving-repositories)ときにトリガーされます。{% ifversion ghes %}
|
||||
| `config.disable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが無効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。 |
|
||||
| `config.enable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが有効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。 |
|
||||
| `config.lock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロックされる](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。 |
|
||||
| `config.unlock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロック解除される](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。{% endif %}
|
||||
| `create` | [新たなリポジトリが作成される](/articles/creating-a-new-repository)ときにトリガーされます。 |
|
||||
| `destroy` | [リポジトリが削除される](/articles/deleting-a-repository)ときにトリガーされます。{% ifversion fpt or ghec %}
|
||||
| `disable` | リポジトリが無効になるときにトリガーされます ([残高不足](/articles/unlocking-a-locked-account)などの場合)。{% endif %}{% ifversion fpt or ghec %}
|
||||
| `enable` | リポジトリが再び有効になるときにトリガーされます。{% endif %}
|
||||
| `remove_member` | {% data variables.product.product_name %}ユーザが[リポジトリのコラボレーターではなくなる](/articles/removing-a-collaborator-from-a-personal-repository)ときにトリガーされます。 |
|
||||
| `remove_topic` | リポジトリのオーナーがリポジトリからトピックを削除するときにトリガーされます。 |
|
||||
| `rename` | [リポジトリの名前が変更される](/articles/renaming-a-repository)ときにトリガーされます。 |
|
||||
| `移譲` | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。 |
|
||||
| `transfer_start` | リポジトリの移譲が行われようとしているときにトリガーされます。 |
|
||||
| `unarchived` | リポジトリのオーナーがリポジトリをアーカイブ解除するときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa).
|
||||
| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository.
|
||||
| `add_topic` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
|
||||
| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
|
||||
| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
|
||||
| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
|
||||
| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
|
||||
| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
|
||||
| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).
|
||||
| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
|
||||
| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
|
||||
| `enable` | Triggered when a repository is re-enabled.{% endif %}
|
||||
| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
|
||||
| `remove_topic` | Triggered when a repository owner removes a topic from a repository.
|
||||
| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
|
||||
| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
|
||||
| `transfer_start` | Triggered when a repository transfer is about to occur.
|
||||
| `unarchived` | Triggered when a repository owner unarchives a repository.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### `sponsors` カテゴリアクション
|
||||
### `sponsors` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `custom_amount_settings_change` | カスタム金額を有効または無効にするとき、または提案されたカスタム金額を変更するときにトリガーされます (「[スポンサーシップ層を管理する](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)」を参照)。 |
|
||||
| `repo_funding_links_file_action` | リポジトリで FUNDING ファイルを変更したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) |
|
||||
| `sponsor_sponsorship_cancel` | スポンサーシップをキャンセルしたときにトリガーされます (「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照) |
|
||||
| `sponsor_sponsorship_create` | アカウントをスポンサーするとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)」を参照) |
|
||||
| `sponsor_sponsorship_payment_complete` | アカウントをスポンサーし、支払が処理されるとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)」を参照) |
|
||||
| `sponsor_sponsorship_preference_change` | スポンサード開発者からメールで最新情報を受け取るかどうかを変更するとトリガーされます (「[スポンサーシップを管理する](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)」を参照) |
|
||||
| `sponsor_sponsorship_tier_change` | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照) |
|
||||
| `sponsored_developer_approve` | {% data variables.product.prodname_sponsors %} アカウントが承認されるとトリガーされます (「[ユーザアカウントに{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照) |
|
||||
| `sponsored_developer_create` | {% data variables.product.prodname_sponsors %} アカウントが作成されるとトリガーされます (「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照) |
|
||||
| `sponsored_developer_disable` | {% data variables.product.prodname_sponsors %} アカウントが無効になるとトリガーされます |
|
||||
| `sponsored_developer_redraft` | {% data variables.product.prodname_sponsors %} アカウントが承認済みの状態からドラフト状態に戻るとトリガーされます |
|
||||
| `sponsored_developer_profile_update` | スポンサード開発者のプロフィールを編集するとトリガーされます (「[{% data variables.product.prodname_sponsors %} のプロフィール詳細を編集する](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)」を参照) |
|
||||
| `sponsored_developer_request_approval` | 承認のために {% data variables.product.prodname_sponsors %} のアプリケーションをサブミットするとトリガーされます (「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照) |
|
||||
| `sponsored_developer_tier_description_update` | スポンサーシップ層の説明を変更したときにトリガーされます (「[スポンサーシップ層を管理する](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)」を参照) |
|
||||
| `sponsored_developer_update_newsletter_send` | スポンサーにメールで最新情報を送信するとトリガーされます (「[スポンサーに連絡する](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)」を参照) |
|
||||
| `waitlist_invite_sponsored_developer` | 待ちリストから {% data variables.product.prodname_sponsors %} に参加するよう招待されたときにトリガーされます (「[ユーザアカウントに{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照) |
|
||||
| `waitlist_join` | スポンサード開発者になるために待ちリストに参加するとトリガーされます (「[ユーザアカウントに {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)」を参照) |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")
|
||||
| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")
|
||||
| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
|
||||
| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
|
||||
| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
|
||||
| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")
|
||||
| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
|
||||
| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled
|
||||
| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state
|
||||
| `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")
|
||||
| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")
|
||||
| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")
|
||||
| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### `successor_invitation` カテゴリアクション
|
||||
### `successor_invitation` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `accept` | 継承の招待を承諾するとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照） |
|
||||
| `cancel` | 継承の招待をキャンセルするとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照） |
|
||||
| `create` | 継承の招待を作成するとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照） |
|
||||
| `decline` | 継承の招待を拒否するとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照） |
|
||||
| `revoke` | 継承の招待を取り消すとトリガーされます（「[ユーザアカウントのリポジトリの所有権の継続性を管理する](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)」を参照） |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
|
||||
### `team` カテゴリアクション
|
||||
### `team` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| ------------------- | ------------------------------------------------------------------------------------------------------------- |
|
||||
| `add_member` | 自分が所属している Organization のメンバーが[自分を Team に追加する](/articles/adding-organization-members-to-a-team)ときにトリガーされます。 |
|
||||
| `add_repository` | 自分がメンバーである Team にリポジトリの管理が任せられるときにトリガーされます。 |
|
||||
| `create` | 自分が所属している Organization で新たな Team が作成されるときにトリガーされます。 |
|
||||
| `destroy` | 自分がメンバーである Team が Organization から削除されるときにトリガーされます。 |
|
||||
| `remove_member` | Organization のメンバーが自分がメンバーである [Team から削除される](/articles/removing-organization-members-from-a-team)ときにトリガーされます。 |
|
||||
| `remove_repository` | リポジトリが Team の管理下でなくなるときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team).
|
||||
| `add_repository` | Triggered when a team you are a member of is given control of a repository.
|
||||
| `create` | Triggered when a new team in an organization you belong to is created.
|
||||
| `destroy` | Triggered when a team you are a member of is deleted from the organization.
|
||||
| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of.
|
||||
| `remove_repository` | Triggered when a repository is no longer under a team's control.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion not ghae %}
|
||||
### `two_factor_authentication` カテゴリアクション
|
||||
### `two_factor_authentication` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| ---------- | ---------------------------------------------------------------------------------------------- |
|
||||
| `enabled` | [2 要素認証](/articles/securing-your-account-with-two-factor-authentication-2fa)が有効になるときにトリガーされます。 |
|
||||
| `disabled` | 2 要素認証が無効になるときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled.
|
||||
| `disabled` | Triggered when two-factor authentication is disabled.
|
||||
{% endif %}
|
||||
|
||||
### `user` カテゴリアクション
|
||||
### `user` category actions
|
||||
|
||||
| アクション | 説明 |
|
||||
| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `add_email` | トリガーされる条件 |
|
||||
| {% ifversion not ghae %}[新しいメールアドレスを追加する](/articles/changing-your-primary-email-address){% else %}新しいメールアドレスを追加する{% endif %}。{% ifversion fpt or ghec %} | |
|
||||
| `codespaces_trusted_repo_access_granted` | リポジトリに作成する Codespaces で、自分のユーザーアカウントが所有している他のリポジトリにアクセスするのを許可するとトリガーされます (/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |
|
||||
| `codespaces_trusted_repo_access_revoked` | リポジトリに作成する Codespaces で、自分のユーザーアカウントが所有している他のリポジトリにアクセスするのを禁止するとトリガーされます (/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. |{% endif %}
|
||||
| `create` | 新しいユーザアカウントを作成するとトリガーされます。{% ifversion not ghae %}
|
||||
| `change_password` | 自分のパスワードを変更するときにトリガーされます。 |
|
||||
| `forgot_password` | [パスワード のリセット](/articles/how-can-i-reset-my-password)を要求したときにトリガーされます。{% endif %}
|
||||
| `hide_private_contributions_count` | [自分のプロファイルでプライベート コントリビューションを非表示にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)ときにトリガーされます。 |
|
||||
| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
|
||||
| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.
|
||||
| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. {% endif %}
|
||||
| `create` | Triggered when you create a new user account.{% ifversion not ghae %}
|
||||
| `change_password` | Triggered when you change your password.
|
||||
| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %}
|
||||
| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).
|
||||
| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
|
||||
`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
|
||||
| `failed_login` | Triggered when you failed to log in successfully.
|
||||
| `remove_email` | Triggered when you remove an email address.
|
||||
| `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %}
|
||||
| `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %}
|
||||
| `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% ifversion not ghae %}
|
||||
| `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %}
|
||||
|
||||
### `user_status` category actions
|
||||
|
||||
`mandatory_message_viewed` | 必須メッセージを表示するとトリガーされます (詳細は「[ユーザーメッセージのカスタマイズ](/admin/user-management/customizing-user-messages-for-your-enterprise)」を参照してください) | |{% endif %}| | `failed_login` | 正常にログインできなかったときにトリガーされます。 | `remove_email` | メール アドレスを削除するとトリガーされます。 | `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %} | `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %} | `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% ifversion not ghae %} | `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %}
|
||||
|
||||
### `user_status` カテゴリアクション
|
||||
|
||||
| アクション | 説明 |
|
||||
| --------- | ------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `update` | 自分のプロファイルでステータスを設定または変更するときにトリガーされます。 詳細は「[ステータスを設定する](/articles/personalizing-your-profile/#setting-a-status)」を参照してください。 |
|
||||
| `destroy` | 自分のプロファイルでステータスを消去するときにトリガーされます。 |
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `update` | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)."
|
||||
| `destroy` | Triggered when you clear the status on your profile.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 2 要素認証クレデンシャルをなくした際のアカウントの回復
|
||||
intro: 2 要素認証の認証情報にアクセスできなくなった場合、リカバリコードまたはその他のリカバリ方法を使用して、アカウントへのアクセスを回復できます。
|
||||
title: Recovering your account if you lose your 2FA credentials
|
||||
intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
|
||||
redirect_from:
|
||||
- /articles/recovering-your-account-if-you-lost-your-2fa-credentials/
|
||||
- /articles/authenticating-with-an-account-recovery-token/
|
||||
@@ -15,91 +15,73 @@ topics:
|
||||
- 2FA
|
||||
shortTitle: Recover an account with 2FA
|
||||
---
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**: {% data reusables.two_fa.support-may-not-help %}
|
||||
**Warning**: {% data reusables.two_fa.support-may-not-help %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 2 要素認証リカバリコードを使用する
|
||||
## Using a two-factor authentication recovery code
|
||||
|
||||
リカバリコードのうち 1 つを使用して、アカウントへのエントリを自動で再取得します。 リカバリコード は、多くの場合、パスワードマネージャまたはご使用のコンピュータのダウンロードフォルダに保存されています。 リカバリコードのデフォルトのファイル名は `github-recovery-codes.txt` です。 リカバリコードの詳しい情報については「[2 要素認証リカバリ方法を設定する](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)」を参照してください。
|
||||
Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
|
||||
|
||||
{% data reusables.two_fa.username-password %}{% ifversion fpt or ghec %}
|
||||
2. [Having Problems?] の下で、[**Enter a two-factor recovery code**] をクリックします。 {% else %}
|
||||
2. [2FA] ページで、[Don't have your phone?] の下にある [**Enter a two-factor recovery code**] をクリックします。 {% endif %}
|
||||
3. リカバリコードを 1 つ入力して、[**Verify**] をクリックします。 ![リカバリコードを入力するフィールドおよび [Verify] ボタン](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
|
||||
2. Under "Having Problems?", click **Enter a two-factor recovery code**.
|
||||
{% else %}
|
||||
2. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
|
||||
{% endif %}
|
||||
3. Type one of your recovery codes, then click **Verify**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## フォールバック番号による認証
|
||||
## Authenticating with a fallback number
|
||||
|
||||
プライマリ TOTP アプリケーションや電話番号へのアクセスをなくした場合でも、 フォールバック番号に送信されている 2 要素認証コードを入力すれば、アカウントへのアクセスを自動で再取得できます。
|
||||
If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account.
|
||||
{% endif %}
|
||||
|
||||
## セキュリティキーによる認証
|
||||
## Authenticating with a security key
|
||||
|
||||
セキュリティキーを使用して 2 要素認証を設定した場合は、セキュリティキーをセカンダリ認証方式として使用すると、アカウントへのアクセスを自動で再取得できます。 詳しい情報については、「[2 要素認証を設定する](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)」を参照してください。
|
||||
If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 検証済みのデバイス、SSHトークン、または個人アクセストークンを使用した認証
|
||||
## Authenticating with a verified device, SSH token, or personal access token
|
||||
|
||||
If you know your {% data variables.product.product_name %} password but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注釈**: セキュリティ上の理由から、ワンタイムパスワードで認証してアカウントへのアクセスを回復するには、3〜5 営業日かかる場合があります。 この間に送信された追加のリクエストはレビューされません。
|
||||
**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take 3-5 business days. Additional requests submitted during this time will not be reviewed.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
2要素認証の認証情報または 2 要素認証のリカバリコードを使用して、3〜5 日間の待機期間中にいつでもアカウントへのアクセスを回復できます。
|
||||
You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
|
||||
|
||||
1. 認証を求めるためにユーザ名とパスワードを入力してください。 If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
|
||||
2. [Having Problems?] の下で、[**Can't access your two factor device or valid recovery codes?**] をクリックします。 
|
||||
3. [**I understand, get started**] をクリックして、認証設定のリセットをリクエストします。 
|
||||
4. [**Send one-time password**] をクリックして、アカウントに関連付けられているすべてのメールアドレスにワンタイムパスワードを送信します。 
|
||||
5. [One-time password] の下で、送信されたリカバリメール{% data variables.product.prodname_dotcom %}の一時パスワードを入力します。 
|
||||
6. [**Verify email address**] をクリックします。
|
||||
7. 別の検証要素を選択します。
|
||||
- 以前に現在のデバイスを使用してこのアカウントにログインしたことがあり、検証にそのデバイスを使用する場合は、[**Verify with this device**] をクリックします。
|
||||
- 以前にこのアカウントで SSH キーを設定しており、検証にその SSH キーを使用する場合は、[** SSH key**] をクリックします。
|
||||
- 以前に個人アクセストークンを設定しており、検証にその個人アクセストークンを使用する場合は、[**Personal access token**] をクリックします。 
|
||||
8. {% data variables.contact.github_support %}のメンバーがリクエストをレビューし、3〜5 営業日以内にメールでお知らせします。 リクエストが承認されると、アカウントリカバリプロセスを完了するためのリンクが送信されます。 リクエストが拒否された場合、追加の質問がある場合のサポートへの問い合わせ方法がメールに記載されます。
|
||||
1. Type your username and password to prompt authentication. If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
|
||||
2. Under "Having Problems?", click **Can't access your two factor device or valid recovery codes?**
|
||||
|
||||
3. Click **I understand, get started** to request a reset of your authentication settings.
|
||||
|
||||
4. Click **Send one-time password** to send a one-time password to all email addresses associated with your account.
|
||||
|
||||
5. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent.
|
||||
|
||||
6. Click **Verify email address**.
|
||||
7. Choose an alternative verification factor.
|
||||
- If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
|
||||
- If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**.
|
||||
- If you've previously set up a personal access token and would like to use the personal access token for verification, click **Personal access token**.
|
||||
|
||||
8. A member of {% data variables.contact.github_support %} will review your request and email you within 3-5 business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
|
||||
|
||||
## アカウントリカバリトークンによる認証
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Account recovery tokens are deprecated and will be disabled on **December 1st, 2021**. Please ensure you have configured other two-factor recovery methods. For more information, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
If you lose access to the two-factor authentication methods for your account on {% data variables.product.product_location %}, you can retrieve your account recovery token from a partner recovery provider and ask {% data variables.product.prodname_dotcom %} Support to review it.
|
||||
|
||||
2 要素認証方式やリカバリコードへのアクセスがない場合でも、Recovery Accounts Elsewhere を使用して Facebook にアカウントリカバリトークンを格納してあれば、トークンを使用してアカウントへのアクセスを再取得できる可能性があります。
|
||||
|
||||
アカウントへのアクセスを回復できない場合は、ワンタイムパスワードを生成してアクセスを回復します。 詳しい情報については、「[検証済みのデバイス、SSHトークン、または個人アクセストークンを使用した認証](#authenticating-with-a-verified-device-ssh-token-or-personal-access-token)」を参照してください。
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告:**
|
||||
- アカウントリカバリトークンを再取得する前に、[2 要素認証コード](/articles/accessing-github-using-two-factor-authentication)か 2 要素認証リカバリコードを使用してアカウントへのアクセスの再取得を試行してください。 詳しい情報については[2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)を参照してください。
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
1. Facebook で、[セキュリティ設定](https://www.facebook.com/settings?tab=security)に移動し、[**Recovery Accounts Elsewhere**] をクリックします。 
|
||||
2. Click the recovery token associated with your account on {% data variables.product.product_location %}. 
|
||||
3. アカウントリカバリトークンを引き換えるため、[**Recover This Account**] をクリックします。 新しいウィンドウが開き、{% data variables.product.product_name %}に戻ります。 ![リカバリトークンについての情報を表示するモーダルボックスおよび [Recover This Account] ボタン](/assets/images/help/settings/security-recover-account-facebook.png)
|
||||
4. {% data variables.contact.contact_support %} に連絡して、アカウントリカバリトークンはレビューの準備ができていることを知らせます。
|
||||
{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [2 要素認証について](/articles/about-two-factor-authentication)
|
||||
- [2 要素認証の設定](/articles/configuring-two-factor-authentication)
|
||||
- [2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods)
|
||||
- [2 要素認証を使用して {% data variables.product.prodname_dotcom %} にアクセスする](/articles/accessing-github-using-two-factor-authentication)
|
||||
- "[About two-factor authentication](/articles/about-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
|
||||
|
||||
@@ -14,15 +14,21 @@ topics:
|
||||
|
||||
{% data reusables.cli.cli-extensions %} For more information about how to use {% data variables.product.prodname_cli %} extensions, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)."
|
||||
|
||||
You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. At the root of the repository, there must be an executable file with the same name as the repository. This file will be executed when the extension is invoked.
|
||||
You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. The repository must have an executable file at its root with the same name as the repository or a set of precompiled binary executables attached to a release.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: We recommend that the executable file is a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension.
|
||||
**Note**: When relying on an executable script, we recommend using a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. If you would prefer to not rely on users having interpreters installed, consider a precompiled extension.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Creating an extension with `gh extension create`
|
||||
## Creating an interpreted extension with `gh extension create`
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Running `gh extension create` with no arguments will start an interactive wizard.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can use the `gh extension create` command to create a project for your extension, including a bash script that contains some starter code.
|
||||
|
||||
@@ -34,7 +40,35 @@ You can use the `gh extension create` command to create a project for your exten
|
||||
|
||||
1. Follow the printed instructions to finalize and optionally publish your extension.
|
||||
|
||||
## Creating an extension manually
|
||||
## Creating a precompiled extension in Go with `gh extension create`
|
||||
|
||||
You can use the `--precompiled=go` argument to create a Go-based project for your extension, including Go scaffolding, workflow scaffolding, and starter code.
|
||||
|
||||
1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=go`.
|
||||
|
||||
```shell
|
||||
gh extension create --precompiled=go <em>EXTENSION-NAME</em>
|
||||
```
|
||||
|
||||
1. Follow the printed instructions to finalize and optionally publish your extension.
|
||||
|
||||
## Creating a non-Go precompiled extension with `gh extension create`
|
||||
|
||||
You can use the `--precompiled=other` argument to create a project for your non-Go precompiled extension, including workflow scaffolding.
|
||||
|
||||
1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=other`.
|
||||
|
||||
```shell
|
||||
gh extension create --precompiled=other <em>EXTENSION-NAME</em>
|
||||
```
|
||||
|
||||
1. Add some initial code for your extension in your compiled language of choice.
|
||||
|
||||
1. Fill in `script/build.sh` with code to build your extension to ensure that your extension can be built automatically.
|
||||
|
||||
1. Follow the printed instructions to finalize and optionally publish your extension.
|
||||
|
||||
## Creating an interpreted extension manually
|
||||
|
||||
1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
|
||||
|
||||
@@ -56,7 +90,7 @@ You can use the `gh extension create` command to create a project for your exten
|
||||
|
||||
1. From your directory, install the extension as a local extension.
|
||||
|
||||
```bash
|
||||
```shell
|
||||
gh extension install .
|
||||
```
|
||||
|
||||
@@ -70,13 +104,13 @@ You can use the `gh extension create` command to create a project for your exten
|
||||
|
||||
```shell
|
||||
git init -b main
|
||||
git add . && git commit -m "initial commit"
|
||||
gh repo create gh-<em>EXTENSION-NAME</em> --source=. --public --push
|
||||
git add . && git commit -m "initial commit"
|
||||
gh repo create gh-<em>EXTENSION-NAME</em> --source=. --public --push
|
||||
```
|
||||
|
||||
1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
|
||||
|
||||
## Tips for writing {% data variables.product.prodname_cli %} extensions
|
||||
## Tips for writing interpreted {% data variables.product.prodname_cli %} extensions
|
||||
|
||||
### Handling arguments and flags
|
||||
|
||||
@@ -120,34 +154,128 @@ fi
|
||||
|
||||
### Calling core commands in non-interactive mode
|
||||
|
||||
Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments.
|
||||
Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments.
|
||||
|
||||
For example, to create an issue programmatically, specify the title and body:
|
||||
|
||||
```bash
|
||||
```shell
|
||||
gh issue create --title "My Title" --body "Issue description"
|
||||
```
|
||||
|
||||
### Fetching data programatically
|
||||
|
||||
Many core commands support the `--json` flag for fetching data programatically. For example, to return a JSON object listing the number, title, and mergeability status of pull requests:
|
||||
```bash
|
||||
|
||||
```shell
|
||||
gh pr list --json number,title,mergeStateStatus
|
||||
```
|
||||
|
||||
If there is not a core command to fetch specific data from GitHub, you can use the [`gh api`](https://cli.github.com/manual/gh_api) command to access the GitHub API. For example, to fetch information about the current user:
|
||||
```bash
|
||||
|
||||
```shell
|
||||
gh api user
|
||||
```
|
||||
|
||||
All commands that output JSON data also have options to filter that data into something more immediately usable by scripts. For example, to get the current user's name:
|
||||
|
||||
```bash
|
||||
```shell
|
||||
gh api user --jq '.name'
|
||||
```
|
||||
|
||||
For more information, see [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting).
|
||||
|
||||
## Creating a precompiled extension manually
|
||||
|
||||
1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
|
||||
|
||||
1. In the directory you created, add some source code. For example:
|
||||
|
||||
```go
|
||||
package main
|
||||
import (
|
||||
"github.com/cli/go-gh"
|
||||
"fmt"
|
||||
)
|
||||
|
||||
func main() {
|
||||
args := []string{"api", "user", "--jq", `"You are @\(.login) (\(.name))"` }
|
||||
stdOut, _, err := gh.Exec(args...)
|
||||
if err != nil {
|
||||
fmt.Println(err)
|
||||
return
|
||||
}
|
||||
fmt.Println(stdOut.String())
|
||||
}
|
||||
```
|
||||
|
||||
1. From your directory, install the extension as a local extension.
|
||||
|
||||
```shell
|
||||
gh extension install .
|
||||
```
|
||||
|
||||
1. Build your code. For example, with Go, replacing `YOUR-USERNAME` with your GitHub username:
|
||||
|
||||
```shell
|
||||
go mod init github.com/<em>YOUR-USERNAME</em>/gh-whoami
|
||||
go mod tidy
|
||||
go build
|
||||
```
|
||||
|
||||
1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`.
|
||||
|
||||
```shell
|
||||
gh <em>EXTENSION-NAME</em>
|
||||
```
|
||||
|
||||
1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Be careful not to commit the binary produced by your compilation step to version control.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
```shell
|
||||
git init -b main
|
||||
echo "gh-<em>EXTENSION-NAME</em>" >> .gitignore
|
||||
git add main.go go.* .gitignore && git commit -m'Initial commit'
|
||||
gh repo create "gh-<em>EXTENSION-NAME</em>"
|
||||
```
|
||||
|
||||
1. Create a release to share your precompiled extension with others. Compile for each platform you want to support, attaching each binary to a release as an asset. Binary executables attached to releases must follow a naming convention and have a suffix of <em>OS-ARCHITECTURE\[EXTENSION\]</em>.
|
||||
|
||||
For example, an extension named `whoami` compiled for Windows 64bit would have the name `gh-whoami-windows-amd64.exe` while the same extension compiled for Linux 32bit would have the name `gh-whoami-linux-386`. To see an exhaustive list of OS and architecture combinations recognized by `gh`, see [this source code](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** For your extension to run properly on Windows, its asset file must have a `.exe` extension. No extension is needed for other operating systems.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Releases can be created from the command line. For example:
|
||||
|
||||
```shell
|
||||
git tag v1.0.0
|
||||
git push origin v1.0.0
|
||||
GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe
|
||||
GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64
|
||||
GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64
|
||||
gh release create v1.0.0 ./*amd64*
|
||||
|
||||
1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
|
||||
|
||||
|
||||
## Tips for writing precompiled {% data variables.product.prodname_cli %} extensions
|
||||
|
||||
### Automating releases
|
||||
|
||||
Consider adding the [gh-extension-precompile](https://github.com/cli/gh-extension-precompile) action to a workflow in your project. This action will automatically produce cross-compiled Go binaries for your extension and supplies build scaffolding for non-Go precompiled extensions.
|
||||
|
||||
### Using {% data variables.product.prodname_cli %} features from Go-based extensions
|
||||
|
||||
Consider using [go-gh](https://github.com/cli/go-gh), a Go library that exposes pieces of `gh` functionality for use in extensions.
|
||||
|
||||
## Next steps
|
||||
|
||||
To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension).
|
||||
|
||||
@@ -6,10 +6,6 @@
|
||||
term: アクセストークン
|
||||
description: >-
|
||||
Git 操作を HTTPS 経由で実行する際、Git がコマンドラインと API のいずれでも、パスワードの代わりに使用されるトークン。個人アクセストークンともいいます。
|
||||
-
|
||||
term: アカウントリカバリトークン
|
||||
description: >-
|
||||
**Deprecated and will be disabled December 1st, 2021.** The authentication credential stored as part of an account recovery setup called Recover Accounts Elsewhere that allows you to store this backup credential.
|
||||
-
|
||||
term: APIプレビュー
|
||||
description: >-
|
||||
@@ -177,17 +173,17 @@
|
||||
-
|
||||
term: ダッシュボード
|
||||
description: >-
|
||||
パーソナルダッシュボードは、GitHub上のアクティビティのメインハブです。パーソナルダッシュボードから、フォローまたは作業をしているIssueやプルリクエストを追跡したり、トップリポジトリやTeamページにアクセスしたり、Watchまたは参加しているリポジトリ内の最近のアクティビティについて学ぶことができます。また、フォローしているユーザーやStarしたリポジトリに基づいて推薦された、新しいリポジトリを発見することもできます。特定のOrganizationのアクティビティだけを見るには、Organizationのダッシュボードにアクセスしてください。詳しい情報については「[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)」もしくは「[Organizationダッシュボードについて](/articles/about-your-organization-dashboard)」を参照してください。
|
||||
パーソナルダッシュボードは、GitHub上のアクティビティのメインハブです。パーソナルダッシュボードから、フォローまたは作業をしているIssueやプルリクエストを追跡したり、トップリポジトリやTeamページにアクセスしたり、Watchまたは参加しているリポジトリ内の最近のアクティビティについて学ぶことができます。また、フォローしているユーザーやStarしたリポジトリに基づいて推薦された、新しいリポジトリを発見することもできます。特定のOrganizationのアクティビティだけを見るには、Organizationのダッシュボードにアクセスしてください。詳しい情報については「[パーソナルダッシュボードについて(/articles/about-your-personal-dashboard)」もしくは「Organizationダッシュボードについて(/articles/about-your-organization-dashboard)」を参照してください。
|
||||
-
|
||||
term: デフォルトブランチ
|
||||
description: >-
|
||||
リポジトリ内の新しいPull Requestやコードのコミットのためのベースブランチ。それぞれのリポジトリは少なくとも1つのブランチを持ち、これはリポジトリを初期化したときにGitが作成します。最初のブランチは通常{% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}と呼ばれ、多くの場合デフォルトブランチです。
|
||||
The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch.
|
||||
-
|
||||
term: 依存グラフ
|
||||
term: dependents graph
|
||||
description: >-
|
||||
パブリックリポジトリに依存するパッケージ、プロジェクト、リポジトリを表示するリポジトリグラフ。
|
||||
-
|
||||
term: 依存関係グラフ
|
||||
term: dependency graph
|
||||
description: >-
|
||||
リポジトリが依存するパッケージおよびプロジェクトを表示するリポジトリグラフ。
|
||||
-
|
||||
@@ -252,7 +248,7 @@
|
||||
-
|
||||
term: gist
|
||||
description: >-
|
||||
Gistは、GitHub上で編集、クローン、フォークできる共有可能なファイルです。Gistは{% ifversion ghae %}インターナル{% else %}パブリック{% endif %}もしくはシークレットにすることができますが、シークレットのGistはURLから{% ifversion ghae %}Enterpriseのメンバーなら誰でも{% else %}誰でも{% endif %}アクセスできます。
|
||||
A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
|
||||
-
|
||||
term: Git
|
||||
description: >-
|
||||
@@ -263,7 +259,7 @@
|
||||
GitHub App は、Organization 全体に対してサービスを提供し、その機能を実行する際は独自の ID を使用します。Organization や ユーザアカウントに直接インストールでき、特定のリポジトリへのアクセス権を付与できます。精細なアクセス権限が付いており、webhook が組み込まれています。
|
||||
-
|
||||
term: GitHub Flavored Markdown
|
||||
description: GitHub 特有の Markdown であり、GitHub 全体で文章やコードをフォーマットするのに使用されます。[GitHub Flavored Markdown の仕様](https://github.github.com/gfm/)または [GitHub で書き、フォーマットしてみる](/articles/getting-started-with-writing-and-formatting-on-github)を参照。
|
||||
description: GitHub 特有の Markdown であり、GitHub 全体で文章やコードをフォーマットするのに使用されます。[GitHub Flavored Markdown の仕様]（https://github.github.com/gfm/）または [GitHub で書き、フォーマットしてみる]（/articles/getting-started-with-writing-and-formatting-on-github）を参照。
|
||||
-
|
||||
term: GitHub Importer
|
||||
description: >-
|
||||
@@ -377,7 +373,7 @@
|
||||
description: >-
|
||||
ユーザがアクセスできない個人アカウント。ユーザが有料アカウントを無料のものにダウングレードした場合、または有料プランの支払いが期限を過ぎた場合、アカウントはロックされます。
|
||||
-
|
||||
term: management Console
|
||||
term: management console
|
||||
description: >-
|
||||
GitHub Enterprise インターフェース内で、管理機能を含むセクション。
|
||||
-
|
||||
@@ -385,7 +381,7 @@
|
||||
description: >-
|
||||
Markdown は非常にシンプルでセマンティックファイル形式であり、.doc、.rtf 、.txtと大差ありません。Markdown はウェブパブリッシングの素養がない人でも簡単に文章（リンク、リスト、箇条書きなど）を書いたりウェブサイトのように表示したりできます。GitHub では Markdown をサポートしており、GitHub Flavored Markdown という特定の形式の Markdown を使用します。[GitHub Flavored Markdown の仕様](https://github.github.com/gfm/)または [GitHub で書き、フォーマットしてみる](/articles/getting-started-with-writing-and-formatting-on-github)を参照。
|
||||
-
|
||||
term: マークアップ
|
||||
term: markup
|
||||
description: ドキュメントのアノテーションおよびフォーマットのためのシステム。
|
||||
-
|
||||
term: main
|
||||
@@ -396,7 +392,7 @@
|
||||
description: >-
|
||||
多くのGitリポジトリのデフォルトブランチ。デフォルトでは、新しいGitリポジトリをコマンドライン上で作成すると、`master`というブランチが作成されます。現在では、多くのツールがデフォルトブランチに代わりの名前を使うようになりました。{% ifversion fpt or ghes > 3.1 or ghae %}たとえばGitHub上で新しいリポジトリを作成すると、デフォルトブランチは`main`になります。{% endif %}
|
||||
-
|
||||
term: メンバーグラフ
|
||||
term: members graph
|
||||
description: リポジトリのすべてのフォークを表示するリポジトリグラフ。
|
||||
-
|
||||
term: メンション
|
||||
@@ -422,7 +418,7 @@
|
||||
description: >-
|
||||
親チームの子チーム。子（または入れ子）チームは複数持つことができます。
|
||||
-
|
||||
term: ネットワークグラフ
|
||||
term: network graph
|
||||
description: >-
|
||||
リポジトリネットワーク全体のブランチ履歴を表示するリポジトリグラフ。ルートリポジトリのブランチと、ネットワークに固有のコミットを含むフォークのブランチが含まれます。
|
||||
-
|
||||
@@ -543,10 +539,10 @@
|
||||
description: >-
|
||||
プルリクエストについてのコラボレータからのコメントで、変更を受け入れたり、プルリクエストがマージされる前にさらなる変更をリクエストしたりするもの。
|
||||
-
|
||||
term: パルスグラフ
|
||||
term: pulse graph
|
||||
description: リポジトリのアクティビティの概要を示すリポジトリグラフ。
|
||||
-
|
||||
term: パンチグラフ
|
||||
term: punch graph
|
||||
description: >-
|
||||
リポジトリへのアップデートの頻度を曜日または 1 日内の時間に基づいて表示するリポジトリグラフ。
|
||||
-
|
||||
@@ -571,10 +567,6 @@
|
||||
term: リベース
|
||||
description: >-
|
||||
ブランチからの一連の変更を異なるベースに再適用し、そのブランチのHEADをその結果にリセットすること。
|
||||
-
|
||||
term: Recovery Accounts Elsewhere
|
||||
description: >-
|
||||
**Deprecated and will be disabled December 1st, 2021.** Allows users to add an extra security factor to their GitHub account in case they lose access to their two-factor authentication method or recovery codes. Users can associate their GitHub account with their Facebook account by storing an authentication credential in the form of an account recovery token for their GitHub account with Facebook.
|
||||
-
|
||||
term: リカバリコード
|
||||
description: GitHub アカウントへのアクセスを再取得できるようにするコード。
|
||||
|
||||
@@ -76,16 +76,6 @@
|
||||
- RemovedFromProjectEvent.projectColumnName
|
||||
owning_teams:
|
||||
- '@github/github-projects'
|
||||
-
|
||||
title: コンテンツ添付ファイルの作成
|
||||
description: このプレビューは、コンテンツ添付ファイルの作成のサポートを追加します。
|
||||
toggled_by: ':corsair-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.createContentAttachment
|
||||
owning_teams:
|
||||
- '@github/feature-lifecycle'
|
||||
-
|
||||
title: ラベルのプレビュー
|
||||
description: >-
|
||||
|
||||
@@ -93,16 +93,6 @@
|
||||
- RemovedFromProjectEvent.projectColumnName
|
||||
owning_teams:
|
||||
- '@github/github-projects'
|
||||
-
|
||||
title: コンテンツ添付ファイルの作成
|
||||
description: このプレビューは、コンテンツ添付ファイルの作成のサポートを追加します。
|
||||
toggled_by: ':corsair-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.createContentAttachment
|
||||
owning_teams:
|
||||
- '@github/feature-lifecycle'
|
||||
-
|
||||
title: ラベルのプレビュー
|
||||
description: >-
|
||||
|
||||
@@ -93,16 +93,6 @@
|
||||
- RemovedFromProjectEvent.projectColumnName
|
||||
owning_teams:
|
||||
- '@github/github-projects'
|
||||
-
|
||||
title: コンテンツ添付ファイルの作成
|
||||
description: このプレビューは、コンテンツ添付ファイルの作成のサポートを追加します。
|
||||
toggled_by: ':corsair-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.createContentAttachment
|
||||
owning_teams:
|
||||
- '@github/feature-lifecycle'
|
||||
-
|
||||
title: ラベルのプレビュー
|
||||
description: >-
|
||||
|
||||
@@ -36,6 +36,7 @@ translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troub
|
||||
translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error
|
||||
translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md,rendering error
|
||||
translations/zh-CN/content/actions/learn-github-actions/contexts.md,rendering error
|
||||
translations/zh-CN/content/actions/learn-github-actions/creating-workflow-templates.md,rendering error
|
||||
translations/zh-CN/content/actions/learn-github-actions/environment-variables.md,rendering error
|
||||
translations/zh-CN/content/actions/learn-github-actions/expressions.md,rendering error
|
||||
translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md,rendering error
|
||||
@@ -46,6 +47,7 @@ translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-gith
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,rendering error
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md,rendering error
|
||||
translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md,rendering error
|
||||
translations/zh-CN/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md,rendering error
|
||||
translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error
|
||||
translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,rendering error
|
||||
@@ -132,9 +134,11 @@ translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/a
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
|
||||
translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
|
||||
translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
|
||||
translations/zh-CN/content/billing/index.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,rendering error
|
||||
|
||||
|
@@ -37,6 +37,7 @@ translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server
|
||||
translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,Listed in localization-support#489
|
||||
translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md,rendering error
|
||||
translations/ja-JP/content/actions/learn-github-actions/contexts.md,rendering error
|
||||
translations/ja-JP/content/actions/learn-github-actions/creating-workflow-templates.md,rendering error
|
||||
translations/ja-JP/content/actions/learn-github-actions/environment-variables.md,rendering error
|
||||
translations/ja-JP/content/actions/learn-github-actions/expressions.md,rendering error
|
||||
translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md,rendering error
|
||||
@@ -48,6 +49,7 @@ translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-gi
|
||||
translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md,rendering error
|
||||
translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,rendering error
|
||||
translations/ja-JP/content/actions/publishing-packages/about-packaging-with-github-actions.md,rendering error
|
||||
translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md,rendering error
|
||||
translations/ja-JP/content/actions/quickstart.md,rendering error
|
||||
translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error
|
||||
translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md,rendering error
|
||||
@@ -138,10 +140,12 @@ translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/a
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
|
||||
translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
|
||||
translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
|
||||
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
|
||||
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
|
||||
translations/ja-JP/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,Listed in localization-support#489
|
||||
translations/ja-JP/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error
|
||||
translations/ja-JP/content/billing/index.md,rendering error
|
||||
|
||||
|
@@ -19,13 +19,13 @@ topics:
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
{% data reusables.actions.ae-beta %}
|
||||
|
||||
## 概览
|
||||
## Overview
|
||||
|
||||
{% data reusables.actions.workflow-organization-templates %}
|
||||
|
||||
## 创建工作流程模板
|
||||
## Creating a workflow template
|
||||
|
||||
对组织的 `.github` 仓库具有写入权限的用户可以创建工作流程模板。 然后，有权限创建工作流程的组织成员便可使用这些模板。
|
||||
Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows.
|
||||
|
||||
{% ifversion fpt %}
|
||||
Your workflow templates can be used to create workflows in public repositories only. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use workflow templates to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/learn-github-actions/creating-workflow-templates).
|
||||
@@ -39,15 +39,15 @@ Your workflow templates can be used to create workflows in public repositories o
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
此过程展示如何创建工作流程模板和元数据文件。 元数据文件描述在用户新建工作流程时如何向其显示模板。
|
||||
This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the template is presented to users when they are creating a new workflow.
|
||||
|
||||
1. 如果组织中没有名为 `.github` 的公共仓库，请新建一个。
|
||||
2. 创建一个名为 `workflow-templates` 的目录。
|
||||
3. 在 `workflow-templates` 目录中创建新的工作流程文件。
|
||||
1. If it doesn't already exist, create a new public repository named `.github` in your organization.
|
||||
2. Create a directory named `workflow-templates`.
|
||||
3. Create your new workflow file inside the `workflow-templates` directory.
|
||||
|
||||
如果需要引用仓库的默认分支，可以使用 `$default-branch` 占位符。 使用模板创建工作流程时，占位符将自动替换为仓库默认分支的名称。
|
||||
If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created using your template, the placeholder will be automatically replaced with the name of the repository's default branch.
|
||||
|
||||
例如，下面这个名为 `octo-organization-ci.yml` 的文件展示了一个基本的工作流程。
|
||||
For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow.
|
||||
|
||||
```yaml
|
||||
name: Octo Organization CI
|
||||
@@ -68,7 +68,7 @@ Your workflow templates can be used to create workflows in public repositories o
|
||||
- name: Run a one-line script
|
||||
run: echo Hello from Octo Organization
|
||||
```
|
||||
4. 在 `workflow-templates` 目录中创建元数据文件。 元数据文件必须与工作流程文件同名，但扩展名不是 `.yml`，而必须附加 `.properties.json`。 例如，下面这个名为 `octo-organization-ci.properties.json` 的文件包含名为 `octo-organization-ci.yml` 的工作流程文件的元数据：
|
||||
4. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
|
||||
```yaml
|
||||
{
|
||||
"name": "Octo Organization Workflow",
|
||||
@@ -84,16 +84,16 @@ Your workflow templates can be used to create workflows in public repositories o
|
||||
]
|
||||
}
|
||||
```
|
||||
* `name` - **必要。**工作流程模板的名称。 这会显示在可用模板列表中。
|
||||
* `description` - **必要。**工作流程模板的描述。 这会显示在可用模板列表中。
|
||||
* `iconName` - **必要。**定义模板列表中工作流程项目的图标。 `iconName` 必须是同名的 SVG 图标，且必须存储在 `workflow-templates` 目录中。 例如，名为 `example-icon.svg` 的 SVG 文件被引用为 `example-icon`。
|
||||
* `categories` - **可选。**定义工作流程的语言类别。 当用户查看可用模板时，匹配相同语言的模板将更加突出。 有关可用语言类别的信息，请参阅https://github.com/github/linguist/blob/master/lib/linguist/languages.yml。
|
||||
* `filePatterns` - **可选。**如果用户仓库在其根目录中有符合定义的正则表达式的文件，则允许使用模板。
|
||||
* `name` - **Required.** The name of the workflow template. This is displayed in the list of available templates.
|
||||
* `description` - **Required.** The description of the workflow template. This is displayed in the list of available templates.
|
||||
* `iconName` - **Optional.** Defines an icon for the workflow's entry in the template list. The `iconName` must be an SVG icon of the same name, and must be stored in the `workflow-templates` directory. For example, a SVG file named `example-icon.svg` is referenced as `example-icon`.
|
||||
* `categories` - **Optional.** Defines the language category of the workflow. When a user views the available templates, those templates that match the same language will feature more prominently. For information on the available language categories, see https://github.com/github/linguist/blob/master/lib/linguist/languages.yml.
|
||||
* `filePatterns` - **Optional.** Allows the template to be used if the user's repository has a file in its root directory that matches a defined regular expression.
|
||||
|
||||
要添加另一个工作流模板，请将您的文件添加到同一 `workflow-templates` 目录中。 例如：
|
||||
To add another workflow template, add your files to the same `workflow-templates` directory. For example:
|
||||
|
||||
|
||||
|
||||
|
||||
## 后续步骤
|
||||
## Next steps
|
||||
|
||||
To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 发布 Node.js 包
|
||||
intro: 您可以将 Node.js 包发布到注册表，作为持续集成 (CI) 工作流程的一部分。
|
||||
title: Publishing Node.js packages
|
||||
intro: You can publish Node.js packages to a registry as part of your continuous integration (CI) workflow.
|
||||
redirect_from:
|
||||
- /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
|
||||
- /actions/language-and-framework-guides/publishing-nodejs-packages
|
||||
@@ -16,51 +16,51 @@ topics:
|
||||
- Publishing
|
||||
- Node
|
||||
- JavaScript
|
||||
shortTitle: Node.js 包
|
||||
shortTitle: Node.js packages
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
{% data reusables.actions.ae-beta %}
|
||||
|
||||
## 简介
|
||||
## Introduction
|
||||
|
||||
本指南介绍如何创建一个工作流程，以在持续集成 (CI) 测试通过后将 Node.js 包发布到 {% data variables.product.prodname_registry %} 和 npm 注册表。 通过单个工作流程，您可以将包发布到单个注册表或多个注册表。
|
||||
This guide shows you how to create a workflow that publishes Node.js packages to the {% data variables.product.prodname_registry %} and npm registries after continuous integration (CI) tests pass. With a single workflow, you can publish packages to a single registry or multiple registries.
|
||||
|
||||
## 基本要求
|
||||
## Prerequisites
|
||||
|
||||
建议基本了解工作流程配置选项和如何创建工作流程文件。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
|
||||
We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
|
||||
|
||||
有关为 Node.js 项目创建 CI 工作流程的更多信息，请参阅“[将 Node.js 与 {% data variables.product.prodname_actions %} 一起使用](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)。”
|
||||
For more information about creating a CI workflow for your Node.js project, see "[Using Node.js with {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)."
|
||||
|
||||
您可能还发现基本了解以下内容是有帮助的：
|
||||
You may also find it helpful to have a basic understanding of the following:
|
||||
|
||||
- “[使用 npm 注册表](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)”
|
||||
- "[环境变量](/actions/reference/environment-variables)"
|
||||
- [加密的密码](/actions/reference/encrypted-secrets)"
|
||||
- "[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow)"
|
||||
- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
|
||||
- "[Environment variables](/actions/reference/environment-variables)"
|
||||
- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
|
||||
- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
|
||||
|
||||
## 关于包配置
|
||||
## About package configuration
|
||||
|
||||
*package.json* 文件中的 `name` 和 `version` 字段创建唯一标识符，供注册表用来将包链接到注册表。 您可以在 *package.json* 文件中添加 `description` 字段，从而为包列表页面添加一个摘要。 更多信息请参阅 npm 文档中的“[创建 package.json 文件](https://docs.npmjs.com/creating-a-package-json-file)”和“[创建 Node.js 模块](https://docs.npmjs.com/creating-node-js-modules)”。
|
||||
The `name` and `version` fields in the *package.json* file create a unique identifier that registries use to link your package to a registry. You can add a summary for the package listing page by including a `description` field in the *package.json* file. For more information, see "[Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file)" and "[Creating Node.js modules](https://docs.npmjs.com/creating-node-js-modules)" in the npm documentation.
|
||||
|
||||
当本地 *.npmrc* 文件存在且指定了 `registry` 值时，`npm publish` 命令将使用 *.npmrc* 文件中配置的注册表。 {% data reusables.github-actions.setup-node-intro %}
|
||||
When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.github-actions.setup-node-intro %}
|
||||
|
||||
您可以使用 `setup-node` 操作指定运行器上安装的 Node.js 版本。
|
||||
You can specify the Node.js version installed on the runner using the `setup-node` action.
|
||||
|
||||
如果在工作流程中添加步骤来配置 *package.json* 文件中的 `publishConfig` 字段，则无需使用 `setup-node` 操作指定注册表 url，但软件包仅限于发布到一个注册表。 更多信息请参阅 npm 文档中的“[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)”。
|
||||
If you add steps in your workflow to configure the `publishConfig` fields in your *package.json* file, you don't need to specify the registry-url using the `setup-node` action, but you will be limited to publishing the package to one registry. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
|
||||
|
||||
## 发布包到 npm 注册表
|
||||
## Publishing packages to the npm registry
|
||||
|
||||
每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件触发时运行。 如果 CI 测试通过，工作流程将包发布到 npm 注册表。
|
||||
Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs when the `release` event triggers with type `created`. The workflow publishes the package to the npm registry if CI tests pass.
|
||||
|
||||
要根据工作流程中的 npm 注册表执行经过身份验证的操作，您需要将 npm 身份验证令牌作存储为密码。 例如，创建名为 `NPM_TOKEN` 的仓库密码。 更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
|
||||
To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
|
||||
|
||||
默认情况下，npm 使用 *package.json* 文件的 `name` 字段来确定 npm 注册表。 当发布到全局命名空间时，您只需要包含包名称。 例如，您要发布一个名为 `npm-hello-world-test` 的包到 `https://www.npmjs.com/package/npm-hello-world-test`。
|
||||
By default, npm uses the `name` field of the *package.json* file to determine the npm registry. When publishing to a global namespace, you only need to include the package name. For example, you would publish a package named `npm-hello-world-test` to the `https://www.npmjs.com/package/npm-hello-world-test`.
|
||||
|
||||
如果发布一个包含范围前缀的包，请将范围包含在 *package.json* 文件的名称中。 例如，如果 npm 范围前缀是 octocat 并且包名是 hello-world，则 *package.json* 文件中的 `name` 应为 `@octocat/hello-world`。 如果 npm 包使用范围前缀且包是公开的，则需使用选项 `npm publish --access public`。 这是 npm 需要用来防止有人无意中发布私有包的选项。
|
||||
If you're publishing a package that includes a scope prefix, include the scope in the name of your *package.json* file. For example, if your npm scope prefix is octocat and the package name is hello-world, the `name` in your *package.json* file should be `@octocat/hello-world`. If your npm package uses a scope prefix and the package is public, you need to use the option `npm publish --access public`. This is an option that npm requires to prevent someone from publishing a private package unintentionally.
|
||||
|
||||
此示例将 `NPM_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时，会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
|
||||
This example stores the `NPM_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable.
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -78,14 +78,14 @@ jobs:
|
||||
with:
|
||||
node-version: '12.x'
|
||||
registry-url: 'https://registry.npmjs.org'
|
||||
- run: npm install
|
||||
- run: npm ci
|
||||
- run: npm publish
|
||||
env:
|
||||
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
在上面的示例中，`setup-node` 操作在运行器上创建一个包含以下内容的 *.npmrc* 文件：
|
||||
In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents:
|
||||
|
||||
```ini
|
||||
//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
|
||||
@@ -93,15 +93,15 @@ registry=https://registry.npmjs.org/
|
||||
always-auth=true
|
||||
```
|
||||
|
||||
## 发布包到 {% data variables.product.prodname_registry %}
|
||||
## Publishing packages to {% data variables.product.prodname_registry %}
|
||||
|
||||
每次创建新版本时，都可以触发工作流程来发布包。 以下示例中的工作流程在类型为 `created` 的 `release` 事件发生时运行。 如果 CI 测试通过，工作流程会将包发布到 {% data variables.product.prodname_registry %}。
|
||||
Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass.
|
||||
|
||||
### 配置目标仓库
|
||||
### Configuring the destination repository
|
||||
|
||||
如果您没有在 *package.json* 文件中提供 `repository` 键，则 {% data variables.product.prodname_registry %} 将包发布到您在 *package.json* 文件的 `name` 字段中指定的 {% data variables.product.prodname_dotcom %} 仓库。 例如，名为 `@my-org/test` 的包将被发布到 `my-org/test` {% data variables.product.prodname_dotcom %} 仓库。
|
||||
If you don't provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository.
|
||||
|
||||
但是，如果您提供了 `repository` 键，则该键中的仓库将被用作 {% data variables.product.prodname_registry %} 的目标 npm 注册表。 例如，发布以下 *package.json* 将导致名为 `my-amazing-package` 的包被发布到 `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} 仓库。
|
||||
However, if you do provide the `repository` key, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository.
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -112,15 +112,15 @@ always-auth=true
|
||||
},
|
||||
```
|
||||
|
||||
### 向目标仓库验证
|
||||
### Authenticating to the destination repository
|
||||
|
||||
要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `GITHUB_TOKEN`。 {% data reusables.github-actions.github-token-permissions %}
|
||||
To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
|
||||
|
||||
如果要将包发布到其他仓库，您必须使用对目标仓库中的包具有写入权限的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”和“[加密密码](/actions/reference/encrypted-secrets)”。
|
||||
If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
|
||||
|
||||
### 示例工作流程
|
||||
### Example workflow
|
||||
|
||||
此示例将 `GITHUB_TOKEN` 密码存储在 `NODE_AUTH_TOKEN` 环境变量中。 当 `setup-node` 操作创建 *.npmrc* 文件时，会引用 `NODE_AUTH_TOKEN` 环境变量中的令牌。
|
||||
This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Node.js Package
|
||||
@@ -142,13 +142,13 @@ jobs:
|
||||
registry-url: 'https://npm.pkg.github.com'
|
||||
# Defaults to the user or organization that owns the workflow file
|
||||
scope: '@octocat'
|
||||
- run: npm install
|
||||
- run: npm ci
|
||||
- run: npm publish
|
||||
env:
|
||||
NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
|
||||
```
|
||||
|
||||
`setup-node` 操作在运行器上创建 *.npmrc* 文件。 使用 `scope` 输入到 `setup-node` 操作时，*.npmrc* 文件包含作用域前缀。 默认情况下，`setup-node` 操作在 *.npmrc* 文件中将作用域设置为包含该工作流程文件的帐户。
|
||||
The `setup-node` action creates an *.npmrc* file on the runner. When you use the `scope` input to the `setup-node` action, the *.npmrc* file includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the account that contains that workflow file.
|
||||
|
||||
```ini
|
||||
//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
|
||||
@@ -156,9 +156,9 @@ jobs:
|
||||
always-auth=true
|
||||
```
|
||||
|
||||
## 使用 yarn 发布包
|
||||
## Publishing packages using yarn
|
||||
|
||||
如果您使用 Yarn 包管理器，可以使用 Yarn 安装和发布包。
|
||||
If you use the Yarn package manager, you can install and publish packages using Yarn.
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -185,25 +185,25 @@ jobs:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
## 发布包到 npm 和 {% data variables.product.prodname_registry %}
|
||||
## Publishing packages to npm and {% data variables.product.prodname_registry %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注意：**如果需要发布到具有不同作用域前缀的注册表，则需修改运行器上的 *package.json* 文件以更改作用域前缀。 例如，如果将包发布到 npm 的 `@mona` 作用域和 {% data variables.product.prodname_registry %} 的 `@octocat` 作用域，则可在发布到 npm 之后和发布到 {% data variables.product.prodname_registry %} 之前，在运行器的 *package.json* 文件中将 `@mona` 作用域替换成 `@octocat`。
|
||||
**Note:** If you need to publish to registries that have different scope prefixes, you'll need to modify the *package.json* file on the runner to change the scope prefix. For example, if you publish a package to the `@mona` scope for npm and `@octocat` scope for {% data variables.product.prodname_registry %}, you can replace the `@mona` scope with `@octocat` in the *package.json* file on the runner after publishing to npm and before publishing to {% data variables.product.prodname_registry %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
您可以使用每个注册表的 `setup-node` 操作将包发布到 npm 注册表和 {% data variables.product.prodname_registry %}。
|
||||
You can publish your packages to both the npm registry and {% data variables.product.prodname_registry %} by using the `setup-node` action for each registry.
|
||||
|
||||
如果将包发布到两个注册表，则需要确保 npm 上的作用域前缀与 {% data variables.product.prodname_dotcom %} 用户或组织名称匹配。 要将包发布到具有作用域前缀的公共注册表，可以使用 `npm publish --access public`。 更多信息请参阅 [`npm-scope`](https://docs.npmjs.com/misc/scope) 和 npm 文档中的“[创建和发布作用域的公共包](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)”。
|
||||
If you publish a package to both registries, you'll need to ensure that your scope prefix on npm matches your {% data variables.product.prodname_dotcom %} user or organization name. To publish packages to a public registry with a scope prefix, you can use the command `npm publish --access public`. For more information, see [`npm-scope`](https://docs.npmjs.com/misc/scope) and "[Creating and publishing scoped public packages](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages)" in the npm documentation.
|
||||
|
||||
确认 *package.json* 文件包含 {% data variables.product.prodname_dotcom %} 仓库和 npm 注册表的作用域。 例如，如果您计划将 `octocat/npm-hello-world-test` 仓库中的包发布到 {% data variables.product.prodname_dotcom %} 和 https://www.npmjs.com/package/@octocat/npm-hello-world-test，则 *package.json* 文件中的名称将是 `"name": "@octocat/npm-hello-world-test"`。
|
||||
Ensure your *package.json* file includes the scope of your {% data variables.product.prodname_dotcom %} repository and npm registry. For example, if you plan to publish a package in the `octocat/npm-hello-world-test` repository to {% data variables.product.prodname_dotcom %} and https://www.npmjs.com/package/@octocat/npm-hello-world-test, the name in your *package.json* file would be `"name": "@octocat/npm-hello-world-test"`.
|
||||
|
||||
要根据 {% data variables.product.prodname_registry %} 注册表在工作流程中执行经验证的操作，可以使用 `GITHUB_TOKEN`。 {% data reusables.github-actions.github-token-permissions %}
|
||||
To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
|
||||
|
||||
使用 `scope` 输入到 `setup-node` 操作时，操作将创建包含作用域前缀的 *.npmrc* 文件。 默认情况下，`setup-node` 操作在 *.npmrc* 文件中将作用域设置为拥有该工作流程文件的用户或组织。
|
||||
When you use the `scope` input to the `setup-node` action, the action creates an *.npmrc* file that includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the user or organization that owns the workflow file.
|
||||
|
||||
此工作流程将调用 `setup-node` 操作两次。 每当 `setup-node` 操作运行时，都会覆盖 *.npmrc* 文件。 *.npmrc* 文件引用的令牌允许您对 `NODE_AUTH_TOKEN` 环境变量中的包注册表执行验证的操作。 工作流程在 `npm publish` 命令每次运行时设置 `NODE_AUTH_TOKEN` 环境变量，先通过令牌发布到 npm (`NPM_TOKEN`)，然后通过令牌发布到 {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`)。
|
||||
This workflow calls the `setup-node` action two times. Each time the `setup-node` action runs, it overwrites the *.npmrc* file. The *.npmrc* file references the token that allows you to perform authenticated operations against the package registry from the `NODE_AUTH_TOKEN` environment variable. The workflow sets the `NODE_AUTH_TOKEN` environment variable each time the `npm publish` command is run, first with a token to publish to npm (`NPM_TOKEN`) and then with a token to publish to {% data variables.product.prodname_registry %} (`GITHUB_TOKEN`).
|
||||
|
||||
|
||||
```yaml{:copy}
|
||||
@@ -224,7 +224,7 @@ jobs:
|
||||
with:
|
||||
node-version: '10.x'
|
||||
registry-url: 'https://registry.npmjs.org'
|
||||
- run: npm install
|
||||
- run: npm ci
|
||||
# Publish to npm
|
||||
- run: npm publish --access public
|
||||
env:{% raw %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 审查您的安全日志
|
||||
intro: 您可以查看用户帐户的安全日志，以更好地了解您执行的操作以及其他人执行的与您有关的操作。
|
||||
title: Reviewing your security log
|
||||
intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /articles/reviewing-your-security-log
|
||||
@@ -14,258 +14,254 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: 安全日志
|
||||
shortTitle: Security log
|
||||
---
|
||||
## Accessing your security log
|
||||
|
||||
## 访问安全日志
|
||||
|
||||
安全日志列出了过去 90 天内执行的所有操作。
|
||||
The security log lists all actions performed within the last 90 days.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
2. 在用户设置侧边栏中，单击 **Security log（安全日志）**。 
|
||||
2. In the user settings sidebar, click **Security log**.
|
||||
|
||||
{% else %}
|
||||
{% data reusables.user_settings.security %}
|
||||
3. 在“Security history（安全历史记录）”下，将显示您的日志。 
|
||||
4. 单击条目以查看有关该事件的更多信息。 
|
||||
3. Under "Security history," your log is displayed.
|
||||
|
||||
4. Click on an entry to see more information about the event.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
## 搜索安全日志
|
||||
## Searching your security log
|
||||
|
||||
{% data reusables.audit_log.audit-log-search %}
|
||||
|
||||
### 基于执行的操作搜索
|
||||
### Search based on the action performed
|
||||
{% else %}
|
||||
## 了解安全日志中的事件
|
||||
## Understanding events in your security log
|
||||
{% endif %}
|
||||
|
||||
安全日志中列出的事件由您的操作触发。 操作分为以下几类：
|
||||
The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
|
||||
|
||||
| 类别名称 | 描述 |
|
||||
| -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %}
|
||||
| [`account_recovery_token`](#account_recovery_token-category-actions) | 包含与[添加恢复令牌](/articles/configuring-two-factor-authentication-recovery-methods)相关的所有活动。 |
|
||||
| [`计费，帐单`](#billing-category-actions) | 包含与帐单信息相关的所有活动。 |
|
||||
| [`codespaces`](#codespaces-category-actions) | 包含与 {% data variables.product.prodname_codespaces %} 相关的所有活动。 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)”。 |
|
||||
| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | 包含与签署 {% data variables.product.prodname_marketplace %} 开发者协议相关的所有活动。 |
|
||||
| [`marketplace_listing`](#marketplace_listing-category-actions) | 包含与 {% data variables.product.prodname_marketplace %} 中列出的应用程序相关的所有活动。{% endif %}
|
||||
| [`oauth_access`](#oauth_access-category-actions) | 包含与您已连接的 [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) 相关的所有活动。{% ifversion fpt or ghec %}
|
||||
| [`payment_method`](#payment_method-category-actions) | 包含与 {% data variables.product.prodname_dotcom %} 订阅支付相关的所有活动。{% endif %}
|
||||
| [`profile_picture`](#profile_picture-category-actions) | 包含与头像相关的所有活动。 |
|
||||
| [`project`](#project-category-actions) | 包含与项目板相关的所有活动。 |
|
||||
| [`public_key`](#public_key-category-actions) | 包含与[公共 SSH 密钥](/articles/adding-a-new-ssh-key-to-your-github-account)相关的所有活动。 |
|
||||
| [`repo`](#repo-category-actions) | 包含与您拥有的仓库相关的所有活动。{% ifversion fpt or ghec %}
|
||||
| [`sponsors`](#sponsors-category-actions) | 包含与 {% data variables.product.prodname_sponsors %}和赞助者按钮相关的所有事件（请参阅“[关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)”和“[在仓库中显示赞助者按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）{% endif %}{% ifversion ghes or ghae %}
|
||||
| [`团队`](#team-category-actions) | 包含与您所在团队相关的所有活动。{% endif %}{% ifversion not ghae %}
|
||||
| [`two_factor_authentication`](#two_factor_authentication-category-actions) | 包含与[双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)相关的所有活动。{% endif %}
|
||||
| [`用户`](#user-category-actions) | 包含与您的帐户相关的所有活动。 |
|
||||
| Category name | Description
|
||||
|------------------|-------------------{% ifversion fpt or ghec %}
|
||||
| [`billing`](#billing-category-actions) | Contains all activities related to your billing information.
|
||||
| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."
|
||||
| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}
|
||||
| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
|
||||
| [`payment_method`](#payment_method-category-actions) | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %}
|
||||
| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your profile picture.
|
||||
| [`project`](#project-category-actions) | Contains all activities related to project boards.
|
||||
| [`public_key`](#public_key-category-actions) | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account).
|
||||
| [`repo`](#repo-category-actions) | Contains all activities related to the repositories you own.{% ifversion fpt or ghec %}
|
||||
| [`sponsors`](#sponsors-category-actions) | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% ifversion ghes or ghae %}
|
||||
| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% ifversion not ghae %}
|
||||
| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
|
||||
| [`user`](#user-category-actions) | Contains all activities related to your account.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## 导出安全日志
|
||||
## Exporting your security log
|
||||
|
||||
{% data reusables.audit_log.export-log %}
|
||||
{% data reusables.audit_log.exported-log-keys-and-values %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 安全日志操作
|
||||
## Security log actions
|
||||
|
||||
安全日志中记录为事件的一些最常见操作的概述。
|
||||
An overview of some of the most common actions that are recorded as events in the security log.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
### `account_recovery_token` 类操作
|
||||
### `billing` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| --------------- | ----------------------------------------------------------------------------------------- |
|
||||
| `confirm` | 当您成功[使用恢复提供程序存储新令牌](/articles/configuring-two-factor-authentication-recovery-methods)时触发。 |
|
||||
| `recover` | 当您成功[取回帐户恢复令牌](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)时触发。 |
|
||||
| `recover_error` | 当 {% data variables.product.prodname_dotcom %} 无法验证所使用的令牌时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
|
||||
| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address).
|
||||
|
||||
### `billing` 类操作
|
||||
### `codespaces` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| --------------------- | ----------------------------------------------------------------------------------------------------------- |
|
||||
| `change_billing_type` | 当您[更改 {% data variables.product.prodname_dotcom %} 的支付方式](/articles/adding-or-editing-a-payment-method)时触发。 |
|
||||
| `change_email` | 当您[更改您的电子邮件地址](/articles/changing-your-primary-email-address)时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [create a codespace](/github/developing-online-with-codespaces/creating-a-codespace).
|
||||
| `resume` | Triggered when you resume a suspended codespace.
|
||||
| `delete` | Triggered when you [delete a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).
|
||||
| `manage_access_and_security` | Triggered when you update [the repositories a codespace has access to](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
| `trusted_repositories_access_update` | Triggered when you change your user account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
|
||||
### `codespaces` 类操作
|
||||
### `marketplace_agreement_signature` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `create` | 当您[创建代码空间](/github/developing-online-with-codespaces/creating-a-codespace)时触发。 |
|
||||
| `resume` | 恢复暂停的代码空间时触发。 |
|
||||
| `delete` | 当您[删除代码空间](/github/developing-online-with-codespaces/deleting-a-codespace)时触发。 |
|
||||
| `manage_access_and_security` | 当您更新[代码空间可以访问的仓库时](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)触发。 |
|
||||
| `trusted_repositories_access_update` | 当您更改用户帐户的 [{% data variables.product.prodname_codespaces %} 访问权限和安全设置](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
|
||||
### `marketplace_agreement_signature` 类操作
|
||||
### `marketplace_listing` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| -------- | --------------------------------------------------------------- |
|
||||
| `create` | 在签署 {% data variables.product.prodname_marketplace %} 开发者协议时触发。 |
|
||||
|
||||
### `marketplace_listing` 类操作
|
||||
|
||||
| 操作 | 描述 |
|
||||
| --------- | -------------------------------------------------------------------- |
|
||||
| `批准` | 当您的列表被批准包含在 {% data variables.product.prodname_marketplace %} 中时触发。 |
|
||||
| `create` | 当您在 {% data variables.product.prodname_marketplace %} 中为应用程序创建列表时触发。 |
|
||||
| `delist` | 当您的列表从 {% data variables.product.prodname_marketplace %} 中被删除时触发。 |
|
||||
| `redraft` | 将您的列表被返回到草稿状态时触发。 |
|
||||
| `reject` | 当您的列表被拒绝包含在 {% data variables.product.prodname_marketplace %} 中时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
|
||||
| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
|
||||
| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
|
||||
| `redraft` | Triggered when your listing is sent back to draft state.
|
||||
| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### `oauth_authority` 类别操作
|
||||
### `oauth_authorization` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `create` | 当您[授予 {% data variables.product.prodname_oauth_app %} 访问权限](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)时触发。 |
|
||||
| `destroy` | 当您 [撤销 {% data variables.product.prodname_oauth_app %}对您帐户的访问](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} 时，以及当 [授权被吊销或过期](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)时触发。{% else %}.{% endif %}
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
|
||||
| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
### `payment_method` 类操作
|
||||
### `payment_method` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| -------- | ------------------------------------------------------ |
|
||||
| `clear` | 当存档的[付款方式](/articles/removing-a-payment-method)被删除时触发。 |
|
||||
| `create` | 在添加新的付款方式（例如新的信用卡或 PayPal 帐户）时触发。 |
|
||||
| `update` | 当现有付款方式被更新时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `clear` | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed.
|
||||
| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account.
|
||||
| `update` | Triggered when an existing payment method is updated.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### `profile_picture` 类操作
|
||||
### `profile_picture` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| -------- | ------------------------------------------------------------ |
|
||||
| `update` | 当您[设置或更新个人资料图片](/articles/setting-your-profile-picture/)时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/).
|
||||
|
||||
### `project` 类操作
|
||||
### `project` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| ------------------------ | --------------------------------- |
|
||||
| `access` | 当项目板的可见性被更改时触发。 |
|
||||
| `create` | 在创建项目板时触发。 |
|
||||
| `rename` | 当项目板被重命名时触发。 |
|
||||
| `update` | 当项目板被更新时触发。 |
|
||||
| `delete` | 在删除项目板时触发。 |
|
||||
| `link` | 当仓库被链接到项目板时触发。 |
|
||||
| `unlink` | 当仓库从项目板解除链接时触发。 |
|
||||
| `update_user_permission` | 在项目板中添加或删除外部协作者时，或者他们的权限级别被更改时触发。 |
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `access` | Triggered when a project board's visibility is changed.
|
||||
| `create` | Triggered when a project board is created.
|
||||
| `rename` | Triggered when a project board is renamed.
|
||||
| `update` | Triggered when a project board is updated.
|
||||
| `delete` | Triggered when a project board is deleted.
|
||||
| `link` | Triggered when a repository is linked to a project board.
|
||||
| `unlink` | Triggered when a repository is unlinked from a project board.
|
||||
| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed.
|
||||
|
||||
### `public_key` 类操作
|
||||
### `public_key` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). |
|
||||
| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys). |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account).
|
||||
| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).
|
||||
|
||||
### `repo` 类操作
|
||||
### `repo` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `access` | 当您拥有的仓库[从“私有”切换到“公共”](/articles/making-a-private-repository-public)（反之亦然）时触发。 |
|
||||
| `add_member` | 当 {% data variables.product.product_name %} 用户{% ifversion fpt or ghec %}[被邀请协作使用](/articles/inviting-collaborators-to-a-personal-repository){% else %}[被授权协作使用](/articles/inviting-collaborators-to-a-personal-repository){% endif %}仓库时触发。 |
|
||||
| `add_topic` | 当仓库所有者向仓库[添加主题](/articles/classifying-your-repository-with-topics)时触发。 |
|
||||
| `archived` | 当仓库所有者[存档仓库](/articles/about-archiving-repositories)时触发。{% ifversion ghes %}
|
||||
| `config.disable_anonymous_git_access` | 当公共仓库中[禁用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)时触发。 |
|
||||
| `config.enable_anonymous_git_access` | 当公共仓库中[启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)时触发。 |
|
||||
| `config.lock_anonymous_git_access` | 当仓库的[匿名 Git 读取权限设置被锁定](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)时触发。 |
|
||||
| `config.unlock_anonymous_git_access` | 当仓库的[匿名 Git 读取权限设置被解锁](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)时触发。{% endif %}
|
||||
| `create` | 在[创建新仓库](/articles/creating-a-new-repository)时触发。 |
|
||||
| `destroy` | 当[仓库被删除](/articles/deleting-a-repository)时触发。{% ifversion fpt or ghec %}
|
||||
| `禁用` | 当仓库被禁用（例如，因[资金不足](/articles/unlocking-a-locked-account)）时触发。{% endif %}{% ifversion fpt or ghec %}
|
||||
| `启用` | 在重新启用仓库时触发。{% endif %}
|
||||
| `remove_member` | 从[仓库中删除 {% data variables.product.product_name %} 用户的协作者身份](/articles/removing-a-collaborator-from-a-personal-repository)时触发。 |
|
||||
| `remove_topic` | 当仓库所有者从仓库中删除主题时触发。 |
|
||||
| `rename` | 当[仓库被重命名](/articles/renaming-a-repository)时触发。 |
|
||||
| `转让` | 当[仓库被转让](/articles/how-to-transfer-a-repository)时触发。 |
|
||||
| `transfer_start` | 在仓库转让即将发生时触发。 |
|
||||
| `unarchived` | 当仓库所有者取消存档仓库时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa).
|
||||
| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository.
|
||||
| `add_topic` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
|
||||
| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
|
||||
| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
|
||||
| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
|
||||
| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
|
||||
| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
|
||||
| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).
|
||||
| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
|
||||
| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
|
||||
| `enable` | Triggered when a repository is re-enabled.{% endif %}
|
||||
| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
|
||||
| `remove_topic` | Triggered when a repository owner removes a topic from a repository.
|
||||
| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
|
||||
| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
|
||||
| `transfer_start` | Triggered when a repository transfer is about to occur.
|
||||
| `unarchived` | Triggered when a repository owner unarchives a repository.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### `sponsors` 类操作
|
||||
### `sponsors` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `custom_amount_settings_change` | 启用或禁用自定义金额时或更改建议的自定义金额时触发（请参阅“[管理您的赞助级别](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)”） |
|
||||
| `repo_funding_links_file_action` | 更改仓库中的 FUNDING 文件时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”） |
|
||||
| `sponsor_sponsorship_cancel` | 当您取消赞助时触发（请参阅“[降级赞助](/articles/downgrading-a-sponsorship)”） |
|
||||
| `sponsor_sponsorship_create` | 当您赞助帐户时触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”） |
|
||||
| `sponsor_sponsorship_payment_complete` | 当您赞助一个帐户并且您的付款已经处理完毕后触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”） |
|
||||
| `sponsor_sponsorship_preference_change` | 当您更改是否接收被赞助开发者的电子邮件更新时触发（请参阅“[管理赞助](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)”） |
|
||||
| `sponsor_sponsorship_tier_change` | 当您升级或降级赞助时触发（请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”） |
|
||||
| `sponsored_developer_approve` | 当您的 {% data variables.product.prodname_sponsors %} 帐户被批准时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） |
|
||||
| `sponsored_developer_create` | 当您的 {% data variables.product.prodname_sponsors %} 帐户创建时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） |
|
||||
| `sponsored_developer_disable` | 帐户 {% data variables.product.prodname_sponsors %} 禁用时触发 |
|
||||
| `sponsored_developer_redraft` | 当您的 {% data variables.product.prodname_sponsors %} 帐户从已批准状态恢复为草稿状态时触发 |
|
||||
| `sponsored_developer_profile_update` | 在编辑您的被赞助开发者个人资料时触发（请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)”） |
|
||||
| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") |
|
||||
| `sponsored_developer_tier_description_update` | 当您更改赞助等级的说明时触发（请参阅“[管理赞助等级](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)”） |
|
||||
| `sponsored_developer_update_newsletter_send` | 当您向赞助者发送电子邮件更新时触发（请参阅“[联系赞助者](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)”） |
|
||||
| `waitlist_invite_sponsored_developer` | 当您从等候名单被邀请加入 {% data variables.product.prodname_sponsors %} 时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） |
|
||||
| `waitlist_join` | 当您加入成为被赞助开发者的等候名单时触发（请参阅“[为您的用户帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")
|
||||
| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")
|
||||
| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
|
||||
| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
|
||||
| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
|
||||
| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")
|
||||
| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
|
||||
| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled
|
||||
| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state
|
||||
| `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")
|
||||
| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")
|
||||
| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")
|
||||
| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### `successor_invitation` 类操作
|
||||
### `successor_invitation` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `accept` | 当您接受继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
|
||||
| `cancel` | 当您取消继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
|
||||
| `create` | 当您创建继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
|
||||
| `decline` | 当您拒绝继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
|
||||
| `revoke` | 当您撤销继承邀请时触发（请参阅“[保持用户帐户仓库的所有权连续性](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)”） |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
|
||||
### `team` 类操作
|
||||
### `team` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| ------------------- | ------------------------------------------------------------------------ |
|
||||
| `add_member` | 当您所属组织的成员[将您添加到团队](/articles/adding-organization-members-to-a-team)时触发。 |
|
||||
| `add_repository` | 当您所属团队被授予控制仓库的权限时触发。 |
|
||||
| `create` | 当您所属组织中创建了新团队时触发。 |
|
||||
| `destroy` | 当您所属团队从组织中被删除时触发。 |
|
||||
| `remove_member` | [从您所属团队中删除组织成员](/articles/removing-organization-members-from-a-team)时触发。 |
|
||||
| `remove_repository` | 当仓库不再受团队控制时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team).
|
||||
| `add_repository` | Triggered when a team you are a member of is given control of a repository.
|
||||
| `create` | Triggered when a new team in an organization you belong to is created.
|
||||
| `destroy` | Triggered when a team you are a member of is deleted from the organization.
|
||||
| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of.
|
||||
| `remove_repository` | Triggered when a repository is no longer under a team's control.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion not ghae %}
|
||||
### `two_factor_authentication` 类操作
|
||||
### `two_factor_authentication` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| ---------- | ----------------------------------------------------------------------------------- |
|
||||
| `enabled` | 在启用[双重身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa)时触发。 |
|
||||
| `disabled` | 在禁用双重身份验证时触发。 |
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled.
|
||||
| `disabled` | Triggered when two-factor authentication is disabled.
|
||||
{% endif %}
|
||||
|
||||
### `user` 类操作
|
||||
### `user` category actions
|
||||
|
||||
| 操作 | 描述 |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `add_email` | 当您 |
|
||||
| {% ifversion not ghae %}[添加新电子邮件地址](/articles/changing-your-primary-email-address){% else %}添加新电子邮件地址{% endif %}时触发。{% ifversion fpt or ghec %} | |
|
||||
| `codespaces_trusted_repo_access_granted` | 当您[允许为某个仓库创建的代码空间访问您的用户帐户拥有的其他仓库]时触发(/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)。 |
|
||||
| `codespaces_trusted_repo_access_revoked` | 当您[禁止为某个仓库创建的代码空间访问您的用户帐户拥有的其他仓库]时触发(/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)。 |{% endif %}
|
||||
| `create` | 在创建新帐户时触发。{% ifversion not ghae %}
|
||||
| `change_password` | 当您更改密码时触发。 |
|
||||
| `forgot_password` | 在您要求[重置密码](/articles/how-can-i-reset-my-password)时触发。{% endif %}
|
||||
| `hide_private_contributions_count` | 当您[在个人资料中隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)时触发。 |
|
||||
| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
|
||||
| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces.
|
||||
| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your user account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces. {% endif %}
|
||||
| `create` | Triggered when you create a new user account.{% ifversion not ghae %}
|
||||
| `change_password` | Triggered when you change your password.
|
||||
| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %}
|
||||
| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).
|
||||
| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
|
||||
`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
|
||||
| `failed_login` | Triggered when you failed to log in successfully.
|
||||
| `remove_email` | Triggered when you remove an email address.
|
||||
| `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %}
|
||||
| `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %}
|
||||
| `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% ifversion not ghae %}
|
||||
| `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %}
|
||||
|
||||
### `user_status` category actions
|
||||
|
||||
`mandatory_message_viewed` | 当您查看必读消息时触发（更多信息请参阅“[自定义用户消息](/admin/user-management/customizing-user-messages-for-your-enterprise)” | |{% endif %}| | `failed_login` | 当您未能成功登录时触发。 | `remove_email` | 当您删除电子邮件地址时触发。 | `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %} | `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %} | `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% ifversion not ghae %} | `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %}
|
||||
|
||||
### `user_status` 类操作
|
||||
|
||||
| 操作 | 描述 |
|
||||
| --------- | -------------------------------------------------------------------------------------------- |
|
||||
| `update` | 当您在个人资料中设置或更改状态时触发。 更多信息请参阅“[设置状态](/articles/personalizing-your-profile/#setting-a-status)”。 |
|
||||
| `destroy` | 当您在个人资料中清除状态时触发。 |
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `update` | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)."
|
||||
| `destroy` | Triggered when you clear the status on your profile.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 丢失 2FA 凭据时恢复帐户
|
||||
intro: 如果无法访问双重身份验证凭据，您可以使用恢复代码或其他恢复选项重新获取对帐户的访问权限。
|
||||
title: Recovering your account if you lose your 2FA credentials
|
||||
intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
|
||||
redirect_from:
|
||||
- /articles/recovering-your-account-if-you-lost-your-2fa-credentials/
|
||||
- /articles/authenticating-with-an-account-recovery-token/
|
||||
@@ -13,93 +13,75 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- 2FA
|
||||
shortTitle: 使用 2FA 找回帐户
|
||||
shortTitle: Recover an account with 2FA
|
||||
---
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**：{% data reusables.two_fa.support-may-not-help %}
|
||||
**Warning**: {% data reusables.two_fa.support-may-not-help %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 使用双因素身份验证恢复代码
|
||||
## Using a two-factor authentication recovery code
|
||||
|
||||
使用您的恢复代码之一自动重新进入您的帐户。 您可能已将恢复代码保存到密码管理器或计算机的下载文件夹中。 恢复代码的默认文件名为 `github-recovery-codes.txt`。 有关恢复代码的更多信息，请参阅“[配置双因素身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)”。
|
||||
Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
|
||||
|
||||
{% data reusables.two_fa.username-password %}{% ifversion fpt or ghec %}
|
||||
2. 在“Having Problems?（有问题？）”下，单击 **Enter a two-factor recovery code（输入双重恢复代码）**。 {% else %}
|
||||
2. 在 2FA 页面上的“Don't have your phone?（没有您的电话？）”下，单击 **Enter a two-factor recovery code（输入双因素恢复代码）**。 {% endif %}
|
||||
3. 输入恢复代码之一，然后单击 **Verify（验证）**。 
|
||||
2. Under "Having Problems?", click **Enter a two-factor recovery code**.
|
||||
{% else %}
|
||||
2. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
|
||||
{% endif %}
|
||||
3. Type one of your recovery codes, then click **Verify**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 使用后备号码进行身份验证
|
||||
## Authenticating with a fallback number
|
||||
|
||||
如果无法访问主要 TOTP 应用程序或电话号码，则可以提供发送到后备号码的双因素身份验证码，以自动重新获得对帐户的访问权限。
|
||||
If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account.
|
||||
{% endif %}
|
||||
|
||||
## 使用安全密钥进行身份验证
|
||||
## Authenticating with a security key
|
||||
|
||||
如果您使用安全密钥配置双重身份验证，则可以使用安全密钥作为辅助身份验证方法来自动重新获得对帐户的访问权限。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)”。
|
||||
If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 使用经过验证的设备、SSH 令牌或个人访问令牌进行身份验证
|
||||
## Authenticating with a verified device, SSH token, or personal access token
|
||||
|
||||
如果您知道 {% data variables.product.product_name %} 密码但无法访问双重身份验证凭据，或没有双重身份验证恢复代码，则可以将一次性密码发送到经验证的电子邮件地址，以开始验证过程，重新获得对帐户的访问权限。
|
||||
If you know your {% data variables.product.product_name %} password but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注**：出于安全原因，使用一次性密码验证来重新获得帐户访问权限可能需要 3-5 个工作日。 在此期间提交的其他请求将不予审查。
|
||||
**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take 3-5 business days. Additional requests submitted during this time will not be reviewed.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
在这 3-5 天的等待期内，您随时可以使用双重身份验证凭据或双重身份验证恢复代码重新获得对帐户的访问权限。
|
||||
You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
|
||||
|
||||
1. 输入您的用户名和密码以提示身份验证。 如果您不知道 {% data variables.product.product_name %} 密码，将无法生成一次性密码。
|
||||
2. 在“Having Problems?（有问题？）”下，单击 **Can't access your two factor device or valid recovery codes?（无法访问双重设备或有效的恢复代码？）**。 
|
||||
3. 单击 **I understand, get started（我理解，开始）**请求重置身份验证设置。 
|
||||
4. 单击 **Send one-time password（发送一次性密码）**向与您的帐户关联的所有电子邮件地址发送一次性密码。 
|
||||
5. 在“One-time password（一次性密码）”下，键入恢复电子邮件 {% data variables.product.prodname_dotcom %} 发送的临时密码。 
|
||||
6. 单击 **Verify email address（验证电子邮件地址）**。
|
||||
7. 选择替代验证因素。
|
||||
- 如果您之前已经使用当前设备登录此帐户，并且想使用该设备进行验证，请单击 **Verify with this device（使用此设备进行验证）**。
|
||||
- 如果您之前已在此帐户上设置 SSH 密钥，并且想使用此 SSH 密钥进行验证，请单击 **SSH key（SSH 密钥）**。
|
||||
- 如果您之前已经设置个人访问令牌，并且想使用个人访问令牌进行验证，请单击 **Personal access token（个人访问令牌）**。 
|
||||
8. {% data variables.contact.github_support %} 的成员将在 3-5 个工作日内审查您的请求并给您发送电子邮件。 如果您的请求获得批准，您将收到一个完成帐户恢复过程的链接。 如果您的请求被拒绝，电子邮件将说明就任何其他问题联系支持的方式。
|
||||
1. Type your username and password to prompt authentication. If you do not know your {% data variables.product.product_name %} password, you will not be able to generate a one-time password.
|
||||
2. Under "Having Problems?", click **Can't access your two factor device or valid recovery codes?**
|
||||
|
||||
3. Click **I understand, get started** to request a reset of your authentication settings.
|
||||
|
||||
4. Click **Send one-time password** to send a one-time password to all email addresses associated with your account.
|
||||
|
||||
5. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent.
|
||||
|
||||
6. Click **Verify email address**.
|
||||
7. Choose an alternative verification factor.
|
||||
- If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
|
||||
- If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**.
|
||||
- If you've previously set up a personal access token and would like to use the personal access token for verification, click **Personal access token**.
|
||||
|
||||
8. A member of {% data variables.contact.github_support %} will review your request and email you within 3-5 business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
|
||||
|
||||
## 使用帐户恢复令牌进行身份验证
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Account recovery tokens are deprecated and will be disabled on **December 1st, 2021**. Please ensure you have configured other two-factor recovery methods. For more information, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
If you lose access to the two-factor authentication methods for your account on {% data variables.product.product_location %}, you can retrieve your account recovery token from a partner recovery provider and ask {% data variables.product.prodname_dotcom %} Support to review it.
|
||||
|
||||
如果您无法访问双因素身份验证方法或恢复代码，并且已通过 Facebook 使用“异地恢复帐户”存储帐户恢复令牌，则可以使用您的令牌重新获得对帐户的访问权限。
|
||||
|
||||
如果无法重新获得对帐户的访问权限，请生成一次性密码以重新获得访问权限。 更多信息请参阅“[使用经过验证的设备、SSH 令牌或个人访问令牌进行身份验证](#authenticating-with-a-verified-device-ssh-token-or-personal-access-token)”。
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告：**
|
||||
- 提取帐户恢复令牌之前，您应尝试使用[双因素身份验证码](/articles/accessing-github-using-two-factor-authentication)或双因素身份验证恢复代码重新获得对帐户的访问权限。 更多信息请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
1. 在 Facebook 中，导航到 [Security Settings（安全设置）](https://www.facebook.com/settings?tab=security)，然后单击 **Recover Accounts Elsewhere（异地恢复帐户）**。 
|
||||
2. Click the recovery token associated with your account on {% data variables.product.product_location %}. 
|
||||
3. 要取回帐户恢复令牌，请单击 **Recover This Account（恢复此帐户）**。 此时将打开一个新窗口，将您返回到 {% data variables.product.product_name %}。 
|
||||
4. 联系 {% data variables.contact.contact_support %}，告知他们您的帐户恢复令牌已准备好进行审查。
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[关于双重身份验证](/articles/about-two-factor-authentication)"
|
||||
- "[配置双重身份验证](/articles/configuring-two-factor-authentication)"
|
||||
- "[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- “[使用双重身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication)”。
|
||||
- "[About two-factor authentication](/articles/about-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
|
||||
|
||||
@@ -14,15 +14,21 @@ topics:
|
||||
|
||||
{% data reusables.cli.cli-extensions %} For more information about how to use {% data variables.product.prodname_cli %} extensions, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)."
|
||||
|
||||
You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. At the root of the repository, there must be an executable file with the same name as the repository. This file will be executed when the extension is invoked.
|
||||
You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. The repository must have an executable file at its root with the same name as the repository or a set of precompiled binary executables attached to a release.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: We recommend that the executable file is a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension.
|
||||
**Note**: When relying on an executable script, we recommend using a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. If you would prefer to not rely on users having interpreters installed, consider a precompiled extension.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Creating an extension with `gh extension create`
|
||||
## Creating an interpreted extension with `gh extension create`
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Running `gh extension create` with no arguments will start an interactive wizard.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can use the `gh extension create` command to create a project for your extension, including a bash script that contains some starter code.
|
||||
|
||||
@@ -34,7 +40,35 @@ You can use the `gh extension create` command to create a project for your exten
|
||||
|
||||
1. Follow the printed instructions to finalize and optionally publish your extension.
|
||||
|
||||
## Creating an extension manually
|
||||
## Creating a precompiled extension in Go with `gh extension create`
|
||||
|
||||
You can use the `--precompiled=go` argument to create a Go-based project for your extension, including Go scaffolding, workflow scaffolding, and starter code.
|
||||
|
||||
1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=go`.
|
||||
|
||||
```shell
|
||||
gh extension create --precompiled=go <em>EXTENSION-NAME</em>
|
||||
```
|
||||
|
||||
1. Follow the printed instructions to finalize and optionally publish your extension.
|
||||
|
||||
## Creating a non-Go precompiled extension with `gh extension create`
|
||||
|
||||
You can use the `--precompiled=other` argument to create a project for your non-Go precompiled extension, including workflow scaffolding.
|
||||
|
||||
1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=other`.
|
||||
|
||||
```shell
|
||||
gh extension create --precompiled=other <em>EXTENSION-NAME</em>
|
||||
```
|
||||
|
||||
1. Add some initial code for your extension in your compiled language of choice.
|
||||
|
||||
1. Fill in `script/build.sh` with code to build your extension to ensure that your extension can be built automatically.
|
||||
|
||||
1. Follow the printed instructions to finalize and optionally publish your extension.
|
||||
|
||||
## Creating an interpreted extension manually
|
||||
|
||||
1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
|
||||
|
||||
@@ -56,7 +90,7 @@ You can use the `gh extension create` command to create a project for your exten
|
||||
|
||||
1. From your directory, install the extension as a local extension.
|
||||
|
||||
```bash
|
||||
```shell
|
||||
gh extension install .
|
||||
```
|
||||
|
||||
@@ -70,13 +104,13 @@ You can use the `gh extension create` command to create a project for your exten
|
||||
|
||||
```shell
|
||||
git init -b main
|
||||
git add . && git commit -m "initial commit"
|
||||
gh repo create gh-<em>EXTENSION-NAME</em> --source=. --public --push
|
||||
git add . && git commit -m "initial commit"
|
||||
gh repo create gh-<em>EXTENSION-NAME</em> --source=. --public --push
|
||||
```
|
||||
|
||||
1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
|
||||
|
||||
## Tips for writing {% data variables.product.prodname_cli %} extensions
|
||||
## Tips for writing interpreted {% data variables.product.prodname_cli %} extensions
|
||||
|
||||
### Handling arguments and flags
|
||||
|
||||
@@ -120,34 +154,128 @@ fi
|
||||
|
||||
### Calling core commands in non-interactive mode
|
||||
|
||||
Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments.
|
||||
Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments.
|
||||
|
||||
For example, to create an issue programmatically, specify the title and body:
|
||||
|
||||
```bash
|
||||
```shell
|
||||
gh issue create --title "My Title" --body "Issue description"
|
||||
```
|
||||
|
||||
### Fetching data programatically
|
||||
|
||||
Many core commands support the `--json` flag for fetching data programatically. For example, to return a JSON object listing the number, title, and mergeability status of pull requests:
|
||||
```bash
|
||||
|
||||
```shell
|
||||
gh pr list --json number,title,mergeStateStatus
|
||||
```
|
||||
|
||||
If there is not a core command to fetch specific data from GitHub, you can use the [`gh api`](https://cli.github.com/manual/gh_api) command to access the GitHub API. For example, to fetch information about the current user:
|
||||
```bash
|
||||
|
||||
```shell
|
||||
gh api user
|
||||
```
|
||||
|
||||
All commands that output JSON data also have options to filter that data into something more immediately usable by scripts. For example, to get the current user's name:
|
||||
|
||||
```bash
|
||||
```shell
|
||||
gh api user --jq '.name'
|
||||
```
|
||||
|
||||
For more information, see [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting).
|
||||
|
||||
## Creating a precompiled extension manually
|
||||
|
||||
1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`.
|
||||
|
||||
1. In the directory you created, add some source code. For example:
|
||||
|
||||
```go
|
||||
package main
|
||||
import (
|
||||
"github.com/cli/go-gh"
|
||||
"fmt"
|
||||
)
|
||||
|
||||
func main() {
|
||||
args := []string{"api", "user", "--jq", `"You are @\(.login) (\(.name))"` }
|
||||
stdOut, _, err := gh.Exec(args...)
|
||||
if err != nil {
|
||||
fmt.Println(err)
|
||||
return
|
||||
}
|
||||
fmt.Println(stdOut.String())
|
||||
}
|
||||
```
|
||||
|
||||
1. From your directory, install the extension as a local extension.
|
||||
|
||||
```shell
|
||||
gh extension install .
|
||||
```
|
||||
|
||||
1. Build your code. For example, with Go, replacing `YOUR-USERNAME` with your GitHub username:
|
||||
|
||||
```shell
|
||||
go mod init github.com/<em>YOUR-USERNAME</em>/gh-whoami
|
||||
go mod tidy
|
||||
go build
|
||||
```
|
||||
|
||||
1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`.
|
||||
|
||||
```shell
|
||||
gh <em>EXTENSION-NAME</em>
|
||||
```
|
||||
|
||||
1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Be careful not to commit the binary produced by your compilation step to version control.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
```shell
|
||||
git init -b main
|
||||
echo "gh-<em>EXTENSION-NAME</em>" >> .gitignore
|
||||
git add main.go go.* .gitignore && git commit -m'Initial commit'
|
||||
gh repo create "gh-<em>EXTENSION-NAME</em>"
|
||||
```
|
||||
|
||||
1. Create a release to share your precompiled extension with others. Compile for each platform you want to support, attaching each binary to a release as an asset. Binary executables attached to releases must follow a naming convention and have a suffix of <em>OS-ARCHITECTURE\[EXTENSION\]</em>.
|
||||
|
||||
For example, an extension named `whoami` compiled for Windows 64bit would have the name `gh-whoami-windows-amd64.exe` while the same extension compiled for Linux 32bit would have the name `gh-whoami-linux-386`. To see an exhaustive list of OS and architecture combinations recognized by `gh`, see [this source code](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** For your extension to run properly on Windows, its asset file must have a `.exe` extension. No extension is needed for other operating systems.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Releases can be created from the command line. For example:
|
||||
|
||||
```shell
|
||||
git tag v1.0.0
|
||||
git push origin v1.0.0
|
||||
GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe
|
||||
GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64
|
||||
GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64
|
||||
gh release create v1.0.0 ./*amd64*
|
||||
|
||||
1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
|
||||
|
||||
|
||||
## Tips for writing precompiled {% data variables.product.prodname_cli %} extensions
|
||||
|
||||
### Automating releases
|
||||
|
||||
Consider adding the [gh-extension-precompile](https://github.com/cli/gh-extension-precompile) action to a workflow in your project. This action will automatically produce cross-compiled Go binaries for your extension and supplies build scaffolding for non-Go precompiled extensions.
|
||||
|
||||
### Using {% data variables.product.prodname_cli %} features from Go-based extensions
|
||||
|
||||
Consider using [go-gh](https://github.com/cli/go-gh), a Go library that exposes pieces of `gh` functionality for use in extensions.
|
||||
|
||||
## Next steps
|
||||
|
||||
To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension).
|
||||
|
||||
@@ -6,10 +6,6 @@
|
||||
term: 访问令牌
|
||||
description: >-
|
||||
在命令行或 API 上执行 HTTPS 上的 Git 操作时，用来代替密码的令牌，也称为个人访问令牌。
|
||||
-
|
||||
term: 帐户恢复令牌
|
||||
description: >-
|
||||
**已废弃，将在 2021 年 12 月 1 日禁用。** 作为帐户恢复设置一部分存储的身份验证凭据称为“异地恢复帐户”，用于存储此备份凭据。
|
||||
-
|
||||
term: API 预览
|
||||
description: >-
|
||||
@@ -158,7 +154,7 @@
|
||||
description: >-
|
||||
GitHub 上的特定活动，将会：- 添加方块到用户的贡献图："[计为贡献的活动](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - 添加活动到用户个人资料上的时间表："[贡献活动](/articles/viewing-contributions-on-your-profile/#contribution-activity)"
|
||||
-
|
||||
term: 贡献者
|
||||
term: 贡献者，参与者
|
||||
description: >-
|
||||
贡献者是指对仓库没有协作者权限但参与过项目，并且他们打开的拉取请求已合并到仓库的人员。
|
||||
-
|
||||
@@ -181,13 +177,13 @@
|
||||
-
|
||||
term: 默认分支
|
||||
description: >-
|
||||
仓库中新拉取请求和代码提交的基本分支。每个仓库至少有一个分支，Git 会在您初始化仓库时创建该分支。第一个分支通常称为 {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}，并且通常是默认分支。
|
||||
The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch.
|
||||
-
|
||||
term: 从属者图
|
||||
term: dependents graph
|
||||
description: >-
|
||||
一种显示依赖于公共仓库的包、项目和仓库的仓库图。
|
||||
-
|
||||
term: 依赖关系图
|
||||
term: dependency graph
|
||||
description: >-
|
||||
一种显示仓库所依赖的包和项目的仓库图。
|
||||
-
|
||||
@@ -252,7 +248,7 @@
|
||||
-
|
||||
term: gist
|
||||
description: >-
|
||||
Gist 是一个您可以在 GitHub 上编辑、克隆和复刻的可共享文件。您可以将 Gist 设为{% ifversion ghae %}内部{% else %}公共{% endif %}或机密，但机密 gist 可用于具有 URL 的{% ifversion ghae %}任何企业成员{% else %}任何人{% endif %}。
|
||||
A gist is a shareable file that you can edit, clone, and fork on GitHub. You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
|
||||
-
|
||||
term: Git
|
||||
description: >-
|
||||
@@ -377,7 +373,7 @@
|
||||
description: >-
|
||||
用户无法访问的个人帐户。当用户将其付费帐户降级到免费帐户或者其付费计划过期时，帐户将被锁定。
|
||||
-
|
||||
term: 管理控制台
|
||||
term: management console
|
||||
description: >-
|
||||
GitHub Enterprise 界面中包含管理功能的部分。
|
||||
-
|
||||
@@ -385,7 +381,7 @@
|
||||
description: >-
|
||||
Markdown 是一种非常简单的语义文件格式，与 .doc、.rtf 和 .txt 等格式不太相似。通过 Markdown，没有 web 发布背景知识的人也能编写文字（包含链接、列表、项目符号等）并将其像网站一样展示。GitHub 支持 Markdown，并使用特定形式的 Markdown，称为 GitHub Flavored Markdown。请参阅 [GitHub Flavored Markdown 规范](https://github.github.com/gfm/) 或 [在 GitHub 上编写和设置格式入门](/articles/getting-started-with-writing-and-formatting-on-github)。
|
||||
-
|
||||
term: 标记
|
||||
term: markup
|
||||
description: 一种用于标注和格式化文档的系统。
|
||||
-
|
||||
term: main
|
||||
@@ -396,7 +392,7 @@
|
||||
description: >-
|
||||
许多 Git 仓库中的默认分支。默认情况下，在命令行上创建新的 Git 仓库时，将创建一个名为 "master" 的分支。许多工具现在对默认分支使用替代名称。{% ifversion fpt or ghes > 3.1 or ghae %} 例如，在 GitHub 上创建新仓库时，默认分支称为 "main"。{% endif %}
|
||||
-
|
||||
term: 成员图
|
||||
term: members graph
|
||||
description: 显示仓库所有分叉的仓库图。
|
||||
-
|
||||
term: 提及
|
||||
@@ -422,7 +418,7 @@
|
||||
description: >-
|
||||
父团队的子团队。您可有多个子（或嵌套的）团队。
|
||||
-
|
||||
term: 网络图
|
||||
term: network graph
|
||||
description: >-
|
||||
显示整个仓库网络的分支历史记录的仓库图，其中包括根仓库的分支以及包含网络独有提交的分叉的分支。
|
||||
-
|
||||
@@ -543,10 +539,10 @@
|
||||
description: >-
|
||||
拉取请求中协作者批准更改或在拉取请求合并之前申请进一步更改的评论。
|
||||
-
|
||||
term: 脉冲图
|
||||
term: pulse graph
|
||||
description: 提供仓库活动概要的仓库图。
|
||||
-
|
||||
term: 打卡图
|
||||
term: punch graph
|
||||
description: >-
|
||||
根据周日期和时间显示仓库更新频率的仓库图
|
||||
-
|
||||
@@ -570,11 +566,7 @@
|
||||
-
|
||||
term: 变基
|
||||
description: >-
|
||||
要将一系列变更从一个分支重新应用到不同的基分支，并将分支的 HEAD 重置为结果。
|
||||
-
|
||||
term: 异地恢复帐户
|
||||
description: >-
|
||||
**已废弃，将在 2021 年 12 月 1 日禁用。**允许用户在无法使用双重身份验证方法或恢复代码时向其 GitHub 帐户添加额外一重安全保护。用户可以通过 Facebook 以帐户恢复令牌的形式存储其 GitHub 帐户的身份验证凭据，将其 GitHub 帐户与其 Facebook 帐户相关联。
|
||||
要将一系列变更从一个分支重新应用到不同的基础分支，并将分支的 HEAD 重置为结果。
|
||||
-
|
||||
term: 恢复代码
|
||||
description: 帮助您重新获取对 GitHub 帐户的访问权限的代码。
|
||||
|
||||
@@ -76,16 +76,6 @@
|
||||
- RemovedFromProjectEvent.projectColumnName
|
||||
owning_teams:
|
||||
- '@github/github-projects'
|
||||
-
|
||||
title: 创建内容附件
|
||||
description: 此预览支持创建内容附件。
|
||||
toggled_by: ':corsair-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.createContentAttachment
|
||||
owning_teams:
|
||||
- '@github/feature-lifecycle'
|
||||
-
|
||||
title: 标签预览
|
||||
description: >-
|
||||
|
||||
@@ -93,16 +93,6 @@
|
||||
- RemovedFromProjectEvent.projectColumnName
|
||||
owning_teams:
|
||||
- '@github/github-projects'
|
||||
-
|
||||
title: 创建内容附件
|
||||
description: 此预览支持创建内容附件。
|
||||
toggled_by: ':corsair-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.createContentAttachment
|
||||
owning_teams:
|
||||
- '@github/feature-lifecycle'
|
||||
-
|
||||
title: 标签预览
|
||||
description: >-
|
||||
|
||||
@@ -93,16 +93,6 @@
|
||||
- RemovedFromProjectEvent.projectColumnName
|
||||
owning_teams:
|
||||
- '@github/github-projects'
|
||||
-
|
||||
title: 创建内容附件
|
||||
description: 此预览支持创建内容附件。
|
||||
toggled_by: ':corsair-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.createContentAttachment
|
||||
owning_teams:
|
||||
- '@github/feature-lifecycle'
|
||||
-
|
||||
title: 标签预览
|
||||
description: >-
|
||||
|
||||
Reference in New Issue
Block a user