New translation batch for pt (#31346)
This commit is contained in:
docubot
@@ -241,7 +241,7 @@ translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-pers
|
||||
translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
|
||||
translations/pt-BR/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/pt-BR/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/pt-BR/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/pt-BR/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/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
|
||||
translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
|
||||
translations/pt-BR/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
|
||||
@@ -308,7 +308,7 @@ translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-
|
||||
translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
|
||||
translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,broken liquid tags
|
||||
translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
|
||||
translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,broken liquid tags
|
||||
translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
|
||||
translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md,broken liquid tags
|
||||
translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
|
||||
translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
@@ -352,7 +352,7 @@ translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/a
|
||||
translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md,rendering error
|
||||
translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error
|
||||
translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error
|
||||
translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,broken liquid tags
|
||||
translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error
|
||||
translations/pt-BR/content/code-security/getting-started/github-security-features.md,rendering error
|
||||
translations/pt-BR/content/code-security/getting-started/securing-your-repository.md,rendering error
|
||||
translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
|
||||
@@ -391,7 +391,7 @@ translations/pt-BR/content/codespaces/getting-started/deep-dive.md,broken liquid
|
||||
translations/pt-BR/content/codespaces/getting-started/quickstart.md,broken liquid tags
|
||||
translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags
|
||||
translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md,broken liquid tags
|
||||
translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,broken liquid tags
|
||||
translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error
|
||||
translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md,broken liquid tags
|
||||
translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,broken liquid tags
|
||||
translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,broken liquid tags
|
||||
@@ -459,7 +459,7 @@ translations/pt-BR/content/organizations/managing-access-to-your-organizations-r
|
||||
translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,rendering error
|
||||
translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md,rendering error
|
||||
translations/pt-BR/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md,broken liquid tags
|
||||
translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,broken liquid tags
|
||||
translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
|
||||
translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error
|
||||
translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md,rendering error
|
||||
translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
|
||||
@@ -472,6 +472,7 @@ translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages
|
||||
translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
|
||||
translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md,rendering error
|
||||
translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
|
||||
translations/pt-BR/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/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
|
||||
@@ -629,6 +630,7 @@ translations/pt-BR/data/reusables/organizations/security.md,rendering error
|
||||
translations/pt-BR/data/reusables/organizations/teams_sidebar.md,rendering error
|
||||
translations/pt-BR/data/reusables/organizations/verified-domains.md,rendering error
|
||||
translations/pt-BR/data/reusables/pages/sidebar-pages.md,rendering error
|
||||
translations/pt-BR/data/reusables/pull_requests/merge-queue-beta.md,broken liquid tags
|
||||
translations/pt-BR/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
|
||||
translations/pt-BR/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md,rendering error
|
||||
translations/pt-BR/data/reusables/repositories/changed-files.md,broken liquid tags
|
||||
@@ -652,5 +654,7 @@ translations/pt-BR/data/reusables/user-settings/saved_replies.md,rendering error
|
||||
translations/pt-BR/data/reusables/user-settings/security-analysis.md,rendering error
|
||||
translations/pt-BR/data/reusables/user-settings/security.md,rendering error
|
||||
translations/pt-BR/data/reusables/user-settings/ssh.md,rendering error
|
||||
translations/pt-BR/data/reusables/webhooks/pull_request_properties.md,broken liquid tags
|
||||
translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags
|
||||
translations/pt-BR/data/variables/migrations.yml,broken liquid tags
|
||||
translations/pt-BR/data/variables/notifications.yml,broken liquid tags
|
||||
|
||||
|
@@ -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: Gerenciar um domínio personalizado do seu site do GitHub Pages
|
||||
intro: 'É possível definir ou atualizar determinados registros DNS e as configurações de repositório para apontar o domínio padrão do seu site do {% data variables.product.prodname_pages %} para um domínio personalizado.'
|
||||
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: pt-BR
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147710320'
|
||||
---
|
||||
Pessoas com permissões de administrador para um repositório podem configurar um domínio personalizado de um site do {% data variables.product.prodname_pages %}.
|
||||
|
||||
## Sobre a configuração de domínio personalizado
|
||||
People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site.
|
||||
|
||||
Lembre-se de adicionar o domínio personalizado ao seu site do {% data variables.product.prodname_pages %} antes de configurar o domínio personalizado com o provedor DNS. Se você configurar o domínio personalizado com o provedor DNS sem adicioná-lo ao {% data variables.product.product_name %}, outra pessoa conseguirá hospedar um site em um dos seus subdomínios.
|
||||
## 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 %}
|
||||
|
||||
O comando `dig`, que pode ser usado para verificar a configuração correta dos registros DNS, não está incluído no Windows. Para verificar se os registros DNS estão configurados corretamente, instale o [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 %}
|
||||
|
||||
**Observação:** as alterações de DNS podem levar até 24 horas para serem propagadas.
|
||||
**Note:** DNS changes can take up to 24 hours to propagate.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Configurando um subdomínio
|
||||
## Configuring a subdomain
|
||||
|
||||
Para configurar um subdomínio `www` ou personalizado, como `www.example.com` ou `blog.example.com`, você precisa adicionar seu domínio às configurações do repositório. Em seguida, configure um registro CNAME com seu provedor DNS.
|
||||
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. Em "Domínio personalizado", digite seu domínio personalizado e clique em **Salvar**. Se você estiver publicando seu site de um branch, isso criará um commit que adiciona um arquivo `CNAME` à raiz do branch de origem. Se você estiver publicando seu site com um fluxo de trabalho de {% data variables.product.prodname_actions %}, nenhum arquivo `CNAME` será criado. Para obter mais informações sobre a sua fonte de publicação, confira "[Como configurar uma fonte de publicação para o seu site do GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
|
||||
|
||||
5. Navegue até o provedor DNS e crie um registro `CNAME` que aponte o subdomínio para o domínio padrão do seu site. Por exemplo, se você quiser usar o subdomínio `www.example.com` para seu site de usuário, crie um registro `CNAME` que aponte `www.example.com` para `<user>.github.io`. Caso deseje usar o subdomínio `another.example.com` para seu site de organização, crie um registro `CNAME` que aponte `another.example.com` para `<organization>.github.io`. O registro `CNAME` deve sempre apontar para `<user>.github.io` ou `<organization>.github.io`, excluindo o nome do repositório. {% 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. Para confirmar se o registro DNS foi configurado corretamente, use o comando `dig`, substituindo _WWW.EXAMPLE.COM_ pelo subdomínio.
|
||||
{% 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 @@ Para configurar um subdomínio `www` ou personalizado, como `www.example.com` ou
|
||||
> <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 %}
|
||||
|
||||
## Configurando um domínio apex
|
||||
## Configuring an apex domain
|
||||
|
||||
Para configurar um domínio apex, como `example.com`, você precisa configurar um domínio personalizado nas configurações do seu repositório e pelo menos um registro `ALIAS`, `ANAME` ou `A` com seu provedor DNS.
|
||||
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 %} Para obter mais informações, confira "[Como configurar um subdomínio](#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. Em "Domínio personalizado", digite seu domínio personalizado e clique em **Salvar**. Se você estiver publicando seu site de um branch, isso criará um commit que adiciona um arquivo `CNAME` à raiz do branch de origem. Se você estiver publicando seu site com um fluxo de trabalho de {% data variables.product.prodname_actions %}, nenhum arquivo `CNAME` será criado. Para obter mais informações sobre a sua fonte de publicação, confira "[Como configurar uma fonte de publicação para o seu site do GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
|
||||
|
||||
5. Navegue até o provedor DNS e crie um registro `ALIAS`, `ANAME` ou `A`. Crie também registros `AAAA` para suporte ao IPv6. {% data reusables.pages.contact-dns-provider %}
|
||||
- Para criar um registro `ALIAS` ou um registro `ANAME`, aponte seu domínio apex para o domínio padrão do seu site. {% data reusables.pages.default-domain-information %}
|
||||
- Para criar registros `A`, aponte seu domínio apex para os endereços IP do {% data variables.product.prodname_pages %}.
|
||||
{% 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
|
||||
```
|
||||
- Para criar registros `AAAA`, aponte seu domínio apex para os endereços IP do {% data variables.product.prodname_pages %}.
|
||||
- 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 @@ Para configurar um domínio apex, como `example.com`, você precisa configurar u
|
||||
2606:50c0:8003::153
|
||||
```
|
||||
|
||||
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. Para confirmar se o registro DNS foi configurado corretamente, use o comando `dig`, substituindo _EXAMPLE.COM_ pelo domínio apex. Confirme que os resultados correspondem aos endereços IP do {% data variables.product.prodname_pages %} acima.
|
||||
- Para registros `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 @@ Para configurar um domínio apex, como `example.com`, você precisa configurar u
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.110.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.111.153
|
||||
```
|
||||
- Para registros `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 @@ Para configurar um domínio apex, como `example.com`, você precisa configurar u
|
||||
> <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 %}
|
||||
|
||||
## Como configurar um domínio apex e a variante de subdomínio `www`
|
||||
## Configuring an apex domain and the `www` subdomain variant
|
||||
|
||||
Quando você usar um domínio apex, recomendamos que você configure seu site do {% data variables.product.prodname_pages %} para hospedar o conteúdo no domínio apex e na variante de subdomínio `www`.
|
||||
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.
|
||||
|
||||
Para configurar um subdomínio `www` ao lado do domínio apex, primeiro, você precisa configurar um domínio apex criando um registro `ALIAS`, `ANAME` ou `A` com o provedor DNS. Para obter mais informações, confira "[Como configurar um domínio 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)."
|
||||
|
||||
Depois de configurar o domínio apex, você deverá configurar um registro CNAME com seu provedor DNS.
|
||||
After you configure the apex domain, you must configure a CNAME record with your DNS provider.
|
||||
|
||||
1. Navegue até o provedor DNS e crie um registro `CNAME` que aponte `www.example.com` para o domínio padrão do seu site: `<user>.github.io` ou `<organization>.github.io`. Não inclua o nome do repositório. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
|
||||
2. Para confirmar se o registro DNS foi configurado corretamente, use o comando `dig`, substituindo _WWW.EXAMPLE.COM_ pela variante de subdomínio `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 @@ Depois de configurar o domínio apex, você deverá configurar um registro 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
|
||||
```
|
||||
## Remover um domínio personalizado
|
||||
## Removing a custom domain
|
||||
|
||||
{% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
|
||||
4. Em "Domínio personalizado", clique em **Remover**.
|
||||
|
||||
{% data reusables.pages.navigate-site-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.pages.sidebar-pages %}
|
||||
4. Under "Custom domain," click **Remove**.
|
||||
|
||||
|
||||
## Protegendo seu domínio personalizado
|
||||
## Securing your custom domain
|
||||
|
||||
{% data reusables.pages.secure-your-domain %} Para obter mais informações, confira "[Como verificar seu domínio personalizado do {% 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)."
|
||||
|
||||
## Leitura adicional
|
||||
## Further reading
|
||||
|
||||
- "[Solução de problemas de domínios personalizados e do {% 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: pt-BR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147496433"
|
||||
---
|
||||
{% ifversion fpt %} {% note %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**Observação:** atualmente, o recurso de fila de mesclagem da solicitação de pull está em versão beta pública limitada e sujeito a alterações.
|
||||
**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: pt-BR
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: "147875515"
|
||||
---
|
||||
`number`|`integer` | O número da solicitação de pull.
|
||||
`changes`|`object`| As alterações no comentário se a ação foi `edited`.
|
||||
`changes[title][from]`|`string` | A versão anterior do título se a ação foi `edited`.
|
||||
`changes[body][from]`|`string` | A versão anterior do corpo se a ação foi `edited`.
|
||||
`pull_request`|`object` | A própria [solicitação de pull](/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: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: "145083272"
|
||||
---
|
||||
Chave | Tipo | Descrição
|
||||
Key | Type | Description
|
||||
----|------|-------------
|
||||
`action`|`string` | A ação que foi executada. Pode ser uma das ações a seguir:<ul><li>`assigned`</li><li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li><li>`closed`: se a ação é `closed` e a chave `merged` é `false`, a solicitação de pull foi fechada com commits não mesclados. Se a ação é `closed` e a chave `merged` é `true`, a solicitação de pull foi mesclada.</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`: disparada quando o branch principal de uma solicitação de pull é atualizado. Por exemplo, quando o branch principal é atualizado com base no branch base, quando novos commits são enviados por push para o branch principal ou quando o branch base é alterado.</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>
|
||||
|
||||
Reference in New Issue
Block a user