Skip to content

Commit b510e0f

Browse files
docubotfrancisfuzz
andauthored
New translation batch for ja (#23805)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check parsing * 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 Co-authored-by: Francis <15894826+francisfuzz@users.noreply.github.com>
1 parent a3027f1 commit b510e0f

70 files changed

Lines changed: 923 additions & 834 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

translations/ja-JP/content/admin/advanced-security/index.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,6 @@ children:
1515
- /enabling-github-advanced-security-for-your-enterprise
1616
- /configuring-code-scanning-for-your-appliance
1717
- /configuring-secret-scanning-for-your-appliance
18-
- /viewing-your-github-advanced-security-usage
1918
- /overview-of-github-advanced-security-deployment
2019
- /deploying-github-advanced-security-in-your-enterprise
2120
---
22-

translations/ja-JP/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Git Large File Storage のダウングレード
3-
intro: '{% data variables.large_files.product_name_short %} のストレージと帯域幅を 1 月あたり 50GB 刻みでダウングレードできます。'
2+
title: Downgrading Git Large File Storage
3+
intro: 'You can downgrade storage and bandwidth for {% data variables.large_files.product_name_short %} by increments of 50 GB per month.'
44
redirect_from:
55
- /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage
6-
- /articles/downgrading-storage-and-bandwidth-for-a-personal-account/
7-
- /articles/downgrading-storage-and-bandwidth-for-an-organization/
6+
- /articles/downgrading-storage-and-bandwidth-for-a-personal-account
7+
- /articles/downgrading-storage-and-bandwidth-for-an-organization
88
- /articles/downgrading-git-large-file-storage
99
- /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage
1010
versions:
@@ -16,19 +16,18 @@ topics:
1616
- LFS
1717
- Organizations
1818
- User account
19-
shortTitle: Git LFSストレージのダウングレード
19+
shortTitle: Downgrade Git LFS storage
2020
---
21+
When you downgrade your number of data packs, your change takes effect on your next billing date. For more information, see "[About billing for {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)."
2122

22-
データパック数をダウングレードすると、その変更は次回の支払日から有効になります。 詳細は「[{% data variables.large_files.product_name_long %} の支払いについて](/articles/about-billing-for-git-large-file-storage)」を参照してください。
23-
24-
## 個人アカウントのストレージと帯域幅をダウングレード
23+
## Downgrading storage and bandwidth for a personal account
2524

2625
{% data reusables.user_settings.access_settings %}
2726
{% data reusables.user_settings.billing_plans %}
2827
{% data reusables.dotcom_billing.lfs-remove-data %}
2928
{% data reusables.large_files.downgrade_data_packs %}
3029

31-
## Organization のストレージと帯域幅をダウングレード
30+
## Downgrading storage and bandwidth for an organization
3231

3332
{% data reusables.dotcom_billing.org-billing-perms %}
3433

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Git Large File Storage をアップグレードする
3-
intro: '追加のデータパックを購入すると、{% data variables.large_files.product_name_short %} の毎月の帯域幅容量と総ストレージ容量を増やすことができます。'
2+
title: Upgrading Git Large File Storage
3+
intro: 'You can purchase additional data packs to increase your monthly bandwidth quota and total storage capacity for {% data variables.large_files.product_name_short %}.'
44
redirect_from:
55
- /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage
6-
- /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account/
7-
- /articles/purchasing-additional-storage-and-bandwidth-for-an-organization/
6+
- /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account
7+
- /articles/purchasing-additional-storage-and-bandwidth-for-an-organization
88
- /articles/upgrading-git-large-file-storage
99
- /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
1010
versions:
@@ -16,18 +16,17 @@ topics:
1616
- Organizations
1717
- Upgrades
1818
- User account
19-
shortTitle: Git LFSストレージのアップグレード
19+
shortTitle: Upgrade Git LFS storage
2020
---
21-
22-
## 個人アカウント用に追加のストレージと帯域幅を購入する
21+
## Purchasing additional storage and bandwidth for a personal account
2322

2423
{% data reusables.user_settings.access_settings %}
2524
{% data reusables.user_settings.billing_plans %}
2625
{% data reusables.dotcom_billing.lfs-add-data %}
2726
{% data reusables.large_files.pack_selection %}
2827
{% data reusables.large_files.pack_confirm %}
2928

30-
## Organization 用に追加のストレージと帯域幅を購入する
29+
## Purchasing additional storage and bandwidth for an organization
3130

3231
{% data reusables.dotcom_billing.org-billing-perms %}
3332

@@ -36,9 +35,9 @@ shortTitle: Git LFSストレージのアップグレード
3635
{% data reusables.large_files.pack_selection %}
3736
{% data reusables.large_files.pack_confirm %}
3837

39-
## 参考リンク
38+
## Further reading
4039

41-
- [{% data variables.large_files.product_name_long %} の支払いについて](/articles/about-billing-for-git-large-file-storage)
42-
- [ストレージと帯域の利用について](/articles/about-storage-and-bandwidth-usage)
43-
- [ {% data variables.large_files.product_name_long %}の利用状況を表示する](/articles/viewing-your-git-large-file-storage-usage)
44-
- [大きなファイルのバージョン付け](/articles/versioning-large-files)
40+
- "[About billing for {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)"
41+
- "[About storage and bandwidth usage](/articles/about-storage-and-bandwidth-usage)"
42+
- "[Viewing your {% data variables.large_files.product_name_long %} usage](/articles/viewing-your-git-large-file-storage-usage)"
43+
- "[Versioning large files](/articles/versioning-large-files)"
Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Git Large File Storage の使用状況を表示する
3-
intro: 'アカウントの毎月の帯域幅容量と {% data variables.large_files.product_name_short %} の残りの容量を監査できます。'
2+
title: Viewing your Git Large File Storage usage
3+
intro: 'You can audit your account''s monthly bandwidth quota and remaining storage for {% data variables.large_files.product_name_short %}.'
44
redirect_from:
55
- /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage
6-
- /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account/
7-
- /articles/viewing-storage-and-bandwidth-usage-for-an-organization/
6+
- /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account
7+
- /articles/viewing-storage-and-bandwidth-usage-for-an-organization
88
- /articles/viewing-your-git-large-file-storage-usage
99
- /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage
1010
versions:
@@ -15,25 +15,24 @@ topics:
1515
- LFS
1616
- Organizations
1717
- User account
18-
shortTitle: Git LFSの使用状況の表示
18+
shortTitle: View Git LFS usage
1919
---
20-
2120
{% data reusables.large_files.owner_quota_only %} {% data reusables.large_files.does_not_carry %}
2221

23-
## 個人アカウントのストレージと帯域幅の使用状況を表示する
22+
## Viewing storage and bandwidth usage for a personal account
2423

2524
{% data reusables.user_settings.access_settings %}
2625
{% data reusables.user_settings.billing_plans %}
2726
{% data reusables.dotcom_billing.lfs-data %}
2827

29-
## Organization のストレージと帯域幅の使用状況を表示する
28+
## Viewing storage and bandwidth usage for an organization
3029

3130
{% data reusables.dotcom_billing.org-billing-perms %}
3231

3332
{% data reusables.organizations.billing-settings %}
3433
{% data reusables.dotcom_billing.lfs-data %}
3534

36-
## 参考リンク
35+
## Further reading
3736

38-
- [ストレージと帯域の利用について](/articles/about-storage-and-bandwidth-usage)
39-
- [{% data variables.large_files.product_name_long %} をアップグレードする](/articles/upgrading-git-large-file-storage/)
37+
- "[About storage and bandwidth usage](/articles/about-storage-and-bandwidth-usage)"
38+
- "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)"
Lines changed: 17 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
2-
title: 購入代行業者のためのOrganizationについて
3-
intro: 企業は、Organizationを使って複数のオーナーと管理者を持つ共有プロジェクト上でコラボレートします。 クライアントのためにOrganizationを作成し、クライアントの代理で支払いを行い、そしてOrganizationの所有権をクライアントに渡すことができます。
2+
title: About organizations for procurement companies
3+
intro: 'Businesses use organizations to collaborate on shared projects with multiple owners and administrators. You can create an organization for your client, make a payment on their behalf, then pass ownership of the organization to your client.'
44
redirect_from:
55
- /github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies
6-
- /articles/about-organizations-for-resellers/
6+
- /articles/about-organizations-for-resellers
77
- /articles/about-organizations-for-procurement-companies
88
- /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies
99
versions:
@@ -12,28 +12,27 @@ versions:
1212
type: overview
1313
topics:
1414
- Organizations
15-
shortTitle: Organizationについて
15+
shortTitle: About organizations
1616
---
17+
To access an organization, each member must sign into their own personal user account.
1718

18-
Organizationにアクセスするためには、各メンバーは自身のパーソナルユーザアカウントにサインインしなければなりません
19+
Organization members can have different roles, such as *owner* or *billing manager*:
1920

20-
Organizationのメンバーは、*オーナー*あるいは*支払いマネージャー*など、様々なロールを持ちます。
21+
- **Owners** have complete administrative access to an organization and its contents.
22+
- **Billing managers** can manage billing settings, and cannot access organization contents. Billing managers are not shown in the list of organization members.
2123

22-
- **オーナー**は、Organizationとそのコンテンツについて完全な管理アクセスを持ちます。
23-
- **支払いマネージャー**は支払いの設定を管理でき、Organization のコンテンツにはアクセスできません。 支払いマネージャーは、Organization のメンバーのリストには表示されません。
24+
## Payments and pricing for organizations
2425

25-
## Organizationの支払いと価格
26+
We don't provide quotes for organization pricing. You can see our published pricing for [organizations](https://github.com/pricing) and [Git Large File Storage](/articles/about-storage-and-bandwidth-usage/). We do not provide discounts for procurement companies or for renewal orders.
2627

27-
Organizationの価格について、弊社は見積もりを提供しません。 [Organization](https://github.com/pricing)[Git Large File Storage](/articles/about-storage-and-bandwidth-usage/)の弊社の公開価格をご覧いただけます。 購買代行業者に対する割引あるいは契約更新時の割引は提供しておりません。
28+
We accept payment in US dollars, although end users may be located anywhere in the world.
2829

29-
支払いはUSドルで受け付けていますが、エンドユーザの場所は世界中のどの地域でも問題ありません。
30+
We accept payment by credit card and PayPal. We don't accept payment by purchase order or invoice.
3031

31-
支払いはクレジットカードと PayPal で受け付けています。 注文書や請求書での支払いは受け付けていません。
32+
For easier and more efficient purchasing, we recommend that procurement companies set up yearly billing for their clients' organizations.
3233

33-
購入を容易かつ効率的に行うために、購入代行業者はクライアントのOrganization用に年間の支払いをセットアップすることをおすすめします。
34+
## Further reading
3435

35-
## 参考リンク
36-
37-
- [クライアントの代理でのOrganizationの作成と支払い](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)
38-
- [クライアントの有料Organizationのアップグレードあるいはダウングレード](/articles/upgrading-or-downgrading-your-client-s-paid-organization)
39-
- [クライアントの有料Organizationの更新](/articles/renewing-your-client-s-paid-organization)
36+
- "[Creating and paying for an organization on behalf of a client](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)"
37+
- "[Upgrading or downgrading your client's paid organization](/articles/upgrading-or-downgrading-your-client-s-paid-organization)"
38+
- "[Renewing your client's paid organization](/articles/renewing-your-client-s-paid-organization)"

translations/ja-JP/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: 購入代行業者のための有料 Organization のセットアップ
3-
shortTitle: 購入代行業者のための有料Organization
4-
intro: 'クライアントに代わり {% data variables.product.product_name %} に支払う場合、利便性とセキュリティを最適化するために、その Organization および支払い設定ができます。'
2+
title: Setting up paid organizations for procurement companies
3+
shortTitle: Paid organizations for procurement companies
4+
intro: 'If you pay for {% data variables.product.product_name %} on behalf of a client, you can configure their organization and payment settings to optimize convenience and security.'
55
redirect_from:
66
- /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies
7-
- /articles/setting-up-and-paying-for-organizations-for-resellers/
8-
- /articles/setting-up-and-paying-for-organizations-for-procurement-companies/
7+
- /articles/setting-up-and-paying-for-organizations-for-resellers
8+
- /articles/setting-up-and-paying-for-organizations-for-procurement-companies
99
- /articles/setting-up-paid-organizations-for-procurement-companies
1010
versions:
1111
fpt: '*'

translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22
title: Managing vulnerabilities in your project's dependencies
33
intro: 'You can track your repository''s dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies.'
44
redirect_from:
5-
- /articles/updating-your-project-s-dependencies/
6-
- /articles/updating-your-projects-dependencies/
7-
- /articles/managing-security-vulnerabilities-in-your-projects-dependencies/
5+
- /articles/updating-your-project-s-dependencies
6+
- /articles/updating-your-projects-dependencies
7+
- /articles/managing-security-vulnerabilities-in-your-projects-dependencies
88
- /articles/managing-vulnerabilities-in-your-projects-dependencies
99
- /github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies
1010
versions:

translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,12 @@ A codespace will stop running after a period of inactivity. You can specify the
1818

1919
{% endwarning %}
2020

21-
## Setting your default timeout
22-
2321
{% include tool-switcher %}
2422

2523
{% webui %}
2624

25+
## Setting your default timeout
26+
2727
{% data reusables.user_settings.access_settings %}
2828
{% data reusables.user_settings.codespaces-tab %}
2929
1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
@@ -33,14 +33,16 @@ A codespace will stop running after a period of inactivity. You can specify the
3333

3434
{% cli %}
3535

36+
## Setting your timeout period
37+
3638
{% data reusables.cli.cli-learn-more %}
3739

38-
To set the timeout period, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (5 hours).
40+
To set the timeout period when you create a codespace, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (4 hours).
3941

4042
```shell
4143
gh codespace create --idle-timeout 90m
4244
```
4345

44-
If you do not specify a timeout period when creating a codespace, then your default timeout period will be used. You cannot currently specify a default timeout period for all future codespaces through {% data variables.product.prodname_cli %}.
46+
If you don't specify a timeout period when you create a codespace, then the default timeout period will be used. For information about setting a default timeout period, click the "Web browser" tab on this page. You can't currently specify a default timeout period through {% data variables.product.prodname_cli %}.
4547

4648
{% endcli %}

0 commit comments

Comments
 (0)