Octomerger Bot
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: GitHub でサブスクリプションと通知を管理する
|
||||
title: Managing subscriptions and notifications on GitHub
|
||||
intro: 'You can specify how to receive notifications, the repositories you are interested in, and the types of activity you want to hear about.'
|
||||
redirect_from:
|
||||
- /categories/76/articles/
|
||||
- /categories/notifications/
|
||||
- /categories/76/articles
|
||||
- /categories/notifications
|
||||
- /categories/receiving-notifications-about-activity-on-github
|
||||
- /github/managing-subscriptions-and-notifications-on-github
|
||||
versions:
|
||||
|
||||
@@ -2,16 +2,16 @@
|
||||
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/
|
||||
- /articles/subscribing-to-conversations
|
||||
- /articles/unsubscribing-from-conversations
|
||||
- /articles/subscribing-to-and-unsubscribing-from-notifications
|
||||
- /articles/listing-the-issues-and-pull-requests-youre-subscribed-to
|
||||
- /articles/watching-repositories/
|
||||
- /articles/unwatching-repositories/
|
||||
- /articles/watching-repositories
|
||||
- /articles/unwatching-repositories
|
||||
- /articles/watching-and-unwatching-repositories
|
||||
- /articles/watching-and-unwatching-releases-for-a-repository
|
||||
- /articles/watching-and-unwatching-team-discussions
|
||||
- /articles/listing-watched-repositories/
|
||||
- /articles/listing-watched-repositories
|
||||
- /articles/listing-the-repositories-you-re-watching
|
||||
- /articles/listing-the-repositories-youre-watching
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: About notifications
|
||||
intro: 'Notifications provide updates about the activity on {% data variables.product.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
|
||||
redirect_from:
|
||||
- /articles/notifications/
|
||||
- /articles/notifications
|
||||
- /articles/about-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/about-notifications-beta
|
||||
- /github/managing-subscriptions-and-notifications-on-github/about-notifications
|
||||
|
||||
@@ -3,16 +3,16 @@ title: Configuring notifications
|
||||
intro: 'Choose the type of activity on {% data variables.product.prodname_dotcom %} that you want to receive notifications for and how you want these updates delivered.'
|
||||
redirect_from:
|
||||
- /articles/about-web-notifications
|
||||
- /format-of-notification-emails/
|
||||
- /articles/configuring-notification-emails/
|
||||
- /articles/about-notification-emails/
|
||||
- /format-of-notification-emails
|
||||
- /articles/configuring-notification-emails
|
||||
- /articles/about-notification-emails
|
||||
- /articles/about-email-notifications
|
||||
- /articles/accessing-your-notifications
|
||||
- /articles/configuring-notification-delivery-methods/
|
||||
- /articles/managing-notification-delivery-methods/
|
||||
- /articles/managing-notification-emails-for-organizations/
|
||||
- /articles/configuring-notification-delivery-methods
|
||||
- /articles/managing-notification-delivery-methods
|
||||
- /articles/managing-notification-emails-for-organizations
|
||||
- /articles/choosing-the-delivery-method-for-your-notifications
|
||||
- /articles/choosing-the-types-of-notifications-you-receive/
|
||||
- /articles/choosing-the-types-of-notifications-you-receive
|
||||
- /github/managing-subscriptions-and-notifications-on-github/configuring-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications
|
||||
versions:
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 通知の表示とトリアージ
|
||||
intro: 通知ワークフローを最適化するために、通知の表示方法とトリアージ方法をカスタマイズできます。
|
||||
title: Viewing and triaging notifications
|
||||
intro: 'To optimize your notifications workflow, you can customize how you view and triage notifications.'
|
||||
redirect_from:
|
||||
- /articles/managing-notifications/
|
||||
- /articles/managing-notifications
|
||||
- /articles/managing-your-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications
|
||||
versions:
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: About your profile
|
||||
intro: 'Your profile page tells people the story of your work through the repositories you''re interested in, the contributions you''ve made, and the conversations you''ve had.'
|
||||
redirect_from:
|
||||
- /articles/viewing-your-feeds/
|
||||
- /articles/profile-pages/
|
||||
- /articles/viewing-your-feeds
|
||||
- /articles/profile-pages
|
||||
- /articles/about-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/about-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: プロフィールをパーソナライズする
|
||||
intro: 'プロフィール画像を設定し、プロフィールに略歴を追加することで、自分自身についての情報を他の {% data variables.product.product_name %} ユーザと共有することができます。'
|
||||
title: Personalizing your profile
|
||||
intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.'
|
||||
redirect_from:
|
||||
- /articles/adding-a-bio-to-your-profile/
|
||||
- /articles/setting-your-profile-picture/
|
||||
- /articles/how-do-i-set-up-my-profile-picture/
|
||||
- /articles/gravatar-problems/
|
||||
- /articles/how-do-i-set-up-my-avatar/
|
||||
- /articles/adding-a-bio-to-your-profile
|
||||
- /articles/setting-your-profile-picture
|
||||
- /articles/how-do-i-set-up-my-profile-picture
|
||||
- /articles/gravatar-problems
|
||||
- /articles/how-do-i-set-up-my-avatar
|
||||
- /articles/personalizing-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/personalizing-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile
|
||||
@@ -19,35 +19,39 @@ topics:
|
||||
- Profiles
|
||||
shortTitle: Personalize
|
||||
---
|
||||
## Changing your profile picture
|
||||
|
||||
## プロフィール画像を変更する
|
||||
Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs.
|
||||
|
||||
プロフィール画像は、{% data variables.product.product_name %} のプルリクエスト、コメント、コントリビューションページ、およびグラフにおいて、あなたを識別するのに役立ちます。
|
||||
|
||||
アカウントにサインアップすると、{% data variables.product.product_name %} はとりあえずランダムなアイデンティコンを生成します。 [アイデンティコン](https://github.com/blog/1586-identicons)は、ユーザ ID のハッシュから生成されるもので、その色やパターンをコントロールする方法はありません。 アイデンティコンは、あなたを表す画像に置き換えることができます。
|
||||
When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**参考**: プロフィール画像は、1 MB 以下の PNG、JPG または GIF である必要があります。 最高の画質をもたらすには、画像を 500 × 500 ピクセルに収めることを推奨します。
|
||||
**Tip**: Your profile picture should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
### プロフィール画像を設定する
|
||||
### Setting a profile picture
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. [**Profile Picture**] で {% octicon "pencil" aria-label="The edit icon" %} [**Edit**] をクリックします。 
|
||||
3. [**Upload a photo...**] をクリックします。 
|
||||
3. 画像をクロッピングします。 作業を終えたら [**Set new profile picture**] をクリックします。 
|
||||
2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
|
||||
|
||||
3. Click **Upload a photo...**.
|
||||
|
||||
3. Crop your picture. When you're done, click **Set new profile picture**.
|
||||
|
||||
|
||||
### プロフィール画像をアイデンティコンへリセットする
|
||||
### Resetting your profile picture to the identicon
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. [**Profile Picture**] で {% octicon "pencil" aria-label="The edit icon" %} [**Edit**] をクリックします。 
|
||||
3. アイデンティコンに戻すには、[**Remove photo**] をクリックします。 メールアドレスが [Gravatar](https://en.gravatar.com/) に関連付けられている場合、アイデンティコンに戻すことはできません。 その場合は、代わりに [**Revert to Gravatar**] をクリックします。 
|
||||
2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
|
||||
|
||||
3. To revert to your identicon, click **Remove photo**. If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
|
||||
|
||||
|
||||
## プロフィール名を変更する
|
||||
## Changing your profile name
|
||||
|
||||
プロフィールに表示される名前は変更可能です。 この名前は、Organization が所有するプライベートリポジトリへのコメントの横に表示されることもあります。 詳細は「[Organization のメンバー名表示を管理する](/articles/managing-the-display-of-member-names-in-your-organization)」を参照してください。
|
||||
You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
@@ -58,81 +62,93 @@ shortTitle: Personalize
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. [Name] の下に、プロフィールに表示する名前を入力します。 ![プロフィール設定の [Name] フィールド](/assets/images/help/profile/name-field.png)
|
||||
2. Under "Name", type the name you want to be displayed on your profile.
|
||||
|
||||
|
||||
## プロフィールに略歴を追加する
|
||||
## Adding a bio to your profile
|
||||
|
||||
自分に関する情報を他の {% data variables.product.product_name %} ユーザーと共有するには、プロフィールに略歴を追加します。 [@メンション](/articles/basic-writing-and-formatting-syntax)と絵文字を使えば、あなたの現在あるいは過去の職場、職種、またどんな種類のコーヒーを飲んでいるかといった情報も含めることができます。
|
||||
Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
自分に関するカスタマイズした情報を長いフォームで、もっと目立つように表示する場合は、プロフィール README を使用することもできます。 詳しい情報については、「[プロフィール README の管理](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)」を参照してください。
|
||||
For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注釈** 自分のプロフィールに対してアクティビティの概要セクションを有効にしていて、そのプロフィール略歴でメンバーになっている Organization を @メンションすると、アクティビティの概要ではその Organization が最初に示されます。 詳しい情報については、「[プロフィールに自分のアクティビティの概要を表示する](/articles/showing-an-overview-of-your-activity-on-your-profile)」を参照してください。
|
||||
**Note:**
|
||||
If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. [**Bio**] の下に、自分のプロフィールに表示する内容を追加してください。 略歴フィールドの上限は 160 文字です。 
|
||||
2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** Organization を @メンションする場合、あなたがメンバーになっている Organization だけがオートコンプリートされます。 以前の職場など、自分がメンバーではない Organization を @メンションすることもできますが、その Organization の名前はオートコンプリートされません。
|
||||
**Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
3. [**Update profile**] をクリックします。 ![[Update profile] ボタン](/assets/images/help/profile/update-profile-button.png)
|
||||
3. Click **Update profile**.
|
||||
|
||||
|
||||
## ステータスを設定する
|
||||
## Setting a status
|
||||
|
||||
ステータスを設定すると、あなたの現在の状況に関する情報を {% data variables.product.product_name %} に表示することができます。 ステータスは次の場所や状況で表示されます:
|
||||
- {% data variables.product.product_name %} のプロフィールページ。
|
||||
- {% data variables.product.product_name %} でユーザがあなたのユーザ名やアバターにカーソルを置いたとき。
|
||||
- 自分が Team メンバーになっている Team の Team ページ。 詳細は「[Team について](/articles/about-teams/#team-pages)」を参照してください。
|
||||
- メンバーになっている Organization の Organization ダッシュボード。 詳細は「[Organization ダッシュボードについて](/articles/about-your-organization-dashboard/)」を参照してください。
|
||||
You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show:
|
||||
- on your {% data variables.product.product_name %} profile page.
|
||||
- when people hover over your username or avatar on {% data variables.product.product_name %}.
|
||||
- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)."
|
||||
- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)."
|
||||
|
||||
ステータスを設定すると、あなたの時間的な制約について、{% data variables.product.product_name %} で他のユーザーに知らせることもできます。
|
||||
When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
[Busy] オプションを選択すると、ユーザがあなたのユーザ名を @メンションしたり、Issue やプルリクエストをあなたに割り当てたりしたとき、またはあなたに Pull Request レビューをリクエストしたとき、ユーザ名の隣にビジーであることを示すノートが表示されます。 You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
|
||||
If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
|
||||
|
||||
1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status. 
|
||||
2. ステータスにカスタムテキストを追加する場合は、テキストフィールドをクリックしてステータスメッセージを入力します。 
|
||||
3. オプションで、ステータス絵文字を設定する場合は、絵文字のアイコンをクリックしてリストから選択します。 
|
||||
4. オプションで、時間に制約があるという情報を共有するには、[Busy] を選択します。 ![[Edit status] オプションで [Busy] オプションを選択](/assets/images/help/profile/limited-availability-status.png)
|
||||
5. [**Clear status**] ドロップダウンメニューを使って、ステータスの有効期限を選択します。 ステータスの有効期限を設定しない場合は、クリアするか編集するまで同じステータスのままになります。 
|
||||
6. ドロップダウンメニューを使って、ステータスを表示する Organization をクリックします。 Organization を選択しない場合、あなたのステータスはパブリックになります。 
|
||||
7. [**Set status**] をクリックします。 
|
||||
1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set your status** or, if you already have a status set, click your current status.
|
||||
|
||||
2. To add custom text to your status, click in the text field and type a status message.
|
||||
|
||||
3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list.
|
||||
|
||||
4. Optionally, if you'd like to share that you have limited availability, select "Busy."
|
||||
|
||||
5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.
|
||||
|
||||
6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public.
|
||||
|
||||
7. Click **Set status**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## プロフィールでバッジを表示する
|
||||
## Displaying badges on your profile
|
||||
|
||||
特定のプログラムに参加すると、{% data variables.product.prodname_dotcom %} でプロフィールに自動的にバッジが表示されます。
|
||||
When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
|
||||
|
||||
| バッジ | プログラム | 説明 |
|
||||
| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|  | **Mars 2020 Helicopter Contributor** | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were used in the mission. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." |
|
||||
|  | **{% data variables.product.prodname_arctic_vault %} Contributor** | 2020 Arctic Vault プログラムでアーカイブされたリポジトリのデフォルトブランチでコミットを作成すると、プロフィールで {% data variables.product.prodname_arctic_vault %} コントリビューターバッジを取得できます。 Hovering over the badge shows you several of the repositories you contributed to that were part of the program. 詳しい情報については、[{% data variables.product.prodname_archive %}](https://archiveprogram.github.com) を参照してください。 |
|
||||
|  | **{% data variables.product.prodname_dotcom %} Sponsor** | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. 詳細は、「[オープンソースコントリビューターに対するスポンサー](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)」を参照してください。 |
|
||||
| {% octicon "cpu" aria-label="The Developer Program icon" %} | **開発者プログラムメンバー** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). |
|
||||
| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | {% data variables.product.prodname_pro %} を使用すると、プロフィールで PRO バッジを取得します。 {% data variables.product.prodname_pro %} の詳細は、「[{% data variables.product.prodname_dotcom %} の製品](/github/getting-started-with-github/githubs-products#github-pro)」を参照してください。 |
|
||||
| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
|
||||
| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
|
||||
| Badge | Program | Description |
|
||||
| --- | --- | --- |
|
||||
|  | **Mars 2020 Helicopter Contributor** | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were used in the mission. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." |
|
||||
|  | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were part of the program. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). |
|
||||
|  | **{% data variables.product.prodname_dotcom %} Sponsor** | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)." |
|
||||
| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Developer Program Member** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). |
|
||||
| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)." |
|
||||
| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
|
||||
| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
|
||||
|
||||
## プロフィールでバッジを無効にする
|
||||
## Disabling badges on your profile
|
||||
|
||||
You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. [Profile settings] で、無効にするバッジの選択を解除します。 
|
||||
3. [**Update preferences**] をクリックします。
|
||||
2. Under "Profile settings", deselect the badge you want you disable.
|
||||
|
||||
3. Click **Update preferences**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -140,77 +156,77 @@ You can disable some of the badges for {% data variables.product.prodname_dotcom
|
||||
|
||||
If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
|
||||
|
||||
| {% data variables.product.prodname_dotcom %} Repository | バージョン | Tag |
|
||||
| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
|
||||
| [torvalds/linux](https://github.com/torvalds/linux) | 3.4 | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4) |
|
||||
| [python/cpython](https://github.com/python/cpython) | 3.9.2 | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2) |
|
||||
| [boto/boto3](https://github.com/boto/boto3) | 1.17.17 | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17) |
|
||||
| [boto/botocore](https://github.com/boto/botocore) | 1.20.11 | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11) |
|
||||
| [certifi/python-certifi](https://github.com/certifi/python-certifi) | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05) |
|
||||
| [chardet/chardet](https://github.com/chardet/chardet) | 4.0.0 | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0) |
|
||||
| [matplotlib/cycler](https://github.com/matplotlib/cycler) | 0.10.0 | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0) |
|
||||
| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py) | 6.8.1 | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1) |
|
||||
| [ianare/exif-py](https://github.com/ianare/exif-py) | 2.3.2 | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2) |
|
||||
| [kjd/idna](https://github.com/kjd/idna) | 2.10 | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10) |
|
||||
| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py) | 0.10.0 | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0) |
|
||||
| [nucleic/kiwi](https://github.com/nucleic/kiwi) | 1.3.1 | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1) |
|
||||
| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib) | 3.3.4 | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4) |
|
||||
| [numpy/numpy](https://github.com/numpy/numpy) | 1.20.1 | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1) |
|
||||
| [opencv/opencv-python](https://github.com/opencv/opencv-python) | 4.5.1.48 | [48](https://github.com/opencv/opencv-python/releases/tag/48) |
|
||||
| [python-pillow/Pillow](https://github.com/python-pillow/Pillow) | 8.1.0 | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0) |
|
||||
| [pycurl/pycurl](https://github.com/pycurl/pycurl) | 7.43.0.6 | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.7 | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7) |
|
||||
| [pyserial/pyserial](https://github.com/pyserial/pyserial) | 3.5 | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5) |
|
||||
| [dateutil/dateutil](https://github.com/dateutil/dateutil) | 2.8.1 | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1) |
|
||||
| [yaml/pyyaml ](https://github.com/yaml/pyyaml) | 5.4.1 | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1) |
|
||||
| [psf/requests](https://github.com/psf/requests) | 2.25.1 | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1) |
|
||||
| [boto/s3transfer](https://github.com/boto/s3transfer) | 0.3.4 | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4) |
|
||||
| [enthought/scimath](https://github.com/enthought/scimath) | 4.2.0 | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0) |
|
||||
| [scipy/scipy](https://github.com/scipy/scipy) | 1.6.1 | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1) |
|
||||
| [benjaminp/six](https://github.com/benjaminp/six) | 1.15.0 | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0) |
|
||||
| [enthought/traits](https://github.com/enthought/traits) | 6.2.0 | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0) |
|
||||
| [urllib3/urllib3](https://github.com/urllib3/urllib3) | 1.26.3 | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3) |
|
||||
| [python-attrs/attrs](https://github.com/python-attrs/attrs) | 19.3.0 | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0) |
|
||||
| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/) | 3.2.4 | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4) |
|
||||
| [pallets/click](https://github.com/pallets/click) | 7.0 | [7.0](https://github.com/pallets/click/releases/tag/7.0) |
|
||||
| [pallets/flask](https://github.com/pallets/flask) | 1.1.1 | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1) |
|
||||
| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7 | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7) |
|
||||
| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig) | 1.0.0 | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0) |
|
||||
| [pallets/itsdangerous](https://github.com/pallets/itsdangerous) | 1.1.0 | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0) |
|
||||
| [pallets/jinja](https://github.com/pallets/jinja) | 2.10.3 | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3) |
|
||||
| [lxml/lxml](https://github.com/lxml/lxml) | 4.4.1 | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1) |
|
||||
| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown) | 3.1.1 | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1) |
|
||||
| [pallets/markupsafe](https://github.com/pallets/markupsafe) | 1.1.1 | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1) |
|
||||
| [pypa/packaging](https://github.com/pypa/packaging) | 19.2 | [19.2](https://github.com/pypa/packaging/releases/tag/19.2) |
|
||||
| [pexpect/pexpect](https://github.com/pexpect/pexpect) | 4.7.0 | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0) |
|
||||
| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy) | 0.13.0 | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0) |
|
||||
| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess) | 0.6.0 | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0) |
|
||||
| [pytest-dev/py](https://github.com/pytest-dev/py) | 1.8.0 | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.5 | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5) |
|
||||
| [pytest-dev/pytest](https://github.com/pytest-dev/pytest) | 5.3.0 | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0) |
|
||||
| [stub42/pytz](https://github.com/stub42/pytz) | 2019.3 | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3) |
|
||||
| [uiri/toml](https://github.com/uiri/toml) | 0.10.0 | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0) |
|
||||
| [pallets/werkzeug](https://github.com/pallets/werkzeug) | 0.16.0 | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0) |
|
||||
| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable) | 1.2 | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2) |
|
||||
| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic) | 2.9.1.1 | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1) |
|
||||
| [nasa/fprime](https://github.com/nasa/fprime) | 1.3 | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3) |
|
||||
| [nucleic/cppy](https://github.com/nucleic/cppy) | 1.1.0 | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0) |
|
||||
| [opencv/opencv](https://github.com/opencv/opencv) | 4.5.1 | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1) |
|
||||
| [curl/curl](https://github.com/curl/curl) | 7.72.0 | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0) |
|
||||
| [madler/zlib](https://github.com/madler/zlib) | 1.2.11 | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11) |
|
||||
| [apache/lucene](https://github.com/apache/lucene) | 7.7.3 | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
|
||||
| [yaml/libyaml](https://github.com/yaml/libyaml) | 0.2.5 | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5) |
|
||||
| [elastic/elasticsearch](https://github.com/elastic/elasticsearch) | 6.8.1 | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1) |
|
||||
| [twbs/bootstrap](https://github.com/twbs/bootstrap) | 4.3.1 | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1) |
|
||||
| [vuejs/vue](https://github.com/vuejs/vue) | 2.6.10 | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10) |
|
||||
| [carrotsearch/hppc](https://github.com/carrotsearch/hppc) | 0.7.1 | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1) |
|
||||
| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time) | 2.10.1 | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1) |
|
||||
| [tdunning/t-digest](https://github.com/tdunning/t-digest) | 3.2 | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2) |
|
||||
| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram) | 2.1.9 | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9) |
|
||||
| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0.7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) |
|
||||
| [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) |
|
||||
| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
|
||||
| {% data variables.product.prodname_dotcom %} Repository | Version | Tag |
|
||||
|---|---|---|
|
||||
| [torvalds/linux](https://github.com/torvalds/linux) | 3.4 | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4) |
|
||||
| [python/cpython](https://github.com/python/cpython) | 3.9.2 | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2) |
|
||||
| [boto/boto3](https://github.com/boto/boto3) | 1.17.17 | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17) |
|
||||
| [boto/botocore](https://github.com/boto/botocore) | 1.20.11 | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11) |
|
||||
| [certifi/python-certifi](https://github.com/certifi/python-certifi) | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05) |
|
||||
| [chardet/chardet](https://github.com/chardet/chardet) | 4.0.0 | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0) |
|
||||
| [matplotlib/cycler](https://github.com/matplotlib/cycler) | 0.10.0 | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0) |
|
||||
| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py) | 6.8.1 | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1) |
|
||||
| [ianare/exif-py](https://github.com/ianare/exif-py) | 2.3.2 | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2) |
|
||||
| [kjd/idna](https://github.com/kjd/idna) | 2.10 | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10) |
|
||||
| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py) | 0.10.0 | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0) |
|
||||
| [nucleic/kiwi](https://github.com/nucleic/kiwi) | 1.3.1 | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1) |
|
||||
| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib) | 3.3.4 | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4) |
|
||||
| [numpy/numpy](https://github.com/numpy/numpy) | 1.20.1 | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1) |
|
||||
| [opencv/opencv-python](https://github.com/opencv/opencv-python) | 4.5.1.48 | [48](https://github.com/opencv/opencv-python/releases/tag/48) |
|
||||
| [python-pillow/Pillow](https://github.com/python-pillow/Pillow) | 8.1.0 | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0) |
|
||||
| [pycurl/pycurl](https://github.com/pycurl/pycurl) | 7.43.0.6 | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.7 | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7) |
|
||||
| [pyserial/pyserial](https://github.com/pyserial/pyserial) | 3.5 | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5) |
|
||||
| [dateutil/dateutil](https://github.com/dateutil/dateutil) | 2.8.1 | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1) |
|
||||
| [yaml/pyyaml ](https://github.com/yaml/pyyaml) | 5.4.1 | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1) |
|
||||
| [psf/requests](https://github.com/psf/requests) | 2.25.1 | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1) |
|
||||
| [boto/s3transfer](https://github.com/boto/s3transfer) | 0.3.4 | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4) |
|
||||
| [enthought/scimath](https://github.com/enthought/scimath) | 4.2.0 | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0) |
|
||||
| [scipy/scipy](https://github.com/scipy/scipy) | 1.6.1 | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1) |
|
||||
| [benjaminp/six](https://github.com/benjaminp/six) | 1.15.0 | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0) |
|
||||
| [enthought/traits](https://github.com/enthought/traits) | 6.2.0 | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0) |
|
||||
| [urllib3/urllib3](https://github.com/urllib3/urllib3) | 1.26.3 | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3) |
|
||||
| [python-attrs/attrs](https://github.com/python-attrs/attrs) | 19.3.0 | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0) |
|
||||
| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/) | 3.2.4 | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4) |
|
||||
| [pallets/click](https://github.com/pallets/click) | 7.0 | [7.0](https://github.com/pallets/click/releases/tag/7.0) |
|
||||
| [pallets/flask](https://github.com/pallets/flask) | 1.1.1 | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1) |
|
||||
| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7 | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7) |
|
||||
| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig) | 1.0.0 | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0) |
|
||||
| [pallets/itsdangerous](https://github.com/pallets/itsdangerous) | 1.1.0 | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0) |
|
||||
| [pallets/jinja](https://github.com/pallets/jinja) | 2.10.3 | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3) |
|
||||
| [lxml/lxml](https://github.com/lxml/lxml) | 4.4.1 | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1) |
|
||||
| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown) | 3.1.1 | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1) |
|
||||
| [pallets/markupsafe](https://github.com/pallets/markupsafe) | 1.1.1 | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1) |
|
||||
| [pypa/packaging](https://github.com/pypa/packaging) | 19.2 | [19.2](https://github.com/pypa/packaging/releases/tag/19.2) |
|
||||
| [pexpect/pexpect](https://github.com/pexpect/pexpect) | 4.7.0 | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0) |
|
||||
| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy) | 0.13.0 | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0) |
|
||||
| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess) | 0.6.0 | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0) |
|
||||
| [pytest-dev/py](https://github.com/pytest-dev/py) | 1.8.0 | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.5 | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5) |
|
||||
| [pytest-dev/pytest](https://github.com/pytest-dev/pytest) | 5.3.0 | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0) |
|
||||
| [stub42/pytz](https://github.com/stub42/pytz) | 2019.3 | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3) |
|
||||
| [uiri/toml](https://github.com/uiri/toml) | 0.10.0 | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0) |
|
||||
| [pallets/werkzeug](https://github.com/pallets/werkzeug) | 0.16.0 | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0) |
|
||||
| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable) | 1.2 | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2) |
|
||||
| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic) | 2.9.1.1 | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1) |
|
||||
| [nasa/fprime](https://github.com/nasa/fprime) | 1.3 | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3) |
|
||||
| [nucleic/cppy](https://github.com/nucleic/cppy) | 1.1.0 | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0) |
|
||||
| [opencv/opencv](https://github.com/opencv/opencv) | 4.5.1 | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1) |
|
||||
| [curl/curl](https://github.com/curl/curl) | 7.72.0 | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0) |
|
||||
| [madler/zlib](https://github.com/madler/zlib) | 1.2.11 | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11) |
|
||||
| [apache/lucene](https://github.com/apache/lucene) | 7.7.3 | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
|
||||
| [yaml/libyaml](https://github.com/yaml/libyaml) | 0.2.5 | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5) |
|
||||
| [elastic/elasticsearch](https://github.com/elastic/elasticsearch) | 6.8.1 | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1) |
|
||||
| [twbs/bootstrap](https://github.com/twbs/bootstrap) | 4.3.1 | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1) |
|
||||
| [vuejs/vue](https://github.com/vuejs/vue) | 2.6.10 | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10) |
|
||||
| [carrotsearch/hppc](https://github.com/carrotsearch/hppc) | 0.7.1 | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1) |
|
||||
| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time) | 2.10.1 | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1) |
|
||||
| [tdunning/t-digest](https://github.com/tdunning/t-digest) | 3.2 | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2) |
|
||||
| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram) | 2.1.9 | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9) |
|
||||
| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0.7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) |
|
||||
| [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) |
|
||||
| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [プロフィールについて](/articles/about-your-profile)
|
||||
- "[About your profile](/articles/about-your-profile)"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: プロフィールにアイテムをピン止めする
|
||||
intro: Gist とリポジトリをプロフィールに固定して、他のユーザがあなたの最高の作品をすばやく確認できるようにすることができます。
|
||||
title: Pinning items to your profile
|
||||
intro: You can pin gists and repositories to your profile so other people can quickly see your best work.
|
||||
redirect_from:
|
||||
- /articles/pinning-repositories-to-your-profile/
|
||||
- /articles/pinning-repositories-to-your-profile
|
||||
- /articles/pinning-items-to-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile
|
||||
@@ -14,22 +14,26 @@ topics:
|
||||
- Profiles
|
||||
shortTitle: Pin items
|
||||
---
|
||||
You can pin a public repository if you own the repository or you've made contributions to the repository. Commits to forks don't count as contributions, so you can't pin a fork that you don't own. For more information, see "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
|
||||
|
||||
あなたが所有するか、コントリビュートしたパブリックリポジトリをピン止めできます。 フォークへのコミットはコントリビューションとして扱われないので、所有していないフォークをピン止めすることはできません。 詳細は「[プロフィール上でコントリビューションが表示されない理由](/articles/why-are-my-contributions-not-showing-up-on-my-profile)」を参照してください。
|
||||
You can pin any public gist you own.
|
||||
|
||||
所有しているパブリック Gist をピン止めできます。
|
||||
Pinned items include important information about the item, like the number of stars a repository has received or the first few lines of a gist. Once you pin items to your profile, the "Pinned" section replaces the "Popular repositories" section on your profile.
|
||||
|
||||
ピン止めしたアイテムには、リポジトリが受け取った Star の数や、Gist の最初の数行など、アイテムに関する重要な情報が含まれます。 アイテムをプロフィールにピン止めすると、プロフィールで [Popular repositories] セクションが [Pinned] セクションに変わります。
|
||||
|
||||
[Pinned] セクションでは、アイテムを並べ替えることができます。 ピンの右上隅で {% octicon "grabber" aria-label="The grabber symbol" %} をクリックして、ピンを新しい場所にドラッグしてください。
|
||||
You can reorder the items in the "Pinned" section. In the upper-right corner of a pin, click {% octicon "grabber" aria-label="The grabber symbol" %} and drag the pin to a new location.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
2. [Popular repositories] または [Pinned] セクションで、[**Customize your pins**] をクリックします。 ![[Customize your pins] ボタン](/assets/images/help/profile/customize-pinned-repositories.png)
|
||||
3. ピン止めするアイテムを検索できるリストで、[Repositories] か [Gists]、または両方を選択します。
|
||||
4. オプションで、特定のアイテムを探しやすいように、フィールドフィールドでユーザ、Organization、リポジトリ、Gist の名前を入力します。
|
||||
5. 最大 6 つのリポジトリ、Gist を組み合わせて表示できます。 
|
||||
6. [**Save pins**] をクリックします。 ![[Save pins] ボタン](/assets/images/help/profile/save-pinned-repositories.png)
|
||||
2. In the "Popular repositories" or "Pinned" section, click **Customize your pins**.
|
||||
|
||||
3. To display a searchable list of items to pin, select "Repositories", "Gists", or both.
|
||||
|
||||
4. Optionally, to make it easier to find a specific item, in the filter field, type the name of a user, organization, repository, or gist.
|
||||
|
||||
5. Select a combination of up to six repositories and/or gists to display.
|
||||
|
||||
6. Click **Save pins**.
|
||||
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [プロフィールについて](/articles/about-your-profile)
|
||||
- "[About your profile](/articles/about-your-profile)"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Sending enterprise contributions to your GitHub.com profile
|
||||
intro: 'You can highlight your work on {% data variables.product.prodname_enterprise %} by sending the contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile.'
|
||||
redirect_from:
|
||||
- /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/
|
||||
- /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile
|
||||
- /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile
|
||||
- /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Viewing contributions on your profile
|
||||
intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.'
|
||||
redirect_from:
|
||||
- /articles/viewing-contributions/
|
||||
- /articles/viewing-contributions-on-your-profile-page/
|
||||
- /articles/viewing-contributions
|
||||
- /articles/viewing-contributions-on-your-profile-page
|
||||
- /articles/viewing-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 個人リポジトリに対するアクセスを管理する
|
||||
intro: 自分の個人アカウントで所有しているリポジトリに対するコラボレーター アクセス権を、ユーザに付与できます。
|
||||
title: Managing access to your personal repositories
|
||||
intro: You can give people collaborator access to repositories owned by your personal account.
|
||||
redirect_from:
|
||||
- /categories/101/articles/
|
||||
- /categories/managing-repository-collaborators/
|
||||
- /categories/101/articles
|
||||
- /categories/managing-repository-collaborators
|
||||
- /articles/managing-access-to-your-personal-repositories
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories
|
||||
product: '{% data reusables.gated-features.user-repo-collaborators %}'
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: コラボレーターを個人リポジトリに招待する
|
||||
intro: '個人リポジトリにコラボレーターとして{% ifversion fpt or ghec %}ユーザを招待{% else %}ユーザを追加{% endif %}することができます。'
|
||||
title: Inviting collaborators to a personal repository
|
||||
intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
|
||||
redirect_from:
|
||||
- /articles/how-do-i-add-a-collaborator/
|
||||
- /articles/adding-collaborators-to-a-personal-repository/
|
||||
- /articles/how-do-i-add-a-collaborator
|
||||
- /articles/adding-collaborators-to-a-personal-repository
|
||||
- /articles/inviting-collaborators-to-a-personal-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
|
||||
@@ -18,8 +18,7 @@ topics:
|
||||
- Repositories
|
||||
shortTitle: Invite collaborators
|
||||
---
|
||||
|
||||
Organization が所有するリポジトリは、細やかなアクセスを許可できます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。
|
||||
Repositories owned by an organization can grant more granular access. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)."
|
||||
|
||||
{% data reusables.organizations.org-invite-expiration %}
|
||||
|
||||
@@ -29,33 +28,39 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
|
||||
|
||||
{% note %}
|
||||
|
||||
**メモ:** {% data variables.product.company_short %} では、24 時間以内にリポジトリに招待できる人数に上限があります。 この上限を超える場合は、24 時間待つか、コラボレーションする人数の多い Organization を作成してください。
|
||||
**Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. コラボレーターとして招待する人のユーザ名を確認してください。{% ifversion fpt or ghec %}まだユーザ名がない場合は、{% data variables.product.prodname_dotcom %}にサインアップできます。詳細は「[新しい {% data variables.product.prodname_dotcom %}アカウントへのサインアップ](/articles/signing-up-for-a-new-github-account)」を参照してください。{% endif %}
|
||||
1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %} For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)".{% endif %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
1. [**Invite a collaborator**] をクリックします。 ![[Invite a collaborator] ボタン](/assets/images/help/repository/invite-a-collaborator-button.png)
|
||||
2. 検索フィールドで、招待する人の名前を入力し、一致するリストの名前をクリックします。 
|
||||
3. [**Add NAME to REPOSITORY**] をクリックします。 
|
||||
1. Click **Invite a collaborator**.
|
||||
|
||||
2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
|
||||
|
||||
3. Click **Add NAME to REPOSITORY**.
|
||||
|
||||
{% else %}
|
||||
5. 左サイドバーで [**Collaborators**] をクリックします。 ![リポジトリの [Settings] サイドバーで [Collaborators] を選択](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
|
||||
6. [Collaborators] で、コラボレーターのユーザ名の入力を始めます。
|
||||
7. ドロップダウンメニューからコラボレーターのユーザ名を選択します。 
|
||||
8. [**Add collaborator**] をクリックします。 
|
||||
5. In the left sidebar, click **Collaborators**.
|
||||
|
||||
6. Under "Collaborators", start typing the collaborator's username.
|
||||
7. Select the collaborator's username from the drop-down menu.
|
||||
|
||||
8. Click **Add collaborator**.
|
||||
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghec %}
|
||||
9. リポジトリへの招待メールがユーザに届きます。 ユーザが招待を受諾すると、そのユーザはコラボレーターとしてリポジトリにアクセスできるようになります。
|
||||
9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
|
||||
{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- "[ユーザ アカウントリポジトリの権限レベル](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
|
||||
- [個人リポジトリからコラボレーターを削除する](/articles/removing-a-collaborator-from-a-personal-repository)
|
||||
- [コラボレーターのリポジトリから自分を削除する](/articles/removing-yourself-from-a-collaborator-s-repository)
|
||||
- [メンバーを Team に編成する](/organizations/organizing-members-into-teams)
|
||||
- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)"
|
||||
- "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)"
|
||||
- "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)"
|
||||
- "[Organizing members into teams](/organizations/organizing-members-into-teams)"
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: 個人リポジトリからコラボレーターを削除する
|
||||
intro: コラボレータをプロジェクトから削除すると、そのコラボレータはリポジトリに対する読み取り/書き込みアクセスを失います。 リポジトリがプライベートであり、その個人がフォークを作成している場合、そのフォークも削除されます。
|
||||
title: Removing a collaborator from a personal repository
|
||||
intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
|
||||
redirect_from:
|
||||
- /articles/how-do-i-remove-a-collaborator/
|
||||
- /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository/
|
||||
- /articles/removing-a-collaborator-from-a-private-repository/
|
||||
- /articles/deleting-a-private-fork-of-a-private-user-repository/
|
||||
- /articles/how-do-i-delete-a-fork-of-my-private-repository/
|
||||
- /articles/how-do-i-remove-a-collaborator
|
||||
- /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
|
||||
- /articles/removing-a-collaborator-from-a-private-repository
|
||||
- /articles/deleting-a-private-fork-of-a-private-user-repository
|
||||
- /articles/how-do-i-delete-a-fork-of-my-private-repository
|
||||
- /articles/removing-a-collaborator-from-a-personal-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository
|
||||
@@ -21,24 +21,26 @@ topics:
|
||||
- Repositories
|
||||
shortTitle: Remove a collaborator
|
||||
---
|
||||
## Deleting forks of private repositories
|
||||
|
||||
## プライベートリポジトリのフォークを削除する
|
||||
While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
|
||||
|
||||
コラボレーターが削除される一方でプライベートリポジトリのフォークが削除されると、その個人はリポジトリのローカルクローンをそのまま保持します。
|
||||
|
||||
## リポジトリへのコントリビューションがある個人からコラボレーター権限を削除する
|
||||
## Removing collaborator permissions from a person contributing to a repository
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
4. 削除するコラボレーターの右で、{% octicon "trash" aria-label="The trash icon" %} をクリックします。 
|
||||
4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
{% else %}
|
||||
3. 左のサイドバーで、[**Collaborators & teams**] をクリックします。 ![[Collaborators] タブ](/assets/images/help/repository/repo-settings-collaborators.png)
|
||||
4. 削除するコラボレーターの横にある [**X**] アイコンをクリックします。 
|
||||
3. In the left sidebar, click **Collaborators & teams**.
|
||||
|
||||
4. Next to the collaborator you want to remove, click the **X** icon.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- 「[チームから Organization メンバーを削除する](/articles/removing-organization-members-from-a-team)」
|
||||
- [外部のコラボレータを Organization のリポジトリから削除する](/articles/removing-an-outside-collaborator-from-an-organization-repository)
|
||||
- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
|
||||
- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: コラボレーターのリポジトリから自分を削除する
|
||||
intro: 他の人の個人リポジトリのコラボレーターを続けたくなくなった場合は、自分を削除できます。
|
||||
title: Removing yourself from a collaborator's repository
|
||||
intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.'
|
||||
redirect_from:
|
||||
- /leave-a-collaborative-repo/
|
||||
- /leave-a-repo/
|
||||
- /articles/removing-yourself-from-a-collaborator-s-repo/
|
||||
- /leave-a-collaborative-repo
|
||||
- /leave-a-repo
|
||||
- /articles/removing-yourself-from-a-collaborator-s-repo
|
||||
- /articles/removing-yourself-from-a-collaborator-s-repository
|
||||
- /articles/removing-yourself-from-a-collaborators-repository
|
||||
- /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
|
||||
@@ -20,8 +20,10 @@ topics:
|
||||
- Repositories
|
||||
shortTitle: Remove yourself
|
||||
---
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. 左のサイドバーで [**Repositories**] をクリックします。 ![[Repositories] タブ](/assets/images/help/settings/settings-sidebar-repositories.png)
|
||||
3. 離脱するリポジトリの横にある [**Leave**] をクリックします。 ![[Leave] ボタン](/assets/images/help/repository/repo-leave.png)
|
||||
4. 警告をよく読んでから [I understand, leave this repository.] をクリックします。 
|
||||
2. In the left sidebar, click **Repositories**.
|
||||
|
||||
3. Next to the repository you want to leave, click **Leave**.
|
||||
|
||||
4. Read the warning carefully, then click "I understand, leave this repository."
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: メール プリファレンスの管理
|
||||
intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. {% data variables.product.product_name %} から受信するメールを管理することもできます。'
|
||||
title: Managing email preferences
|
||||
intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
|
||||
redirect_from:
|
||||
- /categories/managing-email-preferences/
|
||||
- /categories/managing-email-preferences
|
||||
- /articles/managing-email-preferences
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences
|
||||
versions:
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 自分の GitHub ユーザ名またはメールアドレスを忘れた場合は
|
||||
intro: '{% data variables.product.product_location %} へのサインインは久しぶりでしょうか? そうであれば、改めてようこそ。 自分の {% data variables.product.product_name %}ユーザアカウント名を思い出せない場合は、次の方法を試してみてください。'
|
||||
title: Remembering your GitHub username or email
|
||||
intro: 'Are you signing in to {% data variables.product.product_location %} for the first time in a while? If so, welcome back! If you can''t remember your {% data variables.product.product_name %} user account name, you can try these methods for remembering it.'
|
||||
redirect_from:
|
||||
- /articles/oh-noes-i-ve-forgotten-my-username-email/
|
||||
- /articles/oh-noes-i-ve-forgotten-my-username-or-email/
|
||||
- /articles/oh-noes-i-ve-forgotten-my-username-email
|
||||
- /articles/oh-noes-i-ve-forgotten-my-username-or-email
|
||||
- /articles/remembering-your-github-username-or-email
|
||||
- /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email
|
||||
@@ -16,61 +16,60 @@ topics:
|
||||
- Notifications
|
||||
shortTitle: Find your username or email
|
||||
---
|
||||
|
||||
{% mac %}
|
||||
|
||||
## {% data variables.product.prodname_desktop %}ユーザ
|
||||
## {% data variables.product.prodname_desktop %} users
|
||||
|
||||
1. [**GitHub Desktop**] メニューで、[**Preferences**] をクリックします。
|
||||
2. [Preferences] ウィンドウで、次のことについて検証します:
|
||||
- {% data variables.product.product_name %}ユーザ名を表示するには [**Accounts**] をクリックします。
|
||||
- Git メールを表示するには [**Git**] をクリックします。 このメールは [{% data variables.product.product_name %} のプライマリメール](/articles/changing-your-primary-email-address)となることが保証されているわけではありませんので、注意してください。
|
||||
1. In the **GitHub Desktop** menu, click **Preferences**.
|
||||
2. In the Preferences window, verify the following:
|
||||
- To view your {% data variables.product.product_name %} username, click **Accounts**.
|
||||
- To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
## {% data variables.product.prodname_desktop %}ユーザ
|
||||
|
||||
1. [**File**] メニューで、[**Options**] をクリックします。
|
||||
2. [Options] ウィンドウで、次のことについて検証します:
|
||||
- {% data variables.product.product_name %}ユーザ名を表示するには [**Accounts**] をクリックします。
|
||||
- Git メールを表示するには [**Git**] をクリックします。 このメールは [{% data variables.product.product_name %} のプライマリメール](/articles/changing-your-primary-email-address)となることが保証されているわけではありませんので、注意してください。
|
||||
## {% data variables.product.prodname_desktop %} users
|
||||
|
||||
1. In the **File** menu, click **Options**.
|
||||
2. In the Options window, verify the following:
|
||||
- To view your {% data variables.product.product_name %} username, click **Accounts**.
|
||||
- To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
## `user.name` 設定からユーザ名を見つける
|
||||
## Finding your username in your `user.name` configuration
|
||||
|
||||
セットアップ時に、[Git でユーザ名を設定](/github/getting-started-with-github/setting-your-username-in-git)してあることがあります。 その場合は、次の設定で値をレビューします:
|
||||
During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting:
|
||||
|
||||
```shell
|
||||
$ git config user.name
|
||||
# 設定を見る
|
||||
<em>あなたのユーザ名</em>
|
||||
# View the setting
|
||||
<em>YOUR_USERNAME</em>
|
||||
```
|
||||
|
||||
## リモートリポジトリの URL からユーザ名を見つける
|
||||
## Finding your username in the URL of remote repositories
|
||||
|
||||
作成またはフォークしたパーソナルリポジトリのローカルコピーがある場合は、リモートリポジトリの URL をチェックします。
|
||||
If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**参考**: この方法が使えるのは、元のリポジトリか他の個人のリポジトリの独自のフォークがある場合のみです。 他の個人のリポジトリのクローンを作成した場合、ご自分のではなく、その個人のユーザ名が表示されます。 同様に、Organization リポジトリでは、リモート URL の特定のユーザのではなく Organization の名前が表示されます。
|
||||
**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
```shell
|
||||
$ cd <em>ご使用のリポジトリ</em>
|
||||
# 初期化された Git リポジトリへディレクトリを変更する
|
||||
$ cd <em>YOUR_REPOSITORY</em>
|
||||
# Change directories to the initialized Git repository
|
||||
$ git remote -v
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>ご使用のユーザ名</em>/<em>ご使用のリポジトリ</em>.git (fetch)
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>ご使用のユーザ名</em>/<em>ご使用のリポジトリ</em>.git (push)
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
ご使用のユーザ名は `https://{% data variables.command_line.backticks %}/` の直後にあるものです。
|
||||
Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- "[メールアドレスを検証する](/articles/verifying-your-email-address)"
|
||||
- "[Verifying your email address](/articles/verifying-your-email-address)"
|
||||
{% endif %}
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
---
|
||||
title: コミットメールアドレスを設定する
|
||||
intro: '{% data variables.product.product_location %} とコンピュータ上でコミットを作成するために使用するメールアドレスを設定できます。'
|
||||
title: Setting your commit email address
|
||||
intro: 'You can set the email address that is used to author commits on {% data variables.product.product_location %} and on your computer.'
|
||||
redirect_from:
|
||||
- /articles/keeping-your-email-address-private/
|
||||
- /articles/setting-your-commit-email-address-on-github/
|
||||
- /articles/about-commit-email-addresses/
|
||||
- /articles/git-email-settings/
|
||||
- /articles/setting-your-email-in-git/
|
||||
- /articles/set-your-user-name-email-and-github-token/
|
||||
- /articles/setting-your-commit-email-address-in-git/
|
||||
- /articles/keeping-your-email-address-private
|
||||
- /articles/setting-your-commit-email-address-on-github
|
||||
- /articles/about-commit-email-addresses
|
||||
- /articles/git-email-settings
|
||||
- /articles/setting-your-email-in-git
|
||||
- /articles/set-your-user-name-email-and-github-token
|
||||
- /articles/setting-your-commit-email-address-in-git
|
||||
- /articles/setting-your-commit-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address
|
||||
@@ -22,30 +22,29 @@ topics:
|
||||
- Notifications
|
||||
shortTitle: Set commit email address
|
||||
---
|
||||
## About commit email addresses
|
||||
|
||||
## コミットメールアドレスについて
|
||||
{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
|
||||
|
||||
{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.product_location %}. コマンドラインからプッシュするコミットや、WebベースのGit操作に関連づけられるメールアドレスは選択できます。
|
||||
For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
|
||||
|
||||
For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. コマンドラインからプッシュするコミットについては、Git のコミットメールアドレスを設定できます。
|
||||
|
||||
{% ifversion fpt or ghec %}コミットメールアドレスの変更前に行ったコミットは、変更前のメールアドレスに関連づけられたままとなります。{% else %}{% data variables.product.product_name %} 上のコミットメールアドレスを変更した後、新規メールアドレスは、今後のウェブベースの Git オペレーションのすべてで表示されます。 コミットメールアドレスを変更する前のコミットは、変更前のメールアドレスに関連付けられたままとなります。{% endif %}
|
||||
{% ifversion fpt or ghec %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.product_name %}, the new email address will be visible in all of your future web-based Git operations by default. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**参考**:{% data reusables.user_settings.no-verification-disposable-emails %}
|
||||
**Note**: {% data reusables.user_settings.no-verification-disposable-emails %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` email address from {% data variables.product.product_name %} as your commit email address. コマンドラインからプッシュするコミットに対して`noreply`メールアドレスを使いたい場合には、そのメールアドレスを Git のコミットメールアドレスの設定で使用してください。 Web ベースの Git 操作に `noreply` アドレスを使いたい場合には、GitHub でコミットメールアドレスの設定を行い、[**Keep my email address private**] を選択してください。
|
||||
{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
|
||||
|
||||
また、個人のメールアドレスを公開するコマンドラインからプッシュされたコミットをブロックするよう選択することもできます。 詳細は「[個人のメールを公開するコマンドラインプッシュのブロック](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)」を参照してください。{% endif %}
|
||||
You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
|
||||
|
||||
To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}詳しい情報については、「[{% data variables.product.prodname_dotcom %} アカウントにメールアドレスを追加する](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)」を参照してください。{% endif %}
|
||||
To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
@@ -55,9 +54,9 @@ To ensure that commits are attributed to you and appear in your contributions gr
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. 詳細は「[{% data variables.product.prodname_dotcom %} ユーザ名を変更する](/articles/changing-your-github-username)」を参照してください。{% endif %}
|
||||
If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_dotcom %} のコミットメールアドレスを設定する
|
||||
## Setting your commit email address on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
{% data reusables.files.commit-author-email-options %}
|
||||
|
||||
@@ -67,11 +66,11 @@ If you use your `noreply` email address for {% data variables.product.product_na
|
||||
{% data reusables.user_settings.select_primary_email %}{% ifversion fpt or ghec %}
|
||||
{% data reusables.user_settings.keeping_your_email_address_private %}{% endif %}
|
||||
|
||||
## Git のコミットメールアドレスを設定する
|
||||
## Setting your commit email address in Git
|
||||
|
||||
`git config`コマンドを使用して、Git コミットに関連付けられているメールアドレスを変更できます。 設定した新しいメールアドレスは、コマンドラインから {% data variables.product.product_location %} にプッシュするこれからのコミットに表示されます。 コミットメールアドレスを変更する前のコミットは、まだ過去のメールアドレスに関連付けられます。
|
||||
You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.product.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
|
||||
|
||||
### コンピュータにあるすべてのリポジトリ用にメールアドレスを設定する
|
||||
### Setting your email address for every repository on your computer
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. {% data reusables.user_settings.set_your_email_address_in_git %}
|
||||
@@ -85,14 +84,14 @@ If you use your `noreply` email address for {% data variables.product.product_na
|
||||
```
|
||||
4. {% data reusables.user_settings.link_email_with_your_account %}
|
||||
|
||||
### 単一リポジトリ用にメールアドレスを設定する
|
||||
### Setting your email address for a single repository
|
||||
|
||||
{% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.product.product_location %}.
|
||||
|
||||
単一のリポジトリで作成するコミットに関連するメールアドレスを変更できます。 この 1 つのリポジトリの Git コンフィグ設定を上書きしますが、他のリポジトリには影響しません。
|
||||
You can change the email address associated with commits you make in a single repository. This will override your global Git config settings in this one repository, but will not affect any other repositories.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 現在のワーキングディレクトリを Git コミットと関連付けたメールアドレスを設定したいローカルリポジトリに変更します。
|
||||
2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
|
||||
3. {% data reusables.user_settings.set_your_email_address_in_git %}
|
||||
```shell
|
||||
$ git config user.email "<em>email@example.com</em>"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: About your personal dashboard
|
||||
redirect_from:
|
||||
- /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github/
|
||||
- /articles/opting-into-the-public-beta-for-a-new-dashboard/
|
||||
- /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github
|
||||
- /articles/opting-into-the-public-beta-for-a-new-dashboard
|
||||
- /articles/about-your-personal-dashboard
|
||||
- /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard
|
||||
|
||||
@@ -2,10 +2,10 @@
|
||||
title: Changing your GitHub username
|
||||
intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/how-to-change-your-username/
|
||||
- /articles/changing-your-github-user-name/
|
||||
- /articles/renaming-a-user/
|
||||
- /articles/what-happens-when-i-change-my-username/
|
||||
- /articles/how-to-change-your-username
|
||||
- /articles/changing-your-github-user-name
|
||||
- /articles/renaming-a-user
|
||||
- /articles/what-happens-when-i-change-my-username
|
||||
- /articles/changing-your-github-username
|
||||
- /github/setting-up-and-managing-your-github-user-account/changing-your-github-username
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: ユーザを Organization に変換する
|
||||
title: Converting a user into an organization
|
||||
redirect_from:
|
||||
- /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization/
|
||||
- /articles/explaining-the-account-transformation-warning/
|
||||
- /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
|
||||
- /articles/explaining-the-account-transformation-warning
|
||||
- /articles/converting-a-user-into-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
|
||||
intro: ユーザアカウントは、Organization に変換できます。 これにより、Organization に属するリポジトリに対して、より細かく権限を設定できます。
|
||||
intro: You can convert your user account into an organization. This allows more granular permissions for repositories that belong to the organization.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -15,53 +15,55 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: User into an organization
|
||||
---
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**: ユーザを Organization に変換する前に、以下の点についてご注意ください:
|
||||
**Warning**: Before converting a user into an organization, keep these points in mind:
|
||||
|
||||
- 変換したユーザアカウントには、サインイン**できなくなります**。
|
||||
- 変換したユーザアカウントが所有していた Gist を作成や変更することは**できなくなります**。
|
||||
- Organization をユーザに変換して元に戻すことは**できません**。
|
||||
- SSH キー、OAuth トークン、ジョブプロフィール、リアクション、および関連するユーザ情報は、Organization に移譲**されません**。 これは、変換されたユーザアカウントのみに該当し、ユーザアカウントのコラボレーターには該当しません。
|
||||
- 変換したユーザアカウントによるコミットは、アカウントに**リンクされなくなります**。 コミットそのものは、**そのまま残ります**。
|
||||
- You will **no longer** be able to sign into the converted user account.
|
||||
- You will **no longer** be able to create or modify gists owned by the converted user account.
|
||||
- An organization **cannot** be converted back to a user.
|
||||
- The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the user account that's being converted, not any of the user account's collaborators.
|
||||
- Any commits made with the converted user account **will no longer be linked** to that account. The commits themselves **will** remain intact.
|
||||
- Any forks of private repositories made with the converted user account will be deleted.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## 個人ユーザアカウントを保ち、新しい Organization を手動で作成する
|
||||
## Keep your personal user account and create a new organization manually
|
||||
|
||||
Organization の名前を、あなたの個人アカウントが使用しているものと同じにしたい場合や、個人のユーザアカウント情報をそのまま残しておきたい場合は、ユーザアカウントを Organization に変換するのではなく、新しい Organization を作成して、そこへリポジトリを移譲する必要があります。
|
||||
If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal user account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your user account into an organization.
|
||||
|
||||
1. 現在のユーザアカウント名を個人的に使いたい場合は、[個人ユーザアカウント名を変更](/articles/changing-your-github-username)し、何か新しくて素敵な名前を付けましょう。
|
||||
2. 元の個人アカウント名で、[新しい Organization を作成](/articles/creating-a-new-organization-from-scratch)します。
|
||||
3. 新しい Organization アカウントに[リポジトリを移譲](/articles/transferring-a-repository)します。
|
||||
1. To retain your current user account name for your personal use, [change the name of your personal user account](/articles/changing-your-github-username) to something new and wonderful.
|
||||
2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal user account.
|
||||
3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.
|
||||
|
||||
## 個人アカウントを Organization に自動で変換する
|
||||
## Convert your personal account into an organization automatically
|
||||
|
||||
あなたの個人ユーザアカウントを Organization に直接変換することも可能です。 アカウントを変換すると、以下のことが起こります:
|
||||
- リポジトリはそのまま保持されます。他のアカウントに手動で移譲する必要はありません。
|
||||
- コラボレーターを、Team に自動的に招待します。コラボレーターの権限は、以前のものがそのまま引き継がれます。
|
||||
{% ifversion fpt or ghec %}- {% data variables.product.prodname_pro %} のユーザアカウントでは、支払い情報の入力や支払いサイクルの調整も必要なく、また二重の支払いもすることなく、自動的に[有料 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) に移行できます。{% endif %}
|
||||
You can also convert your personal user account directly into an organization. Converting your account:
|
||||
- Preserves the repositories as they are without the need to transfer them to another account manually
|
||||
- Automatically invites collaborators to teams with permissions equivalent to what they had before
|
||||
{% ifversion fpt or ghec %}- For user accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
|
||||
|
||||
1. GitHub にサインインし、変換後に Organization やリポジトリにアクセスするために使う、新しい個人アカウントを作成します。
|
||||
2. 変換するアカウントで参加している、[すべての Organization から自分を削除](/articles/removing-yourself-from-an-organization)してください。
|
||||
1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
|
||||
2. [Leave any organizations](/articles/removing-yourself-from-an-organization) the user account you're converting has joined.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.organizations %}
|
||||
5. [Transform account] で、[**Turn <username> into an organization**] をクリックします。 
|
||||
6. [Account Transformation Warning] ダイアログボックスで、変換に関する情報を読み、変換を確定します。 このボックスに記載されている情報は、この記事で上述したものと同じです。 
|
||||
7. [Transform your user into an organization] ページの、[Choose an organization owner] で、前のセクションで作成したセカンダリの個人アカウントか、Organization の管理を信頼して任せられる他のユーザを選択します。 
|
||||
8. 入力を求められた場合、Organization の新しいプランを選択し、支払い情報を入力します。
|
||||
9. [**Create Organization**] をクリックします。
|
||||
10. ステップ 1 で作成した、新しいユーザアカウントにサインインし、コンテキストスイッチャーを使って新しい Organization にアクセスします。
|
||||
5. Under "Transform account", click **Turn <username> into an organization**.
|
||||
|
||||
6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
|
||||
|
||||
7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
|
||||
|
||||
8. Choose your new organization's subscription and enter your billing information if prompted.
|
||||
9. Click **Create Organization**.
|
||||
10. Sign in to the new user account you created in step one, then use the context switcher to access your new organization.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント**: ユーザアカウントを Organization に変換した場合、アカウントに属していたリポジトリのコラボレーターは、新しい Organization に*外部コラボレーター*として追加されます。 希望する場合は、*外部コラボレーター*を新しい Organization のメンバーに招待できます。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
**Tip**: When you convert a user account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 参考リンク
|
||||
- [Team の設定](/articles/setting-up-teams)
|
||||
{% ifversion fpt or ghec %}-"[Organization に参加するようユーザを招待する](/articles/inviting-users-to-join-your-organization){% endif %}
|
||||
- [Organization にアクセスする](/articles/accessing-an-organization)
|
||||
## Further reading
|
||||
- "[Setting up teams](/articles/setting-up-teams)"
|
||||
{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
|
||||
- "[Accessing an organization](/articles/accessing-an-organization)"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 自分のユーザアカウントの削除
|
||||
intro: 'いつでも自分の {% data variables.product.product_name %}ユーザアカウントを削除できます。'
|
||||
title: Deleting your user account
|
||||
intro: 'You can delete your {% data variables.product.product_name %} user account at any time.'
|
||||
redirect_from:
|
||||
- /articles/deleting-a-user-account/
|
||||
- /articles/deleting-a-user-account
|
||||
- /articles/deleting-your-user-account
|
||||
- /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account
|
||||
@@ -12,39 +12,40 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: ユーザアカウントを削除
|
||||
shortTitle: Delete your user account
|
||||
---
|
||||
|
||||
自分のユーザアカウントを削除すると、リポジトリ、プライベートリポジトリのフォーク、ウィキ、Issue、プルリクエスト、また自分のアカウントが所有しているページもすべて削除されます。 {% ifversion fpt or ghec %} 他のユーザが所有するリポジトリでこれまで作成した Issue とプルリクエスト、また行ったコメントが削除されることはなく、代わりに [ゴーストユーザ](https://github.com/ghost)に関連付けられます。{% else %}他のユーザが所有するリポジトリでこれまで作成した Issue とプルリクエスト、また行ったコメントが削除されることはありません。{% endif %}
|
||||
Deleting your user account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %} Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted - instead, they'll be associated with our [Ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %} When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.product.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %}
|
||||
|
||||
あなたが Organization のただ一人のオーナーの場合は、ユーザアカウントを削除する前に、所有権を他の人に移譲するか、Organization を削除する必要があります。 Organization に別のオーナーがいる場合は、自分のユーザアカウントを削除する前に、Organization から自分を削除する必要があります。
|
||||
If you’re the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your user account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your user account.
|
||||
|
||||
詳しい情報については、以下を参照してください。
|
||||
- "[Organization の所有権の移譲](/articles/transferring-organization-ownership)"
|
||||
- "[Organization アカウントの削除](/articles/deleting-an-organization-account)"
|
||||
- "[Organization から自分を削除する](/articles/removing-yourself-from-an-organization/)"
|
||||
For more information, see:
|
||||
- "[Transferring organization ownership](/articles/transferring-organization-ownership)"
|
||||
- "[Deleting an organization account](/articles/deleting-an-organization-account)"
|
||||
- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)"
|
||||
|
||||
## アカウントデータのバックアップ
|
||||
## Back up your account data
|
||||
|
||||
自分のユーザアカウントを削除する前に、リポジトリ、プライベートフォーク、ウィキ、Issue、また自分のアカウントが所有しているプルリクエストすべてのコピーを作成します。
|
||||
Before you delete your user account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告:** 一度ユーザアカウントを削除すると、GitHub はそのコンテンツを復元できません。
|
||||
**Warning:** Once your user account has been deleted, GitHub cannot restore your content.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## ユーザアカウントを削除
|
||||
## Delete your user account
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.account_settings %}
|
||||
3. アカウント設定ページの下部にある [Delete account] の下で [**Delete your account**] をクリックします。 自分のユーザアカウントを削除する前にすべきことは次のとおりです:
|
||||
- 自分が Organization で唯一のオーナーの場合、Organization を削除する前に所有権を別の人に移譲する必要があります。
|
||||
- Organization に別のオーナーがいる場合は、自分自身を Organization から削除する必要があります。 
|
||||
4. [Make sure you want to do this] ダイアログボックスで、アカウントを削除すると何が起こるか理解したことを確認する手順を完了させます: 
|
||||
3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your user account:
|
||||
- If you're the only owner in the organization, you must transfer ownership to another person or delete your organization.
|
||||
- If there are other organization owners in the organization, you must remove yourself from the organization.
|
||||
|
||||
4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted:
|
||||
|
||||
{% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days.
|
||||
{% else %}- リポジトリ、プライベートリポジトリのフォーク、ウィキ、Issue、プルリクエスト、そして自分のアカウントが所有しているページが、すべて削除されること、ユーザ名が {% data variables.product.product_name %} 上で誰でも使用できるようになることを再確認します。
|
||||
{% endif %}- 最初のフィールドに、自分の {% data variables.product.product_name %}ユーザ名またはメールアドレスを入力してください。
|
||||
- 2 番目のフィールドに、指示されたとおりのフレーズを入力してください。
|
||||
{% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}.
|
||||
{% endif %}- In the first field, type your {% data variables.product.product_name %} username or email.
|
||||
- In the second field, type the phrase from the prompt.
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Managing user account settings
|
||||
intro: 'You can change several settings for your personal account, including changing your username and deleting your account.'
|
||||
redirect_from:
|
||||
- /categories/29/articles/
|
||||
- /categories/user-accounts/
|
||||
- /categories/29/articles
|
||||
- /categories/user-accounts
|
||||
- /articles/managing-user-account-settings
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings
|
||||
versions:
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: ユーザ アカウントのプロジェクトボードに対するアクセスを管理する
|
||||
intro: プロジェクトボードのオーナーは、コラボレーターを追加または削除して、そのプロジェクトボードに対する権限をカスタマイズすることができます。
|
||||
title: Managing access to your user account's project boards
|
||||
intro: 'As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.'
|
||||
redirect_from:
|
||||
- /articles/managing-project-boards-in-your-repository-or-organization/
|
||||
- /articles/managing-project-boards-in-your-repository-or-organization
|
||||
- /articles/managing-access-to-your-user-account-s-project-boards
|
||||
- /articles/managing-access-to-your-user-accounts-project-boards
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards
|
||||
@@ -16,20 +16,21 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: Manage access project boards
|
||||
---
|
||||
A collaborator is a person who has permissions to a project board you own. A collaborator's permissions will default to read access. For more information, see "[Permission levels for user-owned project boards](/articles/permission-levels-for-user-owned-project-boards)."
|
||||
|
||||
コラボレーターは、あなたが所有しているプロジェクトボードにアクセスを許可されているユーザです。 コラボレーターの権限は、デフォルトでは読み取りアクセスになります。 詳細は「[ユーザ所有のプロジェクトボードの権限レベル](/articles/permission-levels-for-user-owned-project-boards)」を参照してください。
|
||||
## Inviting collaborators to a user-owned project board
|
||||
|
||||
## ユーザ所有のプロジェクトボードにコラボレーターを招待する
|
||||
|
||||
1. アプリケーションを追加したいプロジェクトボードに移動します。
|
||||
1. Navigate to the project board where you want to add an collaborator.
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
{% data reusables.project-management.collaborator-option %}
|
||||
5. [Search by username, full name or email address] で、コラボレーターの名前、ユーザ名、または {% data variables.product.prodname_dotcom %} メールを入力します。 
|
||||
5. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
|
||||
|
||||
{% data reusables.project-management.add-collaborator %}
|
||||
7. 新しいコラボレーターは、デフォルトで読み取り権限を持ちます。 オプションで、新しいコラボレータの名前の隣にあるドロップダウン メニューを使って、権限レベルを変更することもできます。 ![[Collaborators] セクションで [Permissions] ドロップダウン メニューを選択](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
|
||||
7. The new collaborator has read permissions by default. Optionally, next to the new collaborator's name, use the drop-down menu and choose a different permission level.
|
||||
|
||||
|
||||
## ユーザ所有のプロジェクトボードからコラボレーターを削除する
|
||||
## Removing a collaborator from a user-owned project board
|
||||
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 複数のユーザアカウントをマージする
|
||||
intro: 業務用と個人用に別々のアカウントを持っている場合は、アカウントをマージできます。
|
||||
title: Merging multiple user accounts
|
||||
intro: 'If you have separate accounts for work and personal use, you can merge the accounts.'
|
||||
redirect_from:
|
||||
- /articles/can-i-merge-two-accounts/
|
||||
- /articles/keeping-work-and-personal-repositories-separate/
|
||||
- /articles/can-i-merge-two-accounts
|
||||
- /articles/keeping-work-and-personal-repositories-separate
|
||||
- /articles/merging-multiple-user-accounts
|
||||
- /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts
|
||||
@@ -14,18 +14,17 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: Merge multiple user accounts
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** 個人用リポジトリ、業務用リポジトリの両方を 1 つのユーザ アカウントで管理するようお勧めします。
|
||||
**Tip:** We recommend using only one user account to manage both personal and professional repositories.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. 削除するアカウントから、残しておくアカウントに[リポジトリを委譲](/articles/how-to-transfer-a-repository)します。 Issue、プルリクエスト、ウィキも移譲されます。 リポジトリが、残しておくアカウントに存在することを確認します。
|
||||
2. 移動したリポジトリにクローンがある場合は、その[リモート URL を更新](/github/getting-started-with-github/managing-remote-repositories) します。
|
||||
3. 使わなくなる[アカウントを削除](/articles/deleting-your-user-account)します。
|
||||
4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. 詳細は「[コントリビューションがプロフィールに表示されないのはなぜですか？](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)」を参照してください。
|
||||
1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
|
||||
2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved.
|
||||
3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use.
|
||||
4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see "[Why are my contributions not showing up on my profile?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- 「[{% data variables.product.prodname_dotcom %}アカウントの種類](/articles/types-of-github-accounts)」
|
||||
- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: Organization へのアクセス
|
||||
intro: 自分がメンバーになっている Organization にアクセスするには、個人ユーザアカウントにサインインしなければなりません。
|
||||
title: Accessing an organization
|
||||
intro: 'To access an organization that you''re a member of, you must sign in to your personal user account.'
|
||||
redirect_from:
|
||||
- /articles/error-cannot-log-in-that-account-is-an-organization/
|
||||
- /articles/cannot-log-in-that-account-is-an-organization/
|
||||
- /articles/how-do-i-access-my-organization-account/
|
||||
- /articles/error-cannot-log-in-that-account-is-an-organization
|
||||
- /articles/cannot-log-in-that-account-is-an-organization
|
||||
- /articles/how-do-i-access-my-organization-account
|
||||
- /articles/accessing-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/accessing-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization
|
||||
@@ -16,10 +16,9 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** Organization のオーナーだけが、Organization のアカウント設定を見て変更できます。
|
||||
**Tip:** Only organization owners can see and change the account settings for an organization.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Organization のメンバーシップを公開または非公開にする
|
||||
intro: 自分がどの Organization に属しているかを知らせたい場合は、Organization のアバターをプロフィールに表示することができます。
|
||||
title: Publicizing or hiding organization membership
|
||||
intro: 'If you''d like to tell the world which organizations you belong to, you can display the avatars of the organizations on your profile.'
|
||||
redirect_from:
|
||||
- /articles/publicizing-or-concealing-organization-membership/
|
||||
- /articles/publicizing-or-concealing-organization-membership
|
||||
- /articles/publicizing-or-hiding-organization-membership
|
||||
- /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership
|
||||
@@ -15,15 +15,16 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: Show or hide membership
|
||||
---
|
||||
|
||||
|
||||
![[Profile organizations] ボックス](/assets/images/help/profile/profile_orgs_box.png)
|
||||
|
||||
## Organization のメンバーシップの可視性を変更する
|
||||
## Changing the visibility of your organization membership
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user_settings.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
4. メンバーのリストで自分のユーザ名を探します。 リストが大きい場合は、検索ボックスでユーザ名を検索できます。 ![[Organization member search] ボックス](/assets/images/help/organizations/member-search-box.png)
|
||||
5. ユーザ名の右にあるメニューで、新しい可視性オプションを選択します:
|
||||
- メンバーシップを公開する場合は [**Public**] を選択します。
|
||||
- メンバーシップを非公開にする場合は [**Private**] を選択します。 
|
||||
4. Locate your username in the list of members. If the list is large, you can search for your username in the search box.
|
||||
|
||||
5. In the menu to the right of your username, choose a new visibility option:
|
||||
- To publicize your membership, choose **Public**.
|
||||
- To hide your membership, choose **Private**.
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Organization から自分を削除する
|
||||
intro: あなたは、ある Organization の外部コラボレーターまたはメンバーになっている場合、その Organization からいつでも離脱できます。
|
||||
title: Removing yourself from an organization
|
||||
intro: 'If you''re an outside collaborator or a member of an organization, you can leave the organization at any time.'
|
||||
redirect_from:
|
||||
- /articles/how-do-i-remove-myself-from-an-organization/
|
||||
- /articles/how-do-i-remove-myself-from-an-organization
|
||||
- /articles/removing-yourself-from-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization
|
||||
@@ -15,14 +15,13 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: Leave an organization
|
||||
---
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告:** 現在 Organization で {% data variables.product.product_name %} の支払いを担当している場合、ご自身を Organization から削除しても、Organization のファイルの支払い情報は更新**されません**。 現在支払いを担当している場合は、Organization の別のコードオーナーまたは支払いマネージャーに、[Organization の支払い方法を更新](/articles/adding-or-editing-a-payment-method)してもらう**必要があります** 。
|
||||
**Warning:** If you're currently responsible for paying for {% data variables.product.product_name %} in your organization, removing yourself from the organization **does not** update the billing information on file for the organization. If you are currently responsible for billing, **you must** have another owner or billing manager for the organization [update the organization's payment method](/articles/adding-or-editing-a-payment-method).
|
||||
|
||||
詳細は「[Organization の所有権を移譲する](/articles/transferring-organization-ownership)」を参照してください。
|
||||
For more information, see "[Transferring organization ownership](/articles/transferring-organization-ownership)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -30,4 +29,5 @@ shortTitle: Leave an organization
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.organizations %}
|
||||
3. [Organizations] の下で、自分を削除する Organization を見つけ、[**Leave**] をクリックします。 ![ロールが表示され、その横に [Leave] ボタンがある](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
|
||||
3. Under "Organizations", find the organization you'd like to remove yourself from, then click **Leave**.
|
||||
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: OAuth App に対する Organization の承認をリクエストする
|
||||
intro: 'Organization のメンバーは、オーナーが {% data variables.product.prodname_oauth_app %} に Organization リソースへのアクセスを許可するようリクエストできます。'
|
||||
title: Requesting organization approval for OAuth Apps
|
||||
intro: 'Organization members can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_app %}.'
|
||||
redirect_from:
|
||||
- /articles/requesting-organization-approval-for-third-party-applications/
|
||||
- /articles/requesting-organization-approval-for-your-authorized-applications/
|
||||
- /articles/requesting-organization-approval-for-third-party-applications
|
||||
- /articles/requesting-organization-approval-for-your-authorized-applications
|
||||
- /articles/requesting-organization-approval-for-oauth-apps
|
||||
- /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps
|
||||
@@ -14,16 +14,18 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: Request OAuth App approval
|
||||
---
|
||||
|
||||
## 個人アカウントではすでに許可されている {% data variables.product.prodname_oauth_app %} を Organization でも承認するようリクエストする
|
||||
## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.access_applications %}
|
||||
{% data reusables.user_settings.access_authorized_oauth_apps %}
|
||||
3. アプリケーションのリストで、アクセスを要求する {% data variables.product.prodname_oauth_app %} の名前をクリックします。 ![[View application] ボタン](/assets/images/help/settings/settings-third-party-view-app.png)
|
||||
4. {% data variables.product.prodname_oauth_app %} にアクセスさせる Organization の横で、[**Request access**] をクリックします。 ![[Request access] ボタン](/assets/images/help/settings/settings-third-party-request-access.png)
|
||||
5. {% data variables.product.prodname_oauth_app %} アクセスをリクエストすることに関する情報を読み、[**Request approval from owners**] をクリックします。 ![[Request approval] ボタン](/assets/images/help/settings/oauth-access-request-approval.png)
|
||||
3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
|
||||
|
||||
4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
|
||||
|
||||
5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
|
||||
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [{% data variables.product.prodname_oauth_app %}のアクセス制限について](/articles/about-oauth-app-access-restrictions)
|
||||
- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Migrating from Azure Pipelines to GitHub Actions
|
||||
intro: '{% data variables.product.prodname_actions %} and Azure Pipelines share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions
|
||||
- /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Migrating from CircleCI to GitHub Actions
|
||||
intro: 'GitHub Actions and CircleCI share several similarities in configuration, which makes migration to GitHub Actions relatively straightforward.'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions
|
||||
- /actions/learn-github-actions/migrating-from-circleci-to-github-actions
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Migrating from Jenkins to GitHub Actions
|
||||
intro: '{% data variables.product.prodname_actions %} and Jenkins share multiple similarities, which makes migration to {% data variables.product.prodname_actions %} relatively straightforward.'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions
|
||||
- /actions/learn-github-actions/migrating-from-jenkins-to-github-actions
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Migrating from Travis CI to GitHub Actions
|
||||
intro: '{% data variables.product.prodname_actions %} and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to {% data variables.product.prodname_actions %}.'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions
|
||||
- /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
---
|
||||
title: 認証
|
||||
intro: '{% ifversion not ghae %}2 要素認証、{% endif %}SSH{% ifversion not ghae %}、{% endif %}コミット署名検証などの機能を使用して、アカウントとデータを安全に保ちます。'
|
||||
title: Authentication
|
||||
intro: 'Keep your account and data secure with features like {% ifversion not ghae %}two-factor authentication, {% endif %}SSH{% ifversion not ghae %},{% endif %} and commit signature verification.'
|
||||
redirect_from:
|
||||
- /categories/56/articles/
|
||||
- /categories/ssh/
|
||||
- /mac-verify-ssh/
|
||||
- /ssh-issues/
|
||||
- /verify-ssh-redirect/
|
||||
- /win-verify-ssh/
|
||||
- /categories/92/articles/
|
||||
- /categories/gpg/
|
||||
- /categories/security/
|
||||
- /categories/56/articles
|
||||
- /categories/ssh
|
||||
- /mac-verify-ssh
|
||||
- /ssh-issues
|
||||
- /verify-ssh-redirect
|
||||
- /win-verify-ssh
|
||||
- /categories/92/articles
|
||||
- /categories/gpg
|
||||
- /categories/security
|
||||
- /categories/authenticating-to-github
|
||||
- /github/authenticating-to-github/
|
||||
- /github/authenticating-to-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: About anonymized URLs
|
||||
intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
|
||||
redirect_from:
|
||||
- /articles/why-do-my-images-have-strange-urls/
|
||||
- /articles/why-do-my-images-have-strange-urls
|
||||
- /articles/about-anonymized-image-urls
|
||||
- /authenticating-to-github/about-anonymized-image-urls
|
||||
- /github/authenticating-to-github/about-anonymized-urls
|
||||
@@ -14,16 +14,15 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
画像をホストするために、{% data variables.product.product_name %}は[オープンソースプロジェクトの Camo](https://github.com/atmos/camo) を使用します。 Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. URL は `https://<subdomain>.githubusercontent.com/` で始まり、画像のアップロード方法に応じて異なるサブドメインがあります。
|
||||
To host your images, {% data variables.product.product_name %} uses the [open-source project Camo](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. The URL starts `https://<subdomain>.githubusercontent.com/`, with different subdomains depending on how you uploaded the image.
|
||||
|
||||
Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
|
||||
|
||||
## Camoでの問題のトラブルシューティング
|
||||
## Troubleshooting issues with Camo
|
||||
|
||||
まれな状況下において、Camoによって処理された画像が{% data variables.product.prodname_dotcom %}に表示されないことがあります。 問題のありかを判断するために利用できる手順を以下に示します。
|
||||
In rare circumstances, images that are processed through Camo might not appear on {% data variables.product.prodname_dotcom %}. Here are some steps you can take to determine where the problem lies.
|
||||
|
||||
{% windows %}
|
||||
|
||||
@@ -35,12 +34,12 @@ Windows users will either need to use the Git PowerShell (which is installed alo
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
### 画像が表示されない
|
||||
### An image is not showing up
|
||||
|
||||
If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
1. `curl` を使って画像ヘッダをリクエストしてください。
|
||||
1. Request the image headers using `curl`.
|
||||
```shell
|
||||
$ curl -I https://www.my-server.com/images/some-image.png
|
||||
> HTTP/2 200
|
||||
@@ -50,20 +49,20 @@ If an image is showing up in your browser but not on {% data variables.product.p
|
||||
> Server: Google Frontend
|
||||
> Content-Length: 6507
|
||||
```
|
||||
3. `Content-Type` の値を確認してください。 ここでは `image/x-png` です。
|
||||
4. コンテントタイプは[Camo がサポートするタイプのリスト](https://github.com/atmos/camo/blob/master/mime-types.json)で確認してください。
|
||||
3. Check the value of `Content-Type`. In this case, it's `image/x-png`.
|
||||
4. Check that content type against [the list of types supported by Camo](https://github.com/atmos/camo/blob/master/mime-types.json).
|
||||
|
||||
コンテントタイプが Camo でサポートされていない場合、試せることがいくつかあります:
|
||||
* 画像をホストしているサーバーを自分で所有しているなら、画像の適切なコンテントタイプを返すように修正してください。
|
||||
* 画像を外部のサービスでホストしているなら、そのサービスのサポートに連絡してください。
|
||||
* Camo にプルリクエストを送り、コンテントタイプをリストに追加してもらってください。
|
||||
If your content type is not supported by Camo, you can try several actions:
|
||||
* If you own the server that's hosting the image, modify it so that it returns a correct content type for images.
|
||||
* If you're using an external service for hosting images, contact support for that service.
|
||||
* Make a pull request to Camo to add your content type to the list.
|
||||
|
||||
### 最近変更した画像が更新されない
|
||||
### An image that changed recently is not updating
|
||||
|
||||
最近変更した画像がブラウザでは表示され、{% data variables.product.prodname_dotcom %}では表示されない場合、その画像のキャッシュをリセットしてみることができます。
|
||||
If you changed an image recently and it's showing up in your browser but not {% data variables.product.prodname_dotcom %}, you can try resetting the cache of the image.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
1. `curl` を使って画像ヘッダをリクエストしてください。
|
||||
1. Request the image headers using `curl`.
|
||||
```shell
|
||||
$ curl -I https://www.my-server.com/images/some-image.png
|
||||
> HTTP/2 200
|
||||
@@ -73,29 +72,29 @@ If an image is showing up in your browser but not on {% data variables.product.p
|
||||
> Server: Jetty(8.y.z-SNAPSHOT)
|
||||
```
|
||||
|
||||
`Cache-Control`の値を確認してください。 この例では`Cache-Control`はありません。 その場合:
|
||||
* 画像をホストしているサーバを自分で保有しているなら、画像に対する `Cache-Control` に `no-cache` を返すように修正してください。
|
||||
* 画像を外部のサービスでホストしているなら、そのサービスのサポートに連絡してください。
|
||||
Check the value of `Cache-Control`. In this example, there's no `Cache-Control`. In that case:
|
||||
* If you own the server that's hosting the image, modify it so that it returns a `Cache-Control` of `no-cache` for images.
|
||||
* If you're using an external service for hosting images, contact support for that service.
|
||||
|
||||
`Cache-Control` *が* `no-cache` に設定されている場合は、{% data variables.contact.contact_support %} にお問い合わせいただくか、{% data variables.contact.community_support_forum %} を検索してください。
|
||||
If `Cache-Control` *is* set to `no-cache`, contact {% data variables.contact.contact_support %} or search the {% data variables.contact.community_support_forum %}.
|
||||
|
||||
### Camoのキャッシュから画像を削除する
|
||||
### Removing an image from Camo's cache
|
||||
|
||||
キャッシュをパージすれば、すべての{% data variables.product.prodname_dotcom %}ユーザは画像をリクエストし直すようになるので、この方法はごく控えめに使うべきであり、これまでに述べたステップがうまく働かなかった場合にかぎるべきです。
|
||||
Purging the cache forces every {% data variables.product.prodname_dotcom %} user to re-request the image, so you should use it very sparingly and only in the event that the above steps did not work.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
1. Camo の URL に対して `curl -X PURGE` を使い、画像をパージしてください。
|
||||
1. Purge the image using `curl -X PURGE` on the Camo URL.
|
||||
```shell
|
||||
$ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
|
||||
> {"status": "ok", "id": "216-8675309-1008701"}
|
||||
```
|
||||
|
||||
### プライベートネットワークでの画像の表示
|
||||
### Viewing images on private networks
|
||||
|
||||
画像がプライベートネットワークや、認証を要求するサーバから提供されている場合、{% data variables.product.prodname_dotcom %}では表示できません。 実際のところ、その画像はユーザにサーバへのログインを求めなければ表示されません。
|
||||
If an image is being served from a private network or from a server that requires authentication, it can't be viewed by {% data variables.product.prodname_dotcom %}. In fact, it can't be viewed by any user without asking them to log into the server.
|
||||
|
||||
この問題を修正するには、その画像をパブリックにアクセスできるサービスに移してください。
|
||||
To fix this, please move the image to a service that is publicly available.
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- {% data variables.product.prodname_blog %}の[ユーザの画像のプロキシ処理](https://github.com/blog/1766-proxying-user-images)
|
||||
- "[Proxying user images](https://github.com/blog/1766-proxying-user-images)" on {% data variables.product.prodname_blog %}
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: GitHubのIPアドレスについて
|
||||
intro: '{% data variables.product.product_name %}は複数のIPアドレスの範囲からアプリケーションを提供します。この範囲は、APIを通じて取得できます。'
|
||||
title: About GitHub's IP addresses
|
||||
intro: '{% data variables.product.product_name %} serves applications from multiple IP address ranges, which are available using the API.'
|
||||
redirect_from:
|
||||
- /articles/what-ip-addresses-does-github-use-that-i-should-whitelist/
|
||||
- /categories/73/articles/
|
||||
- /categories/administration/
|
||||
- /articles/github-s-ip-addresses/
|
||||
- /articles/what-ip-addresses-does-github-use-that-i-should-whitelist
|
||||
- /categories/73/articles
|
||||
- /categories/administration
|
||||
- /articles/github-s-ip-addresses
|
||||
- /articles/about-github-s-ip-addresses
|
||||
- /articles/about-githubs-ip-addresses
|
||||
- /github/authenticating-to-github/about-githubs-ip-addresses
|
||||
@@ -19,7 +19,7 @@ topics:
|
||||
shortTitle: GitHub's IP addresses
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_dotcom %}のIPアドレスのリストは、[メタ](https://api.github.com/meta)APIエンドポイントから取得できます。 詳しい情報については、「[メタ](/rest/reference/meta)」を参照してください。
|
||||
You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)."
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -29,12 +29,12 @@ shortTitle: GitHub's IP addresses
|
||||
|
||||
These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds.
|
||||
|
||||
これらの範囲は[CIDR表記](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)になっています。 [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php)のようなツールを使って、CIDR表記をIPアドレスの範囲に変換できます。
|
||||
These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges.
|
||||
|
||||
We make changes to our IP addresses from time to time. IP アドレスによる許可はお勧めしませんが、これらの IP 範囲を使用する場合は、API を定期的にモニタリングすることを強くお勧めします。
|
||||
We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API.
|
||||
|
||||
アプリケーションが機能するためには、`github.com`のIPの範囲についてTCPポートの22、80、443、9418を許可しなければなりません。
|
||||
For applications to function, you must allow TCP ports 22, 80, 443, and 9418 via our IP ranges for `github.com`.
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [接続の問題のトラブルシューティング](/articles/troubleshooting-connectivity-problems)
|
||||
- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Creating a personal access token
|
||||
intro: You should create a personal access token to use in place of a password with the command line or with the API.
|
||||
redirect_from:
|
||||
- /articles/creating-an-oauth-token-for-command-line-use/
|
||||
- /articles/creating-an-access-token-for-command-line-use/
|
||||
- /articles/creating-an-oauth-token-for-command-line-use
|
||||
- /articles/creating-an-access-token-for-command-line-use
|
||||
- /articles/creating-a-personal-access-token-for-the-command-line
|
||||
- /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
|
||||
- /github/authenticating-to-github/creating-a-personal-access-token
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 強力なパスワードの作成
|
||||
title: Creating a strong password
|
||||
intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} with a strong and unique password using a password manager.'
|
||||
redirect_from:
|
||||
- /articles/what-is-a-strong-password/
|
||||
- /articles/what-is-a-strong-password
|
||||
- /articles/creating-a-strong-password
|
||||
- /github/authenticating-to-github/creating-a-strong-password
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password
|
||||
@@ -15,25 +15,24 @@ topics:
|
||||
- Access management
|
||||
shortTitle: Create a strong password
|
||||
---
|
||||
|
||||
You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} that is at least:
|
||||
- 数字と小文字アルファベットを含む場合は長さ {% ifversion ghes %}7{% else %}8{% endif %} 文字以上、または
|
||||
- 文字の組み合わせを考慮しない場合は長さ 15 文字以上
|
||||
- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or
|
||||
- 15 characters long with any combination of characters
|
||||
|
||||
アカウントを安全に保つため、以下のベストプラクティスに従うことをお勧めします:
|
||||
- [LastPass](https://lastpass.com/) や [1Password](https://1password.com/) などのパスワードマネージャを使用して、15 文字以上のパスワードを生成すること。
|
||||
- {% data variables.product.product_name %}用に独自のパスワードを生成すること。 If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
|
||||
To keep your account secure, we recommend you follow these best practices:
|
||||
- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
|
||||
- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
|
||||
|
||||
- 個人アカウントに 2 要素認証を設定する。 詳しい情報については「[2 要素認証について](/articles/about-two-factor-authentication)」を参照してください。
|
||||
- 潜在的なコラボレーターであっても誰であっても、パスワードは決して共有しないでください。 {% data variables.product.product_name %}では一人ひとりが自分の個人アカウントを使用すべきです。 コラボレートする方法の詳しい情報については、「[コラボレーターを個人リポジトリに招待する](/articles/inviting-collaborators-to-a-personal-repository)」、「[共同開発モデルについて](/articles/about-collaborative-development-models/)」、または「[Organization のグループでコラボレーションする](/organizations/collaborating-with-groups-in-organizations/)」を参照してください。
|
||||
- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
|
||||
- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
|
||||
|
||||
{% data reusables.repositories.blocked-passwords %}
|
||||
|
||||
ブラウザを使用して {% data variables.product.product_name %} にログオンする場合のみパスワードを使用できます。 コマンドラインや API などの他の方法で {% data variables.product.product_name %} を認証する場合は、他の認証情報を使用する必要があります。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github)」を参照してください。
|
||||
You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
|
||||
|
||||
{% ifversion fpt or ghec %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- "[Git で {% data variables.product.product_name %} 認証情報をキャッシュ](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
|
||||
- "[アカウントとデータの安全を保つ](/articles/keeping-your-account-and-data-secure/)"
|
||||
- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
|
||||
- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: GitHub's SSH key fingerprints
|
||||
intro: Public key fingerprints can be used to validate a connection to a remote server.
|
||||
redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints/
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
- /articles/githubs-ssh-key-fingerprints
|
||||
- /github/authenticating-to-github/githubs-ssh-key-fingerprints
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: アカウントとデータを安全に保つ
|
||||
title: Keeping your account and data secure
|
||||
intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and any associated data secure.'
|
||||
redirect_from:
|
||||
- /articles/keeping-your-account-and-data-secure
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
title: Removing sensitive data from a repository
|
||||
intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.'
|
||||
redirect_from:
|
||||
- /remove-sensitive-data/
|
||||
- /removing-sensitive-data/
|
||||
- /articles/remove-sensitive-data/
|
||||
- /remove-sensitive-data
|
||||
- /removing-sensitive-data
|
||||
- /articles/remove-sensitive-data
|
||||
- /articles/removing-sensitive-data-from-a-repository
|
||||
- /github/authenticating-to-github/removing-sensitive-data-from-a-repository
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: SSH キーをレビューする
|
||||
title: Reviewing your SSH keys
|
||||
intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/keeping-your-application-access-tokens-safe/
|
||||
- /articles/keeping-your-ssh-keys-and-application-access-tokens-safe/
|
||||
- /articles/keeping-your-application-access-tokens-safe
|
||||
- /articles/keeping-your-ssh-keys-and-application-access-tokens-safe
|
||||
- /articles/reviewing-your-ssh-keys
|
||||
- /github/authenticating-to-github/reviewing-your-ssh-keys
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-ssh-keys
|
||||
@@ -16,32 +16,32 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
許可されていない (あるいは侵害された可能性のある) SSH キーを削除することで、攻撃者が以後自分のリポジトリにアクセスすることを防止できます。 有効な既存の SSH キーを承認することもできます。
|
||||
You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid.
|
||||
|
||||
{% mac %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.ssh %}
|
||||
3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[**Delete**] をクリックします。 残しておきたい有効な SSH キーがある場合は、[**Approve**] をクリックします。 
|
||||
3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**メモ:** Git 操作が失敗したために SSH キーを監査している場合は、 [SSH キー監査エラー](/articles/error-we-re-doing-an-ssh-key-audit)の原因となった未検証のキーが SSH キーのリストで強調表示されます。
|
||||
**Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
4. ターミナルを開きます。
|
||||
4. Open Terminal.
|
||||
|
||||
{% data reusables.command_line.start_ssh_agent %}
|
||||
|
||||
6. 自分の公開鍵のフィンガープリントを見つけてメモします。
|
||||
6. Find and take a note of your public key fingerprint.
|
||||
```shell
|
||||
$ ssh-add -l -E sha256
|
||||
> 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
|
||||
```
|
||||
|
||||
7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致して*いなければなりません* 。
|
||||
7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
|
||||
|
||||
{% endmac %}
|
||||
|
||||
@@ -49,27 +49,28 @@ topics:
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.ssh %}
|
||||
3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[**Delete**] をクリックします。 残しておきたい有効な SSH キーがある場合は、[**Approve**] をクリックします。 
|
||||
3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**メモ:** Git 操作が失敗したために SSH キーを監査している場合は、 [SSH キー監査エラー](/articles/error-we-re-doing-an-ssh-key-audit)の原因となった未検証のキーが SSH キーのリストで強調表示されます。
|
||||
**Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
4. Git Bash を開きます。
|
||||
4. Open Git Bash.
|
||||
|
||||
5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %}
|
||||
|
||||
{% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %}
|
||||
|
||||
6. 自分の公開鍵のフィンガープリントを見つけてメモします。
|
||||
6. Find and take a note of your public key fingerprint.
|
||||
```shell
|
||||
$ ssh-add -l -E sha256
|
||||
> 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
|
||||
```
|
||||
|
||||
7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致して*いなければなりません* 。
|
||||
7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -77,30 +78,31 @@ topics:
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.ssh %}
|
||||
3. [SSH Settings] ページで、自分のアカウントに関連付けられている SSH キーを書き留めます。 覚えていないか古くなっている場合は、[**Delete**] をクリックします。 残しておきたい有効な SSH キーがある場合は、[**Approve**] をクリックします。 
|
||||
3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**メモ:** Git 操作が失敗したために SSH キーを監査している場合は、 [SSH キー監査エラー](/articles/error-we-re-doing-an-ssh-key-audit)の原因となった未検証のキーが SSH キーのリストで強調表示されます。
|
||||
**Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
4. ターミナルを開きます。
|
||||
4. Open Terminal.
|
||||
|
||||
{% data reusables.command_line.start_ssh_agent %}
|
||||
|
||||
6. 自分の公開鍵のフィンガープリントを見つけてメモします。
|
||||
6. Find and take a note of your public key fingerprint.
|
||||
```shell
|
||||
$ ssh-add -l -E sha256
|
||||
> 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
|
||||
```
|
||||
|
||||
7. {% data variables.product.product_name %} での SSH キーは、お使いのコンピュータでの同じキーと一致して*いなければなりません* 。
|
||||
7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**: 見慣れない SSH キーが {% data variables.product.product_name %} で見つかった場合は、すぐにそれを削除し、さらに支援が必要な場合は {% data variables.contact.contact_support %} に問い合わせてください。 確認できない公開鍵は、潜在的なセキュリティ上の問題を示している可能性があります。
|
||||
**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Updating your GitHub access credentials
|
||||
intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Should you have the need, you can reset all of these access credentials yourself.'
|
||||
redirect_from:
|
||||
- /articles/rolling-your-credentials/
|
||||
- /articles/how-can-i-reset-my-password/
|
||||
- /articles/rolling-your-credentials
|
||||
- /articles/how-can-i-reset-my-password
|
||||
- /articles/updating-your-github-access-credentials
|
||||
- /github/authenticating-to-github/updating-your-github-access-credentials
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 2 要素認証を利用した GitHub へのアクセス
|
||||
intro: '2FA を有効にすると、{% data variables.product.product_name %} にサインインするときに、2FA 認証コードとパスワードを入力するように求められます。'
|
||||
title: Accessing GitHub using two-factor authentication
|
||||
intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.'
|
||||
redirect_from:
|
||||
- /articles/providing-your-2fa-security-code/
|
||||
- /articles/providing-your-2fa-authentication-code/
|
||||
- /articles/authenticating-to-github-using-fido-u2f-via-nfc/
|
||||
- /articles/providing-your-2fa-security-code
|
||||
- /articles/providing-your-2fa-authentication-code
|
||||
- /articles/authenticating-to-github-using-fido-u2f-via-nfc
|
||||
- /articles/accessing-github-using-two-factor-authentication
|
||||
- /github/authenticating-to-github/accessing-github-using-two-factor-authentication
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication
|
||||
@@ -16,58 +16,57 @@ topics:
|
||||
- 2FA
|
||||
shortTitle: Access GitHub with 2FA
|
||||
---
|
||||
With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
|
||||
|
||||
2 要素認証を有効にすると、ブラウザから {% data variables.product.product_name %} にアクセスするときに認証コードを入力する必要があります。 API やコマンドラインなどの他の方法を使用して {% data variables.product.product_name %} にアクセスする場合は、別の形式の認証を使用する必要があります。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} への認証について](/github/authenticating-to-github/about-authentication-to-github)」を参照してください。
|
||||
## Providing a 2FA code when signing in to the website
|
||||
|
||||
## Web サイトへのサインインの際に 2FA コードを提供
|
||||
After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app.
|
||||
|
||||
パスワードを使用して {% data variables.product.product_name %}にサインインした後、{% ifversion fpt or ghec %}テキストメッセージまたは {% endif %}TOTP アプリケーションから、認証コードを入力するよう求められます。
|
||||
{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires.
|
||||
|
||||
{% data variables.product.product_name %}が 2FA 認証コードを再度求めるのは、ログアウトした場合、新しいデバイスを使う場合、またはセッションが期限切れになった場合のみです。
|
||||
### Generating a code through a TOTP application
|
||||
|
||||
### TOTP アプリケーションでのコード生成
|
||||
If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions.
|
||||
|
||||
スマートフォン上の TOTP アプリケーションを使用して 2 要素認証をセットアップすることにした場合は、いつでも {% data variables.product.product_name %}のための認証コードを生成できます。 多くの場合、アプリケーションを起動するだけで新しいコードが生成されます。 個別の手順についてはアプリケーションのドキュメンテーションを参照してください。
|
||||
|
||||
2 要素認証を設定した後にモバイルアプリケーションを削除した場合、アカウントにアクセスする際にリカバリコードを入力しなければなりません。 詳しい情報については[2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)を参照してください。
|
||||
If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
### テキストメッセージの受信
|
||||
### Receiving a text message
|
||||
|
||||
テキストメッセージで 2 要素認証をセットアップする場合、{% data variables.product.product_name %}は認証コードが記されたテキストメッセージを送信します。
|
||||
If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## コマンドラインでの 2 要素認証の使用
|
||||
## Using two-factor authentication with the command line
|
||||
|
||||
2 要素認証を有効化した後は、{% data variables.product.product_name %} にコマンドラインからアクセスする際に、パスワードの代わりに個人アクセストークンまたは SSH キーを使わなければなりません。
|
||||
After you've enabled 2FA, you must use a personal access token or SSH key instead of your password when accessing {% data variables.product.product_name %} on the command line.
|
||||
|
||||
### HTTPS を利用したコマンドラインでの認証
|
||||
### Authenticating on the command line using HTTPS
|
||||
|
||||
2FA を有効化した後は、コマンドライン上で HTTPS の URL を使って {% data variables.product.product_name %}の認証を受けるために、パスワードとして使うための個人アクセストークンを作成しなければなりません。
|
||||
After you've enabled 2FA, you must create a personal access token to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs.
|
||||
|
||||
コマンドラインでユーザ名とパスワードを求められたら、{% data variables.product.product_name %}のユーザ名と個人アクセストークンを入力してください。 コマンドラインプロンプトがパスワードを要求する際には、個人アクセストークンを入力すべきだということを示しません。
|
||||
When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and personal access token. The command line prompt won't specify that you should enter your personal access token when it asks for your password.
|
||||
|
||||
詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
|
||||
For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
|
||||
### SSH を利用したコマンドラインでの認証
|
||||
### Authenticating on the command line using SSH
|
||||
|
||||
2 要素認証を有効化しても、コマンドライン上で SSH URL を使って {% data variables.product.product_name %} の認証を受けるやり方は変わりません。 SSH キーのセットアップと利用に関する詳しい情報については、「[{% data variables.product.prodname_dotcom %} に SSH で接続する](/articles/connecting-to-github-with-ssh/)」を参照してください。
|
||||
Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)."
|
||||
|
||||
## Subversion を使ったリポジトリへのアクセスでの 2 要素認証の利用
|
||||
## Using two-factor authentication to access a repository using Subversion
|
||||
|
||||
SubVersion を介してリポジトリにアクセスする際には、パスワードを入力する代わりに個人アクセストークンを提供しなければなりません。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
|
||||
When you access a repository via Subversion, you must provide a personal access token instead of entering your password. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
|
||||
## トラブルシューティング
|
||||
## Troubleshooting
|
||||
|
||||
2 要素認証のクレデンシャルを利用できなくなった場合、アカウントに再びアクセスするためには、リカバリコードを使用するか、その他のリカバリ方法 (セットアップ済みである場合) を使用できます。 詳しい情報については[2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)を参照してください。
|
||||
If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
|
||||
|
||||
認証が何度も失敗するようであれば、スマートフォンのクロックをモバイルプロバイダと同期してみてください。 多くの場合、タイムゾーンを指定するのではなく、スマートフォンのクロックの「自動設定」オプションをオンにすることになります。
|
||||
If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone.
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [2 要素認証について](/articles/about-two-factor-authentication)
|
||||
- [2 要素認証の設定](/articles/configuring-two-factor-authentication)
|
||||
- [2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods)
|
||||
- [2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)
|
||||
- "[About two-factor authentication](/articles/about-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Changing two-factor authentication delivery methods for your mobile device
|
||||
intro: You can switch between receiving authentication codes through a text message or a mobile application.
|
||||
redirect_from:
|
||||
- /articles/changing-two-factor-authentication-delivery-methods/
|
||||
- /articles/changing-two-factor-authentication-delivery-methods
|
||||
- /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
- /github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: 2 要素認証リカバリ方法を設定する
|
||||
intro: 2 要素認証のクレデンシャルを紛失した場合に備え、アカウントへのアクセスを回復するさまざまな方法を設定できます。
|
||||
title: Configuring two-factor authentication recovery methods
|
||||
intro: You can set up a variety of recovery methods to access your account if you lose your two-factor authentication credentials.
|
||||
redirect_from:
|
||||
- /articles/downloading-your-two-factor-authentication-recovery-codes/
|
||||
- /articles/setting-a-fallback-authentication-number/
|
||||
- /articles/about-recover-accounts-elsewhere/
|
||||
- /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere/
|
||||
- /articles/generating-and-storing-an-account-recovery-token/
|
||||
- /articles/downloading-your-two-factor-authentication-recovery-codes
|
||||
- /articles/setting-a-fallback-authentication-number
|
||||
- /articles/about-recover-accounts-elsewhere
|
||||
- /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere
|
||||
- /articles/generating-and-storing-an-account-recovery-token
|
||||
- /articles/configuring-two-factor-authentication-recovery-methods
|
||||
- /github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods
|
||||
@@ -18,69 +18,73 @@ topics:
|
||||
- 2FA
|
||||
shortTitle: Configure 2FA recovery
|
||||
---
|
||||
In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
|
||||
|
||||
2 要素認証リカバリコードを安全に保管することに加え、別のリカバリ方法を 1 つ以上設定することを強くおすすめします。
|
||||
## Downloading your two-factor authentication recovery codes
|
||||
|
||||
## 2 要素認証リカバリコードのダウンロード
|
||||
{% data reusables.two_fa.about-recovery-codes %} You can also download your recovery codes at any point after enabling two-factor authentication.
|
||||
|
||||
{% data reusables.two_fa.about-recovery-codes %}また、2 要素認証の有効化後は、リカバリコードをいつでもダウンロードできます。
|
||||
|
||||
アカウントを安全に保つため、リカバリコードを共有や配布しないでください。 以下のような、安全なパスワードマネージャで保存することをおすすめします:
|
||||
To keep your account secure, don't share or distribute your recovery codes. We recommend saving them with a secure password manager, such as:
|
||||
- [1Password](https://1password.com/)
|
||||
- [LastPass](https://lastpass.com/)
|
||||
|
||||
新しいリカバリコードを生成するか、2 要素認証を無効化してから再有効化すると、セキュリティ設定にあるリカバリコードが自動的に更新されます。
|
||||
If you generate new recovery codes or disable and re-enable 2FA, the recovery codes in your security settings automatically update.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
{% data reusables.two_fa.show-recovery-codes %}
|
||||
4. リカバリコードを安全な場所に保存します。 リカバリコードは、アカウントにアクセスできなくなった場合に、再びアクセスするために役立ちます。
|
||||
- リカバリコードをデバイスに保存するには、[**Download**] をクリックします。
|
||||
- リカバリコードのハードコピーを保存するには、[**Print**] をクリックします。
|
||||
- パスワードマネージャーに保存するためにリカバリコードをコピーするには [**Copy**] をクリックします。 
|
||||
4. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
|
||||
- To save your recovery codes on your device, click **Download**.
|
||||
- To save a hard copy of your recovery codes, click **Print**.
|
||||
- To copy your recovery codes for storage in a password manager, click **Copy**.
|
||||
|
||||
|
||||
## リカバリコードのセットを新しく生成する
|
||||
## Generating a new set of recovery codes
|
||||
|
||||
アクセス回復のためにリカバリコードを一度使うと、再利用はできません。 16 個のリカバリコードをすべて使った場合は、別のコードのリストを生成できます。 リカバリコードのセットを新しく生成すると、以前生成したコードはすべて無効になります。
|
||||
Once you use a recovery code to regain access to your account, it cannot be reused. If you've used all 16 recovery codes, you can generate another list of codes. Generating a new set of recovery codes will invalidate any codes you previously generated.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
{% data reusables.two_fa.show-recovery-codes %}
|
||||
3. リカバリコードのセットを新しく作成するには、[**Generate new recovery codes**] をクリックします。 ![[Generate new recovery codes] ボタン](/assets/images/help/2fa/generate-new-recovery-codes.png)
|
||||
3. To create another batch of recovery codes, click **Generate new recovery codes**.
|
||||
|
||||
|
||||
## セキュリティキーを追加の 2 要素認証方式として設定する
|
||||
## Configuring a security key as an additional two-factor authentication method
|
||||
|
||||
2 要素認証の二次的な方法としてセキュリティキーを設定し、そのセキュリティキーを使ってアカウントへのアクセスを回復することができます。 詳しい情報については、「[2 要素認証を設定する](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)」を参照してください。
|
||||
You can set up a security key as a secondary two-factor authentication method, and use the security key to regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## フォールバック認証番号を設定する
|
||||
## Setting a fallback authentication number
|
||||
|
||||
フォールバックデバイスのために、別の番号を提供できます。 主に使うデバイスにもリカバリコードにもアクセスできなくなった場合、バックアップの SMS 番号でアカウントにアクセスできます。
|
||||
You can provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
|
||||
|
||||
認証をテキストメッセージから設定しても、TOTP モバイルアプリケーションから設定しても、フォールバック番号を使うことは可能です。
|
||||
You can use a fallback number regardless of whether you've configured authentication via text message or TOTP mobile application.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告:** フォールバック番号を使うのは、最後の手段です。 フォールバック認証番号を設定した場合は、別のリカバリ方法も設定するようおすすめします。
|
||||
- 悪意のある人が携帯電話会社を攻撃する可能性があるため、SMS 認証にはリスクがあります。
|
||||
- SMS メッセージは、米国およびその他特定の国においてのみサポートされています。その一覧については、「[SMS 認証がサポートされている国](/articles/countries-where-sms-authentication-is-supported)」を参照してください。
|
||||
**Warning:** Using a fallback number is a last resort. We recommend configuring additional recovery methods if you set a fallback authentication number.
|
||||
- Bad actors may attack cell phone carriers, so SMS authentication is risky.
|
||||
- SMS messages are only supported for certain countries outside the US; for the list, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
3. [Fallback SMS number] の隣にある [**Add**] をクリックします。 ![[Add fallback SMS number] ボタン](/assets/images/help/2fa/add-fallback-sms-number-button.png)
|
||||
4. [Fallback SMS number] の下にある [**Add fallback SMS number**] をクリックします。 ![[Add fallback SMS number] テキスト](/assets/images/help/2fa/add_fallback_sms_number_text.png)
|
||||
5. 国コードを選択し、携帯電話番号を入力します。 入力した情報が正しいことを確認してから、[**Set fallback**] をクリックします。 
|
||||
3. Next to "Fallback SMS number", click **Add**.
|
||||
|
||||
4. Under "Fallback SMS number", click **Add fallback SMS number**.
|
||||
|
||||
5. Select your country code and type your mobile phone number, including the area code. When your information is correct, click **Set fallback**.
|
||||
|
||||
|
||||
設定後、バックアップデバイスが確認の SMS を受信します。
|
||||
After setup, the backup device will receive a confirmation SMS.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [2 要素認証について](/articles/about-two-factor-authentication)
|
||||
- [2 要素認証の設定](/articles/configuring-two-factor-authentication)
|
||||
- [2 要素認証を使用して {% data variables.product.prodname_dotcom %} にアクセスする](/articles/accessing-github-using-two-factor-authentication)
|
||||
- [2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)
|
||||
- "[About two-factor authentication](/articles/about-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
|
||||
- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
|
||||
- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 2 要素認証を設定する
|
||||
intro: 複数のオプションから選択して、アカウントの 2 番目の認証方法を追加できます。
|
||||
title: Configuring two-factor authentication
|
||||
intro: You can choose among multiple options to add a second source of authentication to your account.
|
||||
redirect_from:
|
||||
- /articles/configuring-two-factor-authentication-via-a-totp-mobile-app/
|
||||
- /articles/configuring-two-factor-authentication-via-text-message/
|
||||
- /articles/configuring-two-factor-authentication-via-fido-u2f/
|
||||
- /articles/configuring-two-factor-authentication-via-a-totp-mobile-app
|
||||
- /articles/configuring-two-factor-authentication-via-text-message
|
||||
- /articles/configuring-two-factor-authentication-via-fido-u2f
|
||||
- /articles/configuring-two-factor-authentication
|
||||
- /github/authenticating-to-github/configuring-two-factor-authentication
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication
|
||||
@@ -16,28 +16,27 @@ topics:
|
||||
- 2FA
|
||||
shortTitle: Configure 2FA
|
||||
---
|
||||
You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key.
|
||||
|
||||
モバイルアプリまたは{% ifversion fpt or ghec %}テキストメッセージ{% endif %}を使って、2 要素認証を設定できます。 また、セキュリティキーを追加することも可能です。
|
||||
|
||||
2 要素認証の設定には、時間ベースのワンタイムパスワード (TOTP) アプリケーションを使うことを強くおすすめします。{% ifversion fpt or ghec %}TOTP アプリケーションは、特に米国外において、SMS より信頼性があります。{% endif %}TOTP アプリは、クラウド内にある認証コードのセキュアなバックアップをサポートしており、デバイスにアクセスできなくなった場合に回復できます。
|
||||
We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告:**
|
||||
- 2 要素認証が必要なメンバー{% ifversion fpt or ghec %}、支払いマネージャー、{% endif %}または Organization のプライベートリポジトリへの外部コラボレーターは、2 要素認証を無効化する前に {% data variables.product.product_location %} で Organization から離脱する必要があります。
|
||||
- 2 要素認証を無効化すると、Organization や Organization のプライベートリポジトリのフォークへのアクセスも失います。 Organization およびフォークへのアクセスを再取得するには、2 要素認証を再有効化し、Organization オーナーに連絡します。
|
||||
**Warning:**
|
||||
- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.product.product_location %}.
|
||||
- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider.
|
||||
If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## TOTP モバイルアプリを使って 2要素認証を設定する
|
||||
## Configuring two-factor authentication using a TOTP mobile app
|
||||
|
||||
時間ベースのワンタイムパスワード (TOTP) アプリケーションは、認証コードを自動的に生成します。このコードは、一定の時間が過ぎた後は変化します。 以下のような、クラウドベースの TOTP アプリの利用をおすすめします:
|
||||
A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as:
|
||||
- [1Password](https://support.1password.com/one-time-passwords/)
|
||||
- [Authy](https://authy.com/guides/github/)
|
||||
- [LastPass Authenticator](https://lastpass.com/auth/)
|
||||
@@ -45,46 +44,51 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
|
||||
|
||||
{% tip %}
|
||||
|
||||
**参考**: 複数のデバイスで TOTP により認証を設定するには、セットアップ時に、QR コード を各デバイスで同時にスキャンします。 2 要素認証がすでに有効化されており、別のデバイスを追加したい場合は、セキュリティ設定から 2 要素認証を再設定する必要があります。
|
||||
**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. TOTP アプリをダウンロードします。
|
||||
1. Download a TOTP app.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
{% data reusables.two_fa.enable-two-factor-authentication %}
|
||||
{%- ifversion fpt or ghes > 3.1 %}
|
||||
5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**.
|
||||
6. Under "Authentication verification", do one of the following:
|
||||
- QR コードを、モバイルデバイスのアプリでスキャンする。 スキャン後、アプリは {% data variables.product.product_name %} で入力する 6 桁の数字を表示します。
|
||||
- If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead. ![[enter this code] をクリック](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
|
||||
7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**. 
|
||||
- Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
|
||||
- If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead.
|
||||
|
||||
7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**.
|
||||
|
||||
{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
|
||||
{%- else %}
|
||||
5. [Two-factor authentication] のページで、[**Set up using an app**] をクリックします。
|
||||
6. リカバリコードを安全な場所に保存します。 リカバリコードは、アカウントにアクセスできなくなった場合に、再びアクセスするために役立ちます。
|
||||
- リカバリコードをデバイスに保存するには、[**Download**] をクリックします。
|
||||
- リカバリコードのハードコピーを保存するには、[**Print**] をクリックします。
|
||||
- パスワードマネージャーに保存するためにリカバリコードをコピーするには [**Copy**] をクリックします。 
|
||||
7. 2要素のリカバリコードを保存したら、**Next**をクリックします。
|
||||
8. [Two-factor authentication] ページで、次のいずれかを実行します:
|
||||
- QR コードを、モバイルデバイスのアプリでスキャンする。 スキャン後、アプリは {% data variables.product.product_name %} で入力する 6 桁の数字を表示します。
|
||||
- QR コードをスキャンできない場合は、[**enter this text code**] をクリックしてコードを表示し、それをコピーして {% data variables.product.product_name %} に手入力してください。 ![[enter this code] をクリック](/assets/images/help/2fa/totp-click-enter-code.png)
|
||||
9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. {% data variables.product.product_name %} の 2 要素認証ページでコードを入力し、[**Enable**] をクリックします。 ![[TOTP Enable] フィールド](/assets/images/help/2fa/totp-enter-code.png)
|
||||
5. On the Two-factor authentication page, click **Set up using an app**.
|
||||
6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
|
||||
- To save your recovery codes on your device, click **Download**.
|
||||
- To save a hard copy of your recovery codes, click **Print**.
|
||||
- To copy your recovery codes for storage in a password manager, click **Copy**.
|
||||
|
||||
7. After saving your two-factor recovery codes, click **Next**.
|
||||
8. On the Two-factor authentication page, do one of the following:
|
||||
- Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
|
||||
- If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead.
|
||||
|
||||
9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**.
|
||||
|
||||
{%- endif %}
|
||||
{% data reusables.two_fa.test_2fa_immediately %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## テキストメッセージを使って 2 要素認証を設定する
|
||||
## Configuring two-factor authentication using text messages
|
||||
|
||||
TOTP モバイルアプリを使って認証できない場合は、SMS メッセージで認証できます。 フォールバックデバイスのために、別の番号を提供することも可能です。 主に使うデバイスにもリカバリコードにもアクセスできなくなった場合、バックアップの SMS 番号でアカウントにアクセスできます。
|
||||
If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
|
||||
|
||||
この方法を使う前に、テキストメッセージが受信できることを確認してください。 携帯電話の料金がかかる場合があります。
|
||||
Before using this method, be sure that you can receive text messages. Carrier rates may apply.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告:** 2 要素認証には、SMS ではなく TOTP アプリケーションを使うことを**強くおすすめします**。 {% data variables.product.product_name %} は、SMS メッセージの送信をサポートしていない国があります。 テキストメッセージによる認証を設定する前に、SMS による認証を {% data variables.product.product_name %} がサポートしている国のリストを確認してください。 詳細は「[SMS 認証がサポートされている国](/articles/countries-where-sms-authentication-is-supported)」を参照してください。
|
||||
**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -92,41 +96,46 @@ TOTP モバイルアプリを使って認証できない場合は、SMS メッ
|
||||
{% data reusables.user_settings.security %}
|
||||
{% data reusables.two_fa.enable-two-factor-authentication %}
|
||||
4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**.
|
||||
5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. 入力した情報が正しいことを確認してから、[**Send authentication code**] をクリックします。
|
||||
5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**.
|
||||
|
||||
|
||||
|
||||
|
||||
6. セキュリティコードが書かれたテキストメッセージが送信されます。 On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
|
||||
6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
|
||||
|
||||
![[2FA SMS continue] フィールド](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
|
||||
|
||||
{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
|
||||
{% data reusables.two_fa.test_2fa_immediately %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## セキュリティキーを使って 2 要素認証を設定する
|
||||
## Configuring two-factor authentication using a security key
|
||||
|
||||
{% data reusables.two_fa.after-2fa-add-security-key %}
|
||||
|
||||
ほとんどのデバイスとブラウザでは、USB または NFC を介して物理セキュリティキーを使用できます。 一部のブラウザでは、デバイス上の指紋リーダー、顔認識、またはパスワード/ PIN をセキュリティキーとして使用できます。
|
||||
On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key.
|
||||
|
||||
セキュリティキーによる認証は、TOTP アプリケーション{% ifversion fpt or ghec %}またはテキストメッセージ{% endif %}による認証の*二次的な*方法です。 セキュリティキーをなくした場合でも、モバイルデバイスのコードを使ってサインインできます。
|
||||
Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in.
|
||||
|
||||
1. TOTP モバイルアプリ{% ifversion fpt or ghec %}または SMS{% endif %} 経由で、あらかじめ 2 要素認証を設定しておく必要があります。
|
||||
2. コンピュータに WebAuthn 準拠のセキュリティキーが挿入されていることを確認してください。
|
||||
1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}.
|
||||
2. Ensure that you have a WebAuthn compatible security key inserted into your computer.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
5. [Security keys] の隣にある [**Add**] をクリックします。 
|
||||
6. [Security keys] で、[**Register new security key**] をクリックします。 
|
||||
7. セキュリティキーのニックネームを入力して、[**Add**] をクリックします。 
|
||||
8. お手持ちのセキュリティキーのドキュメンテーションに従い、セキュリティキーをアクティベートします。 
|
||||
9. リカバリコードをダウンロードしていて、アクセスできることを確認してください。 まだコードをダウンロードしていないか、コードのセットをもう 1 つ生成したい場合は、コードをダウンロードして、安全な場所に保存します。 アカウントにアクセスできなくなった場合、リカバリコードを使ってアカウントへのアクセスを回復できます。 詳しい情報については[2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)を参照してください。 ![[Download recovery codes] ボタン](/assets/images/help/2fa/2fa-recover-during-setup.png)
|
||||
5. Next to "Security keys", click **Add**.
|
||||
|
||||
6. Under "Security keys", click **Register new security key**.
|
||||
|
||||
7. Type a nickname for the security key, then click **Add**.
|
||||
|
||||
8. Activate your security key, following your security key's documentation.
|
||||
|
||||
9. Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
|
||||
|
||||
{% data reusables.two_fa.test_2fa_immediately %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [2 要素認証について](/articles/about-two-factor-authentication)
|
||||
- [2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods)
|
||||
- [2 要素認証を使用して {% data variables.product.prodname_dotcom %} にアクセスする](/articles/accessing-github-using-two-factor-authentication)
|
||||
- [2FA クレデンシャルをなくした際のアカウントの回復](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)
|
||||
- [個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)
|
||||
- "[About two-factor authentication](/articles/about-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
|
||||
- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: 2 要素認証でアカウントを保護する
|
||||
title: Securing your account with two-factor authentication (2FA)
|
||||
intro: 'You can set up your account on {% data variables.product.product_location %} to require an authentication code in addition to your password when you sign in.'
|
||||
redirect_from:
|
||||
- /categories/84/articles/
|
||||
- /categories/two-factor-authentication-2fa/
|
||||
- /categories/84/articles
|
||||
- /categories/two-factor-authentication-2fa
|
||||
- /articles/securing-your-account-with-two-factor-authentication-2fa
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Recovering your account if you lose your 2FA credentials
|
||||
intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
|
||||
redirect_from:
|
||||
- /articles/recovering-your-account-if-you-lost-your-2fa-credentials/
|
||||
- /articles/authenticating-with-an-account-recovery-token/
|
||||
- /articles/recovering-your-account-if-you-lost-your-2fa-credentials
|
||||
- /articles/authenticating-with-an-account-recovery-token
|
||||
- /articles/recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
- /github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: GitHub でオープンソースにコントリビュートする方法を見つける
|
||||
intro: '自分に関連する {% data variables.product.product_location %} のオープンソースプロジェクトにコントリビュートする方法を見つけることができます。'
|
||||
title: Finding ways to contribute to open source on GitHub
|
||||
intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_location %} that are relevant to you.'
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
|
||||
redirect_from:
|
||||
- /articles/where-can-i-find-open-source-projects-to-work-on/
|
||||
- /articles/finding-interesting-projects-on-github/
|
||||
- /articles/about-official-github-mirrors/
|
||||
- /articles/about-github-mirrors/
|
||||
- /articles/where-can-i-find-open-source-projects-to-work-on
|
||||
- /articles/finding-interesting-projects-on-github
|
||||
- /articles/about-official-github-mirrors
|
||||
- /articles/about-github-mirrors
|
||||
- /articles/finding-open-source-projects-on-github
|
||||
- /github/getting-started-with-github/finding-open-source-projects-on-github
|
||||
- /github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github
|
||||
@@ -18,22 +18,21 @@ topics:
|
||||
- Open Source
|
||||
shortTitle: Contribute to open source
|
||||
---
|
||||
## Discovering relevant projects
|
||||
|
||||
## 関連プロジェクトを発見する
|
||||
If there's a particular topic that interests you, visit `github.com/topics/<topic>`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)."
|
||||
|
||||
興味のある特定の Topics がある場合は、`github.com/topics/<topic>` にアクセスしてください。 たとえば、機械学習に興味がある場合は、https://github.com/topics/machine-learning にアクセスして、関連するプロジェクトと good first issue を見つけることができます。 [[Topics](https://github.com/topics)] にアクセスすると、人気のある Topics を閲覧できます。 興味のある Topics に一致するリポジトリを検索することもできます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories#search-by-topic)を参照してください。
|
||||
If you've been active on {% data variables.product.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe).
|
||||
|
||||
{% data variables.product.product_location %} で積極的に活動している場合は、[Explore](https://github.com/explore) での過去のコントリビューション、Star、およびその他のアクティビティに基づいて、プロジェクトについての個別の推奨事項と good first issue を見つけることができます。 Explore ニュースレターにサインアップして、あなたの興味に基づいて {% data variables.product.product_name %} にコントリビュートする機会について記載されたメールを受け取ることもできます。 サインアップするには、「[Explore メールニュースレター](https://github.com/explore/subscribe)」を参照してください。
|
||||
|
||||
パーソナルダッシュボードの [All activity] セクションで、Watch しているリポジトリやフォローしているユーザについての最新情報を入手できます。 詳しい情報については[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)を参照してください。
|
||||
Keep up with recent activity from repositories you watch and people you follow in the "All activity" section of your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
|
||||
|
||||
{% data reusables.support.ask-and-answer-forum %}
|
||||
|
||||
## good first issue を見つける
|
||||
## Finding good first issues
|
||||
|
||||
作業するプロジェクトが既にわかっている場合は、[`github.com/<owner>/<repository>/contribute`] にアクセスして、そのリポジトリで初心者向けの Issue を見つけることができます。 たとえば、https://github.com/electron/electron/contribute で `electron/electron` に初めてコントリビュートする方法を見つけることができます。
|
||||
If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com/<owner>/<repository>/contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute.
|
||||
|
||||
## Issue を開くこと
|
||||
## Opening an issue
|
||||
|
||||
If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines.
|
||||
|
||||
@@ -42,7 +41,7 @@ If you encounter a bug in an open source project, check if the bug has already b
|
||||
There are a variety of ways that you can contribute to open source projects.
|
||||
|
||||
### Reproducing a reported bug
|
||||
You can contribute to an open source project by validating an issue or adding additional context to an existing issue.
|
||||
You can contribute to an open source project by validating an issue or adding additional context to an existing issue.
|
||||
|
||||
### Testing a pull request
|
||||
You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request.
|
||||
@@ -51,7 +50,7 @@ You can contribute to an open source project by merging a pull request into your
|
||||
You can contribute to an open source project by adding additional information to existing issues.
|
||||
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [Topics によるリポジトリの分類](/articles/classifying-your-repository-with-topics)
|
||||
- 「[Organization ダッシュボードについて](/articles/about-your-organization-dashboard)」
|
||||
- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
|
||||
- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: GitHub 上でプロジェクトを探索する
|
||||
title: Exploring projects on GitHub
|
||||
intro: 'Discover interesting projects on {% data variables.product.product_name %} and contribute to open source by collaborating with other people.'
|
||||
redirect_from:
|
||||
- /categories/stars/
|
||||
- /categories/87/articles/
|
||||
- /categories/exploring-projects-on-github/
|
||||
- /categories/stars
|
||||
- /categories/87/articles
|
||||
- /categories/exploring-projects-on-github
|
||||
- /articles/exploring-projects-on-github
|
||||
- /github/getting-started-with-github/exploring-projects-on-github/
|
||||
- /github/getting-started-with-github/exploring-projects-on-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -2,10 +2,10 @@
|
||||
title: Saving repositories with stars
|
||||
intro: 'You can star repositories and topics to keep track of projects you find interesting{% ifversion fpt or ghec %} and discover related content in your news feed{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/stars/
|
||||
- /articles/about-stars/
|
||||
- /articles/browsing-friends-stars/
|
||||
- /articles/managing-your-stars/
|
||||
- /articles/stars
|
||||
- /articles/about-stars
|
||||
- /articles/browsing-friends-stars
|
||||
- /articles/managing-your-stars
|
||||
- /articles/saving-repositories-with-stars
|
||||
- /github/getting-started-with-github/saving-repositories-with-stars
|
||||
- /github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: リモートリポジトリについて
|
||||
title: About remote repositories
|
||||
redirect_from:
|
||||
- /articles/working-when-github-goes-down/
|
||||
- /articles/sharing-repositories-without-github/
|
||||
- /articles/working-when-github-goes-down
|
||||
- /articles/sharing-repositories-without-github
|
||||
- /articles/about-remote-repositories
|
||||
- /articles/which-url-should-i-use/
|
||||
- /articles/which-url-should-i-use
|
||||
- /articles/which-remote-url-should-i-use
|
||||
- /github/using-git/which-remote-url-should-i-use
|
||||
- /github/using-git/about-remote-repositories
|
||||
@@ -17,82 +17,82 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
## About remote repositories
|
||||
|
||||
## リモートリポジトリについて
|
||||
A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
|
||||
|
||||
リモート URL は、「コードがここに保存されています」ということを表現する Git のしゃれた方法です。 That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
|
||||
You can only push to two types of URL addresses:
|
||||
|
||||
プッシュできるのは、2 種類の URL アドレスに対してのみです。
|
||||
* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git`
|
||||
* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git`
|
||||
|
||||
* `https://{% data variables.command_line.backticks %}/user/repo.git` のような HTTPS URL
|
||||
* `git@{% data variables.command_line.backticks %}:user/repo.git` のような SSH URL
|
||||
|
||||
Git はリモート URL に名前を関連付けます。デフォルトのリモートは通常 `origin` と呼ばれます。
|
||||
Git associates a remote URL with a name, and your default remote is usually called `origin`.
|
||||
|
||||
## Creating remote repositories
|
||||
|
||||
`git remote add` コマンドを使用してリモート URL に名前を関連付けることができます。 たとえば、コマンドラインに以下のように入力できます:
|
||||
You can use the `git remote add` command to match a remote URL with a name.
|
||||
For example, you'd type the following in the command line:
|
||||
|
||||
```shell
|
||||
git remote add origin <em> <REMOTE_URL> </em>
|
||||
```
|
||||
|
||||
これで `origin` という名前が `REMOTE_URL` に関連付けられます。
|
||||
This associates the name `origin` with the `REMOTE_URL`.
|
||||
|
||||
`git remote set-url` を使えば、[リモートの URL を変更](/github/getting-started-with-github/managing-remote-repositories)できます。
|
||||
You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories).
|
||||
|
||||
## Choosing a URL for your remote repository
|
||||
|
||||
{% data variables.product.product_location %} で使用できるリポジトリを複製する方法は複数あります。
|
||||
There are several ways to clone repositories available on {% data variables.product.product_location %}.
|
||||
|
||||
アカウントにサインインしているときにリポジトリを表示すると、プロジェクトを自分のコンピュータに複製するために使用できるURLがリポジトリの詳細の下に表示されます.
|
||||
When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
|
||||
|
||||
For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
|
||||
|
||||
## HTTPS URL を使ってクローンを作成する
|
||||
## Cloning with HTTPS URLs
|
||||
|
||||
`https://` は、可視性に関係なく、すべてのリポジトリで使用できます。 `https://` のクローン URL は、ファイアウォールまたはプロキシの内側にいる場合でも機能します。
|
||||
The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy.
|
||||
|
||||
コマンドラインで、HTTPS URL を使用してリモートリポジトリに `git clone`、`git fetch`、`git pull` または `git push` を行った場合、{% data variables.product.product_name %} のユーザ名とパスワードの入力を求められます。 {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
|
||||
{% data reusables.command_line.provide-an-access-token %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント**:
|
||||
- 認証情報ヘルパーを使用すれば、{% data variables.product.prodname_dotcom %} と通信するたびに、{% data variables.product.prodname_dotcom %} の認証情報が Git で記憶されます。 詳細は「[Git に {% data variables.product.prodname_dotcom %} の認証情報をキャッシュする](/github/getting-started-with-github/caching-your-github-credentials-in-git)」を参照してください。
|
||||
- コマンドラインで {% data variables.product.product_name %} の認証なしでリポジトリを複製するために、クローンの代わりに、{% data variables.product.prodname_desktop %} を使用することができます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} から {% data variables.product.prodname_dotcom %} Desktop にリポジトリをクローンする](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)」を参照してください。
|
||||
**Tips**:
|
||||
- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
|
||||
- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghec %}SSH を使用したくてもポート 22 で接続できない場合は、HTTPS ポートを介する SSH を使用できる場合があります。 詳細は、「[HTTPS ポートを介して SSH を使用する](/github/authenticating-to-github/using-ssh-over-the-https-port)」を参照してください。{% endif %}
|
||||
{% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
|
||||
|
||||
## SSH URL を使ってクローンする
|
||||
## Cloning with SSH URLs
|
||||
|
||||
SSH URL は、SSH (安全なプロトコル) を介した Git リポジトリへのアクセスを提供します。 To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 詳しい情報については「[{% data variables.product.prodname_dotcom %} に SSH で接続する](/github/authenticating-to-github/connecting-to-github-with-ssh)」を参照してください。
|
||||
SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
|
||||
|
||||
SSH URL を使用して、`git clone`、`git fetch`、`git pull` または `git push` をリモートリポジトリに実行すると、パスワードの入力を求められ、SSH キーパスフレーズを入力する必要があります。 詳しい情報については[SSH キーのパスフレーズを使う](/github/authenticating-to-github/working-with-ssh-key-passphrases)を参照してください。
|
||||
When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
|
||||
|
||||
{% ifversion fpt or ghec %}SAML シングルサインオン (SSO) を使っている Organization にアクセスしている場合は、認証を受ける前に、Organization にアクセスする SSHキーを認可する必要があります。 詳しい情報については「[SAMLシングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」および「[SAML シングルサインオンで使うためにSSHキーを認可する](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)」を参照してください。{% endif %}
|
||||
{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント**: SSH URL は、お使いのコンピュータにリポジトリを作成する際にも、または本番サーバーにコードをデプロイする安全な方法としても使用できます。 デプロイスクリプトで SSH エージェント転送を使用して、サーバー上のキーの管理を回避することもできます。 詳細は「[SSH エージェント転送を使用する](/developers/overview/using-ssh-agent-forwarding)」を参照してください。
|
||||
**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
|
||||
## {% data variables.product.prodname_cli %} を使ってクローンを作成する
|
||||
## Cloning with {% data variables.product.prodname_cli %}
|
||||
|
||||
{% data variables.product.prodname_cli %} をインストールして、ターミナルで {% data variables.product.product_name %} ワークフローを使用することもできます。 詳しい情報については、「[{% data variables.product.prodname_cli %} について](/github-cli/github-cli/about-github-cli)」を参照してください。
|
||||
You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion not ghae %}
|
||||
## Subversion を使って複製する
|
||||
## Cloning with Subversion
|
||||
|
||||
[Subversion](https://subversion.apache.org/) クライアントを使用して、{% data variables.product.prodname_dotcom %} のリポジトリにアクセスすることもできます。 Subversion と Git では、提供する機能群に違いがあります。 詳しい情報については、「[Subversion と Git の違い](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)」を参照してください。
|
||||
You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
|
||||
|
||||
Subversion クライアントから {% data variables.product.prodname_dotcom %} のリポジトリにアクセスすることもできます。 詳細は、「[Subversion クライアントのサポート](/github/importing-your-projects-to-github/support-for-subversion-clients)」を参照してください。
|
||||
You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
|
||||
{% endif %}
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
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/
|
||||
- /articles/using-sublime-text-2-as-your-default-editor/
|
||||
- /textmate
|
||||
- /articles/using-textmate-as-your-default-editor
|
||||
- /articles/using-sublime-text-2-as-your-default-editor
|
||||
- /articles/associating-text-editors-with-git
|
||||
- /github/using-git/associating-text-editors-with-git
|
||||
- /github/getting-started-with-github/associating-text-editors-with-git
|
||||
@@ -16,42 +16,41 @@ versions:
|
||||
ghec: '*'
|
||||
shortTitle: Associate text editors
|
||||
---
|
||||
|
||||
{% mac %}
|
||||
|
||||
## エディタとして Atom を使う
|
||||
## Using Atom as your editor
|
||||
|
||||
1. [Atom](https://atom.io/)をインストールします。 詳しい情報については、Atomのドキュメンテーションの「[Atomのインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」を参照してください。
|
||||
1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 以下のコマンドを入力してください:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## エディタとして Visual Studio Code を使う
|
||||
## Using Visual Studio Code as your editor
|
||||
|
||||
1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。
|
||||
1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
|
||||
{% 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"
|
||||
```
|
||||
@@ -59,38 +58,38 @@ shortTitle: Associate text editors
|
||||
|
||||
{% windows %}
|
||||
|
||||
## エディタとして Atom を使う
|
||||
## Using Atom as your editor
|
||||
|
||||
1. [Atom](https://atom.io/)をインストールします。 詳しい情報については、Atomのドキュメンテーションの「[Atomのインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」を参照してください。
|
||||
1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 以下のコマンドを入力してください:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## エディタとして Visual Studio Code を使う
|
||||
## Using Visual Studio Code as your editor
|
||||
|
||||
1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。
|
||||
1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
|
||||
{% 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++ のドキュメンテーションで「[Getting started](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"
|
||||
```
|
||||
@@ -98,29 +97,29 @@ shortTitle: Associate text editors
|
||||
|
||||
{% linux %}
|
||||
|
||||
## エディタとして Atom を使う
|
||||
## Using Atom as your editor
|
||||
|
||||
1. [Atom](https://atom.io/)をインストールします。 詳しい情報については、Atomのドキュメンテーションの「[Atomのインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」を参照してください。
|
||||
1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 以下のコマンドを入力してください:
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## エディタとして Visual Studio Code を使う
|
||||
## Using Visual Studio Code as your editor
|
||||
|
||||
1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。
|
||||
1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
|
||||
{% 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"
|
||||
```
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Caching your GitHub credentials in Git
|
||||
redirect_from:
|
||||
- /firewalls-and-proxies/
|
||||
- /firewalls-and-proxies
|
||||
- /articles/caching-your-github-password-in-git
|
||||
- /github/using-git/caching-your-github-password-in-git
|
||||
- /github/using-git/caching-your-github-credentials-in-git
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 行終端を処理するようGitを設定する
|
||||
intro: diff における問題を回避するため、行終端を正しく処理できるよう Git を設定できます。
|
||||
title: Configuring Git to handle line endings
|
||||
intro: 'To avoid problems in your diffs, you can configure Git to properly handle line endings.'
|
||||
redirect_from:
|
||||
- /dealing-with-lineendings/
|
||||
- /line-endings/
|
||||
- /articles/dealing-with-line-endings/
|
||||
- /dealing-with-lineendings
|
||||
- /line-endings
|
||||
- /articles/dealing-with-line-endings
|
||||
- /articles/configuring-git-to-handle-line-endings
|
||||
- /github/using-git/configuring-git-to-handle-line-endings
|
||||
- /github/getting-started-with-github/configuring-git-to-handle-line-endings
|
||||
@@ -16,21 +16,20 @@ versions:
|
||||
ghec: '*'
|
||||
shortTitle: Handle line endings
|
||||
---
|
||||
|
||||
## About line endings
|
||||
キーボードで <kbd>return</kbd> を押すたびに、行終端と呼ばれる目に見えない文字が挿入されています。 行終端の処理は、オペレーティングシステムによって異なります。
|
||||
Every time you press <kbd>return</kbd> on your keyboard you insert an invisible character called a line ending. Different operating systems handle line endings differently.
|
||||
|
||||
When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
|
||||
|
||||
異なるオペレーティングシステムを使用しているユーザとも効果的にコラボレーションができるように、自動的に行終端を処理するよう Git を設定することができます。
|
||||
You can configure Git to handle line endings automatically so you can collaborate effectively with people who use different operating systems.
|
||||
|
||||
## 行終端のグローバル設定
|
||||
## Global settings for line endings
|
||||
|
||||
Git による行終端の扱い方を変更するには `git config core.autocrlf` コマンドを使用します。 必要な引数は 1 つです。
|
||||
The `git config core.autocrlf` command is used to change how Git handles line endings. It takes a single argument.
|
||||
|
||||
{% mac %}
|
||||
|
||||
On macOS, you simply pass `input` to the configuration. 例:
|
||||
On macOS, you simply pass `input` to the configuration. For example:
|
||||
|
||||
```shell
|
||||
$ git config --global core.autocrlf input
|
||||
@@ -41,7 +40,7 @@ $ git config --global core.autocrlf input
|
||||
|
||||
{% windows %}
|
||||
|
||||
Windows では、設定に `true` を渡すだけです。 例:
|
||||
On Windows, you simply pass `true` to the configuration. For example:
|
||||
|
||||
```shell
|
||||
$ git config --global core.autocrlf true
|
||||
@@ -53,7 +52,7 @@ $ git config --global core.autocrlf true
|
||||
|
||||
{% linux %}
|
||||
|
||||
Linux では、設定に `input` を渡すだけです。 例:
|
||||
On Linux, you simply pass `input` to the configuration. For example:
|
||||
|
||||
```shell
|
||||
$ git config --global core.autocrlf input
|
||||
@@ -62,75 +61,75 @@ $ git config --global core.autocrlf input
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
## リポジトリ単位での設定
|
||||
## Per-repository settings
|
||||
|
||||
オプションで *.gitattributes* ファイルを設定すれば、特定のリポジトリで Git が行終端をどう読み込むかを管理することもできます。 このファイルをリポジトリにコミットすると、すべてのリポジトリコントリビューターの `core.autocrlf` 設定がオーバーライドされます。 そのため、Git 設定と環境にかかわらずすべてのユーザで一貫した動作を確保できます。
|
||||
Optionally, you can configure a *.gitattributes* file to manage how Git reads line endings in a specific repository. When you commit this file to a repository, it overrides the `core.autocrlf` setting for all repository contributors. This ensures consistent behavior for all users, regardless of their Git settings and environment.
|
||||
|
||||
*.gitattributes* ファイルは、リポジトリのルートに作成し、他のファイルと同様にコミットする必要があります。
|
||||
The *.gitattributes* file must be created in the root of the repository and committed like any other file.
|
||||
|
||||
*.gitattributes* ファイルは 2 列で構成される表のようなものです:
|
||||
A *.gitattributes* file looks like a table with two columns:
|
||||
|
||||
* 左側は Git が一致させるファイル名です。
|
||||
* 右側はそのようなファイルに対して Git が使用すべき行終端の設定です。
|
||||
* On the left is the file name for Git to match.
|
||||
* On the right is the line ending configuration that Git should use for those files.
|
||||
|
||||
### サンプル
|
||||
### Example
|
||||
|
||||
以下は *.gitattributes* ファイルの例です。 リポジトリのテンプレートとして使用できます。
|
||||
Here's an example *.gitattributes* file. You can use it as a template for your repositories:
|
||||
|
||||
```
|
||||
# core.autocrlf を設定していない人のために、デフォルトの動作を設定する。
|
||||
# Set the default behavior, in case people don't have core.autocrlf set.
|
||||
* text=auto
|
||||
|
||||
# 常に正規化し、チェックアウトの際ネイティブの行終端に変換したい
|
||||
# テキストファイルを明示的に宣言する。
|
||||
# Explicitly declare text files you want to always be normalized and converted
|
||||
# to native line endings on checkout.
|
||||
*.c text
|
||||
*.h text
|
||||
|
||||
# チェックアウトの際常に CRLF を行終端とするファイルを宣言する。
|
||||
# Declare files that will always have CRLF line endings on checkout.
|
||||
*.sln text eol=crlf
|
||||
|
||||
# 完全にバイナリで変更すべきでないファイルをすべて示す。
|
||||
# Denote all files that are truly binary and should not be modified.
|
||||
*.png binary
|
||||
*.jpg binary
|
||||
```
|
||||
|
||||
上のように、まずファイルの種類を示し (`*.c`、`*.sln`、`*.png` など)、そのあとに区切り文字として空白文字を続け、そのあとに、そのファイルの種類に適用すべき設定 (`text`、`text eol=crlf`、`binary` など) を指定します。 以下、利用可能な設定を見てみましょう。
|
||||
You'll notice that files are matched—`*.c`, `*.sln`, `*.png`—, separated by a space, then given a setting—`text`, `text eol=crlf`, `binary`. We'll go over some possible settings below.
|
||||
|
||||
- `text=auto` Git が最善と判断する方法でファイルを処理します。 これは便利なデフォルトのオプションです。
|
||||
- `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option.
|
||||
|
||||
- `text eol=crlf` Git はチェックアウトの際常に行終端を `CRLF` に変換します。 OSX や Linux であったとしても、終端が `CRLF` でなければならないファイルにはこれを使用する必要があります。
|
||||
- `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux.
|
||||
|
||||
- `text eol=lf` Git はチェックアウトの際常に行終端を `LF` に変換します。 Windows であったとしても、終端が LF でなければならないファイルにはこれを使用する必要があります。
|
||||
- `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows.
|
||||
|
||||
- `binary` Git は指定されているファイルがテキストではなく、変更を試みるべきではないと判断します。 `binary` 設定は `-text -diff` のエイリアスでもあります。
|
||||
- `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`.
|
||||
|
||||
## 行終端を変更した後でリポジトリを更新
|
||||
## Refreshing a repository after changing line endings
|
||||
|
||||
`core.autocrlf` オプションを設定するか、または *.gitattributes* ファイルをコミットするとき、自分で更新したことがないファイルが変更されていることを Git が報告する場合があります。 これは、新しい設定に合致するように Git が行終端を変更したということです。
|
||||
When you set the `core.autocrlf` option or commit a *.gitattributes* file, you may find that Git reports changes to files that you have not modified. Git has changed line endings to match your new configuration.
|
||||
|
||||
リポジトリのすべての行終端が新しい設定と一致するようにするには、Git でファイルをバックアップし、リポジトリ ( `git` は除いて) のすべてのファイルを削除してから、ファイルを一度にすべて復元します。
|
||||
To ensure that all the line endings in your repository match your new configuration, backup your files with Git, delete all files in your repository (except the `.git` directory), then restore the files all at once.
|
||||
|
||||
1. 作業結果を失うことのないよう、Git で現在のファイルを保存します。
|
||||
1. Save your current files in Git, so that none of your work is lost.
|
||||
```shell
|
||||
$ git add . -u
|
||||
$ git commit -m "Saving files before refreshing line endings"
|
||||
```
|
||||
2. 変更したファイルをすべて再度追加し、行終端を正規化します。
|
||||
2. Add all your changed files back and normalize the line endings.
|
||||
```shell
|
||||
$ git add --renormalize .
|
||||
```
|
||||
3. 書き直し、正規化したファイルを表示します。
|
||||
3. Show the rewritten, normalized files.
|
||||
```shell
|
||||
$ git status
|
||||
```
|
||||
4. 変更をリポジトリにコミットします。
|
||||
4. Commit the changes to your repository.
|
||||
```shell
|
||||
$ git commit -m "Normalize all the line endings"
|
||||
```
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- Pro Git ブックの「[Git のカスタマイズ - Git の属性](https://git-scm.com/book/en/Customizing-Git-Git-Attributes)」
|
||||
- Git の man ページの [git-config](https://git-scm.com/docs/git-config)
|
||||
- Pro Git ブックの「[使い始める - 最初の Git の構成](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup)」
|
||||
- [Tim Clem](https://github.com/tclem) による「[Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/)」
|
||||
- [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book
|
||||
- [git-config](https://git-scm.com/docs/git-config) in the man pages for Git
|
||||
- [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book
|
||||
- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Git のワークフロー
|
||||
intro: '{% data variables.product.prodname_dotcom %} フローは、軽量でブランチベースのワークフローで、規則的にデプロイされる Team とプロジェクトをサポートしています。'
|
||||
title: Git workflows
|
||||
intro: '{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow that supports teams and projects that deploy regularly.'
|
||||
redirect_from:
|
||||
- /articles/what-is-a-good-git-workflow/
|
||||
- /articles/what-is-a-good-git-workflow
|
||||
- /articles/git-workflows
|
||||
- /github/using-git/git-workflows
|
||||
- /github/getting-started-with-github/git-workflows
|
||||
@@ -13,5 +13,4 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_dotcom %} フローの手法を使うと、Team の機能と {% data variables.product.prodname_dotcom %} でのコラボレーションを標準化することができます。 For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
|
||||
You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
|
||||
|
||||
@@ -1,66 +1,66 @@
|
||||
---
|
||||
title: ファイルを無視する
|
||||
title: Ignoring files
|
||||
redirect_from:
|
||||
- /git-ignore/
|
||||
- /ignore-files/
|
||||
- /git-ignore
|
||||
- /ignore-files
|
||||
- /articles/ignoring-files
|
||||
- /github/using-git/ignoring-files
|
||||
- /github/getting-started-with-github/ignoring-files
|
||||
- /github/getting-started-with-github/getting-started-with-git/ignoring-files
|
||||
intro: '{% data variables.product.product_name %} にチェックインしたくないファイルを無視するように Git を設定することができます。'
|
||||
intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.product_name %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
## Configuring ignored files for a single repository
|
||||
|
||||
## 単一リポジトリについて無視するファイルを設定する
|
||||
You can create a *.gitignore* file in your repository's root directory to tell Git which files and directories to ignore when you make a commit.
|
||||
To share the ignore rules with other users who clone the repository, commit the *.gitignore* file in to your repository.
|
||||
|
||||
リポジトリのルートディレクトリで *.gitignore* ファイルを作成すると、コミットの際にどのファイルとディレクトリを無視するか Git に指示できます。 リポジトリのクローンを作成する他のユーザと、この無視ルールを共有するには、*.gitignore* ファイルをリポジトリにコミットします。
|
||||
|
||||
GitHub は、一般的なオペレーティング システム、環境、言語で推奨される *.gitignore* ファイルの公式なリストを、`github/gitignore` パブリックリポジトリに保持します。 gitignore.io ファイルを使用して、お使いのオペレーティング システム、プログラミング言語、または IDE に応じた *.gitignore* ファイルを作成することもできます。 詳細は「[github/gitignore](https://github.com/github/gitignore)」および「[gitignore.io](https://www.gitignore.io/)」のサイトを参照してください。
|
||||
GitHub maintains an official list of recommended *.gitignore* files for many popular operating systems, environments, and languages in the `github/gitignore` public repository. You can also use gitignore.io to create a *.gitignore* file for your operating system, programming language, or IDE. For more information, see "[github/gitignore](https://github.com/github/gitignore)" and the "[gitignore.io](https://www.gitignore.io/)" site.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. Git リポジトリの場所まで移動します。
|
||||
3. リポジトリに *.gitignore* ファイルを作成します。
|
||||
2. Navigate to the location of your Git repository.
|
||||
3. Create a *.gitignore* file for your repository.
|
||||
```shell
|
||||
$ touch .gitignore
|
||||
```
|
||||
|
||||
If the command succeeds, there will be no output.
|
||||
|
||||
For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository.
|
||||
|
||||
たとえば *.gitignore* ファイルは、Octocat リポジトリで 「[一般的な .gitignore 設定](https://gist.github.com/octocat/9257657)」を参照してください。
|
||||
|
||||
すでにチェックインしたファイルを無視したい場合は、追跡を解除してから、それを無視するルールを追加します。 ターミナルから、ファイルの追跡を解除してください。
|
||||
If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file.
|
||||
|
||||
```shell
|
||||
$ git rm --cached <em>ファイル名</em>
|
||||
$ git rm --cached <em>FILENAME</em>
|
||||
```
|
||||
|
||||
## コンピューター上のすべてのリポジトリについて無視するファイルを設定する
|
||||
## Configuring ignored files for all repositories on your computer
|
||||
|
||||
グローバルな *.gitignore* ファイルも作成して、お使いのコンピューター上の各 Git リポジトリでファイルを無視するルールを定義することもできます。 たとえば、*~/.gitignore_global* にファイルを作成し、そこにルールを追加することができます。
|
||||
You can also create a global *.gitignore* file to define a list of rules for ignoring files in every Git repository on your computer. For example, you might create the file at *~/.gitignore_global* and add some rules to it.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. すべての Git リポジトリについて除外ファイル *~/.gitignore_global* を使用するよう Git を設定します。
|
||||
2. Configure Git to use the exclude file *~/.gitignore_global* for all Git repositories.
|
||||
```shell
|
||||
$ git config --global core.excludesfile ~/.gitignore_global
|
||||
```
|
||||
|
||||
## *.gitignore* ファイルを作成せずにローカルファイルを除外する
|
||||
## Excluding local files without creating a *.gitignore* file
|
||||
|
||||
他のユーザと共有される *.gitignore* ファイルを作成したくない場合は、リポジトリにコミットされないルールを作成することもできます。 ローカルで生成され、他のユーザが生成することは想定されないファイル、たとえば自分のエディターで作成されるファイルなどを無視するときに使える方法です。
|
||||
If you don't want to create a *.gitignore* file to share with others, you can create rules that are not committed with the repository. You can use this technique for locally-generated files that you don't expect other users to generate, such as files created by your editor.
|
||||
|
||||
使い慣れたテキストエディターを使って、Git リポジトリのルートにある *.git/info/exclude* というファイルを開きます。 ここで追加するルールはチェックインされないので、ローカル リポジトリにあるファイルだけが無視されます。
|
||||
Use your favorite text editor to open the file called *.git/info/exclude* within the root of your Git repository. Any rule you add here will not be checked in, and will only ignore files for your local repository.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. Git リポジトリの場所まで移動します。
|
||||
3. 使い慣れたテキストエディターを使って、*.git/info/exclude* ファイルを開きます。
|
||||
2. Navigate to the location of your Git repository.
|
||||
3. Using your favorite text editor, open the file *.git/info/exclude*.
|
||||
|
||||
## 参考リンク
|
||||
## Further Reading
|
||||
|
||||
* Pro Git ブックの「[ファイルを無視する](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring)」
|
||||
* Git の man ページの [.gitignore](https://git-scm.com/docs/gitignore)
|
||||
* github/gitignore リポジトリにある、[有益で充実した *.gitignore* テンプレート](https://github.com/github/gitignore) のコレクション
|
||||
* [gitignore.io](https://www.gitignore.io/) サイト
|
||||
* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Pro Git book
|
||||
* [.gitignore](https://git-scm.com/docs/gitignore) in the man pages for Git
|
||||
* [A collection of useful *.gitignore* templates](https://github.com/github/gitignore) in the github/gitignore repository
|
||||
* [gitignore.io](https://www.gitignore.io/) site
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /github/using-git/getting-started-with-git-and-github
|
||||
- /github/using-git/learning-about-git
|
||||
- /articles/learning-about-git
|
||||
- /github/getting-started-with-github/getting-started-with-git/
|
||||
- /github/getting-started-with-github/getting-started-with-git
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: リモートリポジトリを管理する
|
||||
intro: 'お手元のコンピューター上にあるローカルリポジトリと、{% data variables.product.product_name %} にホストされているリポジトリを使用する方法を学びます。'
|
||||
title: Managing remote repositories
|
||||
intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.'
|
||||
redirect_from:
|
||||
- /categories/18/articles/
|
||||
- /remotes/
|
||||
- /categories/managing-remotes/
|
||||
- /categories/18/articles
|
||||
- /remotes
|
||||
- /categories/managing-remotes
|
||||
- /articles/managing-remote-repositories
|
||||
- /articles/adding-a-remote
|
||||
- /github/using-git/adding-a-remote
|
||||
@@ -25,23 +25,22 @@ versions:
|
||||
ghec: '*'
|
||||
shortTitle: Manage remote repositories
|
||||
---
|
||||
|
||||
## Adding a remote repository
|
||||
|
||||
To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
|
||||
|
||||
`git remote add` コマンドは 2 つの引数を取ります:
|
||||
* リモート名。たとえば `origin`
|
||||
* リモート URL。たとえば `https://{% data variables.command_line.backticks %}/user/repo.git`
|
||||
The `git remote add` command takes two arguments:
|
||||
* A remote name, for example, `origin`
|
||||
* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git`
|
||||
|
||||
例:
|
||||
For example:
|
||||
|
||||
```shell
|
||||
$ git remote add origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git
|
||||
# 新しいリモートの設定
|
||||
# Set a new remote
|
||||
|
||||
$ git remote -v
|
||||
# 新しいリモートの検証
|
||||
# Verify new remote
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git (push)
|
||||
```
|
||||
@@ -58,7 +57,7 @@ $ git remote add origin https://{% data variables.command_line.codeblock %}/octo
|
||||
```
|
||||
|
||||
To fix this, you can:
|
||||
* 新しいリモートに別の名前を使う.
|
||||
* Use a different name for the new remote.
|
||||
* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
|
||||
* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
|
||||
|
||||
@@ -72,34 +71,34 @@ The `git remote set-url` command changes an existing remote repository URL.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
`git remote set-url`コマンドは 2 つの引数を取ります:
|
||||
The `git remote set-url` command takes two arguments:
|
||||
|
||||
* 既存のリモート名。 `origin` や `upstream` がよく使われます。
|
||||
* リモートの新しい URL。 例:
|
||||
* HTTPS を使うよう更新する場合、URL は以下のようになります:
|
||||
* An existing remote name. For example, `origin` or `upstream` are two common choices.
|
||||
* A new URL for the remote. For example:
|
||||
* If you're updating to use HTTPS, your URL might look like:
|
||||
```shell
|
||||
https://{% data variables.command_line.backticks %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
|
||||
```
|
||||
* SSH を使うよう更新する場合、URL は以下のようになります:
|
||||
* If you're updating to use SSH, your URL might look like:
|
||||
```shell
|
||||
git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
|
||||
```
|
||||
|
||||
### リモート URL の SSH から HTTPS への切り替え
|
||||
### Switching remote URLs from SSH to HTTPS
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. ワーキングディレクトリをローカルプロジェクトに変更します。
|
||||
3. 変更したいリモートの名前を取得するため、既存のリモート一覧を表示します。
|
||||
2. Change the current working directory to your local project.
|
||||
3. List your existing remotes in order to get the name of the remote you want to change.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (fetch)
|
||||
> origin git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
|
||||
```
|
||||
4. `git remote set-url` コマンドでリモートの URL を SSH から HTTPS に変更します。
|
||||
4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command.
|
||||
```shell
|
||||
$ git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
|
||||
```
|
||||
5. リモート URL が変更されたことを検証します。
|
||||
5. Verify that the remote URL has changed.
|
||||
```shell
|
||||
$ git remote -v
|
||||
# Verify new remote URL
|
||||
@@ -107,25 +106,25 @@ git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
次にリモートリポジトリに対して `git fetch`、`git pull`、または `git push` を実行するときに、GitHub ユーザ名とパスワードを求められます。 {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
|
||||
You can [use a credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git) so Git will remember your GitHub username and personal access token every time it talks to GitHub.
|
||||
|
||||
### リモート URL の HTTPS から SSH への切り替え
|
||||
### Switching remote URLs from HTTPS to SSH
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. ワーキングディレクトリをローカルプロジェクトに変更します。
|
||||
3. 変更したいリモートの名前を取得するため、既存のリモート一覧を表示します。
|
||||
2. Change the current working directory to your local project.
|
||||
3. List your existing remotes in order to get the name of the remote you want to change.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
|
||||
```
|
||||
4. `git remote set-url` コマンドでリモートの URL を HTTPS から SSH に変更します。
|
||||
4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command.
|
||||
```shell
|
||||
$ git remote set-url origin git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
|
||||
```
|
||||
5. リモート URL が変更されたことを検証します。
|
||||
5. Verify that the remote URL has changed.
|
||||
```shell
|
||||
$ git remote -v
|
||||
# Verify new remote URL
|
||||
@@ -135,103 +134,104 @@ You can [use a credential helper](/github/getting-started-with-github/caching-yo
|
||||
|
||||
### Troubleshooting: No such remote '[name]'
|
||||
|
||||
このエラーは、変更しようとしたリモートが存在しないことを意味します。
|
||||
This error means that the remote you tried to change doesn't exist:
|
||||
|
||||
```shell
|
||||
$ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife
|
||||
> fatal: No such remote 'sofake'
|
||||
```
|
||||
|
||||
リモート名を正しく入力したか確認してください。
|
||||
Check that you've correctly typed the remote name.
|
||||
|
||||
## Renaming a remote repository
|
||||
|
||||
Use the `git remote rename` command to rename an existing remote.
|
||||
|
||||
`git remote rename` コマンドは、次の 2 つの引数を取ります:
|
||||
* 既存のリモート名（`origin` など）
|
||||
* リモートの新しい名前 (`destination` など)
|
||||
The `git remote rename` command takes two arguments:
|
||||
* An existing remote name, for example, `origin`
|
||||
* A new name for the remote, for example, `destination`
|
||||
|
||||
## サンプル
|
||||
## Example
|
||||
|
||||
次の例は (推奨されるとおり) [HTTPS を使用してクローンを作成](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)したと想定しています。
|
||||
These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
|
||||
|
||||
```shell
|
||||
$ git remote -v
|
||||
# 既存のリモートを表示
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>オーナー</em>/<em>リポジトリ</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>オーナー</em>/<em>リポジトリ</em>.git (push)
|
||||
# View existing remotes
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
|
||||
|
||||
$ git remote rename origin destination
|
||||
# リモート名を「origin」から「destination」に変更
|
||||
# Change remote name from 'origin' to 'destination'
|
||||
|
||||
$ git remote -v
|
||||
# リモートの新しい名前を確認
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>オーナー</em>/<em>リポジトリ</em>.git (fetch)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>オーナー</em>/<em>リポジトリ</em>.git (push)
|
||||
# Verify remote's new name
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]'
|
||||
|
||||
This error means that the old remote name you typed doesn't exist.
|
||||
|
||||
現在どのリモートが存在するかは、次のように `git remote -v` コマンドでチェックできます:
|
||||
You can check which remotes currently exist with the `git remote -v` command:
|
||||
|
||||
```shell
|
||||
$ git remote -v
|
||||
# 既存のリモートを表示
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>コードオーナー</em>/<em>リポジトリ</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>コードオーナー</em>/<em>リポジトリ</em>.git (push)
|
||||
# View existing remotes
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
### Troubleshooting: Remote [new name] already exists
|
||||
|
||||
このエラーは、使用しようとしたリモート名がすでに存在する、という意味です。 To solve this, either use a different remote name, or rename the original remote.
|
||||
This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote.
|
||||
|
||||
## Removing a remote repository
|
||||
## Removing a remote repository
|
||||
|
||||
Use the `git remote rm` command to remove a remote URL from your repository.
|
||||
|
||||
`git remote rm` コマンドは 1 つの引数を取ります:
|
||||
* リモート名 (`destination` など)
|
||||
The `git remote rm` command takes one argument:
|
||||
* A remote name, for example, `destination`
|
||||
|
||||
## サンプル
|
||||
## Example
|
||||
|
||||
次の例は (推奨されるとおり) [HTTPS を使用してクローンを作成](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)したと想定しています。
|
||||
These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
|
||||
|
||||
```shell
|
||||
$ git remote -v
|
||||
# 現在のリモートの表示
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>オーナー/リポジトリ</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>オーナー/リポジトリ</em>.git (push)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>フォーカー/リポジトリ</em>.git (fetch)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>フォーカー/リポジトリ</em>.git (push)
|
||||
# View current remotes
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (fetch)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (push)
|
||||
|
||||
$ git remote rm destination
|
||||
# リモートの削除
|
||||
# Remove remote
|
||||
$ git remote -v
|
||||
# 削除されていることの検証
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>オーナー/リポジトリ</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>オーナー/リポジトリ</em>.git (push)
|
||||
# Verify it's gone
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
{% warning %}
|
||||
|
||||
**メモ**: `git remote rm` はリモートリポジトリをサーバから削除するわけではありません。 リモートとその参照をローカルリポジトリから削除するだけです。
|
||||
**Note**: `git remote rm` does not delete the remote repository from the server. It simply
|
||||
removes the remote and its references from your local repository.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### Troubleshooting: Could not remove config section 'remote.[name]'
|
||||
|
||||
このエラーは、削除しようとしたリモートが存在しないことを意味します。
|
||||
This error means that the remote you tried to delete doesn't exist:
|
||||
|
||||
```shell
|
||||
$ git remote rm sofake
|
||||
> error: Could not remove config section 'remote.sofake'
|
||||
```
|
||||
|
||||
リモート名を正しく入力したか確認してください。
|
||||
Check that you've correctly typed the remote name.
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [書籍 _Pro Git_ のリモートでの作業](https://git-scm.com/book/ja/v2/Git-の基本-リモートでの作業)
|
||||
- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: GitHub 上のアクセス権限
|
||||
title: Access permissions on GitHub
|
||||
redirect_from:
|
||||
- /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do/
|
||||
- /articles/what-are-the-different-types-of-team-permissions/
|
||||
- /articles/what-are-the-different-access-permissions/
|
||||
- /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do
|
||||
- /articles/what-are-the-different-types-of-team-permissions
|
||||
- /articles/what-are-the-different-access-permissions
|
||||
- /articles/access-permissions-on-github
|
||||
- /github/getting-started-with-github/access-permissions-on-github
|
||||
- /github/getting-started-with-github/learning-about-github/access-permissions-on-github
|
||||
intro: 個人のリポジトリにはコラボレータに読み取り/書き込みアクセスを許可できる一方、Organization のメンバーは、Organization のリポジトリに対してより精細なアクセス権限を持つことができます。
|
||||
intro: 'While you can grant read/write access to collaborators on a personal repository, members of an organization can have more granular access permissions for the organization''s repositories.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -18,24 +18,23 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: Access permissions
|
||||
---
|
||||
## Personal user accounts
|
||||
|
||||
## 個人ユーザアカウント
|
||||
A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)."
|
||||
|
||||
ユーザアカウントが所有するリポジトリは、*リポジトリオーナー*と*コラボレータ*という 2 つの権限レベルを持ちます。 詳しい情報については[ユーザアカウントのリポジトリ権限レベル](/articles/permission-levels-for-a-user-account-repository)を参照してください。
|
||||
## Organization accounts
|
||||
|
||||
## Organization アカウント
|
||||
|
||||
Organization のメンバーは、*owner (オーナー)*{% ifversion fpt or ghec %}、*billing manager (支払いマネージャー)*、{% endif %}あるいは*member (メンバー)* ロールを持つことができます。 オーナーは、Organization に対する完全な管理者アクセスを持ち{% ifversion fpt or ghec %}、支払いマネージャーは支払いの設定を管理でき{% endif %}ます。 メンバーは、その他の人のデフォルトのロールです。 Team を使って、複数のメンバーのアクセス権限を一度に管理できます。 詳しい情報については、以下を参照してください。
|
||||
Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
|
||||
- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
|
||||
- [Organization のプロジェクトボード権限](/articles/project-board-permissions-for-an-organization)
|
||||
- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
|
||||
- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
|
||||
- [Team について](/articles/about-teams)
|
||||
- "[About teams](/articles/about-teams)"
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## Enterprise アカウント
|
||||
## Enterprise accounts
|
||||
|
||||
*Enterprise のオーナー*は、Enterprise アカウントに対して最大の力を持ち、Enterprise アカウントであらゆるアクションを取ることができます。 *支払いマネージャー*は、Enterprise アカウントの支払い設定を管理できます。 Enterprise アカウントが所有する Organization のメンバーと外部コラボレーターは、自動的に Enterprise アカウントのメンバーになりますが、Enterprise アカウントそのものやその設定にはアクセスできません。 詳しい情報については、「[Enterprise アカウントのロール](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)」を参照してください。
|
||||
*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
|
||||
|
||||
If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
|
||||
|
||||
@@ -43,6 +42,6 @@ If an enterprise uses {% data variables.product.prodname_emus %}, members are pr
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- 「[{% data variables.product.prodname_dotcom %}アカウントの種類](/articles/types-of-github-accounts)」
|
||||
- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: GitHub について学ぶ
|
||||
title: Learning about GitHub
|
||||
intro: 'Learn how you can use {% data variables.product.company_short %} products to improve your software management process and collaborate with other people.'
|
||||
redirect_from:
|
||||
- /articles/learning-about-github
|
||||
- /github/getting-started-with-github/learning-about-github/
|
||||
- /github/getting-started-with-github/learning-about-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: GitHub アカウントの種類
|
||||
intro: 'ユーザアカウントは {% data variables.product.product_location %} 上での身分証明となります。 Your user account can be a member of any number of organizations.{% ifversion fpt or ghec %} Organizations can belong to enterprise accounts.{% endif %}'
|
||||
title: Types of GitHub accounts
|
||||
intro: 'Your user account is your identity on {% data variables.product.product_location %}. Your user account can be a member of any number of organizations.{% ifversion fpt or ghec %} Organizations can belong to enterprise accounts.{% endif %}'
|
||||
redirect_from:
|
||||
- /manage-multiple-clients/
|
||||
- /managing-clients/
|
||||
- /articles/what-s-the-difference-between-user-and-organization-accounts/
|
||||
- /articles/differences-between-user-and-organization-accounts/
|
||||
- /manage-multiple-clients
|
||||
- /managing-clients
|
||||
- /articles/what-s-the-difference-between-user-and-organization-accounts
|
||||
- /articles/differences-between-user-and-organization-accounts
|
||||
- /articles/types-of-github-accounts
|
||||
- /github/getting-started-with-github/types-of-github-accounts
|
||||
- /github/getting-started-with-github/learning-about-github/types-of-github-accounts
|
||||
@@ -21,26 +21,25 @@ topics:
|
||||
- Desktop
|
||||
- Security
|
||||
---
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
各 {% data variables.product.product_name %} 製品の機能の完全なリストについては、「[{% data variables.product.prodname_dotcom %} の製品](/github/getting-started-with-github/githubs-products)」を参照してください。
|
||||
For a full list of features for each {% data variables.product.product_name %} product, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)."
|
||||
{% endif %}
|
||||
|
||||
## 個人ユーザアカウント
|
||||
## Personal user accounts
|
||||
|
||||
{% data variables.product.product_location %} を使用するすべての人は、次のような独自のユーザーアカウントを持っています。
|
||||
Every person who uses {% data variables.product.product_location %} has their own user account, which includes:
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
- {% data variables.product.prodname_free_user %} での無制限のパブリックリポジトリおよびプライベートリポジトリ
|
||||
- {% data variables.product.prodname_free_user %} での無制限のコラボレータ
|
||||
- {% data variables.product.prodname_pro %} でのプライベートリポジトリの追加機能
|
||||
- [リポジトリのコラボレーターを招待する](/articles/inviting-collaborators-to-a-personal-repository)機能
|
||||
- Unlimited public and private repositories with {% data variables.product.prodname_free_user %}
|
||||
- Unlimited collaborators with {% data variables.product.prodname_free_user %}
|
||||
- Additional features for private repositories with {% data variables.product.prodname_pro %}
|
||||
- Ability to [invite repository collaborators](/articles/inviting-collaborators-to-a-personal-repository)
|
||||
|
||||
{% else %}
|
||||
|
||||
- 無制限のリポジトリおよび[コラボレーター](/articles/permission-levels-for-a-user-account-repository)
|
||||
- [リポジトリのコラボレーターを無制限に追加する](/articles/inviting-collaborators-to-a-personal-repository)機能
|
||||
- Unlimited repositories and [collaborators](/articles/permission-levels-for-a-user-account-repository)
|
||||
- Ability to [add unlimited repository collaborators](/articles/inviting-collaborators-to-a-personal-repository)
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -48,10 +47,10 @@ topics:
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント**:
|
||||
**Tips**:
|
||||
|
||||
- 個人での使用や仕事での使用など、1 つのアカウントを複数の目的で使用できます。 複数のアカウントを作成することはおすすめしません。 詳細は「[複数のユーザアカウントをマージする](/articles/merging-multiple-user-accounts)」を参照してください。
|
||||
- ユーザアカウントは人間のためのものですが、必要に応じて継続的インテグレーションボットなどのロボットに付与することもできます。
|
||||
- You can use one account for multiple purposes, such as for personal use and business use. We do not recommend creating more than one account. For more information, see "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)."
|
||||
- User accounts are intended for humans, but you can give one to a robot, such as a continuous integration bot, if necessary.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -59,7 +58,7 @@ topics:
|
||||
|
||||
{% tip %}
|
||||
|
||||
**参考**: ユーザアカウントはもともとは人間のためのものですが、必要に応じて継続的インテグレーションボットなどのロボットに付与することもできます。
|
||||
**Tip**: User accounts are intended for humans, but you can give one to a robot, such as a continuous integration bot, if necessary.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -73,22 +72,22 @@ With {% data variables.product.prodname_emus %}, instead of using your personal
|
||||
{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
{% endif %}
|
||||
|
||||
## Organization アカウント
|
||||
## Organization accounts
|
||||
|
||||
Organization は、多くの人がいくつものプロジェクトにわたって同時にコラボレーションできる共有アカウントです。 オーナーと管理者は、Organizationのデータとプロジェクトへのメンバーのアクセスを、洗練されたセキュリティ及び管理機能で管理できます。
|
||||
Organizations are shared accounts where groups of people can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features.
|
||||
|
||||
{% data reusables.organizations.organizations_include %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## Enterprise アカウント
|
||||
## Enterprise accounts
|
||||
|
||||
Enterprise アカウントを使用すると、複数の {% data variables.product.prodname_dotcom_the_website %} Organization のポリシーと支払いを集中管理できます。 {% data reusables.gated-features.enterprise-accounts %}
|
||||
With enterprise accounts, you can centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations. {% data reusables.gated-features.enterprise-accounts %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
{% ifversion fpt or ghec %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"
|
||||
- 「[{% data variables.product.prodname_dotcom %} の製品](/articles/githubs-products)」{% endif %}
|
||||
- 「[新しい Organization アカウントを作成する](/articles/creating-a-new-organization-account)」
|
||||
- "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)"{% endif %}
|
||||
- "[Creating a new organization account](/articles/creating-a-new-organization-account)"
|
||||
|
||||
@@ -40,16 +40,16 @@ Once you choose the account type you would like, you can proceed to setting up y
|
||||
To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage.
|
||||
### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
#### 1. Organizationについて
|
||||
Organization は、多くの人がいくつものプロジェクトにわたって同時にコラボレーションできる共有アカウントです。 With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. 詳細は「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。
|
||||
#### 1. About organizations
|
||||
Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
|
||||
#### 2. Creating or upgrading an organization account
|
||||
|
||||
To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。
|
||||
To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
|
||||
|
||||
Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)."
|
||||
#### 3. Setting up and managing billing
|
||||
|
||||
When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [14-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
|
||||
Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
|
||||
|
||||
@@ -62,21 +62,21 @@ To get an enterprise account created for you, contact [{% data variables.product
|
||||
|
||||
{% endnote %}
|
||||
|
||||
#### 1. Enterprise アカウントについて
|
||||
#### 1. About enterprise accounts
|
||||
|
||||
An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. 詳細は「[Enterprise アカウントについて](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)」を参照してください。
|
||||
#### 2. Enterprise アカウントに Organization を追加する
|
||||
An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
|
||||
#### 2. Adding organizations to your enterprise account
|
||||
|
||||
Enterprise アカウント内に、新しい Organization を作成して管理できます。 For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
|
||||
You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
|
||||
|
||||
Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account.
|
||||
#### 3. Enterprise アカウントのプランおよび利用状況を表示する
|
||||
#### 3. Viewing the subscription and usage for your enterprise account
|
||||
You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
|
||||
|
||||
## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
### Managing members and teams in your organization
|
||||
You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization.
|
||||
You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization.
|
||||
#### 1. Managing members of your organization
|
||||
{% data reusables.getting-started.managing-org-members %}
|
||||
#### 2. Organization permissions and roles
|
||||
@@ -96,13 +96,13 @@ If your enterprise uses {% data variables.product.prodname_emus %}, your members
|
||||
If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below.
|
||||
|
||||
#### 1. Assigning roles in an enterprise
|
||||
By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. 詳しい情報については、「[Enterprise アカウントのロール](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)」を参照してください。
|
||||
#### 2. Enterprise を管理するようユーザを招待する
|
||||
By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
|
||||
#### 2. Inviting people to manage your enterprise
|
||||
You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
|
||||
|
||||
You can also grant enterprise members the ability to manage support tickets in the support portal. 詳しい情報については「[Enterpriseのサポート資格の管理](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)」を参照してください。
|
||||
#### 3. Enterprise の人を表示する
|
||||
To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. 詳しい情報については、「[Enterprise の人を表示する](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)」を参照してください。
|
||||
You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
|
||||
#### 3. Viewing people in your enterprise
|
||||
To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
|
||||
|
||||
## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
@@ -124,12 +124,12 @@ You can help keep your organization secure by requiring two-factor authenticatio
|
||||
If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
|
||||
|
||||
Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
|
||||
#### 5. Organization の Team 同期を管理する
|
||||
Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 詳細は「[Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)」を参照してください。
|
||||
#### 5. Managing team synchronization for your organization
|
||||
Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)."
|
||||
|
||||
### Managing security for an {% data variables.product.prodname_emu_enterprise %}
|
||||
|
||||
With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP.
|
||||
With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP.
|
||||
|
||||
#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %}
|
||||
|
||||
@@ -141,23 +141,23 @@ You can connect teams in your organizations to security groups in your identity
|
||||
|
||||
#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %}
|
||||
|
||||
You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. 詳しい情報については、「[Enterprise にセキュリティ設定のポリシーを適用する](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)」以下を参照してください。
|
||||
You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
|
||||
|
||||
#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %}
|
||||
{% data reusables.getting-started.enterprise-advanced-security %}
|
||||
|
||||
### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}
|
||||
To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features.
|
||||
To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features.
|
||||
|
||||
#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account
|
||||
Enterprise のオーナーは、Enterprise アカウントが所有するすべての Organization で、Organization のメンバー、支払いマネージャー、外部コラボレーターに対して個人アカウントをセキュアに保つために 2 要素認証の使用を義務化できます。 Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account.
|
||||
Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account.
|
||||
|
||||
For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
|
||||
#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account
|
||||
You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. 詳しい情報については、「[Enterprise のアイデンティティとアクセス管理について](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)」を参照してください。
|
||||
You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
|
||||
|
||||
#### 3. Managing team synchronization
|
||||
You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. 詳しい情報については、「[Enterprise アカウントで Organization の Team 同期を管理する](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)」参照してください。
|
||||
You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
|
||||
|
||||
#### 4. Enforcing policies for Advanced Security features in your enterprise account
|
||||
{% data reusables.getting-started.enterprise-advanced-security %}
|
||||
@@ -186,19 +186,19 @@ You can also restrict email notifications for your enterprise account so that en
|
||||
## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %}
|
||||
Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work.
|
||||
|
||||
### 1. {% data variables.product.prodname_marketplace %}を使用する
|
||||
### 1. Using {% data variables.product.prodname_marketplace %}
|
||||
{% data reusables.getting-started.marketplace %}
|
||||
### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
|
||||
{% data reusables.getting-started.api %}
|
||||
### 3. Building {% data variables.product.prodname_actions %}
|
||||
{% data reusables.getting-started.actions %}
|
||||
### 4. Publishing and managing {% data variables.product.prodname_registry %}
|
||||
### 4. Publishing and managing {% data variables.product.prodname_registry %}
|
||||
{% data reusables.getting-started.packages %}
|
||||
### 5. {% data variables.product.prodname_pages %}を使用する
|
||||
### 5. Using {% data variables.product.prodname_pages %}
|
||||
{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
|
||||
## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community
|
||||
|
||||
Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community.
|
||||
Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community.
|
||||
### 1. Learning with {% data variables.product.prodname_learning %}
|
||||
Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot.
|
||||
|
||||
@@ -206,7 +206,7 @@ For more information, see "[Git and {% data variables.product.prodname_dotcom %}
|
||||
### 2. Supporting the open source community
|
||||
{% data reusables.getting-started.sponsors %}
|
||||
|
||||
### 3. {% data variables.contact.github_support %} への連絡
|
||||
### 3. Contacting {% data variables.contact.github_support %}
|
||||
{% data reusables.getting-started.contact-support %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. 詳細は「[{% data variables.product.prodname_ghe_cloud %} サポート](/github/working-with-github-support/github-enterprise-cloud-support)」を参照してください。
|
||||
{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)."
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: ソーシャル機能
|
||||
title: Be social
|
||||
redirect_from:
|
||||
- /be-social/
|
||||
- /be-social
|
||||
- /articles/be-social
|
||||
- /github/getting-started-with-github/be-social
|
||||
- /github/getting-started-with-github/quickstart/be-social
|
||||
intro: '{% data variables.product.prodname_dotcom %} 上で、人々、リポジトリ、Organization と関わることができます。 個人ダッシュボードから、他の人々がどんな作業をしていて、何とつながっているのかを見てください。'
|
||||
intro: 'You can interact with people, repositories, and organizations on {% data variables.product.prodname_dotcom %}. See what others are working on and who they''re connecting with from your personal dashboard.'
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -19,26 +19,25 @@ topics:
|
||||
- Notifications
|
||||
- Accounts
|
||||
---
|
||||
To learn about accessing your personal dashboard, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
|
||||
|
||||
個人ダッシュボードへのアクセスについて学ぶには、「[個人ダッシュボードについて](/articles/about-your-personal-dashboard)」を参照してください。
|
||||
## Following people
|
||||
|
||||
## 人をフォローする
|
||||
When you follow someone on {% data variables.product.prodname_dotcom %}, you'll get notifications on your personal dashboard about their activity. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
|
||||
|
||||
{% data variables.product.prodname_dotcom %} 上で人をフォローすれば、その人のアクティビティについてパーソナルダッシュボードで通知を受けられます。 詳しい情報については[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)を参照してください。
|
||||
Click **Follow** on a person's profile page to follow them.
|
||||
|
||||
人をフォローするには、その人のプロフィールページで [**Follow**] をクリックします。
|
||||
|
||||
|
||||
|
||||
## Watching a repository
|
||||
|
||||
## リポジトリを Watch する
|
||||
You can watch a repository to receive notifications for new pull requests and issues. When the owner updates the repository, you'll see the changes in your personal dashboard. For more information see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}."
|
||||
|
||||
リポジトリを Watch して、新しいプルリクエストと Issue に関する通知を受け取ることができます。 オーナーがリポジトリを更新すると、個人ダッシュボード上で変更を見ることができます。 詳しい情報については、{% ifversion fpt or ghae or ghes or ghec %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}「[リポジトリを Watch および Watch 解除する](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}」を参照してください。
|
||||
Click **Watch** at the top of a repository to watch it.
|
||||
|
||||
リポジトリを Watch するには、リポジトリの上部で [**Watch**] をクリックします。
|
||||
|
||||
|
||||
|
||||
|
||||
## 会話に参加する
|
||||
## Joining the conversation
|
||||
|
||||
{% data reusables.support.ask-and-answer-forum %}
|
||||
|
||||
@@ -46,33 +45,34 @@ topics:
|
||||
|
||||
{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
|
||||
|
||||
## さらなる活動
|
||||
## Doing even more
|
||||
|
||||
### プルリクエストを作成する
|
||||
### Creating pull requests
|
||||
|
||||
機能を追加したり、バグを修正したりして、他者のプロジェクトにコントリビュートしたいこともあるでしょう。 変更を行ったら、プルリクエストを送信してオリジナルの作者に知らせましょう。 詳しい情報については[プルリクエストについて](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)を参照してください。
|
||||
You may want to contribute to another person's project, whether to add features or to fix bugs. After making changes, let the original author know by sending a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
|
||||
|
||||
|
||||
|
||||
|
||||
### Issue を使用する
|
||||
### Using issues
|
||||
|
||||
リポジトリでコラボレーションする際に、Issue を使ってアイデア、拡張、タスク、バグを追跡してください。 詳細は「[Issues について](/articles/about-issues/)」を参照してください。
|
||||
When collaborating on a repository, use issues to track ideas, enhancements, tasks, or bugs. For more information, see '[About issues](/articles/about-issues/)."
|
||||
|
||||
|
||||
|
||||
|
||||
### Organization への参加
|
||||
### Participating in organizations
|
||||
|
||||
Organizationは、企業やオープンソースプロジェクトが多くのプロジェクトにわたって一度にコラボレーションできる共有アカウントです。 オーナーや管理者は、特殊な権限を持つ Team を作ることができ、パブリックな Organization のプロフィールを持つことができ、Organization 内でのアクティビティを追跡することができます。 詳細は「[Organization について](/articles/about-organizations/)」を参照してください。
|
||||
Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can establish teams with special permissions, have a public organization profile, and keep track of activity within the organization. For more information, see "[About organizations](/articles/about-organizations/)."
|
||||
|
||||
|
||||
|
||||
|
||||
### {% data variables.product.prodname_dotcom %} 上の他のプロジェクトを調べる
|
||||
### Exploring other projects on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
{% data variables.explore.explore_github %}、[リポジトリを調べる](https://github.com/explore)、そして {% data variables.explore.trending_page %} を使って、興味深いプロジェクトを見つけてください。 興味深いプロジェクトに Star を付け、後から戻っていってください。 {% data variables.explore.your_stars_page %} にアクセスすれば、Star を付けたすべてのプロジェクトを見ることができます。 詳細は「[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard/)」を参照してください。
|
||||
Discover interesting projects using {% data variables.explore.explore_github %}, [Explore repositories](https://github.com/explore), and the {% data variables.explore.trending_page %}. Star interesting projects and come back to them later. Visit your {% data variables.explore.your_stars_page %} to see all your starred projects. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard/)."
|
||||
|
||||
## おめでとうございます
|
||||
## Celebrate
|
||||
|
||||
これで、{% data variables.product.product_name %} コミュニティにつながりました。 次に何をしたいですか? 
|
||||
You're now connected to the {% data variables.product.product_name %} community. What do you want to do next?
|
||||
|
||||
|
||||
|
||||
- To synchronize your {% data variables.product.product_name %} projects with your computer, you can set up Git. For more information see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
@@ -4,7 +4,7 @@ intro: 'You can discuss specific projects and changes, as well as broader ideas
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github
|
||||
- /articles/about-discussions-in-issues-and-pull-requests/
|
||||
- /articles/about-discussions-in-issues-and-pull-requests
|
||||
- /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
|
||||
- /github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github
|
||||
- /github/getting-started-with-github/quickstart/communicating-on-github
|
||||
@@ -19,8 +19,7 @@ topics:
|
||||
- Discussions
|
||||
- Fundamentals
|
||||
---
|
||||
|
||||
## はじめに
|
||||
## Introduction
|
||||
|
||||
{% 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.
|
||||
|
||||
@@ -32,27 +31,27 @@ You can create and participate in issues, pull requests and team discussions, de
|
||||
{% endif %}
|
||||
|
||||
### {% data variables.product.prodname_github_issues %}
|
||||
- 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 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 requests
|
||||
- allow you to propose specific changes.
|
||||
- allow you to comment directly on proposed changes suggested by others.
|
||||
- are specific to a repository.
|
||||
|
||||
- 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.
|
||||
- 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 ディスカッション
|
||||
- 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. アイデアについてディスカッションするためにリポジトリでIssueを開く代わりに、Teamディスカッションで会話することでTeam全体を巻き込めます。
|
||||
- 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 %}
|
||||
### 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 %}
|
||||
@@ -68,11 +67,11 @@ You can create and participate in issues, pull requests and team discussions, de
|
||||
|
||||
#### Issue example
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
- 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.
|
||||
- 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.
|
||||
@@ -86,7 +85,7 @@ This example illustrates how a {% data variables.product.prodname_dotcom %} user
|
||||
|
||||
#### Pull request example
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
In the **Conversation** tab of the pull request, the author explains why they created the pull request.
|
||||
|
||||
@@ -142,16 +141,16 @@ The `octocat` team member posted a team discussion, informing the team of variou
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 次のステップ
|
||||
## Next steps
|
||||
|
||||
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.
|
||||
|
||||
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)."
|
||||
|
||||
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. 詳しい情報については[プルリクエストについて](/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 fpt or ghec %}
|
||||
For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and pin discussions that contain important information for your community. 詳しい情報については「[ディスカッションについて](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」を参照してください。
|
||||
For {% data variables.product.prodname_discussions %}, you can set up a code of conduct and 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 %}
|
||||
|
||||
For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. 詳しい情報については[Team ディスカッションについて](/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)."
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
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/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
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: GitHub のフロー
|
||||
title: GitHub flow
|
||||
intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
|
||||
redirect_from:
|
||||
- /articles/creating-and-editing-files-in-your-repository/
|
||||
- /articles/github-flow-in-the-browser/
|
||||
- /articles/creating-and-editing-files-in-your-repository
|
||||
- /articles/github-flow-in-the-browser
|
||||
- /articles/github-flow
|
||||
- /github/collaborating-with-issues-and-pull-requests/github-flow
|
||||
- /github/getting-started-with-github/github-flow
|
||||
@@ -18,12 +18,11 @@ topics:
|
||||
- Fundamentals
|
||||
miniTocMaxHeadingLevel: 3
|
||||
---
|
||||
|
||||
## はじめに
|
||||
## Introduction
|
||||
|
||||
{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow. The {% data variables.product.prodname_dotcom %} flow is useful for everyone, not just developers. For example, here at {% data variables.product.prodname_dotcom %}, we use {% data variables.product.prodname_dotcom %} flow for our [site policy](https://github.com/github/site-policy), [documentation](https://github.com/github/docs), and [roadmap](https://github.com/github/roadmap).
|
||||
|
||||
## 必要な環境
|
||||
## Prerequisites
|
||||
|
||||
To follow {% data variables.product.prodname_dotcom %} flow, you will need {% data variables.product.prodname_dotcom %} account and a repository. For information on how to create an account, see "[Signing up for {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github)." For information on how to create a repository, see "[Create a repo](/github/getting-started-with-github/create-a-repo)."{% ifversion fpt or ghec %} For information on how to find an existing repository to contribute to, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
|
||||
|
||||
@@ -41,7 +40,7 @@ To follow {% data variables.product.prodname_dotcom %} flow, you will need {% da
|
||||
|
||||
### Create a branch
|
||||
|
||||
Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. 詳しい情報については[リポジトリ内でのブランチの作成と削除](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)を参照してください。
|
||||
Create a branch in your repository. A short, descriptive branch name enables your collaborators to see ongoing work at a glance. For example, `increase-test-timeout` or `add-code-of-conduct`. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
By creating a branch, you create a space to work without affecting the default branch. Additionally, you give collaborators a chance to review your work.
|
||||
|
||||
@@ -65,9 +64,9 @@ Continue to make, commit, and push changes to your branch until you are ready to
|
||||
|
||||
{% endtip %}
|
||||
|
||||
### Pull Requestの作成
|
||||
### Create a pull request
|
||||
|
||||
Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. 詳しい情報については[プルリクエストの作成](/articles/creating-a-pull-request)を参照してください。
|
||||
Create a pull request to ask collaborators for feedback on your changes. Pull request review is so valuable that some repositories require an approving review before pull requests can be merged. If you want early feedback or advice before you complete your changes, you can mark your pull request as a draft. For more information, see "[Creating a pull request](/articles/creating-a-pull-request)."
|
||||
|
||||
When you create a pull request, include a summary of the changes and what problem they solve. You can include images, links, and tables to help convey this information. If your pull request addresses an issue, link the issue so that issue stakeholders are aware of the pull request and vice versa. If you link with a keyword, the issue will close automatically when the pull request merges. For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)" and "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)."
|
||||
|
||||
@@ -79,21 +78,21 @@ In addition to filling out the body of the pull request, you can add comments to
|
||||
|
||||
Your repository may be configured to automatically request a review from specific teams or users when a pull request is created. You can also manually @mention or request a review from specific people or teams.
|
||||
|
||||
If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. 詳しい情報については、「[ステータスチェックについて](/github/collaborating-with-issues-and-pull-requests/about-status-checks)」を参照してください。
|
||||
If your repository has checks configured to run on pull requests, you will see any checks that failed on your pull request. This helps you catch errors before merging your branch. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
|
||||
|
||||
### Address review comments
|
||||
|
||||
Reviewers should leave questions, comments, and suggestions. Reviewers can comment on the whole pull request or add comments to specific lines. You and reviewers can insert images or code suggestions to clarify comments. For more information, see "[Reviewing changes in pull requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests)."
|
||||
|
||||
You can continue to commit and push changes in response to the reviews. プルリクエストは自動的に更新されます。
|
||||
You can continue to commit and push changes in response to the reviews. Your pull request will update automatically.
|
||||
|
||||
### Merge your pull request
|
||||
|
||||
Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. 詳しい情報については[プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)を参照してください。
|
||||
Once your pull request is approved, merge your pull request. This will automatically merge your branch so that your changes appear on the default branch. {% data variables.product.prodname_dotcom %} retains the history of comments and commits in the pull request to help future contributors understand your changes. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)."
|
||||
|
||||
{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. 詳細は「[マージコンフリクトに対処する](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)」を参照してください。
|
||||
{% data variables.product.prodname_dotcom %} will tell you if your pull request has conflicts that must be resolved before merging. For more information, see "[Addressing merge conflicts](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)."
|
||||
|
||||
Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)を参照してください。
|
||||
Branch protection settings may block merging if your pull request does not meet certain requirements. For example, you need a certain number of approving reviews or an approving review from a specific team. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
|
||||
|
||||
### Delete your branch
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Signing up for GitHub
|
||||
intro: 'Start using {% data variables.product.prodname_dotcom %} for yourself or your team.'
|
||||
redirect_from:
|
||||
- /articles/signing-up-for-github
|
||||
- /github/getting-started-with-github/signing-up-for-github/
|
||||
- /github/getting-started-with-github/signing-up-for-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub Enterprise Cloud のトライアルを設定する
|
||||
intro: '{% data variables.product.prodname_ghe_cloud %} のトライアルは無料でできます。'
|
||||
title: Setting up a trial of GitHub Enterprise Cloud
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_cloud %} for free.'
|
||||
redirect_from:
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-cloud
|
||||
- /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
|
||||
@@ -17,49 +17,52 @@ shortTitle: Enterprise Cloud trial
|
||||
{% data reusables.enterprise.ghec-cta-button %}
|
||||
|
||||
|
||||
## {% data variables.product.prodname_ghe_cloud %}について
|
||||
## About {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
{% data reusables.organizations.about-organizations %}
|
||||
|
||||
You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
|
||||
|
||||
{% data reusables.saml.saml-accounts %} 詳細は「<a href="/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on" class="dotcom-only">SAML シングルサインオンを使うアイデンティティおよびアクセス管理について</a>」を参照してください。
|
||||
{% data reusables.saml.saml-accounts %} For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on" class="dotcom-only">About identity and access management with SAML single sign-on</a>."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## {% data variables.product.prodname_ghe_cloud %} のトライアルについて
|
||||
## About trials of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
You can set up a 14-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. 支払方法が必要な {% data variables.product.prodname_marketplace %} アプリを Organization に追加しない限り、トライアル期間中に支払方法を指定する必要はありません。 詳しい情報については、「<a href="/articles/about-billing-for-github-marketplace/" class="dotcom-only">{% data variables.product.prodname_marketplace %}の支払いについて</a>」を参照してください。
|
||||
You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "<a href="/articles/about-billing-for-github-marketplace/" class="dotcom-only">About billing for {% data variables.product.prodname_marketplace %}</a>."
|
||||
|
||||
トライアルには50シートが含まれています。 {% data variables.product.prodname_ghe_cloud %} を評価するためにより多くのシートが必要な場合は、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 トライアルの終了時に、別のシート数を選択できます。
|
||||
Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} のトライアルも利用できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} のトライアルを設定する](/articles/setting-up-a-trial-of-github-enterprise-server)」を参照してください。
|
||||
Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
|
||||
|
||||
## {% data variables.product.prodname_ghe_cloud %} のトライアルを設定する
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. 詳しい情報については、「<a href="/articles/signing-up-for-a-new-github-account" class="dotcom-only">新しい {% data variables.product.prodname_dotcom %} アカウントにサインアップする</a>」を参照してください。
|
||||
Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "<a href="/articles/signing-up-for-a-new-github-account" class="dotcom-only">Signing up for a new {% data variables.product.prodname_dotcom %} account</a>."
|
||||
|
||||
1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
|
||||
1. Click **Start a free trial**. 
|
||||
1. Click **Enterprise Cloud**. 
|
||||
1. Click **Start a free trial**.
|
||||
|
||||
1. Click **Enterprise Cloud**.
|
||||
|
||||
1. Follow the prompts to configure your trial.
|
||||
|
||||
## {% data variables.product.prodname_ghe_cloud %} に触れる
|
||||
## Exploring {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
トライアルを設定したら、[エンタープライズオンボーディングガイド](https://resources.github.com/enterprise-onboarding/)に従って {% data variables.product.prodname_ghe_cloud %} を試してみることができます。
|
||||
After setting up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the [Enterprise Onboarding Guide](https://resources.github.com/enterprise-onboarding/).
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## トライアルを終了する
|
||||
## Finishing your trial
|
||||
|
||||
トライアル期間中はいつでも {% data variables.product.prodname_enterprise %} を購入するか、{% data variables.product.prodname_team %} にダウングレードできます。
|
||||
You can buy {% data variables.product.prodname_enterprise %} or downgrade to {% data variables.product.prodname_team %} at any time during your trial.
|
||||
|
||||
トライアル期間の終了までに {% data variables.product.prodname_enterprise %} または {% data variables.product.prodname_team %} を購入しない場合、Organization は {% data variables.product.prodname_free_team %} にダウングレードされ、これらのプライベートリポジトリから公開された {% data variables.product.prodname_pages %} サイトを含む有料の製品にのみ含まれる高度なツールや機能にアクセスできなくなります。 アップグレードする予定がない場合は、高度な機能へのアクセスを失わないように、トライアル期間の終了前にリポジトリを公開してください。 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。
|
||||
If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_team %} and lose access to any advanced tooling and features that are only included with paid products, including {% data variables.product.prodname_pages %} sites published from those private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, make the repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
|
||||
|
||||
Organization の {% data variables.product.prodname_free_team %} にダウングレードすると、トライアル期間中に設定した SAML 設定も無効になります。 {% data variables.product.prodname_enterprise %} または {% data variables.product.prodname_team %} を購入すると、Organization 内のユーザーが認証できるように SAML 設定が再度有効になります。
|
||||
Downgrading to {% data variables.product.prodname_free_team %} for organizations also disables any SAML settings configured during the trial period. Once you purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %}, your SAML settings will be enabled again for users in your organization to authenticate.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
5. [{% data variables.product.prodname_ghe_cloud %} Free Trial] の下で、[**Buy Enterprise**] または [**Downgrade to Team**] をクリックします。 ![[Buy Enterprise and Downgrade to Team] ボタン](/assets/images/help/organizations/finish-trial-buttons.png)
|
||||
6. プロンプトに従ってお支払い方法を入力し、[**Submit**] をクリックします。
|
||||
5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
|
||||
|
||||
6. Follow the prompts to enter your payment method, then click **Submit**.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: GitHub Enterprise Server のトライアルを設定する
|
||||
intro: '{% data variables.product.prodname_ghe_server %} のトライアルは無料でできます。'
|
||||
title: Setting up a trial of GitHub Enterprise Server
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
|
||||
redirect_from:
|
||||
- /articles/requesting-a-trial-of-github-enterprise/
|
||||
- /articles/requesting-a-trial-of-github-enterprise
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-server
|
||||
- /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server
|
||||
- /github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server
|
||||
@@ -14,54 +14,53 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Server trial
|
||||
---
|
||||
## About trials of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
## {% data variables.product.prodname_ghe_server %} のトライアルについて
|
||||
You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For a list of supported visualization platforms, see "[Setting up a GitHub Enterprise Server instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} を評価するための 45 日間トライアルをリクエストできます。 トライアルは仮想アプライアンスとしてインストールされ、オンプレミスまたはクラウドでのデプロイメントのオプションがあります。 サポートされている仮想化プラットフォームの一覧については「[GitHub Enterprise Server インスタンスをセットアップする](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
|
||||
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}現在、セキュリティ{% endif %}アラートと {% data variables.product.prodname_github_connect %} は {% data variables.product.prodname_ghe_server %} のトライアルでは利用できません。 これらの機能のデモについては、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} のトライアルも利用できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_cloud %} のトライアルを設定する](/articles/setting-up-a-trial-of-github-enterprise-cloud)」を参照してください。
|
||||
Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## {% data variables.product.prodname_ghe_server %} のトライアルを設定する
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} は仮想アプライアンスとしてインストールされます。 組織で仮想マシンをセットアップするのに最適な担当者を決定し、その担当者に[トライアルリクエスト](https://enterprise.github.com/trial)をサブミットするよう依頼してください。 トライアルはリクエストをサブミットした直後に開始できます。
|
||||
{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
|
||||
|
||||
{% data variables.product.prodname_enterprise %} ウェブポータルのアカウントをセットアップするため、トライアルリクエストをサブミットした後に受信したメールにあるリンクをクリックして、プロンプトに従います。 次に、ライセンスファイルをダウンロードします。 For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
|
||||
To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} をインストールするために必要なコンポーネントをダウンロードしてライセンスファイルをアップロードします。 詳細は「[{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)」で、選択した可視化プラットフォームについての手順を参照してください。
|
||||
To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
|
||||
## 次のステップ
|
||||
## Next steps
|
||||
|
||||
トライアルを最大限に活用するためには、次の手順に従ってください:
|
||||
To get the most out of your trial, follow these steps:
|
||||
|
||||
1. [Organization を作成します](/enterprise-server@latest/admin/user-management/creating-organizations)。
|
||||
2. {% data variables.product.prodname_dotcom %} の基本的な使い方を学ぶには、次を参照してください:
|
||||
- [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) ウェブキャスト
|
||||
- {% data variables.product.prodname_dotcom %} ガイドの [Understanding the {% data variables.product.prodname_dotcom %}flow](https://guides.github.com/introduction/flow/)
|
||||
- {% data variables.product.prodname_dotcom %} ガイドの [Hello World](https://guides.github.com/activities/hello-world/)
|
||||
3. 組織のニーズに合わせてインスタンスを設定するには、「[Enterprise を設定する](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)」を参照してください。
|
||||
4. {% data variables.product.prodname_ghe_server %} とご使用のアイデンティティプロバイダとを統合するには、「[SAML を使用する](/enterprise-server@latest/admin/user-management/using-saml)」および「[LDAP を使用する](/enterprise-server@latest/admin/authentication/using-ldap)」を参照してください。
|
||||
5. 個人をトライアルに招待します。人数制限はありません。
|
||||
- ビルトイン認証または設定済みアイデンティティプロバイダを使用して、ユーザを {% data variables.product.prodname_ghe_server %} インスタンスに追加します。 詳細は「[ビルトイン認証を使用する](/enterprise-server@latest/admin/user-management/using-built-in-authentication)」を参照してください。
|
||||
- アカウント管理者になる個人を招待するには、[{% data variables.product.prodname_enterprise %}ウェブポータル](https://enterprise.github.com/login)にアクセスしてください。
|
||||
1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
|
||||
2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
|
||||
- [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast
|
||||
- [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
- [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
|
||||
4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
|
||||
5. Invite an unlimited number of people to join your trial.
|
||||
- Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
|
||||
- To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
|
||||
|
||||
{% note %}
|
||||
|
||||
**注釈:** アカウント管理者になるよう招待したユーザには、招待を承諾するためのリンクが記載されたメールが届きます。
|
||||
**Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## トライアルを終了する
|
||||
## Finishing your trial
|
||||
|
||||
トライアル期間中のいつでも [{% data variables.product.prodname_enterprise %} Web ポータル](https://enterprise.github.com/login)でフルライセンスにアップグレードできます。
|
||||
You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
|
||||
|
||||
トライアル最終日になってもアップグレードしていない場合、トライアルが終了したことを通知するメールが送信されます。 {% data variables.product.prodname_enterprise %} を評価するための時間がさらに必要な場合は、{% data variables.contact.contact_enterprise_sales %} に連絡して延長をリクエストしてください。
|
||||
If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [{% data variables.product.prodname_ghe_cloud %} のトライアルをセットアップする](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)
|
||||
- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: メールアドレスを検証する
|
||||
intro: 'プライマリメールアドレスを検証することでセキュリティが強化され、パスワードを忘れた場合、{% data variables.product.prodname_dotcom %} スタッフによる支援がさらに充実し、{% data variables.product.prodname_dotcom %} のその他の機能にアクセスできるようになります。'
|
||||
title: Verifying your email address
|
||||
intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.'
|
||||
redirect_from:
|
||||
- /articles/troubleshooting-email-verification/
|
||||
- /articles/setting-up-email-verification/
|
||||
- /articles/troubleshooting-email-verification
|
||||
- /articles/setting-up-email-verification
|
||||
- /articles/verifying-your-email-address
|
||||
- /github/getting-started-with-github/verifying-your-email-address
|
||||
- /github/getting-started-with-github/signing-up-for-github/verifying-your-email-address
|
||||
@@ -14,57 +14,58 @@ topics:
|
||||
- Accounts
|
||||
shortTitle: Verify your email address
|
||||
---
|
||||
## About email verification
|
||||
|
||||
## メール検証について
|
||||
You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified.
|
||||
|
||||
新しいアカウントにサインアップした後、または新しいメールアドレスを追加するときに、メールアドレスを検証できます。 メールアドレスが配信不能またはバウンスしている場合、そのメールアドレスは未検証になります。
|
||||
|
||||
メールアドレスを検証しなければ、次のことができません:
|
||||
- リポジトリを作成またはフォークすること
|
||||
- Issue またはプルリクエストを作成すること
|
||||
- Issue、プルリクエスト、あるいはコメントにコメントする
|
||||
- {% data variables.product.prodname_oauth_app %} アプリケーションを承認すること
|
||||
- 個人アクセストークンを生成すること
|
||||
- メール通知を受け取ること
|
||||
- リポジトリに Star を付けること
|
||||
- カードの追加を含めて、プロジェクトボードを作成、更新すること
|
||||
- Gist を作成すること
|
||||
- {% data variables.product.prodname_actions %} を作成または利用すること
|
||||
- {% data variables.product.prodname_sponsors %} で開発者をスポンサーする
|
||||
If you do not verify your email address, you will not be able to:
|
||||
- Create or fork repositories
|
||||
- Create issues or pull requests
|
||||
- Comment on issues, pull requests, or commits
|
||||
- Authorize {% data variables.product.prodname_oauth_app %} applications
|
||||
- Generate personal access tokens
|
||||
- Receive email notifications
|
||||
- Star repositories
|
||||
- Create or update project boards, including adding cards
|
||||
- Create or update gists
|
||||
- Create or use {% data variables.product.prodname_actions %}
|
||||
- Sponsor developers with {% data variables.product.prodname_sponsors %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**:
|
||||
**Warnings**:
|
||||
|
||||
- {% data reusables.user_settings.no-verification-disposable-emails %}
|
||||
- {% data reusables.user_settings.verify-org-approved-email-domain %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## メールアドレスを検証する
|
||||
## Verifying your email address
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.emails %}
|
||||
1. メールアドレスの下にある [**Resend verification email**] をクリックします。 ![[Resend verification email] リンク](/assets/images/help/settings/email-verify-button.png)
|
||||
4. {% data variables.product.prodname_dotcom %} からリンクが記載された電子メールが送信されます。 そのリンクをクリックすると、{% data variables.product.prodname_dotcom %} ダッシュボードに移動して確認バナーが表示されます。 
|
||||
1. Under your email address, click **Resend verification email**.
|
||||
|
||||
4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
|
||||
|
||||
|
||||
## メール検証のトラブルシューティング
|
||||
## Troubleshooting email verification
|
||||
|
||||
### 検証メールを送信できない
|
||||
### Unable to send verification email
|
||||
|
||||
{% data reusables.user_settings.no-verification-disposable-emails %}
|
||||
|
||||
### 検証用リンクをクリックした後のエラーページ
|
||||
### Error page after clicking verification link
|
||||
|
||||
検証用リンクは、24 時間で期限が切れます。 24 時間以内にメールを検証しなかった場合、新たなメール検証用リンクをリクエストできます。 詳細は「[メールアドレスを検証する](/articles/verifying-your-email-address)」を参照してください。
|
||||
The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
|
||||
|
||||
If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.product.product_location %}.
|
||||
|
||||
1. {% data variables.product.signout_link %} of your personal account on {% data variables.product.product_location %}.
|
||||
2. ブラウザを閉じて再起動します。
|
||||
2. Quit and restart your browser.
|
||||
3. {% data variables.product.signin_link %} to your personal account on {% data variables.product.product_location %}.
|
||||
4. 弊社が送ったメール上の検証リンクをクリックします。
|
||||
4. Click on the verification link in the email we sent you.
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- 「[プライマリメールアドレスを変更する](/articles/changing-your-primary-email-address)」
|
||||
- "[Changing your primary email address](/articles/changing-your-primary-email-address)"
|
||||
|
||||
@@ -1,75 +1,74 @@
|
||||
---
|
||||
title: Gitリベースについて
|
||||
title: About Git rebase
|
||||
redirect_from:
|
||||
- /rebase/
|
||||
- /rebase
|
||||
- articles/interactive-rebase/
|
||||
- /articles/about-git-rebase
|
||||
- /github/using-git/about-git-rebase
|
||||
- /github/getting-started-with-github/about-git-rebase
|
||||
- /github/getting-started-with-github/using-git/about-git-rebase
|
||||
intro: '`git rebase` コマンドを使えば、一連のコミットを容易に修正し、リポジトリの履歴を変更できます。 コミットの順序を変更したり、編集したり、まとめて squash できます。'
|
||||
intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
Typically, you would use `git rebase` to:
|
||||
|
||||
通常、`git rebase`は以下の目的で使われます。
|
||||
|
||||
* 以前のコミットメッセージの編集
|
||||
* 複数のコミットを1つにまとめる
|
||||
* 不要になったコミットの削除もしくは打ち消し
|
||||
* Edit previous commit messages
|
||||
* Combine multiple commits into one
|
||||
* Delete or revert commits that are no longer necessary
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**：コミット履歴を変更すると、リポジトリを使う他の人々にとっては難しいことになり得るので、リポジトリにプッシュ済みのコミットをリベースするのは悪いプラクティスと考えられています。 {% data variables.product.product_location %}で安全にリベースする方法を学ぶには[プルリクエストのマージについて](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)を参照してください。
|
||||
**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.product.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## ブランチに対するコミットのリベース
|
||||
## Rebasing commits against a branch
|
||||
|
||||
他のブランチと現在のブランチの状態との間のすべてのコミットをリベースするには、シェル（Windowsのコマンドプロンプト、あるいはMacやLinuxのターミナル）で以下のコマンドを入力してください。
|
||||
To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux):
|
||||
|
||||
```shell
|
||||
$ git rebase --interactive <em>other_branch_name</em>
|
||||
```
|
||||
|
||||
## ある時点に対するコミットのリベース
|
||||
## Rebasing commits against a point in time
|
||||
|
||||
現在のブランチの最後のいくつかのコミットをリベースするには、シェルに以下のコマンドを入力してください。
|
||||
To rebase the last few commits in your current branch, you can enter the following command in your shell:
|
||||
|
||||
```shell
|
||||
$ git rebase --interactive HEAD~7
|
||||
```
|
||||
|
||||
## リベースに利用できるコマンド
|
||||
## Commands available while rebasing
|
||||
|
||||
リベースの際に利用できるコマンドは6つあります。
|
||||
There are six commands available while rebasing:
|
||||
|
||||
<dl>
|
||||
<dt><code>pick</code></dt>
|
||||
<dd><code>pick</code>は単にそのコミットが含まれるということを意味します。 <code>pick</code>コマンドの順序を入れ替えると、リベースが進んでいるときにコミットの順序が変更されます。 コミットを含めないのであれば、行全体を削除してください。 </dd>
|
||||
<dd><code>pick</code> simply means that the commit is included. Rearranging the order of the <code>pick</code> commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line. </dd>
|
||||
|
||||
<dt><code>reword</code></dt>
|
||||
<dd><code>reword</code>コマンドは<code>pick</code>に似ていますが、このコマンドを使った後、リベースの処理は一時的に止まり、コミットメッセージを変更する機会を与えてくれます。 コミットによる変更は影響されません。 </dd>
|
||||
<dd>The <code>reword</code> command is similar to <code>pick</code>, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected. </dd>
|
||||
|
||||
<dt><code>edit</code></dt>
|
||||
<dd>コミットを<code>edit</code>すると、コミットを修正することができます。すなわち、コミットに対して追加をしたり、完全に変更したりすることができます。 また、リベースを続ける前にさらにコミットをすることもできます。 こうすることで大きなコミットを小さなコミット群に分割したり、コミット中の間違った変更を取り除いたりすることができます。 </dd>
|
||||
<dd>If you choose to <code>edit</code> a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit. </dd>
|
||||
|
||||
<dt><code>squash</code></dt>
|
||||
<dd>このコマンドを使うと、2 つ以上のコミットを結合して 1 つのコミットにできます。 コミットはその上にあるコミットに squash されます。 Git は、どちらの変更についても記述する新しいコミットメッセージを書かせてくれます。</dd>
|
||||
<dd>This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.</dd>
|
||||
|
||||
<dt><code>fixup</code></dt>
|
||||
<dd>これは<code>squash</code>に似ていますが、マージされるコミットのメッセージは破棄されます。 コミットはその上位のコミットに単純にマージされ、選考するコミットのメッセージがどちらの変更の記述としても使われます。</dd>
|
||||
<dd>This is similar to <code>squash</code>, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.</dd>
|
||||
|
||||
<dt><code>exec</code></dt>
|
||||
<dd>このコマンドは、コミットに対して任意のシェルコマンドを実行させてくれます。</dd>
|
||||
<dd>This lets you run arbitrary shell commands against a commit.</dd>
|
||||
</dl>
|
||||
|
||||
## `git rebase`の利用例
|
||||
## An example of using `git rebase`
|
||||
|
||||
どのコマンドを使うにしても、Gitは[デフォルトのテキストエディタ](/github/getting-started-with-github/associating-text-editors-with-git)を起動し、選択した範囲のコミットの詳細を記述したファイルをオープンします。 このファイルは以下のようになります。
|
||||
No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this:
|
||||
|
||||
```
|
||||
pick 1fc6c95 Patch A
|
||||
@@ -90,22 +89,23 @@ pick 7b36971 something to move before patch B
|
||||
# f, fixup = like "squash", but discard this commit's log message
|
||||
# x, exec = run command (the rest of the line) using shell
|
||||
#
|
||||
# If you remove a line here THAT COMMIT WILL BE LOST.
|
||||
# However, if you remove everything, the rebase will be aborted.
|
||||
#
|
||||
```
|
||||
|
||||
この情報を上から下へ見ていくと、以下のことが分かります。
|
||||
Breaking this information, from top to bottom, we see that:
|
||||
|
||||
- 7つのコミットがリストされており、出発点から現在のブランチの状態までに7つの変更があったことが示されています。
|
||||
- リベースすることにしたコミットは、古い変更（先頭）から新しい変更（末尾）の順に並べられています。
|
||||
- 各行にはコマンド（デフォルトでは`pick`）、コミットのSHA、そしてコミットメッセージがリストされています。 `git rebase`の全体の手続きは、これらの3つの列の操作を軸として展開されます。 行った変更は、リポジトリに*リベース*されます。
|
||||
- コミット後に、Gitは作業しているコミットの範囲（`41a72e6..7b36971`）を示します。
|
||||
- 最後に、Gitはコミットをリベースする際に利用できるコメントを示すことで多少のヘルプを提供しています。
|
||||
- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state.
|
||||
- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom).
|
||||
- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository.
|
||||
- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`).
|
||||
- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits.
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [Git rebaseの利用](/articles/using-git-rebase)
|
||||
- [_Pro Git_の"Git Branching"の章](https://git-scm.com/book/en/Git-Branching-Rebasing)
|
||||
- [_Pro Git_の"Interactive Rebasing"の章](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
|
||||
- [リベースでのコミットのsquash](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)
|
||||
- {% data variables.product.prodname_desktop %} ドキュメンテーションの「[ブランチを同期する](/desktop/contributing-to-projects/syncing-your-branch)」
|
||||
- "[Using Git rebase](/articles/using-git-rebase)"
|
||||
- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing)
|
||||
- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
|
||||
- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
|
||||
- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation
|
||||
|
||||
@@ -1,45 +1,44 @@
|
||||
---
|
||||
title: Gitのサブツリーのマージについて
|
||||
title: About Git subtree merges
|
||||
redirect_from:
|
||||
- /articles/working-with-subtree-merge/
|
||||
- /subtree-merge/
|
||||
- /articles/working-with-subtree-merge
|
||||
- /subtree-merge
|
||||
- /articles/about-git-subtree-merges
|
||||
- /github/using-git/about-git-subtree-merges
|
||||
- /github/getting-started-with-github/about-git-subtree-merges
|
||||
- /github/getting-started-with-github/using-git/about-git-subtree-merges
|
||||
intro: 複数のプロジェクトを単一のリポジトリで管理する必要がある場合、*サブツリーマージ*を使ってすべての参照を扱うことができます。
|
||||
intro: 'If you need to manage multiple projects within a single repository, you can use a *subtree merge* to handle all the references.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
|
||||
## About subtree merges
|
||||
|
||||
通常、サブツリーのマージはリポジトリ内にリポジトリを格納するために使われます。 「サブリポジトリ」はメインのリポジトリのフォルダー内に格納されます。
|
||||
Typically, a subtree merge is used to contain a repository within a repository. The "subrepository" is stored in a folder of the main repository.
|
||||
|
||||
サブツリーマージは、例で説明するのが最も分かりやすいでしょう。 以下のように進めます:
|
||||
The best way to explain subtree merges is to show by example. We will:
|
||||
|
||||
- プロジェクトを表す`test`という空のリポジトリの作成。
|
||||
- `Spoon-Knife`というもう1つのリポジトリをサブツリーとしてマージ。
|
||||
- `test`プロジェクトは、そのサブプロジェクトを同じリポジトリの一部であるかのように使う。
|
||||
- `Spoon-Knife`からの更新を`test` プロジェクトにフェッチする。
|
||||
- Make an empty repository called `test` that represents our project
|
||||
- Merge another repository into it as a subtree called `Spoon-Knife`.
|
||||
- The `test` project will use that subproject as if it were part of the same repository.
|
||||
- Fetch updates from `Spoon-Knife` into our `test` project.
|
||||
|
||||
## サブツリーマージのための空のリポジトリのセットアップ
|
||||
## Setting up the empty repository for a subtree merge
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 新しいディレクトリを作成し、そこに移動します。
|
||||
2. Create a new directory and navigate to it.
|
||||
```shell
|
||||
$ mkdir test
|
||||
$ cd test
|
||||
```
|
||||
3. 新しい Git リポジトリを初期化します。
|
||||
3. Initialize a new Git repository.
|
||||
```shell
|
||||
$ git init
|
||||
> Initialized empty Git repository in /Users/octocat/tmp/test/.git/
|
||||
```
|
||||
4. 新しいファイルを作成してコミットします。
|
||||
4. Create and commit a new file.
|
||||
```shell
|
||||
$ touch .gitignore
|
||||
$ git add .gitignore
|
||||
@@ -49,9 +48,9 @@ versions:
|
||||
> create mode 100644 .gitignore
|
||||
```
|
||||
|
||||
## 新しいリポジトリをサブツリーとして追加
|
||||
## Adding a new repository as a subtree
|
||||
|
||||
1. 関心のある別個のプロジェクトを指す新しいリモート URL を追加します。
|
||||
1. Add a new remote URL pointing to the separate project that we're interested in.
|
||||
```shell
|
||||
$ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
|
||||
> Updating spoon-knife
|
||||
@@ -64,52 +63,52 @@ versions:
|
||||
> From git://github.com/octocat/Spoon-Knife
|
||||
> * [new branch] main -> Spoon-Knife/main
|
||||
```
|
||||
2. `Spoon-Knife` プロジェクトをローカルの Git プロジェクトにマージします。 こうしてもローカルではファイルはまったく変更されませんが、Git は次のステップに備えることになります。
|
||||
2. Merge the `Spoon-Knife` project into the local Git project. This doesn't change any of your files locally, but it does prepare Git for the next step.
|
||||
|
||||
Git 2.9 以降を使用している場合:
|
||||
If you're using Git 2.9 or above:
|
||||
```shell
|
||||
$ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main
|
||||
> Automatic merge went well; stopped before committing as requested
|
||||
```
|
||||
|
||||
Git 2.8 以前を使用している場合:
|
||||
If you're using Git 2.8 or below:
|
||||
```shell
|
||||
$ git merge -s ours --no-commit spoon-knife/main
|
||||
> Automatic merge went well; stopped before committing as requested
|
||||
```
|
||||
3. **spoon-knife** というディレクトリを新たに作成し、`Spoon-Knife` プロジェクトの Git の履歴をそこへコピーします。
|
||||
3. Create a new directory called **spoon-knife**, and copy the Git history of the `Spoon-Knife` project into it.
|
||||
```shell
|
||||
$ git read-tree --prefix=spoon-knife/ -u spoon-knife/main
|
||||
```
|
||||
4. 変更をコミットして安全にします。
|
||||
4. Commit the changes to keep them safe.
|
||||
```shell
|
||||
$ git commit -m "Subtree merged in spoon-knife"
|
||||
> [main fe0ca25] Subtree merged in spoon-knife
|
||||
```
|
||||
|
||||
ここでは 1 つのサブプロジェクトを追加しただけですが、Git リポジトリには任意の数のサブプロジェクトを取り込むことができます。
|
||||
Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント**: 将来このリポジトリのクローンを新しく作成した場合、追加したリモートは作成されません。 [`git remote add` コマンド](/github/getting-started-with-github/managing-remote-repositories)を使って、再び追加する必要があります。
|
||||
**Tip**: If you create a fresh clone of the repository in the future, the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/github/getting-started-with-github/managing-remote-repositories).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 更新および変更の同期
|
||||
## Synchronizing with updates and changes
|
||||
|
||||
サブプロジェクトが追加された場合、そのサブプロジェクトは上流の変更と自動的には同期されません。 以下のコマンドで、サブプロジェクトを更新する必要があります。
|
||||
When a subproject is added, it is not automatically kept in sync with the upstream changes. You will need to update the subproject with the following command:
|
||||
|
||||
```shell
|
||||
$ git pull -s subtree <em>remotename</em> <em>branchname</em>
|
||||
```
|
||||
|
||||
上の例では、以下のようになるでしょう:
|
||||
For the example above, this would be:
|
||||
|
||||
```shell
|
||||
$ git pull -s subtree spoon-knife main
|
||||
```
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [_Pro Git_ ブックの「高度なマージ」の章](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
|
||||
- [サブツリーマージの戦略の使い方](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)
|
||||
- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
|
||||
- "[How to use the subtree merge strategy](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Getting changes from a remote repository
|
||||
intro: You can use common Git commands to access remote repositories.
|
||||
redirect_from:
|
||||
- /articles/fetching-a-remote/
|
||||
- /articles/fetching-a-remote
|
||||
- /articles/getting-changes-from-a-remote-repository
|
||||
- /github/using-git/getting-changes-from-a-remote-repository
|
||||
- /github/getting-started-with-github/getting-changes-from-a-remote-repository
|
||||
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
title: Git を使用する
|
||||
title: Using Git
|
||||
intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.'
|
||||
redirect_from:
|
||||
- /articles/using-common-git-commands
|
||||
- /github/using-git/using-common-git-commands
|
||||
- /github/using-git/using-advanced-git-commands
|
||||
- /categories/52/articles/
|
||||
- /categories/advanced-git/
|
||||
- /categories/52/articles
|
||||
- /categories/advanced-git
|
||||
- /articles/using-advanced-git-commands
|
||||
- /github/using-git/changing-author-info
|
||||
- /github/getting-started-with-github/using-git/
|
||||
- /github/getting-started-with-github/using-git
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: コミットをリモートリポジトリにプッシュする
|
||||
intro: ローカルブランチで実行されたコミットをリモートリポジトリにプッシュするには、`git push` を使用します。
|
||||
title: Pushing commits to a remote repository
|
||||
intro: Use `git push` to push commits made on your local branch to a remote repository.
|
||||
redirect_from:
|
||||
- /articles/pushing-to-a-remote/
|
||||
- /articles/pushing-to-a-remote
|
||||
- /articles/pushing-commits-to-a-remote-repository
|
||||
- /github/using-git/pushing-commits-to-a-remote-repository
|
||||
- /github/getting-started-with-github/pushing-commits-to-a-remote-repository
|
||||
@@ -14,94 +14,106 @@ versions:
|
||||
ghec: '*'
|
||||
shortTitle: Push commits to a remote
|
||||
---
|
||||
|
||||
## About `git push`
|
||||
`git push` コマンドは、2 つの引数を取ります:
|
||||
The `git push` command takes two arguments:
|
||||
|
||||
* リモート名。たとえば `origin`
|
||||
* ブランチ名。 たとえば `master`
|
||||
* A remote name, for example, `origin`
|
||||
* A branch name, for example, `main`
|
||||
|
||||
例:
|
||||
For example:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME> <BRANCHNAME> </em>
|
||||
```
|
||||
|
||||
たとえば、通常は `git push origin master` を実行してローカルの変更をオンラインリポジトリプッシュします。
|
||||
As an example, you usually run `git push origin main` to push your local changes
|
||||
to your online repository.
|
||||
|
||||
## ブランチの名前を変更する
|
||||
## Renaming branches
|
||||
|
||||
ブランチの名前を変更する場合も、同じ `git push` コマンドを使用しますが、引数が 1 つ増えます。新しいブランチの名前です。 例:
|
||||
To rename a branch, you'd use the same `git push` command, but you would add
|
||||
one more argument: the name of the new branch. For example:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME> <LOCALBRANCHNAME></em>:<em><REMOTEBRANCHNAME> </em>
|
||||
```
|
||||
|
||||
こうすると、`LOCALBRANCHNAME` が `REMOTENAME` にプッシュされますが、名前が `REMOTEBRANCHNAME` に変更されます。
|
||||
This pushes the `LOCALBRANCHNAME` to your `REMOTENAME`, but it is renamed to `REMOTEBRANCHNAME`.
|
||||
|
||||
## "non-fast-forward" エラーに対処する
|
||||
## Dealing with "non-fast-forward" errors
|
||||
|
||||
リポジトリのローカルコピーが同期されていない、つまりプッシュ先である上流リポジトリより古くなっている場合は、`non-fast-forward updates were rejected` というメッセージが表示されます。 これは、ローカルの変更をプッシュする前に上流の変更を取得、つまり「フェッチ」する必要があるという意味です。
|
||||
If your local copy of a repository is out of sync with, or "behind," the upstream
|
||||
repository you're pushing to, you'll get a message saying `non-fast-forward updates were rejected`.
|
||||
This means that you must retrieve, or "fetch," the upstream changes, before
|
||||
you are able to push your local changes.
|
||||
|
||||
このエラーに関する詳細は、「[non-fast-forward エラーに対処する](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)」を参照してください。
|
||||
For more information on this error, see "[Dealing with non-fast-forward errors](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)."
|
||||
|
||||
## タグをプッシュする
|
||||
## Pushing tags
|
||||
|
||||
デフォルトで、追加のパラメータを使用しない場合、`git push` はリモートブランチと名前が一致するすべてのブランチを送信します。
|
||||
By default, and without additional parameters, `git push` sends all matching branches
|
||||
that have the same names as remote branches.
|
||||
|
||||
1 つのタグをプッシュする場合は、ブランチをプッシュするときと同じコマンドを発行できます。
|
||||
To push a single tag, you can issue the same command as pushing a branch:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME> <TAGNAME> </em>
|
||||
```
|
||||
|
||||
すべてのタグをプッシュする場合は、次のコマンドを使用できます:
|
||||
To push all your tags, you can type the command:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME></em> --tags
|
||||
```
|
||||
|
||||
## リモートブランチまたはタグを削除する
|
||||
## Deleting a remote branch or tag
|
||||
|
||||
ブランチを削除する構文は、1 回見ただけでは少し難解です:
|
||||
The syntax to delete a branch is a bit arcane at first glance:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME></em> :<em><BRANCHNAME> </em>
|
||||
```
|
||||
|
||||
コロンの前にスペースがあることに注意してください。 このコマンドは、ブランチの名前を変更するときと似ています。 ただしこちらでは、`REMOTENAME` の `BRANCHNAME` に_何もプッシュしない_よう Git に指示しています。 そのため、`git push` によってリモートリポジトリのブランチが削除されます。
|
||||
Note that there is a space before the colon. The command resembles the same steps
|
||||
you'd take to rename a branch. However, here, you're telling Git to push _nothing_
|
||||
into `BRANCHNAME` on `REMOTENAME`. Because of this, `git push` deletes the branch
|
||||
on the remote repository.
|
||||
|
||||
## リモートとフォーク
|
||||
## Remotes and forks
|
||||
|
||||
GitHub では、[リポジトリを「フォーク」できる](https://guides.github.com/overviews/forking/)ことをご存じでしょう。
|
||||
You might already know that [you can "fork" repositories](https://guides.github.com/overviews/forking/) on GitHub.
|
||||
|
||||
自分が所有しているリポジトリをクローンするとき、リモート URL を指定すると、更新をフェッチおよびプッシュする対象を Git に指示することができます。 元のリポジトリとのコラボレーションが必要な場合は、ローカルの Git クローンに新しいリモート URL を追加するといいでしょう。その名前は通例、`upstream` です。
|
||||
When you clone a repository you own, you provide it with a remote URL that tells
|
||||
Git where to fetch and push updates. If you want to collaborate with the original
|
||||
repository, you'd add a new remote URL, typically called `upstream`, to
|
||||
your local Git clone:
|
||||
|
||||
```shell
|
||||
git remote add upstream <em> <THEIR_REMOTE_URL> </em>
|
||||
```
|
||||
|
||||
これで、更新とブランチを*その*フォークからフェッチできるようになります。
|
||||
Now, you can fetch updates and branches from *their* fork:
|
||||
|
||||
```shell
|
||||
git fetch upstream
|
||||
# 上流のリモートブランチを取得
|
||||
# Grab the upstream remote's branches
|
||||
> remote: Counting objects: 75, done.
|
||||
> remote: Compressing objects: 100% (53/53), done.
|
||||
> remote: Total 62 (delta 27), reused 44 (delta 9)
|
||||
> Unpacking objects: 100% (62/62), done.
|
||||
> From https://{% data variables.command_line.codeblock %}/<em>octocat</em>/<em>repo</em>
|
||||
> * [new branch] master -> upstream/master
|
||||
> * [new branch] main -> upstream/main
|
||||
```
|
||||
|
||||
ローカルの変更が終わったら、ローカルブランチを GitHub にプッシュし、[プルリクエストを開始する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)ことができます。
|
||||
When you're done making local changes, you can push your local branch to GitHub
|
||||
and [initiate a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
フォークの扱いに関する詳細は、「[フォークを同期する](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)」を参照してください。
|
||||
For more information on working with forks, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)".
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
- [「Pro Git」ブックの「リモート」の章](https://git-scm.com/book/ch5-2.html)
|
||||
- [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/ch5-2.html)
|
||||
- [`git remote` main page](https://git-scm.com/docs/git-remote.html)
|
||||
- [Git チートシート](/articles/git-cheatsheet)
|
||||
- [Git のワークフロー](/github/getting-started-with-github/git-workflows)
|
||||
- 「[Git ハンドブック](https://guides.github.com/introduction/git-handbook/)」
|
||||
- "[Git cheatsheet](/articles/git-cheatsheet)"
|
||||
- "[Git workflows](/github/getting-started-with-github/git-workflows)"
|
||||
- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)"
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Splitting a subfolder out into a new repository
|
||||
redirect_from:
|
||||
- /articles/splitting-a-subpath-out-into-a-new-repository/
|
||||
- /articles/splitting-a-subpath-out-into-a-new-repository
|
||||
- /articles/splitting-a-subfolder-out-into-a-new-repository
|
||||
- /github/using-git/splitting-a-subfolder-out-into-a-new-repository
|
||||
- /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: コマンドラインで Git リベースを使う
|
||||
title: Using Git rebase on the command line
|
||||
redirect_from:
|
||||
- /articles/using-git-rebase/
|
||||
- /articles/using-git-rebase
|
||||
- /articles/using-git-rebase-on-the-command-line
|
||||
- /github/using-git/using-git-rebase-on-the-command-line
|
||||
- /github/getting-started-with-github/using-git-rebase-on-the-command-line
|
||||
- /github/getting-started-with-github/using-git/using-git-rebase-on-the-command-line
|
||||
intro: コマンドラインで、「git rebase」を使うための簡単なチュートリアルです。
|
||||
intro: Here's a short tutorial on using `git rebase` on the command line.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -14,12 +14,11 @@ versions:
|
||||
ghec: '*'
|
||||
shortTitle: Git rebase
|
||||
---
|
||||
|
||||
## Using Git rebase
|
||||
|
||||
この例では、`exec` を除く、利用可能なすべての ` git rebase ` コマンドについて説明します。
|
||||
In this example, we will cover all of the `git rebase` commands available, except for `exec`.
|
||||
|
||||
端末で `git rebase --interactive HEAD~7` と入力して、リベースを開始します。 お気に入りのテキストエディタに以下の行が表示されます:
|
||||
We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines:
|
||||
|
||||
```
|
||||
pick 1fc6c95 Patch A
|
||||
@@ -31,17 +30,17 @@ pick 4ca2acc i cant' typ goods
|
||||
pick 7b36971 something to move before patch B
|
||||
```
|
||||
|
||||
この例では、以下を行います:
|
||||
In this example, we're going to:
|
||||
|
||||
* `squash` を使用して、5 番目のコミット (`fa39187`) を `"Patch A"` コミット (`1fc6c95squash`) に Squash します。
|
||||
* 最後のコミット (`7b36971`) を`"Patch B"`コミット (`6b2481b`) の前に移動し、`pick` のままにします。
|
||||
* `"A fix for Patch B"` コミット (`c619268`) を `"Patch B"` コミット (`6b2481b`) にマージし、`fixup` を使用して、コミットメッセージを無視します。
|
||||
* `edit` を使用して、3 番目のコミット (`dd1475d`) を 2 つの小さなコミットに分割します。
|
||||
* `reword` を使用して、スペルミスのコミットメッセージ (`4ca2acc`) を修正します。
|
||||
* Squash the fifth commit (`fa39187`) into the `"Patch A"` commit (`1fc6c95`), using `squash`.
|
||||
* Move the last commit (`7b36971`) up before the `"Patch B"` commit (`6b2481b`), and keep it as `pick`.
|
||||
* Merge the `"A fix for Patch B"` commit (`c619268`) into the `"Patch B"` commit (`6b2481b`), and disregard the commit message using `fixup`.
|
||||
* Split the third commit (`dd1475d`) into two smaller commits, using `edit`.
|
||||
* Fix the commit message of the misspelled commit (`4ca2acc`), using `reword`.
|
||||
|
||||
いかがですか。 やることが多くて大変なように見えますが、落ち着いて、一度に 1 ステップずつ進めましょう。すぐに慣れて素早くできるようになります。
|
||||
Phew! This sounds like a lot of work, but by taking it one step at a time, we can easily make those changes.
|
||||
|
||||
はじめに、ファイル内のコマンドを次のように変更します:
|
||||
To start, we'll need to modify the commands in the file to look like this:
|
||||
|
||||
```
|
||||
pick 1fc6c95 Patch A
|
||||
@@ -53,11 +52,11 @@ edit dd1475d something I want to split
|
||||
reword 4ca2acc i cant' typ goods
|
||||
```
|
||||
|
||||
各行のコマンドを、適宜、`pick` から別のコマンドに置き換えました。
|
||||
We've changed each line's command from `pick` to the command we're interested in.
|
||||
|
||||
それでは、エディタを保存して閉じます。 これにより、対話的なリベースを開始します。
|
||||
Now, save and close the editor; this will start the interactive rebase.
|
||||
|
||||
Git は、最初のリベースコマンド `pick 1fc6c95` では何もすることがないので、スキップします。 次のコマンド `squash fa39187` に進みます。 この操作には入力が必要なので、Git はもう一度テキストエディタを開きます。 開かれるファイルは次のようになります:
|
||||
Git skips the first rebase command, `pick 1fc6c95`, since it doesn't need to do anything. It goes to the next command, `squash fa39187`. Since this operation requires your input, Git opens your text editor once again. The file it opens up looks something like this:
|
||||
|
||||
```
|
||||
# This is a combination of two commits.
|
||||
@@ -79,9 +78,9 @@ something to add to patch A
|
||||
#
|
||||
```
|
||||
|
||||
このファイルは Git の言い方で、「ほら、これが今私がこの `squash` でやろうとしていることです」という意味です。 最初のコミットのメッセージ (`"Patch A"`) と 2 番目のコミットのメッセージ (`"something to add to patch A"`) が一覧表示されます。 これらのコミットメッセージに満足したら、ファイルを保存してエディタを閉じることができます。 それ以外の場合は、テキストを変更するだけでコミットメッセージを変更することができます。
|
||||
This file is Git's way of saying, "Hey, here's what I'm about to do with this `squash`." It lists the first commit's message (`"Patch A"`), and the second commit's message (`"something to add to patch A"`). If you're happy with these commit messages, you can save the file, and close the editor. Otherwise, you have the option of changing the commit message by simply changing the text.
|
||||
|
||||
エディタを閉じると、リベースは続行されます:
|
||||
When the editor is closed, the rebase continues:
|
||||
|
||||
```
|
||||
pick 1fc6c95 Patch A
|
||||
@@ -93,9 +92,9 @@ edit dd1475d something I want to split
|
||||
reword 4ca2acc i cant' typ goods
|
||||
```
|
||||
|
||||
Git は 2 つの `pick` コマンドを処理します (`pick 7b36971` と `pick 6b2481b`) 。 対話を必要としないため、`fixup` コマンド (`fixup c619268`) *も*処理されます。 `fixup` は、`c619268` から `6b2481b` の前のコミットに変更をマージします。 両方の変更とも同じコミットメッセージ `"Patch B"` を持つことになります。
|
||||
Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It *also* processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`.
|
||||
|
||||
Git は `edit dd1475d` 操作を開始して停止し、次のメッセージを端末に表示します:
|
||||
Git gets to the `edit dd1475d` operation, stops, and prints the following message to the terminal:
|
||||
|
||||
```shell
|
||||
You can amend the commit now, with
|
||||
@@ -107,9 +106,9 @@ Once you are satisfied with your changes, run
|
||||
git rebase --continue
|
||||
```
|
||||
|
||||
この時点で、プロジェクト内の任意のファイルを編集して追加の変更を加えることができます。 変更するたびに、新しいコミットを実行する必要があります。そのためには、`git commit --amend` コマンドを入力します。 すべての変更を終えたら、`git rebase --continue` を実行できます。
|
||||
At this point, you can edit any of the files in your project to make any additional changes. For each change you make, you'll need to perform a new commit, and you can do that by entering the `git commit --amend` command. When you're finished making all your changes, you can run `git rebase --continue`.
|
||||
|
||||
そして、Git は `reword 4ca2acc` コマンドを使います。 テキストエディタがもう一度開き、次の情報が表示されます:
|
||||
Git then gets to the `reword 4ca2acc` command. It opens up your text editor one more time, and presents the following information:
|
||||
|
||||
```
|
||||
i cant' typ goods
|
||||
@@ -124,26 +123,26 @@ i cant' typ goods
|
||||
#
|
||||
```
|
||||
|
||||
以前と同様に、Git は編集するためのコミットメッセージを表示しています。 テキスト (`"i cant' typ goods"`) を変更し、ファイルを保存し、エディタを閉じることができます。 Git はリベースを終了して、端末に戻ります。
|
||||
As before, Git is showing the commit message for you to edit. You can change the text (`"i cant' typ goods"`), save the file, and close the editor. Git will finish the rebase and return you to the terminal.
|
||||
|
||||
## リベースされたコードを GitHub にプッシュする
|
||||
## Pushing rebased code to GitHub
|
||||
|
||||
Git の履歴を変更したので、通常の `git push origin` **は動作しません**。 最新の変更を「強制プッシュ」して、コマンドを変更する必要があります:
|
||||
Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes:
|
||||
|
||||
```shell
|
||||
# 変更をオーバーライドしない
|
||||
# Don't override changes
|
||||
$ git push origin main --force-with-lease
|
||||
|
||||
# 変更をオーバーライドする
|
||||
# Override changes
|
||||
$ git push origin main --force
|
||||
```
|
||||
|
||||
{% warning %}
|
||||
|
||||
フォースプッシュは、ブランチに対するコミットの履歴上の順序を変更するので、深刻な影響を及ぼします。 特にあなたのリポジトリが複数の人々によってアクセスされている場合は、注意して使用してください。
|
||||
Force pushing has serious implications because it changes the historical sequence of commits for the branch. Use it with caution, especially if your repository is being accessed by multiple people.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## 参考リンク
|
||||
## Further reading
|
||||
|
||||
* 「[Git リベース後のマージコンフリクトを解決する](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)」
|
||||
* "[Resolving merge conflicts after a Git rebase](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)"
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Using GitHub
|
||||
intro: 'Explore {% data variables.product.company_short %}''s products from different platforms and devices.'
|
||||
redirect_from:
|
||||
- /articles/using-github
|
||||
- /github/getting-started-with-github/using-github/
|
||||
- /github/getting-started-with-github/using-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
title: Keyboard shortcuts
|
||||
intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.'
|
||||
redirect_from:
|
||||
- /articles/using-keyboard-shortcuts/
|
||||
- /categories/75/articles/
|
||||
- /categories/keyboard-shortcuts/
|
||||
- /articles/using-keyboard-shortcuts
|
||||
- /categories/75/articles
|
||||
- /categories/keyboard-shortcuts
|
||||
- /articles/keyboard-shortcuts
|
||||
- /github/getting-started-with-github/keyboard-shortcuts
|
||||
- /github/getting-started-with-github/using-github/keyboard-shortcuts
|
||||
|
||||
@@ -1,23 +1,22 @@
|
||||
---
|
||||
title: サポートされているブラウザ
|
||||
title: Supported browsers
|
||||
redirect_from:
|
||||
- /articles/why-doesn-t-graphs-work-with-ie-8/
|
||||
- /articles/why-don-t-graphs-work-with-ie8/
|
||||
- /articles/why-doesn-t-graphs-work-with-ie-8
|
||||
- /articles/why-don-t-graphs-work-with-ie8
|
||||
- /articles/supported-browsers
|
||||
- /github/getting-started-with-github/supported-browsers
|
||||
- /github/getting-started-with-github/using-github/supported-browsers
|
||||
intro: '{% data variables.product.product_name %} は、最新の Web ブラウザをサポートするよう設計されています。 [Chrome](https://www.google.com/chrome/)、[Firefox](http://www.mozilla.org/firefox/)、[Safari](http://www.apple.com/safari/)、[Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge)の現在のバージョンがサポートされています。'
|
||||
intro: 'We design {% data variables.product.product_name %} to support the latest web browsers. We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
## Firefox Extended Support Release
|
||||
|
||||
## Firefox の延長サポートリリース
|
||||
We do our best to support Firefox's latest [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR). Older versions of Firefox may disable some features on {% data variables.product.product_name %} and require the latest version of Firefox.
|
||||
|
||||
弊社は Firefox の最新の[拡張サポートサービス](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) をサポートするのに最善を尽くしています。 Firefox の古いバージョンは、{% data variables.product.product_name %} のいくつかの機能を作動させなくする可能性がありますので、Firefox の最新バージョンが必要です。
|
||||
## Beta and developer builds
|
||||
|
||||
## ベータ版および開発者版
|
||||
|
||||
サポートしているブラウザのベータ版や開発者版では予期しないバグに出くわす可能性があります。 このようなリリースされていないビルドで、{% data variables.product.product_name %} 上のバグに出くわした場合、同じブラウザの正式バージョンでも存在するかどうか確認してください。 もしバグが非公式バージョンに限って存在する場合、バグをブラウザのデベロッパーに報告することを検討してください。
|
||||
You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.
|
||||
|
||||
@@ -4,7 +4,7 @@ redirect_from:
|
||||
- /articles/
|
||||
- /common-issues-and-questions/
|
||||
- /troubleshooting-common-issues/
|
||||
intro: ソフトウェア開発者、設計者、およびプロジェクトマネージャーのためのドキュメント、ガイド、およびヘルプトピックです。 Git、プルリクエスト、Issues、Wiki、Gist の使用方法、および開発のために GitHub を最大限活用するために必要な全てのポイントをカバーしています。
|
||||
intro: 'Documentation, guides, and help topics for software developers, designers, and project managers. Covers using Git, pull requests, issues, wikis, gists, and everything you need to make the most of GitHub for development.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -20,6 +20,4 @@ children:
|
||||
- /understanding-how-github-uses-and-protects-your-data
|
||||
- /site-policy
|
||||
- /site-policy-deprecated
|
||||
- /setting-up-and-managing-your-enterprise
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ページネーションの詳細
|
||||
intro: Search API を使ったいくつかの例で、ページネーションを使用してレスポンスを扱うために方法を調べましょう。
|
||||
title: Traversing with pagination
|
||||
intro: Explore how to use pagination to manage your responses with some examples using the Search API.
|
||||
redirect_from:
|
||||
- /guides/traversing-with-pagination/
|
||||
- /v3/guides/traversing-with-pagination
|
||||
@@ -11,75 +11,105 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
shortTitle: ページネーション付きのトラバース
|
||||
shortTitle: Traverse with pagination
|
||||
---
|
||||
|
||||
The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume. ほとんどの場合は、要求している情報が_多すぎる_ということに気付くかもしれません。サーバーに負担をかけすぎないため、API は自動的に[リクエストされたアイテムをページネーション][pagination]します。
|
||||
The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
|
||||
Most of the time, you might even find that you're asking for _too much_ information,
|
||||
and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination).
|
||||
|
||||
このガイドでは、 Search APIを呼び出し、ページネーションを使って結果を反復処理します。 このプロジェクトの完全なソースコードは、[platform-samples][platform samples]リポジトリにあります。
|
||||
In this guide, we'll make some calls to the Search API, and iterate over
|
||||
the results using pagination. You can find the complete source code for this project
|
||||
in the [platform-samples][platform samples] repository.
|
||||
|
||||
{% data reusables.rest-api.dotcom-only-guide-note %}
|
||||
|
||||
## ページネーションの基本
|
||||
## Basics of Pagination
|
||||
|
||||
はじめに、ページネーションされたアイテムの受け取りについて、いくつかの事実を知っておくことが重要です。
|
||||
To start with, it's important to know a few facts about receiving paginated items:
|
||||
|
||||
1. 呼び出す API によって、応答するデフォルト値が異なります。 [パブリックリポジトリのリスト化](/rest/reference/repos#list-public-repositories)を呼び出すと、ページネーションされて提供されるのは 1 セットで 30 アイテムですが、GitHub Search APIを呼び出すと 1 セットで 100 アイテムとなります。
|
||||
2. 受け取るアイテムの数は指定できます (最大 100 まで)。
|
||||
3. ただし、技術的な理由により、すべてのエンドポイントが同じ動作をするわけではありません。 たとえば、[イベント](/rest/reference/activity#events)では受け取るアイテム数の最大値を設定できません。 特定のエンドポイントにおけるページネーションされた結果の処理方法については、必ずドキュメントをお読みください。
|
||||
1. Different API calls respond with different defaults. For example, a call to
|
||||
[List public repositories](/rest/reference/repos#list-public-repositories)
|
||||
provides paginated items in sets of 30, whereas a call to the GitHub Search API
|
||||
provides items in sets of 100
|
||||
2. You can specify how many items to receive (up to a maximum of 100); but,
|
||||
3. For technical reasons, not every endpoint behaves the same. For example,
|
||||
[events](/rest/reference/activity#events) won't let you set a maximum for items to receive.
|
||||
Be sure to read the documentation on how to handle paginated results for specific endpoints.
|
||||
|
||||
ページネーションに関する情報は、API呼び出しの[リンクヘッダ](https://datatracker.ietf.org/doc/html/rfc5988)に記載されています。 たとえば、検索APIにcurlでリクエストを行って、Mozilla プロジェクトで `addClass`というフレーズを何回使っているか調べましょう。
|
||||
Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988)
|
||||
of an API call. For example, let's make a curl request to the search API, to find
|
||||
out how many times Mozilla projects use the phrase `addClass`:
|
||||
|
||||
```shell
|
||||
$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla"
|
||||
```
|
||||
|
||||
`-I`パラメータは、実際のコンテンツではなくヘッダのみを扱うことを示します。 結果を調べると、Linkヘッダの中に以下のような情報があることに気付くでしょう。
|
||||
The `-I` parameter indicates that we only care about the headers, not the actual
|
||||
content. In examining the result, you'll notice some information in the Link header
|
||||
that looks like this:
|
||||
|
||||
Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last"
|
||||
|
||||
さて、細かく見ていきましょう。 `rel="next"`には、次のページが`page=2`だと書かれています。 これは納得できる話です。というのも、デフォルトでは、すべてのページネーションされたクエリは`1`ページから始まります。`rel="last"`には追加情報があり、最後のページは`34`ページになると書かれています。 つまり、`addClass`で利用できる情報はあと33ページあるということですね。 よし！
|
||||
Let's break that down. `rel="next"` says that the next page is `page=2`. This makes
|
||||
sense, since by default, all paginated queries start at page `1.` `rel="last"`
|
||||
provides some more information, stating that the last page of results is on page `34`.
|
||||
Thus, we have 33 more pages of information about `addClass` that we can consume.
|
||||
Nice!
|
||||
|
||||
提供されたこのリンク関係に**常に**依存しましょう。 URLを推測したり、自分で構築したりしないでください。
|
||||
**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL.
|
||||
|
||||
### ページ間の移動
|
||||
### Navigating through the pages
|
||||
|
||||
さて、受信するページ数がわかったので、ページを移動して結果の利用を開始できます。 これを行うには、`page`パラメータを渡します。 デフォルトでは、 `page`は常に`1`から始まります。 14ページまでジャンプして、どうなるか見てみましょう。
|
||||
Now that you know how many pages there are to receive, you can start navigating
|
||||
through the pages to consume the results. You do this by passing in a `page`
|
||||
parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14
|
||||
and see what happens:
|
||||
|
||||
```shell
|
||||
$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14"
|
||||
```
|
||||
|
||||
ここでもう一度リンクヘッダを見てみます。
|
||||
Here's the link header once more:
|
||||
|
||||
Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev"
|
||||
|
||||
予想通り`rel="next"`は15で、`rel="last"`は34のままです。 しかし今度は少し情報が増えています。`rel="first"`は、、_最初_のページのURLを示しています。さらに重要なこととして、`rel="prev"`は前のページのページ番号を示しています。 この情報を用いて、APIの呼び出しでリストの最初、前、次、最後にユーザがジャンプできるUIを構築できるでしょう。
|
||||
As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've
|
||||
got some more information: `rel="first"` indicates the URL for the _first_ page,
|
||||
and more importantly, `rel="prev"` lets you know the page number of the previous
|
||||
page. Using this information, you could construct some UI that lets users jump
|
||||
between the first, previous, next, or last list of results in an API call.
|
||||
|
||||
### 受け取るアイテム数の変更
|
||||
### Changing the number of items received
|
||||
|
||||
`per_page`パラメータを渡すことで、各ページが返すアイテム数を最大100まで指定できます。 `addClass`について50アイテムを要求してみましょう。
|
||||
By passing the `per_page` parameter, you can specify how many items you want
|
||||
each page to return, up to 100 items. Let's try asking for 50 items about `addClass`:
|
||||
|
||||
```shell
|
||||
$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50"
|
||||
```
|
||||
|
||||
ヘッダのレスポンスに何が起こるかに注目してください。
|
||||
Notice what it does to the header response:
|
||||
|
||||
Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=20>; rel="last"
|
||||
|
||||
ご想像の通り、`rel="last"`情報には、最後のページが20になったと書かれています。 これは、結果のページごとに、より多くの情報を要求しているからです。
|
||||
As you might have guessed, the `rel="last"` information says that the last page
|
||||
is now 20. This is because we are asking for more information per page about
|
||||
our results.
|
||||
|
||||
## 情報の取得
|
||||
## Consuming the information
|
||||
|
||||
ページネーションを扱うためだけに低レベルのcurlを呼び出したくはないでしょうから、上記で説明したことをすべて行うような、ちょっとしたRubyスクリプトを書いてみましょう。
|
||||
You don't want to be making low-level curl calls just to be able to work with
|
||||
pagination, so let's write a little Ruby script that does everything we've
|
||||
just described above.
|
||||
|
||||
いつものように、まずは[GitHub's Octokit.rb][octokit.rb] Rubyライブラリを読み込んで、[個人アクセストークン][personal token]を渡す必要があります。
|
||||
As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and
|
||||
pass in our [personal access token][personal token]:
|
||||
|
||||
``` ruby
|
||||
require 'octokit'
|
||||
@@ -89,16 +119,26 @@ require 'octokit'
|
||||
client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
|
||||
```
|
||||
|
||||
次に、Octokitの`search_code`メソッドを使用して、検索を実行します。 `curl`を使用する場合と異なり、結果の数をすぐ取得することもできるので、そうしてみましょう。
|
||||
Next, we'll execute the search, using Octokit's `search_code` method. Unlike
|
||||
using `curl`, we can also immediately retrieve the number of results, so let's
|
||||
do that:
|
||||
|
||||
``` ruby
|
||||
results = client.search_code('addClass user:mozilla')
|
||||
total_count = results.total_count
|
||||
```
|
||||
|
||||
さて、リンクヘッダの `page=34>; rel="last"` 情報と同様に、最後のページ番号を取得しましょう。 Octokit.rb は、「[ハイパーメディアリンク関係][hypermedia-relations]」という実装を通じてページネーション情報をサポートしています。 それについて詳しくは扱いませんが、`results`変数の各要素には`rels`というハッシュがあり、そのハッシュには結果に応じて`:next`、`:last`、`:first`、`:prev`といった情報が含まれることだけ触れておけばここでは十分でしょう。 また、生成されるURLについての情報も含まれ、`rels[:last].href`を呼び出すことにより取得できます。
|
||||
Now, let's grab the number of the last page, similar to `page=34>; rel="last"`
|
||||
information in the link header. Octokit.rb support pagination information through
|
||||
an implementation called "[Hypermedia link relations][hypermedia-relations]."
|
||||
We won't go into detail about what that is, but, suffice to say, each element
|
||||
in the `results` variable has a hash called `rels`, which can contain information
|
||||
about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're
|
||||
on. These relations also contain information about the resulting URL, by calling
|
||||
`rels[:last].href`.
|
||||
|
||||
これがわかったら、最後の結果のページ番号を取得し、ユーザにすべての情報を表示しましょう。
|
||||
Knowing this, let's grab the page number of the last result, and present all
|
||||
this information to the user:
|
||||
|
||||
``` ruby
|
||||
last_response = client.last_response
|
||||
@@ -107,7 +147,13 @@ number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
|
||||
puts "There are #{total_count} results, on #{number_of_pages} pages!"
|
||||
```
|
||||
|
||||
最後に、結果を反復処理しましょう。 `for i in 1..number_of_pages.to_i`のループを使うこともできますが、ここでは`rels[:next]`ヘッダに従って、各ページから情報を取得します。 簡単にするため、各ページの最初の結果の、ファイルパスだけを取得します。 これを行うには、ループが必要です。そして各ループの最後で、`rels[:next]`情報に従って、次のページのデータセットを取得します。 取得する`rels[:next]`情報がなくなる (言い換えれば、`rels[:last]`に到着する) と、ループは終了します。 このようになるでしょう。
|
||||
Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`,
|
||||
but instead, let's follow the `rels[:next]` headers to retrieve information from
|
||||
each page. For the sake of simplicity, let's just grab the file path of the first
|
||||
result from each page. To do this, we'll need a loop; and at the end of every loop,
|
||||
we'll retrieve the data set for the next page by following the `rels[:next]` information.
|
||||
The loop will finish when there is no `rels[:next]` information to consume (in other
|
||||
words, we are at `rels[:last]`). It might look something like this:
|
||||
|
||||
``` ruby
|
||||
puts last_response.data.items.first.path
|
||||
@@ -117,7 +163,9 @@ until last_response.rels[:next].nil?
|
||||
end
|
||||
```
|
||||
|
||||
Octokit.rb では、ページあたりのアイテム数を変更することは非常に簡単です。 `per_page` オプションのハッシュを初期クライアント構築に渡すだけです。 その後、コードはそのままになっているはずです。
|
||||
Changing the number of items per page is extremely simple with Octokit.rb. Simply
|
||||
pass a `per_page` options hash to the initial client construction. After that,
|
||||
your code should remain intact:
|
||||
|
||||
``` ruby
|
||||
require 'octokit'
|
||||
@@ -144,15 +192,17 @@ until last_response.rels[:next].nil?
|
||||
end
|
||||
```
|
||||
|
||||
## ページネーションリンクの作成
|
||||
## Constructing Pagination Links
|
||||
|
||||
通常、ページネーションの目的は可能なすべての結果を連結することではなく、以下のようなナビゲーションを生成することです。
|
||||
Normally, with pagination, your goal isn't to concatenate all of the possible
|
||||
results, but rather, to produce a set of navigation, like this:
|
||||
|
||||
|
||||
|
||||
|
||||
ここで起こりそうなことを小さなモデルを使って描いてみましょう。
|
||||
Let's sketch out a micro-version of what that might entail.
|
||||
|
||||
以下の最初の呼び出しでページネーションされた結果の`number_of_pages`を所得できることは、上記のコードからすでに知っています。
|
||||
From the code above, we already know we can get the `number_of_pages` in the
|
||||
paginated results from the first call:
|
||||
|
||||
``` ruby
|
||||
require 'octokit'
|
||||
@@ -171,7 +221,7 @@ puts last_response.rels[:last].href
|
||||
puts "There are #{total_count} results, on #{number_of_pages} pages!"
|
||||
```
|
||||
|
||||
ここから、数値ボックスを美しい ASCII 文字で構築できます。
|
||||
From there, we can construct a beautiful ASCII representation of the number boxes:
|
||||
``` ruby
|
||||
numbers = ""
|
||||
for i in 1..number_of_pages.to_i
|
||||
@@ -180,7 +230,8 @@ end
|
||||
puts numbers
|
||||
```
|
||||
|
||||
ランダムな番号を生成して、このボックスのいずれかをクリックするユーザをシミュレートしてみます。
|
||||
Let's simulate a user clicking on one of these boxes, by constructing a random
|
||||
number:
|
||||
|
||||
``` ruby
|
||||
random_page = Random.new
|
||||
@@ -189,13 +240,15 @@ random_page = random_page.rand(1..number_of_pages.to_i)
|
||||
puts "A User appeared, and clicked number #{random_page}!"
|
||||
```
|
||||
|
||||
さて、ページ番号があるので、 `:page`オプションを渡すことにより、Octokitで各ページを明示的に取得できます。
|
||||
Now that we have a page number, we can use Octokit to explicitly retrieve that
|
||||
individual page, by passing the `:page` option:
|
||||
|
||||
``` ruby
|
||||
clicked_results = client.search_code('addClass user:mozilla', :page => random_page)
|
||||
```
|
||||
|
||||
もっと見栄えをよくしたければ、前のページと次のページも取得して、戻る (`<<`) と進む (`>>`) のリンクも生成できます。
|
||||
If we wanted to get fancy, we could also grab the previous and next pages, in
|
||||
order to generate links for back (`<<`) and forward (`>>`) elements:
|
||||
|
||||
``` ruby
|
||||
prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)"
|
||||
@@ -210,3 +263,4 @@ puts "The next page link is #{next_page_href}"
|
||||
[octokit.rb]: https://github.com/octokit/octokit.rb
|
||||
[personal token]: /articles/creating-an-access-token-for-command-line-use
|
||||
[hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination
|
||||
[listing commits]: /rest/reference/repos#list-commits
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
date: '2021-12-07'
|
||||
intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
|
||||
intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."<br><br>**Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command.
|
||||
sections:
|
||||
features:
|
||||
-
|
||||
@@ -159,6 +159,7 @@ sections:
|
||||
#bugs:
|
||||
#- PLACEHOLDER
|
||||
known_issues:
|
||||
- After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。
|
||||
- Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
|
||||
|
||||
@@ -1,22 +1,41 @@
|
||||
file,reason
|
||||
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md,rendering error
|
||||
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,rendering error
|
||||
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,Listed in localization-support#489
|
||||
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/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/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-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
|
||||
translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md,rendering error
|
||||
translations/ja-JP/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,rendering error
|
||||
translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
|
||||
@@ -242,18 +261,28 @@ translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-ent
|
||||
translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,rendering error
|
||||
translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/index.md,rendering error
|
||||
translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
|
||||
translations/ja-JP/content/authentication/index.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/index.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
|
||||
translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
|
||||
translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
|
||||
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error
|
||||
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
|
||||
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
|
||||
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
|
||||
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
|
||||
translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
|
||||
translations/ja-JP/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,Listed in localization-support#489
|
||||
translations/ja-JP/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md,rendering error
|
||||
@@ -396,28 +425,54 @@ translations/ja-JP/content/education/manage-coursework-with-github-classroom/tea
|
||||
translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,rendering error
|
||||
translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md,rendering error
|
||||
translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,rendering error
|
||||
translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
|
||||
translations/ja-JP/content/get-started/exploring-projects-on-github/index.md,rendering error
|
||||
translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/git-workflows.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/ignoring-files.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/index.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
|
||||
translations/ja-JP/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
|
||||
translations/ja-JP/content/get-started/index.md,rendering error
|
||||
translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,Listed in localization-support#489
|
||||
translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,parsing error
|
||||
translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error
|
||||
translations/ja-JP/content/get-started/learning-about-github/index.md,rendering error
|
||||
translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
|
||||
translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/be-social.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/communicating-on-github.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/create-a-repo.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/fork-a-repo.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/github-flow.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/index.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/set-up-git.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/index.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/about-git-rebase.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/about-git-subtree-merges.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/about-git.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/getting-changes-from-a-remote-repository.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/index.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-git/using-git-rebase-on-the-command-line.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-github/github-mobile.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-github/index.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md,rendering error
|
||||
translations/ja-JP/content/get-started/using-github/supported-browsers.md,rendering error
|
||||
translations/ja-JP/content/github-cli/github-cli/creating-github-cli-extensions.md,rendering error
|
||||
translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,rendering error
|
||||
translations/ja-JP/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,rendering error
|
||||
translations/ja-JP/content/github/index.md,rendering error
|
||||
translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md,rendering error
|
||||
translations/ja-JP/content/github/site-policy/github-terms-of-service.md,rendering error
|
||||
translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md,rendering error
|
||||
@@ -516,6 +571,7 @@ translations/ja-JP/content/repositories/working-with-files/managing-large-files/
|
||||
translations/ja-JP/content/repositories/working-with-files/using-files/navigating-code-on-github.md,rendering error
|
||||
translations/ja-JP/content/rest/guides/discovering-resources-for-a-user.md,rendering error
|
||||
translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md,rendering error
|
||||
translations/ja-JP/content/rest/guides/traversing-with-pagination.md,rendering error
|
||||
translations/ja-JP/content/rest/index.md,rendering error
|
||||
translations/ja-JP/content/rest/overview/api-previews.md,rendering error
|
||||
translations/ja-JP/content/rest/reference/actions.md,rendering error
|
||||
|
||||
|
Reference in New Issue
Block a user