New translation batch for ja (#28376)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja * run script/i18n/reset-known-broken-translation-files.js * Check in ja CSV report
This commit is contained in:
docubot
@@ -17,7 +17,7 @@ featuredLinks:
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
|
||||
- /account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications
|
||||
guideCards:
|
||||
- /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
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
|
||||
- '{% ifversion ghes or ghae %}/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories{% endif %}'
|
||||
|
||||
@@ -33,7 +33,7 @@ topics:
|
||||
- あなたが所有している、もしくはコントリビューションしたリポジトリと Gist。 {% ifversion fpt or ghes or ghec %}You can showcase your best work by pinning repositories and gists to your profile. 詳細は「[プロフィールにアイテムをピン止めする](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)」を参照してください。{% endif %}
|
||||
- Repositories you've starred{% ifversion fpt or ghec %} and organized into lists.{% endif %} For more information, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)."
|
||||
- あなたが最もアクティブな Organization、リポジトリ、Team でのあなたのアクティビティの概要。 詳しい情報については、「[プロフィール上にアクティビティの概要を表示する](/articles/showing-an-overview-of-your-activity-on-your-profile)」を参照してください。{% ifversion fpt or ghec %}
|
||||
- {% data variables.product.prodname_pro %} の使用や、{% data variables.product.prodname_arctic_vault %}、{% data variables.product.prodname_sponsors %}、{% data variables.product.company_short %} 開発者プログラムなどのプログラムへの参加を示すバッジ。 詳細は「[プロフィールをパーソナライズする](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)」を参照してください。{% endif %}
|
||||
- Badges and Achievements that highlight your activity and show if you use {% data variables.product.prodname_pro %} or participate in programs like the {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, or the {% data variables.product.company_short %} Developer Program. 詳細は「[プロフィールをパーソナライズする](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)」を参照してください。{% endif %}
|
||||
|
||||
プロフィールにステータスを設定して、可用性に関する情報を提供することもできます。 詳細は「[ステータスを設定する](/articles/personalizing-your-profile/#setting-a-status)」を参照してください。
|
||||
|
||||
|
||||
@@ -119,31 +119,36 @@ shortTitle: Personalize
|
||||
|
||||
特定のプログラムに参加すると、{% data variables.product.prodname_dotcom %} でプロフィールに自動的にバッジが表示されます。
|
||||
|
||||
| バッジ | プログラム | 説明 |
|
||||
| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|  | **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). |
|
||||
| {% octicon "shield" aria-label="The shield icon" %} | **Security advisory credit** | If a security advisory you submit to the [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) is accepted, you'll get a Security advisory credit badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Security Advisories, see [{% data variables.product.prodname_dotcom %} Security Advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). |
|
||||
| {% octicon "check" aria-label="The check icon" %} | **Discussion answered** | If your reply to a discussion is marked as the answer, you'll get a Discussion answered badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Discussions, see [About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions). |
|
||||
|
||||
## プロフィールでバッジを無効にする
|
||||
|
||||
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] で、無効にするバッジの選択を解除します。 
|
||||
{% data reusables.user-settings.update-preferences %}
|
||||
| バッジ | プログラム | 説明 |
|
||||
| --------------------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| {% 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). |
|
||||
| {% octicon "shield" aria-label="The shield icon" %} | **Security advisory credit** | If a security advisory you submit to the [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) is accepted, you'll get a Security advisory credit badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Security Advisories, see [{% data variables.product.prodname_dotcom %} Security Advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). |
|
||||
| {% octicon "check" aria-label="The check icon" %} | **Discussion answered** | If your reply to a discussion is marked as the answer, you'll get a Discussion answered badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Discussions, see [About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions). |
|
||||
|
||||
{% endif %}
|
||||
|
||||
## List of qualifying repositories for Mars 2020 Helicopter Contributor badge
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
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.
|
||||
## Earning Achievements
|
||||
|
||||
Achievements celebrate specific events and actions that happen on {% data variables.product.prodname_dotcom %}. They will appear as small badges listed in the sidebar of your profile. Clicking or hovering on an achievement will show a detailed view that hints at how the achievement was earned, with a short description and links to the contributing events. The event links will only be visible to users that have access to the repository or organization that the event took place in. Event links will appear inaccessible to all users without access.
|
||||
|
||||
To stop private contributions from counting toward your Achievements, or to turn off Achievements entirely, see "[Showing your private contributions and Achievements on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** This feature is currently in beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## List of qualifying repositories for Mars 2020 Helicopter Contributor achievement
|
||||
|
||||
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 achievement 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 |
|
||||
| ----------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
|
||||
|
||||
@@ -14,6 +14,6 @@ topics:
|
||||
- Profiles
|
||||
children:
|
||||
- /customizing-your-profile
|
||||
- /managing-contribution-graphs-on-your-profile
|
||||
- /managing-contribution-settings-on-your-profile
|
||||
---
|
||||
|
||||
|
||||
@@ -1,9 +1,10 @@
|
||||
---
|
||||
title: プロフィールでコントリビューショングラフを管理する
|
||||
title: Managing contribution settings on your profile
|
||||
intro: コミット、プルリクエストの提案、Issue のオープンなどのコントリビューションはあなたのプロフィールに表示されるので、あなたが行った作業をユーザは簡単に確認できます。
|
||||
redirect_from:
|
||||
- /articles/managing-contribution-graphs-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -14,10 +15,10 @@ topics:
|
||||
children:
|
||||
- /viewing-contributions-on-your-profile
|
||||
- /showing-an-overview-of-your-activity-on-your-profile
|
||||
- /publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /showing-your-private-contributions-and-achievements-on-your-profile
|
||||
- /sending-enterprise-contributions-to-your-githubcom-profile
|
||||
- /why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /troubleshooting-commits-on-your-timeline
|
||||
shortTitle: Manage contribution graph
|
||||
shortTitle: Manage contribution settings
|
||||
---
|
||||
|
||||
@@ -7,6 +7,7 @@ redirect_from:
|
||||
- /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
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -1,10 +1,11 @@
|
||||
---
|
||||
title: プライベートコントリビューションをプロフィールで公開または非公開にする
|
||||
title: Showing your private contributions and achievements on your profile
|
||||
intro: 'Your {% data variables.product.product_name %} profile shows a graph of your repository contributions over the past year. You can choose to show anonymized activity from {% ifversion fpt or ghes or ghec %}private and internal{% else %}private{% endif %} repositories{% ifversion fpt or ghes or ghec %} in addition to the activity from public repositories{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -12,7 +13,7 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: Private contributions
|
||||
shortTitle: Private contributions and achievements
|
||||
---
|
||||
|
||||
プライベートコントリビューションを公開しても、あなたが作業しているプライベートリポジトリへのアクセス権がないユーザーがあなたのプライベートコントリビューションを見ることはできません。 かわりに、特定の日におけるプライベートコントリビューションの数だけを見ることができます。 パブリックコントリビューションには、詳細な情報が含まれます。 For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)."
|
||||
@@ -30,6 +31,13 @@ shortTitle: Private contributions
|
||||
- プライベートコントリビューションを公開するには、コントリビューショングラフの上で、[**Contribution settings**] ドロップダウンメニューから [**Private contributions**] を選択します。 訪問者には、プライベートコントリビューションの数だけが表示され、それ以上の詳細は表示されません。 ![[Contribution settings] メニューで、訪問者がプライベートコントリビューションを見られるようにする](/assets/images/help/profile/private-contributions-on.png)
|
||||
- プライベートコントリビューションを非公開にするには、コントリビューショングラフの上で、[**Contribution settings**] ドロップダウンメニューを使用し、[**Private contributions**] の選択を解除します。訪問者には、パブリックコントリビューションのみが表示されるようになります。 ![[Contribution settings] メニューで、訪問者がプライベートコントリビューションを見られるようにする](/assets/images/help/profile/private-contributions-off.png)
|
||||
|
||||
## Changing the visibility of Achievements
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
1. Show or hide Achievements on your profile:
|
||||
- To show Achievements on your profile, navigate to **Profile settings**, and select the checkbox next to **Show Achievements on my profile.** 
|
||||
- To hide Achievements from your profile, navigate to **Profile settings**, and unselect the checkbox next to **Show Achievements on my profile.** 
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- [プロフィールページ上にコントリビューションを表示する](/articles/viewing-contributions-on-your-profile-page)
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/troubleshooting-commits-on-your-timeline
|
||||
- /github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
|
||||
- /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
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.'
|
||||
intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories, Achievements, and{% endif %} a graph of your repository contributions over the past year.'
|
||||
redirect_from:
|
||||
- /articles/viewing-contributions
|
||||
- /articles/viewing-contributions-on-your-profile-page
|
||||
@@ -16,7 +16,7 @@ topics:
|
||||
- Profiles
|
||||
shortTitle: View contributions
|
||||
---
|
||||
{% ifversion fpt or ghes or ghec %}Your contribution graph shows activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
|
||||
{% ifversion fpt or ghes or ghec %}Your contribution graph and Achievements show activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/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
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -80,7 +81,7 @@ If the email address used for the commit is not connected to your account on {%
|
||||
|
||||
コミットがデフォルト以外または `gh-pages` 以外のブランチにあり、コントリビューションにカウントする場合は、以下のうち 1 つを行う必要があります:
|
||||
- 変更をデフォルトのブランチまたは `gh-pages` ブランチにマージするには、[プルリクエストを開きます](/articles/creating-a-pull-request)。
|
||||
- リポジトリの[デフォルトブランチを変更します](/github/administering-a-repository/changing-the-default-branch)。
|
||||
- [Change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository.
|
||||
|
||||
{% warning %}
|
||||
|
||||
@@ -92,7 +93,7 @@ If the email address used for the commit is not connected to your account on {%
|
||||
|
||||
フォークで行われたコミットは、 コントリビューションにはカウントされません。 カウントには、次のいずれかを実行する必要があります:
|
||||
- 変更内容を親リポジトリにマージするために、[プルリクエストを開きます](/articles/creating-a-pull-request)。
|
||||
- フォークをデタッチして、{% data variables.product.product_location %} 上のスタンドアロンリポジトリに変換するために、{% data variables.contact.contact_support %} に連絡してください。 フォークに独自のフォークがある場合は、フォークがリポジトリと一緒に新しいネットワークに移動するのか、現在のネットワークに残るのかを {% data variables.contact.contact_support %}に連絡してください。 詳細は「[フォークについて](/articles/about-forks/)」を参照してください。
|
||||
- To detach the fork and turn it into a standalone repository on {% data variables.product.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, let {% data variables.contact.contact_support %} know if the forks should move with your repository into a new network or remain in the current network. 詳細は「[フォークについて](/articles/about-forks/)」を参照してください。
|
||||
|
||||
## 参考リンク
|
||||
|
||||
@@ -137,6 +137,14 @@ gh run rerun --job <em>job-id</em> --debug
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion partial-reruns-with-reusable %}
|
||||
|
||||
## Re-running workflows and jobs with reusable workflows
|
||||
|
||||
{% data reusables.actions.partial-reruns-with-reusable %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.4 or ghae-issue-4721 or ghec %}
|
||||
## Reviewing previous workflow runs
|
||||
|
||||
|
||||
@@ -310,6 +310,14 @@ For information about using the REST API to query the audit log for an organizat
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion partial-reruns-with-reusable %}
|
||||
|
||||
## Re-running workflows and jobs with reusable workflows
|
||||
|
||||
{% data reusables.actions.partial-reruns-with-reusable %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 次のステップ
|
||||
|
||||
To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)."
|
||||
|
||||
@@ -1,9 +1,36 @@
|
||||
---
|
||||
title: GitHub Desktopのドキュメント
|
||||
title: GitHub Desktop
|
||||
shortTitle: GitHub Desktop
|
||||
intro: プロジェクトの作業を管理するための、GitHub Desktop設定と使用方法のステップバイステップガイド。
|
||||
intro: 'With GitHub Desktop, you can interact with GitHub using a GUI instead of the command line or a web browser. You can use GitHub Desktop to complete most Git commands from your desktop, such as pushing to, pulling from, and cloning remote repositories, attributing commits, and creating pull requests, with visual confirmation of changes.'
|
||||
introLinks:
|
||||
overview: /desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop
|
||||
- /desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop
|
||||
- /desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github
|
||||
guideCards:
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit
|
||||
popular:
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/managing-commits
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request
|
||||
- /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github
|
||||
changelog:
|
||||
label: desktop
|
||||
versions:
|
||||
fpt: '*'
|
||||
layout: product-landing
|
||||
versions:
|
||||
fpt: '*'
|
||||
topics:
|
||||
- Desktop
|
||||
- Repositories
|
||||
children:
|
||||
- /installing-and-configuring-github-desktop
|
||||
- /contributing-and-collaborating-using-github-desktop
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: About GitHub Community Exchange
|
||||
intro: 'As a student, learn the skills you need to contribute to open source projects and grow your own portfolio, with {% data variables.product.prodname_community_exchange %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Community Exchange
|
||||
---
|
||||
|
||||
## {% data variables.product.prodname_community_exchange %}について
|
||||
|
||||
{% data variables.product.prodname_community_exchange %} is a student community within the {% data variables.product.prodname_global_campus %} portal. As a student, it's a place where you can get exposure for your project and discover other student repositories in need of collaborators and maintainers.
|
||||
|
||||
|
||||
|
||||
You can help your peers learn open source skills, become a project maintainer, and grow your {% data variables.product.prodname_dotcom %} portfolio and network within a safe and verified community platform.
|
||||
|
||||
{% data variables.product.prodname_community_exchange %} allows you to:
|
||||
- Discover student created repositories
|
||||
- Star repositories of interest
|
||||
- Submit a repository in need of collaborators
|
||||
- Submit a repository to teach new skills
|
||||
- Manage your repository submissions
|
||||
|
||||
To access {% data variables.product.prodname_community_exchange %}, visit your {% data variables.product.prodname_global_campus %} dashboard at https://education.github.com.
|
||||
|
||||
If you're a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_community_exchange %} within {% data variables.product.prodname_global_campus %}.
|
||||
|
||||
- If you’re a student and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [student application form](https://education.github.com/discount_requests/student_application). For more information, see "[About GitHub Education for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students)."
|
||||
|
||||
- If you’re an educator and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [teacher application form](https://education.github.com/discount_requests/teacher_application). For more information, see "[About GitHub Education for educators](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount)."
|
||||
@@ -22,3 +22,4 @@ shortTitle: For students
|
||||
## 参考リンク
|
||||
|
||||
- [教育者および研究者のための {% data variables.product.prodname_education %} について](/articles/about-github-education-for-educators-and-researchers)
|
||||
- 「[{% data variables.product.prodname_community_exchange %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)」
|
||||
|
||||
@@ -11,6 +11,7 @@ children:
|
||||
- /about-github-education-for-students
|
||||
- /apply-for-a-student-developer-pack
|
||||
- /why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /about-github-community-exchange
|
||||
shortTitle: For your schoolwork
|
||||
---
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ The {% data variables.product.prodname_codespaces %} Education benefit gives ver
|
||||
|
||||
To become a verified teacher, you need to be approved for an educator or teacher benefit. For more information, see "[Applying for an educator or teacher benefit](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount#applying-for-an-educator-or-researcher-discount)."
|
||||
|
||||
After you have confirmation that you are a verified teacher, visit [Global Campus for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team).
|
||||
After you have confirmation that you are a verified teacher, visit [{% data variables.product.prodname_global_campus %} for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team).
|
||||
|
||||
If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, when you enable {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_classroom %} for your organization, GitHub automatically adds a Codespace policy to restrict machine types for all codespaces in the organization to 2 core machines. This helps you make the most of the free {% data variables.product.prodname_codespaces %} usage. However, you can change or remove these policies in your organization settings. 詳しい情報については「[マシンタイプへのアクセス制限](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)」を参照してください。
|
||||
|
||||
|
||||
@@ -29,9 +29,12 @@ HTTP/2 200
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xml:lang="en-US">
|
||||
<feed xmlns="http://www.w3.org/2005/Atom"
|
||||
xmlns:media="http://search.yahoo.com/mrss/"
|
||||
xml:lang="en-US">
|
||||
<id>tag:github.com,2008:/security-advisories</id>
|
||||
<link rel="self" type="application/atom+xml" href="https://github.com/security-advisories.atom"/>
|
||||
<link rel="self" type="application/atom+xml"
|
||||
href="https://github.com/security-advisories.atom"/>
|
||||
<title>GitHub Security Advisory Feed</title>
|
||||
<author>
|
||||
<name>GitHub</name>
|
||||
@@ -41,10 +44,18 @@ HTTP/2 200
|
||||
<id>tag:github.com,2008:GHSA-abcd-12ab-23cd</id>
|
||||
<published>2018-07-26T15:14:52Z</published>
|
||||
<updated>2019-01-14T19:34:52Z</updated>
|
||||
<title type="html">[GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp</title>
|
||||
<title type="html">[GHSA-abcd-12ab-23cd] Moderate
|
||||
severity vulnerability that affects Octoapp</title>
|
||||
<category term="NPM"/>
|
||||
<content type="html">
|
||||
<p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p>
|
||||
<p>Octoapp node module before 4.17.5 suffers
|
||||
from a Modification of Assumed-Immutable Data (MAID)
|
||||
vulnerability via defaultsDeep, merge, and mergeWith
|
||||
functions, which allows a malicious user to modify
|
||||
the prototype of "Object" via
|
||||
<strong>proto</strong>, causing the
|
||||
addition or modification of an existing property
|
||||
that will exist on all objects.</p>
|
||||
<p><strong>Affected Packages</strong></p>
|
||||
|
||||
<dl>
|
||||
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
#Issue #7062
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-7062'
|
||||
@@ -9,6 +9,7 @@ sections:
|
||||
- SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog.
|
||||
- For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.
|
||||
- When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.
|
||||
- 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
|
||||
changes:
|
||||
- In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.
|
||||
- When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported.
|
||||
|
||||
@@ -12,6 +12,7 @@ sections:
|
||||
- Issueコメントにアップロードされたビデオが適切にレンダリングされません。
|
||||
- SAML暗号化されたアサーションを利用する場合、一部のアサーションは正しくSSHキーを検証済みとしてマークしませんでした。
|
||||
- '`ghe-migrator`を使う場合、移行はIssueやPull Request内のビデオの添付ファイルのインポートに失敗します。'
|
||||
- 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
|
||||
changes:
|
||||
- 高可用性構成では、Management Consoleのレプリケーションの概要ページが現在のレプリケーションのステータスではなく、現在のレプリケーション設定だけを表示することを明確にしてください。
|
||||
- '{% data variables.product.prodname_registry %}を有効化する場合、接続文字列としてのShared Access Signature (SAS)トークンの利用は現在サポートされていないことを明確にしてください。'
|
||||
|
||||
@@ -15,6 +15,7 @@ sections:
|
||||
- リポジトリページでファイルファインダーを使おうとしたとき、検索フィールド内でバックスペースキーを入力すると、検索結果が複数回リストされ、レンダリングの問題が生じます。
|
||||
- GitHub Enterprise Importerを使ってリポジトリをインポートしようとすると、プロジェクトのタイムラインイベントが正しく設定されていないことから、一部のIssueのインポートに失敗します。
|
||||
- '`ghe-migrator`を使う場合、移行はIssueやPull Request内のビデオの添付ファイルのインポートに失敗します。'
|
||||
- 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
|
||||
changes:
|
||||
- 高可用性構成では、Management Consoleのレプリケーションの概要ページが現在のレプリケーションのステータスではなく、現在のレプリケーション設定だけを表示することを明確にしてください。
|
||||
- '{% data variables.product.prodname_registry %}を有効化する場合、接続文字列としてのShared Access Signature (SAS)トークンの利用は現在サポートされていないことを明確にしてください。'
|
||||
|
||||
@@ -18,6 +18,7 @@ sections:
|
||||
- Issueコメントにアップロードされたビデオが適切にレンダリングされません。
|
||||
- GitHub Enterprise Importerを使ってリポジトリをインポートしようとすると、プロジェクトのタイムラインイベントが正しく設定されていないことから、一部のIssueのインポートに失敗します。
|
||||
- '`ghe-migrator`を使う場合、移行はIssueやPull Request内のビデオの添付ファイルのインポートに失敗します。'
|
||||
- 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
|
||||
changes:
|
||||
- 高可用性構成では、Management Consoleのレプリケーションの概要ページが現在のレプリケーションのステータスではなく、現在のレプリケーション設定だけを表示することを明確にしてください。
|
||||
- アップグレード後の移行が確実に完了するようにするため、依存関係グラフのためのNomadの割り当てのタイムアウトは長くなりました。
|
||||
|
||||
@@ -112,78 +112,78 @@ sections:
|
||||
heading: ワークフローに制限によるGitHub Actionsのためのセルフホストランナーの保護
|
||||
notes:
|
||||
- |
|
||||
Organization owners can now increase the security of CI/CD workflows on self-hosted runners by choosing which workflows can access a runner group. Previously, any workflow in a repository, such as an issue labeler, could access the self-hosted runners available to an organization. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)" and the [GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/).
|
||||
Organizationのオーナーは、セルフホストランナー上のCI/CDワークフローのセキュリティを、ランナーグループにアクセスできるワークフローを選択することによって向上させられるようになりました。以前は、Issueへのラベル付けなど、リポジトリ内の任意のワークフローがOrganizationで利用できるセルフホストランナーにアクセスできました。詳しい情報については「[グループを使ったセルフホストランナーへのアクセスの管理](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)」及び[GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/)を参照してください。
|
||||
-
|
||||
heading: Prevent GitHub Actions from approving pull requests
|
||||
heading: GitHub ActionsによるPull Requestの承認の回避
|
||||
notes:
|
||||
- |
|
||||
You can now control whether GitHub Actions can approve pull requests. This feature protects against a user using GitHub Actions to satisfy the "Required approvals" branch protection requirement and merging a change that was not reviewed by another user. To prevent breaking existing workflows, **Allow GitHub Actions reviews to count towards required approval** is enabled by default. Organization owners can disable the feature in the organization's GitHub Actions settings. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)."
|
||||
GitHub ActionsがPull Requestを承認できるかを制御できるようになりました。この機能は、ユーザがGitHub Actionsを使って"Required approvals（必須の承認）"ブランチ保護要求を満たし、他のユーザがレビューしてない変更をマージしてしまうことに対する保護になります。既存のワークフローを壊してしまわないように、**Allow GitHub Actions reviews to count towards required approval （GitHub Actionsレビューを必須の承認に対してカウントすることの許可）**はデフォルトで有効になっています。Organizationのオーナーはこの機能をOrganizationのGitHub Actions設定で無効化できます。詳しい情報については「[OrganizationでのGitHub Actionsの無効化もしくは制限(/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)」を参照してください。
|
||||
-
|
||||
heading: Re-run failed or individual GitHub Actions jobs
|
||||
heading: 失敗もしくは個々のGitHub Actionsのジョブの再実行
|
||||
notes:
|
||||
- |
|
||||
You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
|
||||
失敗したジョブ、あるいはGitHub Actionsワークフローの実行中の個別のジョブだけを再実行できるようになりました。詳しい情報については「[ワークフローとジョブの再実行](/actions/managing-workflow-runs/re-running-workflows-and-jobs)」を参照してください。
|
||||
-
|
||||
heading: Dependency graph supports GitHub Actions
|
||||
heading: 依存関係グラフによるGitHub Actionsのサポート
|
||||
notes:
|
||||
- |
|
||||
The dependency graph now detects YAML files for GitHub Actions workflows. GitHub Enterprise Server will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the "Used By" control on the repository homepage. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
依存関係グラフは、GitHub ActionsワークフローのYAMLファイルを検出するようになりました。GitHub Enterprise Serverは、**Insights**タブの依存関係グラフセクションの中にワークフローファイルを表示します。アクションを公開するリポジトリは、リポジトリのホームページの"Used By（利用先）"コントロールからそのアクションに依存しているリポジトリ数を見ることができるようにもなりました。詳しい情報については「[依存関係グラフについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)」を参照してください。
|
||||
-
|
||||
heading: Security overview for enterprises in public beta
|
||||
heading: Enterpriseのセキュリティ概要のパブリックベータ
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security customers can now view an overview of security alerts at the enterprise level. The new **Security** tab at the enterprise level provides a repository-centric view of application security risks, as well as an alert-centric view of all secret scanning alerts. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
GitHub Advanced Securityのお客様は、Enterpriseレベルでセキュリティアラートの概要を見ることができるようになりました。Enterpriseレベルの新たな**Security**タブは、アプリケーションのセキュリティリスクのリポジトリ中心のビューとともに、すべてのSecret scanningアラートのアラート中心のビューを提供します。詳しい情報については「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。
|
||||
-
|
||||
heading: Security view for organizations is generally available
|
||||
heading: Organizationのセキュリティビューの一般提供
|
||||
notes:
|
||||
- |
|
||||
The overview of security alerts at the organization level is now generally available. GitHub Advanced Security customers can use the security overview to view a repository-centric view of application security risks, or an alert-centric view of all code scanning, Dependabot, and secret scanning alerts for all repositories in an organization. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
Organizationレベルのセキュリティアラートの概要が、一般提供になりました。GitHub Advanced Securityのお客様は、セキュリティの概要を使ってアプリケーションのセキュリティリスクのリポジトリ中心のビューを見たり、Organization内のすべてのリポジトリに対するCode scanning、Dependabot、Secret scanningのすべてのアラートのアラート中心のビューを見たりすることができます。詳しい情報については「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。
|
||||
-
|
||||
heading: Code scanning detects more security issues, supports new language versions
|
||||
heading: Code scanningはより多くのセキュリティの問題を検出し、新しい言語のバージョンをサポート
|
||||
notes:
|
||||
- |
|
||||
Code scanning now detects a larger number of CWEs, and CodeQL code scanning fully supports the standard language features in the following language releases.
|
||||
Code scanningは多くのCWEを検出するようになり、CodeQLによるコードスキャンニングは以下の言語のリリースの標準的な言語機能を完全にサポートします。
|
||||
|
||||
- C# 10 / .NET 6
|
||||
- Python 3.10
|
||||
- Java 17
|
||||
- TypeScript 4.5
|
||||
|
||||
For more information, see the [GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/).
|
||||
詳しい情報については[GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/)を参照してください。
|
||||
-
|
||||
heading: View code scanning alerts across an organization
|
||||
heading: Organization全体のコードスキャンニングアラートの表示
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security customers can now view code scanning alerts in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
GitHub Advanced Securityのお客様は、Organizationの**Security*タブでコードスキャンニングアラートを見ることができるようになりました。このビューは、Organizationのオーナーと、[セキュリティ管理者のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)を持つTeamのメンバーが利用できます。詳しい情報については「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。
|
||||
- |
|
||||
Users can now retrieve code scanning alerts for an organization on your GitHub Enterprise Server instance via the REST API. This new API endpoint supplements the existing [endpoint for repositories](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository). For more information, see [Code Scanning](/rest/code-scanning) in the REST API documentation.
|
||||
ユーザは、REST APIを通じてGitHub Enterprise Serverインスタンス上のOrganizationのコードスキャンニングアラートを取得できるようになりました。この新しいAPIエンドポイントは、既存の[リポジトリのエンドポイント](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)を補完するものです。詳しい情報については、REST APIドキュメンテーションの[Code scanning](/rest/code-scanning)を参照してください。
|
||||
-
|
||||
heading: Secret scanning available as a push protection
|
||||
heading: プッシュ保護としてSecret scanningが利用可能
|
||||
notes:
|
||||
- |
|
||||
GitHub Enterprise Server can now block any pushes where a token is detected with high confidence. Developers can bypass the block by providing details of why the secret needs to be committed via a web UI. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
GitHub Enterprise Serverは、高い信頼度でトークンが検出されたプッシュをブロックできるようになりました。開発者は、シークレットをコミットしなければならない理由ｍの詳細をWeb UIから提供することによって、このブロックをバイパスできます。詳しい情報については「[Secret scanningでのプッシュの保護](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)」を参照してください。
|
||||
-
|
||||
heading: Dry runs for custom patterns with secret scanning
|
||||
heading: Secret Scanningのカスタムパターンのdry run
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security customers can now dry run custom secret scanning patterns at the organization or repository level. Dry runs allow people with owner or admin access to review and hone their patterns before publishing them and generating alerts. You can compose a pattern, then use **Save and dry run** to retrieve results. The scans typically take just a few seconds, but GitHub Enterprise Server will also notify organization owners or repository admins via email when dry run results are ready. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)" and "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
|
||||
GitHub Advanced Securityのお客様は、Organizationあるいはリポジトリレベルのカスタムのシークレットスキャンニングパターンをdry runできるようになりました。dry runを行うことで、オーナーもしくは管理アクセスを持つ人は、パターンを公開してアラートを発生させる前に、そのパターンをレビューして磨きあげることができます。パターンを作成し、**Save and dry run（保存してdry run）**を使って結果を取得してください。スキャンには通常数秒しかかかりませんが、GitHub Enterprise Serverはdry runの結果が準備できればメールでOrganizationのオーナーもしくはリポジトリ管理者に通知も行います。詳しい情報については「[Secret scanningについて](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)」及び「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。
|
||||
-
|
||||
heading: Secret scanning custom pattern events now in the audit log
|
||||
heading: Secret scanningのカスタムパターンイベントがAudit logに記録されるようになりました
|
||||
notes:
|
||||
- |
|
||||
The audit log now includes events associated with secret scanning custom patterns. This data helps GitHub Advanced Security customers understand actions taken on their [repository](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)-, [organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)-, or [enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)-level custom patterns for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)" or "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)."
|
||||
Audit logには、シークレットスキャンニングのカスタムパターンに関連するイベントが含まれるようになりました。このデータは、GitHub Advanced Securityのお客様がセキュリティ及びコンプライアンスの監査のために[リポジトリ](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)、[Organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)、[Enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)レベルのカスタムパターンに対して行われたアクションを理解するための役に立ちます。詳しい情報については「[OrganizationのAudit logのレビュー](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)」あるいは「[EnterpriseのAudit logのレビュー](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)」を参照してください。
|
||||
-
|
||||
heading: Configure permissions for secret scanning with custom repository roles
|
||||
heading: カスタムリポジトリロールでのSecret scanningの権限設定
|
||||
notes:
|
||||
- |
|
||||
You can now configure two new permissions for secret scanning when managing custom repository roles.
|
||||
カスタムリポジトリロールを管理する際に、Secret scanningのための2つの新たな権限を設定できるようになりました。
|
||||
|
||||
- View secret scanning results
|
||||
- Dismiss or reopen secret scanning results
|
||||
- Secret scanningの結果表示
|
||||
- Secret scanningの結果の却下もしくは再オープン
|
||||
|
||||
For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
|
||||
詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。
|
||||
-
|
||||
heading: Secret scanning now supports archived repositories
|
||||
heading: Secret scanningはアーカイブされたリポジトリをサポートしました
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security customers can now enable secret scanning for archived repositories via the UI and API. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)," "[About archived repositories](/repositories/archiving-a-github-repository/archiving-repositories)," and "[Repositories](/rest/repos/repos#update-a-repository)" in the REST API documentation.
|
||||
|
||||
@@ -105,78 +105,78 @@ sections:
|
||||
heading: ワークフローに制限によるGitHub Actionsのためのセルフホストランナーの保護
|
||||
notes:
|
||||
- |
|
||||
Organization owners can now increase the security of CI/CD workflows on self-hosted runners by choosing which workflows can access a runner group. Previously, any workflow in a repository, such as an issue labeler, could access the self-hosted runners available to an organization. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)" and the [GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/).
|
||||
Organizationのオーナーは、セルフホストランナー上のCI/CDワークフローのセキュリティを、ランナーグループにアクセスできるワークフローを選択することによって向上させられるようになりました。以前は、Issueへのラベル付けなど、リポジトリ内の任意のワークフローがOrganizationで利用できるセルフホストランナーにアクセスできました。詳しい情報については「[グループを使ったセルフホストランナーへのアクセスの管理](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)」及び[GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/)を参照してください。
|
||||
-
|
||||
heading: Prevent GitHub Actions from approving pull requests
|
||||
heading: GitHub ActionsによるPull Requestの承認の回避
|
||||
notes:
|
||||
- |
|
||||
You can now control whether GitHub Actions can approve pull requests. This feature protects against a user using GitHub Actions to satisfy the "Required approvals" branch protection requirement and merging a change that was not reviewed by another user. To prevent breaking existing workflows, **Allow GitHub Actions reviews to count towards required approval** is enabled by default. Organization owners can disable the feature in the organization's GitHub Actions settings. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)."
|
||||
GitHub ActionsがPull Requestを承認できるかを制御できるようになりました。この機能は、ユーザがGitHub Actionsを使って"Required approvals（必須の承認）"ブランチ保護要求を満たし、他のユーザがレビューしてない変更をマージしてしまうことに対する保護になります。既存のワークフローを壊してしまわないように、**Allow GitHub Actions reviews to count towards required approval （GitHub Actionsレビューを必須の承認に対してカウントすることの許可）**はデフォルトで有効になっています。Organizationのオーナーはこの機能をOrganizationのGitHub Actions設定で無効化できます。詳しい情報については「[OrganizationでのGitHub Actionsの無効化もしくは制限(/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)」を参照してください。
|
||||
-
|
||||
heading: Re-run failed or individual GitHub Actions jobs
|
||||
heading: 失敗もしくは個々のGitHub Actionsのジョブの再実行
|
||||
notes:
|
||||
- |
|
||||
You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
|
||||
失敗したジョブ、あるいはGitHub Actionsワークフローの実行中の個別のジョブだけを再実行できるようになりました。詳しい情報については「[ワークフローとジョブの再実行](/actions/managing-workflow-runs/re-running-workflows-and-jobs)」を参照してください。
|
||||
-
|
||||
heading: Dependency graph supports GitHub Actions
|
||||
heading: 依存関係グラフによるGitHub Actionsのサポート
|
||||
notes:
|
||||
- |
|
||||
The dependency graph now detects YAML files for GitHub Actions workflows. GitHub Enterprise Server will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the "Used By" control on the repository homepage. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
依存関係グラフは、GitHub ActionsワークフローのYAMLファイルを検出するようになりました。GitHub Enterprise Serverは、**Insights**タブの依存関係グラフセクションの中にワークフローファイルを表示します。アクションを公開するリポジトリは、リポジトリのホームページの"Used By（利用先）"コントロールからそのアクションに依存しているリポジトリ数を見ることができるようにもなりました。詳しい情報については「[依存関係グラフについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)」を参照してください。
|
||||
-
|
||||
heading: Security overview for enterprises in public beta
|
||||
heading: Enterpriseのセキュリティ概要のパブリックベータ
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security customers can now view an overview of security alerts at the enterprise level. The new **Security** tab at the enterprise level provides a repository-centric view of application security risks, as well as an alert-centric view of all secret scanning alerts. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
GitHub Advanced Securityのお客様は、Enterpriseレベルでセキュリティアラートの概要を見ることができるようになりました。Enterpriseレベルの新たな**Security**タブは、アプリケーションのセキュリティリスクのリポジトリ中心のビューとともに、すべてのSecret scanningアラートのアラート中心のビューを提供します。詳しい情報については「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。
|
||||
-
|
||||
heading: Security view for organizations is generally available
|
||||
heading: Organizationのセキュリティビューの一般提供
|
||||
notes:
|
||||
- |
|
||||
The overview of security alerts at the organization level is now generally available. GitHub Advanced Security customers can use the security overview to view a repository-centric view of application security risks, or an alert-centric view of all code scanning, Dependabot, and secret scanning alerts for all repositories in an organization. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
Organizationレベルのセキュリティアラートの概要が、一般提供になりました。GitHub Advanced Securityのお客様は、セキュリティの概要を使ってアプリケーションのセキュリティリスクのリポジトリ中心のビューを見たり、Organization内のすべてのリポジトリに対するCode scanning、Dependabot、Secret scanningのすべてのアラートのアラート中心のビューを見たりすることができます。詳しい情報については「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。
|
||||
-
|
||||
heading: Code scanning detects more security issues, supports new language versions
|
||||
heading: Code scanningはより多くのセキュリティの問題を検出し、新しい言語のバージョンをサポート
|
||||
notes:
|
||||
- |
|
||||
Code scanning now detects a larger number of CWEs, and CodeQL code scanning fully supports the standard language features in the following language releases.
|
||||
Code scanningは多くのCWEを検出するようになり、CodeQLによるコードスキャンニングは以下の言語のリリースの標準的な言語機能を完全にサポートします。
|
||||
|
||||
- C# 10 / .NET 6
|
||||
- Python 3.10
|
||||
- Java 17
|
||||
- TypeScript 4.5
|
||||
|
||||
For more information, see the [GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/).
|
||||
詳しい情報については[GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/)を参照してください。
|
||||
-
|
||||
heading: View code scanning alerts across an organization
|
||||
heading: Organization全体のコードスキャンニングアラートの表示
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security customers can now view code scanning alerts in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
|
||||
GitHub Advanced Securityのお客様は、Organizationの**Security*タブでコードスキャンニングアラートを見ることができるようになりました。このビューは、Organizationのオーナーと、[セキュリティ管理者のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)を持つTeamのメンバーが利用できます。詳しい情報については「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。
|
||||
- |
|
||||
Users can now retrieve code scanning alerts for an organization on your GitHub Enterprise Server instance via the REST API. This new API endpoint supplements the existing [endpoint for repositories](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository). For more information, see [Code Scanning](/rest/code-scanning) in the REST API documentation.
|
||||
ユーザは、REST APIを通じてGitHub Enterprise Serverインスタンス上のOrganizationのコードスキャンニングアラートを取得できるようになりました。この新しいAPIエンドポイントは、既存の[リポジトリのエンドポイント](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)を補完するものです。詳しい情報については、REST APIドキュメンテーションの[Code scanning](/rest/code-scanning)を参照してください。
|
||||
-
|
||||
heading: Secret scanning available as a push protection
|
||||
heading: プッシュ保護としてSecret scanningが利用可能
|
||||
notes:
|
||||
- |
|
||||
GitHub Enterprise Server can now block any pushes where a token is detected with high confidence. Developers can bypass the block by providing details of why the secret needs to be committed via a web UI. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
GitHub Enterprise Serverは、高い信頼度でトークンが検出されたプッシュをブロックできるようになりました。開発者は、シークレットをコミットしなければならない理由ｍの詳細をWeb UIから提供することによって、このブロックをバイパスできます。詳しい情報については「[Secret scanningでのプッシュの保護](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)」を参照してください。
|
||||
-
|
||||
heading: Dry runs for custom patterns with secret scanning
|
||||
heading: Secret Scanningのカスタムパターンのdry run
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security customers can now dry run custom secret scanning patterns at the organization or repository level. Dry runs allow people with owner or admin access to review and hone their patterns before publishing them and generating alerts. You can compose a pattern, then use **Save and dry run** to retrieve results. The scans typically take just a few seconds, but GitHub Enterprise Server will also notify organization owners or repository admins via email when dry run results are ready. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)" and "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
|
||||
GitHub Advanced Securityのお客様は、Organizationあるいはリポジトリレベルのカスタムのシークレットスキャンニングパターンをdry runできるようになりました。dry runを行うことで、オーナーもしくは管理アクセスを持つ人は、パターンを公開してアラートを発生させる前に、そのパターンをレビューして磨きあげることができます。パターンを作成し、**Save and dry run（保存してdry run）**を使って結果を取得してください。スキャンには通常数秒しかかかりませんが、GitHub Enterprise Serverはdry runの結果が準備できればメールでOrganizationのオーナーもしくはリポジトリ管理者に通知も行います。詳しい情報については「[Secret scanningについて](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)」及び「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。
|
||||
-
|
||||
heading: Secret scanning custom pattern events now in the audit log
|
||||
heading: Secret scanningのカスタムパターンイベントがAudit logに記録されるようになりました
|
||||
notes:
|
||||
- |
|
||||
The audit log now includes events associated with secret scanning custom patterns. This data helps GitHub Advanced Security customers understand actions taken on their [repository](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)-, [organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)-, or [enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)-level custom patterns for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)" or "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)."
|
||||
Audit logには、シークレットスキャンニングのカスタムパターンに関連するイベントが含まれるようになりました。このデータは、GitHub Advanced Securityのお客様がセキュリティ及びコンプライアンスの監査のために[リポジトリ](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)、[Organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)、[Enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)レベルのカスタムパターンに対して行われたアクションを理解するための役に立ちます。詳しい情報については「[OrganizationのAudit logのレビュー](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)」あるいは「[EnterpriseのAudit logのレビュー](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)」を参照してください。
|
||||
-
|
||||
heading: Configure permissions for secret scanning with custom repository roles
|
||||
heading: カスタムリポジトリロールでのSecret scanningの権限設定
|
||||
notes:
|
||||
- |
|
||||
You can now configure two new permissions for secret scanning when managing custom repository roles.
|
||||
カスタムリポジトリロールを管理する際に、Secret scanningのための2つの新たな権限を設定できるようになりました。
|
||||
|
||||
- View secret scanning results
|
||||
- Dismiss or reopen secret scanning results
|
||||
- Secret scanningの結果表示
|
||||
- Secret scanningの結果の却下もしくは再オープン
|
||||
|
||||
For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
|
||||
詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。
|
||||
-
|
||||
heading: Secret scanning now supports archived repositories
|
||||
heading: Secret scanningはアーカイブされたリポジトリをサポートしました
|
||||
notes:
|
||||
- |
|
||||
GitHub Advanced Security customers can now enable secret scanning for archived repositories via the UI and API. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)," "[About archived repositories](/repositories/archiving-a-github-repository/archiving-repositories)," and "[Repositories](/rest/repos/repos#update-a-repository)" in the REST API documentation.
|
||||
|
||||
@@ -0,0 +1,6 @@
|
||||
Reusable workflows from public repositories can be referenced using a SHA, a release tag, or a branch name. For more information, see ["Calling a reusable workflow"](/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow).
|
||||
|
||||
When you re-run a workflow that uses a reusable workflow and the reference is not a SHA, there are some behaviors to be aware of:
|
||||
|
||||
* Re-running all jobs in a workflow will use the reusable workflow from the specified reference. For more information about re-running all jobs in a workflow, see ["Re-running all the jobs in a workflow"](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-all-the-jobs-in-a-workflow).
|
||||
* Re-running failed jobs or a specific job in a workflow will use the reusable workflow from the same commit SHA of the first attempt. For more information about re-running failed jobs in a workflow, see ["Re-running failed jobs in a workflow"](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-failed-jobs-in-a-workflow). For more information about re-running a specific job in a workflow, see ["Re-running a specific job in a workflow"](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-a-specific-job-in-a-workflow).
|
||||
@@ -1,3 +1,3 @@
|
||||
As a student or faculty member at an accredited educational institution, you can apply for GitHub Education benefits, which includes access to GitHub Global Campus. Global Campus is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The Global Campus portal includes access to the GitHub Education Community, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, GitHub Classroom, and other exclusive features to help students and teachers shape the next generation of software development.
|
||||
As a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_global_campus %}. {% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits—all in one place! The {% data variables.product.prodname_global_campus %} portal includes access to {% data variables.product.prodname_education_community_with_url %}, industry tools used by professional developers, events, [Campus TV](https://www.twitch.tv/githubeducation) content, {% data variables.product.prodname_classroom_with_url %}, and other exclusive features to help students and teachers shape the next generation of software development.
|
||||
|
||||
個人の割引を適用する前に、あなたの学習コミュニティがすでに弊社と{% data variables.product.prodname_campus_program %}学校としてパートナーになっているかを確認してください。 詳しい情報については、「[{% data variables.product.prodname_campus_program %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)」を参照してください。
|
||||
|
||||
@@ -45,6 +45,8 @@ prodname_classroom: 'GitHub Classroom'
|
||||
prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)'
|
||||
prodname_campus_program: 'GitHub Campus Program'
|
||||
prodname_student_pack: 'GitHub 学生開発者パック'
|
||||
prodname_global_campus: 'GitHub Global Campus'
|
||||
prodname_community_exchange: 'GitHub Community Exchange'
|
||||
#GitHub CLI
|
||||
prodname_cli: 'GitHub CLI'
|
||||
#GitHub Desktop
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
file,reason
|
||||
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,broken liquid tags
|
||||
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,broken liquid tags
|
||||
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,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags
|
||||
|
||||
|
Reference in New Issue
Block a user