From 72dc13e723c021cbdfa66a15283d5e85ef51e67f Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Sat, 19 Nov 2022 08:59:06 -0800 Subject: [PATCH] New translation batch for pt (#32774) --- translations/log/msft-pt-resets.csv | 6 +++--- .../configuring-your-enterprise/command-line-utilities.md | 2 ++ .../configuration-options-for-the-dependabot.yml-file.md | 2 +- .../pt-BR/content/get-started/quickstart/fork-a-repo.md | 6 +++--- .../splitting-a-subfolder-out-into-a-new-repository.md | 2 +- 5 files changed, 10 insertions(+), 8 deletions(-) diff --git a/translations/log/msft-pt-resets.csv b/translations/log/msft-pt-resets.csv index 01832857fb..a62377b995 100644 --- a/translations/log/msft-pt-resets.csv +++ b/translations/log/msft-pt-resets.csv @@ -790,7 +790,7 @@ translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/set translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,broken liquid tags -translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags +translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md,rendering error translations/pt-BR/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,broken liquid tags translations/pt-BR/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags translations/pt-BR/content/codespaces/troubleshooting/index.md,broken liquid tags @@ -1275,7 +1275,7 @@ 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/repository_vulnerability_alert_short_desc.md,broken liquid tags translations/pt-BR/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags -translations/pt-BR/data/variables/migrations.yml,broken liquid tags +translations/pt-BR/data/variables/migrations.yml,rendering error translations/pt-BR/data/variables/notifications.yml,broken liquid tags -translations/pt-BR/data/variables/product.yml,broken liquid tags +translations/pt-BR/data/variables/product.yml,rendering error translations/pt-BR/data/variables/projects.yml,broken liquid tags diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 7c9921bd9a..81e5573b49 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -895,6 +895,8 @@ ghe-upgrade UPGRADE-PACKAGE-FILENAME This utility manages scheduled installation of upgrade packages. You can show, create new, or remove scheduled installations. You must create schedules using cron expressions. For more information, see the [Cron Wikipedia entry](https://en.wikipedia.org/wiki/Cron#Overview). +The `ghe-upgrade-scheduler` utility is best suited for scheduling hotpatch upgrades, which do not require maintenance mode or a reboot in most cases. This utility is not practical for full package upgrades, which require an administrator to manually set maintenance mode, reboot the instance, and unset maintenance mode. For more information about the different types of upgrades, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/upgrading-github-enterprise-server#upgrading-with-an-upgrade-package)" + To schedule a new installation for a package: ```shell $ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md index eaefe0047a..e597d6e5fc 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md @@ -244,7 +244,7 @@ Supported options {% note %} -**Note:** The `prefix` and the `prefix-development` options have a 15 character limit. +**Note:** The `prefix` and the `prefix-development` options have a {% ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}50{% elsif ghes < 3.8 or ghae < 3.8 %}15{% endif %} character limit. {% endnote %} diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md index a8107f1dd2..553a37ad5e 100644 --- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md @@ -175,10 +175,10 @@ When you fork a project in order to propose changes to the original repository, 7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/ YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (fetch) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) ``` Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)." diff --git a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 672cc12698..95dee0189f 100644 --- a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -30,7 +30,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist $ cd REPOSITORY-NAME ``` -5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information: +5. To filter out the subfolder from the rest of the files in the repository, install [`git-filter-repo`](https://github.com/newren/git-filter-repo), then run `git filter-repo` with the following arguments. - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository. {% windows %}