New translation batch for ja (#31451)
This commit is contained in:
docubot
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: サブスクリプションを表示する
|
||||
intro: 通知の送信元と通知のボリュームを把握するため、定期的にサブスクリプションを確認し、リポジトリを Watch することをお勧めします。
|
||||
title: Viewing your subscriptions
|
||||
intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.'
|
||||
redirect_from:
|
||||
- /articles/subscribing-to-conversations
|
||||
- /articles/unsubscribing-from-conversations
|
||||
@@ -24,63 +24,61 @@ versions:
|
||||
topics:
|
||||
- Notifications
|
||||
shortTitle: View subscriptions
|
||||
ms.openlocfilehash: 34faad79004d34f5beb14e8992b9aff4e6a3ab39
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145117238'
|
||||
---
|
||||
{% data variables.product.product_name %} で進行中のアクティビティのサブスクリプションの通知を受け取ります。 会話をサブスクライブする理由はたくさんあります。 詳細については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)」を参照してください。
|
||||
You receive notifications for your subscriptions of ongoing activity on {% data variables.product.product_name %}. There are many reasons you can be subscribed to a conversation. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)."
|
||||
|
||||
健全な通知ワークフローの一環として、サブスクリプションの監査とサブスクライブ解除をお勧めします。 登録解除のオプションの詳細については、「[サブスクリプションの管理」を](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)参照してください。
|
||||
We recommend auditing and unsubscribing from your subscriptions as a part of a healthy notifications workflow. For more information about your options for unsubscribing, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
|
||||
|
||||
## 通知過多の理由を診断する
|
||||
## Diagnosing why you receive too many notifications
|
||||
|
||||
インボックスの通知が多すぎて管理できない場合は、サブスクリプションが多すぎないか確認したり、通知設定を変更して、サブスクリプションと受信する通知の種類を減らしたりすることを検討してください。 たとえば、設定を無効にして、チームまたはリポジトリに参加するたびにすべてのリポジトリとすべての Team ディスカッションを自動的に監視することを検討できます。
|
||||
When your inbox has too many notifications to manage, consider whether you have oversubscribed or how you can change your notification settings to reduce the subscriptions you have and the types of notifications you're receiving. For example, you may consider disabling the settings to automatically watch all repositories and all team discussions whenever you've joined a team or repository.
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
詳細については、「[通知の設定](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)」を参照してください。
|
||||
For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
|
||||
|
||||
リポジトリのサブスクリプションの概要を確認するには、「[Watch しているリポジトリを確認する](#reviewing-repositories-that-youre-watching)」を参照してください。 {% tip %}
|
||||
To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)."
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** 通知するイベントの種類を選択するには、**監視ページ** の **[Watch/Watch 解除]** ドロップダウン リストの [[カスタム]](https://github.com/watching) オプションを使用するか、{% data variables.product.product_name %} の任意のリポジトリ ページを使用します。 詳細については、「[通知の設定](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)」を参照してください。
|
||||
**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
過去に Watch することを選択したリポジトリが忘れらていることが多くあります。 「Watched repositories」ページから、リポジトリから素早く Watch 解除することができます。 サブスクライブ解除する方法について詳しくは、{% data variables.product.prodname_blog %} の「[Watch 解除の推奨](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)」および「[サブスクリプションを管理する](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)」を参照してください。 トリアージワークフローを作成して、受信する通知を支援することもできます。 トリアージ ワークフローのガイダンスについては、「[通知をトリアージするためのワークフローのカスタマイズ](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)」を参照してください。
|
||||
Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
|
||||
|
||||
## サブスクリプションのリストを確認する
|
||||
## Reviewing all of your subscriptions
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. 左側のサイドバーの、通知元のリポジトリリストの下にある [通知の管理] ドロップダウンを使用して、 **[サブスクリプション]** をクリックします。
|
||||
![[通知の管理] ドロップダウン メニュー オプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
|
||||
1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**.
|
||||
|
||||
|
||||
2. フィルタとソートを使用して、サブスクリプションのリストを絞り込み、通知の受信を希望しない会話のサブスクリプションを解除します。
|
||||
2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:**
|
||||
- 忘れている可能性のあるサブスクリプションを確認するには、[least recently subscribed] でソートします。
|
||||
**Tips:**
|
||||
- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
|
||||
|
||||
- 引き続き通知が受信可能なリポジトリのリストを確認するには、[filter by repository] ドロップダウンメニューのリポジトリリストを参照します。
|
||||
- To review a list of repositories that you can still receive notifications for, see the repository list in the "filter by repository" drop-down menu.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Watch しているリポジトリを確認する
|
||||
## Reviewing repositories that you're watching
|
||||
|
||||
1. 左側のサイドバーの、リポジトリ リストの下にある [通知の管理] ドロップダウン メニューを使用して、 **[Watched repositories]** をクリックします。
|
||||
![[通知の管理] ドロップダウン メニュー オプション](/assets/images/help/notifications-v2/manage-notifications-options.png)
|
||||
2. Watch しているリポジトリを評価し、それらの更新がまだ関連していて有用であるかどうかを判断します。 リポジトリを Watch すると、そのリポジトリのすべての会話が通知されます。
|
||||
|
||||
1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**.
|
||||
|
||||
2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** リポジトリを監視する代わりに、{% data reusables.notifications-v2.custom-notification-types %} (リポジトリで有効になっている場合) の更新がある場合、またはこれらのオプションの任意の組み合わせがある場合にのみ通知を受信するか、リポジトリの監視を完全に解除することを検討してください。
|
||||
**Tip:** Instead of watching a repository, consider only receiving notifications when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options, or completely unwatching a repository.
|
||||
|
||||
リポジトリの Watch を解除しても、@mentioned されたときやスレッドに参加しているときには通知を受信することができます。 特定のイベント タイプの通知を受信するように設定すると、リポジトリにこれらのイベント タイプが更新された場合、スレッドに参加している場合、または参加している自分またはチームが @mentioned された場合にのみ通知されます。
|
||||
When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -79,15 +79,27 @@ You can customize notifications for a repository. For example, you can choose to
|
||||
### Participating in conversations
|
||||
Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox.
|
||||
|
||||
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %}.
|
||||
{% ifversion update-notification-settings-22 %}For conversations you're watching or participating in, you can choose whether you want to receive notifications on {% data variables.product.company_short %} or by email in your notification settings. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
For example:
|
||||
- If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications.
|
||||
- If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating".
|
||||
|
||||
If you do not enable watching or participating notifications for web{% ifversion fpt or ghes or ghec %} and mobile{% endif %}, then your notifications inbox will not have any updates.
|
||||
{% ifversion update-notification-settings-22 %}If you do not enable "Notify me: On GitHub" for watching or participating notifications, then your notifications inbox will not have any updates.
|
||||
|
||||
{% else %}
|
||||
|
||||
If you do not enable watching or participating notifications for web{% ifversion ghes %} and mobile{% endif %}, then your notifications inbox will not have any updates.{% endif %}
|
||||
|
||||
## Customizing your email notifications
|
||||
|
||||
@@ -146,11 +158,16 @@ Email notifications from {% data variables.product.product_location %} contain t
|
||||
|
||||
## Automatic watching
|
||||
|
||||
By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options.
|
||||
By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options in your notification settings.
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
|
||||
If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
|
||||
|
||||
For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
## Configuring your watch settings for an individual repository
|
||||
|
||||
@@ -172,9 +189,17 @@ If you belong to an organization, you can choose the email account you want noti
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
|
||||
3. Under "Default notification email", select the email address you'd like notifications sent to.
|
||||
|
||||
4. Click **Save**.
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes or ghae %}
|
||||
4. Click **Save**.{% endif %}
|
||||
|
||||
### Customizing email routes per organization
|
||||
|
||||
@@ -182,12 +207,35 @@ If you are a member of more than one organization, you can configure each one to
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
3. Under "Custom routing," find your organization's name in the list.
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
3. Under "Default notifications email", click **Custom routing**.
|
||||
|
||||
|
||||
|
||||
4. Click **Add new route**.
|
||||
|
||||
|
||||
|
||||
5. Click **Pick organization**, then select the organization you want to customize from the dropdown.
|
||||
|
||||
|
||||
|
||||
6. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
3. Under "Custom routing," find your organization's name in the list.
|
||||
|
||||
|
||||
|
||||
4. Click **Edit** next to the email address you want to change.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_dependabot_alerts %} notification options
|
||||
|
||||
@@ -197,14 +245,17 @@ If you are a member of more than one organization, you can configure each one to
|
||||
|
||||
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
{% ifversion update-notification-settings-22 or ghes %}
|
||||
## {% data variables.product.prodname_actions %} notification options
|
||||
|
||||
Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.
|
||||
Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.{% endif %}
|
||||
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
## Organization alerts notification options
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: プロフィールの README を管理する
|
||||
intro: '{% data variables.product.prodname_dotcom %} プロフィールに README を追加して、他のユーザに自分の情報を伝えることができます。'
|
||||
title: Managing your profile README
|
||||
intro: 'You can add a README to your {% data variables.product.prodname_dotcom %} profile to tell other people about yourself.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -11,71 +11,67 @@ redirect_from:
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-your-profile-readme
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
|
||||
shortTitle: Your profile README
|
||||
ms.openlocfilehash: 587bcea1e1a0f96aad8882b41196afcc6e433363
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147578901'
|
||||
---
|
||||
## プロフィール README について
|
||||
## About your profile README
|
||||
|
||||
プロフィール README を作成すると、{% data variables.product.product_location %} で自分に関する情報をコミュニティと共有できます。 {% data variables.product.prodname_dotcom %} では、プロフィールページの上部にプロフィール README が表示されます。
|
||||
You can share information about yourself with the community on {% data variables.product.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page.
|
||||
|
||||
プロフィール README に含める情報を決めることができるため、{% data variables.product.prodname_dotcom %} で自分に関するどのような情報を表示するかを完全に制御できます。 アクセスしたユーザがあなたのプロフィール README を見て、興味深い、楽しい、役立つと感じる可能性のある情報の例は次のとおりです。
|
||||
You decide what information to include in your profile README, so you have full control over how you present yourself on {% data variables.product.prodname_dotcom %}. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README.
|
||||
|
||||
- あなたの仕事や興味について説明した「自己紹介」セクション
|
||||
- あなたが誇りに思っているコントリビューションとそれらのコントリビューションについてのコンテキスト
|
||||
- あなたが関連しているコミュニティでサポートを得るためのガイド
|
||||
- An "About me" section that describes your work and interests
|
||||
- Contributions you're proud of, and context about those contributions
|
||||
- Guidance for getting help in communities where you're involved
|
||||
|
||||
|
||||
|
||||
|
||||
{% data variables.product.company_short %} Flavored Markdown を使用して、テキストをフォーマットし、絵文字、画像、GIF をプロフィール README に含めることができます。 詳細については、「[{% data variables.product.prodname_dotcom %} での書き込みと書式設定の概要](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)」を参照してください。
|
||||
You can format text and include emoji, images, and GIFs in your profile README by using {% data variables.product.company_short %} Flavored Markdown. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)." For a hands-on guide to customizing your profile README, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
|
||||
|
||||
## 前提条件
|
||||
## Prerequisites
|
||||
|
||||
次のすべてが当てはまる場合、GitHubは プロフィールページにプロフィール README を表示します。
|
||||
GitHub will display your profile README on your profile page if all of the following are true.
|
||||
|
||||
- {% data variables.product.prodname_dotcom %} ユーザ名にマッチする名前のリポジトリを作成した。
|
||||
- リポジトリがパブリックである。
|
||||
- リポジトリのルートに README.md という名前のファイルが含まれている。
|
||||
- README.md ファイルに任意のコンテンツが含まれている。
|
||||
- You've created a repository with a name that matches your {% data variables.product.prodname_dotcom %} username.
|
||||
- The repository is public.
|
||||
- The repository contains a file named README.md in its root.
|
||||
- The README.md file contains any content.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注**: 2020 年 7 月以前にユーザー名と同名のパブリック リポジトリを作成していた場合、{% data variables.product.prodname_dotcom %} のプロフィールにはリポジトリの README が自動的に表示されません。 {% data variables.product.prodname_dotcom_the_website %} のリポジトリに移動して、 **[プロフィールで共有]** をクリックすると、リポジトリの README をプロフィールで手動で共有できます。
|
||||
**Note**: If you created a public repository with the same name as your username before July 2020, {% data variables.product.prodname_dotcom %} won't automatically show the repository's README on your profile. You can manually share the repository's README to your profile by going to the repository on {% data variables.product.prodname_dotcom_the_website %} and clicking **Share to profile**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## プロフィールの README を追加する
|
||||
## Adding a profile README
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
2. [Repository name] の下に、{% data variables.product.prodname_dotcom %} のユーザ名とマッチするリポジトリ名を入力します。 たとえば、ユーザ名が「octocat」の場合、リポジトリ名は「octocat」である必要があります。
|
||||
![ユーザー名に一致する [リポジトリ名] フィールド](/assets/images/help/repository/repo-username-match.png)
|
||||
3. 必要に応じて、リポジトリの説明を追加します。 たとえば、「個人リポジトリ」などです。
|
||||
|
||||
4. **[パブリック]** を選択します。
|
||||
![可視性を選択するためのオプション ボタン ([パブリック] が選択された状態)](/assets/images/help/repository/create-personal-repository-visibility.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
|
||||
7. 右側のサイドバーの上にある **[README の編集]** をクリックします。
|
||||
|
||||
2. Under "Repository name", type a repository name that matches your {% data variables.product.prodname_dotcom %} username. For example, if your username is "octocat", the repository name must be "octocat".
|
||||
|
||||
3. Optionally, add a description of your repository. For example, "My personal repository."
|
||||
|
||||
4. Select **Public**.
|
||||
|
||||
{% data reusables.repositories.initialize-with-readme %}
|
||||
{% data reusables.repositories.create-repo %}
|
||||
7. Above the right sidebar, click **Edit README**.
|
||||
|
||||
|
||||
生成された README ファイルには、プロフィール README のアイディアを得るためのテンプレートが事前入力されています。
|
||||
|
||||
The generated README file is pre-populated with a template to give you some inspiration for your profile README.
|
||||
|
||||
|
||||
使用できるすべての絵文字とそのコードの概要については、[絵文字のチート シート](https://www.webfx.com/tools/emoji-cheat-sheet/)を参照してください。
|
||||
For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](https://www.webfx.com/tools/emoji-cheat-sheet/)."
|
||||
|
||||
## プロフィール README を削除する
|
||||
## Removing a profile README
|
||||
|
||||
次のいずれかに該当する場合、プロフィール README は {% data variables.product.prodname_dotcom %} のプロフィールから削除されます。
|
||||
The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply:
|
||||
|
||||
- README ファイルが空であるか、存在しない。
|
||||
- リポジトリがプライベートである。
|
||||
- リポジトリ名がユーザ名とマッチしなくなった。
|
||||
- The README file is empty or doesn't exist.
|
||||
- The repository is private.
|
||||
- The repository name no longer matches your username.
|
||||
|
||||
The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. リポジトリをプライベートにする方法については、「[リポジトリの可視性を変更する](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)」を参照してください。
|
||||
The method you choose depends upon your needs, but if you're unsure, we recommend making your repository private. For steps on how to make your repository private, see "[Changing a repository's visibility](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)."
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- [README について](/github/creating-cloning-and-archiving-repositories/about-readmes)
|
||||
- [About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Creating a JavaScript action
|
||||
shortTitle: Create a JavaScript action
|
||||
intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.'
|
||||
redirect_from:
|
||||
- /articles/creating-a-javascript-action
|
||||
@@ -15,7 +16,6 @@ type: tutorial
|
||||
topics:
|
||||
- Action development
|
||||
- JavaScript
|
||||
shortTitle: JavaScript action
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Releasing and maintaining actions
|
||||
shortTitle: Releasing and maintaining actions
|
||||
shortTitle: Release and maintain actions
|
||||
intro: You can leverage automation and open source best practices to release and maintain actions.
|
||||
type: tutorial
|
||||
topics:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configuring OpenID Connect in HashiCorp Vault
|
||||
shortTitle: Configuring OpenID Connect in HashiCorp Vault
|
||||
shortTitle: OpenID Connect in HashiCorp Vault
|
||||
intro: Use OpenID Connect within your workflows to authenticate with HashiCorp Vault.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Autoscaling with self-hosted runners
|
||||
shortTitle: Autoscale self-hosted runners
|
||||
intro: You can automatically scale your self-hosted runners in response to webhook events.
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -63,7 +64,7 @@ By default, self-hosted runners will automatically perform a software update whe
|
||||
To turn off automatic software updates and install software updates yourself, specify the `--disableupdate` flag when registering your runner using `config.sh`. For example:
|
||||
|
||||
```shell
|
||||
./config.sh --url <em>https://github.com/octo-org</em> --token <em>example-token</em> --disableupdate
|
||||
./config.sh --url https://github.com/YOUR-ORGANIZATION --token EXAMPLE-TOKEN --disableupdate
|
||||
```
|
||||
|
||||
If you disable automatic updates, you must still update your runner version regularly. New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software. The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
|
||||
|
||||
@@ -59,7 +59,7 @@ For example:
|
||||
{% windows %}
|
||||
|
||||
```shell
|
||||
run.cmd --check --url <em>https://github.com/octo-org/octo-repo</em> --pat <em>ghp_abcd1234</em>
|
||||
run.cmd --check --url https://github.com/YOUR-ORG/YOUR-REPO --pat GHP_ABCD1234
|
||||
```
|
||||
|
||||
{% endwindows %}
|
||||
@@ -79,7 +79,7 @@ To disable TLS certification verification in the self-hosted runner application,
|
||||
|
||||
```shell
|
||||
export GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY=1
|
||||
./config.sh --url <em>https://github.com/octo-org/octo-repo</em> --token
|
||||
./config.sh --url https://github.com/YOUR-ORG/YOUR-REPO --token
|
||||
./run.sh
|
||||
```
|
||||
|
||||
|
||||
@@ -201,7 +201,7 @@ The `github` context contains information about the workflow run and the event t
|
||||
| `github.ref` | `string` | {% data reusables.actions.ref-description %} |
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
|
||||
| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} |
|
||||
| `github.ref_protected` | `boolean` | {% data reusables.actions.ref_protected-description %} |
|
||||
| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
|
||||
{%- endif %}
|
||||
| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." |
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Finding and customizing actions
|
||||
shortTitle: Finding and customizing actions
|
||||
shortTitle: Find and customize actions
|
||||
intro: 'Actions are the building blocks that power your workflow. A workflow can contain actions created by the community, or you can create your own actions directly within your application''s repository. This guide will show you how to discover, use, and customize actions.'
|
||||
redirect_from:
|
||||
- /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Understanding GitHub Actions
|
||||
shortTitle: Understanding GitHub Actions
|
||||
shortTitle: Understand GitHub Actions
|
||||
intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
@@ -87,15 +87,9 @@ For more information, see "[Creating actions](/actions/creating-actions)."
|
||||
|
||||
{% data reusables.actions.workflow-basic-example-and-explanation %}
|
||||
|
||||
## More complex examples
|
||||
{% data reusables.actions.link-to-example-library %}
|
||||
|
||||
## Next steps
|
||||
|
||||
- To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
- To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)."
|
||||
{% endif %}
|
||||
{% data reusables.actions.onboarding-next-steps %}
|
||||
|
||||
## Contacting support
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Re-running workflows and jobs
|
||||
shortTitle: Re-run workflows and jobs
|
||||
intro: 'You can re-run a workflow run{% ifversion re-run-jobs %}, all failed jobs in a workflow run, or specific jobs in a workflow run{% endif %} up to 30 days after its initial run.'
|
||||
permissions: People with write permissions to a repository can re-run workflows in the repository.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
@@ -48,14 +49,14 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
|
||||
To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em>
|
||||
gh run rerun RUN_ID
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --debug
|
||||
gh run rerun RUN_ID --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
@@ -90,14 +91,14 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
|
||||
To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --failed
|
||||
gh run rerun RUN_ID --failed
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --failed --debug
|
||||
gh run rerun RUN_ID --failed --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
@@ -127,14 +128,14 @@ When you re-run a specific job in a workflow, a new workflow run will start for
|
||||
To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run.
|
||||
|
||||
```shell
|
||||
gh run rerun --job <em>job-id</em>
|
||||
gh run rerun --job JOB_ID
|
||||
```
|
||||
|
||||
{% ifversion debug-reruns %}
|
||||
{% data reusables.actions.enable-debug-logging-cli %}
|
||||
|
||||
```shell
|
||||
gh run rerun --job <em>job-id</em> --debug
|
||||
gh run rerun --job JOB_ID --debug
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Publishing Docker images
|
||||
shortTitle: Publish Docker images
|
||||
intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
|
||||
redirect_from:
|
||||
- /actions/language-and-framework-guides/publishing-docker-images
|
||||
|
||||
@@ -77,21 +77,13 @@ Committing the workflow file to a branch in your repository triggers the `push`
|
||||
|
||||
For example, you can see the list of files in your repository:
|
||||
|
||||
|
||||
|
||||
The example workflow you just added is triggered each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. For an in-depth tutorial, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
|
||||
|
||||
## More starter workflows
|
||||
|
||||
{% data reusables.actions.workflow-template-overview %}
|
||||
|
||||
## More complex examples
|
||||
{% data reusables.actions.link-to-example-library %}
|
||||
|
||||
## Next steps
|
||||
|
||||
The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- Your repository can contain multiple workflows that trigger different jobs based on different events.
|
||||
- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners.
|
||||
|
||||
{% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial.
|
||||
{% data reusables.actions.onboarding-next-steps %}
|
||||
|
||||
@@ -93,13 +93,13 @@ If your repository has environment secrets or can access secrets from the parent
|
||||
To add a repository secret, use the `gh secret set` subcommand. Replace `secret-name` with the name of your secret.
|
||||
|
||||
```shell
|
||||
gh secret set <em>secret-name</em>
|
||||
gh secret set SECRET_NAME
|
||||
```
|
||||
|
||||
The CLI will prompt you to enter a secret value. Alternatively, you can read the value of the secret from a file.
|
||||
|
||||
```shell
|
||||
gh secret set <em>secret-name</em> < secret.txt
|
||||
gh secret set SECRET_NAME < secret.txt
|
||||
```
|
||||
|
||||
To list all secrets for the repository, use the `gh secret list` subcommand.
|
||||
@@ -128,13 +128,13 @@ To list all secrets for the repository, use the `gh secret list` subcommand.
|
||||
To add a secret for an environment, use the `gh secret set` subcommand with the `--env` or `-e` flag followed by the environment name.
|
||||
|
||||
```shell
|
||||
gh secret set --env <em>environment-name</em> <em>secret-name</em>
|
||||
gh secret set --env ENV_NAME SECRET_NAME
|
||||
```
|
||||
|
||||
To list all secrets for an environment, use the `gh secret list` subcommand with the `--env` or `-e` flag followed by the environment name.
|
||||
|
||||
```shell
|
||||
gh secret list --env <em>environment-name</em>
|
||||
gh secret list --env ENV_NAME
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
@@ -173,25 +173,25 @@ gh auth login --scopes "admin:org"
|
||||
To add a secret for an organization, use the `gh secret set` subcommand with the `--org` or `-o` flag followed by the organization name.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em>
|
||||
gh secret set --org ORG_NAME SECRET_NAME
|
||||
```
|
||||
|
||||
By default, the secret is only available to private repositories. To specify that the secret should be available to all repositories within the organization, use the `--visibility` or `-v` flag.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em> --visibility all
|
||||
gh secret set --org ORG_NAME SECRET_NAME --visibility all
|
||||
```
|
||||
|
||||
To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag.
|
||||
|
||||
```shell
|
||||
gh secret set --org <em>organization-name</em> <em>secret-name</em> --repos <em>repo-name-1</em>,<em>repo-name-2</em>"
|
||||
gh secret set --org ORG_NAME SECRET_NAME --repos REPO-NAME-1, REPO-NAME-2"
|
||||
```
|
||||
|
||||
To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name.
|
||||
|
||||
```shell
|
||||
gh secret list --org <em>organization-name</em>
|
||||
gh secret list --org ORG_NAME
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Using larger runners
|
||||
shortTitle: 'Larger runners'
|
||||
intro: '{% data variables.product.prodname_dotcom %} offers larger runners with more RAM and CPU.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
product: '{% data reusables.gated-features.hosted-runners %}'
|
||||
versions:
|
||||
feature: 'actions-hosted-runners'
|
||||
shortTitle: Using {% data variables.actions.hosted_runner %}s
|
||||
---
|
||||
|
||||
## Overview of {% data variables.actions.hosted_runner %}s
|
||||
@@ -87,7 +87,7 @@ You can add a {% data variables.actions.hosted_runner %} to an organization, whe
|
||||
|
||||
## Running jobs on your runner
|
||||
|
||||
Once your runner type has been been defined, you can update your workflows to send jobs to the runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
|
||||
Once your runner type has been defined, you can update your workflow YAML files to send jobs to your newly created runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
|
||||
|
||||
```yaml
|
||||
name: learn-github-actions
|
||||
@@ -104,6 +104,8 @@ jobs:
|
||||
- run: bats -v
|
||||
```
|
||||
|
||||
To find out which runners are enabled for your repository and organization, you must contact your organization admin. Your organization admin can create new runners and runner groups, as well as configure permissions to specify which repositories can access a runner group.
|
||||
|
||||
## Managing access to your runners
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating starter workflows for your organization
|
||||
shortTitle: Creating starter workflows
|
||||
shortTitle: Create starter workflows
|
||||
intro: Learn how you can create starter workflows to help people in your team add new workflows more easily.
|
||||
redirect_from:
|
||||
- /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Reusing workflows
|
||||
shortTitle: Reusing workflows
|
||||
shortTitle: Reuse workflows
|
||||
intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows.
|
||||
redirect_from:
|
||||
- /actions/learn-github-actions/reusing-workflows
|
||||
@@ -105,7 +105,7 @@ You can define inputs and secrets, which can be passed from the caller workflow
|
||||
on:
|
||||
workflow_call:
|
||||
inputs:
|
||||
username:
|
||||
config-path:
|
||||
required: true
|
||||
type: string
|
||||
secrets:
|
||||
@@ -133,10 +133,10 @@ You can define inputs and secrets, which can be passed from the caller workflow
|
||||
runs-on: ubuntu-latest
|
||||
environment: production
|
||||
steps:
|
||||
- uses: octo-org/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.envPAT }}
|
||||
- uses: actions/labeler@v4
|
||||
with:
|
||||
repo-token: ${{ secrets.envPAT }}
|
||||
configuration-path: ${{ inputs.config-path }}
|
||||
```
|
||||
{% endraw %}
|
||||
In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
|
||||
@@ -162,7 +162,7 @@ name: Reusable workflow example
|
||||
on:
|
||||
workflow_call:
|
||||
inputs:
|
||||
username:
|
||||
config-path:
|
||||
required: true
|
||||
type: string
|
||||
secrets:
|
||||
@@ -170,14 +170,13 @@ on:
|
||||
required: true
|
||||
|
||||
jobs:
|
||||
example_job:
|
||||
name: Pass input and secrets to my-action
|
||||
triage:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: octo-org/my-action@v1
|
||||
with:
|
||||
username: ${{ inputs.username }}
|
||||
token: ${{ secrets.token }}
|
||||
- uses: actions/labeler@v4
|
||||
with:
|
||||
repo-token: ${{ secrets.token }}
|
||||
configuration-path: ${{ inputs.config-path }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
@@ -256,7 +255,7 @@ When you call a reusable workflow, you can only use the following keywords in th
|
||||
|
||||
### Example caller workflow
|
||||
|
||||
This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`username`) and a secret (`token`).
|
||||
This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`config-path`) and a secret (`token`).
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -272,11 +271,14 @@ jobs:
|
||||
uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1
|
||||
|
||||
call-workflow-passing-data:
|
||||
permissions:
|
||||
contents: read
|
||||
pull-requests: write
|
||||
uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main
|
||||
with:
|
||||
username: mona
|
||||
config-path: .github/labeler.yml
|
||||
secrets:
|
||||
token: ${{ secrets.TOKEN }}
|
||||
token: ${{ secrets.GITHUB_TOKEN }}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'Sharing workflows, secrets, and runners with your organization'
|
||||
shortTitle: Sharing workflows with your organization
|
||||
shortTitle: Share workflows with your organization
|
||||
intro: 'Learn how you can use organization features to collaborate with your team, by sharing starter workflows, secrets, and self-hosted runners.'
|
||||
redirect_from:
|
||||
- /actions/learn-github-actions/sharing-workflows-with-your-organization
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Triggering a workflow
|
||||
shortTitle: Triggering a workflow
|
||||
shortTitle: Trigger a workflow
|
||||
intro: 'How to automatically trigger {% data variables.product.prodname_actions %} workflows'
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -93,7 +93,7 @@ By default, the rate limit for {% data variables.product.prodname_actions %} is
|
||||
|
||||
```shell
|
||||
ghe-config actions-rate-limiting.enabled true
|
||||
ghe-config actions-rate-limiting.queue-runs-per-minute <em>RUNS-PER-MINUTE</em>
|
||||
ghe-config actions-rate-limiting.queue-runs-per-minute RUNS-PER-MINUTE
|
||||
```
|
||||
1. To disable the rate limit after it's been enabled, run the following command.
|
||||
|
||||
|
||||
@@ -118,7 +118,7 @@ If the upgrade target you're presented with is a feature release instead of a pa
|
||||
{% data reusables.enterprise_installation.download-package %}
|
||||
4. Run the `ghe-upgrade` command using the package file name:
|
||||
```shell
|
||||
admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.hpkg</em>
|
||||
admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.hpkg
|
||||
*** verifying upgrade package signature...
|
||||
```
|
||||
5. If a reboot is required for updates for kernel, MySQL, Elasticsearch or other programs, the hotpatch upgrade script notifies you.
|
||||
@@ -170,14 +170,14 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea
|
||||
|
||||
5. Run the `ghe-upgrade` command using the package file name:
|
||||
```shell
|
||||
admin@<em>HOSTNAME</em>:~$ ghe-upgrade <em>GITHUB-UPGRADE.pkg</em>
|
||||
admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.pkg
|
||||
*** verifying upgrade package signature...
|
||||
```
|
||||
6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode:
|
||||
```shell
|
||||
*** applying update...
|
||||
This package will upgrade your installation to version <em>version-number</em>
|
||||
Current root partition: /dev/xvda1 [<em>version-number</em>]
|
||||
This package will upgrade your installation to version VERSION-NUMBER
|
||||
Current root partition: /dev/xvda1 [VERSION-NUMBER]
|
||||
Target root partition: /dev/xvda2
|
||||
Proceed with installation? [y/N]
|
||||
```
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enterprise の監査ログのストリーミング
|
||||
intro: '監査イベントと Git イベントのデータを {% data variables.product.prodname_dotcom %} から外部のデータ管理システムにストリーミングできます。'
|
||||
title: Streaming the audit log for your enterprise
|
||||
intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: audit-log-streaming
|
||||
@@ -15,34 +15,32 @@ redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
|
||||
- /admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
|
||||
permissions: Enterprise owners can configure audit log streaming.
|
||||
ms.openlocfilehash: 81eb88f760016390a321798589e7994542c9f312
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147710340'
|
||||
---
|
||||
{% ifversion ghes %} {% note %}
|
||||
|
||||
**注:** {% data variables.product.product_name %} の監査ログ ストリーミングは現在、ベータ版であり、変更される可能性があります。
|
||||
{% ifversion ghes %}
|
||||
{% note %}
|
||||
|
||||
{% endnote %} {% endif %}
|
||||
**Note:** Audit log streaming is currently in beta for {% data variables.product.product_name %} and is subject to change.
|
||||
|
||||
## 監査ログのストリーミングについて
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
知的財産を保護し、組織のコンプライアンスを維持するために、ストリーミングを使用して監査ログ データのコピーを保持し、監視できます。{% data reusables.audit_log.audited-data-list %}
|
||||
## About audit log streaming
|
||||
|
||||
監査ログのストリーミングには、次の利点があります。
|
||||
To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor:
|
||||
{% data reusables.audit_log.audited-data-list %}
|
||||
|
||||
* **データの探索**。 大量のデータに対してクエリを実行するために、推奨されるツールを使用して、ストリーミングされたイベントを調べることができます。 ストリーミングには、Enterprise アカウント全体の監査イベントと Git イベントの両方が含まれます。{% ifversion pause-audit-log-stream %}
|
||||
* **データの継続性**。 ストリーミングは、最長 7 日間、監査データを失うことなく一時停止できます。{% endif %}
|
||||
* **データ保有**。 エクスポートされた監査ログと Git イベント データを必要な期間だけ保持できます。
|
||||
The benefits of streaming audit data include:
|
||||
|
||||
Enterprise 所有者は、ストリームをいつでも設定{% ifversion pause-audit-log-stream %}、一時停止、{% endif %}または削除することができます。 ストリーミングによって、Enterprise 内のすべての Organization に関する監査と Git イベント データがエクスポートされます。
|
||||
* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.{% ifversion pause-audit-log-stream %}
|
||||
* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.{% endif %}
|
||||
* **Data retention**. You can keep your exported audit logs and Git events data as long as you need to.
|
||||
|
||||
## 監査ログのストリーミングの設定
|
||||
Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise.
|
||||
|
||||
プロバイダーの指示に従って、{% data variables.product.product_name %} での監査ログのストリーミングを設定します。
|
||||
## Setting up audit log streaming
|
||||
|
||||
You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider.
|
||||
|
||||
- [Amazon S3](#setting-up-streaming-to-amazon-s3)
|
||||
- [Azure Blob Storage](#setting-up-streaming-to-azure-blob-storage)
|
||||
@@ -51,52 +49,49 @@ Enterprise 所有者は、ストリームをいつでも設定{% ifversion pause
|
||||
- [Google Cloud Storage](#setting-up-streaming-to-google-cloud-storage)
|
||||
- [Splunk](#setting-up-streaming-to-splunk)
|
||||
|
||||
### Amazon S3 へのストリーミングの設定
|
||||
|
||||
{% ifversion streaming-oidc-s3 %}アクセス キーを使用して S3 へのストリーミングを設定したり、OpenID Connect (OIDC) を使用して {% data variables.product.product_name %} に有効期間の長いシークレットを格納するのを回避したりできます。
|
||||
|
||||
- [アクセス キーを使用して S3 へのストリーミングを設定する](#setting-up-streaming-to-s3-with-access-keys)
|
||||
- [OpenID Connect を使用して S3 へのストリーミングを設定する](#setting-up-streaming-to-s3-with-openid-connect)
|
||||
- [OpenID Connect を使用して S3 へのストリーミングを無効にする](#disabling-streaming-to-s3-with-openid-connect)
|
||||
|
||||
#### アクセス キーを使用して S3 へのストリーミングを設定する
|
||||
{% endif %}
|
||||
|
||||
監査ログを Amazon の S3 エンドポイントにストリーミングするには、バケットとアクセス キーが必要です。 詳しくは、AWS のドキュメント「[Amazon S3 バケットの作成、設定、操作](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html)」をご覧ください。 必ず、バケットへのパブリック アクセスをブロックして監査ログ情報を保護してください。
|
||||
|
||||
{% data variables.product.prodname_dotcom %} から監査ログのストリーミングを設定するには、次のものが必要です。
|
||||
* Amazon S3 バケットの名前
|
||||
* AWS アクセス キー ID
|
||||
* AWS 秘密鍵
|
||||
|
||||
アクセス キー ID と秘密鍵の作成またはアクセスについては、AWS ドキュメントの「[Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html)」 (AWS 資格情報の理解と取得) を参照してください。
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %} {% data reusables.audit_log.streaming-choose-s3 %}{% ifversion streaming-oidc-s3 %}
|
||||
1. [認証] で **[アクセス キー]** をクリックします。
|
||||
|
||||
{% endif %}
|
||||
1. ストリームの設定を構成します。
|
||||
|
||||
- [バケット] に、ストリーミング先のバケットの名前を入力します。 たとえば、`auditlog-streaming-test` のようにします。
|
||||
- [アクセス キー ID] に、アクセス キーの ID を入力します。 たとえば、`ABCAIOSFODNN7EXAMPLE1` のようにします。
|
||||
- [シークレット キー] に、シークレット キーを入力します。 たとえば、`aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY` のようにします。
|
||||
{% data reusables.audit_log.streaming-check-s3-endpoint %} {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
### Setting up streaming to Amazon S3
|
||||
|
||||
{% ifversion streaming-oidc-s3 %}
|
||||
#### OpenID Connect を使用して S3 へのストリーミングを設定する
|
||||
You can set up streaming to S3 with access keys or, to avoid storing long-lived secrets in {% data variables.product.product_name %}, with OpenID Connect (OIDC).
|
||||
|
||||
{% note %}
|
||||
- [Setting up streaming to S3 with access keys](#setting-up-streaming-to-s3-with-access-keys)
|
||||
- [Setting up streaming to S3 with OpenID Connect](#setting-up-streaming-to-s3-with-openid-connect)
|
||||
- [Disabling streaming to S3 with OpenID Connect](#disabling-streaming-to-s3-with-openid-connect)
|
||||
|
||||
**注:** OpenID Connect を使った Amazon S3 へのストリーミングは、現在ベータ版であり、変更される可能性があります。
|
||||
#### Setting up streaming to S3 with access keys
|
||||
{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the AWS documentation. Make sure to block public access to the bucket to protect your audit log information.
|
||||
|
||||
1. AWS では、{% data variables.product.prodname_dotcom %} の OIDC プロバイダーを IAM に追加します。 詳しくは、AWS のドキュメント「[OpenID Connect (OIDC) ID プロバイダーの作成](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html)」をご覧ください。
|
||||
To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need:
|
||||
* The name of your Amazon S3 bucket
|
||||
* Your AWS access key ID
|
||||
* Your AWS secret key
|
||||
|
||||
- プロバイダーの URL には、`https://oidc-configuration.audit-log.githubusercontent.com` を使います。
|
||||
- [対象者] には、`sts.amazonaws.com` を使います。
|
||||
1. バケットを作成し、バケットへのパブリック アクセスをブロックします。 詳しくは、AWS のドキュメント「[Amazon S3 バケットの作成、設定、操作](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html)」をご覧ください。
|
||||
1. {% data variables.product.company_short %} によるバケットへの書き込みを許可するポリシーを作成します。 {% data variables.product.prodname_dotcom %} には、次のアクセス許可のみが必要です。
|
||||
For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
{% data reusables.audit_log.streaming-choose-s3 %}{% ifversion streaming-oidc-s3 %}
|
||||
1. Under "Authentication", click **Access keys**.
|
||||
|
||||
{% endif %}
|
||||
1. Configure the stream settings.
|
||||
|
||||
- Under "Bucket", type the name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
|
||||
- Under "Access Key ID", type your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
|
||||
- Under "Secret Key", type your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
|
||||
{% data reusables.audit_log.streaming-check-s3-endpoint %}
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
{% ifversion streaming-oidc-s3 %}
|
||||
#### Setting up streaming to S3 with OpenID Connect
|
||||
|
||||
1. In AWS, add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM. For more information, see [Creating OpenID Connect (OIDC) identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) in the AWS documentation.
|
||||
|
||||
- For the provider URL, use `https://oidc-configuration.audit-log.githubusercontent.com`.
|
||||
- For "Audience", use `sts.amazonaws.com`.
|
||||
1. Create a bucket, and block public access to the bucket. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the AWS documentation.
|
||||
1. Create a policy that allows {% data variables.product.company_short %} to write to the bucket. {% data variables.product.prodname_dotcom %} requires only the following permissions.
|
||||
|
||||
```
|
||||
{
|
||||
@@ -113,11 +108,11 @@ Enterprise 所有者は、ストリームをいつでも設定{% ifversion pause
|
||||
]
|
||||
}
|
||||
```
|
||||
詳しくは、AWS のドキュメント「[IAM ポリシーの作成](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html)」をご覧ください。
|
||||
1. {% data variables.product.prodname_dotcom %} IdP のロールと信頼ポリシーを構成します。 詳しくは、AWS のドキュメント「[ウェブ ID または OpenID Connect フェデレーション用のロールを作成する (コンソール)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html)」をご覧ください。
|
||||
For more information, see [Creating IAM policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the AWS documentation.
|
||||
1. Configure the role and trust policy for the {% data variables.product.prodname_dotcom %} IdP. For more information, see [Creating a role for web identity or OpenID Connect Federation (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html) in the AWS documentation.
|
||||
|
||||
- 上で作成したアクセス許可ポリシーを追加して、バケットへの書き込みを許可します。
|
||||
- 信頼関係を編集して、`sub` フィールドを検証条件に追加し、`ENTERPRISE` を自分の Enterprise の名前に置き換えます。
|
||||
- Add the permissions policy you created above to allow writes to the bucket.
|
||||
- Edit the trust relationship to add the `sub` field to the validation conditions, replacing `ENTERPRISE` with the name of your enterprise.
|
||||
```
|
||||
"Condition": {
|
||||
"StringEquals": {
|
||||
@@ -126,209 +121,217 @@ Enterprise 所有者は、ストリームをいつでも設定{% ifversion pause
|
||||
}
|
||||
}
|
||||
```
|
||||
- 作成されたロールの Amazon Resource Name (ARN) を記録しておきます。
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %} {% data reusables.audit_log.streaming-choose-s3 %}
|
||||
1. [認証] の **[OpenID Connect]** をクリックします。
|
||||
- Make note of the Amazon Resource Name (ARN) of the created role.
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
{% data reusables.audit_log.streaming-choose-s3 %}
|
||||
1. Under "Authentication", click **OpenID Connect**.
|
||||
|
||||
|
||||
1. ストリームの設定を構成します。
|
||||
|
||||
1. Configure the stream settings.
|
||||
|
||||
- [バケット] に、ストリーミング先のバケットの名前を入力します。 たとえば、`auditlog-streaming-test` のようにします。
|
||||
- [ARN ロール] に、前に記録した ARN ロールを入力します。 たとえば、`arn:aws::iam::1234567890:role/github-audit-log-streaming-role` のようにします。
|
||||
{% data reusables.audit_log.streaming-check-s3-endpoint %} {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
- Under "Bucket", type the name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
|
||||
- Under "ARN Role" type the ARN role you noted earlier. For example, `arn:aws::iam::1234567890:role/github-audit-log-streaming-role`.
|
||||
{% data reusables.audit_log.streaming-check-s3-endpoint %}
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
#### OpenID Connect を使用して S3 へのストリーミングを無効にする
|
||||
#### Disabling streaming to S3 with OpenID Connect
|
||||
|
||||
OIDC のセキュリティ脆弱性を検出したなど、何らかの理由で OIDC を使用した S3 へのストリーミングを無効にする場合は、ストリーミングの設定時に AWS で作成した {% data variables.product.prodname_dotcom %} OIDC プロバイダーを削除します。 詳しくは、AWS のドキュメント「[OpenID Connect (OIDC) ID プロバイダーの作成](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html)」をご覧ください。
|
||||
If you want to disable streaming to S3 with OIDC for any reason, such as the discovery of a security vulnerability in OIDC, delete the {% data variables.product.prodname_dotcom %} OIDC provider you created in AWS when you set up streaming. For more information, see [Creating OpenID Connect (OIDC) identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) in the AWS documentation.
|
||||
|
||||
その後は、脆弱性が解決されるまで、アクセス キーを使用してストリーミングを設定します。 詳しい情報については、「[アクセス キーを使用して S3 へのストリーミングを設定する](#setting-up-streaming-to-s3-with-access-keys)」を参照してください。
|
||||
Then, set up streaming with access keys until the vulnerability is resolved. For more information, see "[Setting up streaming to S3 with access keys](#setting-up-streaming-to-s3-with-access-keys)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Azure Blob Storage へのストリーミングの設定
|
||||
### Setting up streaming to Azure Blob Storage
|
||||
|
||||
{% data variables.product.prodname_dotcom %} でのストリーミングを設定する前に、まず、Microsoft Azure でストレージ アカウントとコンテナーを作成しておく必要があります。 詳細については、Microsoft のドキュメント「[Azure Blob Storage の概要](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)」を参照してください。
|
||||
Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have created a storage account and a container in Microsoft Azure. For details, see the Microsoft documentation, "[Introduction to Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)."
|
||||
|
||||
{% data variables.product.prodname_dotcom %} でストリーミングを構成するには、SAS トークンの URL が必要です。
|
||||
To configure the stream in {% data variables.product.prodname_dotcom %} you need the URL of a SAS token.
|
||||
|
||||
**Microsoft Azure portal** で次の操作を行います。
|
||||
1. [ホーム] ページで、 **[ストレージ アカウント]** をクリックします。
|
||||
2. 使用するストレージ アカウントの名前をクリックし、 **[コンテナー]** をクリックします。
|
||||
**On Microsoft Azure portal**:
|
||||
1. On the Home page, click **Storage Accounts**.
|
||||
2. Click the name of the storage account you want to use, then click **Containers**.
|
||||
|
||||
![Azure の [コンテナー] リンク](/assets/images/azure/azure-storage-containers.png)
|
||||
|
||||
|
||||
1. 使用するコンテナーの名前をクリックします。
|
||||
1. **[共有アクセス トークン]** をクリックします。
|
||||
1. Click the name of the container you want to use.
|
||||
1. Click **Shared access tokens**.
|
||||
|
||||
![Azure の [共有アクセス トークン] リンク](/assets/images/azure/azure-storage-shared-access-tokens.png)
|
||||
|
||||
|
||||
1. **[アクセス許可]** ドロップダウン メニューで、`Create` と `Write` のみを許可するようにアクセス許可を変更します。
|
||||
1. In the **Permissions** drop-down menu, change the permissions to only allow `Create` and `Write`.
|
||||
|
||||
![[アクセス許可] ドロップダウン メニュー](/assets/images/azure/azure-storage-permissions.png)
|
||||
|
||||
|
||||
1. シークレット ローテーション ポリシーに準拠する有効期限を設定します。
|
||||
1. **[SAS トークンおよび URL を生成]** をクリックします。
|
||||
1. 表示される **BLOB SAS URL** フィールドの値をコピーします。 この URL を {% data variables.product.prodname_dotcom %} で使用します。
|
||||
1. Set an expiry date that complies with your secret rotation policy.
|
||||
1. Click **Generate SAS token and URL**.
|
||||
1. Copy the value of the **Blob SAS URL** field that's displayed. You will use this URL in {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
**{% data variables.product.prodname_dotcom %}** で次の操作を行います。{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. **[Configure stream]** をクリックし、 **[Azure Blob Storage]** を選択します。
|
||||
**On {% data variables.product.prodname_dotcom %}**:
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Configure stream** and select **Azure Blob Storage**.
|
||||
|
||||
![ドロップダウン メニューから [Azure Blob Storage] を選択する](/assets/images/help/enterprises/audit-stream-choice-azureblob.png)
|
||||
|
||||
|
||||
1. 構成ページで、Azure でコピーした BLOB SAS URL を入力します。 **[Container]** フィールドは、その URL に基づいて自動入力されます。
|
||||
1. On the configuration page, enter the blob SAS URL that you copied in Azure. The **Container** field is auto-filled based on the URL.
|
||||
|
||||
|
||||
|
||||
|
||||
1. **[Check endpoint]** をクリックして、{% data variables.product.prodname_dotcom %} で Azure Blob Storage エンドポイントに接続して書き込むことができることを確認します。
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
### Azure Event Hubs へのストリーミングの設定
|
||||
### Setting up streaming to Azure Event Hubs
|
||||
|
||||
{% data variables.product.prodname_dotcom %} でのストリーミングを設定する前に、まず、Microsoft Azure でイベント ハブ名前空間が必要です。 次に、その名前空間内にイベント ハブ インスタンスを作成する必要があります。 ストリーミングを設定するときに、このイベント ハブ インスタンスの詳細が必要になります。 詳細については、Microsoft のドキュメント「[クイック スタート:Azure portal を使用したイベント ハブの作成](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)」を参照してください。
|
||||
Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)."
|
||||
|
||||
イベント ハブに関する 2 つの情報 (インスタント名と接続文字列) が必要です。
|
||||
You need two pieces of information about your event hub: its instance name and the connection string.
|
||||
|
||||
**Microsoft Azure portal** で次の操作を行います。
|
||||
1. 「Event Hubs」を検索します。
|
||||
**On Microsoft Azure portal**:
|
||||
1. Search for "Event Hubs".
|
||||
|
||||
|
||||
|
||||
|
||||
1. **[Event Hubs]** を選択します。 イベント ハブの名前が一覧表示されます。
|
||||
1. Select **Event Hubs**. The names of your event hubs are listed.
|
||||
|
||||
|
||||
|
||||
|
||||
1. ストリーミング先のイベント ハブの名前をメモします。
|
||||
1. 必要なイベント ハブをクリックします。 次に、左側のメニューで、 **[共有アクセスポリシー]** を選択します。
|
||||
1. ポリシーの一覧で共有アクセス ポリシーを選択するか、新しいポリシーを作成します。
|
||||
1. Make a note of the name of the event hub you want to stream to.
|
||||
1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
|
||||
1. Select a shared access policy in the list of policies, or create a new policy.
|
||||
|
||||
|
||||
|
||||
|
||||
1. **[接続文字列 – 主キー]** フィールドの右側にあるボタンをクリックして、接続文字列をコピーします。
|
||||
1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
|
||||
|
||||
|
||||
|
||||
|
||||
**{% data variables.product.prodname_dotcom %}** で次の操作を行います。{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. **[Configure stream]** をクリックし、 **[Azure Event Hubs]** を選択します。
|
||||
**On {% data variables.product.prodname_dotcom %}**:
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Configure stream** and select **Azure Event Hubs**.
|
||||
|
||||
![ドロップダウン メニューから [Azure Events Hubs] を選択する](/assets/images/help/enterprises/audit-stream-choice-azure.png)
|
||||
|
||||
|
||||
1. 構成ページで、次の項目を入力します。
|
||||
* Azure Event Hubs インスタンスの名前。
|
||||
* 接続文字列。
|
||||
1. On the configuration page, enter:
|
||||
* The name of the Azure Event Hubs instance.
|
||||
* The connection string.
|
||||
|
||||
|
||||
|
||||
|
||||
1. **[Check endpoint]** をクリックして、{% data variables.product.prodname_dotcom %} で Azure Events Hubs エンドポイントに接続して書き込むことができることを確認します。
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
{% ifversion streaming-datadog %}
|
||||
### Datadog へのストリーミングの設定
|
||||
### Setting up streaming to Datadog
|
||||
|
||||
Datadog へのストリーミングを設定するには、Datadog でクライアント トークンまたは API キーを作成し、次に認証用のトークンを使用して {% data variables.product.product_name %} で監査ログ ストリーミングを構成する必要があります。 Datadog でバケットやその他のストレージ コンテナーを作成する必要はありません。
|
||||
To set up streaming to Datadog, you must create a client token or an API key in Datadog, then configure audit log streaming in {% data variables.product.product_name %} using the token for authentication. You do not need to create a bucket or other storage container in Datadog.
|
||||
|
||||
Datadog へのストリーミングを設定した後は、"github.audit.streaming" でフィルター処理することで自分の監査ログ データを確認できます。 詳しくは、「[ログ管理](https://docs.datadoghq.com/logs/)」を参照してください。
|
||||
After you set up streaming to Datadog, you can see your audit log data by filtering by "github.audit.streaming." For more information, see [Log Management](https://docs.datadoghq.com/logs/).
|
||||
|
||||
1. まだ Datadog アカウントがない場合は、それを作成します。
|
||||
1. Datadog で、クライアント トークンまたは API キーを生成して、 **[キーのコピー]** をクリックします。 詳しくは、Datadog Docs の「[API キーとアプリケーション キー](https://docs.datadoghq.com/account_management/api-app-keys/)」を参照してください。 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. **[ストリームの構成]** ドロップダウンを選び、 **[Datadog]** をクリックします。
|
||||
1. If you don't already have a Datadog account, create one.
|
||||
1. In Datadog, generate a client token or an API key, then click **Copy key**. For more information, see [API and Application Keys](https://docs.datadoghq.com/account_management/api-app-keys/) in Datadog Docs.
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Select the **Configure stream** dropdown menu and click **Datadog**.
|
||||
|
||||
![[Datadog] が強調表示された [ストリームの構成] ドロップダウン メニューのスクリーンショット](/assets/images/help/enterprises/audit-stream-choice-datadog.png)
|
||||
1. [トークン] の下に、先ほどコピーしたトークンを貼り付けます。
|
||||
|
||||
1. Under "Token", paste the token you copied earlier.
|
||||
|
||||
![[トークン] フィールドのスクリーンショット](/assets/images/help/enterprises/audit-stream-datadog-token.png)
|
||||
1. [サイト] ドロップダウン メニューを選び、Datadog サイトをクリックします。 ご利用の Datadog サイトを特定するには、その Datadog の URL を Datadog Docs にある [Datadog サイト](https://docs.datadoghq.com/getting_started/site/) 内のテーブルと比較します。
|
||||
|
||||
1. Select the "Site" dropdown menu and click your Datadog site. To determine your Datadog site, compare your Datadog URL to the table in [Datadog sites](https://docs.datadoghq.com/getting_started/site/) in Datadog Docs.
|
||||
|
||||
![[サイト] ドロップダウン メニューのスクリーンショット](/assets/images/help/enterprises/audit-stream-datadog-site.png)
|
||||
1. {% data variables.product.prodname_dotcom %} で Datadog エンドポイントに接続して書き込みができることを確認するには、 **[エンドポイントのチェック]** をクリックします。
|
||||
|
||||
1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Datadog endpoint, click **Check endpoint**.
|
||||
|
||||
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
1. 数分後、Datadog の **[ログ]** タブに監査ログ データが表示されていることを確認します。 監査ログ データが表示されない場合は、トークンとサイトが正しいことを {% data variables.product.prodname_dotcom %} で確認します。
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
1. After a few minutes, confirm that audit log data is appearing on the **Logs** tab in Datadog. If audit log data is not appearing, confirm that your token and site are correct in {% data variables.product.prodname_dotcom %}.
|
||||
{% endif %}
|
||||
|
||||
### Google Cloud Storage へのストリーミングの設定
|
||||
### Setting up streaming to Google Cloud Storage
|
||||
|
||||
Google Cloud Storage へのストリーミングを設定するには、適切な資格情報とアクセス許可を使用して、Google Cloud にサービス アカウントを作成し、そのサービス アカウントの資格情報を認証に使用して {% data variables.product.product_name %} での監査ログのストリーミングを構成します。
|
||||
To set up streaming to Google Cloud Storage, you must create a service account in Google Cloud with the appropriate credentials and permissions, then configure audit log streaming in {% data variables.product.product_name %} using the service account's credentials for authentication.
|
||||
|
||||
1. Google Cloud のサービス アカウントを作成します。 サービス アカウントのアクセス制御または IAM ロールを設定する必要はありません。 詳細については、Google Cloud のドキュメント「[サービス アカウントの作成と管理](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating)」を参照してください。
|
||||
1. サービス アカウントの JSON キーを作成し、キーを安全に格納します。 詳細については、Google Cloud のドキュメント「[サービス アカウント キーの作成と管理](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating)」を参照してください。
|
||||
1. バケットをまだ作成していない場合は、作成します。 詳細については、Google Cloud のドキュメント「[ストレージ バケットの作成](https://cloud.google.com/storage/docs/creating-buckets)」を参照してください。
|
||||
1. バケットのストレージ オブジェクト作成者のロールをサービス アカウントに付与します。 詳細については、Google Cloud のドキュメント「[クラウド IAM 権限を使用する](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add)」を参照してください。
|
||||
1. Create a service account for Google Cloud. You do not need to set access controls or IAM roles for the service account. For more information, see [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating) in the Google Cloud documentation.
|
||||
1. Create a JSON key for the service account, and store the key securely. For more information, see [Creating and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating) in the Google Cloud documentation.
|
||||
1. If you haven't created a bucket yet, create the bucket. For more information, see [Creating storage buckets](https://cloud.google.com/storage/docs/creating-buckets) in the Google Cloud documentation.
|
||||
1. Give the service account the Storage Object Creator role for the bucket. For more information, see [Using Cloud IAM permissions](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add) in the Google Cloud documentation.
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. [Configure stream] ドロップダウン メニューを選択し、 **[Google Cloud Storage]** をクリックします。
|
||||
1. Select the Configure stream drop-down menu and click **Google Cloud Storage**.
|
||||
|
||||
![[Configure stream] ドロップダウン メニューのスクリーンショット](/assets/images/help/enterprises/audit-stream-choice-google-cloud-storage.png)
|
||||
|
||||
|
||||
1. [Bucket] で、Google Cloud Storage バケットの名前を入力します。
|
||||
1. Under "Bucket", type the name of your Google Cloud Storage bucket.
|
||||
|
||||
![[Bucket] テキスト フィールドのスクリーンショット](/assets/images/help/enterprises/audit-stream-bucket-google-cloud-storage.png)
|
||||
|
||||
|
||||
1. [JSON Credentials] で、サービス アカウントの JSON キーのファイルの内容全体を貼り付けます。
|
||||
1. Under "JSON Credentials", paste the entire contents of the file for your service account's JSON key.
|
||||
|
||||
![[JSON Credentials] テキスト フィールドのスクリーンショット](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png)
|
||||
|
||||
|
||||
1. {% data variables.product.prodname_dotcom %} で Google Cloud Storage バケットに接続して書き込めることを確認するには、 **[Check endpoint]** をクリックします。
|
||||
1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**.
|
||||
|
||||
![[Check endpoint] ボタンのスクリーンショット](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png)
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
### Splunk へのストリーミングの設定
|
||||
### Setting up streaming to Splunk
|
||||
|
||||
監査ログを Splunk の HTTP Event Collector (HEC) エンドポイントにストリーミングするには、エンドポイントが HTTPS 接続を受け入れるように構成されていることを確認する必要があります。 詳細については、Splunk のドキュメント「[Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector)」 (Splunk Web で HTTP Event Collector を設定および作成する) を参照してください。
|
||||
To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. **[Configure stream]** をクリックし、 **[Splunk]** を選択します。
|
||||
1. Click **Configure stream** and select **Splunk**.
|
||||
|
||||
![ドロップダウン メニューから [Splunk] を選択する](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
|
||||
|
||||
|
||||
1. 構成ページで、次の項目を入力します。
|
||||
* ストリーミング先のアプリケーションがホストされているドメイン。
|
||||
1. On the configuration page, enter:
|
||||
* The domain on which the application you want to stream to is hosted.
|
||||
|
||||
Splunk Cloud を使用している場合、`Domain` は `http-inputs-<host>` である必要があります。ここで、`host` は、Splunk Cloud で使用するドメインです。 (例: `http-inputs-mycompany.splunkcloud.com`)。
|
||||
If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. For example: `http-inputs-mycompany.splunkcloud.com`.
|
||||
|
||||
* アプリケーションでデータを受け入れるポート。<br>
|
||||
* The port on which the application accepts data.<br>
|
||||
|
||||
Splunk Cloud を使用していて、ポート構成を変更していない場合、`Port` は `443` である必要があります。 Splunk Cloud の無料試用版を使用している場合、`Port` は `8088` である必要があります。
|
||||
If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
|
||||
|
||||
* {% data variables.product.prodname_dotcom %} でサードパーティ アプリケーションに対する認証に使用できるトークン。
|
||||
* A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
|
||||
|
||||
|
||||
|
||||
|
||||
1. **[Enable SSL verification]** チェック ボックスはオンのままにします。
|
||||
1. Leave the **Enable SSL verification** check box selected.
|
||||
|
||||
監査ログは常に、暗号化されたデータとしてストリーミングされます。ただし、このオプションを選択すると、{% data variables.product.prodname_dotcom %} によって、イベントの配信前に Splunk インスタンスの SSL 証明書が検証されます。 SSL 検証は、イベントが URL エンドポイントに安全に配信されることを保証するために役立ちます。 このオプションの選択をオフにすることはできますが、SSL 検証を有効のままにすることをお勧めします。
|
||||
1. **[Check endpoint]** をクリックして、{% data variables.product.prodname_dotcom %} で Splunk エンドポイントに接続して書き込むことができることを確認します。
|
||||
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint.
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
{% ifversion pause-audit-log-stream %}
|
||||
## 監査ログのストリーミングの一時停止
|
||||
## Pausing audit log streaming
|
||||
|
||||
ストリーミングを一時停止すると、監査ログ データを失うことなく、受信側のアプリケーションでメンテナンスを実行できます。 監査ログは、最長 7 日間 {% data variables.product.product_location %} に格納され、ストリーミングの一時停止を解除するとエクスポートされます。
|
||||
Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
|
||||
|
||||
{% ifversion streaming-datadog %} Datadog で受け入れるログは過去 18 時間以降のものに限られます。 Datadog エンドポイントへのストリームを 18 時間以上一時停止した場合、ストリーミングを再開した後に Datadog で受け入れられないログが失われるリスクがあります。
|
||||
{% ifversion streaming-datadog %}
|
||||
Datadog only accepts logs from up to 18 hours in the past. If you pause a stream to a Datadog endpoint for more than 18 hours, you risk losing logs that Datadog won't accept after you resume streaming.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. **[Pause stream]** をクリックします。
|
||||
1. Click **Pause stream**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. 確認メッセージが表示されます。 **[Pause stream]** をクリックして確定します。
|
||||
1. A confirmation message is displayed. Click **Pause stream** to confirm.
|
||||
|
||||
アプリケーションが、監査ログを再び受信できるようになったら、 **[Resume stream]** をクリックして監査ログのストリーミングを再開します。
|
||||
When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
|
||||
{% endif %}
|
||||
|
||||
## 監査ログのストリーミングの削除
|
||||
## Deleting the audit log stream
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. **[Delete stream]** をクリックします。
|
||||
1. Click **Delete stream**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. 確認メッセージが表示されます。 **[Delete stream]** をクリックして確定します。
|
||||
1. A confirmation message is displayed. Click **Delete stream** to confirm.
|
||||
|
||||
@@ -121,7 +121,7 @@ For more information about the audit log REST API, see "[Enterprise administrati
|
||||
The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination):
|
||||
|
||||
```shell
|
||||
curl -H "Authorization: Bearer <em>TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100"
|
||||
```
|
||||
@@ -133,7 +133,7 @@ You can specify multiple search phrases, such as `created` and `actor`, by separ
|
||||
The query below searches for audit log events for pull requests, where the event occurred on or after Jan 1st, 2022 in the `avocado-corp` enterprise, and the action was performed by the `octocat` user:
|
||||
|
||||
```shell
|
||||
curl -H "Authorization: Bearer <em>TOKEN</em>" \
|
||||
curl -H "Authorization: Bearer TOKEN" \
|
||||
--request GET \
|
||||
"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
|
||||
```
|
||||
|
||||
@@ -44,17 +44,19 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
{%- ifversion ghae %}
|
||||
<!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
|
||||
```shell
|
||||
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
|
||||
$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
|
||||
|
||||
```
|
||||
{%- else %}
|
||||
```shell
|
||||
$ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t ed25519 -C "your_email@example.com"
|
||||
```
|
||||
{% note %}
|
||||
|
||||
**Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
|
||||
```shell
|
||||
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
|
||||
```
|
||||
|
||||
{% endnote %}
|
||||
@@ -62,14 +64,14 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
|
||||
This creates a new SSH key, using the provided email as a label.
|
||||
```shell
|
||||
> Generating public/private <em>algorithm</em> key pair.
|
||||
> Generating public/private ALGORITHM key pair.
|
||||
```
|
||||
3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
|
||||
|
||||
{% mac %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/Users/YOU/.ssh/id_ALGORITHM: [Press enter]
|
||||
```
|
||||
|
||||
{% endmac %}
|
||||
@@ -77,7 +79,7 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
{% windows %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/c/Users/YOU/.ssh/id_ALGORITHM):[Press enter]
|
||||
```
|
||||
|
||||
{% endwindows %}
|
||||
@@ -85,15 +87,15 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
{% linux %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/home/YOU/.ssh/ALGORITHM):[Press enter]
|
||||
```
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
|
||||
```shell
|
||||
> Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
|
||||
> Enter same passphrase again: <em>[Type passphrase again]</em>
|
||||
> Enter passphrase (empty for no passphrase): [Type a passphrase]
|
||||
> Enter same passphrase again: [Type passphrase again]
|
||||
```
|
||||
|
||||
## Adding your SSH key to the ssh-agent
|
||||
@@ -110,7 +112,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
|
||||
|
||||
```shell
|
||||
$ open ~/.ssh/config
|
||||
> The file /Users/<em>you</em>/.ssh/config does not exist.
|
||||
> The file /Users/YOU/.ssh/config does not exist.
|
||||
```
|
||||
|
||||
* If the file doesn't exist, create the file.
|
||||
@@ -198,7 +200,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
|
||||
```shell
|
||||
$ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "YOUR_EMAIL"
|
||||
```
|
||||
|
||||
{%- ifversion not ghae %}
|
||||
@@ -217,7 +219,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
{% mac %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/Users/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter]
|
||||
```
|
||||
|
||||
{% endmac %}
|
||||
@@ -225,7 +227,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
{% windows %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/c/Users/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter]
|
||||
```
|
||||
|
||||
{% endwindows %}
|
||||
@@ -233,14 +235,14 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
{% linux %}
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
|
||||
> Enter a file in which to save the key (/home/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter]
|
||||
```
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
6. When you are prompted to type a passphrase, press **Enter**.
|
||||
```shell
|
||||
> Enter passphrase (empty for no passphrase): <em>[Type a passphrase]</em>
|
||||
> Enter same passphrase again: <em>[Type passphrase again]</em>
|
||||
> Enter passphrase (empty for no passphrase): [Type a passphrase]
|
||||
> Enter same passphrase again: [Type passphrase again]
|
||||
```
|
||||
7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Dependabot アラートの通知を構成する
|
||||
title: Configuring notifications for Dependabot alerts
|
||||
shortTitle: Configure notifications
|
||||
intro: '{% data variables.product.prodname_dependabot_alerts %} に関する通知の受信方法を最適化する'
|
||||
intro: 'Optimize how you receive notifications about {% data variables.product.prodname_dependabot_alerts %}.'
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
|
||||
- /code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies
|
||||
@@ -19,50 +19,51 @@ topics:
|
||||
- Vulnerabilities
|
||||
- Dependencies
|
||||
- Repositories
|
||||
ms.openlocfilehash: b8810c27a10302a7873fc61a32189f33855140bb
|
||||
ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147878560'
|
||||
---
|
||||
## {% data variables.product.prodname_dependabot_alerts %} の通知について
|
||||
|
||||
{% data variables.product.prodname_dependabot %} でリポジトリ中に脆弱性のある依存関係{% ifversion GH-advisory-db-supports-malware %}またはマルウェア{% endif %}を検出すると、{% data variables.product.prodname_dependabot %} アラートが生成され、そのリポジトリの [Security]\(セキュリティ\) タブに表示されます。 {% data variables.product.product_name %} では、影響を受けるリポジトリのメンテナーに、その通知設定に従って新しいアラートに関する通知が行われます。{% ifversion fpt or ghec %} {% data variables.product.prodname_dependabot %} は、すべてのパブリック リポジトリでデフォルトで有効化されています。 {% data variables.product.prodname_dependabot_alerts %} の場合、デフォルト設定では、特定の脆弱性ごとにグループ化された {% data variables.product.prodname_dependabot_alerts %} をメールで受信します。
|
||||
## About notifications for {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% ifversion fpt or ghec %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 また、新しく作成されたリポジトリに対して {% data variables.product.prodname_dependabot_alerts %} を有効にするか無効にするかを設定することもできます。 詳細については、「[Managing security and analysis settings for your organization (組織のセキュリティと分析の設定を管理する)](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)」を参照してください。
|
||||
{% ifversion fpt or ghec %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether {% data variables.product.prodname_dependabot_alerts %} will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}デフォルトでは、Enterprise のオーナーが Enterprise での通知のためのメールを設定していれば、あなたはメールで {% data variables.product.prodname_dependabot_alerts %} を受け取ることになります。
|
||||
{% ifversion ghes or ghae %}
|
||||
By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.
|
||||
|
||||
Enterprise のオーナーは、通知なしで {% data variables.product.prodname_dependabot_alerts %} を有効にすることもできます。 詳細については、「[エンタープライズでの {% data variables.product.prodname_dependabot %} の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。
|
||||
Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_dependabot_alerts %}の通知設定
|
||||
## Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}新しい {% data variables.product.prodname_dependabot %} のアラートが検出されると、{% data variables.product.product_name %} によって、通知の設定に従って、リポジトリについて {% data variables.product.prodname_dependabot_alerts %} にアクセスできるすべてのユーザーに通知されます。 あなたがリポジトリを監視しており、セキュリティ アラートまたはリポジトリ上のすべてのアクティビティの通知を有効にしていて、リポジトリを無視していない場合は、アラートが通知されます。 詳細については、「[通知の設定](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)」を参照してください。
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_alerts %} for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, and are not ignoring the repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
|
||||
{% endif %}
|
||||
|
||||
各ページの上部に表示される [Manage notifications] ドロップダウン {% octicon "bell" aria-label="The notifications bell" %} から、自分または Organization の通知設定を構成できます。 詳細については、「[通知の設定](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)」を参照してください。
|
||||
You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
|
||||
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} {% data reusables.notifications.vulnerable-dependency-notification-options %}
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %}
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-options %}
|
||||
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** {% data variables.product.company_short %} で通知をフィルター処理して、{% data variables.product.prodname_dependabot_alerts %} を表示できます。 詳細については、「[受信トレイからの通知の管理](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)」を参照してください。
|
||||
**Note:** You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.repositories.security-alerts-x-github-severity %} 詳しくは、[通知の構成](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)に関するページをご覧ください。
|
||||
{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
|
||||
|
||||
## {% data variables.product.prodname_dependabot_alerts %} の通知によるノイズを軽減する方法
|
||||
## How to reduce the noise from notifications for {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %}の通知をあまりに多く受け取ることが心配なら、週次のメールダイジェストにオプトインするか、{% data variables.product.prodname_dependabot_alerts %}を有効化したままで通知をオフにすることをおすすめします。 引き続き移動して、リポジトリの [セキュリティ] タブに {% data variables.product.prodname_dependabot_alerts %} を表示することができます。詳しくは、「[{% data variables.product.prodname_dependabot_alerts %}の表示と更新](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)」を参照してください。
|
||||
If you are concerned about receiving too many notifications for {% data variables.product.prodname_dependabot_alerts %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% data variables.product.prodname_dependabot_alerts %} enabled. You can still navigate to see your {% data variables.product.prodname_dependabot_alerts %} in your repository's Security tab. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- 「[通知の構成](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)」
|
||||
- 「[インボックスからの通知を管理する](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)」
|
||||
- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
|
||||
- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
|
||||
|
||||
@@ -33,6 +33,12 @@ You must store this file in the `.github` directory of your repository. When you
|
||||
|
||||
Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You cannot configure {% data variables.product.prodname_dependabot_alerts %} using the *dependabot.yml* file.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
The *dependabot.yml* file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key{% ifversion ghes = 3.5 %} and/or a `enable-beta-ecosystems` key{% endif %}. The file must start with `version: 2`.
|
||||
|
||||
## Configuration options for the *dependabot.yml* file
|
||||
|
||||
@@ -116,7 +116,7 @@ For more information, see "[Managing security and analysis settings for your org
|
||||
|
||||
## Configuring {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors
|
||||
{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors.
|
||||
|
||||
{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally use {% data variables.product.prodname_code_scanning %} for private and internal repositories.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
|
||||
|
||||
|
||||
@@ -42,9 +42,9 @@ While {% data variables.product.prodname_github_codespaces %} provides the benef
|
||||
|
||||
While this option does not configure a development environment for you, it will allow you to make changes to your source code as needed while you wait for the service disruption to resolve.
|
||||
|
||||
## Option 4: Use Remote-Containers and Docker for a local containerized environment
|
||||
## Option 4: Use the Dev Containers extension and Docker for a local containerized environment
|
||||
|
||||
If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup.
|
||||
If your repository has a `devcontainer.json`, consider using the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup. For more information, see "[Developing inside a container](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -79,4 +79,4 @@ For more information on deleting a codespace, see "[Deleting a codespace](/codes
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} is a cloud-based development environment and requires an internet connection. If you lose connection to the internet while working in a codespace, you will not be able to access your codespace. However, any uncommitted changes will be saved. When you have access to an internet connection again, you can connect to your codespace in the exact same state that it was left in. If you have an unstable internet connection, you should commit and push your changes often.
|
||||
|
||||
If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["{% data variables.product.prodname_vscode %} Remote - Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
If you know that you will often be working offline, you can use your `devcontainer.json` file with the ["Dev Containers" extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) for {% data variables.product.prodname_vscode_shortname %} to build and attach to a local development container for your repository. For more information, see [Developing inside a container](https://code.visualstudio.com/docs/remote/containers) in the {% data variables.product.prodname_vscode %} documentation.
|
||||
|
||||
@@ -73,6 +73,8 @@ Organization owners can specify who can create and use codespaces at the organiz
|
||||
|
||||
|
||||
|
||||
If codespaces for this repository are billable, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
|
||||
|
||||
1. Create your codespace, either using the default options, or after configuring advanced options:
|
||||
|
||||
* **Use the default options**
|
||||
@@ -131,12 +133,12 @@ To create a new codespace, use the `gh codespace create` subcommand.
|
||||
gh codespace create
|
||||
```
|
||||
|
||||
You are prompted to choose a repository, a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
|
||||
You are prompted to choose a repository. If codespaces for this repository are billable, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
|
||||
|
||||
Alternatively, you can use flags to specify some or all of the options:
|
||||
|
||||
```shell
|
||||
gh codespace create -r <em>owner</em>/<em>repo</em> -b <em>branch</em> --devcontainer-path <em>path</em> -m <em>machine-type</em>
|
||||
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
|
||||
```
|
||||
|
||||
In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
|
||||
|
||||
@@ -78,7 +78,7 @@ By default, {% data variables.product.prodname_github_codespaces %} forwards por
|
||||
To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
|
||||
|
||||
```shell
|
||||
gh codespace ports forward <em>codespace-port</em>:<em>local-port</em>
|
||||
gh codespace ports forward CODESPACE-PORT:LOCAL-PORT
|
||||
```
|
||||
|
||||
For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
|
||||
@@ -132,7 +132,7 @@ To change the visibility of a forwarded port, use the `gh codespace ports visibi
|
||||
Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility <em>codespace-port</em>:<em>setting</em>
|
||||
gh codespace ports visibility CODESPACE-PORT:SETTINGS
|
||||
```
|
||||
|
||||
You can set the visibility for multiple ports with one command. For example:
|
||||
|
||||
@@ -62,7 +62,7 @@ For a complete reference of `gh` commands for {% data variables.product.prodname
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The `-c <em>codespace-name</em>` flag, used with many commands, is optional. If you omit it a list of codespaces is displayed for you to choose from.
|
||||
**Note**: The `-c CODESPACE_NAME` flag, used with many commands, is optional. If you omit it a list of codespaces is displayed for you to choose from.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -77,7 +77,7 @@ The list includes the unique name of each codespace, which you can use in other
|
||||
### Create a new codespace
|
||||
|
||||
```shell
|
||||
gh codespace create -r <em>owner/repository</em> [-b <em>branch</em>]
|
||||
gh codespace create -r OWNER/REPO_NAME [-b BRANCH]
|
||||
```
|
||||
|
||||
For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."
|
||||
@@ -85,7 +85,7 @@ For more information, see "[Creating a codespace](/codespaces/developing-in-code
|
||||
### Stop a codespace
|
||||
|
||||
```shell
|
||||
gh codespace stop -c <em>codespace-name</em>
|
||||
gh codespace stop -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)."
|
||||
@@ -93,7 +93,7 @@ For more information, see "[Deep dive into {% data variables.product.prodname_gi
|
||||
### Delete a codespace
|
||||
|
||||
```shell
|
||||
gh codespace delete -c <em>codespace-name</em>
|
||||
gh codespace delete -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
@@ -103,7 +103,7 @@ For more information, see "[Deleting a codespace](/codespaces/developing-in-code
|
||||
To run commands on the remote codespace machine, from your terminal, you can SSH into the codespace.
|
||||
|
||||
```shell
|
||||
gh codespace ssh -c <em>codespace-name</em>
|
||||
gh codespace ssh -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} copies your GitHub SSH keys into the codespace on creation for a seamless authentication experience. You may be asked to enter the passphrase for your SSH key, after which you will get a command prompt from the remote codespace machine.
|
||||
@@ -113,7 +113,7 @@ If you don't have any SSH keys, follow the instructions in "[Generating a new SS
|
||||
### Open a codespace in {% data variables.product.prodname_vscode %}
|
||||
|
||||
```shell
|
||||
gh codespace code -c <em>codespace-name</em>
|
||||
gh codespace code -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code)."
|
||||
@@ -121,13 +121,13 @@ For more information, see "[Using {% data variables.product.prodname_github_code
|
||||
### Open a codespace in JupyterLab
|
||||
|
||||
```shell
|
||||
gh codespace jupyter -c <em>codespace-name</em>
|
||||
gh codespace jupyter -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
### Copy a file to/from a codespace
|
||||
|
||||
```shell
|
||||
gh codespace cp [-r] <em>source(s)</em> <em>destination</em>
|
||||
gh codespace cp [-r] SOURCE(S) DESTINATION
|
||||
```
|
||||
|
||||
Use the prefix `remote:` on a file or directory name to indicate that it's on the codespace. As with the UNIX `cp` command, the first argument specifies the source and the last specifies the destination. If the destination is a directory, you can specify multiple sources. Use the `-r` (recursive) flag if any of the sources is a directory.
|
||||
@@ -171,7 +171,7 @@ For more information about the `gh codespace cp` command, including additional f
|
||||
You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>Control</kbd>+<kbd>C</kbd>.
|
||||
|
||||
```shell
|
||||
gh codespace ports forward <em>codespace-port-number</em>:<em>local-port-number</em> -c <em>codespace-name</em>
|
||||
gh codespace ports forward CODESPACE-PORT_NAME:LOCAL-PORT-NAME -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
To see details of forwarded ports enter `gh codespace ports` and then choose a codespace.
|
||||
@@ -179,13 +179,13 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
|
||||
You can set the visibility of a forwarded port. {% data reusables.codespaces.port-visibility-settings %}
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility <em>codespace-port</em>:<em>private|org|public</em> -c <em>codespace-name</em>
|
||||
gh codespace ports visibility CODESPACE-PORT:private|org|public -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
You can set the visibility for multiple ports with one command. For example:
|
||||
|
||||
```shell
|
||||
gh codespace ports visibility 80:private 3000:public 3306:org -c <em>codespace-name</em>
|
||||
gh codespace ports visibility 80:private 3000:public 3306:org -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
|
||||
@@ -195,7 +195,7 @@ For more information, see "[Forwarding ports in your codespace](/codespaces/deve
|
||||
You can see the creation log for a codespace. After entering this command you will be asked to enter the passphrase for your SSH key.
|
||||
|
||||
```shell
|
||||
gh codespace logs -c <em>codespace-name</em>
|
||||
gh codespace logs -c CODESPACE-NAME
|
||||
```
|
||||
|
||||
For more information about the creation log, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs#creation-logs)."
|
||||
|
||||
@@ -41,3 +41,5 @@ You can also personalize aspects of your codespace environment by using a public
|
||||
For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
|
||||
@@ -27,9 +27,7 @@ Before you can configure prebuilds for your project the following must be true:
|
||||
|
||||
## Configuring a prebuild
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. In the "Code & automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}**.
|
||||
{% data reusables.codespaces.accessing-prebuild-configuration %}
|
||||
1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
|
||||
|
||||
|
||||
@@ -80,6 +78,12 @@ Before you can configure prebuilds for your project the following must be true:
|
||||
|
||||
|
||||
|
||||
1. Optionally, at the bottom of the page, click **Show advanced options**.
|
||||
|
||||
|
||||
|
||||
In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
|
||||
|
||||
1. Click **Create**.
|
||||
|
||||
{% data reusables.codespaces.prebuilds-permission-authorization %}
|
||||
|
||||
@@ -126,7 +126,7 @@ You can choose from a list of predefined configurations to create a dev containe
|
||||
|
||||
Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. For more information about the definitions of predefined dev containers, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) repository.
|
||||
|
||||
You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Remote - Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar.
|
||||
You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Dev Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar.
|
||||
|
||||
{% data reusables.codespaces.command-palette-container %}
|
||||
1. Click the definition you want to use.
|
||||
|
||||
@@ -30,6 +30,38 @@ If you create a codespace and it does not open:
|
||||
|
||||
If you still cannot create a codespace for a repository where {% data variables.product.prodname_github_codespaces %} is available, {% data reusables.codespaces.contact-support %}
|
||||
|
||||
### Codespace creation fails
|
||||
|
||||
If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is cancelled and codespace creation will fail.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** A codespace that was not successfully created is never going to be usable and should be deleted. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you create a codespace and the creation fails:
|
||||
|
||||
1. Check {% data variables.product.prodname_dotcom %}'s [Status page](https://githubstatus.com) for any active incidents.
|
||||
1. Go to [your {% data variables.product.prodname_github_codespaces %} page](https://github.com/codespaces), delete the codespace, and create a new codespace.
|
||||
1. If the container is building, look at the logs that are streaming and make sure the build is not stuck. A container build that takes longer than one hour will be canceled, resulting in a failed creation.
|
||||
|
||||
One common scenario where this could happen is if you have a script running that is prompting for user input and waiting for an answer. If this is the case, remove the interactive prompt so that the build can complete non-interactively.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: To view the logs during a build:
|
||||
* In the browser, click **View logs.**
|
||||
|
||||
|
||||
|
||||
* In the VS Code desktop application, click **Building codespace** in the "Setting up remote connection" that's displayed.
|
||||
|
||||
|
||||
|
||||
{% endnote %}
|
||||
2. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
## Deleting codespaces
|
||||
|
||||
The owner of a codespace has full control over it and only they can delete their codespaces. You cannot delete a codespace created by another user.
|
||||
|
||||
@@ -65,6 +65,24 @@ If the `devcontainer.json` configuration file for a prebuild configuration is up
|
||||
|
||||
If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
|
||||
|
||||
### Preventing out-of-date prebuilds being used
|
||||
|
||||
By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
|
||||
|
||||
We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
|
||||
|
||||
{% data reusables.codespaces.accessing-prebuild-configuration %}
|
||||
1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
|
||||
|
||||
|
||||
1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
|
||||
|
||||
|
||||
1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
|
||||
|
||||
|
||||
1. To save your change, click **Update**.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: リポジトリコントリビューターのためのガイドラインを定める
|
||||
intro: プロジェクトに人々がどのようにコントリビュートするべきかを伝えるガイドラインを作成できます。
|
||||
title: Setting guidelines for repository contributors
|
||||
intro: You can create guidelines to communicate how people should contribute to your project.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -13,59 +13,56 @@ redirect_from:
|
||||
topics:
|
||||
- Community
|
||||
shortTitle: Contributor guidelines
|
||||
ms.openlocfilehash: b418c5a3d10f8b8f7572f33b17a9ebfbb3de27d3
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147578789'
|
||||
---
|
||||
## コントリビューションガイドラインについて
|
||||
プロジェクトの共同作成者が適切な作業を行えるように、コントリビューション ガイドラインを含むファイルをプロジェクト リポジトリのルート、`docs`、または `.github` フォルダーに追加できます。 プルリクエストをオープンした場合や Issue を作成した場合、そのファイルへのリンクが表示されます。 コントリビューション ガイドラインへのリンクは、ご自分のリポジトリの `contribute` ページにも表示されます。 `contribute` ページの例については、[github/docs/contribute](https://github.com/github/docs/contribute) を参照してください。
|
||||
## About contributing guidelines
|
||||
To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
|
||||
|
||||
|
||||
|
||||
リポジトリのオーナーにとって、コントリビューションガイドラインとは、人々がどのようにコントリビュートするべきかを伝える方法です。
|
||||
For the repository owner, contribution guidelines are a way to communicate how people should contribute.
|
||||
|
||||
コントリビューターにとって、このガイドラインは、上手に構築されたプルリクエストの提出をしたり、有益な Issue をオープンすることの確認に役立ちます。
|
||||
For contributors, the guidelines help them verify that they're submitting well-formed pull requests and opening useful issues.
|
||||
|
||||
オーナーおよびコントリビューターの双方にとって、コントリビューションガイドラインは、プルリクエストや Issue のリジェクトや再提出の手間を未然に軽減するための有効な手段です。
|
||||
For both owners and contributors, contribution guidelines save time and hassle caused by improperly created pull requests or issues that have to be rejected and re-submitted.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
ご自分の組織 {% ifversion fpt or ghes or ghec %} または、個人アカウント {% endif %} 向けに既定のコントリビューション ガイドラインを作成できます。 詳細については、「[既定のコミュニティ正常性ファイルの作成](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。
|
||||
You can create default contribution guidelines for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** リポジトリの保守担当者は、リポジトリの Issue や pull request のテンプレートを作成して、Issue についての特定のガイドラインを設定できます。 詳細については、「[Issue と pull request テンプレートについて](/articles/about-issue-and-pull-request-templates)」を参照してください。
|
||||
**Tip:** Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## *CONTRIBUTING* ファイルを追加する
|
||||
## Adding a *CONTRIBUTING* file
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
|
||||
3. リポジトリのルート `docs` または `.github` のディレクトリにコントリビューション ガイドラインを保存するかどうかを決定します。 そして、ファイル名のフィールドに、ファイルの名前および拡張子を入力します。 コントリビューションガイドラインのファイル名では大文字と小文字は区別されません。 サポートされているファイル拡張子の場合、ファイルはリッチテキスト形式でレンダリングされます。 詳細については、「[非コード ファイルでの作業](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)」を参照してください。
|
||||
|
||||
- リポジトリのルート ディレクトリにコントリビューション ガイドラインが表示されるようにするには、「*CONTRIBUTING*」と入力します。
|
||||
- リポジトリの `docs` ディレクトリにコントリビューション ガイドラインが表示されるようにするには、「*docs/* 」と入力して新しいディレクトリを作成してから、「*CONTRIBUTING*」を入力します。
|
||||
- リポジトリに複数の *CONTRIBUTING* ファイルが含まれている場合、リンクに表示されるファイルは、`.github` ディレクトリ、リポジトリのルート ディレクトリ、最後に `docs` ディレクトリの順に選択されます。
|
||||
4. 新しいファイルに、コントリビューションガイドラインを追加します。 このガイドラインには、次のことを含めましょう:
|
||||
- 有意義な Issue やプルリクエストの作成手順
|
||||
- \- 外部ドキュメント、メーリングリストや行動規範へのリンク
|
||||
- \- コミュニティや行動への期待
|
||||
{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.files.add-file %}
|
||||
3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)."
|
||||
|
||||
- To make your contributing guidelines visible in the repository's root directory, type *CONTRIBUTING*.
|
||||
- To make your contributing guidelines visible in the repository's `docs` directory, type *docs/* to create the new directory, then *CONTRIBUTING*.
|
||||
- If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
|
||||
4. In the new file, add contribution guidelines. These could include:
|
||||
- Steps for creating good issues or pull requests.
|
||||
- Links to external documentation, mailing lists, or a code of conduct.
|
||||
- Community and behavioral expectations.
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose_commit_branch %}
|
||||
{% data reusables.files.propose_new_file %}
|
||||
|
||||
## コントリビューションガイドラインの例
|
||||
## Examples of contribution guidelines
|
||||
|
||||
最初は悩むかもしれませんが、以下のコントリビューションガイドラインの例を役立ててください:
|
||||
If you're stumped, here are some good examples of contribution guidelines:
|
||||
|
||||
- Atom エディターの[コントリビューション ガイドライン](https://github.com/atom/atom/blob/master/CONTRIBUTING.md)。
|
||||
- Ruby on Rails の[コントリビューション ガイドライン](https://github.com/rails/rails/blob/main/CONTRIBUTING.md)。
|
||||
- Open Government の[コントリビューション ガイドライン](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md)。
|
||||
- The {% data variables.product.prodname_docs %} [contribution guidelines](https://github.com/github/docs/blob/main/CONTRIBUTING.md).
|
||||
- The Ruby on Rails [contribution guidelines](https://github.com/rails/rails/blob/main/CONTRIBUTING.md).
|
||||
- The Open Government [contribution guidelines](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md).
|
||||
|
||||
## 参考資料
|
||||
- オープン ソース ガイドのセクション「[Starting an Open Source Project](https://opensource.guide/starting-a-project/)」(オープン ソース プロジェクトの開始){% ifversion fpt or ghec %}
|
||||
## Further reading
|
||||
- The Open Source Guides' section "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% ifversion fpt or ghec %}
|
||||
- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% ifversion fpt or ghes or ghec %}
|
||||
- 「[リポジトリへのライセンスの追加](/articles/adding-a-license-to-a-repository)」{% endif %}
|
||||
- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ブランチでの変更
|
||||
intro: '[Atom](https://atom.io/) など、お好きなテキスト エディターを使用して、プロジェクトに変更を加え、{% data variables.product.prodname_desktop %} を使って役に立つコミットを視覚化します。'
|
||||
title: Making changes in a branch
|
||||
intro: 'Use your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), to make changes to your project, then use {% data variables.product.prodname_desktop %} to visualize useful commits.'
|
||||
redirect_from:
|
||||
- /desktop/contributing-to-projects/making-changes-in-a-branch
|
||||
versions:
|
||||
@@ -12,11 +12,5 @@ children:
|
||||
- /viewing-the-branch-history
|
||||
- /pushing-changes-to-github
|
||||
shortTitle: Make changes in a branch
|
||||
ms.openlocfilehash: 3ff1729cdf050f3604c383d965dda117b5a18e42
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145090142'
|
||||
---
|
||||
|
||||
|
||||
@@ -113,7 +113,7 @@ To troubleshoot, sign out of your account on {% data variables.product.prodname_
|
||||
### Empty token
|
||||
|
||||
```shell
|
||||
info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - <username> (empty token)
|
||||
info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - USERNAME (empty token)
|
||||
```
|
||||
|
||||
This error means that {% data variables.product.prodname_desktop %} is unable to find the access token that it created in the system keychain.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: デプロイキーの管理
|
||||
intro: デプロイメントのスクリプトを自動化する際にサーバー上のSSHキーを管理する様々な方法と、どれが最適な方法かを学んでください。
|
||||
title: Managing deploy keys
|
||||
intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you.
|
||||
redirect_from:
|
||||
- /guides/managing-deploy-keys
|
||||
- /v3/guides/managing-deploy-keys
|
||||
@@ -14,91 +14,90 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: 425535eb582c84801d79f00df751bb48d4a5b05e
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146058469'
|
||||
---
|
||||
SSHエージェントのフォワーディング、OAuthトークンでのHTTPS、デプロイキー、マシンユーザを使ってデプロイメントスクリプトを自動化する際に、サーバー上のSSHキーを管理できます。
|
||||
|
||||
## SSHエージェントのフォワーディング
|
||||
|
||||
多くの場合、特にプロジェクトの開始時には、SSHエージェントのフォワーディングが最も素早くシンプルに使える方法です。 エージェントのフォワーディングでは、ローカルの開発コンピュータで使うのと同じSSHキーを使います。
|
||||
You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users.
|
||||
|
||||
#### 長所
|
||||
## SSH agent forwarding
|
||||
|
||||
* 新しいキーを生成したり追跡したりしなくていい。
|
||||
* キーの管理は不要。ユーザはローカルと同じ権限をサーバーでも持つ。
|
||||
* サーバーにキーは保存されないので、サーバーが侵害を受けた場合でも、侵害されたキーを追跡して削除する必要はない。
|
||||
In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses.
|
||||
|
||||
#### 短所
|
||||
#### Pros
|
||||
|
||||
* ユーザーは、デプロイに SSH 接続する **必要があります**。自動デプロイ プロセスは使用できません。
|
||||
* SSHエージェントのフォワーディングは、Windowsのユーザが実行するのが面倒。
|
||||
* You do not have to generate or keep track of any new keys.
|
||||
* There is no key management; users have the same permissions on the server that they do locally.
|
||||
* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys.
|
||||
|
||||
#### セットアップ
|
||||
#### Cons
|
||||
|
||||
1. エージェントのフォワーディングをローカルでオンにしてください。 詳細については、[SSH エージェントの転送に関するガイド][ssh-agent-forwarding]を参照してください。
|
||||
2. エージェントフォワーディングを使用するように、デプロイスクリプトを設定してください。 たとえば、bash スクリプトでは、エージェントの転送を有効にすると、次のようになります: `ssh -A serverA 'bash -s' < deploy.sh`
|
||||
* Users **must** SSH in to deploy; automated deploy processes can't be used.
|
||||
* SSH agent forwarding can be troublesome to run for Windows users.
|
||||
|
||||
## OAuthトークンを使ったHTTPSでのクローニング
|
||||
#### Setup
|
||||
|
||||
SSH キーを使用しない場合は、OAuth トークンで HTTPS を使用できます。
|
||||
1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information.
|
||||
2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this:
|
||||
`ssh -A serverA 'bash -s' < deploy.sh`
|
||||
|
||||
#### 長所
|
||||
## HTTPS cloning with OAuth tokens
|
||||
|
||||
* サーバーにアクセスできる人なら、リポジトリをデプロイできる。
|
||||
* ユーザはローカルのSSH設定を変更する必要がない。
|
||||
* 複数のトークン（ユーザごと）が必要ない。サーバーごとに1つのトークンで十分。
|
||||
* トークンはいつでも取り消しできるので、本質的には使い捨てのパスワードにすることができる。
|
||||
If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
|
||||
|
||||
#### Pros
|
||||
|
||||
* Anyone with access to the server can deploy the repository.
|
||||
* Users don't have to change their local SSH settings.
|
||||
* Multiple tokens (one for each user) are not needed; one token per server is enough.
|
||||
* A token can be revoked at any time, turning it essentially into a one-use password.
|
||||
{% ifversion ghes %}
|
||||
* 新しいトークンの生成は、[OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization) を使用して簡単にスクリプト化できます。
|
||||
* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization).
|
||||
{% endif %}
|
||||
|
||||
#### 短所
|
||||
#### Cons
|
||||
|
||||
* トークンを確実に正しいアクセススコープで設定しなければならない。
|
||||
* トークンは本質的にはパスワードであり、パスワードと同じように保護しなければならない。
|
||||
* You must make sure that you configure your token with the correct access scopes.
|
||||
* Tokens are essentially passwords, and must be protected the same way.
|
||||
|
||||
#### セットアップ
|
||||
#### Setup
|
||||
|
||||
[個人用アクセス トークンの作成に関するガイド](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)を参照してください。
|
||||
See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
|
||||
|
||||
## デプロイ キー
|
||||
## Deploy keys
|
||||
|
||||
{% data reusables.repositories.deploy-keys %}
|
||||
|
||||
{% data reusables.repositories.deploy-keys-write-access %}
|
||||
|
||||
#### 長所
|
||||
#### Pros
|
||||
|
||||
* リポジトリとサーバーにアクセスできる人は、誰でもプロジェクトをデプロイできる。
|
||||
* ユーザはローカルのSSH設定を変更する必要がない。
|
||||
* デプロイ キーは既定では読み取り専用ですが、リポジトリに追加するときに書き込みアクセス権を付与することができます。
|
||||
* Anyone with access to the repository and server has the ability to deploy the project.
|
||||
* Users don't have to change their local SSH settings.
|
||||
* Deploy keys are read-only by default, but you can give them write access when adding them to a repository.
|
||||
|
||||
#### 短所
|
||||
#### Cons
|
||||
|
||||
* デプロイキーは単一のリポジトリに対するアクセスだけを許可できる。 より複雑なプロジェクトは、同じサーバーからプルする多くのリポジトリを持っていることがある。
|
||||
* デプロイキーは通常パスフレーズで保護されていないので、サーバーが侵害されると簡単にキーにアクセスされることになる。
|
||||
* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server.
|
||||
* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised.
|
||||
|
||||
#### セットアップ
|
||||
#### Setup
|
||||
|
||||
1. サーバーで [`ssh-keygen` 手順を実行][generating-ssh-keys]し、生成された公開キーと秘密 RSA キーのペアを保存する場所を覚えておいてください。
|
||||
2. 任意の {% data variables.product.product_name %} ページ上の右上隅にある自分のプロフィール写真をクリックしてから、 **[自分のプロフィール]** をクリックします。 
|
||||
3. プロフィール ページで、 **[リポジトリ]** をクリックし、リポジトリの名前をクリックします。 
|
||||
4. リポジトリから、 **[設定]** をクリックします。 
|
||||
5. サイドバーで、 **[キーのデプロイ]** 、 **[デプロイ キーの追加]** の順にクリックします。 
|
||||
6. タイトルを入力し、公開鍵に貼り付けてください。 
|
||||
7. このキーにリポジトリへの書き込みアクセス権を付与する場合は、 **[書き込みアクセスを許可する]** を選択します。 書き込みアクセス権を持つデプロイキーを使うと、リポジトリにデプロイメントのプッシュができるようになります。
|
||||
8. **[キーの追加]** をクリックします。
|
||||
1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public and private rsa key pair.
|
||||
{% data reusables.profile.navigating-to-profile %}
|
||||
|
||||
#### 1つのサーバー上で複数のリポジトリを利用する
|
||||
|
||||
1. On your profile page, click **Repositories**, then click the name of your repository. 
|
||||
2. From your repository, click **Settings**. 
|
||||
3. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. 
|
||||
4. Provide a title, paste in your public key. 
|
||||
5. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository.
|
||||
6. Click **Add key**.
|
||||
|
||||
1つのサーバー上で複数のリポジトリを使うなら、それぞれのリポジトリに対して専用のキーペアを生成しなければなりません。 複数のリポジトリでデプロイキーを再利用することはできません。
|
||||
#### Using multiple repositories on one server
|
||||
|
||||
サーバーの SSH 構成ファイル (通常 `~/.ssh/config`) に、各リポジトリのエイリアス エントリを追加します。 次に例を示します。
|
||||
If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.
|
||||
|
||||
In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example:
|
||||
|
||||
```bash
|
||||
Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0
|
||||
@@ -110,79 +109,79 @@ Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif
|
||||
IdentityFile=/home/user/.ssh/repo-1_deploy_key
|
||||
```
|
||||
|
||||
* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - リポジトリのエイリアス。
|
||||
* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - エイリアスで使用するホスト名を構成します。
|
||||
* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - 秘密キーをエイリアスに割り当てます。
|
||||
* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias.
|
||||
* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias.
|
||||
* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias.
|
||||
|
||||
こうすれば、ホスト名のエイリアスを使ってSSHでリポジトリとやりとりできます。この場合、このエイリアスに割り当てられたユニークなデプロイキーが使われます。 次に例を示します。
|
||||
You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example:
|
||||
|
||||
```bash
|
||||
$ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git
|
||||
```
|
||||
|
||||
## サーバー間トークン
|
||||
## Server-to-server tokens
|
||||
|
||||
サーバーが 1 つ以上の組織にわたるリポジトリにアクセスする必要がある場合、GitHub アプリを使用して必要なアクセスを定義し、その GitHub アプリから _スコープを厳格に設定した_、_サーバー間_ のトークンを生成します。 サーバー対サーバーのトークンは単一または複数のリポジトリをスコープとすることができ、権限を細かく設定できます。 たとえば、リポジトリのコンテンツへの読み取り専用アクセス権を持つトークンを生成できます。
|
||||
If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents.
|
||||
|
||||
GitHub Appは{% data variables.product.product_name %}でも主役級の存在なので、サーバー間トークンはあらゆるGitHubユーザから分離され、「サービストークン」に相当します。 さらに、サーバー間トークンには独自のレート制限があり、その制限は実行されるOrganizationの規模に応じて拡大されます。 詳細については、「[{% data variables.product.prodname_github_apps %} のレート制限](/developers/apps/rate-limits-for-github-apps)」を参照してください。
|
||||
Since GitHub Apps are a first class actor on {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for {% data variables.product.prodname_github_apps %}](/developers/apps/rate-limits-for-github-apps).
|
||||
|
||||
#### 長所
|
||||
#### Pros
|
||||
|
||||
- 権限設定と有効期限 (1時間、またはAPIで手動で取り消された場合にはそれ以下) が明確に定義された、スコープが厳格なトークン。
|
||||
- Organizationの規模に従って拡大する、独自のレート制限。
|
||||
- GitHubユーザIDと分離されているため、ライセンスのシート数を消費しない。
|
||||
- パスワードが付与されないので、直接サインインされない。
|
||||
- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API).
|
||||
- Dedicated rate limits that grow with your organization.
|
||||
- Decoupled from GitHub user identities, so they do not consume any licensed seats.
|
||||
- Never granted a password, so cannot be directly signed in to.
|
||||
|
||||
#### 短所
|
||||
#### Cons
|
||||
|
||||
- GitHub Appを作成するには追加設定が必要。
|
||||
- サーバー間トークンは1時間後に期限切れとなるので、再生成する必要がある (通常はコードを使用して、オンデマンドで行なう)。
|
||||
- Additional setup is needed to create the GitHub App.
|
||||
- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code.
|
||||
|
||||
#### セットアップ
|
||||
#### Setup
|
||||
|
||||
1. GitHub Appをパブリックにするかプライベートにするか決定します。 GitHub AppがOrganization内のリポジトリのみで動作する場合は、プライベートに設定した方がいいでしょう。
|
||||
1. リポジトリのコンテンツへの読み取り専用アクセスなど、GitHub Appが必要とする権限を決定します。
|
||||
1. Organizationの設定ページからGitHub Appを作成します。 詳細については、「[GitHub アプリの作成](/developers/apps/creating-a-github-app)」を参照してください。
|
||||
1. GitHub アプリ `id` をメモします。
|
||||
1. GitHub Appの秘密鍵を生成してダウンロードし、安全な方法で保存します。 詳細については、「[秘密キーを生成する](/developers/apps/authenticating-with-github-apps#generating-a-private-key)」を参照してください。
|
||||
1. 動作させたいリポジトリにGitHubをインストールします。Organizationの全リポジトリにGitHub Appをインストールしても構いません。
|
||||
1. GitHub アプリと、それがアクセスできる組織リポジトリの間の接続を表す `installation_id` を特定します。 各 GitHub アプリと組織のペアには、最大で 1 つの `installation_id` があります。 「[認証されたアプリの組織のインストールを取得する](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app)」を使用してこの `installation_id` を識別できます。 これには、JWT を使用した GitHub アプリとしての認証が必要です。詳細については、「[GitHub アプリとしての認証](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app)」を参照してください。
|
||||
1. 「[アプリのインストール アクセス トークンを作成する](/rest/reference/apps#create-an-installation-access-token-for-an-app)」を使用して、対応する REST API エンドポイントを使用してサーバー間トークンを生成します。 これには、JWT を使用した GitHub アプリとしての認証が必要です。詳細については、「[GitHub アプリとしての認証](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app)」と「[インストールとしての認証](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)」を参照してください。
|
||||
1. このサーバー間トークンを使用して、REST、GraphQL API、またはGitクライアント経由でリポジトリとやり取りします。
|
||||
1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private.
|
||||
1. Determine the permissions your GitHub App requires, such as read-only access to repository contents.
|
||||
1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app).
|
||||
1. Note your GitHub App `id`.
|
||||
1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key).
|
||||
1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization.
|
||||
1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access. Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app).
|
||||
1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation).
|
||||
1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client.
|
||||
|
||||
## マシンユーザ
|
||||
## Machine users
|
||||
|
||||
サーバーが複数のリポジトリにアクセスする必要がある場合、新しいアカウントを{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}で作成し、自動化専用に使われるSSHキーを添付できます。 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}のこのアカウントは人間によって使用されるものではないため、_マシン ユーザー_ と呼ばれます。 マシン ユーザーを個人リポジトリの [コラボレーター][collaborator] (読み取りと書き込みアクセス権の付与)、組織リポジトリの [外部コラボレーター][outside-collaborator] (読み取り、書き込み、または管理者アクセス権の付与)、または自動化する必要があるリポジトリへのアクセス権を持つ [チーム][team] (チームのアクセス許可の付与) として追加できます。
|
||||
If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team).
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** [サービス使用条件][tos]の状態:
|
||||
**Tip:** Our [terms of service][tos] state:
|
||||
|
||||
> *"ボット" またはその他の自動化された手段で "アカウント" を登録することは許可されていません。*
|
||||
> *Accounts registered by "bots" or other automated methods are not permitted.*
|
||||
|
||||
これは、アカウントの生成を自動化することはできないということです。 しかし、プロジェクトやOrganization内でデプロイスクリプトのような自動化タスクのために1つのマシンユーザを作成したいなら、それはまったく素晴らしいことです。
|
||||
This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### 長所
|
||||
#### Pros
|
||||
|
||||
* リポジトリとサーバーにアクセスできる人は、誰でもプロジェクトをデプロイできる。
|
||||
* （人間の）ユーザがローカルのSSH設定を変更する必要がない。
|
||||
* 複数のキーは必要ない。サーバーごとに1つでよい。
|
||||
* Anyone with access to the repository and server has the ability to deploy the project.
|
||||
* No (human) users need to change their local SSH settings.
|
||||
* Multiple keys are not needed; one per server is adequate.
|
||||
|
||||
#### 短所
|
||||
#### Cons
|
||||
|
||||
* Organizationだけがマシンユーザをリードオンリーのアクセスにできる。 個人リポジトリは、常にコラボレータの読み書きアクセスを許可する。
|
||||
* マシンユーザのキーは、デプロイキーのように、通常パスフレーズで保護されない。
|
||||
* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access.
|
||||
* Machine user keys, like deploy keys, are usually not protected by a passphrase.
|
||||
|
||||
#### セットアップ
|
||||
#### Setup
|
||||
|
||||
1. サーバーで [`ssh-keygen` 手順を実行][generating-ssh-keys]し、公開キーをマシン ユーザー アカウントにアタッチします。
|
||||
2. マシンユーザアカウントに自動化したいリポジトリへのアクセスを付与してください。 これを行うには、アカウントを [コラボレーター][collaborator] として、[外部コラボレーター][outside-collaborator] として、または組織内の [チーム][team] に追加します。
|
||||
1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account.
|
||||
2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization.
|
||||
|
||||
[ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
|
||||
[generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
|
||||
@@ -192,5 +191,5 @@ GitHub Appは{% data variables.product.product_name %}でも主役級の存在
|
||||
[outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
|
||||
[team]: /articles/adding-organization-members-to-a-team
|
||||
|
||||
## 参考資料
|
||||
- [通知の構成](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
|
||||
## Further reading
|
||||
- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
|
||||
|
||||
@@ -106,7 +106,7 @@ Activity related to a branch protection rule. For more information, see "[About
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration
|
||||
- {% data variables.product.prodname_github_apps %} with **Administration** repository permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -161,7 +161,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks only receive payloads for the `created` and `completed` event types in a repository
|
||||
- Organization webhooks only receive payloads for the `created` and `completed` event types in repositories
|
||||
- {% data variables.product.prodname_github_apps %} with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `rerequested` and `requested_action` event types. The `rerequested` and `requested_action` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event.
|
||||
- {% data variables.product.prodname_github_apps %} with **Checks** read permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have **Checks** write permission to receive the `rerequested` and `requested_action` event types. The `rerequested` and `requested_action` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with **Checks** write permission are automatically subscribed to this webhook event.
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -185,7 +185,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks only receive payloads for the `completed` event types in a repository
|
||||
- Organization webhooks only receive payloads for the `completed` event types in repositories
|
||||
- {% data variables.product.prodname_github_apps %} with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `requested` and `rerequested` event types. The `requested` and `rerequested` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event.
|
||||
- {% data variables.product.prodname_github_apps %} with **Checks** read permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have **Checks** write permission to receive the `requested` and `rerequested` event types. The `requested` and `rerequested` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with **Checks** write permission are automatically subscribed to this webhook event.
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -207,7 +207,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `security_events :read` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Code scanning alerts** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -229,7 +229,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -273,7 +273,7 @@ Webhook events are triggered based on the specificity of the domain you register
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -302,7 +302,7 @@ Webhook events are triggered based on the specificity of the domain you register
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -345,7 +345,7 @@ Webhook events are triggered based on the specificity of the domain you register
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `deployments` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Deployments** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -370,7 +370,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `deployments` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Deployments** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -401,7 +401,7 @@ Activity related to a discussion. For more information, see the "[Using the Grap
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `discussions` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Discussions** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -427,7 +427,7 @@ Activity related to a comment in a discussion. For more information, see "[Using
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `discussions` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Discussions** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -475,7 +475,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -518,7 +518,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -576,7 +576,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `issues` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Issues** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -599,7 +599,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `issues` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Issues** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -622,7 +622,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `metadata` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Metadata** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -673,7 +673,7 @@ For a detailed description of this payload and the payload for each type of `act
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -695,7 +695,7 @@ For a detailed description of this payload and the payload for each type of `act
|
||||
### Availability
|
||||
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -721,7 +721,7 @@ Activity related to merge groups in a merge queue. The type of activity is speci
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `merge_queues` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Merge queues** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -775,7 +775,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -798,7 +798,7 @@ Key | Type | Description
|
||||
{% ifversion ghes or ghae %}
|
||||
- GitHub Enterprise webhooks only receive `created` and `deleted` events. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/).{% endif %}
|
||||
- Organization webhooks only receive the `deleted`, `added`, `removed`, `renamed`, and `invited` events
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -824,7 +824,7 @@ Key | Type | Description
|
||||
### Availability
|
||||
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `organization_administration` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Administration** organization permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -870,7 +870,7 @@ Activity related to {% data variables.product.prodname_registry %}. {% data reus
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pages` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pages** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -921,7 +921,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Projects** repository or organization permission
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
@@ -953,7 +953,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Projects** repository or organization permission
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
@@ -983,7 +983,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Projects** repository or organization permission
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
@@ -1020,7 +1020,7 @@ Activity related to items in a {% data variables.projects.project_v2 %}. {% data
|
||||
### Availability
|
||||
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `organization_projects` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Projects** organization permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1046,7 +1046,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `metadata` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Metadata** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1073,7 +1073,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1098,7 +1098,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1120,7 +1120,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1143,7 +1143,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Pull requests** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1171,7 +1171,7 @@ Deliveries for `review_requested` and `review_request_removed` events will have
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1215,7 +1215,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `contents` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1236,7 +1236,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends
|
||||
|
||||
### Availability
|
||||
|
||||
- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload example
|
||||
|
||||
@@ -1250,7 +1250,7 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends
|
||||
|
||||
- Repository webhooks receive all event types except `deleted`
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `metadata` permission receive all event types except `deleted`
|
||||
- {% data variables.product.prodname_github_apps %} with **Metadata** permission receive all event types except `deleted`
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1319,7 +1319,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Secret scanning alerts** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1343,7 +1343,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Secret scanning alerts** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1366,7 +1366,7 @@ The security advisory dataset also powers the GitHub {% data variables.product.p
|
||||
|
||||
### Availability
|
||||
|
||||
- {% data variables.product.prodname_github_apps %} with the `security_events` permission
|
||||
- {% data variables.product.prodname_github_apps %}
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1391,7 +1391,7 @@ Activity related to enabling or disabling code security and analysis features fo
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration
|
||||
- {% data variables.product.prodname_github_apps %} with **Administration** repository permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1464,7 +1464,7 @@ You can only create a sponsorship webhook on {% data variables.product.prodname_
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `statuses` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Commit statuses** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1492,7 +1492,7 @@ Key | Type | Description
|
||||
### Availability
|
||||
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1523,7 +1523,7 @@ Key | Type | Description
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `members` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Members** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1564,7 +1564,7 @@ The event’s actor is the [user](/rest/reference/users) who starred a repositor
|
||||
|
||||
- Repository webhooks
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `metadata` permission
|
||||
- {% data variables.product.prodname_github_apps %} with **Metadata** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1585,7 +1585,7 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
|
||||
|
||||
### Availability
|
||||
|
||||
- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
|
||||
- {% data variables.product.prodname_github_apps %} with **Contents** permission
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
@@ -1634,7 +1634,7 @@ When a {% data variables.product.prodname_actions %} workflow run is requested o
|
||||
|
||||
### Availability
|
||||
|
||||
- {% data variables.product.prodname_github_apps %} with the `actions` or `contents` permissions.
|
||||
- {% data variables.product.prodname_github_apps %} with **Actions** or **Contents** permissions
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub の機能拡張およびインテグレーション
|
||||
intro: 'サードパーティアプリケーションの中でシームレスに{% data variables.product.product_name %}リポジトリ内で作業をするために、{% data variables.product.product_name %}機能拡張を使ってください。'
|
||||
title: GitHub extensions and integrations
|
||||
intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.'
|
||||
redirect_from:
|
||||
- /articles/about-github-extensions-for-third-party-applications
|
||||
- /articles/github-extensions-and-integrations
|
||||
@@ -10,53 +10,43 @@ versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Extensions & integrations
|
||||
ms.openlocfilehash: f33ce9b9ae55e523bedff1309f3f2f15202dcf82
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147884214'
|
||||
---
|
||||
## エディタツール
|
||||
## Editor tools
|
||||
|
||||
Atom、Unity、{% data variables.product.prodname_vs %} などのサードパーティ エディター ツール内で、{% data variables.product.product_name %} リポジトリに接続できます。
|
||||
|
||||
### {% data variables.product.product_name %} for Atom
|
||||
|
||||
{% data variables.product.product_name %} for Atom機能拡張を使うと、Atomエディタからコミット、プッシュ、プル、マージコンフリクトの解決などが行えます。 詳細については、公式の [{% data variables.product.product_name %} for Atom サイト](https://github.atom.io/)を参照してください。
|
||||
You can connect to {% data variables.product.product_name %} repositories within third-party editor tools such as Unity and {% data variables.product.prodname_vs %}.
|
||||
|
||||
### {% data variables.product.product_name %} for Unity
|
||||
|
||||
{% data variables.product.product_name %} for Unityエディタ機能拡張を使うと、オープンソースのゲーム開発プラットフォームであるUnity上で開発を行い、作業内容を{% data variables.product.product_name %}上で見ることができます。 詳細については、公式の Unity エディター拡張機能の[サイト](https://unity.github.com/)または[ドキュメント](https://github.com/github-for-unity/Unity/tree/master/docs)を参照してください。
|
||||
With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs).
|
||||
|
||||
### {% data variables.product.prodname_vs %} の {% data variables.product.product_name %}
|
||||
### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %}
|
||||
|
||||
{% data variables.product.prodname_vs %} 拡張機能の {% data variables.product.product_name %} を使用すると、{% data variables.product.prodname_vs %} を離れることなく、{% data variables.product.product_name %} リポジトリで作業できます。 詳しい情報については、公式の {% data variables.product.prodname_vs %} 拡張機能の[サイト](https://visualstudio.github.com/)または[ドキュメント](https://github.com/github/VisualStudio/tree/master/docs)を参照してください。
|
||||
With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs).
|
||||
|
||||
### {% data variables.product.prodname_vscode %} の {% data variables.product.prodname_dotcom %}
|
||||
### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %}
|
||||
|
||||
{% data variables.product.prodname_vscode %} 拡張機能の {% data variables.product.prodname_dotcom %} を使用すると、{% data variables.product.prodname_vscode_shortname %} で {% data variables.product.product_name %} pull requests を確認および管理できます。 詳しい情報については、公式の {% data variables.product.prodname_vscode_shortname %} 拡張機能の[サイト](https://vscode.github.com/)または[ドキュメント](https://github.com/Microsoft/vscode-pull-request-github)を参照してください。
|
||||
With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
|
||||
|
||||
## プロジェクト管理ツール
|
||||
## Project management tools
|
||||
|
||||
{% data variables.product.product_location %} の個人または Organization アカウントを Jira などのサードパーティのプロジェクト管理ツールと統合できます。
|
||||
You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira.
|
||||
|
||||
### Jira Cloud と {% data variables.product.product_name %}.com の統合
|
||||
### Jira Cloud and {% data variables.product.product_name %}.com integration
|
||||
|
||||
Jira Cloud を個人または Organization のアカウントに統合すると、コミットとプルリクエストをスキャンし、メンションされている JIRA の Issue で、関連するメタデータとハイパーリンクを作成できます。 詳細については、マーケットプレースの [Jira 統合アプリ](https://github.com/marketplace/jira-software-github)を参照してください。
|
||||
You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.
|
||||
|
||||
## チームコミュニケーションツール
|
||||
## Team communication tools
|
||||
|
||||
{% data variables.product.product_location %} の個人または Organization アカウントを Slack や Microsoft Teams などのサードパーティのコミュニケーション ツールと統合できます。
|
||||
You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
|
||||
|
||||
### Slack と {% data variables.product.product_name %} の統合
|
||||
### Slack and {% data variables.product.product_name %} integration
|
||||
|
||||
Slack + {% data variables.product.prodname_dotcom %} アプリを使用すると、リポジトリまたは Organization をサブスクライブし、Issue、pull request、コミット、ディスカッション、リリース、デプロイ レビュー、デプロイの状態に関するリアルタイムの更新を取得できます。 また、Issue を開いたり閉じたりするなどのアクティビティを実行したり、Slack を離れることなく、Issue や pull request に関する詳細な参照を確認することもできます。 また、あなたがチャネルや個人用チャットで受信した {% data variables.product.prodname_dotcom %} 通知の一部でメンションされている場合、このアプリから Slack であなたに直接 ping が実行されます。
|
||||
The Slack + {% data variables.product.prodname_dotcom %} app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, and you can see detailed references to issues and pull requests without leaving Slack. The app will also ping you personally in Slack if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
|
||||
|
||||
Slack + {% data variables.product.prodname_dotcom %} アプリも [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid) と互換性があります。 詳細については、マーケットプレースの [Slack + {% data variables.product.prodname_dotcom %} アプリ](https://github.com/marketplace/slack-github)を参照してください。
|
||||
The Slack + {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack + {% data variables.product.prodname_dotcom %} app](https://github.com/marketplace/slack-github) in the marketplace.
|
||||
|
||||
### Microsoft Teams と {% data variables.product.product_name %} の統合
|
||||
### Microsoft Teams and {% data variables.product.product_name %} integration
|
||||
|
||||
{% data variables.product.prodname_dotcom %} for Teams アプリを使用すると、リポジトリまたは Organization をサブスクライブし、Issue、pull request、コミット、ディスカッション、リリース、デプロイ レビュー、デプロイの状態に関するリアルタイムの更新を取得できます。 また、Issue の開始と終了、Issue や pull request へのコメントなどのアクティビティを実行したり、Microsoft Teams を離れることなく Issue や pull request に関する詳細な参照を確認したりすることができます。 また、あなたがチャネルや個人用チャットで受信した {% data variables.product.prodname_dotcom %} 通知の一部でメンションされている場合、このアプリから Teams であなたに直接 ping が実行されます。
|
||||
The {% data variables.product.prodname_dotcom %} for Teams app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, commenting on your issues and pull requests, and you can see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally in Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
|
||||
|
||||
詳細については、Microsoft AppSource で [{% data variables.product.prodname_dotcom %} for Teams アプリ](https://appsource.microsoft.com/en-us/product/office/WA200002077)を参照してください。
|
||||
For more information, visit the [{% data variables.product.prodname_dotcom %} for Teams app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Git とのテキストエディタの関連付け
|
||||
intro: テキストエディタを使って Git でファイルを開いたり編集したりしてください。
|
||||
title: Associating text editors with Git
|
||||
intro: Use a text editor to open and edit your files with Git.
|
||||
redirect_from:
|
||||
- /textmate
|
||||
- /articles/using-textmate-as-your-default-editor
|
||||
@@ -15,48 +15,33 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Associate text editors
|
||||
ms.openlocfilehash: 0d02c32ff04d4a5a2a1003464175e866630603f4
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145148757'
|
||||
---
|
||||
{% mac %}
|
||||
|
||||
## エディタとして Atom を使う
|
||||
## Using {% data variables.product.prodname_vscode %} as your editor
|
||||
|
||||
1. [Atom](https://atom.io/) をインストールしてください。 詳しい情報については、Atom の「[Atom のインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」のドキュメントを参照してください。
|
||||
1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## {% data variables.product.prodname_vscode %} をエディターに使う
|
||||
|
||||
1. [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}) をインストールします。 詳しい情報については、{% data variables.product.prodname_vscode_shortname %} のドキュメントの「[{% data variables.product.prodname_vscode_shortname %} の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」をご覧ください。
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## エディタとして Sublime Text を使う
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. [Sublime Text](https://www.sublimetext.com/) をインストールします。 詳しい情報については、Sublime Text の「[インストール](https://docs.sublimetext.io/guide/getting-started/installation.html)」のドキュメントを参照してください。
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "subl -n -w"
|
||||
```
|
||||
|
||||
## エディタとして TextMate を使う
|
||||
## Using TextMate as your editor
|
||||
|
||||
1. [TextMate](https://macromates.com/) をインストールします。
|
||||
2. TextMate の `mate` シェル ユーティリティをインストールします。 詳しい情報については、TextMate のドキュメントで「[`mate` と `rmate`](https://macromates.com/blog/2011/mate-and-rmate/)」を参照してください。
|
||||
1. Install [TextMate](https://macromates.com/).
|
||||
2. Install TextMate's `mate` shell utility. For more information, see "[`mate` and `rmate`](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
4. 次のコマンドを入力します。
|
||||
4. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "mate -w"
|
||||
```
|
||||
@@ -64,38 +49,29 @@ ms.locfileid: '145148757'
|
||||
|
||||
{% windows %}
|
||||
|
||||
## エディタとして Atom を使う
|
||||
## Using {% data variables.product.prodname_vscode %} as your editor
|
||||
|
||||
1. [Atom](https://atom.io/) をインストールしてください。 詳しい情報については、Atom の「[Atom のインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」のドキュメントを参照してください。
|
||||
1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## {% data variables.product.prodname_vscode %} をエディターに使う
|
||||
|
||||
1. [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}) をインストールします。 詳しい情報については、{% data variables.product.prodname_vscode_shortname %} のドキュメントの「[{% data variables.product.prodname_vscode_shortname %} の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」をご覧ください。
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## エディタとして Sublime Text を使う
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. [Sublime Text](https://www.sublimetext.com/) をインストールします。 詳しい情報については、Sublime Text の「[インストール](https://docs.sublimetext.io/guide/getting-started/installation.html)」のドキュメントを参照してください。
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w"
|
||||
```
|
||||
|
||||
## エディタとして Notepad++ を使う
|
||||
## Using Notepad++ as your editor
|
||||
|
||||
1. https://notepad-plus-plus.org/ Notepad++ をインストールしてください。 詳しい情報については、Notepad++ の「[概要](https://npp-user-manual.org/docs/getting-started/)」のドキュメントを参照してください。
|
||||
1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
|
||||
```
|
||||
@@ -103,29 +79,20 @@ ms.locfileid: '145148757'
|
||||
|
||||
{% linux %}
|
||||
|
||||
## エディタとして Atom を使う
|
||||
## Using {% data variables.product.prodname_vscode %} as your editor
|
||||
|
||||
1. [Atom](https://atom.io/) をインストールしてください。 詳しい情報については、Atom の「[Atom のインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」のドキュメントを参照してください。
|
||||
1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## {% data variables.product.prodname_vscode %} をエディターに使う
|
||||
|
||||
1. [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}) をインストールします。 詳しい情報については、{% data variables.product.prodname_vscode_shortname %} のドキュメントの「[{% data variables.product.prodname_vscode_shortname %} の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」をご覧ください。
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## エディタとして Sublime Text を使う
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. [Sublime Text](https://www.sublimetext.com/) をインストールします。 詳しい情報については、Sublime Text の「[インストール](https://docs.sublimetext.io/guide/getting-started/installation.html)」のドキュメントを参照してください。
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 次のコマンドを入力します。
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "subl -n -w"
|
||||
```
|
||||
|
||||
@@ -32,6 +32,7 @@ featuredLinks:
|
||||
- /get-started/onboarding/getting-started-with-github-enterprise-cloud
|
||||
- /get-started/onboarding/getting-started-with-github-enterprise-server
|
||||
- /get-started/onboarding/getting-started-with-github-ae
|
||||
- /get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github
|
||||
popular:
|
||||
- /github/getting-started-with-github/signing-up-for-a-new-github-account
|
||||
- /get-started/quickstart/hello-world
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub でのコミュニケーション
|
||||
intro: '{% data variables.product.product_name %} 上でさまざまな種類のディスカッションを用い、特定のプロジェクトや変更について、そしてもっと幅広くアイデアや Team のゴールについて話し合うことができます。'
|
||||
title: Communicating on GitHub
|
||||
intro: 'You can discuss specific projects and changes, as well as broader ideas or team goals, using different types of discussions on {% data variables.product.product_name %}.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github
|
||||
@@ -18,137 +18,137 @@ topics:
|
||||
- Issues
|
||||
- Discussions
|
||||
- Fundamentals
|
||||
ms.openlocfilehash: 6c7461a01cd0bc44bff93b1eb4e8a013d26bc147
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147408892'
|
||||
---
|
||||
## はじめに
|
||||
## Introduction
|
||||
|
||||
{% data variables.product.product_name %} には、コミュニティと密接にやり取りできる、コラボレーション可能なコミュニケーション ツールが組み込まれています。 このクイックスタート ガイドでは、ニーズに適したツールの選択方法について説明します。
|
||||
{% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
|
||||
|
||||
{% ifversion discussions %}行いたい会話の種類に応じて、issue、pull request、{% data variables.product.prodname_discussions %}、チーム ディスカッションを作成して参加できます。
|
||||
{% else %}行いたい会話の種類に応じて、issue、pull request、チーム ディスカッションを作成して参加できます。
|
||||
{% ifversion discussions %}
|
||||
You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
|
||||
{% else %}
|
||||
You can create and participate in issues, pull requests and team discussions, depending on the type of conversation you'd like to have.
|
||||
{% endif %}
|
||||
|
||||
### {% data variables.product.prodname_github_issues %}
|
||||
- バグ報告や改善計画、フィードバックなど、プロジェクトの特定の詳細についてのディスカッションに役立ちます。
|
||||
- リポジトリに固有であり、通常は明確なオーナーがいます。
|
||||
- 多くの場合、{% data variables.product.prodname_dotcom %} のバグ追跡システムと呼ばれます。
|
||||
- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
|
||||
- are specific to a repository, and usually have a clear owner.
|
||||
- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
|
||||
|
||||
### Pull Request
|
||||
- 特定の変更を提案できます。
|
||||
- 他のユーザーが提案した変更について直接コメントできます。
|
||||
- リポジトリに固有です。
|
||||
### Pull requests
|
||||
- allow you to propose specific changes.
|
||||
- allow you to comment directly on proposed changes suggested by others.
|
||||
- are specific to a repository.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### {% data variables.product.prodname_discussions %}
|
||||
- フォーラムのようなもので、コラボレーションが重要なオープン形式のアイデアやディスカッションに最適です。
|
||||
- 多数のリポジトリにまたがる場合があります。
|
||||
- コードベースの外部でコラボレーション エクスペリエンスを提供し、アイデアのブレーンストーミングとコミュニティのナレッジ ベースの作成を可能にします。
|
||||
- 多くの場合、明確なオーナーはいません。
|
||||
- 多くの場合、操作可能なタスクは発生しません。
|
||||
- are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
|
||||
- may span many repositories.
|
||||
- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
|
||||
- often don’t have a clear owner.
|
||||
- often do not result in an actionable task.
|
||||
{% endif %}
|
||||
|
||||
### Team ディスカッション
|
||||
- プロジェクトをまたぎ、特定の issue または pull request に属していない会話に対して、チームのページで開始できます。 アイデアについてディスカッションするためにリポジトリでIssueを開く代わりに、Teamディスカッションで会話することでTeam全体を巻き込めます。
|
||||
- 計画、分析、設計、ユーザー調査、一般的なプロジェクトの意思決定に関するチームのディスカッションを 1 か所で行うことができます。{% ifversion ghes or ghae %}
|
||||
- コードベースの外部でコラボレーション エクスペリエンスを提供し、アイデアのブレーンストーミングを可能にします。
|
||||
- 多くの場合、明確なオーナーはいません。
|
||||
- 多くの場合、操作可能なタスクは発生しません。{% endif %}
|
||||
### Team discussions
|
||||
- can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion.
|
||||
- allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% ifversion ghes or ghae %}
|
||||
- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
|
||||
- often don’t have a clear owner.
|
||||
- often do not result in an actionable task.{% endif %}
|
||||
|
||||
## どのディスカッション ツールを使用すべきか
|
||||
## Which discussion tool should I use?
|
||||
|
||||
### issue のシナリオ
|
||||
### Scenarios for issues
|
||||
|
||||
- タスク、機能強化、バグを追跡したい。
|
||||
- バグ報告を提出したい。
|
||||
- 特定の機能に関するフィードバックを共有したい。
|
||||
- リポジトリ内のファイルについて質問したい。
|
||||
- I want to keep track of tasks, enhancements and bugs.
|
||||
- I want to file a bug report.
|
||||
- I want to share feedback about a specific feature.
|
||||
- I want to ask a question about files in the repository.
|
||||
|
||||
#### 問題の例
|
||||
#### Issue example
|
||||
|
||||
この例では、{% data variables.product.prodname_dotcom %} ユーザーがどのようにしてドキュメント オープン ソース リポジトリに issue を作成してバグを認識させ、修正プログラムについて話し合うかを示しています。
|
||||
This example illustrates how a {% data variables.product.prodname_dotcom %} user created an issue in our documentation open source repository to make us aware of a bug, and discuss a fix.
|
||||
|
||||
|
||||
|
||||
|
||||
- あるユーザーが、中国語版の {% data variables.product.prodname_dotcom %} Docs のページ上部にあるバナーの青い色で、バナー内のテキストが読めなくなることに気付きました。
|
||||
- そのユーザーはリポジトリに issue を作成し、問題について述べ、修正プログラム (バナーに別の背景色を使用する) を提案しました。
|
||||
- ディスカッションが続き、最終的には、修正プログラムの適用に関する合意に達します。
|
||||
- これで、共同作成者が修正プログラムを含む pull request を作成できます。
|
||||
- A user noticed that the blue color of the banner at the top of the page in the Chinese version of the {% data variables.product.prodname_dotcom %} Docs makes the text in the banner unreadable.
|
||||
- The user created an issue in the repository, stating the problem and suggesting a fix (which is, use a different background color for the banner).
|
||||
- A discussion ensues, and eventually, a consensus will be reached about the fix to apply.
|
||||
- A contributor can then create a pull request with the fix.
|
||||
|
||||
### pull request のシナリオ
|
||||
### Scenarios for pull requests
|
||||
|
||||
- リポジトリの入力ミスを修正したい。
|
||||
- リポジトリに変更を加えたい。
|
||||
- 変更を加えて issue を修正したい。
|
||||
- 他の人によって提案された変更についてコメントしたい。
|
||||
- I want to fix a typo in a repository.
|
||||
- I want to make changes to a repository.
|
||||
- I want to make changes to fix an issue.
|
||||
- I want to comment on changes suggested by others.
|
||||
|
||||
#### プル要求の例
|
||||
#### Pull request example
|
||||
|
||||
この例では、{% data variables.product.prodname_dotcom %} ユーザーがどのようにしてドキュメント オープン ソース リポジトリに pull request を作成して入力ミスを修正するかを示します。
|
||||
This example illustrates how a {% data variables.product.prodname_dotcom %} user created a pull request in our documentation open source repository to fix a typo.
|
||||
|
||||
pull request の **[会話]** タブで、作成者が pull request を作成した理由を説明します。
|
||||
In the **Conversation** tab of the pull request, the author explains why they created the pull request.
|
||||
|
||||
![pull request の例 - [会話] タブ](/assets/images/help/pull_requests/pr-conversation-example.png)
|
||||
|
||||
|
||||
pull request の **[ファイルの変更]** タブには、実装された修正プログラムが表示されます。
|
||||
The **Files changed** tab of the pull request shows the implemented fix.
|
||||
|
||||
![pull request の例 - [ファイルの変更] タブ](/assets/images/help/pull_requests/pr-files-changed-example.png)
|
||||
|
||||
|
||||
- この共同作成者は、リポジトリの入力ミスに気付きました。
|
||||
- このユーザーが、修正プログラムを含む pull request を作成します。
|
||||
- リポジトリの保守担当者は、pull request を確認し、それにコメントを付けてマージします。
|
||||
- This contributor notices a typo in the repository.
|
||||
- The user creates a pull request with the fix.
|
||||
- A repository maintainer reviews the pull request, comments on it, and merges it.
|
||||
|
||||
{% ifversion discussions %}
|
||||
### {% data variables.product.prodname_discussions %} のシナリオ
|
||||
### Scenarios for {% data variables.product.prodname_discussions %}
|
||||
|
||||
- リポジトリ内の特定のファイルに必ずしも関連していない質問がある。
|
||||
- コラボレーターやチームとニュースを共有したい。
|
||||
- 自由回答の会話を開始または参加したい。
|
||||
- コミュニティで発表を行いたい。
|
||||
- I have a question that's not necessarily related to specific files in the repository.
|
||||
- I want to share news with my collaborators, or my team.
|
||||
- I want to start or participate in an open-ended conversation.
|
||||
- I want to make an announcement to my community.
|
||||
|
||||
#### {% data variables.product.prodname_discussions %} の例
|
||||
#### {% data variables.product.prodname_discussions %} example
|
||||
|
||||
この例では、{% data variables.product.prodname_dotcom %} Docs オープン ソース リポジトリの {% data variables.product.prodname_discussions %} ウェルカム投稿を示し、チームがコミュニティとどのようなコラボレーションを望んでいるかを示しています。
|
||||
This example shows the {% data variables.product.prodname_discussions %} welcome post for the {% data variables.product.prodname_dotcom %} Docs open source repository, and illustrates how the team wants to collaborate with their community.
|
||||
|
||||
|
||||
|
||||
|
||||
このコミュニティ保守担当者は、コミュニティを歓迎し、メンバーに自己紹介を求めるディスカッションを始めました。 この投稿は、訪問者と共同作成者が参加しやすい雰囲気を生み出します。 この投稿では、チームがリポジトリへの投稿を喜んで支援することも明らかになっています。
|
||||
This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
|
||||
|
||||
{% endif %}
|
||||
### チーム ディスカッションのシナリオ
|
||||
### Scenarios for team discussions
|
||||
|
||||
- リポジトリ内の特定のファイルに必ずしも関連していない質問がある。
|
||||
- コラボレーターやチームとニュースを共有したい。
|
||||
- 自由回答の会話を開始または参加したい。
|
||||
- チームで発表を行いたい。
|
||||
- I have a question that's not necessarily related to specific files in the repository.
|
||||
- I want to share news with my collaborators, or my team.
|
||||
- I want to start or participate in an open-ended conversation.
|
||||
- I want to make an announcement to my team.
|
||||
|
||||
{% ifversion fpt or ghec %} ご覧のように、チーム ディスカッションは {% data variables.product.prodname_discussions %} と非常によく似ています。 {% data variables.product.prodname_dotcom_the_website %} の場合、会話の出発点として {% data variables.product.prodname_discussions %} を使用することをお勧めします。 {% data variables.product.prodname_discussions %} を使用して、{% data variables.product.prodname_dotcom %} 上のどのコミュニティともコラボレーションを行うことができます。 あなたが組織の一員であり、組織内または組織のチーム内で会話を開始したい場合は、チーム ディスカッションを使用する必要があります。
|
||||
{% ifversion fpt or ghec %}
|
||||
As you can see, team discussions are very similar to {% data variables.product.prodname_discussions %}. For {% data variables.product.prodname_dotcom_the_website %}, we recommend using {% data variables.product.prodname_discussions %} as the starting point for conversations. You can use {% data variables.product.prodname_discussions %} to collaborate with any community on {% data variables.product.prodname_dotcom %}. If you are part of an organization, and would like to initiate conversations within your organization or team within that organization, you should use team discussions.
|
||||
{% endif %}
|
||||
|
||||
#### チーム ディスカッションの例
|
||||
#### Team discussion example
|
||||
|
||||
この例は、`octo-team` チームのチーム投稿を示しています。
|
||||
This example shows a team post for the `octo-team` team.
|
||||
|
||||
|
||||
|
||||
|
||||
`octocat` のチーム メンバーはチーム ディスカッションを投稿し、さまざまなことをチームに通知しました。
|
||||
- Mona というチーム メンバーがリモート ゲーム イベントを開始しました。
|
||||
- チームが {% data variables.product.prodname_actions %} を使用してどのようにドキュメントを生成するのかを説明するブログ記事があります。
|
||||
- April All Hands に関する資料を、すべてのチーム メンバーが閲覧できるようになりました。
|
||||
The `octocat` team member posted a team discussion, informing the team of various things:
|
||||
- A team member called Mona started remote game events.
|
||||
- There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs.
|
||||
- Material about the April All Hands is now available for all team members to view.
|
||||
|
||||
## 次の手順
|
||||
## Next steps
|
||||
|
||||
これらの例では、{% data variables.product.product_name %} で会話に最適なツールを決定する方法を示しました。 しかし、これは始まりにすぎません。これらのツールをニーズに合わせて調整するためにできることは、他にもたくさんあります。
|
||||
These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
|
||||
|
||||
たとえば、issue の場合は、より迅速に検索できるように issue にラベルをタグ付けしたり、共同作成者が有意義な issue をオープンできるように issue テンプレートを作成したりできます。 詳細については、「[Issue について](/github/managing-your-work-on-github/about-issues#working-with-issues)」と「[Issue と pull request のテンプレートについて](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)」を参照してください。
|
||||
For issues, for example, you can tag issues with labels for quicker searching and create issue templates to help contributors open meaningful issues. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues#working-with-issues)" and "[About issue and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)."
|
||||
|
||||
pull request の場合、提案された変更がまだ進行中の場合は、下書きの pull request を作成できます。 下書きの pull request は、レビュー準備完了としてマークされるまでマージできません。 詳細については、「[pull request について](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)」を参照してください。
|
||||
For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)."
|
||||
|
||||
{% ifversion discussions %}{% data variables.product.prodname_discussions %} の場合は、{% ifversion fpt or ghec %}行動規定を設定し、{% endif %}コミュニティの重要な情報を含むディスカッションをピン留めすることができます。 詳細については、「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
|
||||
{% ifversion discussions %}
|
||||
For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
|
||||
{% endif %}
|
||||
|
||||
チーム ディスカッションの場合は、チームのページでディスカッションを編集または削除したり、チーム ディスカッションの通知を構成したりできます。 詳細については、「[チーム ディスカッションについて](/organizations/collaborating-with-your-team/about-team-discussions)」を参照してください。
|
||||
For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
|
||||
|
||||
To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Git と GitHub の学習リソース
|
||||
title: Git and GitHub learning resources
|
||||
redirect_from:
|
||||
- /articles/good-resources-for-learning-git-and-github
|
||||
- /articles/what-are-other-good-resources-for-learning-git-and-github
|
||||
- /articles/git-and-github-learning-resources
|
||||
- /github/getting-started-with-github/git-and-github-learning-resources
|
||||
- /github/getting-started-with-github/quickstart/git-and-github-learning-resources
|
||||
intro: 'ウェブ上には数多くの役に立つ Git と {% data variables.product.product_name %} のリソースが存在します。 おすすめのものをまとめました。'
|
||||
intro: 'There are a lot of helpful Git and {% data variables.product.product_name %} resources on the web. This is a short list of our favorites!'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -15,55 +15,49 @@ versions:
|
||||
authors:
|
||||
- GitHub
|
||||
shortTitle: Learning resources
|
||||
ms.openlocfilehash: d8d0457de2842392febee0c90660285e9b1afef8
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146139297'
|
||||
---
|
||||
## Git の使用
|
||||
## Using Git
|
||||
|
||||
[Git の公式プロジェクト サイト](https://git-scm.com)にアクセスし、[ProGit の本](http://git-scm.com/book)を読むことで、Git について理解を深めてください。 [Git コマンド リスト](https://git-scm.com/docs)を確認することもできます。
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs).
|
||||
|
||||
## {% data variables.product.product_name %}を使用する
|
||||
## Using {% data variables.product.product_name %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% data variables.product.prodname_learning %} では、即座に自動化されたフィードバックやヘルプとともに、{% data variables.product.prodname_dotcom %} に組み込まれた無料のインタラクティブなコースを提供しています。 最初のプルリクエストをオープンしたり、最初のオープンソースへのコントリビューションを行ったり、{% data variables.product.prodname_pages %} のサイトを作成したりできます。 コース オファリングの詳細については、「[{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})」を参照してください。
|
||||
{% data variables.product.prodname_learning %} offers free interactive courses that are built into {% data variables.product.prodname_dotcom %} with instant automated feedback and help. Learn to open your first pull request, make your first open source contribution, create a {% data variables.product.prodname_pages %} site, and more. For more information about course offerings, see [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}).
|
||||
|
||||
{% endif %}
|
||||
|
||||
[概要](/categories/getting-started-with-github/)に関 する記事を通じて、{% data variables.product.product_name %} について理解を深めることができます。 プロセスの概要については、「[{% data variables.product.prodname_dotcom %} フロー](https://guides.github.com/introduction/flow)」を参照してください。 基本的な概念については、[概要ガイド](https://guides.github.com)を参照してください。
|
||||
Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. See our [{% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow) for a process introduction. Refer to our [overview guides](https://guides.github.com) to walk through basic concepts.
|
||||
|
||||
{% data reusables.support.ask-and-answer-forum %}
|
||||
|
||||
### ブランチ、フォーク、プルリクエスト
|
||||
### Branches, forks, and pull requests
|
||||
|
||||
対話型ツールを使用した [Git ブランチ](http://learngitbranching.js.org/)について説明します。 [フォーク](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)と [pull request](/articles/using-pull-requests)、および {% data variables.product.prodname_dotcom %} での [pull request の使用方法](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github)について説明します。 [コマンド ライン](https://cli.github.com/)から {% data variables.product.prodname_dotcom %} の使用に関するリファレンスにアクセスしてください。
|
||||
Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) and [pull requests](/articles/using-pull-requests) as well as [how we use pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) at {% data variables.product.prodname_dotcom %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/).
|
||||
|
||||
### 動画
|
||||
### Tune in
|
||||
|
||||
Microsoft の {% data variables.product.prodname_dotcom %} [YouTube のトレーニングとガイドのチャンネル](https://youtube.com/githubguides)では、[pull request](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19)、[フォーク](https://www.youtube.com/watch?v=5oJHRbqEofs)、[リベース](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22)、[リセット](https://www.youtube.com/watch?v=BKPjPMVB81g)機能に関するチュートリアルを提供しています。 各トピックの所要時間は 5 分以内です。
|
||||
Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides channel](https://youtube.com/githubguides) offers tutorials about [pull requests](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [forking](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22), and [reset](https://www.youtube.com/watch?v=BKPjPMVB81g) functions. Each topic is covered in 5 minutes or less.
|
||||
|
||||
## トレーニング
|
||||
## Training
|
||||
|
||||
### 無料コース
|
||||
### Free courses
|
||||
|
||||
{% data variables.product.product_name %} は、[{% data variables.product.prodname_dotcom %} の紹介](https://github.com/skills/introduction-to-github)を含む一連のインタラクティブな[オンデマンド トレーニング コース](https://skills.github.com/)や、{% data variables.product.prodname_actions %} などの {% data variables.product.product_name %} 固有のツールに関するコースを提供しています。
|
||||
{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://skills.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://github.com/skills/introduction-to-github); and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}.
|
||||
|
||||
### {% data variables.product.prodname_dotcom %}のウェブベース教育プログラム
|
||||
### {% data variables.product.prodname_dotcom %}'s web-based educational programs
|
||||
|
||||
{% data variables.product.prodname_dotcom %} では、生中継の[トレーニング](https://services.github.com/#upcoming-events)を提供しています。コマンド ラインの好き嫌いにかかわらず、すべてのユーザー向けにハンズオンのプロジェクトベースのアプローチを提供します。
|
||||
{% data variables.product.prodname_dotcom %} offers live [trainings](https://services.github.com/#upcoming-events) with a hands-on, project-based approach for those who love the command line and those who don't.
|
||||
|
||||
### 企業向けトレーニング
|
||||
### Training for your company
|
||||
|
||||
{% data variables.product.prodname_dotcom %} は、経験豊富な教師が教える[対面式のクラス](https://services.github.com/#offerings)を提供しています。 トレーニング関連の質問がある場合は[お問い合わせください](https://services.github.com/#contact)。
|
||||
{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contact us](https://services.github.com/#contact) to ask your training-related questions.
|
||||
|
||||
## 追加
|
||||
## Extras
|
||||
|
||||
[Pluralsight](https://www.pluralsight.com/codeschool) のインタラクティブな[オンライン Git コース](https://www.pluralsight.com/courses/code-school-git-real)には、7 つのレベルがあり、楽しいゲーム形式の数十の演習が提供されます。 [.gitignore テンプレート](https://github.com/github/gitignore)をニーズに合わせて自由に調整してください。
|
||||
An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Feel free to adapt our [.gitignore templates](https://github.com/github/gitignore) to meet your needs.
|
||||
|
||||
{% ifversion fpt or ghec %}integrations{% else %}[integrations](/articles/about-integrations){% endif %} を使用するか、{% data variables.product.prodname_desktop %} と堅牢な [Atom](https://desktop.github.com) テキスト エディターをインストールして、[{% data variables.product.prodname_dotcom %}](https://atom.io) の範囲を拡張します。
|
||||
Extend your {% data variables.product.prodname_dotcom %} reach through {% ifversion fpt or ghec %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) text editor.
|
||||
|
||||
[オープン ソース ガイド](https://opensource.guide/)を使用すると、オープンソース プロジェクトを起動して拡張する方法を確認できます。
|
||||
Learn how to launch and grow your open source project with the [Open Source Guides](https://opensource.guide/).
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub 上での執筆とフォーマットについて
|
||||
intro: GitHubは、GitHub Flavored Markdown と呼ばれるテキストフォーマットの構文を、いくつかのユニークな執筆用の機能と組み合わせています。
|
||||
title: About writing and formatting on GitHub
|
||||
intro: GitHub combines a syntax for formatting text called GitHub Flavored Markdown with a few unique writing features.
|
||||
redirect_from:
|
||||
- /articles/about-writing-and-formatting-on-github
|
||||
- /github/writing-on-github/about-writing-and-formatting-on-github
|
||||
@@ -10,40 +10,36 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Write & format on GitHub
|
||||
ms.openlocfilehash: 7819ebc6bbf3ffa8696c87f82745a19c103c8134
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147860835'
|
||||
shortTitle: About writing & formatting
|
||||
---
|
||||
[Markdown](http://daringfireball.net/projects/markdown/) は、プレーンテキストを書式設定するための読みやすく、書きやすい構文です。
|
||||
[Markdown](http://daringfireball.net/projects/markdown/) is an easy-to-read, easy-to-write syntax for formatting plain text.
|
||||
|
||||
サイトで文章とコードをフォーマットするのに使われる {% data variables.product.prodname_dotcom %}Flavored Markdown を作り出すために、弊社ではカスタムの機能をいくつか追加しました。
|
||||
We've added some custom functionality to create {% data variables.product.prodname_dotcom %} Flavored Markdown, used to format prose and code across our site.
|
||||
|
||||
また、pull request や issue では、[@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)、[issue と PR の参照](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)、[絵文字](/articles/basic-writing-and-formatting-syntax/#using-emoji)などの機能を使って他のユーザーとやり取りすることもできます。
|
||||
You can also interact with other users in pull requests and issues using features like [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [issue and PR references](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests), and [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji).
|
||||
|
||||
## テキストフォーマット用のツールバー
|
||||
## Text formatting toolbar
|
||||
|
||||
{% data variables.product.product_name %}のすべてのコメントフィールドには、テキストフォーマット用のツールバーが含まれており、Markdown の構文を学ばなくてもテキストをフォーマットできます。 太字や斜体といったスタイルなどの Markdown の書式、ヘッダー、リンク、リストの作成といったことに加えて、このツールバーには @mentions、タスクリスト、issue と pull request へのリンクといった {% data variables.product.product_name %} 固有の機能があります。
|
||||
Every comment field on {% data variables.product.product_name %} contains a text formatting toolbar, allowing you to format your text without learning Markdown syntax. In addition to Markdown formatting like bold and italic styles and creating headers, links, and lists, the toolbar includes {% data variables.product.product_name %}-specific features such as @mentions, task lists, and links to issues and pull requests.
|
||||
|
||||
{% ifversion fixed-width-font-gfm-fields %}
|
||||
|
||||
## エディターで固定幅フォントを有効にする
|
||||
## Enabling fixed-width fonts in the editor
|
||||
|
||||
{% data variables.product.product_name %} のすべてのコメント フィールドで固定幅フォントを有効にすることができます。 固定幅 (等幅) フォントの各文字は同じ水平方向の間隔を占めるため、テーブルやコード スニペットなどの高度な Markdown 構造の編集が簡単にできます。
|
||||
You can enable a fixed-width font in every comment field on {% data variables.product.product_name %}. Each character in a fixed-width, or monospace, font occupies the same horizontal space which can make it easier to edit advanced Markdown structures such as tables and code snippets.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.appearance-settings %}
|
||||
1. [Markdown editor font preference]\(Markdown エディターのフォント設定\) で **[Use a fixed-width (monospace) font when editing Markdown]\(Markdown の編集時に固定幅 (等幅) フォントを使用する\)** を選びます。
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.appearance-settings %}
|
||||
1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
|
||||
- [Basic writing and formatting syntax (基本的な書き方とフォーマットの構文)](/articles/basic-writing-and-formatting-syntax)
|
||||
- [Working with advanced formatting (高度な書式設定を使った作業)](/articles/working-with-advanced-formatting)
|
||||
- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
|
||||
- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
|
||||
- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
|
||||
- "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)"
|
||||
|
||||
@@ -179,13 +179,7 @@ You can specify the theme an image is displayed for in Markdown by using the HTM
|
||||
|
||||
For example, the following code displays a sun image for light themes and a moon for dark themes:
|
||||
|
||||
```HTML
|
||||
<picture>
|
||||
<source media="(prefers-color-scheme: dark)" srcset="https://user-images.githubusercontent.com/25423296/163456776-7f95b81a-f1ed-45f7-b7ab-8fa810d529fa.png">
|
||||
<source media="(prefers-color-scheme: light)" srcset="https://user-images.githubusercontent.com/25423296/163456779-a8556205-d0a5-45e2-ac17-42d089e3c3f8.png">
|
||||
<img alt="Shows an illustrated sun in light color mode and a moon with stars in dark color mode." src="https://user-images.githubusercontent.com/25423296/163456779-a8556205-d0a5-45e2-ac17-42d089e3c3f8.png">
|
||||
</picture>
|
||||
```
|
||||
{% data reusables.getting-started.picture-element-example %}
|
||||
|
||||
The old method of specifying images based on the theme, by using a fragment appended to the URL (`#gh-dark-mode-only` or `#gh-light-mode-only`), is deprecated and will be removed in favor of the new method described above.
|
||||
{% endif %}
|
||||
@@ -216,7 +210,7 @@ To order your list, precede each line with a number.
|
||||
|
||||
You can create a nested list by indenting one or more list items below another item.
|
||||
|
||||
To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [Atom](https://atom.io/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (<kbd>-</kbd> or <kbd>*</kbd>) lies directly below the first character of the text in the item above it.
|
||||
To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (<kbd>-</kbd> or <kbd>*</kbd>) lies directly below the first character of the text in the item above it.
|
||||
|
||||
```markdown
|
||||
1. First list item
|
||||
@@ -394,3 +388,4 @@ For more information, see Daring Fireball's "[Markdown Syntax](https://daringfir
|
||||
- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
|
||||
- "[About writing and formatting on GitHub](/articles/about-writing-and-formatting-on-github)"
|
||||
- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
|
||||
- "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)"
|
||||
|
||||
@@ -12,6 +12,7 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
children:
|
||||
- /quickstart-for-writing-on-github
|
||||
- /about-writing-and-formatting-on-github
|
||||
- /basic-writing-and-formatting-syntax
|
||||
shortTitle: Start writing on GitHub
|
||||
|
||||
@@ -70,8 +70,8 @@ You can find the node ID of an organization project if you know the organization
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{organization(login: \"<em>ORGANIZATION</em>\") {projectV2(number: <em>NUMBER</em>){id}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{organization(login: \"ORGANIZATION\") {projectV2(number: NUMBER){id}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -79,8 +79,8 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
organization(login: "<em>ORGANIZATION</em>"){
|
||||
projectV2(number: <em>NUMBER</em>) {
|
||||
organization(login: "ORGANIZATION"){
|
||||
projectV2(number: NUMBER) {
|
||||
id
|
||||
}
|
||||
}
|
||||
@@ -94,8 +94,8 @@ You can also find the node ID of all projects in your organization. The followin
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"{organization(login: \"<em>ORGANIZATION</em>\") {projectsV2(first: 20) {nodes {id title}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"{organization(login: \"ORGANIZATION") {projectsV2(first: 20) {nodes {id title}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -103,7 +103,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
organization(login: "<em>ORGANIZATION</em>") {
|
||||
organization(login: "ORGANIZATION") {
|
||||
projectsV2(first: 20) {
|
||||
nodes {
|
||||
id
|
||||
@@ -125,8 +125,8 @@ You can find the node ID of a user project if you know the project number. Repla
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{user(login: \"<em>USER</em>\") {projectV2(number: <em>NUMBER</em>){id}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{user(login: \"USER\") {projectV2(number: NUMBER){id}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -134,8 +134,8 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
user(login: "<em>USER</em>"){
|
||||
projectV2(number: <em>NUMBER</em>) {
|
||||
user(login: "USER"){
|
||||
projectV2(number: NUMBER) {
|
||||
id
|
||||
}
|
||||
}
|
||||
@@ -149,8 +149,8 @@ You can also find the node ID for all of your projects. The following example wi
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"{user(login: \"<em>USER</em>\") {projectsV2(first: 20) {nodes {id title}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"{user(login: \"USER\") {projectsV2(first: 20) {nodes {id title}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -158,7 +158,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
user(login: "<em>USER</em>") {
|
||||
user(login: "USER") {
|
||||
projectsV2(first: 20) {
|
||||
nodes {
|
||||
id
|
||||
@@ -180,8 +180,8 @@ The following example will return the ID, name, settings, and configuration for
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{ node(id: \"<em>PROJECT_ID</em>\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2Field { id name } ... on ProjectV2IterationField { id name configuration { iterations { startDate id }}} ... on ProjectV2SingleSelectField { id name options { id name }}}}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2Field { id name } ... on ProjectV2IterationField { id name configuration { iterations { startDate id }}} ... on ProjectV2SingleSelectField { id name options { id name }}}}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -189,7 +189,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
node(id: "<em>PROJECT_ID</em>") {
|
||||
node(id: "PROJECT_ID") {
|
||||
... on ProjectV2 {
|
||||
fields(first: 20) {
|
||||
nodes {
|
||||
@@ -284,8 +284,8 @@ If you just need the name and ID of a field, and do not need information about i
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{ node(id: \"<em>PROJECT_ID</em>\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2FieldCommon { id name }}}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2FieldCommon { id name }}}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -293,7 +293,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
node(id: "<em>PROJECT_ID</em>") {
|
||||
node(id: "PROJECT_ID") {
|
||||
... on ProjectV2 {
|
||||
fields(first: 20) {
|
||||
nodes {
|
||||
@@ -354,8 +354,8 @@ The following example will return the first 20 issues, pull requests, and draft
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"query{ node(id: \"<em>PROJECT_ID</em>\") { ... on ProjectV2 { items(first: 20) { nodes{ id fieldValues(first: 8) { nodes{ ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2FieldCommon { name }}} ... on ProjectV2ItemFieldDateValue { date field { ... on ProjectV2FieldCommon { name } } } ... on ProjectV2ItemFieldSingleSelectValue { name field { ... on ProjectV2FieldCommon { name }}}}} content{ ... on DraftIssue { title body } ...on Issue { title assignees(first: 10) { nodes{ login }}} ...on PullRequest { title assignees(first: 10) { nodes{ login }}}}}}}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { items(first: 20) { nodes{ id fieldValues(first: 8) { nodes{ ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2FieldCommon { name }}} ... on ProjectV2ItemFieldDateValue { date field { ... on ProjectV2FieldCommon { name } } } ... on ProjectV2ItemFieldSingleSelectValue { name field { ... on ProjectV2FieldCommon { name }}}}} content{ ... on DraftIssue { title body } ...on Issue { title assignees(first: 10) { nodes{ login }}} ...on PullRequest { title assignees(first: 10) { nodes{ login }}}}}}}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -363,7 +363,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
query{
|
||||
node(id: "<em>PROJECT_ID</em>") {
|
||||
node(id: "PROJECT_ID") {
|
||||
... on ProjectV2 {
|
||||
items(first: 20) {
|
||||
nodes{
|
||||
@@ -446,8 +446,8 @@ The following example will add an issue or pull request to your project. Replace
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {addProjectV2ItemById(input: {projectId: \"<em>PROJECT_ID</em>\" contentId: \"<em>CONTENT_ID</em>\"}) {item {id}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {addProjectV2ItemById(input: {projectId: \"PROJECT_ID\" contentId: \"CONTENT_ID\"}) {item {id}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -455,7 +455,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
mutation {
|
||||
addProjectV2ItemById(input: {projectId: "<em>PROJECT_ID</em>" contentId: "<em>CONTENT_ID</em>"}) {
|
||||
addProjectV2ItemById(input: {projectId: "PROJECT_ID" contentId: "CONTENT_ID"}) {
|
||||
item {
|
||||
id
|
||||
}
|
||||
@@ -488,8 +488,8 @@ The following example will add a draft issue to your project. Replace `PROJECT_I
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {addProjectV2DraftIssue(input: {projectId: "<em>PROJECT_ID</em>" title: "<em>TITLE</em>" body: "<em>BODY</em>"}) {projectItem {id}}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {addProjectV2DraftIssue(input: {projectId: \"PROJECT_ID\" title: \"TITLE\" body: \"BODY\"}) {projectItem {id}}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -497,7 +497,7 @@ curl --request POST \
|
||||
```shell
|
||||
gh api graphql -f query='
|
||||
mutation {
|
||||
addProjectV2DraftIssue(input: {projectId: "<em>PROJECT_ID</em>" title: "<em>TITLE</em>" body: "<em>BODY</em>"}) {
|
||||
addProjectV2DraftIssue(input: {projectId: "PROJECT_ID" title: "TITLE" body: "BODY"}) {
|
||||
projectItem {
|
||||
id
|
||||
}
|
||||
@@ -528,8 +528,8 @@ The following example will update your project's settings. Replace `PROJECT_ID`
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation { updateProjectV2(input: { projectId: \"<em>PROJECT_ID</em>\", title: \"Project title\", public: false, readme: \"# Project README\n\nA long description\", shortDescription: \"A short description\"}) { projectV2 { id, title, readme, shortDescription }}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation { updateProjectV2(input: { projectId: \"PROJECT_ID\", title: \"Project title\", public: false, readme: \"# Project README\n\nA long description\", shortDescription: \"A short description\"}) { projectV2 { id, title, readme, shortDescription }}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -539,7 +539,7 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
updateProjectV2(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>",
|
||||
projectId: "PROJECT_ID",
|
||||
title: "Project title",
|
||||
public: false,
|
||||
readme: "# Project README\n\nA long description",
|
||||
@@ -565,8 +565,8 @@ The following example will update the value of a text field for an item. Replace
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "<em>PROJECT_ID</em>" itemId: "<em>ITEM_ID</em>" fieldId: "<em>FIELD_ID</em>" value: { text: "Updated text" }}) { projectV2Item { id }}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { text: "Updated text" }}) { projectV2Item { id }}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -576,9 +576,9 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
updateProjectV2ItemFieldValue(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>"
|
||||
itemId: "<em>ITEM_ID</em>"
|
||||
fieldId: "<em>FIELD_ID</em>"
|
||||
projectId: "PROJECT_ID"
|
||||
itemId: "ITEM_ID"
|
||||
fieldId: "FIELD_ID"
|
||||
value: {
|
||||
text: "Updated text"
|
||||
}
|
||||
@@ -619,8 +619,8 @@ The following example will update the value of a single select field for an item
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "<em>PROJECT_ID</em>" itemId: "<em>ITEM_ID</em>" fieldId: "<em>FIELD_ID</em>" value: { singleSelectOptionId: "<em>OPTION_ID</em>" }}) { projectV2Item { id }}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { singleSelectOptionId: "OPTION_ID" }}) { projectV2Item { id }}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -630,11 +630,11 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
updateProjectV2ItemFieldValue(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>"
|
||||
itemId: "<em>ITEM_ID</em>"
|
||||
fieldId: "<em>FIELD_ID</em>"
|
||||
projectId: "PROJECT_ID"
|
||||
itemId: "ITEM_ID"
|
||||
fieldId: "FIELD_ID"
|
||||
value: {
|
||||
singleSelectOptionId: "<em>OPTION_ID</em>"
|
||||
singleSelectOptionId: "OPTION_ID"
|
||||
}
|
||||
}
|
||||
) {
|
||||
@@ -659,8 +659,8 @@ The following example will update the value of an iteration field for an item.
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "<em>PROJECT_ID</em>" itemId: "<em>ITEM_ID</em>" fieldId: "<em>FIELD_ID</em>" value: { singleSelectOptionId: "<em>OPTION_ID</em>" }}) { projectV2Item { id }}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { singleSelectOptionId: "OPTION_ID" }}) { projectV2Item { id }}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -670,11 +670,11 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
updateProjectV2ItemFieldValue(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>"
|
||||
itemId: "<em>ITEM_ID</em>"
|
||||
fieldId: "<em>FIELD_ID</em>"
|
||||
projectId: "PROJECT_ID"
|
||||
itemId: "ITEM_ID"
|
||||
fieldId: "FIELD_ID"
|
||||
value: {
|
||||
iterationId: "<em>ITERATION_ID</em>"
|
||||
iterationId: "ITERATION_ID"
|
||||
}
|
||||
}
|
||||
) {
|
||||
@@ -694,8 +694,8 @@ The following example will delete an item from a project. Replace `PROJECT_ID` w
|
||||
```shell
|
||||
curl --request POST \
|
||||
--url https://api.github.com/graphql \
|
||||
--header 'Authorization: Bearer <em>TOKEN</em>' \
|
||||
--data '{"query":"mutation {deleteProjectV2Item(input: {projectId: \"<em>PROJECT_ID</em>\" itemId: \"<em>ITEM_ID</em>\"}) {deletedItemId}}"}'
|
||||
--header 'Authorization: Bearer TOKEN' \
|
||||
--data '{"query":"mutation {deleteProjectV2Item(input: {projectId: \"PROJECT_ID\" itemId: \"ITEM_ID\"}) {deletedItemId}}"}'
|
||||
```
|
||||
{% endcurl %}
|
||||
|
||||
@@ -705,8 +705,8 @@ gh api graphql -f query='
|
||||
mutation {
|
||||
deleteProjectV2Item(
|
||||
input: {
|
||||
projectId: "<em>PROJECT_ID</em>"
|
||||
itemId: "<em>ITEM_ID</em>"
|
||||
projectId: "PROJECT_ID"
|
||||
itemId: "ITEM_ID"
|
||||
}
|
||||
) {
|
||||
deletedItemId
|
||||
|
||||
@@ -192,7 +192,7 @@ For pull requests, you can also use search to:
|
||||
- Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
|
||||
- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %}
|
||||
- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`
|
||||
- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/docs`
|
||||
- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`
|
||||
|
||||
## Sorting issues and pull requests
|
||||
|
||||
@@ -62,11 +62,11 @@ For more information on Punycodes, see [Internationalized domain name](https://e
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain.
|
||||
```shell
|
||||
$ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
|
||||
> ;<em>WWW.EXAMPLE.COM.</em> IN A
|
||||
> <em>WWW.EXAMPLE.COM.</em> 3592 IN CNAME <em>YOUR-USERNAME</em>.github.io.
|
||||
> <em>YOUR-USERNAME</em>.github.io. 43192 IN CNAME <em> GITHUB-PAGES-SERVER </em>.
|
||||
> <em> GITHUB-PAGES-SERVER </em>. 22 IN A 192.0.2.1
|
||||
$ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
|
||||
> ;WWW.EXAMPLE.COM. IN A
|
||||
> WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io.
|
||||
> YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER .
|
||||
> GITHUB-PAGES-SERVER . 22 IN A 192.0.2.1
|
||||
```
|
||||
{% data reusables.pages.build-locally-download-cname %}
|
||||
{% data reusables.pages.enforce-https-custom-domain %}
|
||||
@@ -104,19 +104,19 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
|
||||
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
|
||||
- For `A` records.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer -t A
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.108.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.109.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.110.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.111.153
|
||||
$ dig EXAMPLE.COM +noall +answer -t A
|
||||
> EXAMPLE.COM 3600 IN A 185.199.108.153
|
||||
> EXAMPLE.COM 3600 IN A 185.199.109.153
|
||||
> EXAMPLE.COM 3600 IN A 185.199.110.153
|
||||
> EXAMPLE.COM 3600 IN A 185.199.111.153
|
||||
```
|
||||
- For `AAAA` records.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer -t AAAA
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8000::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8001::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8002::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8003::153
|
||||
$ dig EXAMPLE.COM +noall +answer -t AAAA
|
||||
> EXAMPLE.COM 3600 IN AAAA 2606:50c0:8000::153
|
||||
> EXAMPLE.COM 3600 IN AAAA 2606:50c0:8001::153
|
||||
> EXAMPLE.COM 3600 IN AAAA 2606:50c0:8002::153
|
||||
> EXAMPLE.COM 3600 IN AAAA 2606:50c0:8003::153
|
||||
```
|
||||
{% data reusables.pages.build-locally-download-cname %}
|
||||
{% data reusables.pages.enforce-https-custom-domain %}
|
||||
@@ -132,11 +132,11 @@ After you configure the apex domain, you must configure a CNAME record with your
|
||||
1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
|
||||
```shell
|
||||
$ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
|
||||
> ;<em>WWW.EXAMPLE.COM.</em> IN A
|
||||
> <em>WWW.EXAMPLE.COM.</em> 3592 IN CNAME <em>YOUR-USERNAME</em>.github.io.
|
||||
> <em>YOUR-USERNAME</em>.github.io. 43192 IN CNAME <em> GITHUB-PAGES-SERVER </em>.
|
||||
> <em> GITHUB-PAGES-SERVER </em>. 22 IN A 192.0.2.1
|
||||
$ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
|
||||
> ;WWW.EXAMPLE.COM IN A
|
||||
> WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io.
|
||||
> YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER.
|
||||
> GITHUB-PAGES-SERVER. 22 IN A 192.0.2.1
|
||||
```
|
||||
## Removing a custom domain
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: コマンド ラインを使用してマージ コンフリクトを解決する
|
||||
intro: コマンド ラインとテキスト エディターを使用することで、マージ コンフリクトを解決できます。
|
||||
title: Resolving a merge conflict using the command line
|
||||
intro: You can resolve merge conflicts using the command line and a text editor.
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
|
||||
- /articles/resolving-a-merge-conflict-from-the-command-line
|
||||
@@ -15,33 +15,27 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: Resolve merge conflicts in Git
|
||||
ms.openlocfilehash: 1d4ff97c2a93d3e5a7aebaa8752810e284203bc1
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '147883458'
|
||||
---
|
||||
マージコンフリクトは、競合している変更がファイルの同じ行に行われるとき、またはある人があるファイルを編集し別の人が同じファイルを削除すると発生します。 詳細については、「[マージコンフリクトについて](/articles/about-merge-conflicts/)」を参照してください。
|
||||
Merge conflicts occur when competing changes are made to the same line of a file, or when one person edits a file and another person deletes the same file. For more information, see "[About merge conflicts](/articles/about-merge-conflicts/)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** {% data variables.product.product_name %} のコンフリクト エディターを使用することで、pull request の一部であるブランチの間で競合している行変更のマージ競合を解決できます。 詳細については、「[GitHub でのマージ コンフリクトを解決する](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)」を参照してください。
|
||||
**Tip:** You can use the conflict editor on {% data variables.product.product_name %} to resolve competing line change merge conflicts between branches that are part of a pull request. For more information, see "[Resolving a merge conflict on GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 競合している行変更のマージ コンフリクト
|
||||
## Competing line change merge conflicts
|
||||
|
||||
競合している行変更により発生するマージ コンフリクトを解決するには、新しいコミットにどの変更を組み込むかをいくつかの別のブランチから選択する必要があります。
|
||||
To resolve a merge conflict caused by competing line changes, you must choose which changes to incorporate from the different branches in a new commit.
|
||||
|
||||
たとえば、自分と別のユーザーの両方が、同じ Git リポジトリの別のブランチにあるファイル _styleguide.md_ で同じ行を編集した場合、これらのブランチをマージしようとするとマージ競合エラーが発生します。 これらのブランチをマージする前に、新たなコミットでこのマージコンフリクトを解決する必要があります。
|
||||
For example, if you and another person both edited the file _styleguide.md_ on the same lines in different branches of the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. マージ コンフリクトが発生しているローカルの Git リポジトリに移動します。
|
||||
2. Navigate into the local Git repository that has the merge conflict.
|
||||
```shell
|
||||
cd <em>REPOSITORY-NAME</em>
|
||||
cd REPOSITORY-NAME
|
||||
```
|
||||
3. マージ コンフリクトの影響を受けるファイルのリストを生成します。 この例では、ファイル *styleguide.md* にマージ競合が発生しています。
|
||||
3. Generate a list of the files affected by the merge conflict. In this example, the file *styleguide.md* has a merge conflict.
|
||||
```shell
|
||||
$ git status
|
||||
> # On branch branch-b
|
||||
@@ -55,8 +49,8 @@ ms.locfileid: '147883458'
|
||||
> #
|
||||
> no changes added to commit (use "git add" and/or "git commit -a")
|
||||
```
|
||||
4. [Atom](https://atom.io/) などの適切なテキスト エディターを開き、マージ競合が発生しているファイルに移動します。
|
||||
5. ファイル内でマージ競合の先頭を確認するには、ファイルで競合マーカー `<<<<<<<` を検索します。 テキスト エディターでファイルを開くと、行 `<<<<<<< HEAD` の後に HEAD つまりベース ブランチからの変更があることがわかります。 次に、`=======` があります。これは、自分の変更と他のブランチでの変更を区別するものであり、その後に `>>>>>>> BRANCH-NAME` が続きます。 この例では、あるユーザーがベース (HEAD) ブランチに "open an issue" と書き込み、別のユーザーが比較ブランチ (`branch-a`) に "ask your question in IRC" と書き込みました。
|
||||
4. Open your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), and navigate to the file that has merge conflicts.
|
||||
5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`.
|
||||
|
||||
```
|
||||
If you have questions, please
|
||||
@@ -66,34 +60,34 @@ ms.locfileid: '147883458'
|
||||
ask your question in IRC.
|
||||
>>>>>>> branch-a
|
||||
```
|
||||
{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}この例では、両方の変更が最終的なマージに取り込まれます。
|
||||
{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge:
|
||||
|
||||
```shell
|
||||
If you have questions, please open an issue or ask in our IRC channel if it's more urgent.
|
||||
```
|
||||
7. 変更を追加またはステージングします。
|
||||
7. Add or stage your changes.
|
||||
```shell
|
||||
$ git add .
|
||||
```
|
||||
8. 変更をコメントを付けてコミットします。
|
||||
8. Commit your changes with a comment.
|
||||
```shell
|
||||
$ git commit -m "Resolved merge conflict by incorporating both suggestions."
|
||||
```
|
||||
|
||||
これで、コマンド ラインでブランチをマージできます。または、{% data variables.product.product_name %} で[変更をリモート リポジトリにプッシュ](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)し、pull request で[変更をマージする](/articles/merging-a-pull-request/)ことができます。
|
||||
You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
|
||||
|
||||
## 削除したファイルのマージコンフリクト
|
||||
## Removed file merge conflicts
|
||||
|
||||
ある人があるブランチでファイルを削除し、別の人が同じファイルを編集するなどの、ファイルへの変更が競合していることにより発生するマージコンフリクトを解決するには、削除したファイルを削除するか保持するかを新しいコミットで選択する必要があります。
|
||||
To resolve a merge conflict caused by competing changes to a file, where a person deletes a file in one branch and another person edits the same file, you must choose whether to delete or keep the removed file in a new commit.
|
||||
|
||||
たとえば、自分が *README.md* などのファイルを編集し、別のユーザーが同じ Git リポジトリ内の別のブランチにある同じファイルを削除した場合、これらのブランチをマージしようとするとマージ競合エラーが発生します。 これらのブランチをマージする前に、新たなコミットでこのマージコンフリクトを解決する必要があります。
|
||||
For example, if you edited a file, such as *README.md*, and another person removed the same file in another branch in the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. マージ コンフリクトが発生しているローカルの Git リポジトリに移動します。
|
||||
2. Navigate into the local Git repository that has the merge conflict.
|
||||
```shell
|
||||
cd <em>REPOSITORY-NAME</em>
|
||||
cd REPOSITORY-NAME
|
||||
```
|
||||
2. マージ コンフリクトの影響を受けるファイルのリストを生成します。 この例では、ファイル *README.md* にマージ競合が発生しています。
|
||||
2. Generate a list of the files affected by the merge conflict. In this example, the file *README.md* has a merge conflict.
|
||||
```shell
|
||||
$ git status
|
||||
> # On branch main
|
||||
@@ -106,32 +100,32 @@ ms.locfileid: '147883458'
|
||||
> # Unmerged paths:
|
||||
> # (use "git add/rm <file>..." as appropriate to mark resolution)
|
||||
> #
|
||||
> # deleted by us: README.md
|
||||
> # deleted by us: README.md
|
||||
> #
|
||||
> # no changes added to commit (use "git add" and/or "git commit -a")
|
||||
```
|
||||
3. [Atom](https://atom.io/) などの適切なテキスト エディターを開き、マージ競合が発生しているファイルに移動します。
|
||||
6. 削除したファイルを保存するかどうかを決めます。 削除したファイルに行った最新の変更をテキスト エディターで確認することをお勧めします。
|
||||
3. Open your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), and navigate to the file that has merge conflicts.
|
||||
6. Decide if you want keep the removed file. You may want to view the latest changes made to the removed file in your text editor.
|
||||
|
||||
削除したファイルをリポジトリに追加して戻すには:
|
||||
To add the removed file back to your repository:
|
||||
```shell
|
||||
$ git add README.md
|
||||
```
|
||||
このファイルをリポジトリから削除するには:
|
||||
To remove this file from your repository:
|
||||
```shell
|
||||
$ git rm README.md
|
||||
> README.md: needs merge
|
||||
> rm 'README.md'
|
||||
```
|
||||
7. 変更をコメントを付けてコミットします。
|
||||
7. Commit your changes with a comment.
|
||||
```shell
|
||||
$ git commit -m "Resolved merge conflict by keeping README.md file."
|
||||
> [branch-d 6f89e49] Merge branch 'branch-c' into branch-d
|
||||
```
|
||||
|
||||
これで、コマンド ラインでブランチをマージできます。または、{% data variables.product.product_name %} で[変更をリモート リポジトリにプッシュ](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)し、pull request で[変更をマージする](/articles/merging-a-pull-request/)ことができます。
|
||||
You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- "[マージコンフリクトについて](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
|
||||
- "[プル リクエストをローカルでチェックアウトする](/articles/checking-out-pull-requests-locally/)"
|
||||
- "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
|
||||
- "[Checking out pull requests locally](/articles/checking-out-pull-requests-locally/)"
|
||||
|
||||
@@ -83,7 +83,7 @@ If you decide you don't want the changes in a topic branch to be merged to the u
|
||||
To merge a pull request, use the `gh pr merge` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request.
|
||||
|
||||
```shell
|
||||
gh pr merge <em>pull-request</em>
|
||||
gh pr merge PULL-REQUEST
|
||||
```
|
||||
|
||||
Follow the interactive prompts to complete the merge. For more information about the merge methods that you can choose, see "[About pull request merges](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
|
||||
|
||||
@@ -43,11 +43,11 @@ Only the user who created the pull request can give you permission to push commi
|
||||
```
|
||||
5. Type `git clone`, and then paste the URL you copied in Step 3.
|
||||
```shell
|
||||
$ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>
|
||||
$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY
|
||||
```
|
||||
6. Press **Enter**. Your local clone will be created.
|
||||
```shell
|
||||
$ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>
|
||||
$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY
|
||||
> Cloning into `FORK-OF-THE-REPOSITORY`...
|
||||
> remote: Counting objects: 10, done.
|
||||
> remote: Compressing objects: 100% (8/8), done.
|
||||
@@ -61,13 +61,13 @@ Only the user who created the pull request can give you permission to push commi
|
||||
{% endtip %}
|
||||
7. Navigate into your new cloned repository.
|
||||
```shell
|
||||
$ cd <em>FORK-OF-THE-REPOSITORY</em>
|
||||
$ cd FORK-OF-THE-REPOSITORY
|
||||
```
|
||||
7. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request.
|
||||
|
||||
In this example, the compare branch is `test-branch`:
|
||||
```shell
|
||||
$ git checkout <em>test-branch</em>
|
||||
$ git checkout TEST-BRANCH
|
||||
```
|
||||
|
||||
{% tip %}
|
||||
@@ -84,8 +84,8 @@ Only the user who created the pull request can give you permission to push commi
|
||||
> Compressing objects: 100% (26/26), done.
|
||||
> Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
|
||||
> Total 29 (delta 8), reused 0 (delta 0)
|
||||
> To https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>FORK-OF-THE-REPOSITORY</em>.git
|
||||
> 12da2e9..250e946 <em>test-branch</em> -> <em>test-branch</em>
|
||||
> To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git
|
||||
> 12da2e9..250e946 TEST-BRANCH -> TEST-BRANCH
|
||||
```
|
||||
|
||||
Your new commits will be reflected on the original pull request on {% data variables.product.product_location %}.
|
||||
|
||||
@@ -44,7 +44,7 @@ shortTitle: Check out a PR locally
|
||||
To check out a pull request locally, use the `gh pr checkout` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request.
|
||||
|
||||
```shell
|
||||
gh pr checkout <em>pull-request</em>
|
||||
gh pr checkout PULL-REQUEST
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
@@ -64,24 +64,24 @@ Anyone can work with a previously opened pull request to continue working on it,
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
5. Fetch the reference to the pull request based on its ID number, creating a new branch in the process.
|
||||
```shell
|
||||
$ git fetch origin pull/<em>ID</em>/head:<em>BRANCHNAME</em>
|
||||
$ git fetch origin pull/ID/head:BRANCH_NAME
|
||||
```
|
||||
6. Switch to the new branch that's based on this pull request:
|
||||
```shell
|
||||
[main] $ git checkout <em>BRANCHNAME</em>
|
||||
> Switched to a new branch '<em>BRANCHNAME</em>'
|
||||
[main] $ git checkout BRANCH_NAME
|
||||
> Switched to a new branch 'BRANCH_NAME'
|
||||
```
|
||||
7. At this point, you can do anything you want with this branch. You can run some local tests, or merge other branches into the branch.
|
||||
8. When you're ready, you can push the new branch up:
|
||||
```shell
|
||||
[pull-inactive-pull-request] $ git push origin <em>BRANCHNAME</em>
|
||||
[pull-inactive-pull-request] $ git push origin BRANCH_NAME
|
||||
> Counting objects: 32, done.
|
||||
> Delta compression using up to 8 threads.
|
||||
> Compressing objects: 100% (26/26), done.
|
||||
> Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
|
||||
> Total 29 (delta 8), reused 0 (delta 0)
|
||||
> To https://{% data variables.command_line.codeblock %}/<em>username</em>/<em>repository</em>.git
|
||||
> * [new branch] <em>BRANCHNAME</em> -> <em>BRANCHNAME</em>
|
||||
> To https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
|
||||
> * [new branch] BRANCH_NAME -> BRANCH_NAME
|
||||
```
|
||||
9. [Create a new pull request](/articles/creating-a-pull-request) with your new branch.
|
||||
|
||||
@@ -90,7 +90,7 @@ Anyone can work with a previously opened pull request to continue working on it,
|
||||
The remote `refs/pull/` namespace is *read-only*. If you try to push any commits there, you'll see this error:
|
||||
```shell
|
||||
! [remote rejected] HEAD -> refs/pull/1/head (deny updating a hidden ref)
|
||||
error: failed to push some refs to 'git@github.local:<em>USERNAME</em>/<em>REPOSITORY</em>.git'
|
||||
error: failed to push some refs to 'git@github.local:USERNAME/REPOSITORY.git'
|
||||
```
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -90,7 +90,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
|
||||
1. To create a release, use the `gh release create` subcommand. Replace `tag` with the desired tag for the release.
|
||||
|
||||
```shell
|
||||
gh release create <em>tag</em>
|
||||
gh release create TAG
|
||||
```
|
||||
|
||||
2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes.
|
||||
@@ -153,7 +153,7 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
|
||||
1. To delete a release, use the `gh release delete` subcommand. Replace `tag` with the tag of the release to delete. Use the `-y` flag to skip confirmation.
|
||||
|
||||
```shell
|
||||
gh release delete <em>tag</em> -y
|
||||
gh release delete TAG -y
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub での大きいファイルについて
|
||||
intro: '{% data variables.product.product_name %} には、通常の Git リポジトリで追跡できるファイルのサイズに制限があります。 制限を超えるファイルを追跡または削除する方法について説明します。'
|
||||
title: About large files on GitHub
|
||||
intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.'
|
||||
redirect_from:
|
||||
- /articles/distributing-large-binaries
|
||||
- /github/managing-large-files/distributing-large-binaries
|
||||
@@ -22,88 +22,85 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Large files
|
||||
ms.openlocfilehash: c9910f669b13c0c2bc4a8517ac6b33476b23b475
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146331649'
|
||||
---
|
||||
## {% data variables.product.product_name %} でのサイズ制限について
|
||||
|
||||
{% ifversion fpt or ghec %} {% data variables.product.product_name %} は、すべての Git リポジトリに対して十分なストレージを提供するよう努めていますが、ファイルとリポジトリのサイズにはハード制限があります。 ユーザのパフォーマンスと信頼性を確保するため、リポジトリ全体の健全性のシグナルを積極的に監視しています。 リポジトリの健全性は、サイズ、コミット頻度、コンテンツ、構造など、さまざまな相互作用要因の機能よるものです。
|
||||
## About size limits on {% data variables.product.product_name %}
|
||||
|
||||
### ファイル サイズ制限
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes. To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.
|
||||
|
||||
### File size limits
|
||||
{% endif %}
|
||||
|
||||
{% data variables.product.product_name %} には、リポジトリで許可されるファイルのサイズに制限があります。 {% data variables.large_files.warning_size %}より大きいファイルを追加または更新しようとすると、Gitから警告が表示されます。 変更は引き続きリポジトリに正常にプッシュされますが、パフォーマンスへの影響を最小限に抑えるためにコミットを削除することを検討してもよいでしょう。 詳しくは、「[ファイルをリポジトリの履歴から削除する](#removing-files-from-a-repositorys-history)」をご覧ください。
|
||||
{% data variables.product.product_name %} limits the size of files allowed in repositories. If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see "[Removing files from a repository's history](#removing-files-from-a-repositorys-history)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** ブラウザーからリポジトリにファイルを追加する場合、そのファイルは {% data variables.large_files.max_github_browser_size %} 以下でなければなりません。 詳細については、「[リポジトリにファイルを追加する](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)」を参照してください。
|
||||
**Note:** If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion ghes %}既定では、{% endif %}{% data variables.product.product_name %} は {% data variables.large_files.max_github_size %} を超えるプッシュをブロックします。 {% ifversion ghes %}ただし、サイト管理者は、{% data variables.product.product_location %} に対して異なる制限を構成できます。 詳しくは、「[Git のプッシュ制限を設定](/enterprise/admin/guides/installation/setting-git-push-limits)」をご覧ください。{% endif %}
|
||||
{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/admin/guides/installation/setting-git-push-limits)."{% endif %}
|
||||
|
||||
この制限を超えるファイルを追跡するには、{% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) を使う必要があります。 詳しくは、「[{% data variables.large_files.product_name_long %} について](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)」をご覧ください。
|
||||
To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)."
|
||||
|
||||
リポジトリ内で大きなファイルを配布する必要がある場合は、ファイルを追跡するのではなく、{% data variables.product.product_location %} でリリースを作成できます。 詳しくは、「[大きなバイナリを配布する](#distributing-large-binaries)」をご覧ください。
|
||||
If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)."
|
||||
|
||||
Git は、大きい SQL ファイルを処理するようには設計されていません。 大きいデータベースを他の開発者と共有するには、[Dropbox](https://www.dropbox.com/) を使うことをお勧めします。
|
||||
Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/).
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### リポジトリ サイズの制限
|
||||
{% ifversion fpt or ghec or ghae %}
|
||||
### Repository size limits
|
||||
|
||||
リポジトリは小さく保ち、理想としては 1GB 未満、および 5GB 未満にすることを強くお勧めします。 リポジトリが小さいほど、クローン作成が速く、操作やメンテナンスが簡単になります。 リポジトリがインフラストラクチャに過度に影響する場合は、{% data variables.contact.github_support %} から是正措置を求めるメールが送られてくる場合があります。 特に多くのコラボレータが参加している大規模なプロジェクトでは、柔軟に対応するよう努めており、可能な限り解決策を見つけるために協力します。 リポジトリのサイズと全体的な健全性を効果的に管理することで、リポジトリがインフラストラクチャに影響を与えることを防ぎます。 [`github/git-sizer`](https://github.com/github/git-sizer) リポジトリには、リポジトリ分析のためのアドバイスとツールがあります。
|
||||
We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. {% ifversion ghae %}The maximum size for a repository on {% data variables.product.product_name %} is 100 GB. {% endif %}Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
|
||||
|
||||
外部依存関係によって、Git リポジトリが非常に大きくなる場合があります。 リポジトリが外部依存関係で埋まってしまうことを避けるために、パッケージマネージャーの使用をお勧めします。 一般的な言語で人気のあるパッケージ マネージャーには、[Bundler](http://bundler.io/)、[Node のパッケージ マネージャー](http://npmjs.org/)、[Maven](http://maven.apache.org/) などがあります。 これらのパッケージマネージャーは Git リポジトリの直接使用をサポートしているため、事前にパッケージ化されたソースは必要ありません。
|
||||
External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](http://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources.
|
||||
|
||||
Git はバックアップツールとして機能するようには設計されていません。 ただし、[Arq](https://www.arqbackup.com/)、[Carbonite](http://www.carbonite.com/)、[CrashPlan](https://www.crashplan.com/en-us/) など、バックアップを実行するために特別に設計された多くのソリューションがあります。
|
||||
Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), and [CrashPlan](https://www.crashplan.com/en-us/).
|
||||
{% endif %}
|
||||
|
||||
## ファイルをリポジトリの履歴から削除する
|
||||
## Removing files from a repository's history
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**: この手順では、ファイルをコンピューターのリポジトリと {% data variables.product.product_location %} から完全に削除します。 ファイルが重要なものである場合は、ローカルバックアップコピーをリポジトリ外にあるディレクトリに作成してください。
|
||||
**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### プッシュされていない直近のコミットで追加されたファイルを削除する
|
||||
### Removing a file added in the most recent unpushed commit
|
||||
|
||||
ファイルが直近のコミットで追加され、{% data variables.product.product_location %} にプッシュしていない場合は、ファイルを削除してコミットを修正することができます。
|
||||
If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit:
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %}
|
||||
3. ファイルを削除するには、「`git rm --cached`」と入力します。
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
{% data reusables.command_line.switching_directories_procedural %}
|
||||
3. To remove the file, enter `git rm --cached`:
|
||||
```shell
|
||||
$ git rm --cached <em>giant_file</em>
|
||||
$ git rm --cached GIANT_FILE
|
||||
# Stage our giant file for removal, but leave it on disk
|
||||
```
|
||||
4. `--amend -CHEAD` を使って、この変更をコミットします。
|
||||
4. Commit this change using `--amend -CHEAD`:
|
||||
```shell
|
||||
$ git commit --amend -CHEAD
|
||||
# Amend the previous commit with your change
|
||||
# Simply making a new commit won't work, as you need
|
||||
# to remove the file from the unpushed history as well
|
||||
```
|
||||
5. コミットを {% data variables.product.product_location %} にプッシュします。
|
||||
5. Push your commits to {% data variables.product.product_location %}:
|
||||
```shell
|
||||
$ git push
|
||||
# Push our rewritten, smaller commit
|
||||
```
|
||||
|
||||
### 以前のコミットで追加されたファイルを削除する
|
||||
### Removing a file that was added in an earlier commit
|
||||
|
||||
以前のコミットでファイルを追加した場合は、リポジトリの履歴から削除する必要があります。 リポジトリの履歴からファイルを削除するには、BFG Repo-Cleaner または `git filter-branch` コマンドを使用できます。 詳しくは、「[機密データをリポジトリから削除する](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)」をご覧ください。
|
||||
If you added a file in an earlier commit, you need to remove it from the repository's history. To remove files from the repository's history, you can use the BFG Repo-Cleaner or the `git filter-branch` command. For more information see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)."
|
||||
|
||||
## 大きなバイナリを配布する
|
||||
## Distributing large binaries
|
||||
|
||||
リポジトリ内で大きなファイルを配布する必要がある場合は、{% data variables.product.product_location %}でリリースを作成できます。 リリースでは、他の人が使用できるように、ソフトウェア、リリースノート、バイナリファイルへのリンクをパッケージ化できます。 詳しくは、「[リリースについて](/github/administering-a-repository/about-releases)」をご覧ください。
|
||||
If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
リリース内のバイナリファイルの合計サイズや、それらの配布に使用される帯域は制限されません。 ただし、個々のファイルは{% data variables.large_files.max_lfs_size %}未満でなければなりません。
|
||||
We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -340,7 +340,7 @@ To view a fully interactive version of your Jupyter Notebook, you can set up a n
|
||||
If you're having trouble rendering Jupyter Notebook files in static HTML, you can convert the file locally on the command line by using the [`nbconvert` command](https://github.com/jupyter/nbconvert):
|
||||
|
||||
```shell
|
||||
$ jupyter nbconvert --to html <em>NOTEBOOK-NAME.ipynb</em>
|
||||
$ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb
|
||||
```
|
||||
|
||||
### Further reading
|
||||
|
||||
@@ -163,7 +163,7 @@ With cURL, you will send an `Authorization` header with your token. Replace `YOU
|
||||
```shell
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/octocat" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% note %}
|
||||
@@ -326,7 +326,7 @@ To send a header with cURL, use the `--header` or `-H` flag followed by the head
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/octocat" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
@@ -390,7 +390,7 @@ To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
@@ -443,7 +443,7 @@ For cURL, add a `?` to the end of the path, then append your query parameter nam
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2&sort=updated&direction=asc" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
@@ -495,7 +495,7 @@ For cURL, use the `--data` flag to pass the body parameters in a JSON object.
|
||||
curl --request POST \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>" \
|
||||
--header "Authorization: Bearer YOUR-TOKEN" \
|
||||
--data '{
|
||||
"title": "Created with the REST API",
|
||||
"body": "This is a test issue created by the REST API"
|
||||
@@ -593,7 +593,7 @@ For example, this request:
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>" \
|
||||
--header "Authorization: Bearer YOUR-TOKEN" \
|
||||
--include
|
||||
```
|
||||
|
||||
@@ -661,7 +661,7 @@ await octokit.request("GET /repos/{owner}/{repo}/issues", {
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>"
|
||||
--header "Authorization: Bearer YOUR-TOKEN"
|
||||
```
|
||||
|
||||
{% endcurl %}
|
||||
@@ -730,7 +730,7 @@ For example, you can use `>` to redirect the response to a file:
|
||||
curl --request GET \
|
||||
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
|
||||
--header "Accept: application/vnd.github.v3+json" \
|
||||
--header "Authorization: Bearer <em>YOUR-TOKEN</em>" > data.json
|
||||
--header "Authorization: Bearer YOUR-TOKEN" > data.json
|
||||
```
|
||||
|
||||
Then you can use jq to get the title and author ID of each issue:
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -268,7 +268,7 @@ You can filter pull requests based on their [review status](/pull-requests/colla
|
||||
| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person.
|
||||
| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %}
|
||||
| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. Requested reviewers are no longer listed in the search results after they review a pull request.
|
||||
| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:github/docs**](https://github.com/search?q=type%3Apr+team-review-requested%3Agithub%2Fdocs&type=pullrequests) matches pull requests that have review requests from the team `github/docs`. Requested reviewers are no longer listed in the search results after they review a pull request.
|
||||
|
||||
## Search by when an issue or pull request was created or last updated
|
||||
|
||||
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: ad73c4455042d29d72d3f76dbbdc512487c9303a
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "146139469"
|
||||
---
|
||||
{% data variables.product.prodname_actions %} のより複雑な機能を示す例については、「[例](/actions/examples)」を参照してください。 ランナーでコードをテストする方法、{% data variables.product.prodname_dotcom %} CLI にアクセスする方法、コンカレンシーやテスト マトリックスなどの高度な機能を使用する方法を説明する詳しい例を確認できます。
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: 5cbe77b1e8580e79c7e77b99de3e1973191d2075
|
||||
ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: "147878807"
|
||||
---
|
||||
メタデータの権限を `No access` に設定し、リポジトリへのアクセスを必要とする権限を選んだら、GitHub はその選択をオーバーライドし、メタデータの権限を `Read-only` に戻して設定します。 メタデータのアクセス許可を `No access` に設定するには、リポジトリへのアクセスを必要とするすべての権限を、最初に `No access` に設定する必要があります。
|
||||
@@ -15,6 +15,8 @@ After you connect your account on {% data variables.product.product_location %}
|
||||
|
||||
|
||||
|
||||
If codespaces are billable for the repository you choose, a message will be displayed in subsequent prompts telling you who will pay for the codespace.
|
||||
|
||||
4. Click the branch you want to develop on.
|
||||
|
||||
|
||||
|
||||
@@ -1,27 +1,22 @@
|
||||
---
|
||||
ms.openlocfilehash: 5120f840aab87ca243eed66c5bb6256e80aefeea
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147064179"
|
||||
---
|
||||
{% ifversion fpt or ghec %}既定では、次のようにして通知を受け取ります。{% endif %}{% ifversion ghes or ghae %}既定では、エンタープライズ所有者がインスタンスで通知用にメールを構成している場合、{% data variables.product.prodname_dependabot_alerts %} を次のように受け取ります。{% endif %}
|
||||
{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %}
|
||||
|
||||
- メール。{% data variables.product.prodname_dependabot %}がリポジトリで有効にされていて、新しいマニフェスト ファイルがリポジトリにコミットされたときに、重要度が重大または高の新しい脆弱性が見つかると、メールが送信されます ( **[脆弱性が見つかるたびにメールを送る]** オプション)。
|
||||
- ユーザー インターフェイス。セキュリティで保護されていない依存関係がある場合、リポジトリのファイル ビューとコード ビューに警告が表示されます ( **[UI alerts]\(UI アラート\)** オプション)。
|
||||
- コマンド ライン。セキュリティで保護されていない依存関係を使用してリポジトリにプッシュすると、警告がコールバックとして表示されます ( **[Command Line]\(コマンド ライン\)** オプション)。
|
||||
- インボックス (Web 通知として)。 Web 通知は、{% data variables.product.prodname_dependabot %} がリポジトリで有効にされていて、新しいマニフェスト ファイルがリポジトリにコミットされたときに、重要度が重大または高の新しい脆弱性が見つかった場合に送信されます ( **[Web]** オプション)。{% ifversion not ghae %}
|
||||
- {% data variables.product.prodname_mobile %}では、Web通知として表示されます。 詳細については、「[GitHub Mobile でプッシュ通知を有効にする](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)」を参照してください。{% endif %}
|
||||
- by email, an email is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option).
|
||||
- in the user interface, a warning is shown in your repository's file and code views if there are any insecure dependencies (**UI alerts** option).
|
||||
- on the command line, warnings are displayed as callbacks when you push to repositories with any insecure dependencies (**Command Line** option).
|
||||
- in your inbox, as web notifications. A web notification is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Web** option).{% ifversion not ghae %}
|
||||
- on {% data variables.product.prodname_mobile %}, as web notifications. For more information, see "[Enabling push notifications with GitHub Mobile](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** メールと Web{% ifversion not ghae %}/{% data variables.product.prodname_mobile %}{% endif %} の通知は次のとおりです。
|
||||
**Note:** The email and web{% ifversion not ghae %}/{% data variables.product.prodname_mobile %}{% endif %} notifications are:
|
||||
|
||||
- {% data variables.product.prodname_dependabot %} がリポジトリで有効にされているとき、または新しいマニフェスト ファイルがリポジトリにコミットされたときは、_リポジトリごと_。
|
||||
- _per repository_ when {% data variables.product.prodname_dependabot %} is enabled on the repository, or when a new manifest file is committed to the repository.
|
||||
|
||||
- 新しい脆弱性が検出されたときは、_Organization ごと_。
|
||||
- _per organization_ when a new vulnerability is discovered.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %} に関する通知を受け取る方法をカスタマイズできます。 たとえば、 **[脆弱性の要約をメールで送る]** と **[週単位のセキュリティ メール ダイジェスト]** オプションを使用すると、最大 10 個のリポジトリについてアラートを要約した週単位のダイジェスト メールを受け取ることができます。
|
||||
{% ifversion update-notification-settings-22 %}
|
||||
You can customize the way you are notified about {% data variables.product.prodname_dependabot_alerts %}. For example, you can receive a daily or weekly digest email summarizing alerts for up to 10 of your repositories using the **Email weekly digest** option.
|
||||
{% else %}
|
||||
You can customize the way you are notified about {% data variables.product.prodname_dependabot_alerts %}. For example, you can receive a weekly digest email summarizing alerts for up to 10 of your repositories using the **Email a digest summary of vulnerabilities** and **Weekly security email digest** options.{% endif %}
|
||||
|
||||
@@ -184,8 +184,10 @@ translations/ja-JP/content/site-policy/github-terms/github-community-forum-code-
|
||||
translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/glossaries/internal.yml,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/apps/metadata-permissions.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/billing/per-user-pricing-reference.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/availability.md,file deleted because it no longer exists in main
|
||||
@@ -246,8 +248,10 @@ translations/ja-JP/data/reusables/rest-reference/webhooks/repos.md,file deleted
|
||||
translations/ja-JP/data/reusables/security-center/beta.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
|
||||
@@ -298,7 +302,7 @@ translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-ac
|
||||
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,rendering error
|
||||
translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
|
||||
translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
|
||||
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
|
||||
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error
|
||||
translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
|
||||
@@ -306,6 +310,7 @@ translations/ja-JP/content/admin/identity-and-access-management/using-enterprise
|
||||
translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,rendering error
|
||||
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
|
||||
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error
|
||||
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error
|
||||
translations/ja-JP/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
|
||||
@@ -339,6 +344,7 @@ translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scannin
|
||||
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
|
||||
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,rendering error
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,rendering error
|
||||
@@ -412,23 +418,31 @@ translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-f
|
||||
translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
|
||||
translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/quickstart.md,broken liquid tags
|
||||
translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
|
||||
translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
|
||||
translations/ja-JP/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,broken liquid tags
|
||||
translations/ja-JP/content/developers/overview/about-githubs-apis.md,broken liquid tags
|
||||
translations/ja-JP/content/developers/overview/managing-deploy-keys.md,broken liquid tags
|
||||
translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
|
||||
translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
|
||||
translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
|
||||
translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
|
||||
translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/communicating-on-github.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-github/github-desktop.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-github/troubleshooting-connectivity-problems.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
|
||||
translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error
|
||||
@@ -460,6 +474,7 @@ translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages
|
||||
translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
|
||||
translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
|
||||
translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
|
||||
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
|
||||
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,broken liquid tags
|
||||
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
|
||||
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,broken liquid tags
|
||||
@@ -489,6 +504,7 @@ translations/ja-JP/content/repositories/releasing-projects-on-github/about-relea
|
||||
translations/ja-JP/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
|
||||
translations/ja-JP/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
|
||||
translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
|
||||
translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
|
||||
translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md,rendering error
|
||||
translations/ja-JP/content/rest/dependabot/index.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md,broken liquid tags
|
||||
@@ -599,6 +615,7 @@ translations/ja-JP/data/reusables/gated-features/secret-scanning-partner.md,rend
|
||||
translations/ja-JP/data/reusables/gated-features/secret-scanning.md,rendering error
|
||||
translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/notifications/shared_state.md,rendering error
|
||||
translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/organizations/billing_plans.md,rendering error
|
||||
translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
|
||||
translations/ja-JP/data/reusables/organizations/member-privileges.md,rendering error
|
||||
|
||||
|
Reference in New Issue
Block a user