New translation batch for ja (#31345)
This commit is contained in:
docubot
@@ -44,14 +44,14 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
{%- ifversion ghae %}
|
||||
<!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
|
||||
```shell
|
||||
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
|
||||
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
|
||||
```
|
||||
{%- else %}
|
||||
```shell
|
||||
$ ssh-keygen -t ed25519 -C "<em>your_email@example.com</em>"
|
||||
```
|
||||
{% note %}
|
||||
|
||||
|
||||
**Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
|
||||
```shell
|
||||
$ ssh-keygen -t rsa -b 4096 -C "<em>your_email@example.com</em>"
|
||||
@@ -67,27 +67,27 @@ If you are a site administrator for {% data variables.product.product_location %
|
||||
3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_<em>algorithm</em>): <em>[Press enter]</em>
|
||||
```
|
||||
|
||||
|
||||
{% endmac %}
|
||||
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_<em>algorithm</em>):<em>[Press enter]</em>
|
||||
```
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
|
||||
{% linux %}
|
||||
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/home/<em>you</em>/.ssh/<em>algorithm</em>): <em>[Press enter]</em>
|
||||
```
|
||||
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
|
||||
@@ -119,7 +119,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
|
||||
$ touch ~/.ssh/config
|
||||
```
|
||||
|
||||
* Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
|
||||
* Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
|
||||
|
||||
```
|
||||
Host *
|
||||
@@ -131,9 +131,9 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
|
||||
{% note %}
|
||||
|
||||
**Notes:**
|
||||
|
||||
|
||||
- If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
|
||||
|
||||
|
||||
- If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *` section.
|
||||
|
||||
```
|
||||
@@ -144,15 +144,16 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
|
||||
|
||||
3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
|
||||
```shell
|
||||
$ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
|
||||
```
|
||||
{% note %}
|
||||
$ ssh-add --apple-use-keychain ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
|
||||
```
|
||||
{% note %}
|
||||
|
||||
**Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `-K` option.
|
||||
**Note:** The `--apple-use-keychain` option stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `--apple-use-keychain` option.
|
||||
|
||||
The `--apple-use-keychain` option is in Apple's standard version of `ssh-add`. In MacOS versions prior to Monterey (12.0), the `--apple-use-keychain` and `--apple-load-keychain` flags used the syntax `-K` and `-A`, respectively.
|
||||
|
||||
If you don't have Apple's standard version of `ssh-add` installed, you may receive an error. For more information, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
|
||||
|
||||
If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
|
||||
|
||||
In MacOS Monterey (12.0), the `-K` and `-A` flags are deprecated and have been replaced by the `--apple-use-keychain` and `--apple-load-keychain` flags, respectively.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -199,7 +200,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
```shell
|
||||
$ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "<em>your_email@example.com</em>"
|
||||
```
|
||||
|
||||
|
||||
{%- ifversion not ghae %}
|
||||
{% note %}
|
||||
|
||||
@@ -207,34 +208,34 @@ If you are using macOS or Linux, you may need to update your SSH client or insta
|
||||
```shell
|
||||
$ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
|
||||
```
|
||||
|
||||
|
||||
{% endnote %}
|
||||
{%- endif %}
|
||||
4. When you are prompted, touch the button on your hardware security key.
|
||||
5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
|
||||
```
|
||||
|
||||
{% endmac %}
|
||||
|
||||
|
||||
{% windows %}
|
||||
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/c/Users/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):<em>[Press enter]</em>
|
||||
```
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
|
||||
{% linux %}
|
||||
|
||||
|
||||
```shell
|
||||
> Enter a file in which to save the key (/home/<em>you</em>/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): <em>[Press enter]</em>
|
||||
```
|
||||
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
6. When you are prompted to type a passphrase, press **Enter**.
|
||||
|
||||
@@ -1065,6 +1065,10 @@ Key | Type | Description
|
||||
|
||||
{% data reusables.webhooks.pull_request_short_desc %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.pull_requests.merge-queue-beta %}
|
||||
{% endif %}
|
||||
|
||||
### Availability
|
||||
|
||||
- Repository webhooks
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub Pages サイトのカスタムドメインを管理する
|
||||
intro: '特定の DNS レコードとリポジトリ設定を設定または更新し、{% data variables.product.prodname_pages %} サイトのデフォルトドメインをカスタムドメインに指定することができます。'
|
||||
title: Managing a custom domain for your GitHub Pages site
|
||||
intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.'
|
||||
redirect_from:
|
||||
- /articles/quick-start-setting-up-a-custom-domain
|
||||
- /articles/setting-up-an-apex-domain
|
||||
@@ -18,42 +18,49 @@ versions:
|
||||
topics:
|
||||
- Pages
|
||||
shortTitle: Manage a custom domain
|
||||
ms.openlocfilehash: ad96d0be88614e8294e29de74fd7112cfed1bc46
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147710324'
|
||||
---
|
||||
リポジトリの管理者権限があるユーザは、{% data variables.product.prodname_pages %} サイトのカスタムドメインを設定できます。
|
||||
|
||||
## カスタムドメインの設定について
|
||||
People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site.
|
||||
|
||||
DNS プロバイダでカスタムドメインを設定する前に、必ず {% data variables.product.prodname_pages %} サイトをカスタムドメインに追加してください。 カスタムドメインを {% data variables.product.product_name %} に追加せずに DNS プロバイダに設定すると、別のユーザがあなたのサブドメインにサイトをホストできることになります。
|
||||
## About custom domain configuration
|
||||
|
||||
Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains.
|
||||
|
||||
{% windows %}
|
||||
|
||||
DNS レコードの構成が正しいかどうかを確認するために利用できる `dig` コマンドは、Windows には含まれていません。 DNS レコードが正しく構成されていることを確認する前に、[BIND](https://www.isc.org/bind/) をインストールする必要があります。
|
||||
The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/).
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** DNS の変更内容が反映されるまで最大で 24 時間かかることがあります。
|
||||
**Note:** DNS changes can take up to 24 hours to propagate.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## サブドメインを設定する
|
||||
## Configuring a subdomain
|
||||
|
||||
`www` またはカスタム サブドメイン (`www.example.com` や `blog.example.com` など) を設定するには、リポジトリ設定にドメインを追加する必要があります。 その後、DNS プロバイダで CNAME レコードを設定します。
|
||||
To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings. After that, configure a CNAME record with your DNS provider.
|
||||
|
||||
{% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
|
||||
4. [カスタム ドメイン] で、カスタム ドメイン名を入力してから、 **[保存]** をクリックします。 ブランチからサイトを公開している場合は、ソース ブランチのルートに `CNAME` ファイルを追加するコミットが作成されます。 カスタムの {% data variables.product.prodname_actions %} ワークフローを使用してサイトを公開している場合、`CNAME` ファイルは作成されません。 公開元の詳細については、「[GitHub Pages サイトの公開元を設定する](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)」を参照してください。
|
||||
![カスタム ドメインの [保存] ボタン](/assets/images/help/pages/save-custom-subdomain.png)
|
||||
5. ご利用の DNS プロバイダーに移動し、サブドメインがサイトの既定のドメインを指す `CNAME`CNAME レコードを作成します。 たとえば、ユーザー サイトのサブドメイン `www.example.com` を使用する場合は、`www.example.com` が `<user>.github.io` を指す `CNAME` レコードを作成します。 組織サイトのサブドメイン `another.example.com` を使用する場合は、`another.example.com` が `<organization>.github.io` を指す `CNAME` レコードを作成します。 `CNAME` レコードは常に、`<user>.github.io` または `<organization>.github.io` (リポジトリ名を除く) を指す必要があります。 {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
{% data reusables.pages.navigate-site-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.pages.sidebar-pages %}
|
||||
4. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow , no `CNAME` file is created. For more information about your publishing source, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
|
||||
|
||||
|
||||
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. DNS レコードが正しく構成されたことを確認するには、`dig` コマンドを使用します。_WWW.EXAMPLE.COM_ はご利用のサブドメインに置き換えてください。
|
||||
{% note %}
|
||||
|
||||
**Note:** If your custom domain is an internationalized domain name, you must enter the Punycode encoded version.
|
||||
|
||||
For more information on Punycodes, see [Internationalized domain name](https://en.wikipedia.org/wiki/Internationalized_domain_name).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
5. Navigate to your DNS provider and create a `CNAME` record that points your subdomain to the default domain for your site. For example, if you want to use the subdomain `www.example.com` for your user site, create a `CNAME` record that points `www.example.com` to `<user>.github.io`. If you want to use the subdomain `another.example.com` for your organization site, create a `CNAME` record that points `another.example.com` to `<organization>.github.io`. The `CNAME` record should always point to `<user>.github.io` or `<organization>.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
|
||||
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain.
|
||||
```shell
|
||||
$ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
|
||||
> ;<em>WWW.EXAMPLE.COM.</em> IN A
|
||||
@@ -61,27 +68,30 @@ DNS レコードの構成が正しいかどうかを確認するために利用
|
||||
> <em>YOUR-USERNAME</em>.github.io. 43192 IN CNAME <em> GITHUB-PAGES-SERVER </em>.
|
||||
> <em> GITHUB-PAGES-SERVER </em>. 22 IN A 192.0.2.1
|
||||
```
|
||||
{% data reusables.pages.build-locally-download-cname %} {% data reusables.pages.enforce-https-custom-domain %}
|
||||
{% data reusables.pages.build-locally-download-cname %}
|
||||
{% data reusables.pages.enforce-https-custom-domain %}
|
||||
|
||||
## Apexドメインを設定する
|
||||
## Configuring an apex domain
|
||||
|
||||
`example.com` などの apex ドメインを設定するには、リポジトリ設定でカスタムドメインを構成し、ご利用の DNS プロバイダーで少なくとも 1 つの `ALIAS`、`ANAME`、または `A` レコードを構成する必要があります。
|
||||
To set up an apex domain, such as `example.com`, you must configure a custom domain in your repository settings and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider.
|
||||
|
||||
{% data reusables.pages.www-and-apex-domain-recommendation %} 詳細については、「[サブドメインの構成](#configuring-a-subdomain)」を参照してください。
|
||||
{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)."
|
||||
|
||||
{% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
|
||||
4. [カスタム ドメイン] で、カスタム ドメイン名を入力してから、 **[保存]** をクリックします。 ブランチからサイトを公開している場合は、ソース ブランチのルートに `CNAME` ファイルを追加するコミットが作成されます。 カスタムの {% data variables.product.prodname_actions %} ワークフローを使用してサイトを公開している場合、`CNAME` ファイルは作成されません。 公開元の詳細については、「[GitHub Pages サイトの公開元を設定する](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)」を参照してください。
|
||||
![カスタム ドメインの [保存] ボタン](/assets/images/help/pages/save-custom-apex-domain.png)
|
||||
5. DNS プロバイダーに移動し、`ALIAS`、`ANAME`、または `A` レコードを作成します。 IPv6 サポートのために `AAAA` レコードを作成することもできます。 {% data reusables.pages.contact-dns-provider %}
|
||||
- `ALIAS` または `ANAME` レコードを作成するには、apex ドメインがサイトの既定のドメインを指すようにします。 {% data reusables.pages.default-domain-information %}
|
||||
- `A` レコードを作成するには、apex ドメインが {% data variables.product.prodname_pages %} の IP アドレスを指すようにします。
|
||||
{% data reusables.pages.navigate-site-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.pages.sidebar-pages %}
|
||||
4. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow , no `CNAME` file is created. For more information about your publishing source, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
|
||||
|
||||
5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
|
||||
- To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
|
||||
- To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
|
||||
```shell
|
||||
185.199.108.153
|
||||
185.199.109.153
|
||||
185.199.110.153
|
||||
185.199.111.153
|
||||
```
|
||||
- `AAAA` レコードを作成するには、apex ドメインが {% data variables.product.prodname_pages %} の IP アドレスを指すようにします。
|
||||
- To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
|
||||
```shell
|
||||
2606:50c0:8000::153
|
||||
2606:50c0:8001::153
|
||||
@@ -89,9 +99,10 @@ DNS レコードの構成が正しいかどうかを確認するために利用
|
||||
2606:50c0:8003::153
|
||||
```
|
||||
|
||||
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. DNS レコードが正しく構成されていることを確認するには、`dig` コマンドを使用します。_EXAMPLE.COM_ はご利用の apex ドメインに置き換えてください。 結果が、上記の {% data variables.product.prodname_pages %} の IP アドレスに一致することを確認します。
|
||||
- `A` レコードの場合。
|
||||
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
|
||||
- For `A` records.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer -t A
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.108.153
|
||||
@@ -99,7 +110,7 @@ DNS レコードの構成が正しいかどうかを確認するために利用
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.110.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.111.153
|
||||
```
|
||||
- `AAAA` レコードの場合。
|
||||
- For `AAAA` records.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer -t AAAA
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8000::153
|
||||
@@ -107,18 +118,19 @@ DNS レコードの構成が正しいかどうかを確認するために利用
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8002::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8003::153
|
||||
```
|
||||
{% data reusables.pages.build-locally-download-cname %} {% data reusables.pages.enforce-https-custom-domain %}
|
||||
{% data reusables.pages.build-locally-download-cname %}
|
||||
{% data reusables.pages.enforce-https-custom-domain %}
|
||||
|
||||
## apex ドメインと `www` サブドメイン バリアントの構成
|
||||
## Configuring an apex domain and the `www` subdomain variant
|
||||
|
||||
apex ドメインを使用する場合は、コンテンツを apex ドメインとそのドメインの `www` サブドメイン バリアントの両方でホストするように {% data variables.product.prodname_pages %} サイトを構成することをお勧めします。
|
||||
When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant.
|
||||
|
||||
apex ドメインと共に `www` サブドメインを設定するには、まず、DNS プロバイダーで `ALIAS`、`ANAME`、または `A` レコードを作成して、apex ドメインを構成する必要があります。 詳細については、「[Apex ドメインを設定する](#configuring-an-apex-domain)」を参照してください。
|
||||
To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain by creating an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)."
|
||||
|
||||
Apexドメインを設定したら、DNSプロバイダでCNAMEレコードを設定しなければなりません。
|
||||
After you configure the apex domain, you must configure a CNAME record with your DNS provider.
|
||||
|
||||
1. DNS プロバイダーに移動し、`www.example.com` がサイトの既定のドメイン (`<user>.github.io` または `<organization>.github.io`) を指す `CNAME` レコードを作成します。 リポジトリ名は含めないでください。 {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
2. DNS レコードが正しく構成されたことを確認するには、`dig` コマンドを使用します。_WWW.EXAMPLE.COM_ は、ご利用の `www` サブドメイン バリアントに置き換えてください。
|
||||
1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
|
||||
```shell
|
||||
$ dig <em>WWW.EXAMPLE.COM</em> +nostats +nocomments +nocmd
|
||||
> ;<em>WWW.EXAMPLE.COM.</em> IN A
|
||||
@@ -126,16 +138,18 @@ Apexドメインを設定したら、DNSプロバイダでCNAMEレコードを
|
||||
> <em>YOUR-USERNAME</em>.github.io. 43192 IN CNAME <em> GITHUB-PAGES-SERVER </em>.
|
||||
> <em> GITHUB-PAGES-SERVER </em>. 22 IN A 192.0.2.1
|
||||
```
|
||||
## カスタムドメインの削除
|
||||
## Removing a custom domain
|
||||
|
||||
{% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
|
||||
4. [カスタム ドメイン] で、 **[削除]** をクリックします。
|
||||
![カスタム ドメインの [保存] ボタン](/assets/images/help/pages/remove-custom-domain.png)
|
||||
{% data reusables.pages.navigate-site-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.pages.sidebar-pages %}
|
||||
4. Under "Custom domain," click **Remove**.
|
||||
|
||||
|
||||
## カスタムドメインの保護
|
||||
## Securing your custom domain
|
||||
|
||||
{% data reusables.pages.secure-your-domain %} 詳細については、「[{% data variables.product.prodname_pages %} のカスタム ドメインの検証](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)」を参照してください。
|
||||
{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- "[カスタム ドメインと {% data variables.product.prodname_pages %} のトラブルシューティング](/articles/troubleshooting-custom-domains-and-github-pages)"
|
||||
- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
|
||||
|
||||
@@ -1,14 +1,7 @@
|
||||
---
|
||||
ms.openlocfilehash: 2aec9cd701a3503386b9d751c1da74f64940c431
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147496437"
|
||||
---
|
||||
{% ifversion fpt %} {% note %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**注:** pull request のマージ キュー機能は現在、限定的なパブリック ベータ版であり、変更される可能性があります。
|
||||
**Note:** The pull request merge queue feature is currently in limited public beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -1,13 +1,6 @@
|
||||
---
|
||||
ms.openlocfilehash: e2c781f830b789fbb8fdaaa9403fe4c7a37c63b5
|
||||
ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: "147878527"
|
||||
---
|
||||
`number`|`integer` | pull request 番号。
|
||||
`changes`|`object` | アクションが `edited` の場合のコメントの変更。
|
||||
`changes[title][from]`|`string` | アクションが `edited` の場合の以前のバージョンのタイトル。
|
||||
`changes[body][from]`|`string` | アクションが `edited` だった場合の本文の以前のバージョン。
|
||||
`pull_request`|`object` | [pull request](/rest/reference/pulls) 自体。
|
||||
`number`|`integer` | The pull request number.
|
||||
`changes`|`object`| The changes to the comment if the action was `edited`.
|
||||
`changes[title][from]`|`string` | The previous version of the title if the action was `edited`.
|
||||
`changes[body][from]`|`string` | The previous version of the body if the action was `edited`.
|
||||
`pull_request`|`object` | The [pull request](/rest/reference/pulls) itself.{% ifversion fpt or ghec %}
|
||||
`reason`|`string` | The reason the pull request was removed from a merge queue if the action was `dequeued`.{% endif %}
|
||||
|
||||
@@ -1,11 +1,3 @@
|
||||
---
|
||||
ms.openlocfilehash: b7fde4d22f9d5e5e8b7a3d8f55b3ab19dee1185a
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "145087366"
|
||||
---
|
||||
キー | Type | [説明]
|
||||
Key | Type | Description
|
||||
----|------|-------------
|
||||
`action`|`string` | 実行されたアクション。 次のいずれかになります。<ul><li>`assigned`</li><li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li><li>`closed`: アクションが `closed` であり、`merged` キーが `false` である場合、プル要求はマージされていないコミットで閉じられました。 アクションが `closed` であり、`merged` キーが `true` である場合、プル要求はマージされました。</li><li>`converted_to_draft`</li><li>`edited`</li><li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: プル要求のヘッド ブランチが更新されたときにトリガーされます。 たとえば、ヘッド ブランチがベース ブランチから更新されたとき、新しいコミットがヘッド ブランチにプッシュされたとき、またはベース ブランチが変更されたときなどです。</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul>
|
||||
`action`|`string` | The action that was performed. Can be one of:<ul><li>`assigned`</li><li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li><li>`closed`: If the action is `closed` and the `merged` key is `false`, the pull request was closed with unmerged commits. If the action is `closed` and the `merged` key is `true`, the pull request was merged.</li><li>`converted_to_draft`</li>{% ifversion fpt or ghec %}<li>`dequeued`: Triggered when a pull request is removed from a merge queue</li>{% endif %}<li>`edited`</li>{% ifversion fpt or ghec %}<li>`enqueued`: Triggered when a pull request is added to a merge queue</li>{% endif %}<li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Triggered when a pull request's head branch is updated. For example, when the head branch is updated from the base branch, when new commits are pushed to the head branch, or when the base branch is changed.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul>
|
||||
|
||||
@@ -253,7 +253,7 @@ translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-pers
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
|
||||
translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
|
||||
translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
|
||||
translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
|
||||
@@ -310,7 +310,7 @@ translations/ja-JP/content/admin/overview/accessing-compliance-reports-for-your-
|
||||
translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,rendering error
|
||||
translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
|
||||
translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
|
||||
@@ -346,7 +346,7 @@ translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/a
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md,rendering error
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error
|
||||
translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error
|
||||
translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error
|
||||
translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md,rendering error
|
||||
translations/ja-JP/content/code-security/getting-started/github-security-features.md,rendering error
|
||||
translations/ja-JP/content/code-security/getting-started/securing-your-organization.md,rendering error
|
||||
@@ -383,7 +383,7 @@ translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-code
|
||||
translations/ja-JP/content/codespaces/getting-started/deep-dive.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/getting-started/quickstart.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md,rendering error
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,rendering error
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,rendering error
|
||||
@@ -458,6 +458,7 @@ translations/ja-JP/content/organizations/restricting-access-to-your-organization
|
||||
translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
|
||||
translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
|
||||
translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
|
||||
translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,broken liquid tags
|
||||
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,broken liquid tags
|
||||
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
|
||||
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,broken liquid tags
|
||||
@@ -605,6 +606,7 @@ translations/ja-JP/data/reusables/organizations/security.md,rendering error
|
||||
translations/ja-JP/data/reusables/organizations/teams_sidebar.md,rendering error
|
||||
translations/ja-JP/data/reusables/organizations/verified-domains.md,rendering error
|
||||
translations/ja-JP/data/reusables/pages/sidebar-pages.md,rendering error
|
||||
translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/repositories/blocked-passwords.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/repositories/changed-files.md,broken liquid tags
|
||||
@@ -631,3 +633,5 @@ translations/ja-JP/data/reusables/user-settings/saved_replies.md,rendering error
|
||||
translations/ja-JP/data/reusables/user-settings/security-analysis.md,rendering error
|
||||
translations/ja-JP/data/reusables/user-settings/security.md,rendering error
|
||||
translations/ja-JP/data/reusables/user-settings/ssh.md,rendering error
|
||||
translations/ja-JP/data/reusables/webhooks/pull_request_properties.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags
|
||||
|
||||
|
Reference in New Issue
Block a user